On Thu, Apr 2, 2020 at 6:50 PM amf <[email protected]> wrote: > > The driver appears to be 8 yrs old, this puts it in kernel version 3.x or > possibly 2.x, a lot of kernel api calls have changed since then. A starting > point would be to get the kernel source that your using in the Stretch > release, add the driver (if it is not already there) and see if you can build > it. However you will most likely need to make driver changes to get it to > build. (IMO). > > Freescale (NXP) maintained there own kernel for LTIB/MX28. So IMO, you will > have some work to do. > > Good luck. > Amf > > On Wednesday, April 1, 2020 at 4:12:18 PM UTC-5, beagleInThePocket wrote: >> >> Currently I have a program that sends/receives data over the ethernet/wlan >> etc. network interface on the PocketBeagle. What I'm trying to achieve is >> simply have the SPI port configured as a Linux network interface to >> send/receive data to a Qualcomm QCA7000 chip (serial-to-powerline bridge >> chip). >> Qualcomm provides the following drivers and only the following drivers to >> access their QCA7000 chip over SPI (qca-spi). How does one actually use >> these SPI drivers on the PocketBeagle (running Debian Stretch IoT)? Are the >> drivers necessary and will they even work at all, or will I need to make use >> of Linux kernel spidev device driver? Not sure if the device tree needs to >> be considered here too, I am very overwhelmed by this concept.
I did give it a go and try to compile on my BeagleBone Black running 5.5.9 kernel. Here are the results: https://gist.github.com/pdp7/22442e49c75570e52e473aa81ec5f68f Notably: qca-spi/qca_spi.c:828:5: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’? qca-spi/qca_spi.c:1079:80: error: macro "alloc_netdev" requires 4 arguments, but only 3 given -Drew -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAEf4M_D-e7qTb5rBrOVW_%2B1m1zp9sNVL3Na0LCkMYmeZrXsSmg%40mail.gmail.com.
