netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Frederiks <frederiks@speechpro.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Linux r8169 crew <netdev@vger.kernel.org>
Subject: Re: Realtek RTL8102E registers
Date: Wed, 06 Nov 2013 14:13:14 +0400	[thread overview]
Message-ID: <527A163A.9010409@speechpro.com> (raw)
In-Reply-To: <20131029214059.GA26496@electric-eye.fr.zoreil.com>

Hello Francois,

I found solution for the issue that I described earlier: one has to set
correct MAC-address before bringing up the interface.

On my board RTL8102E works without EEPROM, so initial MAC-address value
is unpredictable. In many cases this value has multicast bit set to 1.
This fact breaks driver and (or) TCP stack operation:
* r8169 reports that link is down
* r8101 reports that link is OK, but Linux TCP stack ignores packets
with multicast destination MAC

Hope this info would be useful. BTW, I suppose that driver could have
some kind of protection against such situations.

On 30.10.2013 01:40, Francois Romieu wrote:
> Ivan Frederiks <frederiks@speechpro.com> :
> [...]
>> Maybe you have access to RTL8102E register description ?
> 
> No.
> 
> Realtek's hardware documentation policy isn't exactly opened. Your hardware
> vendor may help.
> 
> [...]
>> Issue description:
> [snip]
> 
> kernel version and r81xx XID value as it should appear in dmesg would
> be welcome.
> 

--
Best regards,

Ivan Frederiks
Embedded developer
Speech Technology Center

Phone: +7-812-331-0665, ext. 6123, 6942
Fax: +7-812-327-9297

      reply	other threads:[~2013-11-06 10:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 15:05 Realtek RTL8102E registers Ivan Frederiks
2013-10-29 21:40 ` Francois Romieu
2013-11-06 10:13   ` Ivan Frederiks [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=527A163A.9010409@speechpro.com \
    --to=frederiks@speechpro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).