public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: ANN: Linux 2.2 driver compatibility toolkit
Date: Wed, 12 Jun 2002 18:47:29 -0400	[thread overview]
Message-ID: <3D07CF81.30904@mandrakesoft.com> (raw)
In-Reply-To: <200206111707.g5BH7qA10658@buggy.badula.org>

Ion Badulescu wrote:
> On Mon, 10 Jun 2002 17:40:18 -0400, Jeff Garzik <jgarzik@mandrakesoft.com> 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.
> 
> 
> Now, if you could get Alan to include it in 2.2.next, that would be even
> better. I could probably drop 90% of the cruft I have in starfire-kcomp22.h...



Absolutely....  I haven't mentioned this to Alan specifically, but it is 
indeed a direction I would like to go.  A good step would be getting 
your help to make sure that starfire works with kcompat24 (perhaps with 
minor patching)  :)  If we have tested patches ready for 2.2 that will 
go a long way towards winning Alan's acceptance, I'm sure.

Another idea I just had:  a good way to introduce kcompat24 to 2.2 is to 
use it to add a few 2.4.x-only net drivers to 2.2.  That way nothing 
changes [initially], only additions are made.

	Jeff



      reply	other threads:[~2002-06-12 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10 21:40 ANN: Linux 2.2 driver compatibility toolkit Jeff Garzik
2002-06-11 17:07 ` Ion Badulescu
2002-06-12 22:47   ` Jeff Garzik [this message]

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=3D07CF81.30904@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ionut@cs.columbia.edu \
    --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