mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nuno Silva <nuno.silva@vgertech.com>
To: root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCI-Bus
Date: Wed, 18 Aug 2004 20:41:36 +0100	[thread overview]
Message-ID: <4123B0F0.5050408@vgertech.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0408181403120.16592@chaos>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard B. Johnson wrote:

[..]

|
| 0e:03.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704
Gigabit Ethernet (rev 03)
| 	Subsystem: Advanced Micro Devices [AMD]: Unknown device 2b80
| 	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 28
| 	Memory at f1370000 (64-bit, non-prefetchable) [size=64K]
| 	Memory at f1360000 (64-bit, non-prefetchable) [size=64K]
| 	Capabilities: [40] PCI-X non-bridge device.
| 	Capabilities: [48] Power Management version 2
| 	Capabilities: [50] Vital Product Data
| 	Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
|
| The Analogic entries of:
| 	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 25
| don't look much different than the Ethernet controllers, above. Of
| course they are built into the motherboard and claim 64-bits.
|

And they are 64bit. They are connected to a PCI-X bus, not plain PCI.

About your real question, I'm sorry but I don't know :(

Reegards,
Nuno


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBI7DwOPig54MP17wRAqbSAKCjK3jqTJr7ap4XVIulXOJNrBeoIgCdEEAH
Lj5QFVoZj29BFJ1G3sA/kE0=
=ycDw
-----END PGP SIGNATURE-----

      reply	other threads:[~2004-08-18 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 18:05 PCI-Bus Richard B. Johnson
2004-08-18 19:41 ` Nuno Silva [this message]

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=4123B0F0.5050408@vgertech.com \
    --to=nuno.silva@vgertech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.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

Powered by JetHome