Vanilla kernel with real-time patch doesn't build for omap3 BBxM Ubuntu12.04

Hi,

I patched a vanilla kernel for realtime and configured it for omap3 beagle. However, after building it using make-kpkg with “DEB_HOST_ARCH=armhf CLEAN_SOURCE=no fakeroot make-kpkg --arch=arm --subarch=omap3 --cross-compile=arm-linux-gnueabihf- --initrd --append-to-version -xenomai-2.6.3-omap3 --revision 1.4 kernel_image kernel_headers”, synaptic tells me it’s armhf but no omap kernel. Despite searching, how should I patch this vanilla kernel for omap3 so it runs on the BBxM ?

Thank you.

I don’t have the answer, but I want the same thing as you: so come on and join to the party here, you’ll have more answers :

https://groups.google.com/d/topic/beagleboard/HqwuSu2tLe8/discussion

Don't use the "subarch" flag with make-kpkg, it's for something else, not
related to the "soc" family of arm devices..

Regards,

So I should use this exact build string, but without --subarch and will get an armhf kernel with omap3 ?

The answer to the first part should have been implied from my last email..

The second part, totally depends on what features you enabled for the
"omap3" devices in your kernel .config.

Regards,

I configured it generally for omap2+, omap3 and beagle. Should there be more features to enable to have it run on BBxM with Ubuntu Precise ?

More then likely yes.. But it depends on the kernel version.. So go
build/test/enable/rebuild/test/etc...

Regards,

Oh, I did. Have reconfigured, rebuilt and tested 4 times by now, and keep getting the dpkg message that it’s not an omap kernel.
I took vanilla kernel 3.5.7 because of a necessary patch that supports this version. Is there any other kernel version you can recommend for omap3 ?

Regards,

hvn

Hi,

I patched a vanilla kernel for realtime and configured it for omap3
beagle. However, after building it using make-kpkg with
"DEB_HOST_ARCH=armhf CLEAN_SOURCE=no fakeroot make-kpkg --arch=arm
--subarch=omap3 --cross-compile=arm-linux-gnueabihf- --initrd
--append-to-version -xenomai-2.6.3-omap3 --revision 1.4 kernel_image
kernel_headers", synaptic tells me it's armhf but no omap kernel. Despite
searching, how should I patch this vanilla kernel for omap3 so it runs on
the BBxM ?

Don't use the "subarch" flag with make-kpkg, it's for something else,
not related to the "soc" family of arm devices..

So I should use this exact build string, but without --subarch and
will get an armhf kernel with omap3 ?

The answer to the first part should have been implied from my last
email..

The second part, totally depends on what features you enabled for the
"omap3" devices in your kernel .config.

I configured it generally for omap2+, omap3 and beagle. Should there be
more features to enable to have it run on BBxM with Ubuntu Precise ?

More then likely yes.. But it depends on the kernel version.. So go
build/test/enable/rebuild/test/etc...

Oh, I did. Have reconfigured, rebuilt and tested 4 times by now, and keep
getting the dpkg message that it's not an omap kernel.

removing the "--subarch" crap will fix that...

I took vanilla kernel 3.5.7 because of a necessary patch that supports
this version. Is there any other kernel version you can recommend for omap3
?

v3.13.2 as it's the latest stable on kernel.org

Regards,

And which is the previous stable for omap3 that you recommend ?

Regards,

hvn

I took vanilla kernel 3.5.7 because of a necessary patch that supports
this version. Is there any other kernel version you can recommend for omap3
?

v3.13.2 as it's the latest stable on kernel.org

And which is the previous stable for omap3 that you recommend ?

v3.13.1

Regards,

OK. Can you tell me about the difference with regard to omap between 3.13.2, and e.g. 3.5.7 or 3.8.13 ? These are all stable kernels.

a few years of development.. Mostly has been the complete removal of the
classic board files to device tree's.. Checkout kernel.org for all details..

or:

git diff v3.5.7..v3.13.2

Regards,

OK, Thanks for your help.

Regards,

hvn

I have removed the “subarch” flag, and now I get the error message “Kernel <…> does not match your subarchitecture omap, therefore not writing it to flash.”. The running kernel (Ubuntu 12.04 omap armv7l) is v3.2.0-55-omap from repo. I noticed that the latest stable kernel indeed has a different configuration for omap. But I wonder, where does that message about “subarchitecture omap” really come from? The kernel configuration or the cross-compilation?

Hi,

I patched a vanilla kernel for realtime and configured it for omap3
beagle. However, after building it using make-kpkg with
"DEB_HOST_ARCH=armhf CLEAN_SOURCE=no fakeroot make-kpkg --arch=arm
--subarch=omap3 --cross-compile=arm-linux-gnueabihf- --initrd
--append-to-version -xenomai-2.6.3-omap3 --revision 1.4 kernel_image
kernel_headers", synaptic tells me it's armhf but no omap kernel. Despite
searching, how should I patch this vanilla kernel for omap3 so it runs on
the BBxM ?

Don't use the "subarch" flag with make-kpkg, it's for something else, not
related to the "soc" family of arm devices..

I have removed the "subarch" flag, and now I get the error message "Kernel
<.....> does not match your subarchitecture omap, therefore not writing it
to flash.".

Okay.. "not writing it to flash" your dealing with ubuntu's flash-kernel
script. So when you install a *.deb, dpkg calls "flash-kernel"...

It's a middle layer script that ubuntu wrote to "generically" install the
boot files to the correct location for a bunch of devices. Unless you run
ubuntu's kernel, it just gets in the way..

With my images:
http://elinux.org/BeagleBoardUbuntu#Demo_Image

I disable flash-kernel outright, as it always makes the wrong assumptions.

via:
https://github.com/RobertCNelson/omap-image-builder/blob/master/scripts/chroot.sh#L261

The running kernel (Ubuntu 12.04 omap armv7l) is v3.2.0-55-omap from repo.

I noticed that the latest stable kernel indeed has a different
configuration for omap. But I wonder, where does that message about
"subarchitecture omap" really come from? The kernel configuration or the
cross-compilation?

So good luck with dealing with the flash-kernel script..

Regards,