a bit closer

This commit is contained in:
Ciro Santilli
2018-02-13 16:09:16 +00:00
parent d97d461605
commit 64130ecfb9
22 changed files with 316 additions and 569 deletions

View File

@@ -1,8 +1,6 @@
[[maintainers]]
= Maintainers
=== Maintainers
[[how-to-update-the-linux-kernel]]
== How to update the Linux kernel?
==== How to update the Linux kernel?
....
# Last point before out patches.
@@ -30,29 +28,21 @@ git push
and update the README!
During update all you kernel modules may break since the kernel API is
not stable.
During update all you kernel modules may break since the kernel API is not stable.
They are usually trivial breaks of things moving around headers or to
sub-structs.
They are usually trivial breaks of things moving around headers or to sub-structs.
The userland, however, should simply not break, as Linus enforces strict
backwards compatibility of userland interfaces.
The userland, however, should simply not break, as Linus enforces strict backwards compatibility of userland interfaces.
This backwards compatibility is just awesome, it makes getting and
running the latest master painless.
This backwards compatibility is just awesome, it makes getting and running the latest master painless.
This also makes this repo the perfect setup to develop the Linux kernel.
[[how-to-downgrade-the-linux-kernel]]
== How to downgrade the Linux kernel?
==== How to downgrade the Linux kernel?
The kernel is not forward compatible, however, so downgrading the Linux
kernel requires downgrading the userland too to the latest Buildroot
branch that supports it.
The kernel is not forward compatible, however, so downgrading the Linux kernel requires downgrading the userland too to the latest Buildroot branch that supports it.
The default Linux kernel version is bumped in Buildroot with commit
messages of type:
The default Linux kernel version is bumped in Buildroot with commit messages of type:
....
linux: bump default to version 4.9.6
@@ -64,15 +54,11 @@ So you can try:
git log --grep 'linux: bump default to version'
....
Those commits change `BR2_LINUX_KERNEL_LATEST_VERSION` in
`/linux/Config.in`.
Those commits change `BR2_LINUX_KERNEL_LATEST_VERSION` in `/linux/Config.in`.
You should then look up if there is a branch that supports that kernel.
Staying on branches is a good idea as they will get backports, in
particular ones that fix the build as newer host versions come out.
You should then look up if there is a branch that supports that kernel. Staying on branches is a good idea as they will get backports, in particular ones that fix the build as newer host versions come out.
[[how-to-add-new-buildroot-options]]
== How to add new Buildroot options?
==== How to add new Buildroot options?
....
cd buildroot/output.x86_64~