On Wed, Sep 01, 2010 at 11:57:32, Caglar Akyuz wrote: > Forget add LCDC register values: > > not working: > *** 4: 0x601 *** > > > *** 8: 0x4 *** > > > *** 40: 0x2ff0c1 *** > > > *** 44: 0x3030fe70 *** > > > *** 48: 0x1f0b05df *** > > > *** 52: 0x270ff00 *** > > > *** 64: 0x45 *** > > > *** 68: 0xc7a00000 *** > > > *** 72: 0xc7a95ffc *** > > > *** 76: 0xc7a00000 *** > > > *** 80: 0xc7a95ffc *** > > working: > *** 4: 0x601 *** > *** 8: 0x145 *** > *** 40: 0xff0c1 *** > *** 44: 0x3030fe70 *** > *** 48: 0x1f0b05df *** > *** 52: 0x270ff00 *** > *** 64: 0x40 *** > *** 68: 0xc7a00fe0 *** > *** 72: 0xc7a96ffc ***
If I am interpreting the above correctly then "*** 8" corresponds to LCD_STAT. In the working case bit 6 is set indicating the palette has been loaded whereas this is not set in the failure case. This was definitely an area of change in the double buffer patch. Prior the palette was loaded explicitly in the fb_probe function. In the double buffer case this is loaded by the setcolreg function. Normally this is called during kernel boot (I think) when the display is configured for the boot logo. If it is not then I believe you can force a call through a user space ioctl but I'm not sure what that is atm. Now if could be that the palette is being loaded but then there is an error afterwards. Can you add a debug print to the lcd_blit function to see if it is being called with LOAD_PALETTE? Regards, Martin _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
