[PATCH openbmc] Force OLDEST_KERNEL to 4.4.0

[PATCH openbmc] Force OLDEST_KERNEL to 4.4.0

[OpenBMC Patches]

This is the oldest kernel currently used by openbmc, so there is no
point in compiling glibc support older kernels.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/openbmc/openbmc/425)
<!-- Reviewable:end -->


https://github.com/openbmc/openbmc/pull/425

Patrick Williams (1):
  Force OLDEST_KERNEL to 4.4.0

 meta-phosphor/conf/distro/openbmc-phosphor.conf | 1 +
 1 file changed, 1 insertion(+)

-- 
2.9.0

[PATCH openbmc] Force OLDEST_KERNEL to 4.4.0

[OpenBMC Patches]

From: Patrick Williams <patrick@stwcx.xyz>

This is the oldest kernel currently used by openbmc, so there is no
point in compiling glibc support older kernels.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
---
 meta-phosphor/conf/distro/openbmc-phosphor.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-phosphor/conf/distro/openbmc-phosphor.conf b/meta-phosphor/conf/distro/openbmc-phosphor.conf
index f37e88c..b4e6f7a 100644
--- a/meta-phosphor/conf/distro/openbmc-phosphor.conf
+++ b/meta-phosphor/conf/distro/openbmc-phosphor.conf
@@ -5,6 +5,7 @@ DISTRO_NAME = "Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
 DISTRO_VERSION = "0.1.0"
 TARGET_VENDOR="-openbmc"
 
+OLDEST_KERNEL = "4.4.0"
 GCCVERSION ?= "4.9.3"
 IMAGE_FSTYPES += "cpio.gz"
 IMAGE_FSTYPES += "squashfs-xz"
-- 
2.9.0

Re: [PATCH openbmc] Force OLDEST_KERNEL to 4.4.0

[Joel Stanley]

On Thu, Jun 30, 2016 at 8:10 AM, OpenBMC Patches
<openbmc-patches@stwcx.xyz> wrote:
> From: Patrick Williams <patrick@stwcx.xyz>
>
> This is the oldest kernel currently used by openbmc, so there is no
> point in compiling glibc support older kernels.

Sounds good. Buildroot does the same thing for our firmware builds on the host.

Is there any way to use the actual kernel version to set this variable?

>
> Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
> ---
>  meta-phosphor/conf/distro/openbmc-phosphor.conf | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/meta-phosphor/conf/distro/openbmc-phosphor.conf b/meta-phosphor/conf/distro/openbmc-phosphor.conf
> index f37e88c..b4e6f7a 100644
> --- a/meta-phosphor/conf/distro/openbmc-phosphor.conf
> +++ b/meta-phosphor/conf/distro/openbmc-phosphor.conf
> @@ -5,6 +5,7 @@ DISTRO_NAME = "Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
>  DISTRO_VERSION = "0.1.0"
>  TARGET_VENDOR="-openbmc"
>
> +OLDEST_KERNEL = "4.4.0"
>  GCCVERSION ?= "4.9.3"
>  IMAGE_FSTYPES += "cpio.gz"
>  IMAGE_FSTYPES += "squashfs-xz"
> --
> 2.9.0
>
>
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc

Re: [PATCH openbmc] Force OLDEST_KERNEL to 4.4.0

[Patrick Williams]

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]

On Thu, Jun 30, 2016 at 05:26:29PM +0930, Joel Stanley wrote:
> On Thu, Jun 30, 2016 at 8:10 AM, OpenBMC Patches
> <openbmc-patches@stwcx.xyz> wrote:
> > From: Patrick Williams <patrick@stwcx.xyz>
> >
> > This is the oldest kernel currently used by openbmc, so there is no
> > point in compiling glibc support older kernels.
> 
> Sounds good. Buildroot does the same thing for our firmware builds on the host.
> 
> Is there any way to use the actual kernel version to set this variable?
> 

I might be able to set OLDEST_KERNEL in terms of LINUX_KERNEL.  Is that
what we want?  I have a little concern that this might affect certain
use cases of code upgrade (or downgrade) and netbooting.

