Video output to S-Video

Hi everyone,
Is it possible to get the video output directed to S-Video instead of
DVI-D... I am running the Angstrom Demo image.

Regards
-Nitin

If you use the 2.8.28rcX uImages that were posted to this list earlier you can get s-video support.

regards,

Koen

Thanks a lot…

-Nitin

Thanks a lot...

For havinf different outputs on dvi and s-video you could use this
script to enable s-video (from Tomba, the father of DSS2):

tvline=`cat /sys/devices/platform/omapfb/displays |grep tv`
w=`echo $tvline | cut -d " " -f 2 | cut -d ":" -f 2`
h=`echo $tvline | cut -d " " -f 3 | cut -d ":" -f 2`

echo "vid1 t:none" > /sys/devices/platform/omapfb/overlays
fbset -fb /dev/fb1 -xres $w -vxres $w -yres $h -vyres $h
echo "vid1 t:tv w:$w h:$h e:1" > /sys/devices/platform/omapfb/overlays
echo "tv e:1" > /sys/devices/platform/omapfb/displays

What it does is:

Hi,Robert

How did you make the uImage with the S-video patch?
which linux kernel did you use?
I git the kernel from
http://www.bat.org/~tomba/git/linux-omap-dss.git/
and compiled it to the uImage, but when i boot it, i cant see "omapfb"
exist in /sys/devices/platform/.
so i thought i should add patch into the DSS kernel, but the version
seems not right, i got some patch and compling errors.
am i right?

And, i have a question : the patch seems only support OMAP3430 instead
of OMAP 3530 which Beagleboard is using.

Thanks.
Liahoo

How did you make the uImage with the S-video patch?
which linux kernel did you use?
I git the kernel from
http://www.bat.org/~tomba/git/linux-omap-dss.git/

What kernle config do you use? You has to enable DSS2 in the kernel
config. Its under driver->graphics (or something like that).

The kernel from the above side has all necessary. It is from the
creater of DSS2.

HTH.

Robert

Hi Robert!

Thanks for your help!
i got the config file and succeeded to build the uImage.
after this, i made a change for Android RootFS.
just patch Android support into the kernel(DSS) from this site:
http://sites.google.com/site/voyageofbeagleboard/how-to-make-kernel

and , i merged you configfile to the "omap3_beagle_android_defconfig"
which is created by the patch.
it was compiled all right, and i could start the android by typing the
"ls" command.

But when i typed the command , i couldn't see the S-Video output
anything.
my steps are:
1, git the kernel from
http://www.bat.org/~tomba/git/linux-omap-dss.git/
2, merge kernel config to omap3_beagle_defconfig.
3, get android patch from
http://sites.google.com/site/voyageofbeagleboard/how-to-make-kernel
4, patch the file to kernel
5, merge omap3_beagle_defconfig to omap3_beagle_android_defconfig.
6, make the image with omap3_beagle_android_defconfig.
7, use the uImage and boot with Android rootFS which i made before
like this site:
http://labs.embinux.org/android-porting-on-beagle.html
8, connect beagleboard S-Video...
9, boot Android.
10,when i typed the commands like "echo "vid1 t:none" > overlays ", i
got nothing output in S-Video.

Any ideas?

Best Regards!
Hu Liang.

But when i typed the command , i couldn't see the S-Video output
anything.
my steps are:
1, git the kernel from
http://www.bat.org/~tomba/git/linux-omap-dss.git/
2, merge kernel config to omap3_beagle_defconfig.

What does
  grep DSS .config
or
  grep DSS omap3_beagle_defconfig
outputs?

The relevant setting is CONFIG_OMAP2_DSS

Robert

What does
  grep DSS .config
or
  grep DSS omap3_beagle_defconfig
outputs?

Sorry,i cant use the S-Video device right now. but in command line, it
appears:

# tvline=`cat /sys/devices/platform/omapfb/displays |grep DSS .config`
grep: not found
# tvline=`cat /sys/devices/platform/omapfb/displays | grep
DSS .config`
grep: not found
# tvline=`cat /sys/devices/platform/omapfb/displays |grep
omap3_beagle_android_defconfig`
grep: not found
# tvline=`cat /sys/devices/platform/omapfb/displays | grep
omap3_beagle_android_defconfig`
grep: not found
# tvline=`cat /sys/devices/platform/omapfb/displays |grep
omap3_beagle_defconfig`
grep: not found
# tvline=`cat /sys/devices/platform/omapfb/displays | grep
omap3_beagle_defconfig`
grep: not found

Actually, i met it at the first time with "tvline=`cat /sys/devices/
platform/omapfb/displays |grep tv`"
But i changed the symbol ` to ' :frowning:
So i think i made a mistake about the ` symbol...
But how about the "grep: not found" issue to fix?

The relevant setting is CONFIG_OMAP2_DSS

i opened CONFIG_OMAP2_DSS before i compiled the kernel:
CONFIG_OMAP2_DSS=y
# CONFIG_OMAP2_DSS_DEBUG is not set
# CONFIG_OMAP2_DSS_RFBI is not set
CONFIG_OMAP2_DSS_VENC=y
# CONFIG_OMAP2_DSS_SDI is not set
# CONFIG_OMAP2_DSS_DSI is not set
# CONFIG_OMAP2_DSS_FAKE_VSYNC is not set
CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=4
CONFIG_ARCH_OMAP34XX=y
CONFIG_ARCH_OMAP3430=y

by the way ,can you tell me how to upload a file like my configfile?

Best Regards!
Hu Liang

What does
  grep DSS .config
or
  grep DSS omap3_beagle_defconfig
outputs?

You are right!
grep command is not supported by Android RootFS , so i got errorlog
like "grep: not found".
Any ideas for adding the commands of Linux to Android RootFS?

Hu Liang wrote:

What does
  grep DSS .config
or
  grep DSS omap3_beagle_defconfig
outputs?

You are right!
grep command is not supported by Android RootFS , so i got errorlog
like "grep: not found".
Any ideas for adding the commands of Linux to Android RootFS?

try grep on your PC, not the android :wink:

Hi Vladimir,

Actually i tried grep in u-boot on my PC connected to Beagleboard with
series line.
When Android is started, i can type simple command as "ls" in android
command environment,
which is the same as the command line by "adb shell" in PC.

i think there is no "grep" in android's commands, so i want to add
some into it.

Best Regards!
Hu Liang.

Hi Robert,

i made the grep and cut command available by putting a busybox into
android rootfs.
and my log is:

# tvline=`cat /sys/devices/platform/omapfb/displays |grep tv`
# w=`echo $tvline | cut -d " " -f 2 | cut -d ":" -f 2`
# h=`echo $tvline | cut -d " " -f 3 | cut -d ":" -f 2`

# echo "1 t:none" > framebuffers
# echo "0 t:gfx,vid1" > framebuffers
# echo "gfx e:1" > overlays
# echo "vid1 t:tv w:$w h:$h e:1" > overlays
omapfb omapfb: enable overlay failed
# echo "tv e:1" > displays

i think the grep command from android's busybox didnt works.
i tried:
# ln -s /system/bin/busybox grep
# ln -s /system/bin/busybox cut
# tvline=`cat /sys/devices/platform/omapfb/displays |grep tv`
# echo $tvline