From owner-freebsd-arm@FreeBSD.ORG Fri Dec 14 15:16:40 2007 Return-Path: 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 23D3516A417 for ; Fri, 14 Dec 2007 15:16:40 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [83.15.139.206]) by mx1.freebsd.org (Postfix) with ESMTP id 94B0E13C4FD for ; Fri, 14 Dec 2007 15:16:39 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from localhost (unknown [127.0.0.1]) by mail.semihalf.com (Postfix) with ESMTP id 46D1A143EA; Fri, 14 Dec 2007 16:20:05 +0100 (CET) Received: from mail.semihalf.com ([127.0.0.1]) by localhost (mail.semihalf.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31509-10; Fri, 14 Dec 2007 16:20:03 +0100 (CET) Message-ID: <47629E53.30404@semihalf.com> Date: Fri, 14 Dec 2007 16:16:35 +0100 From: Rafal Jaworowski MIME-Version: 1.0 To: gary.jennejohn@freenet.de References: <20071213222654.GE17356@dracon.ht-systems.ru> <20071214090128.GM31230@cicely12.cicely.de> <20071214115226.0b2cb7e2@peedub.jennejohn.org> <20071214.062511.74732956.imp@bsdimp.com> <20071214153201.18c4c5ea@peedub.jennejohn.org> In-Reply-To: <20071214153201.18c4c5ea@peedub.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at semihalf.com Cc: freebsd-arm@freebsd.org Subject: Re: MMC cards support X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Dec 2007 15:16:40 -0000 Gary Jennejohn wrote: >>> u-boot passes this information to Linux in the board info (bd_t) >>> structure at boot time. A lot of Linux ethernet drivers read the MAC >>> out of this structure and then set it in the hardware/software. >>> >>> Very few u-boot ethernet drivers set the MAC in the hardware themselves. >>> >>> With FreeBSD this mechanism is missing. >> I did it this way because the Linux driver for the Atmel driver did it >> this way. I thought it was the de-facto way things work. Patches to >> implement this would be welcome. >> > > It is effectively the de-facto way to do things in the Linux embedded > world. Just about every embedded board used with Linux also uses > u-boot. It just won't work with FreeBSD because the infrastructure > (passing bd_t to the kernel) is missing. > > This is a weakness of which Wolfgang Denk is well aware and he'd just > love for somebody to put together the missing glue for *BSD and send it > to him. Of course, this would also require changes to the kernel > itself. > Do you know my work on U-Boot-FreeBSD interface in the custodian repo? http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-freebsd.git;a=summary Wolfgang is aware of the above and I'm going to have those merged with mainline, when now the merge window is open again after 1.3.1 has been released. We're probably getting a bit OT here, but just to clarify U-Boot networking model of operation that was mentioned: MAC address is usually programmed by a U-Boot network controller driver into relevant h/w registers upon every network access, so provided a given interface was used at least once in U-Boot (whatever net command), it should have the MAC addresss programmed correctly when running in the kernel. Otherwise it is left untouched, which happens in most of the cases with multiple integrated controllers -- usually only the first one gets ever used, others are left unconfigured... Rafal