Messages in this thread | | | From | Pete Clements <> | Subject | 2.6.0-test1 and second 3c509 | Date | Tue, 15 Jul 2003 11:13:27 -0400 (EDT) |
| |
Just a reminder, I'm still backing out the 2.5.71 3c509 changes to get my second 3c509 card. Glad to test.
Quoting viro@parcelfarce.linux.theplanet.co.uk > On Sun, Jun 15, 2003 at 09:52:01AM -0700, David S. Miller wrote: > > From: Pete Clements <clem@clem.clem-digital.net> > > Date: Sun, 15 Jun 2003 12:50:25 -0400 (EDT) > > > > >From boot log: > > > > Kernel command line: auto BOOT_IMAGE=Linux ro root=341 ether=9,0x310,4,0x3c509,eth1 > > > > Yes, that explains why the second card isn't found. > > > > The problem is: > > > > 1) the we can't assign a name to the device > > until we've registered it with the networking > > > > 2) without a name the boot argument lookup doesn't work > > > > 3) we have to register the device with the networking only > > after it is initialized > > > > Hmmm... > > Crap. AFAICS, the clean solution would be to pass these guys (blah_probe()) > expected device name. And let them do allocation, etc., themselves. > > Looking into it... >
-- Pete Clements
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |