From: Peter L. <pl...@gm...> - 2007-08-21 18:42:25
|
Hi, I'm trying to get my Sony Acx705akm display running and got the test program from: http://docwiki.gumstix.org/Display#Setting_up_the_Sony_ACX705AKM_on_gumstix My .config for the linux kernel has: CONFIG_FB_PXA=m # CONFIG_FB_PXA_ALPS_CDOLLAR is not set # CONFIG_FB_PXA_SHARP_LQ043_PSP is not set CONFIG_FB_PXA_SAMSUNG_LTE430WQ_F0C=y CONFIG_FB_PXA_PARAMETERS=y so I think the PXA FB stuff is in the build and should be able to handle the Sony display despite the Samsung being configured. In U-boot's bootargs, I have: video=pxafb:mode:240x160-16,active,hsynclen:7,right:16,left:5,upper:19,low er:19,vsynclen:2,hsync:1,vsync:1,pixclockpol:0,pixclock:216363 and I do: mknod /dev/fb0 c 29 0 chmod a+rw /dev/fb0 modprobe pxafb I compile the test program from the Web page and do: ppmv_sony692 sony_penguin.ppm The code displays the expected message: Mapping SCREENSIZE: 76800 done width = 240, height = 160 done which seems to indicate that the device was opened correctly and the image was written to the frame buffer. However, my screen shows nothing. What steps am I missing and how do I go about diagnosing what's wrong? Thanks for all help. |
From: Craig H. <cr...@gu...> - 2007-08-21 19:20:51
|
On Aug 21, 2007, at 11:42 AM, Peter Lu wrote: > I'm trying to get my Sony Acx705akm display running and got the > test program from: > > http://docwiki.gumstix.org/ > Display#Setting_up_the_Sony_ACX705AKM_on_gumstix > > My .config for the linux kernel has: > > CONFIG_FB_PXA=m > # CONFIG_FB_PXA_ALPS_CDOLLAR is not set > # CONFIG_FB_PXA_SHARP_LQ043_PSP is not set > CONFIG_FB_PXA_SAMSUNG_LTE430WQ_F0C=y > CONFIG_FB_PXA_PARAMETERS=y > > so I think the PXA FB stuff is in the build and should be able to > handle > the Sony display despite the Samsung being configured. If you don't have the samsung screen, don't turn that on. > In U-boot's bootargs, I have: > > video=pxafb:mode:240x160-16,active,hsynclen:7,right:16,left:5,upper: > 19,low > er:19,vsynclen:2,hsync:1,vsync:1,pixclockpol:0,pixclock:216363 > > and I do: > > mknod /dev/fb0 c 29 0 > chmod a+rw /dev/fb0 Don't create this manually. udev will make the device node automatically when you load the module. > modprobe pxafb You need to pass the pxafb options here, or else set them in /etc/ modprobe.conf to be passed automatically. the u-boot "video=xyz" stuff will only work if pxafb is builtin to the kernel uImage. C |
From: Peter L. <pl...@gm...> - 2007-08-21 20:15:24
|
Hi, The FB_PXA selection for ALPS, SHARP, or SAMSUNG is forced upon me by the configuration process. I tried turning off SAMSUNG manually via .config and doing "make oldconfig" and the SAMSUNG selection keeps getting defined to =y. I don't think there's a way to configure all 3 items to "is not set." I tried to manually "modprobe pxafb mode=240x160-16 active ..." and dmesg keeps showing: pxafb: Unknown parameter `mode' I've tried similar options setting in modprobe.conf without luck. Please advise. Thanks. Thanks for mentioning that the "video=" boot option is only applicable to in-kernel pxafb. On 8/21/07, Craig Hughes <cr...@gu...> wrote: > > On Aug 21, 2007, at 11:42 AM, Peter Lu wrote: > > I'm trying to get my Sony Acx705akm display running and got the > test program from: > > http://docwiki.gumstix.org/Display#Setting_up_the_Sony_ACX705AKM_on_gumstix > > > My .config for the linux kernel has: > > CONFIG_FB_PXA=m > # CONFIG_FB_PXA_ALPS_CDOLLAR is not set > # CONFIG_FB_PXA_SHARP_LQ043_PSP is not set > CONFIG_FB_PXA_SAMSUNG_LTE430WQ_F0C=y > CONFIG_FB_PXA_PARAMETERS=y > > so I think the PXA FB stuff is in the build and should be able to handle > the Sony display despite the Samsung being configured. > > > If you don't have the samsung screen, don't turn that on. > > In U-boot's bootargs, I have: > > video=pxafb:mode:240x160-16,active,hsynclen:7,right:16,left:5,upper:19,low > > er:19,vsynclen:2,hsync:1,vsync:1,pixclockpol:0,pixclock:216363 > > and I do: > > mknod /dev/fb0 c 29 0 > chmod a+rw /dev/fb0 > > > Don't create this manually. udev will make the device node automatically > when you load the module. > > modprobe pxafb > > > You need to pass the pxafb options here, or else set them in > /etc/modprobe.conf to be passed automatically. the u-boot "video=xyz" stuff > will only work if pxafb is builtin to the kernel uImage. > > C > > ------------------------------------------------------------------------- > 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 > > |
From: Craig H. <cr...@gu...> - 2007-08-21 20:43:18
|
On Aug 21, 2007, at 1:15 PM, Peter Lu wrote: > I tried to manually "modprobe pxafb mode=240x160-16 active ..." and > dmesg keeps > showing: > > pxafb: Unknown parameter `mode' I think you need to do modprobe pxafb video=mode=240x160-16,active,.... C |
From: Peter L. <pl...@gm...> - 2007-08-21 20:45:38
|
I have the options line set correctly in modprobe.conf, but nothing displays when running " options pxafb options=mode:240x160-16,active,hsynclen:7,right:16,left:5,upper:19 ,lower:19,vsynclen:2,hsync:1,vsync:1,pixclockpol:0,pixclock:216363 # modprobe pxafb pxa2xx-fb pxa2xx-fb: overriding resolution: 240x160 pxa2xx-fb pxa2xx-fb: overriding bit depth: 16 pxa2xx-fb pxa2xx-fb: override hsynclen: 7 pxa2xx-fb pxa2xx-fb: override right: 16 pxa2xx-fb pxa2xx-fb: override left: 5 pxa2xx-fb pxa2xx-fb: override upper: 19 pxa2xx-fb pxa2xx-fb: override lower: 19 pxa2xx-fb pxa2xx-fb: override vsynclen: 2 pxa2xx-fb pxa2xx-fb: override hsync: Active High pxa2xx-fb pxa2xx-fb: override vsync: Active High pxa2xx-fb pxa2xx-fb: override pixel clock polarity: falling edge # lsmod Module Size Used by pxafb 10312 0 [permanent] cfbcopyarea 3072 1 pxafb fb 34180 1 pxafb cfbimgblt 2464 1 pxafb cfbfillrect 3456 1 pxafb ipv6 259744 10 nfsd 223148 13 exportfs 4576 1 nfsd lockd 63640 2 nfsd nfs_acl 3040 1 nfsd sunrpc 163440 9 nfsd,lockd,nfs_acl af_packet 17608 2 proc_gpio 7084 0 nls_iso8859_1 3872 1 nls_cp437 5536 1 vfat 10112 1 fat 46492 1 vfat nls_base 6752 4 nls_iso8859_1,nls_cp437,vfat,fat pata_pcmcia 9696 0 libata 97268 1 pata_pcmcia scsi_mod 87236 1 libata ide_disk 13248 2 ide_cs 8960 1 ide_core 79252 2 ide_disk,ide_cs pxa2xx_cs 2980 3 pxa2xx_core 10400 1 pxa2xx_cs pcmcia 25384 2 pata_pcmcia,ide_cs pcmcia_core 31184 4 pata_pcmcia,ide_cs,pxa2xx_core,pcmcia firmware_class 7552 1 pcmcia unix 24308 12 smc91x 16680 0 mii 4736 1 smc91x gumstix_smc91x 2816 1 smc91x # # ./ppmv_sony692 sony_penguin2.ppm Mapping SCREENSIZE: 76800 done width = 240, height = 160 done But I'm still using the "Samsung" FB driver, if there is such a mode, since the Linux .config doesn't allow me to turn it off. On 8/21/07, Peter Lu <pl...@gm...> wrote: > > Hi, > > The FB_PXA selection for ALPS, SHARP, or SAMSUNG is forced upon me by the > configuration process. I tried turning off SAMSUNG manually via .config > and doing > "make oldconfig" and the SAMSUNG selection keeps getting defined to =y. I > > don't think there's a way to configure all 3 items to "is not set." > > I tried to manually "modprobe pxafb mode=240x160-16 active ..." and dmesg > keeps > showing: > > pxafb: Unknown parameter `mode' > > I've tried similar options setting in modprobe.conf without luck. > > Please advise. Thanks. > > Thanks for mentioning that the "video=" boot option is only applicable to > in-kernel > pxafb. > > > On 8/21/07, Craig Hughes <cr...@gu...> wrote: > > > On Aug 21, 2007, at 11:42 AM, Peter Lu wrote: > > > > I'm trying to get my Sony Acx705akm display running and got the > > test program from: > > > > http://docwiki.gumstix.org/Display#Setting_up_the_Sony_ACX705AKM_on_gumstix > > > > > > My .config for the linux kernel has: > > > > CONFIG_FB_PXA=m > > # CONFIG_FB_PXA_ALPS_CDOLLAR is not set > > # CONFIG_FB_PXA_SHARP_LQ043_PSP is not set > > CONFIG_FB_PXA_SAMSUNG_LTE430WQ_F0C=y > > CONFIG_FB_PXA_PARAMETERS=y > > > > so I think the PXA FB stuff is in the build and should be able to handle > > the Sony display despite the Samsung being configured. > > > > > > If you don't have the samsung screen, don't turn that on. > > > > In U-boot's bootargs, I have: > > > > video=pxafb:mode:240x160-16,active,hsynclen:7,right:16,left:5,upper:19,low > > > > er:19,vsynclen:2,hsync:1,vsync:1,pixclockpol:0,pixclock:216363 > > > > and I do: > > > > mknod /dev/fb0 c 29 0 > > chmod a+rw /dev/fb0 > > > > > > Don't create this manually. udev will make the device node > > automatically when you load the module. > > > > modprobe pxafb > > > > > > You need to pass the pxafb options here, or else set them in > > /etc/modprobe.conf to be passed automatically. the u-boot "video=xyz" stuff > > will only work if pxafb is builtin to the kernel uImage. > > > > C > > > > > > ------------------------------------------------------------------------- > > 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 > > > > > |
From: Craig H. <cr...@gu...> - 2007-08-21 20:55:32
|
On Aug 21, 2007, at 1:45 PM, Peter Lu wrote: > But I'm still using the "Samsung" FB driver, if there is such a mode, > since the Linux .config doesn't allow me to turn it off. Hmm. Well, try the "Chris Dollar ALPS" choice instead. I'll see about allowing that setting to just be turned off (ie add a "none" option). C |
From: Peter L. <pl...@gm...> - 2007-08-21 21:32:39
|
I just tried the Chris Dollar driver and nothing displays. My hardware wiring may be different from the "standard" one, if there is such a thing. I'm not sure how to go about verifying the wiring. These are some of the LCD-related signals, according to the .sh scripts in the acx705akm/ sample package. # cat dregs_sony692.sh #!/bin/sh P=/usr/sbin $P/pxaregs GPCR2_81 $P/pxaregs GPDR2_81 $P/pxaregs LCCR1_HSW $P/pxaregs LCCR1_ELW $P/pxaregs LCCR1_BLW $P/pxaregs LCCR2_VSW $P/pxaregs LCCR2_EFW $P/pxaregs LCCR2_BFW $P/pxaregs LCCR3_PCD $P/pxaregs LCCR3_VSP $P/pxaregs LCCR3_HSP $P/pxaregs LCCR3_PCP # dregs_sony692.sh GPIO 81 clear GPCR2_81 0x00000000 00000000 00000000 00000000 00000000 GPCR2_81 0 GPIO 81 clear GPIO 81 i/o direction (1=output) GPDR2_81 0x0015bfff 00000000 00010101 10111111 11111111 GPDR2_81 0 GPIO 81 i/o direction (1=output) LCD horizontal sync pulse width (+1) LCCR1_HSW 0x040f18ef 00000100 00001111 00011000 11101111 LCCR1_HSW 6 LCD horizontal sync pulse width (+1) LCD end of line pixel clock wait count (+1) LCCR1_ELW 0x040f18ef 00000100 00001111 00011000 11101111 LCCR1_ELW 15 LCD end of line pixel clock wait count (+1) LCD beginning of line pixel clock wait count (+1) LCCR1_BLW 0x040f18ef 00000100 00001111 00011000 11101111 LCCR1_BLW 4 LCD beginning of line pixel clock wait coun t (+1) LCD vertical sync pulse width (+1) LCCR2_VSW 0x1313049f 00010011 00010011 00000100 10011111 LCCR2_VSW 1 LCD vertical sync pulse width (+1) LCD end of frame line clock wait count (+1) LCCR2_EFW 0x1313049f 00010011 00010011 00000100 10011111 LCCR2_EFW 19 LCD end of frame line clock wait count (+1) LCD beginning of frame line clock wait count (+1) LCCR2_BFW 0x1313049f 00010011 00010011 00000100 10011111 LCCR2_BFW 19 LCD beginning of frame line clock wait coun t (+1) LCD pixel clock divisor (+1) LCCR3_PCD 0x0440000a 00000100 01000000 00000000 00001010 LCCR3_PCD 10 LCD pixel clock divisor (+1) LCD L_FCLK vertical sync polarity active low LCCR3_VSP 0x0440000a 00000100 01000000 00000000 00001010 LCCR3_VSP 0 LCD L_FCLK vertical sync polarity active lo w LCD L_LCLK horizontal sync polarity active low LCCR3_HSP 0x0440000a 00000100 01000000 00000000 00001010 LCCR3_HSP 0 LCD L_LCLK horizontal sync polarity active low LCD data sampled on falling edge of L_PCLK LCCR3_PCP 0x0440000a 00000100 01000000 00000000 00001010 LCCR3_PCP 1 LCD data sampled on falling edge of L_PCLK # On 8/21/07, Craig Hughes <cr...@gu...> wrote: > > On Aug 21, 2007, at 1:45 PM, Peter Lu wrote: > > But I'm still using the "Samsung" FB driver, if there is such a mode, > since the Linux .config doesn't allow me to turn it off. > > > Hmm. Well, try the "Chris Dollar ALPS" choice instead. I'll see about > allowing that setting to just be turned off (ie add a "none" option). > > C > > ------------------------------------------------------------------------- > 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 > > |
From: Peter L. <pl...@gm...> - 2007-08-22 14:17:00
|
Hi, The pxafb driver uses pr_debug() to print messages. How do I go about turning it on/off (and is this a run-time or compile-time option)? Thanks for help. On 8/21/07, Peter Lu <pl...@gm...> wrote: > > I just tried the Chris Dollar driver and nothing displays. My hardware > wiring may be > different from the "standard" one, if there is such a thing. I'm not sure > how to go > about verifying the wiring. > > These are some of the LCD-related signals, according to the .sh scripts in > the acx705akm/ sample package. > > # cat > dregs_sony692.sh > #!/bin/sh > > > > P=/usr/sbin > > > > $P/pxaregs > GPCR2_81 > $P/pxaregs > GPDR2_81 > > > $P/pxaregs > LCCR1_HSW > $P/pxaregs > LCCR1_ELW > $P/pxaregs > LCCR1_BLW > > > $P/pxaregs > LCCR2_VSW > $P/pxaregs > LCCR2_EFW > $P/pxaregs > LCCR2_BFW > > > $P/pxaregs > LCCR3_PCD > $P/pxaregs > LCCR3_VSP > $P/pxaregs > LCCR3_HSP > $P/pxaregs > LCCR3_PCP > # > dregs_sony692.sh > > > > GPIO 81 > clear > GPCR2_81 0x00000000 00000000 00000000 00000000 > 00000000 > GPCR2_81 0 GPIO 81 > clear > > > GPIO 81 i/o direction > (1=output) > GPDR2_81 0x0015bfff 00000000 00010101 10111111 > 11111111 > GPDR2_81 0 GPIO 81 i/o direction > (1=output) > > > LCD horizontal sync pulse width > (+1) > LCCR1_HSW 0x040f18ef 00000100 00001111 00011000 > 11101111 > LCCR1_HSW 6 LCD horizontal sync pulse width > (+1) > > > LCD end of line pixel clock wait count > (+1) > LCCR1_ELW 0x040f18ef 00000100 00001111 00011000 > 11101111 > LCCR1_ELW 15 LCD end of line pixel clock wait > count (+1) > > > LCD beginning of line pixel clock wait count > (+1) > LCCR1_BLW 0x040f18ef 00000100 00001111 00011000 > 11101111 > LCCR1_BLW 4 LCD beginning of line pixel clock > wait coun > t > (+1) > > > > LCD vertical sync pulse width > (+1) > LCCR2_VSW 0x1313049f 00010011 00010011 00000100 > 10011111 > LCCR2_VSW 1 LCD vertical sync pulse width > (+1) > > > LCD end of frame line clock wait count > (+1) > LCCR2_EFW 0x1313049f 00010011 00010011 00000100 > 10011111 > LCCR2_EFW 19 LCD end of frame line clock wait > count (+1) > > > LCD beginning of frame line clock wait count > (+1) > LCCR2_BFW 0x1313049f 00010011 00010011 00000100 > 10011111 > LCCR2_BFW 19 LCD beginning of frame line clock > wait coun > t > (+1) > > > > LCD pixel clock divisor > (+1) > LCCR3_PCD 0x0440000a 00000100 01000000 00000000 > 00001010 > LCCR3_PCD 10 LCD pixel clock divisor > (+1) > > > LCD L_FCLK vertical sync polarity active > low > LCCR3_VSP 0x0440000a 00000100 01000000 00000000 > 00001010 > LCCR3_VSP 0 LCD L_FCLK vertical sync polarity > active lo > w > > > > LCD L_LCLK horizontal sync polarity active > low > LCCR3_HSP 0x0440000a 00000100 01000000 00000000 > 00001010 > LCCR3_HSP 0 LCD L_LCLK horizontal sync polarity > active > low > > > > LCD data sampled on falling edge of > L_PCLK > LCCR3_PCP 0x0440000a 00000100 01000000 00000000 > 00001010 > LCCR3_PCP 1 LCD data sampled on falling edge of > L_PCLK > # > > > > > On 8/21/07, Craig Hughes <cr...@gu...> wrote: > > > > On Aug 21, 2007, at 1:45 PM, Peter Lu wrote: > > > > But I'm still using the "Samsung" FB driver, if there is such a mode, > > since the Linux .config doesn't allow me to turn it off. > > > > > > Hmm. Well, try the "Chris Dollar ALPS" choice instead. I'll see about > > allowing that setting to just be turned off (ie add a "none" option). > > > > C > > > > > > ------------------------------------------------------------------------- > > 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 > > > > > |
From: Mark A. <ma...@le...> - 2007-08-22 12:17:12
|
Any guidance for the best hardware and OS for this project is appreciate= d. =20 I'd like to assemble a cellular internet kiosk device capable of running= a full web browser with Flash player support. It will have no other= mission in life other than to download and display web pages with Flash= content over the cell networks: no custom apps are planned. =20 It should satisfy these requirements: 1. small and economical so as to be embedded in varied enclosure types= and sizes=20 2. able to run on wall power, no battery required=20 3. no moving parts=20 4. must have an embedded OS capable of running a full browser with Flash= support. I expect this will be embedded Linux due to cost and compatib= ility with Firefox and Flash Player, but I'm no Linux expert. WinCE cou= ld also be an option if a full browser and/or Flash player support is= available.=20 5. should support audio embedded in the web pages and Flash movies but= not required=20 6. must be remotely controllable through FTP, telnet, etc. for updates= =20 7. must be able to interface with different cellular networks (Sprint,= Verizon, etc). This could be through onboard cellular hardware or perh= aps through USB or PCMCIA add-on hardware=20 8. should be able to interface with 802.11 wireless networks but not req= uired=20 9. must include or be able to interface with a PDA sized display, 3x5"= etc. (size is flexible) What do you suggest is a good approach to putting together this device?= Does Gumstix have products you recommend I consider? The Verdex with= Goliath board may be a good option, but I'm concerned it may end up bei= ng larger than I want and have more functionality than I need. Any thoughts are much appreciated! Mark |
From: dima Q <di...@gm...> - 2007-08-23 12:11:38
|
I think you should make a PC prototype first, then find a small pc - I tried 99-dollar mini-pc (200MHz), it ran firefox and flash, did sound fine, but was too slow for youtube (about 1fps), so perhaps you should consider something a bit faster - either one of those 300-dollar home PC's or Via mini-ITX. Unless you are going to make thousands of these, I would not bother with embedded components - whether gumstix or displays, instead stick to off-the shelf components and car entertainment displays. As far as mobile networks are concerned you need to decide what your bandwidth requirements are, namely whether you need 3G - that alone will influence your choice of modem more than anything. A radical alternative is to use a smartphone that already plays flash, has mobile data and a screen, and sprinkle a bit custom software on it. There are many choices, although a bit pricey :) Good Luck d. On 8/22/07, Mark Arnold <ma...@le...> wrote: > > Any guidance for the best hardware and OS for this project is appreciated. > > I'd like to assemble a cellular internet kiosk device capable of running a > full web browser with Flash player support. It will have no other mission > in life other than to download and display web pages with Flash content over > the cell networks: no custom apps are planned. > > It should satisfy these requirements: > > 1. small and economical so as to be embedded in varied enclosure > types and sizes > 2. able to run on wall power, no battery required > 3. no moving parts > 4. must have an embedded OS capable of running a full browser with > Flash support. I expect this will be embedded Linux due to cost and > compatibility with Firefox and Flash Player, but I'm no Linux expert. WinCE > could also be an option if a full browser and/or Flash player support is > available. > 5. should support audio embedded in the web pages and Flash movies > but not required > 6. must be remotely controllable through FTP, telnet, etc. for > updates > 7. must be able to interface with different cellular networks > (Sprint, Verizon, etc). This could be through onboard cellular hardware or > perhaps through USB or PCMCIA add-on hardware > 8. should be able to interface with 802.11 wireless networks but not > required > 9. must include or be able to interface with a PDA sized display, > 3x5" etc. (size is flexible) > > What do you suggest is a good approach to putting together this > device? Does Gumstix have products you recommend I consider? The Verdex > with Goliath board may be a good option, but I'm concerned it may end up > being larger than I want and have more functionality than I need. > > Any thoughts are much appreciated! > Mark > > > > ------------------------------------------------------------------------- > 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 > |
From: Peter L. <pl...@gm...> - 2007-08-24 11:04:43
|
Hi, My LCD is now apparently working, after adjusting some mechanical cabling problem and deasserting SHUTDOWN. However, when I run: ppmv_sony692 sony_penguin.ppm I get three faint penguins somewhat overlapped and a flickering screen. I'm sure the intent of the app was to display only one penguin, which would probably get rid of the flickering and faintness. The documentation seems to indicate that this app is customized for the acx705akm, so I don't know what tweaks are needed. My understanding of frame buffers and LCD parameters is minimal. I have tried both the Samsung and ALPS mode drivers and the LCD behaves the same way (as expected). I think I will stick with the Samsung mode as the ALPS mode doesn't seem to support screen backlighting (by a quick look at the code). I'm also looking for some app or configuration to use the acx705akm as a simple ascii text display device. Is setting it us as a virtual terminal the best bet? Thanks for help. On 8/21/07, Craig Hughes <cr...@gu...> wrote: > > On Aug 21, 2007, at 1:45 PM, Peter Lu wrote: > > But I'm still using the "Samsung" FB driver, if there is such a mode, > since the Linux .config doesn't allow me to turn it off. > > > Hmm. Well, try the "Chris Dollar ALPS" choice instead. I'll see about > allowing that setting to just be turned off (ie add a "none" option). > > C > > ------------------------------------------------------------------------- > 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 > > |
From: Craig H. <cr...@gu...> - 2007-08-24 19:30:45
|
On Aug 24, 2007, at 4:04 AM, Peter Lu wrote: > My LCD is now apparently working, after adjusting some mechanical > cabling problem and deasserting SHUTDOWN. However, when I run: > > ppmv_sony692 sony_penguin.ppm > > I get three faint penguins somewhat overlapped and a flickering > screen. > I'm sure the intent of the app was to display only one penguin, which > would probably get rid of the flickering and faintness. The > documentation seems to indicate that this app is customized for the > acx705akm, so I don't know what tweaks are needed. My understanding > of frame buffers and LCD parameters is minimal. The program makes strong compiled-in assumptions about the screen resolution and bits-per-pixel depth. It basically will attempt to just stuff raw bits together based on these hardcoded params, and then dump that bitstream into /dev/fb0. If your screen is a different x-y size or uses a different bit depth than the one the program encodes for, then it won't work for you unless you modify those params in the code. iirc the x-y dimensions are #defined so it's easy to change those, but the code basically just completely assumes some bit-depth in terms of how the algorithm works -- I forget if it was 8 or 16bpp. To handle, eg, 24bpp (where maybe only some of those 24bpp are significant, like when the PXA FB controller is in 18bpp mode) you'll need to rewrite the algorithm to align the bits correctly. > I have tried both the Samsung and ALPS mode drivers and the LCD > behaves the same way (as expected). I think I will stick with the > Samsung mode as the ALPS mode doesn't seem to support > screen backlighting (by a quick look at the code). > > I'm also looking for some app or configuration to use the acx705akm > as a simple ascii text display device. Is setting it us as a virtual > terminal the best bet? Yes, using the fbcon is the easiest way to do text on an fb-backed LCD panel. C |
From: Peter L. <pl...@gm...> - 2007-08-27 20:58:08
|
Hi, The sample program ppmv_sony692 is very straight-forward. All it does is take each 3-consecutive bytes of the input .ppm file, representing RBG pixels, and pack them into 5+6+5-bit words and write them into the frame buffer. I verified the obvious things, like the size of the .ppm file, the size of the frame buffer (device), the mode of the acx705akm (works in 240x160-16) and the wiring between the LCD panel to the PXA255. The fact that the penguin displays decently indicates that basic parameters are functional. Since I'm seeing 2 penguins overlapped vertically (note penguin image is stored and displayed sideways rather than upright), it's likely that the vsync parameters are off. I've played around with the LCCR2 register, but have not managed to "lock" the vsync properly. Tweaking VSW (vertical sync pulse width) doesn't seem to do much and tweaking LPP (lines per panel) wreaks a lot of vertical havoc without getting the proper vertical lock. This exercise is like tweaking the vertical hold on old TVs. Does anyone have suggestions as to what PXA255 LCD Controller registers might be involved in getting the vertical sync right? Thanks for all help. On 8/24/07, Craig Hughes <cr...@gu...> wrote: > > On Aug 24, 2007, at 4:04 AM, Peter Lu wrote: > > > My LCD is now apparently working, after adjusting some mechanical > > cabling problem and deasserting SHUTDOWN. However, when I run: > > > > ppmv_sony692 sony_penguin.ppm > > > > I get three faint penguins somewhat overlapped and a flickering > > screen. > > I'm sure the intent of the app was to display only one penguin, which > > would probably get rid of the flickering and faintness. The > > documentation seems to indicate that this app is customized for the > > acx705akm, so I don't know what tweaks are needed. My understanding > > of frame buffers and LCD parameters is minimal. > > The program makes strong compiled-in assumptions about the screen > resolution and bits-per-pixel depth. It basically will attempt to > just stuff raw bits together based on these hardcoded params, and > then dump that bitstream into /dev/fb0. If your screen is a > different x-y size or uses a different bit depth than the one the > program encodes for, then it won't work for you unless you modify > those params in the code. iirc the x-y dimensions are #defined so > it's easy to change those, but the code basically just completely > assumes some bit-depth in terms of how the algorithm works -- I > forget if it was 8 or 16bpp. To handle, eg, 24bpp (where maybe only > some of those 24bpp are significant, like when the PXA FB controller > is in 18bpp mode) you'll need to rewrite the algorithm to align the > bits correctly. > > > I have tried both the Samsung and ALPS mode drivers and the LCD > > behaves the same way (as expected). I think I will stick with the > > Samsung mode as the ALPS mode doesn't seem to support > > screen backlighting (by a quick look at the code). > > > > I'm also looking for some app or configuration to use the acx705akm > > as a simple ascii text display device. Is setting it us as a virtual > > terminal the best bet? > > Yes, using the fbcon is the easiest way to do text on an fb-backed > LCD panel. > > C > > ------------------------------------------------------------------------- > 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 > |