Problems trying to get 1024x768 with DSS2
chr...@goop.org
I've been pulling my hair out for the past week and half trying to get
DDS2 to work at 1024x768.
I'm wanting to run mplayer -fs on the framebuffer at 1024x768 at 24-
bit. If I use the 2.6.27 kernel from:
http://www.angstrom-distribution.org/demo/beagleboard/
mplayer -fs runs with no problem, though it's 16-bit.
I've tried various 2.6.28 and "2.6.27+2.6.28" kernels from koen and
others with DSS2, including a 2.6.8-r25 I build yesterday via open
embedded with bitbake -b packages/linux/linux-omap_2.6.28 (which
definitely has the patch to video modes selectable) and I can switch
the video mode to a 1024x768 resolution, but always mplayer -fs plays
the video squashed into the top left 640x480 region.
No matter what I do /sys/devices/platform/omapfb/framebuffers has:
0 p:8064f000 v:c9000000 size:1228800 t:gfx
1 p:00000000 v:00000000 size:0 t:vid1
2 p:00000000 v:00000000 size:0 t:vid2
1228800 is 6480x480x4, right? And displays has:
dvi e:1 u:1 t:0 h:640/48/80/32 v:480/3/7/4 p:23500
tv e:0 u:-1 t:0 h:720/0/0/0 v:574/0/0/0 p:0
On bootup fbset reports:
mode "640x480-59"
# D: 23.500 MHz, H: 29.375 kHz, V: 59.464 Hz
geometry 640 480 640 480 32
timings 42553 48 80 3 7 32 4
accel false
rgba 8/16,8/8,8/0,0/0
endmode
After running various commands like:
echo "dvi h:1024/20/8/30 v:768/4/2/20 p:48000"
fbset -fb /dev/fb0 -xres 1024 -yres 768
fbset will report:
mode "1024x768-25"
# D: 23.500 MHz, H: 19.848 kHz, V: 25.381 Hz
geometry 1024 768 640 480 32
timings 42553 48 80 3 7 32 4
accel false
rgba 8/16,8/8,8/0,0/0
endmode
and displays has:
dvi e:1 u:1 t:0 h:1024/20/8/30 v:768/4/2/20 p:48000
tv e:0 u:-1 t:0 h:720/0/0/0 v:574/0/0/0 p:0
... but framebuffers always reports:
0 p:8064f000 v:c9000000 size:1228800 t:gfx
... and mplayer only dsplays in the top,right corner of the
framebuffer.
(I'm using the 25Hz mode because if I try and use a standard
1024x768@60 timing DSS2 crashes with a null pointer deference as
reported elsewhere - not sure if this is fixed in current kernels or
not)
I believe I've tried adding ,vxvres=1024,vyres=768 parameters which I
think someone suggested by to no avail.
Does anyone have any ideas?
Regards,
Christopher.
Koen Kooi
Op 14 jan 2009, om 13:52 heeft chr...@goop.org het volgende geschreven:
>
> Hello,
>
> I've been pulling my hair out for the past week and half trying to get
> DDS2 to work at 1024x768.
Put 'omapfb.mode=1024x768MR-24@60' in your kernel cmdline.
regards,
Koen
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "Beagle Board" group.
> To post to this group, send email to discu...@beagleboard.org.
> To unsubscribe from this group, send email to beagleboard...@beagleboard.org
> For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
chr...@goop.org
On Jan 15, 6:42 am, Koen Kooi <k...@beagleboard.org> wrote:
> Op 14 jan 2009, om 13:52 heeft chr...@goop.org het volgende geschreven:
> > Hello,
>
> > I've been pulling my hair out for the past week and half trying to get
> > DDS2 to work at 1024x768.
>
> Put 'omapfb.mode=1024x768MR-24@60' in your kernel cmdline.
Linux version 2.6.28-omap1 (koen@dominion) (gcc version 4.2.1) #1 Fri
Jan 9 17:10:15 CET
2009
[...]
Kernel command line: console=ttyS2,115200n8 console=tty0 root=/dev/
mmcblk0p2 rootwait rootfstype=ext3
omapfb.mode=1024x768MR-24@60
Unknown boot option `omapfb.mode=1024x768MR-24@60': ignoring
I don't have a SD card reader here to check but I think this is the
uImage-2.6.28-r5 kernel I built from OE.
I also tried
uImage-2.6.27+2.6.28rc6+r1+gitr3b7de4be
879f1f4f55ae59882a5cbd80f6dcf0f0-r1-beagleboard.bin and got the same
thing.
Cheers,
Christopher.
Koen Kooi
Op 16 jan 2009 om 16:29 heeft chr...@goop.org het volgende geschreven:\
>
>
> On Jan 15, 6:42 am, Koen Kooi <k...@beagleboard.org> wrote:
>> Op 14 jan 2009, om 13:52 heeft chr...@goop.org het volgende
>> geschreven:
>>> Hello,
>>
>>> I've been pulling my hair out for the past week and half trying to
>>> get
>>> DDS2 to work at 1024x768.
>>
>> Put 'omapfb.mode=1024x768MR-24@60' in your kernel cmdline.
>
recalcati
root@beagleboard:~# cat /proc/cmdline
console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait
rootfstype=ext3 omapfb.videomode=1024x768MR-24@60
and booting
Unknown boot option `omapfb.videomode=1024x768MR-24@60': ignoring
With 2.6.28 I really can't give parameters to omapfb_main
I read arm/OMAP/DSS documentation and also fb/mode..
but the commandline doesn't work.
I also tried to re-compile the kernel in oe/tmp/work/beagleboard-
angstrom-linux-gnueabi/linux-omap-2.6.28-r0/git but it is the same.
I tried to add some tracing in dirvers/video/omap/omafb_main.c adding
#define DEBUG 1
before the include, but pr_debug doesn't appear ( or maybe the
parameter didn't arrive to omapfb)
Tomi Valkeinen
On Sun, 2009-01-25 at 17:24 -0800, ext recalcati wrote:
> I tried the same, but without result
>
> root@beagleboard:~# cat /proc/cmdline
> console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait
> rootfstype=ext3 omapfb.videomode=1024x768MR-24@60
>
> and booting
> Unknown boot option `omapfb.videomode=1024x768MR-24@60': ignoring
>
> With 2.6.28 I really can't give parameters to omapfb_main
> I read arm/OMAP/DSS documentation and also fb/mode..
> but the commandline doesn't work.
Read it again, this time correctly =).
omapfb.video_mode
- Default video mode for default display. For example,
"800x400MR-24@60". See drivers/video/modedb.c
>
> I also tried to re-compile the kernel in oe/tmp/work/beagleboard-
> angstrom-linux-gnueabi/linux-omap-2.6.28-r0/git but it is the same.
> I tried to add some tracing in dirvers/video/omap/omafb_main.c adding
> #define DEBUG 1
> before the include, but pr_debug doesn't appear ( or maybe the
> parameter didn't arrive to omapfb)
That doesn't help, as that file is for the old display subsystem.
Tomi