Setting up framebuffer raises a floating point exception

[arvindsraj]

When trying to setup the framebuffer, a floating point exception is raised. The fault is actually when a value is written to CM_CLKSEL_DSS. For now, the process has been disabled by setting gFramebuffer to NULL and a TODO has been included.

[arvindsraj]

Modified the patch. Here's a description of the changes made.

• The comment is more verbose than before - it also mentions the specific commit of the qemu-linaro from git at which this was tested.
• The commented code now uses FB_BASE instead of harcoding it's value.

[pulkomandy]

Applied in hrev47590. Leaving the ticket open until the issue is actually fixed and we get the framebuffer going.

[ithamar]

This isn't an issue with the code, the issue is that we are trying to use OMAP3 code on an AM37x SoC. The LCD controller is not the same, just like another long list of peripherals. The problem is that the original target was the original BeagleBoard, while we are now testing it on QEMU using the BeagleBoard-xM target (which has a different SoC).

[pulkomandy]

This was fixed during the coding sprint. It works now!