public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Greg.Chandler@wellsfargo.com
Cc: auke-jan.h.kok@intel.com, hancockr@shaw.ca,
	linux-kernel@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: 1000xf bus problem
Date: Sun, 18 Mar 2007 20:39:42 -0700	[thread overview]
Message-ID: <45FE05FE.80009@intel.com> (raw)
In-Reply-To: <E8C008223DD5F64485DFBDF6D4B7F71D0289EDC1@msgswbmnmsp25.wellsfargo.com>

Greg.Chandler@wellsfargo.com wrote:
> If you mean dmesg it says this:
> e1000: 0000:0d:02.0: e1000_probe: (PCI-X:100MHz:64-bit)  {macaddress}
> 
> That's weird... dmesg shows one thing, lspci shows another, and my data
> transfers seem to point to the lspci info...
> 
> Any idea which I should trust?


Both, the e1000 driver asks the card what it sees from it's side of the 
connection, and lspci tells you what the cpu side of it is connected to.

Since stuff like pci bridges exist, both could very well be correct!

I highly suspect that that is exactly the case.


Auke

  reply	other threads:[~2007-03-19  3:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.wDPF1lWlqGQpxbyWee64Z3t4BVM@ifi.uio.no>
2007-03-18 19:41 ` 1000xf bus problem Robert Hancock
2007-03-18 20:51   ` Kok, Auke
2007-03-19  3:03     ` Greg.Chandler
2007-03-19  3:39       ` Kok, Auke [this message]
2007-03-19  3:48         ` Greg.Chandler
2007-03-19  2:53   ` Greg.Chandler
2007-03-19  5:20     ` Robert Hancock
2007-03-19  5:31       ` Willy Tarreau
2007-03-19  5:59         ` [E1000-devel] " Robin Humble
2007-03-19  6:56           ` Willy Tarreau
2007-03-18 18:51 Greg.Chandler

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=45FE05FE.80009@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=Greg.Chandler@wellsfargo.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=hancockr@shaw.ca \
    --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