On Thu, Jan 29, 2009 at 12:16 PM, Mike Ditto <mdi...@consentry.com> wrote: > But I can't explain why the driver isn't attaching for you. Did you > try it built-in instead of as a module? >
Hi Mike et al, I am trying it built-in at the moment (ie. not as a module). I've stuck a whole bunch of printks() in. This is what is happening during boot-up: 1) fs_init() from fs_enet-main.c is called 2) This in turn calls driver_register() with the 'fs_enet' driver 3) This results in a call to bus_add_driver() with the following parameters: driver = 'fs_enet' driver bus = 'of_platform' bus 4) Then, driver_attach() is called with 'fs_enet' driver as the parameter 5) driver_attach() calls bus_for_each_dev() with "__driver_attach()" and the 'of_platform' bus as the relevant parameters However, __driver_attach() is never called from bus_for_each_dev() ie. there seems to be no devices on the 'of_platform' bus. Hence, is there some way to add an appropriate device to the 'of_platform' bus so that __driver_attach() can be called for that device? Or, perhaps it is ok for the 'of_platform' bus to have no devices on it, and so I might be using the wrong bus?? Why would this be? Or is it something else?? Either way, I still get the following boot error message: IP-Config: Device `eth0' not found. -and fs_enet_probe() is NEVER called. Cheers, Daniel _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
