From: Alexander Dahl <ada@thorsis.com>
To: Jon Ringle <jon@ringle.org>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] ethernet on SAMA5D2-SOM1-EK1
Date: Fri, 19 Mar 2021 14:17:57 +0100 (CET) [thread overview]
Message-ID: <1062235164.11566.1616159878053@seven.thorsis.com> (raw)
In-Reply-To: <CAMwGMjyA6wVZGYq-BYa28gLOZAdSauABiniOouqLzqx3ynpy+g@mail.gmail.com>
Hei hei,
> Jon Ringle <jon@ringle.org> hat am 17.03.2021 17:34 geschrieben:
> On Wed, Mar 17, 2021 at 10:30 AM Alexander Dahl <ada@thorsis.com> wrote:
> > Hello,
> >
> > for testing some new mikroBUS modules I got a dusty SAMA5D2-SOM1-EK1 from our
> > shelf and build recent DistroKit master for it. Nice thing: SD card works in
> > both ports. However ethernet does not work correctly out of the box. :-/
> >
> > In barebox shell it uses a random mac address (the real one is in a small
> > eeprom on the SoM), dhcp and ping successful.
> >
> > In Linux (5.11.4) however it also uses a random mac address and furthermore
> > either the micrel ethernet phy is not found at all or the link can not be set
> > to up. Tried both nmtui and raw iproute2 command.
>
> Hey Alexander,
>
> I don't know if this will apply to you with sama5d2-som1-ek1, but we have a board that is based on sama5d2-som1 that has ksz8081rna phy, which based on the strap on options configured via pull up/down is on phy 4.
We also have boards based on that SoC, but those use a different ethernet phy. No problems with kernel v5.4 and v5.10 series.
> We are in the process of updating from linux-4.14 to linux-5.4. A problem that was noticed on update to linux-5.4 was that the Ethernet port stopped working after power on boot, but would work after a subsequent soft reboot.
> I noticed that the phy address used in arch/arm/boot/dts/at91-sama5d27_som1.dtsi didn't match the one for our board in either the linux-4.14 or linux-5.4 tree, but we never noticed a problem when we did initial bring up of our board with linux-4.14 a couple years ago. When I fixed the device tree to use the correct phy address 4 for our board. The problem went away and the Ethernet port now works properly on linux-5.4.
Nice to know. Meanwhile I digged in my old projects and managed to get a modified DistroKit with at91bootstrap 3 and u-boot running, with kernel 4.19.x and everything works just fine, including ethernet. :-)
(The hardware itself is also modified, I can not just use mainline dts, but that's not the point.)
That means to me, there are still some open working spots for barebox and/or DistroKit to fully support that board.
Greets
Alex
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2021-03-19 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 14:29 Alexander Dahl
2021-03-17 16:34 ` Jon Ringle
2021-03-19 13:17 ` Alexander Dahl [this message]
2021-03-22 18:56 ` Ahmad Fatoum
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=1062235164.11566.1616159878053@seven.thorsis.com \
--to=ada@thorsis.com \
--cc=distrokit@pengutronix.de \
--cc=jon@ringle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox