Sorry but you are wrong.

My example was for a BYTE datatype, if you use an INT it is normal that it works as you expected because my numbers are too little to generate an overflow during left shift.

But please try with correct numbers
And the above code yields to these results:
Numbers are very different now.

I reapet that C code like n<<VAR>>n (or (2^n)*VAR>>n) is usually used to clear the n most significative bits of VAR (if VAR is unsigned)

It is the same only for values smaller than 2^(n-2), where n is the number of bits contained on you variable/constant (8, 16, 32 or 64).
So compiler can optimize (and remove useless operations) only if it is a constant and the fixed value assigned is less then 2^(n-2) alias 1,073,741,824 for an integer costant

@Fabry: ok, now I know this, but in U-Boot our number was not very big (so no change)

Now I published new version of U-Boot. It has fixed eMMC support and runtime configurable bootmenu.

Source code is now in branch pali on u-boot-shr: https://gitorious.org/u-boot-shr/u-boot/commits/pali

Good job.

Now when this problems:

• High power consumption
• Incompatibility with HW Rev different from 2101 (as Matan's version)

will be fixed, Pali's u-boot will be the best boot-loader for N900

For compatibility with other HW revisions, see http://talk.maemo.org/showpost.php?p...&postcount=120
Should work on 2101, 2204 and 2104...

And power problem. Now we have in u-boot code for twl4030 regulator, so we have tool for power control. Also code for control GPIO and MUX is in u-boot too...

So the two problems have been already fixed ?

I have a rev 2101 and I can check eventually only power consumption.

Holy ****, Pali! This is better than Multiboot!
I'm going to measure power consumption before/after u-boot when I have time (probably this Saturday).

Can we have this by default in power50?

I made an attempt with the new kp48 image.

These are the problems found:

• Power consumption problem is still present.
  Initially it seems that p. consumption is normal (discharge rate on idle = 1-3% / hour) but after 1-2 hours of continuos idle the situation changes and becomes "discharge rate on idle greater than 10% / hour"
• Lcd screen is always powered on.
  Maemo never turns off it, it only shows a black screen (with backlight on, this is evident on a dark room)
• There is problem with battery's charge measurement.
  I had 50% of reported battery's charge and I have rebooted the phone.
  After reboot reported battery's charge was only 7% and some mins after it was still 7%.
  I doubted that a boot process can really consume over 40% of battery's charge, so I have flashed, by multiboot, a PR1.3 kernel (with no u-boot).
  After reboot the reported battery's charge was 10% (greater than before) and some mins after it has raised to 39%
• It seems that bootmenu appears even with closed keyboard

@fabry
comparing uboot+kp48 with pr13kernel seems wrong to see power consumption differences.
You should use kp48 with and without u-boot to do valid comparison tests.