From owner-freebsd-arm@FreeBSD.ORG Fri Jan 23 16:15:58 2009 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 18A0410658C3; Fri, 23 Jan 2009 16:15:58 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from mx.bulinfo.net (mx.bulinfo.net [193.194.156.1]) by mx1.freebsd.org (Postfix) with ESMTP id 89B738FC14; Fri, 23 Jan 2009 16:15:57 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id EACC8CC45; Fri, 23 Jan 2009 18:15:55 +0200 (EET) Received: from mx.bulinfo.net ([127.0.0.1]) by localhost (mx.bulinfo.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13545-07; Fri, 23 Jan 2009 18:15:54 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id A7263CC32; Fri, 23 Jan 2009 18:15:54 +0200 (EET) Message-ID: <4979ED3A.2020008@bulinfo.net> Date: Fri, 23 Jan 2009 18:15:54 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 2.0.0.14 (X11/20080616) MIME-Version: 1.0 To: "M. Warner Losh" References: <20090122230647.GN50103@cicely7.cicely.de> <20090122.162633.1849591410.imp@bsdimp.com> <20090122235712.GO50103@cicely7.cicely.de> <20090122.171304.-1528842637.imp@bsdimp.com> In-Reply-To: <20090122.171304.-1528842637.imp@bsdimp.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: mav@freebsd.org, ticso@cicely7.cicely.de, freebsd-arm@freebsd.org, ticso@cicely.de Subject: Re: Mount root from SD card? 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, 23 Jan 2009 16:15:59 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 M. Warner Losh wrote: > In message: <20090122235712.GO50103@cicely7.cicely.de> > Bernd Walter writes: > : On Thu, Jan 22, 2009 at 04:26:33PM -0700, M. Warner Losh wrote: > : > In message: <20090122230647.GN50103@cicely7.cicely.de> > : > Bernd Walter writes: > : > : On Thu, Jan 22, 2009 at 03:57:41PM -0700, M. Warner Losh wrote: > : > : > In message: <20090122180518.GK50103@cicely7.cicely.de> > : > : > Bernd Walter writes: > : > : > : On Thu, Jan 22, 2009 at 08:02:14PM +0200, Alexander Motin wrote: > : > : > : > Bernd Walter wrote: > : > : > : > >As another point: > : > : > : > >Is it possible to support SHDC with mci some day, or is there a special > : > : > : > >hardware requirement for SDHC? > : > : > : > > : > : > : > SDHC (SD High Capacity) has just a different data addressing scheme (in > : > : > : > 512bytes blocks instead of bytes). There is no special hardware > : > : > : > requirements, only minor initialization differences. With present > : > : > : > mmc/mmcsd modules SDHC should work fine on any controller. > : > : > : > : > : > : Good news - thank you for clearification. > : > : > > : > : > Now all we need to do is to enhance the boot blocks to be able to boot > : > : > off the SDHC cards :) > : > : > : > : Yes, but since you wrote code to store the kernel inside SPI-flash > : > : there is a useable workaround available ;-) > : > : Full loader support would be more interesting than SDHC in boot code > : > : anyway. > : > > : > Raj@ did some interesting work in this area for the marvel port... > : > : I already noticed his work with great pleasure. > : > : > : > BTW, I found and fixed the bug (at least I think so). We were > : > : > assuming that all transfers were 512 bytes long. The newly used 16 > : > : > and 64 byte transfers broke that assumption, which is why things broke > : > : > after Alexander's latest commits. There's still a small chance that > : > : > there's something borked in the byte swapping code, but I kinda doubt > : > : > it since I was able to mount root. > : > : > > : > : > svn commit r187603 is the fix. > : > : > : > : Great! > : > > : > Well, it doesn't work in 4-bit bus mode. Of course, I'm not sure it > : > ever worked in 4-bit bus mode... > : > : It never worked - I tried it a while back and had interesting results, > : but it wasn't stable, which I asumed to be my bad knowledge on how this > : should be implemented correctly. > : Thanks to mav@ we have other controllers working and can test the > : sdmmc part unrelated from mci. > : Nevertheless: multiblock is the real speed issue. > : My speed tests were very impressive, but because of mci problems data > : were corrupted of course. > > I'll see if I can find an hour or two to look into the proper reset of > the mci fifos after use... I'd also like to get 4-bit working too... I have added some debug info with 4-bit mode enabled: http://mnemonic.bulinfo.net/~krassi/ARM/sd.dump3 > > Right now I'm only getting ~900kB/s (890-919) and we can do much > better, no? > > Warner > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFJee06xJBWvpalMpkRAgZ/AJ9FzKp7Oq00CZqWC/KIb31Ve0EPAgCdGH/l B1mZQcf8IYmdI/8x7C29iLo= =y2Rs -----END PGP SIGNATURE-----