linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Aymeric <mulx@aplu.fr>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org
Subject: Re: Meson8b network not stable at gigabit
Date: Sun, 16 Jun 2019 20:57:46 +0200	[thread overview]
Message-ID: <22a14736-d363-f5a8-fdb3-fec5400cb6a8@aplu.fr> (raw)
In-Reply-To: <CAFBinCDJ0oAhrficayP0aMWrUsasU-NT6RkGH3x1BLw8U3h6pA@mail.gmail.com>

Hello Martin,

Le 16/06/2019 à 18:30, Martin Blumenstingl a écrit :
> On Sun, Jun 16, 2019 at 6:05 PM Aymeric <mulx@aplu.fr> wrote:
> [...]
>> The result from /proc/interrupts above are when I'm connected to my
>> operator box, from the d-link the value doesn't change any more.
>>
>> According to the "about page" of the internet box, this is a Sagemcom
>> (Livebox 3).
>>
>> So it look like there a incompatibility between the Realtek RTL8211F and
>> the "Sagemcom" but not with a "stupid" d-link switch….
> can you try to disable EEE (energy efficient Ethernet) for Gbit links?
> you need to rebuild the .dtb (typically built together with the
> kernel) for that:
> - open arch/arm/boot/dts/meson8b-odroidc1.dts
> - go to the "eth_phy" node (for example: [0])
> - below the "reg = <0>;" line add: eee-broken-1000t;
> - rebuild the kernel to get an updated .dtb
> - boot the kernel with that .dtb

Test done on 5.2.0-rc4, that didn't change anything (I've double
checked, this is the new .dtb I'm using).

-- 
Aymeric

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2019-06-16 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 22:22 Meson8b network not stable at gigabit Aymeric
2019-06-15 11:34 ` Martin Blumenstingl
2019-06-16 16:05   ` Aymeric
2019-06-16 16:30     ` Martin Blumenstingl
2019-06-16 18:57       ` Aymeric [this message]
2019-06-17 19:36         ` Martin Blumenstingl
2019-06-19  8:20           ` Aymeric

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=22a14736-d363-f5a8-fdb3-fec5400cb6a8@aplu.fr \
    --to=mulx@aplu.fr \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.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).