From: Christoph Hellwig <hch@infradead.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
solca@guug.org, zaitcev@redhat.com, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, debian-sparc@lists.debian.org
Subject: Re: sparc scsi esp depends on pci & hangs on boot
Date: Wed, 23 Jul 2003 07:40:33 +0100 [thread overview]
Message-ID: <20030723074033.A1687@infradead.org> (raw)
In-Reply-To: <20030722232911.2e6fda86.davem@redhat.com>; from davem@redhat.com on Tue, Jul 22, 2003 at 11:29:11PM -0700
On Tue, Jul 22, 2003 at 11:29:11PM -0700, David S. Miller wrote:
> And unlike this particular scsi layer usage, such drivers will be
> dependant upon things like CONFIG_PCI and thus won't get compiled
> in unless CONFIG_PCI has been enabled in the kernel configuration.
Umm, no. The whole idea of the DMA mapping API is that it's independant
of the underlying bus. Think of usb or ieee1394 drivers doing direct DMA
independant of the bus the underlying host adapter uses.
> And linux/dma-mapping.h is a bad name to use, call it dma-dir.h or
> something, because linux/dma-mapping.h would need to include
> asm/dma-mapping.h which is what we're trying to avoid here.
We don't try to avoid that. You should at least make them sparc dma
mapping API noops for !CONFIG_PCI because it's assume you always
include the header - whether you can actually use the functionaly
depends on whether your bus supports this API.
next prev parent reply other threads:[~2003-07-23 6:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 2:51 sparc scsi esp depends on pci & hangs on boot Otto Solares
2003-07-22 12:09 ` Pete Zaitcev
2003-07-22 18:26 ` Otto Solares
2003-07-23 0:54 ` David S. Miller
2003-07-23 2:32 ` Otto Solares
2003-07-23 6:07 ` Christoph Hellwig
2003-07-23 6:24 ` David S. Miller
2003-07-23 6:28 ` Christoph Hellwig
2003-07-23 6:29 ` David S. Miller
2003-07-23 6:40 ` Christoph Hellwig [this message]
2003-07-23 6:57 ` David S. Miller
2003-07-23 7:02 ` Christoph Hellwig
2003-07-23 7:20 ` David S. Miller
2003-07-23 8:45 ` Otto Solares
2003-07-23 14:42 ` Geert Uytterhoeven
2003-07-23 6:43 ` Otto Solares
2003-07-23 7:04 ` Christoph Hellwig
2003-07-23 7:20 ` Otto Solares
2003-07-23 7:27 ` David S. Miller
2003-07-23 8:33 ` C.Newport
2003-07-23 8:28 ` David S. Miller
2003-07-23 9:35 ` C.Newport
2003-07-23 9:37 ` David S. Miller
2003-07-23 8:55 ` Otto Solares
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=20030723074033.A1687@infradead.org \
--to=hch@infradead.org \
--cc=davem@redhat.com \
--cc=debian-sparc@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solca@guug.org \
--cc=sparclinux@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).