From: Tom Rini <trini@konsulko.com>
To: Josua Mayer <josua@solid-run.com>
Cc: u-boot@lists.denx.de, yazan.shhady@solid-run.com,
Stefano Babic <sbabic@denx.de>,
Fabio Estevam <festevam@gmail.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
Baruch Siach <baruch@tkos.co.il>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>
Subject: Re: [PATCH] mx6cuboxi: fix ethernet after synchronise device-tree
Date: Thu, 28 Jul 2022 07:41:54 -0400 [thread overview]
Message-ID: <20220728114154.GG1146598@bill-the-cat> (raw)
In-Reply-To: <20220728070540.28554-1-josua@solid-run.com>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On Thu, Jul 28, 2022 at 10:05:40AM +0300, Josua Mayer wrote:
> The i.MX6 Cubox-i and HummingBoards can have different PHYs at varying
> addresses. U-Boot needs to auto-detect which phy is actually present,
> and at which address it is responding.
>
> Auto-detection from multiple phy nodes specified in device-tree does not
> currently work correct. As a work-around merge all three possible phys
> into one node with the special address 0xffffffff which indicates to the
> generic phy driver to probe all addresses.
> Also fixup this fake address before booting Linux, *if* booting with
> U-Boot's internal dtb.
>
> Signed-off-by: Josua Mayer <josua@solid-run.com>
> Fixes: d0399a46e7cd
Tested-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-07-28 11:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220728070540.28554-1-josua@solid-run.com>
2022-07-28 7:08 ` [PATCH] mx6cuboxi: fix ethernet after synchronise device-tree Josua Mayer
2022-07-28 11:11 ` Fabio Estevam
2022-07-28 11:16 ` Tom Rini
2024-03-27 12:06 ` Josua Mayer
2024-03-27 12:17 ` Christian Gmeiner
2024-03-27 13:20 ` Josua Mayer
2024-03-27 15:55 ` Christian Gmeiner
2024-03-27 16:54 ` Josua Mayer
2024-03-27 19:29 ` Fabio Estevam
2024-03-27 21:04 ` Fabio Estevam
2024-03-27 23:17 ` Fabio Estevam
2024-03-28 7:08 ` Christian Gmeiner
2022-07-28 11:41 ` Tom Rini [this message]
2022-07-28 11:51 ` Fabio Estevam
2022-07-28 12:01 ` Tom Rini
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=20220728114154.GG1146598@bill-the-cat \
--to=trini@konsulko.com \
--cc=baruch@tkos.co.il \
--cc=festevam@gmail.com \
--cc=josua@solid-run.com \
--cc=marcel.ziswiler@toradex.com \
--cc=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=yazan.shhady@solid-run.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