Date: Sat, 26 Nov 2016 10:27:11 +0100 From: "John W. Kitz" <John.Kitz@xs4all.nl> To: <freebsd-arm@freebsd.org> Subject: RE: How to change MAC address on RPI-B? Message-ID: <000c01d247c7$452a4db0$cf7ee910$@Kitz@xs4all.nl> In-Reply-To: <1480137537.1889.97.camel@freebsd.org> References: <001701d245ce$e64e33f0$b2ea9bd0$@Kitz@xs4all.nl> <454137dc-30f7-cd33-6c75-0cc3045090dd@t-online.de> <002801d24755$f9017420$eb045c60$@Kitz@xs4all.nl> <177ae37f-db52-c7ee-77fa-d9bc7d61b4ee@t-online.de> <1480137537.1889.97.camel@freebsd.org>
index | next in thread | previous in thread | raw e-mail
Ian, On Sat, 2016-11-26 at 00:07 +0100, diffusae wrote: > Hi John, > > On 25.11.2016 20:56, John W. Kitz wrote: > > > > > So when doing so the locally administered MAC address is passed on > > from uEnv.txt to the O/S during boot and is then used to override > > the globally > I didn't think, that it will be passed from the U-Boot Enviroment > settings. You can set the MAC address, but the FreeBSD kernel shows > always the unique MAC address. > > > > > unique MAC address or does the O/S check both the information found > > in its configuration files and what is configured in uEnv.txt before > > configuring and activating the network interface(s)? > Which configuration files do you mean? AFAIK there is only the FDT > blob. > I guess it ignores the setting in uEnv.txt. > > > > > Makes me wonder which of the two (i.e. locally administered through > > uEnv.txt or locally administered through the O/S) takes precedence. > Only the unique MAC address and the locally administered MAC address, > will take affect. > > > > > In addition this might affect configuration decisions when one would > > want to configure a device for net booting (at least when browsing > > through what can be configured by means of uEnv.txt I believe that > > was one of the options I > > saw) through uEnv.txt? > Personally, I like u-boot. It has various options, runs on a lot of > devices and it's also nice to handle. > > Best regards, > _ I looked into this tonight, and there is some code missing in u-boot to handle passing a mac address set in the u-boot environment into the kernel via the fdt data. It would be pretty simple to fix. We need to add an ethernet0 alias pointing to the /axi/usb/hub/ethernet node to our rpi dts, and the attached patch needs to replace the current one in the u-boot-rpi port. This lets you set usbethaddr in the u-boot environment (via uEnv.txt or saved directly using saveenv), and it will get used by both u-boot and freebsd. Having gotten it this far, I don't really have time right now to get the patch committed to ports. Hopefully somebody else can help with that. JKi: I was just curious, but have no immediate use for the features discussed in this particular thread at this time. So please don't make the effort to get mentioned changes implemented because of this thread.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000c01d247c7$452a4db0$cf7ee910$>