Hi Albert,
On 5 May 2015 at 01:17, Albert ARIBAUD albert.aribaud@3adev.fr wrote:
Bonjour Simon,
Le Mon, 4 May 2015 15:37:22 -0600, Simon Glass sjg@chromium.org a écrit :
On 4 May 2015 at 13:55, Joe Hershberger joe.hershberger@ni.com wrote:
We really don't want boards defining fixed MAC addresses in their config so we just remove the option to set it in a fixed way. If you must have a MAC address that was not provisioned, then use the random MAC address functionality.
Signed-off-by: Joe Hershberger joe.hershberger@ni.com
Reviewed-by: Simon Glass sjg@chromium.org
As much as I support the idea that one should not hard-code MAC addresses, I also support the idea that changes should not break previous behavior.
And regarding the WORK board which I submitted, its configuration header file had this address encoded in the in-house U-Boot which the customer was using before; removing this address might lead to the customer provisioning scripts failing.
Shouldn't this be done with either MAC address or CONFIG_BOOTP_VCI_STRING or similar?
Regards, Simon