Reported by Russell King:
mmcblk0: error -84 transferring data, sector 149201, nr 64,
cmd response 0x900, card status 0xb00
mmcblk0: retrying using single block read
WARNING: at /home/rmk/git/linux-2.6-rmk/lib/dma-debug.c:811 check_unmap
omap_hsmmc omap_hsmmc.0: DMA-API: device driver
On Sun, Aug 28, 2011 at 8:52 PM, Bernhard Rosenkranzer
wrote:
> On 27 August 2011 21:45, Bernhard Rosenkranzer
> wrote:
>> That's exactly what Android does in a couple of places, e.g.
>> system/core/init/logo.c, function fb_update() [that one actually calls
>> FBIOPUT_VSCREENINFO _twice_ to updat
On 27 August 2011 21:45, Bernhard Rosenkranzer
wrote:
> That's exactly what Android does in a couple of places, e.g.
> system/core/init/logo.c, function fb_update() [that one actually calls
> FBIOPUT_VSCREENINFO _twice_ to update the screen]
> hardware/libhardware/modules/gralloc/framebuffer.cpp,
On 28 August 2011 13:11, Russell King - ARM Linux
wrote:
> On Sun, Aug 28, 2011 at 12:50:54PM +0200, Per Forlin wrote:
>> On 26 August 2011 18:28, Santosh wrote:
>> > + Balaji,
>> >
>> > On Friday 26 August 2011 09:49 PM, Russell King - ARM Linux wrote:
>> >>
>> >> I'm not sure who's responsible
On Sun, Aug 28, 2011 at 12:50:54PM +0200, Per Forlin wrote:
> On 26 August 2011 18:28, Santosh wrote:
> > + Balaji,
> >
> > On Friday 26 August 2011 09:49 PM, Russell King - ARM Linux wrote:
> >>
> >> I'm not sure who's responsible for this, but the nonblocking MMC stuff is
> >> broken on OMAPs HS
On 26 August 2011 18:28, Santosh wrote:
> + Balaji,
>
> On Friday 26 August 2011 09:49 PM, Russell King - ARM Linux wrote:
>>
>> I'm not sure who's responsible for this, but the nonblocking MMC stuff is
>> broken on OMAPs HSMMC:
>>
>> mmcblk0: error -84 transferring data, sector 149201, nr 64, cmd
