From: Dan Malek <dan@mvista.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Ralph Blach <rcblach@raleigh.ibm.com>,
paulus@samba.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: pci_dma_sync_single
Date: Fri, 19 Oct 2001 22:04:27 -0400 [thread overview]
Message-ID: <3BD0DBAB.8A7B1461@mvista.com> (raw)
In-Reply-To: 20011016140816.2321@smtp.adsl.oleane.com
Benjamin Herrenschmidt wrote:
> Well, the last time we discussed about book E,
I'm kinda planning to roll a whole new book E arch tree so we can
take advantage of their features without hacking up the traditional
PowerPC. There are a variety of options that will be necessary to
fit a wide range of embedded applications for which they are
specifically designed. While we can make Book E fit into the
traditional PowerPC tree by forcing some fixed rules, it wouldn't
be fair to their flexibility or performance options.
I've got a couple of things to finish up and would like to start
discussing this in the next couple of weeks, as more documentation
and perhaps some hardware arrives on my doorstep.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-20 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 12:03 pci_dma_sync_single Paul Mackerras
2001-10-16 13:12 ` pci_dma_sync_single Ralph Blach
2001-10-16 14:08 ` pci_dma_sync_single Benjamin Herrenschmidt
2001-10-20 2:04 ` Dan Malek [this message]
2001-10-17 1:47 ` pci_dma_sync_single Paul Mackerras
2001-10-17 14:26 ` pci_dma_sync_single Tom Rini
2001-10-17 14:34 ` pci_dma_sync_single Ralph Blach
2001-10-20 2:13 ` pci_dma_sync_single Dan Malek
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=3BD0DBAB.8A7B1461@mvista.com \
--to=dan@mvista.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=rcblach@raleigh.ibm.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).