From: Elvis D. <elv...@ma...> - 2009-01-12 19:31:22
|
Hi, I'm using an Overo with the summit expansion board connected to an HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" using the Overo console. How can I change this setting to 1920x160-60 ? Best regards, Elvis Dowson |
From: Koen K. <k....@st...> - 2009-01-12 20:18:47
|
On 12-01-09 20:31, Elvis Dowson wrote: > Hi, > I'm using an Overo with the summit expansion board connected to an > HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" > using the Overo console. > > How can I change this setting to 1920x160-60 ? depending on your kernel: video=omapfb:vram:6M,mode:1920x1600@60 or omapfb.mode=1920x1600MR-16@60 There's a but: the pixclock can be 86MHz maximum, which when I tried this weekend gave me 1600x1200@40Hz, you could tweak the timings a bit to get some more Hertzes, but I don't think you'll make 1920x1600. I'll leave it to Steve to comment on what DSS the overo uses by default :) regards, Koen |
From: Elvis D. <elv...@ma...> - 2009-01-12 20:52:38
|
Hi, I just got the Overo and Summit fresh out of the box, so to speak. :-) I just plugged it in and connected it to the console port and I'm able to access it just find. However, what escapes me is how I can get a graphical login screen to appear. I've heard that there is an Enlightnment desktop that's supposed to appear, but don't know how to get that started. So, not sure if I can actually get a graphical login going with my current build, or is it failing because of the display resolution not being supported with my display monitor. Typing the command on the console did not work. I'm begining to see that there's more work to be done in terms of bringing this board up that I initially thought!! I also don't have a computer that has a microSD/SD card reader, so it makes it difficult to create a bootable microSD card. I tried using the Overo itself to prepare the bootable microSD card, but got stuck at the point of formatting the microSD card because the Overo factory image does not have a mkfs.vfat utility. Best regards, Elvis On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: > On 12-01-09 20:31, Elvis Dowson wrote: >> Hi, >> I'm using an Overo with the summit expansion board connected to an >> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >> using the Overo console. >> >> How can I change this setting to 1920x160-60 ? > > depending on your kernel: > > video=omapfb:vram:6M,mode:1920x1600@60 > > or > > omapfb.mode=1920x1600MR-16@60 > > There's a but: the pixclock can be 86MHz maximum, which when I tried > this weekend gave me 1600x1200@40Hz, you could tweak the timings a bit > to get some more Hertzes, but I don't think you'll make 1920x1600. > > I'll leave it to Steve to comment on what DSS the overo uses by > default :) > > regards, > > Koen > |
From: Steve S. <sa...@gm...> - 2009-01-12 20:58:15
|
On Mon, Jan 12, 2009 at 12:18 PM, Koen Kooi <k....@st...> wrote: > On 12-01-09 20:31, Elvis Dowson wrote: >> Hi, >> I'm using an Overo with the summit expansion board connected to an >> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >> using the Overo console. >> >> How can I change this setting to 1920x160-60 ? > > depending on your kernel: > > video=omapfb:vram:6M,mode:1920x1600@60 > > or > > omapfb.mode=1920x1600MR-16@60 > > There's a but: the pixclock can be 86MHz maximum, which when I tried > this weekend gave me 1600x1200@40Hz, you could tweak the timings a bit > to get some more Hertzes, but I don't think you'll make 1920x1600. > > I'll leave it to Steve to comment on what DSS the overo uses by default :) 1920x1600@60 requires a 205.250 Mhz clock, so it is not a supported option. Steve |
From: Elvis D. <elv...@ma...> - 2009-01-12 21:01:45
|
Hi Steve, What would the correct display setting be ? At 1024x768-57 I get no output on my LCD TV. What would a workable resolution be 1368x768 at 60Hz? I'm trying to get the overo to boot and display a GUI log on screen. I just got it default from the factory. Best regards, Elvis On Jan 13, 2009, at 12:54 AM, Steve Sakoman wrote: > On Mon, Jan 12, 2009 at 12:18 PM, Koen Kooi > <k....@st...> wrote: >> On 12-01-09 20:31, Elvis Dowson wrote: >>> Hi, >>> I'm using an Overo with the summit expansion board connected >>> to an >>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >>> using the Overo console. >>> >>> How can I change this setting to 1920x160-60 ? >> >> depending on your kernel: >> >> video=omapfb:vram:6M,mode:1920x1600@60 >> >> or >> >> omapfb.mode=1920x1600MR-16@60 >> >> There's a but: the pixclock can be 86MHz maximum, which when I tried >> this weekend gave me 1600x1200@40Hz, you could tweak the timings a >> bit >> to get some more Hertzes, but I don't think you'll make 1920x1600. >> >> I'll leave it to Steve to comment on what DSS the overo uses by >> default :) > > 1920x1600@60 requires a 205.250 Mhz clock, so it is not a supported > option. > > Steve > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2009-01-12 23:37:47
|
On Mon, Jan 12, 2009 at 12:52 PM, Elvis Dowson <elv...@ma...> wrote: > Hi, > I just got the Overo and Summit fresh out of the box, so to > speak. :-) I just plugged it in and connected it to the console port > and I'm able to access it just find. > > However, what escapes me is how I can get a graphical login screen to > appear. I've heard that there is an Enlightnment desktop that's > supposed to appear, but don't know how to get that started. As shipped from the factory the display resolution is set to 1024 x 768 @ 60hz. This works with most LCD computer monitors (note that for many monitors you will need to use an hdmi to dvi-d adaptor) As you discovered, many LCD *TV's* do not support this resolution. Do you have an LCD computer monitor you can try? > So, not sure if I can actually get a graphical login going with my > current build, or is it failing because of the display resolution not > being supported with my display monitor. Typing the command on the > console did not work. The OMAP3 video driver does not currently support changing the resolution with fbset. More recent versions of u-boot and kernel support changing the resolution with a kernel command line option, but only for a limited set of options. This is done using a u-boot environment variable. If you type the u-boot printenv command you will see this line in the output: videomode=1024x768@60,vxres=1024,vyres=768 You can use the setenv command to change the videomode variable to one of the .name options you find in the omapfb_main.c video_modes table: static struct video_mode video_modes[] __initdata = { { /* 640 x 480 @ 60 Hz Reduced blanking VESA CVT 0.31M3-R */ .name = "640x480@60", .x_res = 640, .y_res = 480, .hfp = 48, .hsw = 32, .hbp = 80, .vfp = 3, .vsw = 4, .vbp = 7, .pixel_clock = 23500, }, { /* 800 x 600 @ 60 Hz Reduced blanking VESA CVT 0.48M3-R */ .name = "800x600@60", .x_res = 800, .y_res = 600, .hfp = 48, .hsw = 32, .hbp = 80, .vfp = 3, .vsw = 4, .vbp = 11, .pixel_clock = 35500, }, { /* 1024 x 768 @ 60 Hz Reduced blanking VESA CVT 0.79M3-R */ .name = "1024x768@60", .x_res = 1024, .y_res = 768, .hfp = 48, .hsw = 32, .hbp = 80, .vfp = 3, .vsw = 4, .vbp = 15, .pixel_clock = 56000, }, { /* 1280 x 720 @ 60 Hz Reduced blanking VESA CVT 0.92M9-R */ .name = "1280x720@60", .x_res = 1280, .y_res = 720, .hfp = 48, .hsw = 32, .hbp = 80, .vfp = 3, .vsw = 5, .vbp = 13, .pixel_clock = 64000, }, { /* 720 x 480 @ 60 Hz CEA-861 Format 3 */ .name = "480p60", .x_res = 720, .y_res = 480, .hfp = 16, .hsw = 62, .hbp = 60, .vfp = 9, .vsw = 6, .vbp = 30, .pixel_clock = 27027, }, { /* 720 x 576 @ 60 Hz CEA-861 Format 18 */ .name = "576p50", .x_res = 720, .y_res = 576, .hfp = 12, .hsw = 64, .hbp = 68, .vfp = 5, .vsw = 5, .vbp = 39, .pixel_clock = 27000, }, { /* 1280 x 720 @ 50 Hz CEA-861B Format 19 */ .name = "720p50", .x_res = 1280, .y_res = 720, .hfp = 440, .hsw = 40, .hbp = 220, .vfp = 20, .vsw = 5, .vbp = 5, .pixel_clock = 74250, }, { /* 1280 x 720 @ 60 Hz CEA-861B Format 4 */ .name = "720p60", .x_res = 1280, .y_res = 720, .hfp = 110, .hsw = 40, .hbp = 220, .vfp = 20, .vsw = 5, .vbp = 5, .pixel_clock = 74250, }, { /* 1920 x 1080 @ 24 Hz CEA-861B Format 32 */ .name = "1080p24", .x_res = 1920, .y_res = 1080, .hfp = 148, .hsw = 44, .hbp = 638, .vfp = 36, .vsw = 5, .vbp = 4, .pixel_clock = 74250, }, { /* 1920 x 1080 @ 25 Hz CEA-861B Format 33 */ .name = "1080p25", .x_res = 1920, .y_res = 1080, .hfp = 148, .hsw = 44, .hbp = 528, .vfp = 36, .vsw = 5, .vbp = 4, .pixel_clock = 74250, }, { /* 1920 x 1080 @ 30 Hz CEA-861B Format 34 */ .name = "1080p30", .x_res = 1920, .y_res = 1080, .hfp = 148, .hsw = 44, .hbp = 88, .vfp = 36, .vsw = 5, .vbp = 4, .pixel_clock = 74250, }, }; > I also don't have a computer that has a microSD/SD card reader, so it > makes it difficult to create a bootable microSD card. I tried using > the Overo itself to prepare the bootable microSD card, but got stuck > at the point of formatting the microSD card because the Overo factory > image does not have a mkfs.vfat utility. Time to buy a cheap ($10-ish) USB card reader! Newer images do contain vfat, but obviously this is a chicken/egg problem for you. I recommend a shopping trip :-) Steve > On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: > >> On 12-01-09 20:31, Elvis Dowson wrote: >>> Hi, >>> I'm using an Overo with the summit expansion board connected to an >>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >>> using the Overo console. >>> >>> How can I change this setting to 1920x160-60 ? >> >> depending on your kernel: >> >> video=omapfb:vram:6M,mode:1920x1600@60 >> >> or >> >> omapfb.mode=1920x1600MR-16@60 >> >> There's a but: the pixclock can be 86MHz maximum, which when I tried >> this weekend gave me 1600x1200@40Hz, you could tweak the timings a bit >> to get some more Hertzes, but I don't think you'll make 1920x1600. >> >> I'll leave it to Steve to comment on what DSS the overo uses by >> default :) >> >> regards, >> >> Koen >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Elvis D. <elv...@ma...> - 2009-01-13 00:24:40
|
Hi Steve, I type setenv at the u-boot prompt but there were no environment variables defined for the system. So at the u-boot prompt I type setenv videomode "800x600@60" setenv vxres 800 setenv vyres 600 and typed boot and it booted. However, when I type fbset, it still reports mode "1024x768-58" Setting the environment variables did not impact it. Best regards, Elvis |
From: Chris D. <chr...@gm...> - 2009-01-13 00:35:05
|
Hi Elvis, You need to have the videomode string and reses on one line like the variable showed when you did a printenv, so it would be: setenv videomode 800x600@60,vxres=800,vyres=600 Chris On Mon, Jan 12, 2009 at 5:24 PM, Elvis Dowson <elv...@ma...> wrote: > Hi Steve, > I type setenv at the u-boot prompt but there were no environment > variables defined for the system. > > So at the u-boot prompt I type > setenv videomode "800x600@60" > setenv vxres 800 > setenv vyres 600 > > and typed boot and it booted. However, when I type fbset, it still > reports mode "1024x768-58" > > Setting the environment variables did not impact it. > > Best regards, > > Elvis > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: TSkutt <tim...@gm...> - 2009-02-01 22:31:12
|
Hi, I seem to be striking out with the video mode guidance and could use a little help. I've followed the advice of this thread and used both the "setenv videomode xxxxx" method as well as modifying the nandbootargs, but with no success. I've tried various video modes with two different monitors (a 19" HDMI panel and a 22" DVI panel), but the kernel seems to ignore everything I throw at it and defaults to 1024x768. My hardware is Overo/Summit and I have run both the v0.90 image as well as a recently built image. What am I missing? Background - I would love to get 720p output on an HDMI monitor (in preparation for using with display hardware that only supports HDTV style resolutions), but I'm suspicious that this will be a failing endeavour. My suspicions are inspired by the BeagleBoard documentation that clearly states you shouldn't plan on connecting an HDMI monitor to the BeagleBoard's HDMI port. Since the video circuits appear to be identical from the schematics, I'm guessing that the same disclaimer should apply to the Summit as well. Is this correct? Thanks, Tim Chris Dollar wrote: > > Hi Elvis, > > You need to have the videomode string and reses on one line like the > variable showed when you did a printenv, so it would be: > setenv videomode 800x600@60,vxres=800,vyres=600 > > Chris > > On Mon, Jan 12, 2009 at 5:24 PM, Elvis Dowson <elv...@ma...> > wrote: >> Hi Steve, >> I type setenv at the u-boot prompt but there were >> no environment >> variables defined for the system. >> >> So at the u-boot prompt I type >> setenv videomode "800x600@60" >> setenv vxres 800 >> setenv vyres 600 >> >> and typed boot and it booted. However, when I type fbset, it still >> reports mode "1024x768-58" >> >> Setting the environment variables did not impact it. >> >> Best regards, >> >> Elvis >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p21780646.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: TSkutt <tim...@gm...> - 2009-02-09 20:42:15
|
Thanks GM, you were right on target. Once I started modifying the kernel configuration, I started getting the resolutions I was looking for (kind of - see below). I used the "fbset -i" method of verifying the video settings. The issue I currently have is that regardless of what I set the video mode to, the driver wants to set up a 72 MHz pixel clock. My HD equipment isn't happy with that because the "standard" pixel clock for 720p video is 74.25 MHz. My flat panel LCD monitor with both a VGA and HDMI input recognizes the 1280x720 format, but when I plug the HDMI cable into some HD equipment expressly designed for HDTV I get nothing. To me, it looks like a problem with the OMAP (TI CPU) display driver. The TI reference manual says the display subsystem is able to drive the correct 720p pixel clock. Before I go deeper with this, can anyone share some wisdom on why this is happening? Am I missing something? Thanks, Tim For reference, here's what I got for the different modes: Using 720p50 I get: mode "1280x720-48" # D: 72.005 MHz, H: 36.366 kHz, V: 48.488 Hz geometry 1280 720 1280 720 16 timings 13888 440 220 20 5 40 5 rgba 5/11,6/5,5/0,0/0 endmode Using 720p60 I get: mode "1280x720-58" # D: 72.005 MHz, H: 43.639 kHz, V: 58.186 Hz geometry 1280 720 1280 720 16 timings 13888 110 220 20 5 40 5 rgba 5/11,6/5,5/0,0/0 endmode Using 1080p24 I get: mode "1920x1080-23" # D: 72.005 MHz, H: 26.183 kHz, V: 23.274 Hz geometry 1920 1080 1920 1080 16 timings 13888 148 638 36 4 44 5 rgba 5/11,6/5,5/0,0/0 endmode Using 1080p25 I get: mode "1920x1080-24" # D: 72.005 MHz, H: 27.274 kHz, V: 24.244 Hz geometry 1920 1080 1920 1080 16 timings 13888 148 528 36 4 44 5 rgba 5/11,6/5,5/0,0/0 endmode Using 1080p30 I get: mode "1920x1080-29" # D: 72.005 MHz, H: 32.729 kHz, V: 29.093 Hz geometry 1920 1080 1920 1080 16 timings 13888 148 88 36 4 44 5 rgba 5/11,6/5,5/0,0/0 endmode gnmckinney wrote: > > > > TSkutt wrote: >> >> Hi, >> >> I seem to be striking out with the video mode guidance and could use a >> little help. I've followed the advice of this thread and used both the >> "setenv videomode xxxxx" method as well as modifying the nandbootargs, >> but with no success. I've tried various video modes with two different >> monitors (a 19" HDMI panel and a 22" DVI panel), but the kernel seems to >> ignore everything I throw at it and defaults to 1024x768. >> >> My hardware is Overo/Summit and I have run both the v0.90 image as well >> as a recently built image. >> >> What am I missing? >> >> Background - I would love to get 720p output on an HDMI monitor (in >> preparation for using with display hardware that only supports HDTV style >> resolutions), but I'm suspicious that this will be a failing endeavour. >> My suspicions are inspired by the BeagleBoard documentation that clearly >> states you shouldn't plan on connecting an HDMI monitor to the >> BeagleBoard's HDMI port. Since the video circuits appear to be identical >> from the schematics, I'm guessing that the same disclaimer should apply >> to the Summit as well. Is this correct? >> >> >> Thanks, >> >> Tim >> >> >> > > You may want to check the kernel config file (defconfig) as it looks like > the mouse_dev is set to 1024X768 and the CONFIG_FB_OMAP_VIDO_MODE variable > is set to 1024X768@60. > > I am not positive but suspect this is "hardcoding" the video mode settings > within the kernel - I could be wrong though (not the first time!). > > gm... > > -- View this message in context: http://www.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p21921493.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Koen K. <k....@st...> - 2009-02-09 23:05:06
|
On 09-02-09 21:42, TSkutt wrote: > Thanks GM, you were right on target. Once I started modifying the kernel > configuration, I started getting the resolutions I was looking for (kind of > - see below). I used the "fbset -i" method of verifying the video settings. > > The issue I currently have is that regardless of what I set the video mode > to, the driver wants to set up a 72 MHz pixel clock. My HD equipment isn't > happy with that because the "standard" pixel clock for 720p video is 74.25 > MHz. My flat panel LCD monitor with both a VGA and HDMI input recognizes > the 1280x720 format, but when I plug the HDMI cable into some HD equipment > expressly designed for HDTV I get nothing. > > To me, it looks like a problem with the OMAP (TI CPU) display driver. The > TI reference manual says the display subsystem is able to drive the correct > 720p pixel clock. > > Before I go deeper with this, can anyone share some wisdom on why this is > happening? Am I missing something? There's a new display driver (nicknamed DSS2), which fixes all this. Steve is working on it to get it working on overo. regards, Koen |
From: kardon33 <Ad...@il...> - 2009-07-13 20:34:48
|
Chris Dollar wrote: > > Hi Elvis, > > You need to have the videomode string and reses on one line like the > variable showed when you did a printenv, so it would be: > setenv videomode 800x600@60,vxres=800,vyres=600 > > Chris > If I wanted to set my display at to 800x600@60 with vertical sync set to negative I am under the impression I would set the environment variable dvimode with: "setenv dvimode 800x600MR-16@60,vsync=low". Is that correct? Is there a way to confirm that the Vertical sync is set to low? -- View this message in context: http://www.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p24468840.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: gnmckinney <gar...@gm...> - 2009-02-03 12:32:30
|
TSkutt wrote: > > Hi, > > I seem to be striking out with the video mode guidance and could use a > little help. I've followed the advice of this thread and used both the > "setenv videomode xxxxx" method as well as modifying the nandbootargs, but > with no success. I've tried various video modes with two different > monitors (a 19" HDMI panel and a 22" DVI panel), but the kernel seems to > ignore everything I throw at it and defaults to 1024x768. > > My hardware is Overo/Summit and I have run both the v0.90 image as well as > a recently built image. > > What am I missing? > > Background - I would love to get 720p output on an HDMI monitor (in > preparation for using with display hardware that only supports HDTV style > resolutions), but I'm suspicious that this will be a failing endeavour. > My suspicions are inspired by the BeagleBoard documentation that clearly > states you shouldn't plan on connecting an HDMI monitor to the > BeagleBoard's HDMI port. Since the video circuits appear to be identical > from the schematics, I'm guessing that the same disclaimer should apply to > the Summit as well. Is this correct? > > > Thanks, > > Tim > > Chris Dollar wrote: >> >> Hi Elvis, >> >> You need to have the videomode string and reses on one line like the >> variable showed when you did a printenv, so it would be: >> setenv videomode 800x600@60,vxres=800,vyres=600 >> >> Chris >> >> On Mon, Jan 12, 2009 at 5:24 PM, Elvis Dowson <elv...@ma...> >> wrote: >>> Hi Steve, >>> I type setenv at the u-boot prompt but there were >>> no environment >>> variables defined for the system. >>> >>> So at the u-boot prompt I type >>> setenv videomode "800x600@60" >>> setenv vxres 800 >>> setenv vyres 600 >>> >>> and typed boot and it booted. However, when I type fbset, it still >>> reports mode "1024x768-58" >>> >>> Setting the environment variables did not impact it. >>> >>> Best regards, >>> >>> Elvis >>> >> > > You may want to check the kernel config file (defconfig) as it looks like the mouse_dev is set to 1024X768 and the CONFIG_FB_OMAP_VIDO_MODE variable is set to 1024X768@60. I am not positive but suspect this is "hardcoding" the video mode settings within the kernel - I could be wrong though (not the first time!). gm... -- View this message in context: http://www.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p21808975.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Vidya M. <vid...@gm...> - 2010-07-26 19:29:48
|
Hello Steve, I am trying to get video output on HDTV and was following this discussion. When I do a printenv at uboot, I see an env variable called "dvimode" dvimode=1024x768MR-16@60 I tried changing this to different modes by using the setenv command eg: setenv dvimode 1920x1080@30 However, when I boot I am getting the following error: Starting PVR omaplfb: OMAPLFB_Init: OMAPLFBInit failed FATAL: Error inserting omaplfb (/lib/modules/2.6.33/kernel/drivers/gpu/pvr/omaplfb.ko): No such device I was wondering if it is because this resolution is not supported? Where can I find this file omapfb_main.c - so that I can check the supported resolutions. Is the resolution 1920x1080@60 not supported yet? Thanks Vidya. sakoman wrote: > > On Mon, Jan 12, 2009 at 12:52 PM, Elvis Dowson <elv...@ma...> > wrote: >> Hi, >> I just got the Overo and Summit fresh out of the box, so to >> speak. :-) I just plugged it in and connected it to the console port >> and I'm able to access it just find. >> >> However, what escapes me is how I can get a graphical login screen to >> appear. I've heard that there is an Enlightnment desktop that's >> supposed to appear, but don't know how to get that started. > > As shipped from the factory the display resolution is set to 1024 x > 768 @ 60hz. This works with most LCD computer monitors (note that for > many monitors you will need to use an hdmi to dvi-d adaptor) > > As you discovered, many LCD *TV's* do not support this resolution. Do > you have an LCD computer monitor you can try? > >> So, not sure if I can actually get a graphical login going with my >> current build, or is it failing because of the display resolution not >> being supported with my display monitor. Typing the command on the >> console did not work. > > The OMAP3 video driver does not currently support changing the > resolution with fbset. > > More recent versions of u-boot and kernel support changing the > resolution with a kernel command line option, but only for a limited > set of options. > > This is done using a u-boot environment variable. If you type the > u-boot printenv command you will see this line in the output: > > videomode=1024x768@60,vxres=1024,vyres=768 > > You can use the setenv command to change the videomode variable to one > of the .name options you find in the omapfb_main.c video_modes table: > > static struct video_mode video_modes[] __initdata = { > { > /* 640 x 480 @ 60 Hz Reduced blanking VESA CVT 0.31M3-R */ > .name = "640x480@60", > .x_res = 640, > .y_res = 480, > .hfp = 48, > .hsw = 32, > .hbp = 80, > .vfp = 3, > .vsw = 4, > .vbp = 7, > .pixel_clock = 23500, > }, > { > /* 800 x 600 @ 60 Hz Reduced blanking VESA CVT 0.48M3-R */ > .name = "800x600@60", > .x_res = 800, > .y_res = 600, > .hfp = 48, > .hsw = 32, > .hbp = 80, > .vfp = 3, > .vsw = 4, > .vbp = 11, > .pixel_clock = 35500, > }, > { > /* 1024 x 768 @ 60 Hz Reduced blanking VESA CVT 0.79M3-R */ > .name = "1024x768@60", > .x_res = 1024, > .y_res = 768, > .hfp = 48, > .hsw = 32, > .hbp = 80, > .vfp = 3, > .vsw = 4, > .vbp = 15, > .pixel_clock = 56000, > }, > { > /* 1280 x 720 @ 60 Hz Reduced blanking VESA CVT 0.92M9-R */ > .name = "1280x720@60", > .x_res = 1280, > .y_res = 720, > .hfp = 48, > .hsw = 32, > .hbp = 80, > .vfp = 3, > .vsw = 5, > .vbp = 13, > .pixel_clock = 64000, > }, > { > /* 720 x 480 @ 60 Hz CEA-861 Format 3 */ > .name = "480p60", > .x_res = 720, > .y_res = 480, > .hfp = 16, > .hsw = 62, > .hbp = 60, > .vfp = 9, > .vsw = 6, > .vbp = 30, > .pixel_clock = 27027, > }, > { > /* 720 x 576 @ 60 Hz CEA-861 Format 18 */ > .name = "576p50", > .x_res = 720, > .y_res = 576, > .hfp = 12, > .hsw = 64, > .hbp = 68, > .vfp = 5, > .vsw = 5, > .vbp = 39, > .pixel_clock = 27000, > }, > { > /* 1280 x 720 @ 50 Hz CEA-861B Format 19 */ > .name = "720p50", > .x_res = 1280, > .y_res = 720, > .hfp = 440, > .hsw = 40, > .hbp = 220, > .vfp = 20, > .vsw = 5, > .vbp = 5, > .pixel_clock = 74250, > }, > { > /* 1280 x 720 @ 60 Hz CEA-861B Format 4 */ > .name = "720p60", > .x_res = 1280, > .y_res = 720, > .hfp = 110, > .hsw = 40, > .hbp = 220, > .vfp = 20, > .vsw = 5, > .vbp = 5, > .pixel_clock = 74250, > }, > { > /* 1920 x 1080 @ 24 Hz CEA-861B Format 32 */ > .name = "1080p24", > .x_res = 1920, > .y_res = 1080, > .hfp = 148, > .hsw = 44, > .hbp = 638, > .vfp = 36, > .vsw = 5, > .vbp = 4, > .pixel_clock = 74250, > }, > { > /* 1920 x 1080 @ 25 Hz CEA-861B Format 33 */ > .name = "1080p25", > .x_res = 1920, > .y_res = 1080, > .hfp = 148, > .hsw = 44, > .hbp = 528, > .vfp = 36, > .vsw = 5, > .vbp = 4, > .pixel_clock = 74250, > }, > { > /* 1920 x 1080 @ 30 Hz CEA-861B Format 34 */ > .name = "1080p30", > .x_res = 1920, > .y_res = 1080, > .hfp = 148, > .hsw = 44, > .hbp = 88, > .vfp = 36, > .vsw = 5, > .vbp = 4, > .pixel_clock = 74250, > }, > }; > >> I also don't have a computer that has a microSD/SD card reader, so it >> makes it difficult to create a bootable microSD card. I tried using >> the Overo itself to prepare the bootable microSD card, but got stuck >> at the point of formatting the microSD card because the Overo factory >> image does not have a mkfs.vfat utility. > > Time to buy a cheap ($10-ish) USB card reader! > > Newer images do contain vfat, but obviously this is a chicken/egg > problem for you. I recommend a shopping trip :-) > > Steve > > >> On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: >> >>> On 12-01-09 20:31, Elvis Dowson wrote: >>>> Hi, >>>> I'm using an Overo with the summit expansion board connected to an >>>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >>>> using the Overo console. >>>> >>>> How can I change this setting to 1920x160-60 ? >>> >>> depending on your kernel: >>> >>> video=omapfb:vram:6M,mode:1920x1600@60 >>> >>> or >>> >>> omapfb.mode=1920x1600MR-16@60 >>> >>> There's a but: the pixclock can be 86MHz maximum, which when I tried >>> this weekend gave me 1600x1200@40Hz, you could tweak the timings a bit >>> to get some more Hertzes, but I don't think you'll make 1920x1600. >>> >>> I'll leave it to Steve to comment on what DSS the overo uses by >>> default :) >>> >>> regards, >>> >>> Koen >>> >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29269881.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: J. L. <vwy...@gm...> - 2010-07-26 19:33:38
|
I was never able to get the HDMI to work with my TV, I have seen and heard mixed results with doing that. Do remember the signal coming out is only digital and is a DVI signal not a true HDMI signal. I gave up trying on my philips and went a different route for when I needed a larger screen. I know this doesnt answer your question but figured I would throw it out there On Mon, Jul 26, 2010 at 12:29 PM, Vidya Menon <vid...@gm...> wrote: > > Hello Steve, > > I am trying to get video output on HDTV and was following this discussion. > When I do a printenv at uboot, I see an env variable called "dvimode" > > dvimode=1024x768MR-16@60 > > I tried changing this to different modes by using the setenv command > > eg: setenv dvimode 1920x1080@30 > > However, when I boot I am getting the following error: > Starting PVR > omaplfb: OMAPLFB_Init: OMAPLFBInit failed > FATAL: Error inserting omaplfb > (/lib/modules/2.6.33/kernel/drivers/gpu/pvr/omaplfb.ko): No such device > > I was wondering if it is because this resolution is not supported? Where can > I find this file omapfb_main.c - so that I can check the supported > resolutions. > > Is the resolution 1920x1080@60 not supported yet? > > Thanks > Vidya. > > > sakoman wrote: >> >> On Mon, Jan 12, 2009 at 12:52 PM, Elvis Dowson <elv...@ma...> >> wrote: >>> Hi, >>> I just got the Overo and Summit fresh out of the box, so to >>> speak. :-) I just plugged it in and connected it to the console port >>> and I'm able to access it just find. >>> >>> However, what escapes me is how I can get a graphical login screen to >>> appear. I've heard that there is an Enlightnment desktop that's >>> supposed to appear, but don't know how to get that started. >> >> As shipped from the factory the display resolution is set to 1024 x >> 768 @ 60hz. This works with most LCD computer monitors (note that for >> many monitors you will need to use an hdmi to dvi-d adaptor) >> >> As you discovered, many LCD *TV's* do not support this resolution. Do >> you have an LCD computer monitor you can try? >> >>> So, not sure if I can actually get a graphical login going with my >>> current build, or is it failing because of the display resolution not >>> being supported with my display monitor. Typing the command on the >>> console did not work. >> >> The OMAP3 video driver does not currently support changing the >> resolution with fbset. >> >> More recent versions of u-boot and kernel support changing the >> resolution with a kernel command line option, but only for a limited >> set of options. >> >> This is done using a u-boot environment variable. If you type the >> u-boot printenv command you will see this line in the output: >> >> videomode=1024x768@60,vxres=1024,vyres=768 >> >> You can use the setenv command to change the videomode variable to one >> of the .name options you find in the omapfb_main.c video_modes table: >> >> static struct video_mode video_modes[] __initdata = { >> { >> /* 640 x 480 @ 60 Hz Reduced blanking VESA CVT 0.31M3-R */ >> .name = "640x480@60", >> .x_res = 640, >> .y_res = 480, >> .hfp = 48, >> .hsw = 32, >> .hbp = 80, >> .vfp = 3, >> .vsw = 4, >> .vbp = 7, >> .pixel_clock = 23500, >> }, >> { >> /* 800 x 600 @ 60 Hz Reduced blanking VESA CVT 0.48M3-R */ >> .name = "800x600@60", >> .x_res = 800, >> .y_res = 600, >> .hfp = 48, >> .hsw = 32, >> .hbp = 80, >> .vfp = 3, >> .vsw = 4, >> .vbp = 11, >> .pixel_clock = 35500, >> }, >> { >> /* 1024 x 768 @ 60 Hz Reduced blanking VESA CVT 0.79M3-R */ >> .name = "1024x768@60", >> .x_res = 1024, >> .y_res = 768, >> .hfp = 48, >> .hsw = 32, >> .hbp = 80, >> .vfp = 3, >> .vsw = 4, >> .vbp = 15, >> .pixel_clock = 56000, >> }, >> { >> /* 1280 x 720 @ 60 Hz Reduced blanking VESA CVT 0.92M9-R */ >> .name = "1280x720@60", >> .x_res = 1280, >> .y_res = 720, >> .hfp = 48, >> .hsw = 32, >> .hbp = 80, >> .vfp = 3, >> .vsw = 5, >> .vbp = 13, >> .pixel_clock = 64000, >> }, >> { >> /* 720 x 480 @ 60 Hz CEA-861 Format 3 */ >> .name = "480p60", >> .x_res = 720, >> .y_res = 480, >> .hfp = 16, >> .hsw = 62, >> .hbp = 60, >> .vfp = 9, >> .vsw = 6, >> .vbp = 30, >> .pixel_clock = 27027, >> }, >> { >> /* 720 x 576 @ 60 Hz CEA-861 Format 18 */ >> .name = "576p50", >> .x_res = 720, >> .y_res = 576, >> .hfp = 12, >> .hsw = 64, >> .hbp = 68, >> .vfp = 5, >> .vsw = 5, >> .vbp = 39, >> .pixel_clock = 27000, >> }, >> { >> /* 1280 x 720 @ 50 Hz CEA-861B Format 19 */ >> .name = "720p50", >> .x_res = 1280, >> .y_res = 720, >> .hfp = 440, >> .hsw = 40, >> .hbp = 220, >> .vfp = 20, >> .vsw = 5, >> .vbp = 5, >> .pixel_clock = 74250, >> }, >> { >> /* 1280 x 720 @ 60 Hz CEA-861B Format 4 */ >> .name = "720p60", >> .x_res = 1280, >> .y_res = 720, >> .hfp = 110, >> .hsw = 40, >> .hbp = 220, >> .vfp = 20, >> .vsw = 5, >> .vbp = 5, >> .pixel_clock = 74250, >> }, >> { >> /* 1920 x 1080 @ 24 Hz CEA-861B Format 32 */ >> .name = "1080p24", >> .x_res = 1920, >> .y_res = 1080, >> .hfp = 148, >> .hsw = 44, >> .hbp = 638, >> .vfp = 36, >> .vsw = 5, >> .vbp = 4, >> .pixel_clock = 74250, >> }, >> { >> /* 1920 x 1080 @ 25 Hz CEA-861B Format 33 */ >> .name = "1080p25", >> .x_res = 1920, >> .y_res = 1080, >> .hfp = 148, >> .hsw = 44, >> .hbp = 528, >> .vfp = 36, >> .vsw = 5, >> .vbp = 4, >> .pixel_clock = 74250, >> }, >> { >> /* 1920 x 1080 @ 30 Hz CEA-861B Format 34 */ >> .name = "1080p30", >> .x_res = 1920, >> .y_res = 1080, >> .hfp = 148, >> .hsw = 44, >> .hbp = 88, >> .vfp = 36, >> .vsw = 5, >> .vbp = 4, >> .pixel_clock = 74250, >> }, >> }; >> >>> I also don't have a computer that has a microSD/SD card reader, so it >>> makes it difficult to create a bootable microSD card. I tried using >>> the Overo itself to prepare the bootable microSD card, but got stuck >>> at the point of formatting the microSD card because the Overo factory >>> image does not have a mkfs.vfat utility. >> >> Time to buy a cheap ($10-ish) USB card reader! >> >> Newer images do contain vfat, but obviously this is a chicken/egg >> problem for you. I recommend a shopping trip :-) >> >> Steve >> >> >>> On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: >>> >>>> On 12-01-09 20:31, Elvis Dowson wrote: >>>>> Hi, >>>>> I'm using an Overo with the summit expansion board connected to an >>>>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >>>>> using the Overo console. >>>>> >>>>> How can I change this setting to 1920x160-60 ? >>>> >>>> depending on your kernel: >>>> >>>> video=omapfb:vram:6M,mode:1920x1600@60 >>>> >>>> or >>>> >>>> omapfb.mode=1920x1600MR-16@60 >>>> >>>> There's a but: the pixclock can be 86MHz maximum, which when I tried >>>> this weekend gave me 1600x1200@40Hz, you could tweak the timings a bit >>>> to get some more Hertzes, but I don't think you'll make 1920x1600. >>>> >>>> I'll leave it to Steve to comment on what DSS the overo uses by >>>> default :) >>>> >>>> regards, >>>> >>>> Koen >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by: >>> SourcForge Community >>> SourceForge wants to tell your story. >>> http://p.sf.net/sfu/sf-spreadtheword >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- > View this message in context: http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29269881.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Robert V. IV <ro...@io...> - 2010-07-26 19:32:26
|
Hi Vidya, I had no trouble with 1280x720MR-16@60 (720p) Robert On Mon, Jul 26, 2010 at 3:29 PM, Vidya Menon <vid...@gm...> wrote: > > Hello Steve, > > I am trying to get video output on HDTV and was following this discussion. > When I do a printenv at uboot, I see an env variable called "dvimode" > > dvimode=1024x768MR-16@60 > > I tried changing this to different modes by using the setenv command > > eg: setenv dvimode 1920x1080@30 > > However, when I boot I am getting the following error: > Starting PVR > omaplfb: OMAPLFB_Init: OMAPLFBInit failed > FATAL: Error inserting omaplfb > (/lib/modules/2.6.33/kernel/drivers/gpu/pvr/omaplfb.ko): No such device > > I was wondering if it is because this resolution is not supported? Where can > I find this file omapfb_main.c - so that I can check the supported > resolutions. > > Is the resolution 1920x1080@60 not supported yet? > > Thanks > Vidya. > > > sakoman wrote: >> >> On Mon, Jan 12, 2009 at 12:52 PM, Elvis Dowson <elv...@ma...> >> wrote: >>> Hi, >>> I just got the Overo and Summit fresh out of the box, so to >>> speak. :-) I just plugged it in and connected it to the console port >>> and I'm able to access it just find. >>> >>> However, what escapes me is how I can get a graphical login screen to >>> appear. I've heard that there is an Enlightnment desktop that's >>> supposed to appear, but don't know how to get that started. >> >> As shipped from the factory the display resolution is set to 1024 x >> 768 @ 60hz. This works with most LCD computer monitors (note that for >> many monitors you will need to use an hdmi to dvi-d adaptor) >> >> As you discovered, many LCD *TV's* do not support this resolution. Do >> you have an LCD computer monitor you can try? >> >>> So, not sure if I can actually get a graphical login going with my >>> current build, or is it failing because of the display resolution not >>> being supported with my display monitor. Typing the command on the >>> console did not work. >> >> The OMAP3 video driver does not currently support changing the >> resolution with fbset. >> >> More recent versions of u-boot and kernel support changing the >> resolution with a kernel command line option, but only for a limited >> set of options. >> >> This is done using a u-boot environment variable. If you type the >> u-boot printenv command you will see this line in the output: >> >> videomode=1024x768@60,vxres=1024,vyres=768 >> >> You can use the setenv command to change the videomode variable to one >> of the .name options you find in the omapfb_main.c video_modes table: >> >> static struct video_mode video_modes[] __initdata = { >> { >> /* 640 x 480 @ 60 Hz Reduced blanking VESA CVT 0.31M3-R */ >> .name = "640x480@60", >> .x_res = 640, >> .y_res = 480, >> .hfp = 48, >> .hsw = 32, >> .hbp = 80, >> .vfp = 3, >> .vsw = 4, >> .vbp = 7, >> .pixel_clock = 23500, >> }, >> { >> /* 800 x 600 @ 60 Hz Reduced blanking VESA CVT 0.48M3-R */ >> .name = "800x600@60", >> .x_res = 800, >> .y_res = 600, >> .hfp = 48, >> .hsw = 32, >> .hbp = 80, >> .vfp = 3, >> .vsw = 4, >> .vbp = 11, >> .pixel_clock = 35500, >> }, >> { >> /* 1024 x 768 @ 60 Hz Reduced blanking VESA CVT 0.79M3-R */ >> .name = "1024x768@60", >> .x_res = 1024, >> .y_res = 768, >> .hfp = 48, >> .hsw = 32, >> .hbp = 80, >> .vfp = 3, >> .vsw = 4, >> .vbp = 15, >> .pixel_clock = 56000, >> }, >> { >> /* 1280 x 720 @ 60 Hz Reduced blanking VESA CVT 0.92M9-R */ >> .name = "1280x720@60", >> .x_res = 1280, >> .y_res = 720, >> .hfp = 48, >> .hsw = 32, >> .hbp = 80, >> .vfp = 3, >> .vsw = 5, >> .vbp = 13, >> .pixel_clock = 64000, >> }, >> { >> /* 720 x 480 @ 60 Hz CEA-861 Format 3 */ >> .name = "480p60", >> .x_res = 720, >> .y_res = 480, >> .hfp = 16, >> .hsw = 62, >> .hbp = 60, >> .vfp = 9, >> .vsw = 6, >> .vbp = 30, >> .pixel_clock = 27027, >> }, >> { >> /* 720 x 576 @ 60 Hz CEA-861 Format 18 */ >> .name = "576p50", >> .x_res = 720, >> .y_res = 576, >> .hfp = 12, >> .hsw = 64, >> .hbp = 68, >> .vfp = 5, >> .vsw = 5, >> .vbp = 39, >> .pixel_clock = 27000, >> }, >> { >> /* 1280 x 720 @ 50 Hz CEA-861B Format 19 */ >> .name = "720p50", >> .x_res = 1280, >> .y_res = 720, >> .hfp = 440, >> .hsw = 40, >> .hbp = 220, >> .vfp = 20, >> .vsw = 5, >> .vbp = 5, >> .pixel_clock = 74250, >> }, >> { >> /* 1280 x 720 @ 60 Hz CEA-861B Format 4 */ >> .name = "720p60", >> .x_res = 1280, >> .y_res = 720, >> .hfp = 110, >> .hsw = 40, >> .hbp = 220, >> .vfp = 20, >> .vsw = 5, >> .vbp = 5, >> .pixel_clock = 74250, >> }, >> { >> /* 1920 x 1080 @ 24 Hz CEA-861B Format 32 */ >> .name = "1080p24", >> .x_res = 1920, >> .y_res = 1080, >> .hfp = 148, >> .hsw = 44, >> .hbp = 638, >> .vfp = 36, >> .vsw = 5, >> .vbp = 4, >> .pixel_clock = 74250, >> }, >> { >> /* 1920 x 1080 @ 25 Hz CEA-861B Format 33 */ >> .name = "1080p25", >> .x_res = 1920, >> .y_res = 1080, >> .hfp = 148, >> .hsw = 44, >> .hbp = 528, >> .vfp = 36, >> .vsw = 5, >> .vbp = 4, >> .pixel_clock = 74250, >> }, >> { >> /* 1920 x 1080 @ 30 Hz CEA-861B Format 34 */ >> .name = "1080p30", >> .x_res = 1920, >> .y_res = 1080, >> .hfp = 148, >> .hsw = 44, >> .hbp = 88, >> .vfp = 36, >> .vsw = 5, >> .vbp = 4, >> .pixel_clock = 74250, >> }, >> }; >> >>> I also don't have a computer that has a microSD/SD card reader, so it >>> makes it difficult to create a bootable microSD card. I tried using >>> the Overo itself to prepare the bootable microSD card, but got stuck >>> at the point of formatting the microSD card because the Overo factory >>> image does not have a mkfs.vfat utility. >> >> Time to buy a cheap ($10-ish) USB card reader! >> >> Newer images do contain vfat, but obviously this is a chicken/egg >> problem for you. I recommend a shopping trip :-) >> >> Steve >> >> >>> On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: >>> >>>> On 12-01-09 20:31, Elvis Dowson wrote: >>>>> Hi, >>>>> I'm using an Overo with the summit expansion board connected to an >>>>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >>>>> using the Overo console. >>>>> >>>>> How can I change this setting to 1920x160-60 ? >>>> >>>> depending on your kernel: >>>> >>>> video=omapfb:vram:6M,mode:1920x1600@60 >>>> >>>> or >>>> >>>> omapfb.mode=1920x1600MR-16@60 >>>> >>>> There's a but: the pixclock can be 86MHz maximum, which when I tried >>>> this weekend gave me 1600x1200@40Hz, you could tweak the timings a bit >>>> to get some more Hertzes, but I don't think you'll make 1920x1600. >>>> >>>> I'll leave it to Steve to comment on what DSS the overo uses by >>>> default :) >>>> >>>> regards, >>>> >>>> Koen >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by: >>> SourcForge Community >>> SourceForge wants to tell your story. >>> http://p.sf.net/sfu/sf-spreadtheword >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> SourcForge Community >> SourceForge wants to tell your story. >> http://p.sf.net/sfu/sf-spreadtheword >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- > View this message in context: http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29269881.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Vidya M. <vid...@gm...> - 2010-07-26 20:16:37
|
Hi Robert, Is that the resolution of your TV? Or did this config work for you instead of 1920x1080@60? I tried giving both the options. But still I get a "mode not supported" message. Thanks for the format. The kernel error I was getting was because of the wrong format I was using with my kernel version. Thanks, Vidya Robert Vogt IV wrote: > > Hi Vidya, > > I had no trouble with 1280x720MR-16@60 (720p) > > > Robert > > > > On Mon, Jul 26, 2010 at 3:29 PM, Vidya Menon <vid...@gm...> wrote: >> >> Hello Steve, >> >> I am trying to get video output on HDTV and was following this >> discussion. >> When I do a printenv at uboot, I see an env variable called "dvimode" >> >> dvimode=1024x768MR-16@60 >> >> I tried changing this to different modes by using the setenv command >> >> eg: setenv dvimode 1920x1080@30 >> >> However, when I boot I am getting the following error: >> Starting PVR >> omaplfb: OMAPLFB_Init: OMAPLFBInit failed >> FATAL: Error inserting omaplfb >> (/lib/modules/2.6.33/kernel/drivers/gpu/pvr/omaplfb.ko): No such device >> >> I was wondering if it is because this resolution is not supported? Where >> can >> I find this file omapfb_main.c - so that I can check the supported >> resolutions. >> >> Is the resolution 1920x1080@60 not supported yet? >> >> Thanks >> Vidya. >> >> >> sakoman wrote: >>> >>> On Mon, Jan 12, 2009 at 12:52 PM, Elvis Dowson <elv...@ma...> >>> wrote: >>>> Hi, >>>> I just got the Overo and Summit fresh out of the box, so to >>>> speak. :-) I just plugged it in and connected it to the console port >>>> and I'm able to access it just find. >>>> >>>> However, what escapes me is how I can get a graphical login screen to >>>> appear. I've heard that there is an Enlightnment desktop that's >>>> supposed to appear, but don't know how to get that started. >>> >>> As shipped from the factory the display resolution is set to 1024 x >>> 768 @ 60hz. This works with most LCD computer monitors (note that for >>> many monitors you will need to use an hdmi to dvi-d adaptor) >>> >>> As you discovered, many LCD *TV's* do not support this resolution. Do >>> you have an LCD computer monitor you can try? >>> >>>> So, not sure if I can actually get a graphical login going with my >>>> current build, or is it failing because of the display resolution not >>>> being supported with my display monitor. Typing the command on the >>>> console did not work. >>> >>> The OMAP3 video driver does not currently support changing the >>> resolution with fbset. >>> >>> More recent versions of u-boot and kernel support changing the >>> resolution with a kernel command line option, but only for a limited >>> set of options. >>> >>> This is done using a u-boot environment variable. If you type the >>> u-boot printenv command you will see this line in the output: >>> >>> videomode=1024x768@60,vxres=1024,vyres=768 >>> >>> You can use the setenv command to change the videomode variable to one >>> of the .name options you find in the omapfb_main.c video_modes table: >>> >>> static struct video_mode video_modes[] __initdata = { >>> { >>> /* 640 x 480 @ 60 Hz Reduced blanking VESA CVT 0.31M3-R >>> */ >>> .name = "640x480@60", >>> .x_res = 640, >>> .y_res = 480, >>> .hfp = 48, >>> .hsw = 32, >>> .hbp = 80, >>> .vfp = 3, >>> .vsw = 4, >>> .vbp = 7, >>> .pixel_clock = 23500, >>> }, >>> { >>> /* 800 x 600 @ 60 Hz Reduced blanking VESA CVT 0.48M3-R >>> */ >>> .name = "800x600@60", >>> .x_res = 800, >>> .y_res = 600, >>> .hfp = 48, >>> .hsw = 32, >>> .hbp = 80, >>> .vfp = 3, >>> .vsw = 4, >>> .vbp = 11, >>> .pixel_clock = 35500, >>> }, >>> { >>> /* 1024 x 768 @ 60 Hz Reduced blanking VESA CVT 0.79M3-R >>> */ >>> .name = "1024x768@60", >>> .x_res = 1024, >>> .y_res = 768, >>> .hfp = 48, >>> .hsw = 32, >>> .hbp = 80, >>> .vfp = 3, >>> .vsw = 4, >>> .vbp = 15, >>> .pixel_clock = 56000, >>> }, >>> { >>> /* 1280 x 720 @ 60 Hz Reduced blanking VESA CVT 0.92M9-R >>> */ >>> .name = "1280x720@60", >>> .x_res = 1280, >>> .y_res = 720, >>> .hfp = 48, >>> .hsw = 32, >>> .hbp = 80, >>> .vfp = 3, >>> .vsw = 5, >>> .vbp = 13, >>> .pixel_clock = 64000, >>> }, >>> { >>> /* 720 x 480 @ 60 Hz CEA-861 Format 3 */ >>> .name = "480p60", >>> .x_res = 720, >>> .y_res = 480, >>> .hfp = 16, >>> .hsw = 62, >>> .hbp = 60, >>> .vfp = 9, >>> .vsw = 6, >>> .vbp = 30, >>> .pixel_clock = 27027, >>> }, >>> { >>> /* 720 x 576 @ 60 Hz CEA-861 Format 18 */ >>> .name = "576p50", >>> .x_res = 720, >>> .y_res = 576, >>> .hfp = 12, >>> .hsw = 64, >>> .hbp = 68, >>> .vfp = 5, >>> .vsw = 5, >>> .vbp = 39, >>> .pixel_clock = 27000, >>> }, >>> { >>> /* 1280 x 720 @ 50 Hz CEA-861B Format 19 */ >>> .name = "720p50", >>> .x_res = 1280, >>> .y_res = 720, >>> .hfp = 440, >>> .hsw = 40, >>> .hbp = 220, >>> .vfp = 20, >>> .vsw = 5, >>> .vbp = 5, >>> .pixel_clock = 74250, >>> }, >>> { >>> /* 1280 x 720 @ 60 Hz CEA-861B Format 4 */ >>> .name = "720p60", >>> .x_res = 1280, >>> .y_res = 720, >>> .hfp = 110, >>> .hsw = 40, >>> .hbp = 220, >>> .vfp = 20, >>> .vsw = 5, >>> .vbp = 5, >>> .pixel_clock = 74250, >>> }, >>> { >>> /* 1920 x 1080 @ 24 Hz CEA-861B Format 32 */ >>> .name = "1080p24", >>> .x_res = 1920, >>> .y_res = 1080, >>> .hfp = 148, >>> .hsw = 44, >>> .hbp = 638, >>> .vfp = 36, >>> .vsw = 5, >>> .vbp = 4, >>> .pixel_clock = 74250, >>> }, >>> { >>> /* 1920 x 1080 @ 25 Hz CEA-861B Format 33 */ >>> .name = "1080p25", >>> .x_res = 1920, >>> .y_res = 1080, >>> .hfp = 148, >>> .hsw = 44, >>> .hbp = 528, >>> .vfp = 36, >>> .vsw = 5, >>> .vbp = 4, >>> .pixel_clock = 74250, >>> }, >>> { >>> /* 1920 x 1080 @ 30 Hz CEA-861B Format 34 */ >>> .name = "1080p30", >>> .x_res = 1920, >>> .y_res = 1080, >>> .hfp = 148, >>> .hsw = 44, >>> .hbp = 88, >>> .vfp = 36, >>> .vsw = 5, >>> .vbp = 4, >>> .pixel_clock = 74250, >>> }, >>> }; >>> >>>> I also don't have a computer that has a microSD/SD card reader, so it >>>> makes it difficult to create a bootable microSD card. I tried using >>>> the Overo itself to prepare the bootable microSD card, but got stuck >>>> at the point of formatting the microSD card because the Overo factory >>>> image does not have a mkfs.vfat utility. >>> >>> Time to buy a cheap ($10-ish) USB card reader! >>> >>> Newer images do contain vfat, but obviously this is a chicken/egg >>> problem for you. I recommend a shopping trip :-) >>> >>> Steve >>> >>> >>>> On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: >>>> >>>>> On 12-01-09 20:31, Elvis Dowson wrote: >>>>>> Hi, >>>>>> I'm using an Overo with the summit expansion board connected to >>>>>> an >>>>>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >>>>>> using the Overo console. >>>>>> >>>>>> How can I change this setting to 1920x160-60 ? >>>>> >>>>> depending on your kernel: >>>>> >>>>> video=omapfb:vram:6M,mode:1920x1600@60 >>>>> >>>>> or >>>>> >>>>> omapfb.mode=1920x1600MR-16@60 >>>>> >>>>> There's a but: the pixclock can be 86MHz maximum, which when I tried >>>>> this weekend gave me 1600x1200@40Hz, you could tweak the timings a bit >>>>> to get some more Hertzes, but I don't think you'll make 1920x1600. >>>>> >>>>> I'll leave it to Steve to comment on what DSS the overo uses by >>>>> default :) >>>>> >>>>> regards, >>>>> >>>>> Koen >>>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.net email is sponsored by: >>>> SourcForge Community >>>> SourceForge wants to tell your story. >>>> http://p.sf.net/sfu/sf-spreadtheword >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by: >>> SourcForge Community >>> SourceForge wants to tell your story. >>> http://p.sf.net/sfu/sf-spreadtheword >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29269881.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------------ >> The Palm PDK Hot Apps Program offers developers who use the >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> of $1 Million in cash or HP Products. Visit us here for more details: >> http://ad.doubleclick.net/clk;226879339;13503038;l? >> http://clk.atdmt.com/CRS/go/247765532/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29270276.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Vidya M. <vid...@gm...> - 2010-07-26 20:52:43
|
@ Robert, Thanks for the help 1024x768 worked for me. @J.L. I checked the specs for my TV . It has the supported computer resolutions ( This might be a fixed standard - I am a newbie and have no idea about this) and try the options. The higher resolutions didn't work. Try lower ones. Vidya. On Mon, Jul 26, 2010 at 1:16 PM, Vidya Menon <vid...@gm...> wrote: > > Hi Robert, > > Is that the resolution of your TV? Or did this config work for you instead > of 1920x1080@60? > I tried giving both the options. But still I get a "mode not supported" > message. > > Thanks for the format. The kernel error I was getting was because of the > wrong format I was using with my kernel version. > > Thanks, > Vidya > > > Robert Vogt IV wrote: > > > > Hi Vidya, > > > > I had no trouble with 1280x720MR-16@60 (720p) > > > > > > Robert > > > > > > > > On Mon, Jul 26, 2010 at 3:29 PM, Vidya Menon <vid...@gm...> > wrote: > >> > >> Hello Steve, > >> > >> I am trying to get video output on HDTV and was following this > >> discussion. > >> When I do a printenv at uboot, I see an env variable called "dvimode" > >> > >> dvimode=1024x768MR-16@60 > >> > >> I tried changing this to different modes by using the setenv command > >> > >> eg: setenv dvimode 1920x1080@30 > >> > >> However, when I boot I am getting the following error: > >> Starting PVR > >> omaplfb: OMAPLFB_Init: OMAPLFBInit failed > >> FATAL: Error inserting omaplfb > >> (/lib/modules/2.6.33/kernel/drivers/gpu/pvr/omaplfb.ko): No such device > >> > >> I was wondering if it is because this resolution is not supported? Where > >> can > >> I find this file omapfb_main.c - so that I can check the supported > >> resolutions. > >> > >> Is the resolution 1920x1080@60 not supported yet? > >> > >> Thanks > >> Vidya. > >> > >> > >> sakoman wrote: > >>> > >>> On Mon, Jan 12, 2009 at 12:52 PM, Elvis Dowson <elv...@ma...> > >>> wrote: > >>>> Hi, > >>>> I just got the Overo and Summit fresh out of the box, so to > >>>> speak. :-) I just plugged it in and connected it to the console port > >>>> and I'm able to access it just find. > >>>> > >>>> However, what escapes me is how I can get a graphical login screen to > >>>> appear. I've heard that there is an Enlightnment desktop that's > >>>> supposed to appear, but don't know how to get that started. > >>> > >>> As shipped from the factory the display resolution is set to 1024 x > >>> 768 @ 60hz. This works with most LCD computer monitors (note that for > >>> many monitors you will need to use an hdmi to dvi-d adaptor) > >>> > >>> As you discovered, many LCD *TV's* do not support this resolution. Do > >>> you have an LCD computer monitor you can try? > >>> > >>>> So, not sure if I can actually get a graphical login going with my > >>>> current build, or is it failing because of the display resolution not > >>>> being supported with my display monitor. Typing the command on the > >>>> console did not work. > >>> > >>> The OMAP3 video driver does not currently support changing the > >>> resolution with fbset. > >>> > >>> More recent versions of u-boot and kernel support changing the > >>> resolution with a kernel command line option, but only for a limited > >>> set of options. > >>> > >>> This is done using a u-boot environment variable. If you type the > >>> u-boot printenv command you will see this line in the output: > >>> > >>> videomode=1024x768@60,vxres=1024,vyres=768 > >>> > >>> You can use the setenv command to change the videomode variable to one > >>> of the .name options you find in the omapfb_main.c video_modes table: > >>> > >>> static struct video_mode video_modes[] __initdata = { > >>> { > >>> /* 640 x 480 @ 60 Hz Reduced blanking VESA CVT 0.31M3-R > >>> */ > >>> .name = "640x480@60", > >>> .x_res = 640, > >>> .y_res = 480, > >>> .hfp = 48, > >>> .hsw = 32, > >>> .hbp = 80, > >>> .vfp = 3, > >>> .vsw = 4, > >>> .vbp = 7, > >>> .pixel_clock = 23500, > >>> }, > >>> { > >>> /* 800 x 600 @ 60 Hz Reduced blanking VESA CVT 0.48M3-R > >>> */ > >>> .name = "800x600@60", > >>> .x_res = 800, > >>> .y_res = 600, > >>> .hfp = 48, > >>> .hsw = 32, > >>> .hbp = 80, > >>> .vfp = 3, > >>> .vsw = 4, > >>> .vbp = 11, > >>> .pixel_clock = 35500, > >>> }, > >>> { > >>> /* 1024 x 768 @ 60 Hz Reduced blanking VESA CVT 0.79M3-R > >>> */ > >>> .name = "1024x768@60", > >>> .x_res = 1024, > >>> .y_res = 768, > >>> .hfp = 48, > >>> .hsw = 32, > >>> .hbp = 80, > >>> .vfp = 3, > >>> .vsw = 4, > >>> .vbp = 15, > >>> .pixel_clock = 56000, > >>> }, > >>> { > >>> /* 1280 x 720 @ 60 Hz Reduced blanking VESA CVT 0.92M9-R > >>> */ > >>> .name = "1280x720@60", > >>> .x_res = 1280, > >>> .y_res = 720, > >>> .hfp = 48, > >>> .hsw = 32, > >>> .hbp = 80, > >>> .vfp = 3, > >>> .vsw = 5, > >>> .vbp = 13, > >>> .pixel_clock = 64000, > >>> }, > >>> { > >>> /* 720 x 480 @ 60 Hz CEA-861 Format 3 */ > >>> .name = "480p60", > >>> .x_res = 720, > >>> .y_res = 480, > >>> .hfp = 16, > >>> .hsw = 62, > >>> .hbp = 60, > >>> .vfp = 9, > >>> .vsw = 6, > >>> .vbp = 30, > >>> .pixel_clock = 27027, > >>> }, > >>> { > >>> /* 720 x 576 @ 60 Hz CEA-861 Format 18 */ > >>> .name = "576p50", > >>> .x_res = 720, > >>> .y_res = 576, > >>> .hfp = 12, > >>> .hsw = 64, > >>> .hbp = 68, > >>> .vfp = 5, > >>> .vsw = 5, > >>> .vbp = 39, > >>> .pixel_clock = 27000, > >>> }, > >>> { > >>> /* 1280 x 720 @ 50 Hz CEA-861B Format 19 */ > >>> .name = "720p50", > >>> .x_res = 1280, > >>> .y_res = 720, > >>> .hfp = 440, > >>> .hsw = 40, > >>> .hbp = 220, > >>> .vfp = 20, > >>> .vsw = 5, > >>> .vbp = 5, > >>> .pixel_clock = 74250, > >>> }, > >>> { > >>> /* 1280 x 720 @ 60 Hz CEA-861B Format 4 */ > >>> .name = "720p60", > >>> .x_res = 1280, > >>> .y_res = 720, > >>> .hfp = 110, > >>> .hsw = 40, > >>> .hbp = 220, > >>> .vfp = 20, > >>> .vsw = 5, > >>> .vbp = 5, > >>> .pixel_clock = 74250, > >>> }, > >>> { > >>> /* 1920 x 1080 @ 24 Hz CEA-861B Format 32 */ > >>> .name = "1080p24", > >>> .x_res = 1920, > >>> .y_res = 1080, > >>> .hfp = 148, > >>> .hsw = 44, > >>> .hbp = 638, > >>> .vfp = 36, > >>> .vsw = 5, > >>> .vbp = 4, > >>> .pixel_clock = 74250, > >>> }, > >>> { > >>> /* 1920 x 1080 @ 25 Hz CEA-861B Format 33 */ > >>> .name = "1080p25", > >>> .x_res = 1920, > >>> .y_res = 1080, > >>> .hfp = 148, > >>> .hsw = 44, > >>> .hbp = 528, > >>> .vfp = 36, > >>> .vsw = 5, > >>> .vbp = 4, > >>> .pixel_clock = 74250, > >>> }, > >>> { > >>> /* 1920 x 1080 @ 30 Hz CEA-861B Format 34 */ > >>> .name = "1080p30", > >>> .x_res = 1920, > >>> .y_res = 1080, > >>> .hfp = 148, > >>> .hsw = 44, > >>> .hbp = 88, > >>> .vfp = 36, > >>> .vsw = 5, > >>> .vbp = 4, > >>> .pixel_clock = 74250, > >>> }, > >>> }; > >>> > >>>> I also don't have a computer that has a microSD/SD card reader, so it > >>>> makes it difficult to create a bootable microSD card. I tried using > >>>> the Overo itself to prepare the bootable microSD card, but got stuck > >>>> at the point of formatting the microSD card because the Overo factory > >>>> image does not have a mkfs.vfat utility. > >>> > >>> Time to buy a cheap ($10-ish) USB card reader! > >>> > >>> Newer images do contain vfat, but obviously this is a chicken/egg > >>> problem for you. I recommend a shopping trip :-) > >>> > >>> Steve > >>> > >>> > >>>> On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: > >>>> > >>>>> On 12-01-09 20:31, Elvis Dowson wrote: > >>>>>> Hi, > >>>>>> I'm using an Overo with the summit expansion board connected to > >>>>>> an > >>>>>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" > >>>>>> using the Overo console. > >>>>>> > >>>>>> How can I change this setting to 1920x160-60 ? > >>>>> > >>>>> depending on your kernel: > >>>>> > >>>>> video=omapfb:vram:6M,mode:1920x1600@60 > >>>>> > >>>>> or > >>>>> > >>>>> omapfb.mode=1920x1600MR-16@60 > >>>>> > >>>>> There's a but: the pixclock can be 86MHz maximum, which when I tried > >>>>> this weekend gave me 1600x1200@40Hz, you could tweak the timings a > bit > >>>>> to get some more Hertzes, but I don't think you'll make 1920x1600. > >>>>> > >>>>> I'll leave it to Steve to comment on what DSS the overo uses by > >>>>> default :) > >>>>> > >>>>> regards, > >>>>> > >>>>> Koen > >>>>> > >>>> > >>>> > >>>> > ------------------------------------------------------------------------------ > >>>> This SF.net email is sponsored by: > >>>> SourcForge Community > >>>> SourceForge wants to tell your story. > >>>> http://p.sf.net/sfu/sf-spreadtheword > >>>> _______________________________________________ > >>>> gumstix-users mailing list > >>>> gum...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> This SF.net email is sponsored by: > >>> SourcForge Community > >>> SourceForge wants to tell your story. > >>> http://p.sf.net/sfu/sf-spreadtheword > >>> _______________________________________________ > >>> gumstix-users mailing list > >>> gum...@li... > >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>> > >>> > >> > >> -- > >> View this message in context: > >> > http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29269881.html > >> Sent from the Gumstix mailing list archive at Nabble.com. > >> > >> > >> > ------------------------------------------------------------------------------ > >> The Palm PDK Hot Apps Program offers developers who use the > >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share > >> of $1 Million in cash or HP Products. Visit us here for more details: > >> http://ad.doubleclick.net/clk;226879339;13503038;l? > >> http://clk.atdmt.com/CRS/go/247765532/direct/01/ > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > > > > ------------------------------------------------------------------------------ > > The Palm PDK Hot Apps Program offers developers who use the > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > of $1 Million in cash or HP Products. Visit us here for more details: > > http://ad.doubleclick.net/clk;226879339;13503038;l? > > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > -- > View this message in context: > http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29270276.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: J. L. <vwy...@gm...> - 2010-07-26 21:09:15
|
yeah for me I have tried all resolutions and I know my tv will display computer resolutions as it works on all my different boxes and laptops. I will give your res a shot though maybe it was one I missed. I know I was trying tons of em so possible I missed one along the way. When you say try the options are you meaning on the tv? I have never had to do anything special on mine to get it to work with a computer, what did you have to change on your tv as far as options if that was the case? Thanks On Mon, Jul 26, 2010 at 1:52 PM, Vidya Menon <vid...@gm...> wrote: > @ Robert, Thanks for the help > 1024x768 worked for me. > @J.L. > I checked the specs for my TV . It has the supported computer resolutions ( > This might be a fixed standard - I am a newbie and have no idea about this) > and try the options. The higher resolutions didn't work. Try lower ones. > > Vidya. > > On Mon, Jul 26, 2010 at 1:16 PM, Vidya Menon <vid...@gm...> wrote: >> >> Hi Robert, >> >> Is that the resolution of your TV? Or did this config work for you instead >> of 1920x1080@60? >> I tried giving both the options. But still I get a "mode not supported" >> message. >> >> Thanks for the format. The kernel error I was getting was because of the >> wrong format I was using with my kernel version. >> >> Thanks, >> Vidya >> >> >> Robert Vogt IV wrote: >> > >> > Hi Vidya, >> > >> > I had no trouble with 1280x720MR-16@60 (720p) >> > >> > >> > Robert >> > >> > >> > >> > On Mon, Jul 26, 2010 at 3:29 PM, Vidya Menon <vid...@gm...> >> > wrote: >> >> >> >> Hello Steve, >> >> >> >> I am trying to get video output on HDTV and was following this >> >> discussion. >> >> When I do a printenv at uboot, I see an env variable called "dvimode" >> >> >> >> dvimode=1024x768MR-16@60 >> >> >> >> I tried changing this to different modes by using the setenv command >> >> >> >> eg: setenv dvimode 1920x1080@30 >> >> >> >> However, when I boot I am getting the following error: >> >> Starting PVR >> >> omaplfb: OMAPLFB_Init: OMAPLFBInit failed >> >> FATAL: Error inserting omaplfb >> >> (/lib/modules/2.6.33/kernel/drivers/gpu/pvr/omaplfb.ko): No such device >> >> >> >> I was wondering if it is because this resolution is not supported? >> >> Where >> >> can >> >> I find this file omapfb_main.c - so that I can check the supported >> >> resolutions. >> >> >> >> Is the resolution 1920x1080@60 not supported yet? >> >> >> >> Thanks >> >> Vidya. >> >> >> >> >> >> sakoman wrote: >> >>> >> >>> On Mon, Jan 12, 2009 at 12:52 PM, Elvis Dowson <elv...@ma...> >> >>> wrote: >> >>>> Hi, >> >>>> I just got the Overo and Summit fresh out of the box, so to >> >>>> speak. :-) I just plugged it in and connected it to the console port >> >>>> and I'm able to access it just find. >> >>>> >> >>>> However, what escapes me is how I can get a graphical login screen to >> >>>> appear. I've heard that there is an Enlightnment desktop that's >> >>>> supposed to appear, but don't know how to get that started. >> >>> >> >>> As shipped from the factory the display resolution is set to 1024 x >> >>> 768 @ 60hz. This works with most LCD computer monitors (note that for >> >>> many monitors you will need to use an hdmi to dvi-d adaptor) >> >>> >> >>> As you discovered, many LCD *TV's* do not support this resolution. Do >> >>> you have an LCD computer monitor you can try? >> >>> >> >>>> So, not sure if I can actually get a graphical login going with my >> >>>> current build, or is it failing because of the display resolution not >> >>>> being supported with my display monitor. Typing the command on the >> >>>> console did not work. >> >>> >> >>> The OMAP3 video driver does not currently support changing the >> >>> resolution with fbset. >> >>> >> >>> More recent versions of u-boot and kernel support changing the >> >>> resolution with a kernel command line option, but only for a limited >> >>> set of options. >> >>> >> >>> This is done using a u-boot environment variable. If you type the >> >>> u-boot printenv command you will see this line in the output: >> >>> >> >>> videomode=1024x768@60,vxres=1024,vyres=768 >> >>> >> >>> You can use the setenv command to change the videomode variable to one >> >>> of the .name options you find in the omapfb_main.c video_modes table: >> >>> >> >>> static struct video_mode video_modes[] __initdata = { >> >>> { >> >>> /* 640 x 480 @ 60 Hz Reduced blanking VESA CVT 0.31M3-R >> >>> */ >> >>> .name = "640x480@60", >> >>> .x_res = 640, >> >>> .y_res = 480, >> >>> .hfp = 48, >> >>> .hsw = 32, >> >>> .hbp = 80, >> >>> .vfp = 3, >> >>> .vsw = 4, >> >>> .vbp = 7, >> >>> .pixel_clock = 23500, >> >>> }, >> >>> { >> >>> /* 800 x 600 @ 60 Hz Reduced blanking VESA CVT 0.48M3-R >> >>> */ >> >>> .name = "800x600@60", >> >>> .x_res = 800, >> >>> .y_res = 600, >> >>> .hfp = 48, >> >>> .hsw = 32, >> >>> .hbp = 80, >> >>> .vfp = 3, >> >>> .vsw = 4, >> >>> .vbp = 11, >> >>> .pixel_clock = 35500, >> >>> }, >> >>> { >> >>> /* 1024 x 768 @ 60 Hz Reduced blanking VESA CVT >> >>> 0.79M3-R >> >>> */ >> >>> .name = "1024x768@60", >> >>> .x_res = 1024, >> >>> .y_res = 768, >> >>> .hfp = 48, >> >>> .hsw = 32, >> >>> .hbp = 80, >> >>> .vfp = 3, >> >>> .vsw = 4, >> >>> .vbp = 15, >> >>> .pixel_clock = 56000, >> >>> }, >> >>> { >> >>> /* 1280 x 720 @ 60 Hz Reduced blanking VESA CVT >> >>> 0.92M9-R >> >>> */ >> >>> .name = "1280x720@60", >> >>> .x_res = 1280, >> >>> .y_res = 720, >> >>> .hfp = 48, >> >>> .hsw = 32, >> >>> .hbp = 80, >> >>> .vfp = 3, >> >>> .vsw = 5, >> >>> .vbp = 13, >> >>> .pixel_clock = 64000, >> >>> }, >> >>> { >> >>> /* 720 x 480 @ 60 Hz CEA-861 Format 3 */ >> >>> .name = "480p60", >> >>> .x_res = 720, >> >>> .y_res = 480, >> >>> .hfp = 16, >> >>> .hsw = 62, >> >>> .hbp = 60, >> >>> .vfp = 9, >> >>> .vsw = 6, >> >>> .vbp = 30, >> >>> .pixel_clock = 27027, >> >>> }, >> >>> { >> >>> /* 720 x 576 @ 60 Hz CEA-861 Format 18 */ >> >>> .name = "576p50", >> >>> .x_res = 720, >> >>> .y_res = 576, >> >>> .hfp = 12, >> >>> .hsw = 64, >> >>> .hbp = 68, >> >>> .vfp = 5, >> >>> .vsw = 5, >> >>> .vbp = 39, >> >>> .pixel_clock = 27000, >> >>> }, >> >>> { >> >>> /* 1280 x 720 @ 50 Hz CEA-861B Format 19 */ >> >>> .name = "720p50", >> >>> .x_res = 1280, >> >>> .y_res = 720, >> >>> .hfp = 440, >> >>> .hsw = 40, >> >>> .hbp = 220, >> >>> .vfp = 20, >> >>> .vsw = 5, >> >>> .vbp = 5, >> >>> .pixel_clock = 74250, >> >>> }, >> >>> { >> >>> /* 1280 x 720 @ 60 Hz CEA-861B Format 4 */ >> >>> .name = "720p60", >> >>> .x_res = 1280, >> >>> .y_res = 720, >> >>> .hfp = 110, >> >>> .hsw = 40, >> >>> .hbp = 220, >> >>> .vfp = 20, >> >>> .vsw = 5, >> >>> .vbp = 5, >> >>> .pixel_clock = 74250, >> >>> }, >> >>> { >> >>> /* 1920 x 1080 @ 24 Hz CEA-861B Format 32 */ >> >>> .name = "1080p24", >> >>> .x_res = 1920, >> >>> .y_res = 1080, >> >>> .hfp = 148, >> >>> .hsw = 44, >> >>> .hbp = 638, >> >>> .vfp = 36, >> >>> .vsw = 5, >> >>> .vbp = 4, >> >>> .pixel_clock = 74250, >> >>> }, >> >>> { >> >>> /* 1920 x 1080 @ 25 Hz CEA-861B Format 33 */ >> >>> .name = "1080p25", >> >>> .x_res = 1920, >> >>> .y_res = 1080, >> >>> .hfp = 148, >> >>> .hsw = 44, >> >>> .hbp = 528, >> >>> .vfp = 36, >> >>> .vsw = 5, >> >>> .vbp = 4, >> >>> .pixel_clock = 74250, >> >>> }, >> >>> { >> >>> /* 1920 x 1080 @ 30 Hz CEA-861B Format 34 */ >> >>> .name = "1080p30", >> >>> .x_res = 1920, >> >>> .y_res = 1080, >> >>> .hfp = 148, >> >>> .hsw = 44, >> >>> .hbp = 88, >> >>> .vfp = 36, >> >>> .vsw = 5, >> >>> .vbp = 4, >> >>> .pixel_clock = 74250, >> >>> }, >> >>> }; >> >>> >> >>>> I also don't have a computer that has a microSD/SD card reader, so it >> >>>> makes it difficult to create a bootable microSD card. I tried using >> >>>> the Overo itself to prepare the bootable microSD card, but got stuck >> >>>> at the point of formatting the microSD card because the Overo factory >> >>>> image does not have a mkfs.vfat utility. >> >>> >> >>> Time to buy a cheap ($10-ish) USB card reader! >> >>> >> >>> Newer images do contain vfat, but obviously this is a chicken/egg >> >>> problem for you. I recommend a shopping trip :-) >> >>> >> >>> Steve >> >>> >> >>> >> >>>> On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: >> >>>> >> >>>>> On 12-01-09 20:31, Elvis Dowson wrote: >> >>>>>> Hi, >> >>>>>> I'm using an Overo with the summit expansion board connected >> >>>>>> to >> >>>>>> an >> >>>>>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get 1024x768-58" >> >>>>>> using the Overo console. >> >>>>>> >> >>>>>> How can I change this setting to 1920x160-60 ? >> >>>>> >> >>>>> depending on your kernel: >> >>>>> >> >>>>> video=omapfb:vram:6M,mode:1920x1600@60 >> >>>>> >> >>>>> or >> >>>>> >> >>>>> omapfb.mode=1920x1600MR-16@60 >> >>>>> >> >>>>> There's a but: the pixclock can be 86MHz maximum, which when I tried >> >>>>> this weekend gave me 1600x1200@40Hz, you could tweak the timings a >> >>>>> bit >> >>>>> to get some more Hertzes, but I don't think you'll make 1920x1600. >> >>>>> >> >>>>> I'll leave it to Steve to comment on what DSS the overo uses by >> >>>>> default :) >> >>>>> >> >>>>> regards, >> >>>>> >> >>>>> Koen >> >>>>> >> >>>> >> >>>> >> >>>> >> >>>> ------------------------------------------------------------------------------ >> >>>> This SF.net email is sponsored by: >> >>>> SourcForge Community >> >>>> SourceForge wants to tell your story. >> >>>> http://p.sf.net/sfu/sf-spreadtheword >> >>>> _______________________________________________ >> >>>> gumstix-users mailing list >> >>>> gum...@li... >> >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >>>> >> >>> >> >>> >> >>> ------------------------------------------------------------------------------ >> >>> This SF.net email is sponsored by: >> >>> SourcForge Community >> >>> SourceForge wants to tell your story. >> >>> http://p.sf.net/sfu/sf-spreadtheword >> >>> _______________________________________________ >> >>> gumstix-users mailing list >> >>> gum...@li... >> >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >>> >> >>> >> >> >> >> -- >> >> View this message in context: >> >> >> >> http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29269881.html >> >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> The Palm PDK Hot Apps Program offers developers who use the >> >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> >> of $1 Million in cash or HP Products. Visit us here for more details: >> >> http://ad.doubleclick.net/clk;226879339;13503038;l? >> >> http://clk.atdmt.com/CRS/go/247765532/direct/01/ >> >> _______________________________________________ >> >> gumstix-users mailing list >> >> gum...@li... >> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> >> > >> > >> > ------------------------------------------------------------------------------ >> > The Palm PDK Hot Apps Program offers developers who use the >> > Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> > of $1 Million in cash or HP Products. Visit us here for more details: >> > http://ad.doubleclick.net/clk;226879339;13503038;l? >> > http://clk.atdmt.com/CRS/go/247765532/direct/01/ >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> > >> >> -- >> View this message in context: >> http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29270276.html >> Sent from the Gumstix mailing list archive at Nabble.com. >> >> >> >> ------------------------------------------------------------------------------ >> The Palm PDK Hot Apps Program offers developers who use the >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> of $1 Million in cash or HP Products. Visit us here for more details: >> http://ad.doubleclick.net/clk;226879339;13503038;l? >> http://clk.atdmt.com/CRS/go/247765532/direct/01/ >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Vidya M. <vid...@gm...> - 2010-07-26 21:21:05
|
Hi JL, I didn't make any changes on the TV configurations. just give setenv command at u-boot prompt. setenv dvimode 1024x768Mr-16@60 save reset On Mon, Jul 26, 2010 at 2:09 PM, J. L. <vwy...@gm...> wrote: > yeah for me I have tried all resolutions and I know my tv will display > computer resolutions as it works on all my different boxes and > laptops. I will give your res a shot though maybe it was one I missed. > I know I was trying tons of em so possible I missed one along the way. > When you say try the options are you meaning on the tv? I have never > had to do anything special on mine to get it to work with a computer, > what did you have to change on your tv as far as options if that was > the case? > > Thanks > > On Mon, Jul 26, 2010 at 1:52 PM, Vidya Menon <vid...@gm...> wrote: > > @ Robert, Thanks for the help > > 1024x768 worked for me. > > @J.L. > > I checked the specs for my TV . It has the supported computer resolutions > ( > > This might be a fixed standard - I am a newbie and have no idea about > this) > > and try the options. The higher resolutions didn't work. Try lower ones. > > > > Vidya. > > > > On Mon, Jul 26, 2010 at 1:16 PM, Vidya Menon <vid...@gm...> > wrote: > >> > >> Hi Robert, > >> > >> Is that the resolution of your TV? Or did this config work for you > instead > >> of 1920x1080@60? > >> I tried giving both the options. But still I get a "mode not supported" > >> message. > >> > >> Thanks for the format. The kernel error I was getting was because of the > >> wrong format I was using with my kernel version. > >> > >> Thanks, > >> Vidya > >> > >> > >> Robert Vogt IV wrote: > >> > > >> > Hi Vidya, > >> > > >> > I had no trouble with 1280x720MR-16@60 (720p) > >> > > >> > > >> > Robert > >> > > >> > > >> > > >> > On Mon, Jul 26, 2010 at 3:29 PM, Vidya Menon <vid...@gm...> > >> > wrote: > >> >> > >> >> Hello Steve, > >> >> > >> >> I am trying to get video output on HDTV and was following this > >> >> discussion. > >> >> When I do a printenv at uboot, I see an env variable called "dvimode" > >> >> > >> >> dvimode=1024x768MR-16@60 > >> >> > >> >> I tried changing this to different modes by using the setenv command > >> >> > >> >> eg: setenv dvimode 1920x1080@30 > >> >> > >> >> However, when I boot I am getting the following error: > >> >> Starting PVR > >> >> omaplfb: OMAPLFB_Init: OMAPLFBInit failed > >> >> FATAL: Error inserting omaplfb > >> >> (/lib/modules/2.6.33/kernel/drivers/gpu/pvr/omaplfb.ko): No such > device > >> >> > >> >> I was wondering if it is because this resolution is not supported? > >> >> Where > >> >> can > >> >> I find this file omapfb_main.c - so that I can check the supported > >> >> resolutions. > >> >> > >> >> Is the resolution 1920x1080@60 not supported yet? > >> >> > >> >> Thanks > >> >> Vidya. > >> >> > >> >> > >> >> sakoman wrote: > >> >>> > >> >>> On Mon, Jan 12, 2009 at 12:52 PM, Elvis Dowson < > elv...@ma...> > >> >>> wrote: > >> >>>> Hi, > >> >>>> I just got the Overo and Summit fresh out of the box, so to > >> >>>> speak. :-) I just plugged it in and connected it to the console > port > >> >>>> and I'm able to access it just find. > >> >>>> > >> >>>> However, what escapes me is how I can get a graphical login screen > to > >> >>>> appear. I've heard that there is an Enlightnment desktop that's > >> >>>> supposed to appear, but don't know how to get that started. > >> >>> > >> >>> As shipped from the factory the display resolution is set to 1024 x > >> >>> 768 @ 60hz. This works with most LCD computer monitors (note that > for > >> >>> many monitors you will need to use an hdmi to dvi-d adaptor) > >> >>> > >> >>> As you discovered, many LCD *TV's* do not support this resolution. > Do > >> >>> you have an LCD computer monitor you can try? > >> >>> > >> >>>> So, not sure if I can actually get a graphical login going with my > >> >>>> current build, or is it failing because of the display resolution > not > >> >>>> being supported with my display monitor. Typing the command on the > >> >>>> console did not work. > >> >>> > >> >>> The OMAP3 video driver does not currently support changing the > >> >>> resolution with fbset. > >> >>> > >> >>> More recent versions of u-boot and kernel support changing the > >> >>> resolution with a kernel command line option, but only for a limited > >> >>> set of options. > >> >>> > >> >>> This is done using a u-boot environment variable. If you type the > >> >>> u-boot printenv command you will see this line in the output: > >> >>> > >> >>> videomode=1024x768@60,vxres=1024,vyres=768 > >> >>> > >> >>> You can use the setenv command to change the videomode variable to > one > >> >>> of the .name options you find in the omapfb_main.c video_modes > table: > >> >>> > >> >>> static struct video_mode video_modes[] __initdata = { > >> >>> { > >> >>> /* 640 x 480 @ 60 Hz Reduced blanking VESA CVT > 0.31M3-R > >> >>> */ > >> >>> .name = "640x480@60", > >> >>> .x_res = 640, > >> >>> .y_res = 480, > >> >>> .hfp = 48, > >> >>> .hsw = 32, > >> >>> .hbp = 80, > >> >>> .vfp = 3, > >> >>> .vsw = 4, > >> >>> .vbp = 7, > >> >>> .pixel_clock = 23500, > >> >>> }, > >> >>> { > >> >>> /* 800 x 600 @ 60 Hz Reduced blanking VESA CVT > 0.48M3-R > >> >>> */ > >> >>> .name = "800x600@60", > >> >>> .x_res = 800, > >> >>> .y_res = 600, > >> >>> .hfp = 48, > >> >>> .hsw = 32, > >> >>> .hbp = 80, > >> >>> .vfp = 3, > >> >>> .vsw = 4, > >> >>> .vbp = 11, > >> >>> .pixel_clock = 35500, > >> >>> }, > >> >>> { > >> >>> /* 1024 x 768 @ 60 Hz Reduced blanking VESA CVT > >> >>> 0.79M3-R > >> >>> */ > >> >>> .name = "1024x768@60", > >> >>> .x_res = 1024, > >> >>> .y_res = 768, > >> >>> .hfp = 48, > >> >>> .hsw = 32, > >> >>> .hbp = 80, > >> >>> .vfp = 3, > >> >>> .vsw = 4, > >> >>> .vbp = 15, > >> >>> .pixel_clock = 56000, > >> >>> }, > >> >>> { > >> >>> /* 1280 x 720 @ 60 Hz Reduced blanking VESA CVT > >> >>> 0.92M9-R > >> >>> */ > >> >>> .name = "1280x720@60", > >> >>> .x_res = 1280, > >> >>> .y_res = 720, > >> >>> .hfp = 48, > >> >>> .hsw = 32, > >> >>> .hbp = 80, > >> >>> .vfp = 3, > >> >>> .vsw = 5, > >> >>> .vbp = 13, > >> >>> .pixel_clock = 64000, > >> >>> }, > >> >>> { > >> >>> /* 720 x 480 @ 60 Hz CEA-861 Format 3 */ > >> >>> .name = "480p60", > >> >>> .x_res = 720, > >> >>> .y_res = 480, > >> >>> .hfp = 16, > >> >>> .hsw = 62, > >> >>> .hbp = 60, > >> >>> .vfp = 9, > >> >>> .vsw = 6, > >> >>> .vbp = 30, > >> >>> .pixel_clock = 27027, > >> >>> }, > >> >>> { > >> >>> /* 720 x 576 @ 60 Hz CEA-861 Format 18 */ > >> >>> .name = "576p50", > >> >>> .x_res = 720, > >> >>> .y_res = 576, > >> >>> .hfp = 12, > >> >>> .hsw = 64, > >> >>> .hbp = 68, > >> >>> .vfp = 5, > >> >>> .vsw = 5, > >> >>> .vbp = 39, > >> >>> .pixel_clock = 27000, > >> >>> }, > >> >>> { > >> >>> /* 1280 x 720 @ 50 Hz CEA-861B Format 19 */ > >> >>> .name = "720p50", > >> >>> .x_res = 1280, > >> >>> .y_res = 720, > >> >>> .hfp = 440, > >> >>> .hsw = 40, > >> >>> .hbp = 220, > >> >>> .vfp = 20, > >> >>> .vsw = 5, > >> >>> .vbp = 5, > >> >>> .pixel_clock = 74250, > >> >>> }, > >> >>> { > >> >>> /* 1280 x 720 @ 60 Hz CEA-861B Format 4 */ > >> >>> .name = "720p60", > >> >>> .x_res = 1280, > >> >>> .y_res = 720, > >> >>> .hfp = 110, > >> >>> .hsw = 40, > >> >>> .hbp = 220, > >> >>> .vfp = 20, > >> >>> .vsw = 5, > >> >>> .vbp = 5, > >> >>> .pixel_clock = 74250, > >> >>> }, > >> >>> { > >> >>> /* 1920 x 1080 @ 24 Hz CEA-861B Format 32 */ > >> >>> .name = "1080p24", > >> >>> .x_res = 1920, > >> >>> .y_res = 1080, > >> >>> .hfp = 148, > >> >>> .hsw = 44, > >> >>> .hbp = 638, > >> >>> .vfp = 36, > >> >>> .vsw = 5, > >> >>> .vbp = 4, > >> >>> .pixel_clock = 74250, > >> >>> }, > >> >>> { > >> >>> /* 1920 x 1080 @ 25 Hz CEA-861B Format 33 */ > >> >>> .name = "1080p25", > >> >>> .x_res = 1920, > >> >>> .y_res = 1080, > >> >>> .hfp = 148, > >> >>> .hsw = 44, > >> >>> .hbp = 528, > >> >>> .vfp = 36, > >> >>> .vsw = 5, > >> >>> .vbp = 4, > >> >>> .pixel_clock = 74250, > >> >>> }, > >> >>> { > >> >>> /* 1920 x 1080 @ 30 Hz CEA-861B Format 34 */ > >> >>> .name = "1080p30", > >> >>> .x_res = 1920, > >> >>> .y_res = 1080, > >> >>> .hfp = 148, > >> >>> .hsw = 44, > >> >>> .hbp = 88, > >> >>> .vfp = 36, > >> >>> .vsw = 5, > >> >>> .vbp = 4, > >> >>> .pixel_clock = 74250, > >> >>> }, > >> >>> }; > >> >>> > >> >>>> I also don't have a computer that has a microSD/SD card reader, so > it > >> >>>> makes it difficult to create a bootable microSD card. I tried using > >> >>>> the Overo itself to prepare the bootable microSD card, but got > stuck > >> >>>> at the point of formatting the microSD card because the Overo > factory > >> >>>> image does not have a mkfs.vfat utility. > >> >>> > >> >>> Time to buy a cheap ($10-ish) USB card reader! > >> >>> > >> >>> Newer images do contain vfat, but obviously this is a chicken/egg > >> >>> problem for you. I recommend a shopping trip :-) > >> >>> > >> >>> Steve > >> >>> > >> >>> > >> >>>> On Jan 13, 2009, at 12:18 AM, Koen Kooi wrote: > >> >>>> > >> >>>>> On 12-01-09 20:31, Elvis Dowson wrote: > >> >>>>>> Hi, > >> >>>>>> I'm using an Overo with the summit expansion board connected > >> >>>>>> to > >> >>>>>> an > >> >>>>>> HDMI LCD TV (1920x1600 @60Hz). When I ran fbset, I get > 1024x768-58" > >> >>>>>> using the Overo console. > >> >>>>>> > >> >>>>>> How can I change this setting to 1920x160-60 ? > >> >>>>> > >> >>>>> depending on your kernel: > >> >>>>> > >> >>>>> video=omapfb:vram:6M,mode:1920x1600@60 > >> >>>>> > >> >>>>> or > >> >>>>> > >> >>>>> omapfb.mode=1920x1600MR-16@60 > >> >>>>> > >> >>>>> There's a but: the pixclock can be 86MHz maximum, which when I > tried > >> >>>>> this weekend gave me 1600x1200@40Hz, you could tweak the timings > a > >> >>>>> bit > >> >>>>> to get some more Hertzes, but I don't think you'll make 1920x1600. > >> >>>>> > >> >>>>> I'll leave it to Steve to comment on what DSS the overo uses by > >> >>>>> default :) > >> >>>>> > >> >>>>> regards, > >> >>>>> > >> >>>>> Koen > >> >>>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > ------------------------------------------------------------------------------ > >> >>>> This SF.net email is sponsored by: > >> >>>> SourcForge Community > >> >>>> SourceForge wants to tell your story. > >> >>>> http://p.sf.net/sfu/sf-spreadtheword > >> >>>> _______________________________________________ > >> >>>> gumstix-users mailing list > >> >>>> gum...@li... > >> >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> >>>> > >> >>> > >> >>> > >> >>> > ------------------------------------------------------------------------------ > >> >>> This SF.net email is sponsored by: > >> >>> SourcForge Community > >> >>> SourceForge wants to tell your story. > >> >>> http://p.sf.net/sfu/sf-spreadtheword > >> >>> _______________________________________________ > >> >>> gumstix-users mailing list > >> >>> gum...@li... > >> >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> >>> > >> >>> > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> >> > http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29269881.html > >> >> Sent from the Gumstix mailing list archive at Nabble.com. > >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ > >> >> The Palm PDK Hot Apps Program offers developers who use the > >> >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share > >> >> of $1 Million in cash or HP Products. Visit us here for more details: > >> >> http://ad.doubleclick.net/clk;226879339;13503038;l? > >> >> http://clk.atdmt.com/CRS/go/247765532/direct/01/ > >> >> _______________________________________________ > >> >> gumstix-users mailing list > >> >> gum...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> >> > >> > > >> > > >> > > ------------------------------------------------------------------------------ > >> > The Palm PDK Hot Apps Program offers developers who use the > >> > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > >> > of $1 Million in cash or HP Products. Visit us here for more details: > >> > http://ad.doubleclick.net/clk;226879339;13503038;l? > >> > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > >> > _______________________________________________ > >> > gumstix-users mailing list > >> > gum...@li... > >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://old.nabble.com/Re%3A-Overo%2C-no-HDMI-output-tp21421975p29270276.html > >> Sent from the Gumstix mailing list archive at Nabble.com. > >> > >> > >> > >> > ------------------------------------------------------------------------------ > >> The Palm PDK Hot Apps Program offers developers who use the > >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share > >> of $1 Million in cash or HP Products. Visit us here for more details: > >> http://ad.doubleclick.net/clk;226879339;13503038;l? > >> http://clk.atdmt.com/CRS/go/247765532/direct/01/ > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------------ > > The Palm PDK Hot Apps Program offers developers who use the > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > of $1 Million in cash or HP Products. Visit us here for more details: > > http://ad.doubleclick.net/clk;226879339;13503038;l? > > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |