Yocto 2.2 minimum kernel requirement

Yocto 2.2 minimum kernel requirement

[Vuille, Martin (Martin)]

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

We are looking at upgrading from Yocto 1.8 to 2.2.

Yocto 2.2 has a minimum kernel requirement of 3.2.0.

This isn't an issue for our target (ARMv5, Linux 4.4) but may be
an issue for our automated build machines (x86, Linux 2.6.32-CentOS 6.)

However, there is a note that says
"For x86 and x86_64, you can reset OLDEST_KERNEL<http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#var-OLDEST_KERNEL> to anything down to 2.6.32 if desired."

Is it possible to configure things such that we can keep supporting the old
kernel for the SDK while we support a more up-to-date kernel for the target?

MV

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

Re: Yocto 2.2 minimum kernel requirement

[Vuille, Martin (Martin)]

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

I should clarify that these build machines are not for Yocto builds,
but for building an application that uses the Yocto SDK.

From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Vuille, Martin (Martin)
Sent: October 31, 2016 10:38
To: yocto@yoctoproject.org
Subject: [yocto] Yocto 2.2 minimum kernel requirement

We are looking at upgrading from Yocto 1.8 to 2.2.

Yocto 2.2 has a minimum kernel requirement of 3.2.0.

This isn't an issue for our target (ARMv5, Linux 4.4) but may be
an issue for our automated build machines (x86, Linux 2.6.32-CentOS 6.)

However, there is a note that says
"For x86 and x86_64, you can reset OLDEST_KERNEL<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.yoctoproject.org_docs_2.2_mega-2Dmanual_mega-2Dmanual.html-23var-2DOLDEST-5FKERNEL&d=DQMFAg&c=BFpWQw8bsuKpl1SgiZH64Q&r=SbT_XjBLTrjzWy1iRhblzG3bKRhcodBp7tD_mnp1dpg&m=JBfbjyLEHgQmBZGcIm8lb9q00p7ApivpoxD9UIz8BE0&s=UevjhjTvolaxefVicfpOrA5-ShXGU7YBHo7bUeDG3OQ&e=> to anything down to 2.6.32 if desired."

Is it possible to configure things such that we can keep supporting the old
kernel for the SDK while we support a more up-to-date kernel for the target?

MV

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

Re: Yocto 2.2 minimum kernel requirement

[Khem Raj]

[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]


> On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) <vmartin@avaya.com> wrote:
> 
> We are looking at upgrading from Yocto 1.8 to 2.2.
> 
> Yocto 2.2 has a minimum kernel requirement of 3.2.0.
> 
> This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
> an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
> 
> However, there is a note that says
> “For x86 and x86_64, you can reset OLDEST_KERNEL <http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#var-OLDEST_KERNEL> to anything down to 2.6.32 if desired.”
> 
> Is it possible to configure things such that we can keep supporting the old
> kernel for the SDK while we support a more up-to-date kernel for the target?

I think that should be the default. We do not set it for x86/nativesdk case. File a ticket if thats not
the case.

> 
> MV
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>

[-- Attachment #1.2: Type: text/html, Size: 7924 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

Re: Yocto 2.2 minimum kernel requirement

[Paul Eggleton]

On Mon, 31 Oct 2016 09:37:07 Khem Raj wrote:
> > On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) <vmartin@avaya.com>
> > wrote:
> > 
> > We are looking at upgrading from Yocto 1.8 to 2.2.
> > 
> > Yocto 2.2 has a minimum kernel requirement of 3.2.0.
> > 
> > This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
> > an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
> > 
> > However, there is a note that says
> > “For x86 and x86_64, you can reset OLDEST_KERNEL
> > <http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#var-OL
> > DEST_KERNEL> to anything down to 2.6.32 if desired.”
> > 
> > Is it possible to configure things such that we can keep supporting the
> > old kernel for the SDK while we support a more up-to-date kernel for the
> > target?
>
> I think that should be the default. We do not set it for x86/nativesdk case.
> File a ticket if thats not the case.

SDK_OLDEST_KERNEL is the variable that's supposed to be controlling this, but 
I noticed a couple of weeks ago that we aren't feeding SDK_OLDEST_KERNEL into 
glibc for nativesdk, so we should fix that - I've filed a bug [1] and will 
sort that out. I think we should probably set the SDK_OLDEST_KERNEL default 
for x86 to 2.6.32 at the same time - I assume there are no objections?

Cheers,
Paul

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10561

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Yocto 2.2 minimum kernel requirement

[Khem Raj]

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


> On Oct 31, 2016, at 2:59 PM, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> 
> On Mon, 31 Oct 2016 09:37:07 Khem Raj wrote:
>>> On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) <vmartin@avaya.com>
>>> wrote:
>>> 
>>> We are looking at upgrading from Yocto 1.8 to 2.2.
>>> 
>>> Yocto 2.2 has a minimum kernel requirement of 3.2.0.
>>> 
>>> This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
>>> an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
>>> 
>>> However, there is a note that says
>>> “For x86 and x86_64, you can reset OLDEST_KERNEL
>>> <http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#var-OL
>>> DEST_KERNEL> to anything down to 2.6.32 if desired.”
>>> 
>>> Is it possible to configure things such that we can keep supporting the
>>> old kernel for the SDK while we support a more up-to-date kernel for the
>>> target?
>> 
>> I think that should be the default. We do not set it for x86/nativesdk case.
>> File a ticket if thats not the case.
> 
> SDK_OLDEST_KERNEL is the variable that's supposed to be controlling this, but
> I noticed a couple of weeks ago that we aren't feeding SDK_OLDEST_KERNEL into
> glibc for nativesdk, so we should fix that - I've filed a bug [1] and will
> sort that out. I think we should probably set the SDK_OLDEST_KERNEL default
> for x86 to 2.6.32 at the same time - I assume there are no objections?

