[PATCH openbmc 07/10] Add a kernel 4.6 recipe
Joel Stanley
joel at jms.id.au
Mon Jun 6 02:47:30 AEST 2016
On Sat, Jun 4, 2016 at 12:20 AM, OpenBMC Patches
<openbmc-patches at stwcx.xyz> wrote:
> From: Brad Bishop <bradleyb at fuzziesquirrel.com>
>
> Adding a 4.6 kernel recipe for the AST2500. AST2400 remains on
> 4.4.
We discussed this on IRC with Rick from Google. He would prefer us to
base the images on a released kernel, so we're what was my dev-4.7
tree rebased back down to 4.6.
The downside here is we now have three trees - 4.4 for the ast2400,
4.6 for the 2500 (but support is incomplete for eg. ftgmac100), and
4.7 for bringup and development.
I intend to clean up the 4.6 patchset and ensure it supports the
ast2500 and ast2400, and we will move to that. This way 4.6 can be our
stable tree, and I will continue to hack on 4.7-rc for bringup.
Once 4.7 is released we will move to that as our stable tree. The plan
is too keep in sync with upstream kernel releases at least until we
have the majority of our patches upstream. At that point we can pick a
long term supported kernel release and stick with that for some time.
This is a similar model that we have been using for the OpenPower
firmware and it is a nice balance between modern supported kernels and
managing workload.
> Signed-off-by: Brad Bishop <bradleyb at fuzziesquirrel.com>
> ---
> meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.6.bb | 5 +++++
> 1 file changed, 5 insertions(+)
> create mode 100644 meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.6.bb
>
> diff --git a/meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.6.bb b/meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.6.bb
> new file mode 100644
> index 0000000..b3891f4
> --- /dev/null
> +++ b/meta-phosphor/common/recipes-kernel/linux/linux-obmc_4.6.bb
> @@ -0,0 +1,5 @@
> +KBRANCH ?= "dev-4.6"
> +LINUX_VERSION ?= "4.6"
> +SRCREV="e377df455809d87488eed132b41583ead909f58a"
I'd prefer we point to a tag, so if we chose to rebase the kernel the
commit will not disappear.
I'll push a tag for you to use.
Cheers,
Joel
More information about the openbmc
mailing list