Hello group,
a rather newbie-ish question. I created my own customized Debian Wheezy system for a Beagleboard xM from armhf builds at rcn-ee.net (specifically: debian-7.4-console-armhf).
Now I am happy with all the tweaks I’ve done so far in the last months but I’d like to upgrade the kernel to a 3.14 release, in order to make use of the new SCHED_DEADLINE.
There are no backports of linux 3.14 for Wheezy but there are Jessie packages for linux-headers-3.14-1-all linux-headers-3.14-1-common linux-headers-3.14-1-all-armhf etc.
What’s the best option to upgrade the kernel? Tweeak /etc/apt/sources.list to add Jessie repos or trying compile it natively (I’m too lazy for setting up a cross-compile chain).
Also, once I’ve got them compiled, I guess I should modify the BOOT partition of my uSD card to point to the proper image? An outline of the steps would be immensely appreciated!
Regards
Leonardo
Hello group,
a rather newbie-ish question. I created my own customized Debian Wheezy
system for a Beagleboard xM from armhf builds at rcn-ee.net (specifically:
debian-7.4-console-armhf).
Now I am happy with all the tweaks I've done so far in the last months but
I'd like to upgrade the kernel to a 3.14 release, in order to make use of
the new SCHED_DEADLINE.
There are no backports of linux 3.14 for Wheezy but there are Jessie
packages for linux-headers-3.14-1-all linux-headers-3.14-1-common
linux-headers-3.14-1-all-armhf etc.
What's the best option to upgrade the kernel? Tweeak /etc/apt/sources.list
to add Jessie repos or trying compile it natively (I'm too lazy for setting
up a cross-compile chain).
I don't think Jessie's 3.14-1 will boot the xm..
or just use this branch:
with your config tweak and really easy to copy the kernel files:
http://eewiki.net/display/linuxonarm/BeagleBoard#BeagleBoard-CopyKernelFiles
Also, once I've got them compiled, I guess I should modify the BOOT
partition of my uSD card to point to the proper image? An outline of the
steps would be immensely appreciated!
Pretty straight forward:
zImage/vmlinux -> /boot/uboot/zImage
dtbs -> /boot/uboot/dtbs
modules -> /lib/modules/
Regards,
Thank you I’ve been trying out this option. Actually I started this project with your custom images, so thumbs up
I’ve opted for a native compile on the BBxm with your scripts (on an additional SD card to have enough space).
When git fetches from https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable
and tags, e.g.:
- [new tag] v3.9.9 → v3.9.9
I get:
error: Your local changes to the following files would be overwritten by checkout:
tools/testing/selftests/rcutorture/configs/rcu/v3.12/P7-4-T-NH-SD-SMP-HP
Please, commit your changes or stash them before you can switch branches.
Aborting
I’m not very familiar with git, but I’ll try to follow the script step by step to find this out. However if you have an insight or quick suggestion please let me know.
Also: when I first tried the script, on the root file system microSD the compile process started and I didn’t have git problems. I had to stop unfortunately, since the uSD space was almost over. I’m wondering whether I screwed up something with git.
Regards
Dear Robert,
could you explain how are the tags and branches generated in your repo? Maybe it’s a silly question but could you elaborate a bit on the naming convention?
How is e.g. the tag 3.15-rc8-armv7-x1 related to the branch 3.15.1-armv7-x2?
Thanks
The x1 -> x2 means it was more then just a kernel jump.
I added 3 kernel patches + a config change between those versions:
https://github.com/RobertCNelson/armv7-multiplatform/commits/v3.15.x
I usually (if i remember) bump the (y) portion of the build number:
x.y between commits:
https://github.com/RobertCNelson/armv7-multiplatform/commit/c70c034e9cb75083f59d0559552cc605bbe3b8b0
Regards,
Ok, so the first part is just the vanilla kernel versioning, while the -x is your own numbering, correct?
Regards