From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dimitar Penev <dpn@switchfin.org>
Date: Sat, 26 Nov 2011 01:40:13 +0200
Subject: [U-Boot] [PATCH] Add PR1 Appliance - ISDN PRI board
References: <014501cca57b$1d65e800$2901a8c0@dpn>
	<201111251555.58146.vapier@gentoo.org>
	<011401ccabbc$cef97cc0$2901a8c0@dpn>
	<201111251708.02707.vapier@gentoo.org>
Message-ID: <015201ccabcb$944655d0$2901a8c0@dpn>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Mike,

>>
>> Currently we keep the MAC as u-boot variable 'ethaddr' and pass it to 
>> Linux
>> using the boot comand line.
>
>right, generally all boards use the 'ethaddr' env var.  the question is how
>does that get initialized ?  many boards have dedicated storage so that 
>even
>if the env gets erased, the value can be recovered from elsewhere.  i guess
>this board doesn't have that redundancy ?


Indeed, PR1 & BR4 Appliance don't keep MAC in a dedicated storage.
It is probably not a bad idea but at the moment we just use the u-boot
environment to store our parameters.
The 'ethaddr' variable is assigned manually by the person who test the 
boards

Best Regards
Dimitar