On Thu, Jan 22, 2009 at 2:09 PM, Jonathan Fournier
jonathan.fourn...@gmail.com wrote:
On Wed, Jan 21, 2009 at 6:10 PM, Brandeburg, Jesse
jesse.brandeb...@intel.com wrote:
Jonathan Fournier wrote:
so what is the actual connection type on your ethernet, is it a
directly connected fiber port?
-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Question regarding e1000 link status
From e1000_hw.c: e1000_set_media_type()
...
default:
status = er32(STATUS);
if (status E1000_STATUS_TBIMODE) {
hw-media_type = e1000_media_type_fiber
Jonathan Fournier wrote:
so what is the actual connection type on your ethernet, is it a
directly connected fiber port? Is it a serdes blade? forgive me
I've never tested one of the ATCA platforms.
I just found out more documentation for that platform, since most ATCA
switch are
On Wed, Jan 21, 2009 at 6:10 PM, Brandeburg, Jesse
jesse.brandeb...@intel.com wrote:
Jonathan Fournier wrote:
so what is the actual connection type on your ethernet, is it a
directly connected fiber port? Is it a serdes blade? forgive me
I've never tested one of the ATCA platforms.
I just
Hi,
I've found more information to share about my problem.
I'm debugging on the ATCA-7101, I initially thought from the datasheet
that it had a 82546EB, but by printing the pdev-device it has a value
of 0x1079 = E1000_DEV_ID_82546GB_COPPER.
Since in the patch I've previously provided, I was
From e1000_hw.c: e1000_set_media_type()
...
default:
status = er32(STATUS);
if (status E1000_STATUS_TBIMODE) {
hw-media_type = e1000_media_type_fiber;
/* tbi_compatibility not valid on fiber */
hw-tbi_compatibility_en
Hi,
I'm currently doing some cleanup in *very* old patches I had against
2.6.10. (patch inlined below)
At that time a patch was provided to me to fix link status problems on
two ATCA boards (Mot ATCA-7101 and Mot ATCA-6101). If I'm correct the
7101 is using a variant of the 82546EB, and the 6101
