lkml.org 
[lkml]   [2007]   [Mar]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: 1000xf bus problem
Date
From

That would completely and uttly suck if it were the case.
So in theory, the card should be talking at full speed, but since the
bridge is 66 then it would be the bottleneck right?

There are 3 pci busses in the server I am working on, so I know there is
at least _a_ bridge there.....


-----Original Message-----
From: Kok, Auke [mailto:auke-jan.h.kok@intel.com]
Sent: Sunday, March 18, 2007 10:40 PM
To: Chandler, Greg
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

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-03-19 04:51    [W:0.058 / U:1.544 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site