public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Torsten Duwe <duwe@lst.de>
To: yanhong wang <yanhong.wang@starfivetech.com>
Cc: <u-boot@lists.denx.de>, Rick Chen <rick@andestech.com>,
	Leo <ycliang@andestech.com>,
	Joe Hershberger <joe.hershberger@ni.com>,
	"Ramon Fried" <rfried.dev@gmail.com>
Subject: Re: [PATCH v1 0/5] Add Ethernet driver for StarFive JH7110 SoC
Date: Mon, 27 Mar 2023 10:09:06 +0200	[thread overview]
Message-ID: <20230327100906.7be78180@blackhole.lan> (raw)
In-Reply-To: <988e7812-ae5c-6f3e-0645-fe1c59973309@starfivetech.com>

On Mon, 27 Mar 2023 10:22:37 +0800
yanhong wang <yanhong.wang@starfivetech.com> wrote:

> On 2023/3/24 20:53, Torsten Duwe wrote:

> > What's missing to read the correct MACs from the EEPROM?
> 
> The minimum system of u-boot supporting JH7110 does not contain EEPROM
[...]

Thanks for the info!

	Torsten


      reply	other threads:[~2023-03-27  8:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  1:05 [PATCH v1 0/5] Add Ethernet driver for StarFive JH7110 SoC Yanhong Wang
2023-03-17  1:05 ` [PATCH v1 1/5] net: phy: Add driver for Motorcomm yt8531 gigabit ethernet phy Yanhong Wang
2023-03-18 20:20   ` Simon Glass
2023-03-20  2:53     ` yanhong wang
2023-03-24  8:21     ` yanhong wang
2023-03-17  1:05 ` [PATCH v1 2/5] net: dwc_eth_qos: Add StarFive ethernet driver glue layer Yanhong Wang
2023-03-18 20:20   ` Simon Glass
2023-03-20  3:30     ` yanhong wang
2023-03-17  1:05 ` [PATCH v1 3/5] riscv: dts: jh7110: Add ethernet device tree nodes Yanhong Wang
2023-03-17  1:05 ` [PATCH v1 4/5] riscv: dts: starfive: Add phy clock delay configuration for StarFive VisionFive2 board Yanhong Wang
2023-03-17  1:05 ` [PATCH v1 5/5] configs: starfive: Enable ethernet configuration for StarFive VisionFive 2 Yanhong Wang
2023-03-24 12:53 ` [PATCH v1 0/5] Add Ethernet driver for StarFive JH7110 SoC Torsten Duwe
2023-03-27  2:22   ` yanhong wang
2023-03-27  8:09     ` Torsten Duwe [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=20230327100906.7be78180@blackhole.lan \
    --to=duwe@lst.de \
    --cc=joe.hershberger@ni.com \
    --cc=rfried.dev@gmail.com \
    --cc=rick@andestech.com \
    --cc=u-boot@lists.denx.de \
    --cc=yanhong.wang@starfivetech.com \
    --cc=ycliang@andestech.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