The saving for this setting ended up being pretty insignificant.  About
7k from glibc.  I can either leave this as something we change for
"major" upgrades of openBMC or attempt to set it in terms of the
LINUX_KERNEL variable.

> >
> > Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
> > ---
> >  meta-phosphor/conf/distro/openbmc-phosphor.conf | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/meta-phosphor/conf/distro/openbmc-phosphor.conf b/meta-phosphor/conf/distro/openbmc-phosphor.conf
> > index f37e88c..b4e6f7a 100644
> > --- a/meta-phosphor/conf/distro/openbmc-phosphor.conf
> > +++ b/meta-phosphor/conf/distro/openbmc-phosphor.conf
> > @@ -5,6 +5,7 @@ DISTRO_NAME = "Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
> >  DISTRO_VERSION = "0.1.0"
> >  TARGET_VENDOR="-openbmc"
> >
> > +OLDEST_KERNEL = "4.4.0"
> >  GCCVERSION ?= "4.9.3"
> >  IMAGE_FSTYPES += "cpio.gz"
> >  IMAGE_FSTYPES += "squashfs-xz"
> > --
> > 2.9.0
> >
> >
> > _______________________________________________
> > openbmc mailing list
> > openbmc@lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/openbmc

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [PATCH openbmc] Force OLDEST_KERNEL to 4.4.0

[Rick Altherr]

[-- Attachment #1: Type: text/plain, Size: 2282 bytes --]

Until we understand the upgrade scenarios better, I prefer to leave it
fixed to the earliest released kernel version.

On Tue, Jul 5, 2016 at 12:47 PM, Patrick Williams <patrick@stwcx.xyz> wrote:

> On Thu, Jun 30, 2016 at 05:26:29PM +0930, Joel Stanley wrote:
> > On Thu, Jun 30, 2016 at 8:10 AM, OpenBMC Patches
> > <openbmc-patches@stwcx.xyz> wrote:
> > > From: Patrick Williams <patrick@stwcx.xyz>
> > >
> > > This is the oldest kernel currently used by openbmc, so there is no
> > > point in compiling glibc support older kernels.
> >
> > Sounds good. Buildroot does the same thing for our firmware builds on
> the host.
> >
> > Is there any way to use the actual kernel version to set this variable?
> >
>
> I might be able to set OLDEST_KERNEL in terms of LINUX_KERNEL.  Is that
> what we want?  I have a little concern that this might affect certain
> use cases of code upgrade (or downgrade) and netbooting.
>
> The saving for this setting ended up being pretty insignificant.  About
> 7k from glibc.  I can either leave this as something we change for
> "major" upgrades of openBMC or attempt to set it in terms of the
> LINUX_KERNEL variable.
>
> > >
> > > Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
> > > ---
> > >  meta-phosphor/conf/distro/openbmc-phosphor.conf | 1 +
> > >  1 file changed, 1 insertion(+)
> > >
> > > diff --git a/meta-phosphor/conf/distro/openbmc-phosphor.conf
> b/meta-phosphor/conf/distro/openbmc-phosphor.conf
> > > index f37e88c..b4e6f7a 100644
> > > --- a/meta-phosphor/conf/distro/openbmc-phosphor.conf
> > > +++ b/meta-phosphor/conf/distro/openbmc-phosphor.conf
> > > @@ -5,6 +5,7 @@ DISTRO_NAME = "Phosphor OpenBMC (Phosphor OpenBMC
> Project Reference Distro)"
> > >  DISTRO_VERSION = "0.1.0"
> > >  TARGET_VENDOR="-openbmc"
> > >
> > > +OLDEST_KERNEL = "4.4.0"
> > >  GCCVERSION ?= "4.9.3"
> > >  IMAGE_FSTYPES += "cpio.gz"
> > >  IMAGE_FSTYPES += "squashfs-xz"
> > > --
> > > 2.9.0
> > >
> > >
> > > _______________________________________________
> > > openbmc mailing list
> > > openbmc@lists.ozlabs.org
> > > https://lists.ozlabs.org/listinfo/openbmc
>
> --
> Patrick Williams
>
> _______________________________________________
> openbmc mailing list
> openbmc@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc
>
>

[-- Attachment #2: Type: text/html, Size: 3571 bytes --]