From: "David S. Miller" <davem@redhat.com>
To: groudier@free.fr
Cc: hozer@drgw.net, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk, rmk@arm.linux.org.uk,
dan@embeddededge.com, mattl@mvista.com
Subject: Re: pci_alloc_consistent from interrupt == BAD
Date: Fri, 18 Jan 2002 13:13:09 -0800 (PST) [thread overview]
Message-ID: <20020118.131309.45713681.davem@redhat.com> (raw)
In-Reply-To: <20020118215449.K2042-100000@gerard>
In-Reply-To: <20020118.123837.21900127.davem@redhat.com> <20020118215449.K2042-100000@gerard>
From: Gérard Roudier <groudier@free.fr>
Date: Fri, 18 Jan 2002 22:07:09 +0100 (CET)
Under Linux, PCI consistent allocation support is a requirement. Let me
cross fingers for this to stay as it is. :)
It is my intention to keep it like this. I have shown 3 or 4 ports,
after I've been told "we cannot do consistent memory on our platform",
that in fact they could :-)
For this reason, someone will have to do the equivalent of parting the
seas to convince me to change things :-)
next prev parent reply other threads:[~2002-01-18 21:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 19:02 pci_alloc_consistent from interrupt == BAD Troy Benjegerdes
2002-01-18 19:22 ` Dan Malek
2002-01-18 20:32 ` David S. Miller
2002-01-18 21:29 ` Russell King
2002-01-18 21:33 ` David S. Miller
2002-01-18 21:42 ` Russell King
2002-01-18 21:46 ` Dan Malek
2002-01-18 21:55 ` Russell King
2002-01-18 22:13 ` Dan Malek
2002-01-18 21:43 ` Dan Malek
2002-01-18 20:50 ` Gérard Roudier
[not found] ` <mailman.1011386221.24072.linux-kernel2news@redhat.com>
2002-01-21 23:52 ` Pete Zaitcev
2002-01-22 0:08 ` David S. Miller
2002-01-22 0:20 ` Pete Zaitcev
2002-01-18 20:21 ` Gérard Roudier
2002-01-18 20:38 ` David S. Miller
2002-01-18 21:07 ` Gérard Roudier
2002-01-18 21:13 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-19 17:21 David Brownell
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=20020118.131309.45713681.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dan@embeddededge.com \
--cc=groudier@free.fr \
--cc=hozer@drgw.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mattl@mvista.com \
--cc=rmk@arm.linux.org.uk \
/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