> I think the error pretty much is what it says it is, the driver doesn't > appear to have a spi_device_id table containing lan8650. The name of > the driver is lan685x which is used in the fallback clause in > __spi_register_driver(), so it complains as it does not find lan8650 in > either. If my understanding is correct, either a spi_device_id table is > required or the driver needs a rename with s/x/0/. > Right you are, no gdb necessary. With the caveat that I only get it working when setting DRV_NAME to "lan8651", setting it to "lan8650" still produces the log R
