From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Steven_Snyder@3com.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Porting Linux v2.2.x Ethernet driver to v2.4.x?
Date: Thu, 09 Nov 2000 13:10:21 -0500 [thread overview]
Message-ID: <3A0AE88D.FCA19A5A@mandrakesoft.com> (raw)
In-Reply-To: <88256992.00632296.00@hqoutbound.ops.3com.com>
Steven_Snyder@3com.com wrote:
>
> Hello.
>
> I am about to modify a Linux v2.2.x-compatible Ethernet driver to allow it to
> work in the new v2.4.x kernel. Are there any documents which describe the
> differences in the device driver models (particularly PCI and Ethernet) of the 2
> kernel versions? If so, where can I find them?
Not all in one place. Read:
Documentation/pci.txt
Documentation/DMA-mapping.txt
Documentation/IO-mapping.txt
and the attached document, regarding netdevice member locking rules.
Your best reference is other PCI ethernet drivers. grep for
'pci_module_init' in drivers/net/*.c of the most recent 2.4.x kernel,
for a good start.
Also... before you start thinking about gunking-up your driver with all
sorts of backwards-compatibility code... remember that most 2.4.x
drivers can easily be backported to 2.2.x with a few magic macros and
static inline functions. I have an example of this sort of thing at
http://gtf.org/garzik/drivers/kcompat24/
Jeff
--
Jeff Garzik |
Building 1024 | Would you like a Twinkie?
MandrakeSoft |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-09 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-09 18:01 Porting Linux v2.2.x Ethernet driver to v2.4.x? Steven_Snyder
2000-11-09 18:10 ` Jeff Garzik [this message]
2000-11-09 18:12 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 18:10 Dunlap, Randy
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=3A0AE88D.FCA19A5A@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Steven_Snyder@3com.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