From owner-freebsd-arm@FreeBSD.ORG Fri Dec 14 19:08:30 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 4BE2116A5F1 for ; Fri, 14 Dec 2007 19:08:30 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from smtp.ht-systems.ru (mr0.ht-systems.ru [78.110.50.55]) by mx1.freebsd.org (Postfix) with ESMTP id BB1B513C468 for ; Fri, 14 Dec 2007 19:08:29 +0000 (UTC) (envelope-from stas@ht-systems.ru) Received: from [78.110.49.49] (helo=quasar.ht-systems.ru) by smtp.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1J3Fta-0000Ym-Vn; Fri, 14 Dec 2007 22:08:27 +0300 Received: by quasar.ht-systems.ru (Postfix, from userid 1024) id DDF9C7D2803; Fri, 14 Dec 2007 22:08:25 +0300 (MSK) Date: Fri, 14 Dec 2007 22:08:25 +0300 From: Stanislav Sedov To: Rafal Jaworowski Message-ID: <20071214190825.GG17356@dracon.ht-systems.ru> 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> <47629E53.30404@semihalf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47629E53.30404@semihalf.com> Organization: The FreeBSD Project X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI X-Mailer: carrier-pigeon X-Operating-System: FreeBSD quasar.ht-systems.ru 7.0-BETA2 FreeBSD 7.0-BETA2 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 19:08:30 -0000 On Fri, Dec 14, 2007 at 04:16:35PM +0100 Rafal Jaworowski mentioned: > > 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... > Well, I downloaded the entire kernel via tftp, so the controller was probably configured correctly. Probably, u-boot resets it after transfer (have not checked this yet). The idea of bd_t support looks promising anyway, especially if we'll continue our expansion in the embedded world (almost all powerpc and arm embedded boards are moving toward using u-boot exclusively). This way we'll get a good cooperation with another projects. I'll look into this after I get ate0 and usb working. BTW, what is the status of usb for now? Should it work? I'm receiving a 'device problem (IOERROR), disabling port 1' message if device attached. Is it known problem, or something is misconfigured in my board? Thanks for information! -- Stanislav Sedov ST4096-RIPE