From: James Kosin <jkosin@intcomgrp.com>
To: unlisted-recipients:; (no To-header on input)
Cc: <netdev@vger.kernel.org>
Subject: Re: EG20T and Micrel KSZ9021 Gigabit Ethernet
Date: Tue, 16 Oct 2012 13:21:59 -0400 [thread overview]
Message-ID: <507D97B7.5090002@intcomgrp.com> (raw)
In-Reply-To: <507D95A2.9090206@intcomgrp.com>
I have to remember to use plain text only....
On 10/16/2012 1:13 PM, James Kosin wrote:
> Hmmm... interesting turn of events.
>
> The problem seems to be in 10 speed support. I hooked the Ethernet
> PHY to a100TX port and don't get these errors.
>
> James
>
> On 10/5/2012 5:09 PM, Francois Romieu wrote:
>> (please don't top post)
>>
>> James Kosin <jkosin@intcomgrp.com> :
>>> The driver is always reporting:
>>> [...] pch_gbe: Transfer Carrier Sense Error
>> You should send more information. Say dmesg, link stats (ip link),
>> ethtool information, stats and offload settings.
>>
>> We have a small Micrel ksz9021 phy driver that the pch_gbe driver does
>> not use and the latter pokes into some phy specific register (0x10) that
>> the Micrel document does not include in its list of vendor registers...
>>
>> Does your motherboard vendor offer some linux driver ?
>>
>> /note to myself: pch_gbe should use standard mii.h registers instead
>> of defining its own redundant set of registers.
>>
>> --
>> Ueimor
>>
>
next prev parent reply other threads:[~2012-10-16 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 19:10 EG20T and Micrel KSZ9021 Gigabit Ethernet James Kosin
2012-10-05 19:53 ` Francois Romieu
[not found] ` <506F41FC.7080108@intcomgrp.com>
2012-10-05 21:09 ` Francois Romieu
2012-10-08 13:23 ` James Kosin
[not found] ` <507D95A2.9090206@intcomgrp.com>
2012-10-16 17:21 ` James Kosin [this message]
2012-10-25 20:30 ` James Kosin
2012-10-25 20:49 ` Veaceslav Falico
2012-10-25 20:52 ` James Kosin
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=507D97B7.5090002@intcomgrp.com \
--to=jkosin@intcomgrp.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.