[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200807052111.49807.saschasommer@freenet.de>
Date: Sat, 5 Jul 2008 21:11:49 +0200
From: Sascha Sommer <saschasommer@...enet.de>
To: Pierre Ossman <drzeus-list@...eus.cx>
Cc: sdricohcs-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: Re: Status of Ricoh Bay1Controller driver?
Hi,
On Samstag, 5. Juli 2008, Pierre Ossman wrote:
> Hi Sascha,
>
> How are things going with the driver? I was hoping we could get it into
> the kernel for 2.6.27 at least.
>
Ok here we go again:
Based on the feedback from your last review I did the following changes:
- the driver should now be able to transfer data blocks with sizes smaller
than 512 mb
- the endian problems in the block/io function should be gone
- the YENTA dependency has been removed
- the cmd specific includes have been removed
- set_ios() has been fixed to set the bus width correctly
- the busy check has been removed as per your suggestion
Apart from that the following problems remain:
There is still some hack for ACMDs. I know you won't like that but I did not
get the SD_APP_SEND_SCR command to work without it.
MMC_SEND_EXT_CSD does not work (also not with that ACMD hack) and prints out
something like:
sdricoh_cs 0.0: query_status: timeout waiting for 1000000
sdricoh_cs 0.0: sdricoh_request: cmd 8 block transfer failed
sdricoh_cs 0.0: query_status: timeout waiting for 4
sdricoh_cs 0.0: sdricoh_request: transfer end error
mmc0: unable to read EXT_CSD, performance might suffer.
The card works without problems after this message.
Regards
Sascha
View attachment "sdricoh_cs_try3.patch" of type "text/x-diff" (16547 bytes)
Powered by blists - more mailing lists