the -more complete- version of the story ...

There is no new mmc driver in the kernel but there was a new generic mmc driver in the 'officail' u-boot code introduced over the last months. Pali is already using that one as the basis for his work.

The latest 'official' u-boot code (+RX-51 patches, as ali1234 made/described above) from the developers is booting Nemo fine. TEsted by ali1234.

So the Pali introduction of the bootmenu style on top of the 'working' code is breaking the init of the mmc, not allowing Nemo kernel to boot through.

Either by not completely initializing/resetting the twl4030 power convertor to power on the mmc subsystem as well or by not restoring/resetting the mmc registers the way the kernel expects them.

btw, Nemo is not the only kernel having this issue. Maemo5 had to include patches to get it working. The Kubuntu Mobile kernel (only one specific patched version of 2.6.35) is working fine with the Beagleboard (v v v similar HW). Later, unpatched kernel versions don't work. Same issue. Plenty of references on the gmane lists on this.

This can be solved (by smart people) on the Kernel side or on the u-boot side. Unfortunately the Nemo kernel people are not really interested, as they say it's mainly a u-boot (Pali version) fault and Pali says it's the kernel fault. I guess it's somewhere in the middle ...

btw, my Nemo Mobile - N900 Adaptation bug has been accepted and received status low.

Unfortunately ali1234 doesn't have access to the real code as created by Pali to help pinpointing where the issue might be on the u-boot side. Kernel side is v hard, as lots of patches I've tried for v similar issues (Error -110, TimeOut while waiting for a mmc answer), are not fixing the issue so far.

We asked Pali for that code so ali1234 can have a look as well and debug his way through if need be.

To be continued ??