From: Christoph Hellwig <hch@lst.de>
To: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [HEADS UP] planned change to <asm-generic/dma-mapping.h> will cause arch breakage
Date: Fri, 25 Apr 2003 13:40:20 +0200 [thread overview]
Message-ID: <20030425134020.A5644@lst.de> (raw)
To allow including <linux/dma-mapping.h> in generic code the default
implemtation of the dma-mapping API in terms of the PCI API will have
to go away. What does this mean for your architecture?
- If your architecture doesn't use <asm-generic/dma-mapping.h>
(arm, i386, parisc): Nothing.
- If your architecture doesn't support PCI (cris, s390. um):
Nothing, except that your arch won't break anymore if somsone
includes dma-mapping.h in generic code. But it would be cool to move
over your dma-capable busses to the dma-mapping API...
- Everyone else: Unless you properly implement the dma-mapping in
your architecture the dma_* APIs won't work anymore for you.
The simplest way to get support for it on pci busses is to change
your implementation of the pci_* dma functions to the dma_* prototypes
and add the following to their top:
struct pci_dev *pdev = to_pci_dev(dev);
and maybe
BUG_ON(dev->bus != &pci_bus_type);
Of course it would be much nicer if you could add support for the
dma-mapping API to your other dma-capable busses..
reply other threads:[~2003-04-25 11:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030425134020.A5644@lst.de \
--to=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--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