On Wed, Jun 12, 2002 at 06:50:10PM -0400, Jeff Garzik wrote:
>
> Sure, that would be fine too.
>
> The main user demand has been for 2.4.x drivers on 2.2.x. If there is
> demand for 2.0.x driver support or, what you describe, 2.5.x driver
> support on 2.[24].x, that's a good direction to head towards. I haven't
> seen any requests for that from driver authors yet.
It seems that most of the 2.5.X construct are also available
in 2.4.X, but 2.5.X obsolete some of the old 2.4.X construct (for
example pci API).
For me, the problem between 2.5.X and 2.4.X is the USB API
which has significantely changed (urb_submit anyone ?). I end up
having two quite different version of irda-usb to maintain. But
probably USB in 2.5.X. is too much a moving target for you to include
in your package.
> I am sadly guilty of "NIH" in several cases, but actually this is not
> one of them :) I think that kcompat24 provides a bit more of a complete
> compatibility package than the other solutions. So, I would like to
> borrow code from pcmcia and other sources to make this toolkit even
> better. (patches accepted! :))
Actually, NIH works both ways (so don't take personally). It
would be nice to have David Hinds using your package, because you
would immediately gain a sizeable user base, and because a lot of
Pcmcia drivers are both in the kernel and the Pcmcia package, and some
pour souls attempt to keep them in sync.
For example, we currently have a unsatisfactory situation with
the orinoco and airo drivers.
By the way, I didn't look in detail at kcompat24, but I
guarantee you that the latest Pcmcia package has quite a complete
solution.
> Jeff
Have fun...
Jean
-
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/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:27 EST