I'm new to the BeagleBoard and OpenEmbedded and still try to understand
how things work. I'm using OpenEmbedded and the angstrom distribution on
the BeagleBoard.
So far I have checked out the oe git-repository and created a
configuration file for the BeagleBoard, everything worked well. Then I
built the target 'console-image' ('beagleboard-demo-image' will be next)
and got a working linux image. Everything great so far :-)
Now for the beginner questions ...
1. How do I control which kernel is used? (or 'understanding the oe
structure')
First of all, I'm not sure how to set the used kernel. I couldn't find
any hint in the build-files about which kernel is used, or a dependency
to it, e.g. in packages/images/beagleboard-demo-image.bb, or
packages/tasks/... etc. Where do I find this info and how would I go
about changing it, when I want to use another kernel instead?
2. How to apply a kernel patch?
How exactly can I apply a kernel patch? Is it enough to copy a
.patch-file into the appropriate kernel directory, e.g.
'openembedded/packages/linux/linux-omap2-git', and do I have to edit the
corresponding .bb file for that kernel and add the patch to it? I've
tried both but didn't succeed ...
3. Getting S-VIDEO to work
I know this topic has already been discussed some time ago, but I'm a
bit lost on how to apply the various solutions, so let me ask again. I
understand that the current omap-kernel doesn't have the S-VIDEO support
yet. But there are some patches out there to enable it (although those
are not recommended and a new driver is being developed). So, what would
be the recommended way to enable S-VIDEO support with a current kernel,
until the new driver is working? And if it is to use a new kernel
(2.6.28) - what would be the best way to add that kernel, as it doesn't
seem to be in the repository yet?
Thanks,
Stefan
Look at conf/machine/beagleboard.conf
>
> 2. How to apply a kernel patch?
>
> How exactly can I apply a kernel patch? Is it enough to copy a
> .patch-file into the appropriate kernel directory, e.g.
> 'openembedded/packages/linux/linux-omap2-git', and do I have to edit the
> corresponding .bb file for that kernel and add the patch to it? I've
> tried both but didn't succeed ...
Look at packages/linux/linux-omap_git.bb (Assuming beagleboard.conf is
using linux-omap, which I think it is at the moment)
>
> 3. Getting S-VIDEO to work
>
> I know this topic has already been discussed some time ago, but I'm a
> bit lost on how to apply the various solutions, so let me ask again. I
> understand that the current omap-kernel doesn't have the S-VIDEO support
> yet. But there are some patches out there to enable it (although those
> are not recommended and a new driver is being developed). So, what would
> be the recommended way to enable S-VIDEO support with a current kernel,
> until the new driver is working? And if it is to use a new kernel
> (2.6.28) - what would be the best way to add that kernel, as it doesn't
> seem to be in the repository yet?
Sorry, I do not know this one.
Philip
> 3. Getting S-VIDEO to work
>
> I know this topic has already been discussed some time ago, but I'm a
> bit lost on how to apply the various solutions, so let me ask again. I
> understand that the current omap-kernel doesn't have the S-VIDEO support
A new system called DSS2 will be integrated in linux-omap whcih
support s-video. Until that you can use the "oe"-kernel which has the
dss2-patches.
Then for having 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:
> 1. disconnect vid1 overlay, so that we can change it freely
> 2. set the framebuffer fb1 to correct size (it is already connected to
> vid1, by default, so we don't need to connect it)
> 3. set vid1 output to tv overlay manager, and set output size to tv's
> size
> 4. enable tv display
Robert