OMAP3 DSS2 - VENC timings
I'm running a frame buffer console on a TV device via the VENC. The video timings don't see to be quite right as Tux is about 1/2 off the screen - both directions, i.e. his head and right side have been cut off as they are outside the viewable area. Also, when I send data to the device (via /dev/tty1) which has 90x35 characters, I lose 4 characters on each end of every line.
Is there something I can do about this? I've looked at the timings in drivers/video/omap2/dss/venc.c
Also, how can I select NTSC vs PAL setups via the command line? I have only the one video device VENC.
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 9 lines · Gary Thomas
I'm running a frame buffer console on a TV device via the VENC. The video timings don't see to be quite right as Tux is about 1/2 off the screen - both directions, i.e. his head and right side have been cut off as they are outside the viewable area. Also, when I send data to the device (via
/dev/tty1) which has 90x35 characters, I lose 4 characters on each end of every line.Is there something I can do about this? I've looked at the timings in
drivers/video/omap2/dss/venc.c
I don't know much about analog TV, but my understanding is that there's always overscanning going on. You just have to size and position the overlay so that it is visible on your TV.
Quoted 2 lines
Also, how can I select NTSC vs PAL setups via the command line? I have only the one video device VENC.
Documentation/arm/OMAP/DSS says you can echo "pal" or "ntsc" to sys/devices/platform/omapdss/display?/timings file.
Tomi
Quoted 8 lines · Tomi
Quoted 7 lines · Gary Thomas
I'm running a frame buffer console on a TV device via the VENC. The video timings don't see to be quite right as Tux is about 1/2 off the screen - both directions, i.e. his head and right side have been cut off as they are outside the viewable area. Also, when I send data to the device (via
/dev/tty1) which has 90x35 characters, I lose 4 characters on each end of every line.
I am not sure whether this applies here with your issue, but if I remember
correctly, during initial days of development we had similar issue where, corners of the display cuts-off. The conclusion was, analog TV's crops the ~5-10% of the input image (depends on TV). I don't quite remember further details on this...
Thanks,
Vaibhav
Quoted 16 lines
Quoted 2 lines
Is there something I can do about this? I've looked at the timings in
drivers/video/omap2/dss/venc.cI don't know much about analog TV, but my understanding is that there's always overscanning going on. You just have to size and position the overlay so that it is visible on your TV.
Quoted 2 lines
Also, how can I select NTSC vs PAL setups via the command line? I have only the one video device VENC.
Documentation/arm/OMAP/DSSsays you can echo "pal" or "ntsc" to sys/devices/platform/omapdss/display?/timings file.Tomi