public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: "Richard B. Johnson" <linux-os@analogic.com>
Cc: christos gentsis <christos_gentsis@yahoo.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI-X support
Date: Fri, 1 Jul 2005 20:40:09 +0200	[thread overview]
Message-ID: <20050701184009.GA2034@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0507011357290.5350@chaos.analogic.com>

On Fri, Jul 01, 2005 at 02:00:15PM -0400, Richard B. Johnson wrote:
> On Fri, 1 Jul 2005, christos gentsis wrote:
> 
> >Hello
> >
> >I have a friend that his Msc project is related with the development
> >over a PCI-X card. the problem is that he do not know if the Linux
> >kernel support the PCI-X bus. i try to find something related with the
> >PCI-X in the kernel source but i didn't found any file or folder with a
> >relevant name... Does any one know if PCI-X bus supported from Linux and
> >if no how can he patch the kernel to support it...?
> >
> >Thanks
> >Chris
> 
> Sure PCI-X is just PCI/66 with 64-bits. It's just like PCI/66
> from a software standpoint.
 
Not really. 64-bit 66MHz PCI is normal PCI, within the PCI 2.1 spec.
Common PCI-X is running at 133MHz, 64-bit wide.

You're correct, though, that from the software standpoint it's not much
different and Linux supports it natively. I'm not sure about MSI-X
extensions, though.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  parent reply	other threads:[~2005-07-01 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 17:48 PCI-X support christos gentsis
2005-07-01 18:00 ` Richard B. Johnson
2005-07-01 18:05   ` christos gentsis
2005-07-01 19:02     ` Richard B. Johnson
2005-07-01 19:09       ` Vojtech Pavlik
2005-07-01 19:25         ` Richard B. Johnson
2005-07-01 22:20           ` Krzysztof Halasa
2005-07-01 18:40   ` Vojtech Pavlik [this message]
2005-07-01 19:09 ` Greg KH

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=20050701184009.GA2034@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=christos_gentsis@yahoo.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.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