Comment 15 for bug 627779

This bug is likely an artifact of the patch applied to fix #624115.

Bug #624115 happened when RMK decided to make ioremap of ram fail. He did this in his -next before the 2.6.36 cycle started. I assume the idea was to fix the framebuffer drivers that used ioremap later. Linux-linaro grabbed the bleeding edge rmk-next thus breaking the omap framebuffer. I assume that eventually there will be a better fix for #624115 but until then I believe we are stuck with some corruption when using framebuffer console. From the discussion that followed the workaround to #624115:

- In many cases we wouldn't need to ioremap inside the kernel at all, as
the kernel doesn't really need to read/write from/to the framebuffer. I
think the only user for this is the framebuffer console, which can be
disabled.

I'm not suggesting that turning off framebuffer console is a realistic option, onlyh that this corruption will likely be around for a while.

Of course Nico may pull a fix out of his hat at anytime.