From owner-freebsd-arm@FreeBSD.ORG Fri Feb 23 11:19:28 2007 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 63E9016A400 for ; Fri, 23 Feb 2007 11:19:28 +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 1F9B113C441 for ; Fri, 23 Feb 2007 11:19:28 +0000 (UTC) (envelope-from krassi@bulinfo.net) Received: from localhost (localhost [127.0.0.1]) by mx.bulinfo.net (Postfix) with ESMTP id 4380F17763F; Fri, 23 Feb 2007 13:19:24 +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 92827-02; Fri, 23 Feb 2007 13:19:22 +0200 (EET) Received: from [192.168.2.188] (pythia.bulinfo.net [212.72.195.5]) by mx.bulinfo.net (Postfix) with ESMTP id 9309917763D; Fri, 23 Feb 2007 13:19:22 +0200 (EET) Message-ID: <45DECDB9.1060906@bulinfo.net> Date: Fri, 23 Feb 2007 13:19:21 +0200 From: Krassimir Slavchev User-Agent: Thunderbird 1.5 (X11/20060201) MIME-Version: 1.0 To: ticso@cicely.de References: <45DD6E45.5000505@bulinfo.net> <20070222.082227.-2001110508.imp@bsdimp.com> <45DDC686.50405@bulinfo.net> <20070222174946.GE24769@cicely12.cicely.de> In-Reply-To: <20070222174946.GE24769@cicely12.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at mx.bulinfo.net Cc: freebsd-arm@freebsd.org Subject: Re: SD card 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, 23 Feb 2007 11:19:28 -0000 Bernd Walter wrote: > On Thu, Feb 22, 2007 at 06:36:22PM +0200, Krassimir Slavchev wrote: > >> M. Warner Losh wrote: >> >>> In message: <45DD6E45.5000505@bulinfo.net> >>> Krassimir Slavchev writes: >>> : Hello, >>> : >>> : I've read that SD is not supported by qdmmc and now qdmmc does not exist >>> : in the source tree. >>> : Are the SD cards supported by mmcsd driver? >>> >>> Yes. The qdmmc driver is no more. The at91_mci driver is the host >>> adapter driver, mmc is the bus, and mmcsd is support for mmc/sd cards >>> (although only sd will work at the moment due to lack of hardware). >>> >>> >>> >> Good! >> >> I am going to investigate why my SD card is not detected. >> >> dmesg says only: >> >> at91_mci0: Setting controller bus width to 1 >> at91_mci0: Setting controller bus width to 1 >> at91_mci0: Setting controller bus width to 1 >> at91_mci0: Setting controller bus width to 1 >> mmc0: setting transfer rate to 30.000MHz >> at91_mci0: Setting controller bus width to 1 >> > > I noticed a problem when netbooting, that cards are only detected on > reboot. > Booting via boot2 doesn't hsow this problem. > Another point, which I noticed yesterday is that the kernel did not > find a verbatim media, although boot2 sucessfully loaded the kernel. > > Yes, because bootspi does not call sdcard_init() function! After adding: Timecounters tick every 10.000 msec at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 at91_mci0: Setting controller bus width to 1 SD CARD: 998768640 bytes at91_mci0: Setting controller bus width to 1 mmcsd0: on mmc0 mmc0: setting transfer rate to 30.000MHz at91_mci0: Setting controller bus width to 1 Trying to mount root from ufs:/dev/mmcsd0s1a >>> : Also what this line in dmesg means: >>> : 'Cannot get 100 Hz clock; using 100Hz' >>> : May be something is not initialized? >>> >>> No, that just means you can't divide 32768 by 100 evenly. >>> >>> Warner >>> >>> >>> >> And another problem: >> >> ate0: mem 0xdffbc000-0xdffbffff irq 24 on atmelarm0 >> ate0: Cannot find my PHY. >> device_attach: ate0 attach returned 6 >> >> Looks like nothing on miibus. Very strange because the bootspi is able >> to boot from tftp server. >> The PHY is RTL8201CP and I use rlphy driver which is for RTL8201L. >> >> Any hints where to look? >> > > Enhance the rlphy driver - should be enough to add the device ID. > The additional automdix feature should be tranparent. > >