Comment 15 for bug 607906

Yeah, my XM Rev A (256Mb) has the same issue. Although i haven't looked at it closely in awhile, is there any kind of "Write Protect" level on the mini-sd card holder? I don't think there is, well the kernel still thinks there is, we will have to add another check here for the XM, to ignore the gpio_wg...

Something like???

diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
index bec90ad..3f95e7e 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -379,7 +379,10 @@ static struct gpio_led gpio_leds[];
 static int beagle_twl_gpio_setup(struct device *dev,
                unsigned gpio, unsigned ngpio)
 {
- if (system_rev >= 0x20 && system_rev <= 0x34301000) {
+ if (cpu_is_omap3630()) {
+ mmc[0].gpio_wp = -EINVAL;
+ }
+ else if (system_rev >= 0x20 && system_rev <= 0x34301000) {
                omap_mux_init_gpio(23, OMAP_PIN_INPUT);
                mmc[0].gpio_wp = 23;
        } else {

Based from: http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=blob;f=arch/arm/mach-omap2/board-omap3beagle.c;h=6a6d2d7a04c6f0bd9f539b4c5f34510f46175bc1;hb=HEAD

Regards,