From: "H. Peter Anvin" <hpa@zytor.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: David Acker <dacker@roinet.com>,
"Kok, Auke" <auke-jan.h.kok@intel.com>,
Lennert Buytenhek <buytenh@wantstofly.org>,
Jeff Garzik <jeff@garzik.org>,
Netdev List <netdev@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [RFT] e100 driver on ARM
Date: Thu, 26 Apr 2007 09:19:34 -0700 [thread overview]
Message-ID: <4630D116.4080202@zytor.com> (raw)
In-Reply-To: <20070417173507.GB5575@csclub.uwaterloo.ca>
Lennart Sorensen wrote:
>
> My suspicision (although it is only that) is that the PXA255 trying to
> access memory may cause interruptions in PCI bus master transfers, which
> is of course not permitted by the PCI spec (at least the way I read it).
Why wouldn't that be permitted? It, in fact, happens all the time (the
host bridge withdraws the GNT# line and raises STOP#, which does a
Termination With Data of the bus transfer.) This is a normal event and
if you can't handle it you won't work with many host bridges at all.
-hpa
next prev parent reply other threads:[~2007-04-26 16:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 10:39 [RFT] e100 driver on ARM Jeff Garzik
2006-09-04 12:31 ` Lennert Buytenhek
2007-03-28 23:04 ` Kok, Auke
2007-03-29 5:17 ` David Acker
2007-03-29 14:10 ` Lennart Sorensen
2007-04-16 15:07 ` David Acker
2007-04-17 17:35 ` Lennart Sorensen
2007-04-26 13:41 ` David Acker
2007-04-26 13:50 ` Lennert Buytenhek
2007-04-26 15:12 ` Jeff Garzik
2007-04-26 15:40 ` Kok, Auke
2007-04-26 16:09 ` Jeff Garzik
2007-04-26 16:20 ` Kok, Auke
2007-04-26 16:19 ` H. Peter Anvin [this message]
2007-04-27 19:01 ` Lennart Sorensen
2006-09-04 14:34 ` Catalin Marinas
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=4630D116.4080202@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=auke-jan.h.kok@intel.com \
--cc=buytenh@wantstofly.org \
--cc=dacker@roinet.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=rmk+lkml@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;
as well as URLs for NNTP newsgroup(s).