From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Richard A Nelson <cowboy@vnet.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Sample device driver - 2.2 and 2.4 support?
Date: Sat, 04 Nov 2000 01:21:57 -0500 [thread overview]
Message-ID: <3A03AB05.5BD95C8B@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0011021711120.1544-100000@badlands.lexington.ibm.com>
Richard A Nelson wrote:
> I've been assigned a device driver that uses the old (2.0) PCI
> support APIs - and is still working on 2.2.
>
> I need to get this driver working on 2.2 and 2.4, I'm assuming I'll
> need to go switch to the newer PCI stuff - but am curious about the
> toleration support in later 2.2 kernels; is it complete enough that
> I can migrate to 2.4, and still compile on 2.2?
You can still use the 2.0.x PCI functions on 2.4.x. They are slower
than the 'struct pci_dev' versions of the functions, because each
pcibios_xxx call incurs a call to pci_find_slot().
>
> The device:
> 1-2 DMA
> 1 IRQ
>
> The driver:
> mkalloc
> __get_free_pages
> virt_to_bus
> request_irc
> wake_up
>
> The driver has similiar functionality to a sound card:
> Send/Receive (possibly large) data to device via DMA (page fixing, etc)
>
> Is there a cononical example (esp. wrt 2.2 <-> 2.4 changes) I should look
> at ?
That depends on both the changes and your driver... Every driver is
different, so nothing is really canonical WRT driver API changes. If
your driver is similar to a sound card, then look at drivers/sound/*.c
...
Jeff
--
Jeff Garzik | Dinner is ready when
Building 1024 | the smoke alarm goes off.
MandrakeSoft | -/usr/games/fortune
-
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/
prev parent reply other threads:[~2000-11-04 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-02 22:32 Sample device driver - 2.2 and 2.4 support? Richard A Nelson
2000-11-04 6:21 ` 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=3A03AB05.5BD95C8B@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=cowboy@vnet.ibm.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