Actually the main trouble I see is with external
drivers that could already exist but may never
make it into the kernel, such as:
- the Compaq PJB-100 (but it's OK, I checked it)
- IONetworks
- Nemosoft's Philips webcam driver(s) [but he could/would
fix it]
- SmartBridges USB-ethernet
- the Alcatel DSL driver [but Johan would know better
or would fix it quickly]
- the Microtek scanner driver (but it's OK, I checked it;
or Oliver could update it if needed)
We could be breaking some drivers quickly.
However, I'm in favor of doing it sooner than later.
Until we remove them, we could add a printk("driver is using a
deprecated API") each time one of them is called.
That could make a large log file...
> On Thu, 4 May 2000, Johannes Erdfelt wrote:
>
> > For a couple of reasons. If people don't want to use my
> driver, there's
> > very little reason to continue putting work into it. The
> same goes for
> > the AFS driver I would assume. Plus, trying to support 2
> drivers on the
> > list when lots of people start using USB will be more
> trouble than it's worth.
>
> I agree with you. However, I've only ever used your driver so
> we should
> allow time for people who use the one that will disappear to verify
> functionality of the one that will be kept.
Good point.
> > It could go either way. Remove them now before 2.4 gets
> released and find
> > the broken drivers now, or have to support them all of the
> way through 2.4.
>
> Without actually having a driver to support myself I'd say
> removing them
> sooner is better. The main trouble I see is for drivers not yet in the
> kernel.
~Randy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
