> Am 12.02.2019 um 07:35 schrieb Anup Patel <a...@brainfault.org>: > >> On Tue, Feb 12, 2019 at 11:52 AM Alexander Graf <ag...@suse.de> wrote: >> >> >> >>>> Am 12.02.2019 um 03:57 schrieb Anup Patel <a...@brainfault.org>: >>>> >>>>> On Mon, Feb 11, 2019 at 9:07 PM Andreas Schwab <sch...@suse.de> wrote: >>>>> >>>>> On Feb 11 2019, Anup Patel <anup.pa...@wdc.com> wrote: >>>>> >>>>> This patchset adds SiFive Freedom Unleashed (FU540) support >>>>> to RISC-V U-Boot. >>>>> >>>>> The patches are based upon latest U-Boot source tree >>>>> (git://git.denx.de/u-boot.git) at commit id >>>>> dbe70c7d4e3d5c705a98d82952e05a591efd0683 >>>>> >>>>> All drivers namely: SiFive PRCI, SiFive Serial, and Cadance >>>>> MACB Ethernet work fine on actual SiFive Unleashed board and >>>>> QEMU sifive_u machine. >>>> >>>> Looks like the MACB driver cannot find the correct MAC address. That >>>> makes it rather awkward for network boot. >>>> >>>> Warning: ethernet@10090000 (eth0) using random MAC address - >>>> 0e:14:15:06:ae:e4 >>> >>> This is because we don't have place to put U-Boot environment >>> variables as of now on Unleashed board. This will be solved once >>> we have SPI driver and SPI_MMC driver for Unleased board. >>> >>> In future, we will be saving "ethaddr" environment variable on >>> SPI_MMC so U-Boot will pick MAC address at boot-time from >>> SPI_MMC. Once this is achieved, the above warning will go away. >> >> How is the MAC determined in Linux? > > In Linux, we have an "local-mac-address" DT property used by > quite a few drivers (including Cadence Ethernet driver) but it's not > uniform across Linux drivers. > > In U-Boot, another option is to change the Candence MACB driver and > set "ethaddr" environment variable based on "local-mac-address" DT > property from driver probe. Suggestions ??
That would be my quick fix suggestion, yes :). Or do it in the board file. Alex > > Regards, > Anup _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot