Jean Tourrilhes wrote:
> Jeff Garzik wrote :
>
>>Don't load your drivers up with 2.2.x compatibility junk. Write a 2.4.x
>>driver... and use this toolkit to make it work under 2.2.
>
>
> Actually, wouldn't it be better to have people writting 2.5.X
> driver and having your toolkit enabling them for 2.4.X and 2.2.X ?
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.
> Also, have you looked at the Pcmcia package, David Hinds has a
> pretty complete compatibility toolkit going back to 1.2.X, and used by
> many Pcmcia drivers (it's actually pretty amazing to see all those
> Pcmcia drivers working regardless). Maybe you could propose David a
> merge of the two (you get some more code and some more userbase).
> Yes, of course, NIH...
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! :))
Jeff
-
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:26 EST