Build custom 3.0 kernel : latest omap integration OR linus + patches OR something else ?

GoogleGroups
1

Hi, for my own understanding of what's going on behind the OpenEmbedded scene I would like to compile a custom kernel (I mean, one that I can menuconfig)
I've got the OMAP 4 kernel (http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/OMAP_04_02/04_02_00_07/index_FDS.html) but it's a 2.6.37
I would like to give a try with a 3.0 kernel, because the driver of my wireless adapter is available in 3.0 branch, and because I've not been able to compile this module under a 2.6 tree

I've tried to manually apply patches stolen from the 3.0 OE recipes, on a vanilla 3.0.28 linus kernel
So far, I can't compile the kernel because some of the patches have been rejected (I suppose I've patched in a wrong order).

So, I understand that beagle/omap/arm patches for 3.0 branch are made available by individuals anywhere, but is there a place when I can find them collected ? And how to learn about the order the patches must be applied ?

To be honest, this is a little bit above my technical skills (and needs). Is there an easier solution ? Is there an TI/OMAP integration 3.0.X kernel somewhere ?
I just wan't to learn, and understand how the several TI SDK fit into the kernel build as modules.

Your advice is welcome !

PS : Should I stick with an easier/already up to date unbuntu kernel source ? And play with it, even if I use an Angstrom bitbaked root file system ?

2

Hi, for my own understanding of what's going on behind the OpenEmbedded
scene I would like to compile a custom kernel (I mean, one that I can
menuconfig)
I've got the OMAP 4 kernel
(Texas Instruments Linux Platform Support)
but it's a 2.6.37
I would like to give a try with a 3.0 kernel, because the driver of my
wireless adapter is available in 3.0 branch, and because I've not been able
to compile this module under a 2.6 tree

I've tried to manually apply patches stolen from the 3.0 OE recipes, on a
vanilla 3.0.28 linus kernel
So far, I can't compile the kernel because some of the patches have been
rejected (I suppose I've patched in a wrong order).

There's a little something still under development, that should
help... (note: it's functionally ready, not necessary feature
complete...)

git clone it, and then switch to the beagleboard-3.0 branch via:
git checkout origin/beagleboard-3.0 -b beagleboard-3.0
then issue "./patch.sh"

The either use the new git generated "kernel" directory as is, as
it'll be a fully patched 3.0.X kernel with an angstrom patchset, or
use the git am-able patchset under "export" with the patch_script.sh

So, I understand that beagle/omap/arm patches for 3.0 branch are made
available by individuals anywhere, but is there a place when I can find them
collected ? And how to learn about the order the patches must be applied ?

To be honest, this is a little bit above my technical skills (and needs). Is
there an easier solution ? Is there an TI/OMAP integration 3.0.X kernel
somewhere ?
I just wan't to learn, and understand how the several TI SDK fit into the
kernel build as modules.

Your advice is welcome !

PS : Should I stick with an easier/already up to date unbuntu kernel source
? And play with it, even if I use an Angstrom bitbaked root file system ?

linux is linux, about 99% of the time, it'll boot just fine, the other
is usually just a missing config setting, or your using a
source/kernel version that's considered ancient..

Regards,

3

Thank you for your answer Robert !

Is it better to go to this 3.2 branch than keeping on the 3.0 ? I mean considering my ultimate goal (sound, opengl, 720p video dsp, omapfb), which I've not been able to reach until now (I've never been able to watch dsp decoded video stream, and the only omapfb player that I know to run well is omapfbplay but which is pretty limited speaking about external control (compared to something like mplayer for example).

I know this stuff is not really related with the kernel, but it seems to me that I need to understand how to cross compile by hand
1) the kernel + needed modules
2) the TI GFX DSK, so PVR modules
3) the DSP link DSK modules
4) TI gstreamer
5) libgles with hardware accel
6) qt4 embedded with opengl (libgles) support
7) irrlicht (3D engine) with qt4 embedded support

1) because needed for 2) & 3)
3) because I don't understand for now why I can't get 4) running
6) because 7) need it

4

Hi, for my own understanding of what's going on behind the OpenEmbedded
scene I would like to compile a custom kernel (I mean, one that I can
menuconfig)
I've got the OMAP 4 kernel

(Texas Instruments Linux Platform Support)
but it's a 2.6.37
I would like to give a try with a 3.0 kernel, because the driver of my
wireless adapter is available in 3.0 branch, and because I've not been
able
to compile this module under a 2.6 tree

I've tried to manually apply patches stolen from the 3.0 OE recipes, on a
vanilla 3.0.28 linus kernel
So far, I can't compile the kernel because some of the patches have been
rejected (I suppose I've patched in a wrong order).

There's a little something still under development, that should
help... (note: it's functionally ready, not necessary feature
complete...)

GitHub - beagleboard/kernel: Kernel for the beagleboard.org boards

Thank you for your answer Robert !

Is it better to go to this 3.2 branch than keeping on the 3.0 ? I mean

It depends, if you want Angstrom's 3.0, use the 3.0.. If you'd like
to use what i've been pushing out to ubuntu/debian users with my demo
images, well that's the 3.2... But now going forward, there should be
more unification. :wink:

considering my ultimate goal (sound, opengl, 720p video dsp, omapfb), which
I've not been able to reach until now (I've never been able to watch dsp
decoded video stream, and the only omapfb player that I know to run well is
omapfbplay but which is pretty limited speaking about external control
(compared to something like mplayer for example).

I know this stuff is not really related with the kernel, but it seems to me
that I need to understand how to cross compile by hand
1) the kernel + needed modules
2) the TI GFX DSK, so PVR modules
3) the DSP link DSK modules

Note, 2,3 depending on the versions, will probally need a few patches
here or their depending on the kernel version... I know a #3, would
be a welcome elinux wiki article, specially with a mainline kernel,
going thru every step with the different ti's software requirements..

4) TI gstreamer
5) libgles with hardware accel
6) qt4 embedded with opengl (libgles) support
7) irrlicht (3D engine) with qt4 embedded support

1) because needed for 2) & 3)
3) because I don't understand for now why I can't get 4) running
6) because 7) need it

Regards,

5

Yes, this make sense... It's better for me to stay with Angstrom 3.0 and tune the kernel 3.0.x and modules.

Just a little help about the 3.0 kernel cloned and patched by ./patch.sh :

I can't find a beagle conf in arch/arm/configs and the beagle is not listed in menuconfig 'system type' / 'ARM system type'

Where can I find the default config file ? (May be I could use one I've found in OE recipe but it's for 3.0.22)

6

Sorry, I missed the config file in patches\beagleboard
Copied into arm/configs - Seems to be fine