linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Riley <oscar@the-rileys.net>
To: jlquinn@us.ibm.com
Cc: tom_gall@vnet.ibm.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: PCI Buses
Date: Tue, 15 Aug 2000 15:13:59 -0400	[thread overview]
Message-ID: <39999677.4790E775@the-rileys.net> (raw)
In-Reply-To: OF2006BA97.98D63D31-ON8525693C.0067A5CE@pok.ibm.com


jlquinn@us.ibm.com wrote:

> I thought the 9500/9600 had two PCI buses with 3 slots each?
>
> Jerry Quinn
>

Well, the 9500/9600 have 6 PCI slots, though it's anyone's guess as to how
many are on each bus.  However, the Blue G3's and all G4's as well as the
iBook and any other computer with AGP (including the "fake AGP" fast PCI slot
on the blue G3's) have two PCI busses, since AGP is only a fast PCI bus (with
a few enhancements, but as far as Linux is concerned, it's PCI).  AGP slots
will run compatible PCI cards at 66MHz (though there are certain keys which
prevent insertion unless the card is compatible).  A notable example is
3Dfx's Voodoo2 1000 card (and several other brands) which allow a 66 MHz bus.

On a side note, does anyone know if Linux properly supports the 64-bit PCI
slots in the Blue G3's and G4's?  The only cards I know of that use them are
several SCSI cards and TotalImpact cards.

Thanks,
    David


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-08-15 19:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-15 18:52 PCI Buses jlquinn
2000-08-15 19:13 ` David Riley [this message]
2000-08-16  8:51   ` Gabriel Paubert
  -- strict thread matches above, loose matches on Subject: below --
2000-08-15 18:46 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
2000-08-16 14:45       ` Geert Uytterhoeven
2000-08-17 20:37     ` Matt Porter

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=39999677.4790E775@the-rileys.net \
    --to=oscar@the-rileys.net \
    --cc=jlquinn@us.ibm.com \
    --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).