uboot sometimes leaves eMMC pointing to the private boot
partition. Ensure we always start looking at the user partition
Signed-off-by: Philip Rakity
Signed-off-by: Bruce Clemens
Signed-off-by: Mark F. Brown
---
drivers/mmc/core/mmc.c | 11 +++
include/linux/mmc/card.h |1 +
Hi,
On Mon, Jan 31, 2011 at 11:42:17AM -0500, Marc-André Hébert wrote:
> While the MMC handled the card's read only flag correctly on open,
> it did not setup the flag in the allocated disk structure. The
> consequence being that probing the /sys/class/block/mmcblkX/ro
> attribute always reported
On Mon, 31 Jan 2011, Philip Rakity wrote:
> The transcend mmc card does not have the PHYSICAL pins for 4 bit mode; only 1
> bit can be supported.
>
> Testing the bus width is the recommend way to find out the bus width. The
> current behavior when the
> QUIRK is not defined is to default to 4
Nico,
Need some advice on how to solve a problem with mmc. Some background
>>>
>>> mmc cards have NO card specific data field to say the bus
>>> width that is supported. SD cards have this field.
>>>
>>> The only way to know what width a mmc card supports is to
>>> probe the card sending CMD14
While the MMC handled the card's read only flag correctly on open,
it did not setup the flag in the allocated disk structure. The
consequence being that probing the /sys/class/block/mmcblkX/ro
attribute always reported 0.
Signed-off-by: Marc-Andre Hebert
---
drivers/mmc/card/block.c |1 +
1
Hi Marc-André,
On Mon, Jan 31, 2011 at 09:01:02AM -0500, Marc-André Hébert wrote:
> Hello,
>
> I have on an OMAPL138 board running 2.6.33-rc4 (I would liked to try a
> more recent kernel but I do not have any boards which supports a more
> recent version). I noticed that I was unable to detect fr
Hello,
I have on an OMAPL138 board running 2.6.33-rc4 (I would liked to try a
more recent kernel but I do not have any boards which supports a more
recent version). I noticed that I was unable to detect from sysfs if
the inserted card was set to read only. The block device's
/sys/class/block/mmcbl