All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Kosin <jkosin@intcomgrp.com>
To: Veaceslav Falico <darkmag@gmail.com>
Cc: Francois Romieu <romieu@fr.zoreil.com>, <netdev@vger.kernel.org>
Subject: Re: EG20T and Micrel KSZ9021 Gigabit Ethernet
Date: Thu, 25 Oct 2012 16:52:26 -0400	[thread overview]
Message-ID: <5089A68A.5000206@intcomgrp.com> (raw)
In-Reply-To: <CAE3RKNmEWk+=OOWzpA+wEmSGRdbKeCpn6PS+dNTTridAPEXbuw@mail.gmail.com>


On 10/25/2012 4:49 PM, Veaceslav Falico wrote:
> On Thu, Oct 25, 2012 at 10:30 PM, James Kosin <jkosin@intcomgrp.com> wrote:
>> 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
>>>>
>> Ueimor & All,
>>
>> The "Transfer Carrier Sense Error" seems to have been hardware related.
>> I replaced with a 10/100Mbps device and the interface is working
>> correctly now.  My hardware engineer is going to look at the 10Mbps HUB
>> later to find out what is going on with that piece of equipment; so, we
>> know what to do when we have future issues.
> Did you run pch_gbe on 1gbps? It might be also speed related, in my tests
> the driver gave CRC errors only on high loads.
>
>> James
I'm not planning on using 1Gbps ... we plan on limiting this by only
advertising and attaching the connections needed for 10/100Mbps support.

      reply	other threads:[~2012-10-25 20:52 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
2012-10-25 20:30         ` James Kosin
2012-10-25 20:49           ` Veaceslav Falico
2012-10-25 20:52             ` James Kosin [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=5089A68A.5000206@intcomgrp.com \
    --to=jkosin@intcomgrp.com \
    --cc=darkmag@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.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 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.