From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Re : ANN: Linux 2.2 driver compatibility toolkit
Date: Wed, 12 Jun 2002 18:50:10 -0400 [thread overview]
Message-ID: <3D07D022.5030106@mandrakesoft.com> (raw)
In-Reply-To: <20020610174050.A21783@bougret.hpl.hp.com>
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
next prev parent reply other threads:[~2002-06-12 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 0:40 Re : ANN: Linux 2.2 driver compatibility toolkit Jean Tourrilhes
2002-06-12 22:50 ` Jeff Garzik [this message]
2002-06-12 23:27 ` Jean Tourrilhes
2002-06-12 23:39 ` Greg KH
2002-06-12 23:50 ` Jean Tourrilhes
2002-06-12 23:57 ` Greg KH
2002-06-13 0:36 ` [linux-usb-devel] " Johannes Erdfelt
2002-06-13 4:31 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D07D022.5030106@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox