Messages in this thread | | | Subject | Re: Re[2]: 2.0.x <-> 2.1.x => eth0 <-> eth1 (almost) | Date | Fri, 01 May 1998 21:55:12 +0200 | From | David Woodhouse <> |
| |
> > >I think you can compile it as module, then add > >alias eth0 card0 > >alias eth1 card1 > > >to /etc/conf=2Emodule
Boot like this. Bring up eth1. Then bring up eth0. Spot the problem.
Admittedly, this isn't a huge problem in the case of network devices, as long as you bring them up in the right order. However, an identical problem exists with the sound drivers, and other such subsystems (SCSI, video4linux,...)
Par example: If I access the synth device first, mixer0 is the AWE equaliser, but if I access the wave device first, it's the real mixer.
We need some mechanism for telling a module what device it's been loaded to support. If we pass it an extra argument telling it the device # or name that caused it to be loaded, then it's got a chance of turning up in the right place.
---- ---- ---- David Woodhouse, Robinson College, CB3 9AN, England. (+44) 0976 658355 Dave@imladris.demon.co.uk http://www.imladris.demon.co.uk finger pgp@dwmw2.robinson.cam.ac.uk for PGP key.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |