From: Christopher Leech <christopher.leech@intel.com>
To: aby_sinha@yahoo.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Intel Plumas Chipset and 100Mhz PCI cards
Date: 25 Jul 2002 23:10:10 -0700 [thread overview]
Message-ID: <1027663813.13982.17.camel@orthanc> (raw)
In-Reply-To: <BD9B60A108C4D511AAA10002A50708F22C1562@orsmsx118.jf.intel.com>
Not only is the bus running at 66 MHz, it's using the PCI protocol not
PCI-X. Is there a card in the other PCI-X capable slot? I think they
are on the same bus, so installing a PCI card there would bring both
slots down to this speed. You should check the output of lspci -v and
make sure all the devices on bus 2 have the PCI-X capability.
- Chris Leech
> PCI_Bus_Type PCI
> PCI_Bus_Speed 66MHz
> PCI_Bus_Width 64-bit
next parent reply other threads:[~2002-07-26 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BD9B60A108C4D511AAA10002A50708F22C1562@orsmsx118.jf.intel.com>
2002-07-26 6:10 ` Christopher Leech [this message]
2002-07-26 17:07 Intel Plumas Chipset and 100Mhz PCI cards abhishek Sinha
-- strict thread matches above, loose matches on Subject: below --
2002-07-26 3:14 abhishek Sinha
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=1027663813.13982.17.camel@orthanc \
--to=christopher.leech@intel.com \
--cc=aby_sinha@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/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