From: David Riley <oscar@the-rileys.net>
To: tom_gall@vnet.ibm.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PCI Buses
Date: Tue, 15 Aug 2000 20:19:25 -0400 [thread overview]
Message-ID: <3999DE0C.4EF5762F@the-rileys.net> (raw)
In-Reply-To: 3999CF3E.561EB9C8@vnet.ibm.com
tom_gall@vnet.ibm.com wrote:
> It's definately interesting to hear that AGP is really just another PCI... or at
> least treated that way. Being PCI/AGP stupid I appreciate the info... if it's
> just another "PCI" of sorts, doesn't that have performance implications or is
> that addressed really by the hardware implementation as apposed to the Linux
> side of things?
It really is just another PCI (there is a 66 MHz PCI specification, and AGP uses
it), though there are improvements made (for example, sidebanding, which gives us
the 2x and 4x modes). Additionally, it's adapted on the Intel side of things for
"write combining" (if anyone comes up with an exact definition of how that works,
please let me know). I'm not sure what you mean by performance implications, but
PCI isn't a horrible bus to start with...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-16 0:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 18:46 PCI Buses tom_gall
2000-08-15 19:14 ` Ani Joshi
2000-08-15 19:39 ` Michel Lanners
2000-08-15 23:16 ` tom_gall
2000-08-16 0:19 ` David Riley [this message]
2000-08-16 14:45 ` Geert Uytterhoeven
2000-08-17 20:37 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2000-08-15 18:52 jlquinn
2000-08-15 19:13 ` David Riley
2000-08-16 8:51 ` Gabriel Paubert
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=3999DE0C.4EF5762F@the-rileys.net \
--to=oscar@the-rileys.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tom_gall@vnet.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).