From owner-freebsd-arm@freebsd.org Sat Nov 26 05:19:00 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B101FC5576A for ; Sat, 26 Nov 2016 05:19:00 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93C32FEA for ; Sat, 26 Nov 2016 05:19:00 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: db338a78-b397-11e6-94b7-cbe6054a74b1 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id db338a78-b397-11e6-94b7-cbe6054a74b1; Sat, 26 Nov 2016 05:19:08 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id uAQ5IvMp010019; Fri, 25 Nov 2016 22:18:57 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1480137537.1889.97.camel@freebsd.org> Subject: Re: How to change MAC address on RPI-B? From: Ian Lepore To: diffusae , freebsd-arm@freebsd.org Date: Fri, 25 Nov 2016 22:18:57 -0700 In-Reply-To: <177ae37f-db52-c7ee-77fa-d9bc7d61b4ee@t-online.de> 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> X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2016 05:19:00 -0000 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. -- Ian