From: "Christian Böhme" <monodhs@gmx.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Interrupt routing broken on TiBook IV with 2.6.21.x ?
Date: Tue, 22 May 2007 01:44:49 +0200 [thread overview]
Message-ID: <46522EF1.6030804@gmx.de> (raw)
In-Reply-To: <1179789304.32247.760.camel@localhost.localdomain>
Benjamin Herrenschmidt wrote:
> I'm not sure what you are talking about here. DMA mapping has existed in
> linux for years.
I do admit that it's been a while since that last look ;) The topic came up
when discussing PCI and bus systems in general with micro/real-time kernel
people whom I assumed to be experts in this since they had Linux kernels
running on top of their scheduling scheme. As it turned out, using an
abstraction such as a DMA map was a totally new concept to them. They
even questioned the usefulness of such an approach.
Cheers,
Christian
prev parent reply other threads:[~2007-05-21 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 0:06 Interrupt routing broken on TiBook IV with 2.6.21.x ? Christian Böhme
2007-05-21 1:56 ` Benjamin Herrenschmidt
2007-05-21 20:08 ` Christian Böhme
2007-05-21 22:11 ` Benjamin Herrenschmidt
2007-05-21 22:47 ` Christian Böhme
2007-05-21 23:15 ` Benjamin Herrenschmidt
2007-05-21 23:44 ` Christian Böhme [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=46522EF1.6030804@gmx.de \
--to=monodhs@gmx.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).