From: Jason P. <ja...@wi...> - 2007-08-08 17:42:10
|
Hi All, I managed to get the frame buffer working with the Panasonic LCD. I mis-typed a rm statement and deleted my linux directory under build_arm_nofpu/. I rebuilt everything and now I get four images of whatever I send to the frame buffer all inter-woven. It looks like the resolution is wrong, or something like that. I did not change any of my bootargs for the screen setup. I am using the following: video=pxafb:mode:640x480-16,passive,color,hsynclen:3,right:5,left:10,vsynclen:39,pixclock:100000,hsync:1,vsync:1,pixclockpol:0 As I said this worked fine before I rebuilt the kernel. I have the framebuffer configs selected according to the Display wiki which is exactly what I did before. This is driving me nuts... I have been trying to get this fixed with no avail for the past couple of days. Any help is greatly appreciated. Thanks, Jason Peterson |
From: Jason P. <ja...@wi...> - 2007-08-08 21:19:58
|
Jason Peterson wrote: > Hi All, > > I managed to get the frame buffer working with the Panasonic LCD. I > mis-typed a rm statement and deleted my linux directory under > build_arm_nofpu/. I rebuilt everything and now I get four images of > whatever I send to the frame buffer all inter-woven. It looks like the > resolution is wrong, or something like that. I did not change any of my > bootargs for the screen setup. I am using the following: > > video=pxafb:mode:640x480-16,passive,color,hsynclen:3,right:5,left:10,vsynclen:39,pixclock:100000,hsync:1,vsync:1,pixclockpol:0 > > As I said this worked fine before I rebuilt the kernel. I have the > framebuffer configs selected according to the Display wiki which is > exactly what I did before. > > This is driving me nuts... I have been trying to get this fixed with no > avail for the past couple of days. > > Any help is greatly appreciated. > > Thanks, > > Jason Peterson > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > I reverted back to revision 1462 and all work... anyone have any insight on why on more recent builds the Panasonic LCD doesn't work? Is the new LCD code overriding the bootargs? jason |
From: Craig H. <cr...@gu...> - 2007-08-08 23:20:06
|
On Aug 8, 2007, at 2:20 PM, Jason Peterson wrote: > I am using the following: > > video=pxafb:mode:640x480-16,passive,color,hsynclen:3,right:5,left: > 10,vsynclen:39,pixclock:100000,hsync:1,vsync:1,pixclockpol:0 > I reverted back to revision 1462 and all work... anyone have any > insight > on why on more recent builds the Panasonic LCD doesn't work? Is > the new > LCD code overriding the bootargs? the bootargs override the hardcoded stuff, not the other way round. r1463 switched the default screen setup from the SHARP panel to the Samsung one, which changes (among other things) the lower_margin setting -- I notice you're not passing upper/lower in the bootargs, so those values will be set up with the hardcoded defaults. Try passing upper/lower and see if that helps. Alternatively, change the linux config to use the SHARP panel instead of the Samsung one for compiled-in defaults. C |