Yes, its for nativesdk/glibc, I think for target x86 we should keep 3.2

> 
> Cheers,
> Paul
> 
> [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10561
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

Re: Yocto 2.2 minimum kernel requirement

[Paul Eggleton]

On Mon, 31 Oct 2016 15:36:24 Khem Raj wrote:
> > On Oct 31, 2016, at 2:59 PM, Paul Eggleton <paul.eggleton@linux.intel.com>
> > wrote:> 
> > On Mon, 31 Oct 2016 09:37:07 Khem Raj wrote:
> >>> On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) <vmartin@avaya.com>
> >>> wrote:
> >>> 
> >>> We are looking at upgrading from Yocto 1.8 to 2.2.
> >>> 
> >>> Yocto 2.2 has a minimum kernel requirement of 3.2.0.
> >>> 
> >>> This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
> >>> an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
> >>> 
> >>> However, there is a note that says
> >>> “For x86 and x86_64, you can reset OLDEST_KERNEL
> >>> <http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#var-O
> >>> L
> >>> DEST_KERNEL> to anything down to 2.6.32 if desired.”
> >>> 
> >>> Is it possible to configure things such that we can keep supporting the
> >>> old kernel for the SDK while we support a more up-to-date kernel for the
> >>> target?
> >> 
> >> I think that should be the default. We do not set it for x86/nativesdk
> >> case. File a ticket if thats not the case.
> > 
> > SDK_OLDEST_KERNEL is the variable that's supposed to be controlling this,
> > but I noticed a couple of weeks ago that we aren't feeding
> > SDK_OLDEST_KERNEL into glibc for nativesdk, so we should fix that - I've
> > filed a bug [1] and will sort that out. I think we should probably set
> > the SDK_OLDEST_KERNEL default for x86 to 2.6.32 at the same time - I
> > assume there are no objections?
>
> Yes, its for nativesdk/glibc, I think for target x86 we should keep 3.2

Right, I'm not proposing changing the target value.

It turns out setting SDK_OLDEST_KERNEL in an arch-specific manner is a little 
awkward since there aren't overrides that can be used for the SDK value, but 
we can do it from conf/machine-sdk/*.conf though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Yocto 2.2 minimum kernel requirement

[Khem Raj]

On Mon, Oct 31, 2016 at 3:44 PM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Mon, 31 Oct 2016 15:36:24 Khem Raj wrote:
>> > On Oct 31, 2016, at 2:59 PM, Paul Eggleton <paul.eggleton@linux.intel.com>
>> > wrote:>
>> > On Mon, 31 Oct 2016 09:37:07 Khem Raj wrote:
>> >>> On Oct 31, 2016, at 7:37 AM, Vuille, Martin (Martin) <vmartin@avaya.com>
>> >>> wrote:
>> >>>
>> >>> We are looking at upgrading from Yocto 1.8 to 2.2.
>> >>>
>> >>> Yocto 2.2 has a minimum kernel requirement of 3.2.0.
>> >>>
>> >>> This isn’t an issue for our target (ARMv5, Linux 4.4) but may be
>> >>> an issue for our automated build machines (x86, Linux 2.6.32—CentOS 6.)
>> >>>
>> >>> However, there is a note that says
>> >>> “For x86 and x86_64, you can reset OLDEST_KERNEL
>> >>> <http://www.yoctoproject.org/docs/2.2/mega-manual/mega-manual.html#var-O
>> >>> L
>> >>> DEST_KERNEL> to anything down to 2.6.32 if desired.”
>> >>>
>> >>> Is it possible to configure things such that we can keep supporting the
>> >>> old kernel for the SDK while we support a more up-to-date kernel for the
>> >>> target?
>> >>
>> >> I think that should be the default. We do not set it for x86/nativesdk
>> >> case. File a ticket if thats not the case.
>> >
>> > SDK_OLDEST_KERNEL is the variable that's supposed to be controlling this,
>> > but I noticed a couple of weeks ago that we aren't feeding
>> > SDK_OLDEST_KERNEL into glibc for nativesdk, so we should fix that - I've
>> > filed a bug [1] and will sort that out. I think we should probably set
>> > the SDK_OLDEST_KERNEL default for x86 to 2.6.32 at the same time - I
>> > assume there are no objections?
>>
>> Yes, its for nativesdk/glibc, I think for target x86 we should keep 3.2
>
> Right, I'm not proposing changing the target value.
>
> It turns out setting SDK_OLDEST_KERNEL in an arch-specific manner is a little
> awkward since there aren't overrides that can be used for the SDK value, but
> we can do it from conf/machine-sdk/*.conf though.
>

yes understood, we do have aarch64 as another option for nativesdk but
practically
not there yet I guess.

> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre