From owner-freebsd-arm@FreeBSD.ORG  Tue Nov  2 21:43:25 2010
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 595C4106566B
	for <freebsd-arm@freebsd.org>; Tue,  2 Nov 2010 21:43:25 +0000 (UTC)
	(envelope-from freebsd-arm@dino.sk)
Received: from loki.netlab.sk (ns3.netlab.sk [84.245.65.11])
	by mx1.freebsd.org (Postfix) with ESMTP id C12108FC12
	for <freebsd-arm@freebsd.org>; Tue,  2 Nov 2010 21:43:24 +0000 (UTC)
Received: from door.dino.sk (fw1.dino.sk [84.245.95.252])
	(AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA)
	by loki.netlab.sk with esmtp; Tue, 02 Nov 2010 22:43:35 +0100
	id 00033C0F.4CD08607.0000A6C9
From: Milan Obuch <freebsd-arm@dino.sk>
To: Rafal Jaworowski <raj@semihalf.com>
Date: Tue, 2 Nov 2010 22:43:31 +0100
User-Agent: KMail/1.13.5 (FreeBSD/8.1-STABLE; KDE/4.5.2; i386; ; )
References: <201010202309.40148.freebsd-arm@dino.sk>
	<201010272259.36319.freebsd-arm@dino.sk>
	<DEF142CA-E6D8-4521-8DB4-D9AB604E919C@semihalf.com>
In-Reply-To: <DEF142CA-E6D8-4521-8DB4-D9AB604E919C@semihalf.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201011022243.33116.freebsd-arm@dino.sk>
Cc: freebsd-arm@freebsd.org
Subject: Re: Guruplug Server Plus working to some extent... [mge1 problem
	SOLVED]
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
	<mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
	<mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 21:43:25 -0000

On Saturday 30 October 2010 15:02:43 Rafal Jaworowski wrote:
> On 2010-10-27, at 22:59, Milan Obuch wrote:
> > On Wednesday 27 October 2010 18:44:23 Rafal Jaworowski wrote:

[snip]

> > 
> > One issue still remains - mge1 has no unique ether address, all-zero is
> > set upon reboot unless explicitly set in dts. This is small issue for
> > me, need not be resolved urgently.
> 
> This issue is not easily resolved in general. U-Boot would only initialize
> MAC address in registers of an Ethernet controller, which was used at
> least once. If an Ethernet controller unit is not used at the U-Boot stage
> its MAC address registers remain uninitialized. Now, in our case the OS
> can only learn about MAC address either from DT or (in case there are all
> 0's) fall back to whatever was set by the firmware.
> 

For now I found simple and effective solution (maybe not nice, but that's just 
matter of taste, anyway). I modified U-Boot's environment, so now there are
following variables set:

bootcmd=setenv ethact egiga1; ${x_bootcmd_ethernet}; setenv ethact egiga0; 
${x_bootcmd_ethernet}; tftpboot kernel.bin; go 800000

x_bootcmd_ethernet=ping 192.168.16.1

ipaddr=192.168.16.5/24

serverip=192.168.16.133

This is not permanent and nice solution, but sufficient for now. This way, 
firmware sets both interfaces' ether address.

Milan