Date: Wed, 20 Sep 2023 22:02:55 +0200 From: "Patrick M. Hausen" <pmh@hausen.com> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org Subject: Re: Getting a stable MAC address for a RPI CM3+ with ue0 interface Message-ID: <9D4027A9-1D1A-44EC-BAA7-8E439CD72E8B@hausen.com> In-Reply-To: <B50A4409-84C0-405D-8099-43692243AE52@hausen.com> References: <3C1032FF-B914-4863-8A03-759A8B4BE216@hausen.com> <77E70D30-8E7D-42DC-A041-3A783E1C6908@yahoo.com> <5205C76E-BAB4-4AB7-8A03-1E8A2D4353BB@hausen.com> <B50A4409-84C0-405D-8099-43692243AE52@hausen.com>
next in thread | previous in thread | raw e-mail | index | archive | help
And some more answers ... On the Raspberry Pi forums, I found a link to this document: = https://pip.raspberrypi.com/categories/685/documents/RP-003474-WP/RP-00347= 4-WP-1.pdf Important part: > On devices prior to the Raspberry Pi 4x the MAC address is generated = from the Raspberry Pi serial number. > For example, if your Raspberry Pi serial number is 58d2ec5c, the MAC = address will be generated from the > bottom six nibbles, combined with the Raspberry Pi Foundation = Organizationally Unique Identifier (OUI), > which is b8:27:eb, so the final MAC address would be = b8:27:eb:d2:ec:5c. >=20 > This address is generated on startup by the firmware, and passed on to = the Linux kernel for use by the Ethernet driver. So it seems like it would be on the FreeBSD kernel to read this = information and pass it down to whatever driver is managing the actual device. I am suprised I am the first to notice this? Am I? Kind regards, Patrick=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D4027A9-1D1A-44EC-BAA7-8E439CD72E8B>