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 from sysfs if > the inserted card was set to read only. The block device's > /sys/class/block/mmcblk0/ro entry always reported 0. The read only > gpio is correctly setup as opening the device for writing fails as > expected. Interesting, thanks -- no, I don't imagine this is intentional, and I can confirm the behavior on an x86 laptop/SDHCI running 2.6.38-rc2. Your patch looks correct to me. I'm surprised no-one's noticed this before. Could you re-send it as a Git patch with a Signed-off-by: line, please? -- Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
