From: Tom Rini <trini@konsulko.com>
To: E Shattow <e@freeshell.de>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Jerome Forissier <jerome.forissier@linaro.org>
Subject: Re: LwIP and multiple network interfaces
Date: Thu, 2 Jan 2025 16:47:24 -0600 [thread overview]
Message-ID: <20250102224724.GS3476@bill-the-cat> (raw)
In-Reply-To: <de7bf6b3-fd45-4c8f-a492-bd41db2aa904@freeshell.de>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On Thu, Jan 02, 2025 at 02:26:06PM -0800, E Shattow wrote:
> Problem: 'dhcp' must be ran twice when the network cable is plugged into a
> port other than the first network port.
>
> Network cable plugged into bottom (first) Ethernet port:
> 1. Power on
> 2. StarFive # dhcp
>
> ethernet@16030000 Waiting for PHY auto negotiation to complete....... done
> DHCP client bound to address 192.168.2.51 (3678 ms)
>
>
> Network cable plugged into top (second) Ethernet port:
> 1. Power on
> 2. StarFive # dhcp
> ethernet@16030000 Waiting for PHY auto negotiation to complete.........
> TIMEOUT !
> phy_startup() failed: -110
> FAILED: -110
> ethernet@16040000 Waiting for PHY auto negotiation to complete...... done
> ethernet@16030000 Waiting for PHY auto negotiation to complete.........
> TIMEOUT !
> phy_startup() failed: -110
> FAILED: -110
> Could not start ethernet@16030000
> 3. StarFive # dhcp
> DHCP client bound to address 192.168.2.77 (31 ms)
What happens when you set ethact to 1 first?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-01-02 22:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 22:26 LwIP and multiple network interfaces E Shattow
2025-01-02 22:47 ` Tom Rini [this message]
2025-01-03 1:34 ` E Shattow
2025-01-03 1:40 ` Tom Rini
2025-01-03 1:52 ` E Shattow
2025-01-03 10:03 ` Jerome Forissier
2025-01-03 17:58 ` E Shattow
2025-01-04 3:05 ` E Shattow
2025-01-06 15:43 ` Jerome Forissier
2025-01-06 19:09 ` E Shattow
2025-01-30 10:23 ` Jerome Forissier
2025-01-31 9:27 ` E Shattow
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=20250102224724.GS3476@bill-the-cat \
--to=trini@konsulko.com \
--cc=e@freeshell.de \
--cc=jerome.forissier@linaro.org \
--cc=u-boot@lists.denx.de \
/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.