.c (board-specific code) read
> the MAC from the board, and pass it to ixpdev.c (generic code) in the
> net_device structure.
that perfectly doable, but maybe having one common interface could
be a cleaner solution. your setup is board -> netdriver
while maclist implements board -> stor
devices like nas, routers et al which already
have been widely deployed.
I know that the solution would be to fix the bootloader, but
Joe Average is a little bit scared of reflashing it.
A maclist-alike system could help to solve that situation.
--
Best regards,
Alessandro Zummo,
Tow
cility can clean some of the mess in that area.
If we implement such a thing in userspace every distribution
will need to be aware of a specific trick for a specific
board. If we have a clean facility in the kernel, userspace
will not need to care.
--
Best regards,
Alessandro Zummo,
> ioctl?
Because sometimes you need to have networking available
well before userspace.
(netconsole, root over nfs, ...)
--
Best regards,
Alessandro Zummo,
Tower Technologies - Turin, Italy
http://www.towertech.it
-
To unsubscribe from this list: send the line "unsubs
