On Thu, Dec 02, 2004 at 11:40:55AM +1100, Andrew Pollock wrote: > On Wed, Dec 01, 2004 at 01:51:28PM +0100, Josselin Mouette wrote: > > Le mercredi 01 d??cembre 2004 ?? 18:48 +0900, Horms a ??crit : > > > > Another example are the Realtek 8149 drivers. I had to blacklist one > > > > of the drivers. This chipset is really common. So many people will > > > > have to do this. > > > > > > If the blacklist exists for other devices, then yes this sounds like > > > a good idea. The e100 should be used over the eepro100 as > > > the later is in the process of being debricated upstream. > > > > The solution looks obvious: don't build these deprecated drivers when > > there is already one working driver in the same kernel package. > > > > Or build them, but put them in a directory which depmod and hotplug will > > omit. The module will still be loadable by hand, but won't be used by > > default. > > Apart from the issue Jerome mentions where some older hardware isn't > supported by e100 but is supported by eepr100, what if new kernels didn't > build/provide eepro100 and instead eepro100 was aliased to e100, or do they > have incompatible parameters?
I am quite confortable with not including the eepro100 driver as it is being debricated upstream. -- Horms
