[meta-fsl-ppc][PATCH 1/2] machines: Dont lock linux-libc-headers-nativesdk preferred provider

[meta-fsl-ppc][PATCH 1/2] machines: Dont lock linux-libc-headers-nativesdk preferred provider

[Khem Raj]

linux-libc-headers-nativesdk is for native bits in an SDK
its not required to be locked in machine conf files since
nothing depends on machine per se here. If its a mattetr of
policy then this should be added to distro conf which
in this layer is fsl.conf

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 conf/machine/e500mc.inc    |    1 -
 conf/machine/e500v2.inc    |    1 -
 conf/machine/e5500-64b.inc |    1 -
 conf/machine/e5500.inc     |    1 -
 4 files changed, 4 deletions(-)

diff --git a/conf/machine/e500mc.inc b/conf/machine/e500mc.inc
index bfac9e6..479c513 100644
--- a/conf/machine/e500mc.inc
+++ b/conf/machine/e500mc.inc
@@ -8,7 +8,6 @@ MACHINE_FEATURES_RRECOMMENDS = ""
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.6"
 PREFERRED_PROVIDER_linux-libc-headers ?= "linux-qoriq-sdk-headers"
-PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?= "linux-qoriq-sdk-headers-nativesdk"
 
 KERNEL_IMAGETYPE ?= "uImage"
 # disable the images below for now
diff --git a/conf/machine/e500v2.inc b/conf/machine/e500v2.inc
index cf8f36c..6e2eb49 100644
--- a/conf/machine/e500v2.inc
+++ b/conf/machine/e500v2.inc
@@ -8,7 +8,6 @@ MACHINE_EXTRA_RRECOMMENDS = ""
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.6"
 PREFERRED_PROVIDER_linux-libc-headers ?= "linux-qoriq-sdk-headers"
-PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?= "linux-qoriq-sdk-headers-nativesdk"
 
 KERNEL_IMAGETYPE ?= "uImage"
 # disable the images below for now
diff --git a/conf/machine/e5500-64b.inc b/conf/machine/e5500-64b.inc
index 80dee5c..1e5d92b 100644
--- a/conf/machine/e5500-64b.inc
+++ b/conf/machine/e5500-64b.inc
@@ -9,7 +9,6 @@ MACHINE_FEATURES_RRECOMMENDS = ""
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.6"
 PREFERRED_PROVIDER_linux-libc-headers ?= "linux-qoriq-sdk-headers"
-PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?= "linux-qoriq-sdk-headers-nativesdk"
 
 KERNEL_IMAGETYPE ?= "uImage"
 # disable the images below for now
diff --git a/conf/machine/e5500.inc b/conf/machine/e5500.inc
index 965618e..f34c2c0 100644
--- a/conf/machine/e5500.inc
+++ b/conf/machine/e5500.inc
@@ -8,7 +8,6 @@ MACHINE_FEATURES_RRECOMMENDS = ""
 PREFERRED_PROVIDER_virtual/kernel ?= "linux-qoriq-sdk"
 PREFERRED_VERSION_virtual/kernel ?= "3.0.6"
 PREFERRED_PROVIDER_linux-libc-headers ?= "linux-qoriq-sdk-headers"
-PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?= "linux-qoriq-sdk-headers-nativesdk"
 
 KERNEL_IMAGETYPE ?= "uImage"
 # disable the images below for now
-- 
1.7.9.5

[meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[Khem Raj]

If not set by user then let distro policy be to use
linux-qoriq-sdk-headers-nativesdk for linux-libc-headers-nativesdk

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 conf/distro/fsl.conf |    1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/distro/fsl.conf b/conf/distro/fsl.conf
index 6d4dc34..8bfb272 100644
--- a/conf/distro/fsl.conf
+++ b/conf/distro/fsl.conf
@@ -83,6 +83,7 @@ IMAGE_CLASSES = "image_types_uboot"
 
 PREFERRED_VERSION_u-boot-mkimage-native_powerpc = "2011.06"
 PREFERRED_PROVIDER_virtual/libx11 = "libx11"
+PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?= "linux-qoriq-sdk-headers-nativesdk"
 
 SYSVINIT_ENABLED_GETTYS = ""
 USE_VT = ""
-- 
1.7.9.5

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[David Nyström]

So that about a disto refusing this and possibly other BSP layers ?
Should the disto.conf  select of nativesdk be made machine specific on all machines in meta-fsl-ppc ? And one added target after a meta-fsl-ppc rebase would break stuff, I guess.


Br
David

Sent from Android


-----Original Message-----
From: Khem Raj [raj.khem@gmail.com]
Received: Friday, 06 Jul 2012, 6:52
To: yocto@yoctoproject.org [yocto@yoctoproject.org]
Subject: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let        linux-qoriq-sdk-headers-nativesdk provide       linux-libc-headers-nativesdk



If not set by user then let distro policy be to use
linux-qoriq-sdk-headers-nativesdk for linux-libc-headers-nativesdk

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 conf/distro/fsl.conf |    1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/distro/fsl.conf b/conf/distro/fsl.conf
index 6d4dc34..8bfb272 100644
--- a/conf/distro/fsl.conf
+++ b/conf/distro/fsl.conf
@@ -83,6 +83,7 @@ IMAGE_CLASSES = "image_types_uboot"

 PREFERRED_VERSION_u-boot-mkimage-native_powerpc = "2011.06"
 PREFERRED_PROVIDER_virtual/libx11 = "libx11"
+PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?= "linux-qoriq-sdk-headers-nativesdk"

 SYSVINIT_ENABLED_GETTYS = ""
 USE_VT = ""
--
1.7.9.5

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[David Nyström]

typo refusing = reusing.


-----Original Message-----
From: David Nyström [David.Nystrom@enea.com]
Received: Friday, 06 Jul 2012, 12:49
To: yocto@yoctoproject.org [yocto@yoctoproject.org]; raj.khem@gmail.com [raj.khem@gmail.com]
Subject: Re: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf:        Let     linux-qoriq-sdk-headers-nativesdk       provide linux-libc-headers-nativesdk



So that about a disto refusing this and possibly other BSP layers ?
Should the disto.conf  select of nativesdk be made machine specific on all machines in meta-fsl-ppc ? And one added target after a meta-fsl-ppc rebase would break stuff, I guess.


Br
David

Sent from Android


-----Original Message-----
From: Khem Raj [raj.khem@gmail.com]
Received: Friday, 06 Jul 2012, 6:52
To: yocto@yoctoproject.org [yocto@yoctoproject.org]
Subject: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let        linux-qoriq-sdk-headers-nativesdk provide       linux-libc-headers-nativesdk



If not set by user then let distro policy be to use
linux-qoriq-sdk-headers-nativesdk for linux-libc-headers-nativesdk

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 conf/distro/fsl.conf |    1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/distro/fsl.conf b/conf/distro/fsl.conf
index 6d4dc34..8bfb272 100644
--- a/conf/distro/fsl.conf
+++ b/conf/distro/fsl.conf
@@ -83,6 +83,7 @@ IMAGE_CLASSES = "image_types_uboot"

 PREFERRED_VERSION_u-boot-mkimage-native_powerpc = "2011.06"
 PREFERRED_PROVIDER_virtual/libx11 = "libx11"
+PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?= "linux-qoriq-sdk-headers-nativesdk"

 SYSVINIT_ENABLED_GETTYS = ""
 USE_VT = ""
--
1.7.9.5

_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[McClintock Matthew-B29882]

On Fri, Jul 6, 2012 at 5:49 AM, David Nyström <David.Nystrom@enea.com> wrote:
> So that about a disto refusing this and possibly other BSP layers ?
> Should the disto.conf  select of nativesdk be made machine specific on all machines in meta-fsl-ppc ? And one added target after a meta-fsl-ppc rebase would break stuff, I guess.

I don't quite follow... you are suggesting we have

PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?=
"linux-qoriq-sdk-headers-nativesdk"

in the machine.conf files instead?

-M

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[David Nyström]

Yes this was my suggestion, since you might not want to change the nativesdk kernel headers for all machines in all BSP layers, if the distro is using multiple BSP layers, which it probably should be able to do.
Setting this  with machine overrides in distro.conf  is possible but quite  messy IMHO.
Furthermore , the nativesdk is set by ?= in machine.conf, any distro.conf  wanting to alter this to a global setting can easily override with  =


Sent from Android


-----Original Message-----
From: McClintock Matthew-B29882 [B29882@freescale.com]
Received: Friday, 06 Jul 2012, 17:48
To: David Nyström [David.Nystrom@enea.com]
CC: yocto@yoctoproject.org [yocto@yoctoproject.org]; raj.khem@gmail.com [raj.khem@gmail.com]
Subject: Re: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk



On Fri, Jul 6, 2012 at 5:49 AM, David Nyström <David.Nystrom@enea.com> wrote:
> So that about a disto refusing this and possibly other BSP layers ?
> Should the disto.conf  select of nativesdk be made machine specific on all machines in meta-fsl-ppc ? And one added target after a meta-fsl-ppc rebase would break stuff, I guess.

I don't quite follow... you are suggesting we have

PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?=
"linux-qoriq-sdk-headers-nativesdk"

in the machine.conf files instead?

-M

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[McClintock Matthew-B29882]

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


On Jul 6, 2012 5:35 PM, "David Nyström" <David.Nystrom@enea.com<mailto:David.Nystrom@enea.com>> wrote:
>
> Yes this was my suggestion, since you might not want to change the nativesdk kernel headers for all machines in all BSP layers, if the distro is using multiple BSP layers, which it probably should be able to do.
> Setting this  with machine overrides in distro.conf  is possible but quite  messy IMHO.
> Furthermore , the nativesdk is set by ?= in machine.conf, any distro.conf  wanting to alter this to a global setting can easily override with  =

I actually agree and was hoping to move everything possible out of distro.conf files. And make it easy as possible for folks to use meta-fsl-ppc in their own distro.

-M

>
>
> Sent from Android
>
>
> -----Original Message-----
> From: McClintock Matthew-B29882 [B29882@freescale.com<mailto:B29882@freescale.com>]
> Received: Friday, 06 Jul 2012, 17:48
> To: David Nyström [David.Nystrom@enea.com<mailto:David.Nystrom@enea.com>]
> CC: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> [yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>]; raj.khem@gmail.com<mailto:raj.khem@gmail.com> [raj.khem@gmail.com<mailto:raj.khem@gmail.com>]
> Subject: Re: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk
>
>
>
> On Fri, Jul 6, 2012 at 5:49 AM, David Nyström <David.Nystrom@enea.com<mailto:David.Nystrom@enea.com>> wrote:
> > So that about a disto refusing this and possibly other BSP layers ?
> > Should the disto.conf  select of nativesdk be made machine specific on all machines in meta-fsl-ppc ? And one added target after a meta-fsl-ppc rebase would break stuff, I guess.
>
> I don't quite follow... you are suggesting we have
>
> PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?=
> "linux-qoriq-sdk-headers-nativesdk"
>
> in the machine.conf files instead?
>
> -M
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto

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

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[David Nyström]

On 07/07/2012 12:39 AM, McClintock Matthew-B29882 wrote:
> On Jul 6, 2012 5:35 PM, "David Nyström" <David.Nystrom@enea.com<mailto:David.Nystrom@enea.com>> wrote:
>> Yes this was my suggestion, since you might not want to change the nativesdk kernel headers for all machines in all BSP layers, if the distro is using multiple BSP layers, which it probably should be able to do.
>> Setting this  with machine overrides in distro.conf  is possible but quite  messy IMHO.
>> Furthermore , the nativesdk is set by ?= in machine.conf, any distro.conf  wanting to alter this to a global setting can easily override with  =
> I actually agree and was hoping to move everything possible out of distro.conf files. And make it easy as possible for folks to use meta-fsl-ppc in their own distro.
>
> -M


Hi, it looks like this was merged to the denzil branch, and 
PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to 
distro.conf.
Any reason for this ?

>
>>
>> Sent from Android
>>
>>
>> -----Original Message-----
>> From: McClintock Matthew-B29882 [B29882@freescale.com<mailto:B29882@freescale.com>]
>> Received: Friday, 06 Jul 2012, 17:48
>> To: David Nyström [David.Nystrom@enea.com<mailto:David.Nystrom@enea.com>]
>> CC: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org> [yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>]; raj.khem@gmail.com<mailto:raj.khem@gmail.com> [raj.khem@gmail.com<mailto:raj.khem@gmail.com>]
>> Subject: Re: [yocto] [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk
>>
>>
>>
>> On Fri, Jul 6, 2012 at 5:49 AM, David Nyström <David.Nystrom@enea.com<mailto:David.Nystrom@enea.com>> wrote:
>>> So that about a disto refusing this and possibly other BSP layers ?
>>> Should the disto.conf  select of nativesdk be made machine specific on all machines in meta-fsl-ppc ? And one added target after a meta-fsl-ppc rebase would break stuff, I guess.
>> I don't quite follow... you are suggesting we have
>>
>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk ?=
>> "linux-qoriq-sdk-headers-nativesdk"
>>
>> in the machine.conf files instead?
>>
>> -M
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
>> https://lists.yoctoproject.org/listinfo/yocto

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[Khem Raj]

On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nystrom@enea.com> wrote:
>
> Hi, it looks like this was merged to the denzil branch, and
> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
> distro.conf.
> Any reason for this ?

why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
dont expect it to have something special for SDK hosts which are
usually x86 ? afterall these are for
the SDK host and not for target. Moreover it means that this BSP will
not play in the multi BSP environment something you never want.

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[McClintock Matthew-B29882]

On Tue, Aug 14, 2012 at 2:26 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nystrom@enea.com> wrote:
>>
>> Hi, it looks like this was merged to the denzil branch, and
>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
>> distro.conf.
>> Any reason for this ?
>
> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
> dont expect it to have something special for SDK hosts which are
> usually x86 ? afterall these are for
> the SDK host and not for target. Moreover it means that this BSP will
> not play in the multi BSP environment something you never want.

But, I think we might need them for this warning specifically:

NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for lib32-linux-libc-headers
(lib32-linux-libc-headers, lib32-linux-libc-headers-yocto,
lib32-linux-qoriq-sdk-headers)
NOTE: consider defining a PREFERRED_PROVIDER entry to match
lib32-linux-libc-headers
NOTE: multiple providers are available for runtime
lib32-linux-libc-headers-dev (lib32-linux-libc-headers,
lib32-linux-libc-headers-yocto, lib32-linux-qoriq-sdk-headers)
NOTE: consider defining a PREFERRED_PROVIDER entry to match
lib32-linux-libc-headers-dev

?

-M

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[Khem Raj]

On Thu, Aug 16, 2012 at 12:37 PM, McClintock Matthew-B29882
<B29882@freescale.com> wrote:
> On Tue, Aug 14, 2012 at 2:26 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nystrom@enea.com> wrote:
>>>
>>> Hi, it looks like this was merged to the denzil branch, and
>>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
>>> distro.conf.
>>> Any reason for this ?
>>
>> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
>> dont expect it to have something special for SDK hosts which are
>> usually x86 ? afterall these are for
>> the SDK host and not for target. Moreover it means that this BSP will
>> not play in the multi BSP environment something you never want.
>
> But, I think we might need them for this warning specifically:
>
> NOTE: Resolving any missing task queue dependencies
> NOTE: multiple providers are available for lib32-linux-libc-headers
> (lib32-linux-libc-headers, lib32-linux-libc-headers-yocto,
> lib32-linux-qoriq-sdk-headers)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match
> lib32-linux-libc-headers
> NOTE: multiple providers are available for runtime
> lib32-linux-libc-headers-dev (lib32-linux-libc-headers,
> lib32-linux-libc-headers-yocto, lib32-linux-qoriq-sdk-headers)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match
> lib32-linux-libc-headers-dev
>

This is a bug in OE-Core, it should have added appropriate defines for
multilib case as well in
tcmode-default.inc and default-providers.inc

> ?
>
> -M

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[McClintock Matthew-B29882]

On Fri, Aug 17, 2012 at 12:12 AM, Khem Raj <raj.khem@gmail.com> wrote:
> On Thu, Aug 16, 2012 at 12:37 PM, McClintock Matthew-B29882
> <B29882@freescale.com> wrote:
>> On Tue, Aug 14, 2012 at 2:26 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nystrom@enea.com> wrote:
>>>>
>>>> Hi, it looks like this was merged to the denzil branch, and
>>>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
>>>> distro.conf.
>>>> Any reason for this ?
>>>
>>> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
>>> dont expect it to have something special for SDK hosts which are
>>> usually x86 ? afterall these are for
>>> the SDK host and not for target. Moreover it means that this BSP will
>>> not play in the multi BSP environment something you never want.
>>
>> But, I think we might need them for this warning specifically:
>>
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: multiple providers are available for lib32-linux-libc-headers
>> (lib32-linux-libc-headers, lib32-linux-libc-headers-yocto,
>> lib32-linux-qoriq-sdk-headers)
>> NOTE: consider defining a PREFERRED_PROVIDER entry to match
>> lib32-linux-libc-headers
>> NOTE: multiple providers are available for runtime
>> lib32-linux-libc-headers-dev (lib32-linux-libc-headers,
>> lib32-linux-libc-headers-yocto, lib32-linux-qoriq-sdk-headers)
>> NOTE: consider defining a PREFERRED_PROVIDER entry to match
>> lib32-linux-libc-headers-dev
>>
>
> This is a bug in OE-Core, it should have added appropriate defines for
> multilib case as well in
> tcmode-default.inc and default-providers.inc

And there appears to be a fix for it already:

http://patches.openembedded.org/patch/34723/

-M

>
>> ?
>>
>> -M
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[David Nyström]

On 08/14/2012 09:26 PM, Khem Raj wrote:
> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nystrom@enea.com> wrote:
>> Hi, it looks like this was merged to the denzil branch, and
>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
>> distro.conf.
>> Any reason for this ?
> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
> dont expect it to have something special for SDK hosts which are
> usually x86 ? afterall these are for
> the SDK host and not for target. Moreover it means that this BSP will
> not play in the multi BSP environment something you never want.

My main concern is that meta-toolchain uses linux-libc-headers-nativesdk 
for the meta-toolchain
tarball build, i.e. the meta-toolchain API may differ from the on-target 
API in regards to kernel-headers, no ?

This might very well be true if kernel version of 
linux-libc-headers-nativesdk != linux-libc-headers

Br,
David

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[Khem Raj]

On Mon, Aug 20, 2012 at 12:23 AM, David Nyström <david.nystrom@enea.com> wrote:
> On 08/14/2012 09:26 PM, Khem Raj wrote:
>>
>> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nystrom@enea.com>
>> wrote:
>>>
>>> Hi, it looks like this was merged to the denzil branch, and
>>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
>>> distro.conf.
>>> Any reason for this ?
>>
>> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
>> dont expect it to have something special for SDK hosts which are
>> usually x86 ? afterall these are for
>> the SDK host and not for target. Moreover it means that this BSP will
>> not play in the multi BSP environment something you never want.
>
>
> My main concern is that meta-toolchain uses linux-libc-headers-nativesdk for
> the meta-toolchain
> tarball build, i.e. the meta-toolchain API may differ from the on-target API
> in regards to kernel-headers, no ?
>
> This might very well be true if kernel version of
> linux-libc-headers-nativesdk != linux-libc-headers

whats the point of keeping header versions same across two entirely
different systems.
can you point to some instances where this API difference if any is in
conflict ?

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[McClintock Matthew-B29882]

On Mon, Aug 20, 2012 at 11:45 AM, Khem Raj <raj.khem@gmail.com> wrote:
> On Mon, Aug 20, 2012 at 12:23 AM, David Nyström <david.nystrom@enea.com> wrote:
>> On 08/14/2012 09:26 PM, Khem Raj wrote:
>>>
>>> On Tue, Aug 14, 2012 at 12:49 AM, David Nyström <david.nystrom@enea.com>
>>> wrote:
>>>>
>>>> Hi, it looks like this was merged to the denzil branch, and
>>>> PREFERRED_PROVIDER_linux-libc-headers-nativesdk was moved back to
>>>> distro.conf.
>>>> Any reason for this ?
>>>
>>> why do you want nativesdk headers to come from BSP its a fsl-ppc bsp I
>>> dont expect it to have something special for SDK hosts which are
>>> usually x86 ? afterall these are for
>>> the SDK host and not for target. Moreover it means that this BSP will
>>> not play in the multi BSP environment something you never want.
>>
>>
>> My main concern is that meta-toolchain uses linux-libc-headers-nativesdk for
>> the meta-toolchain
>> tarball build, i.e. the meta-toolchain API may differ from the on-target API
>> in regards to kernel-headers, no ?
>>
>> This might very well be true if kernel version of
>> linux-libc-headers-nativesdk != linux-libc-headers
>
> whats the point of keeping header versions same across two entirely
> different systems.
> can you point to some instances where this API difference if any is in
> conflict ?

I just checked and we do have a few obscure bits in our kernel tree's
header files. Nothing that 99.9% would use but it seems reasonable to
include these...

-M

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[Khem Raj]

> I just checked and we do have a few obscure bits in our kernel tree's
> header files. Nothing that 99.9% would use but it seems reasonable to
> include these...

Do you want applications for sdk host to be built using these obscure bits ?
if yes I would like to know why?

since then you are creating a scenariou where nativesdk is dependent on target
kernel and we need to fix it so that nativesdk can be common again.

if patches you are carrying are good for nativesdk headers can they be made
available for other kernels like linux-yocto e.g. ?

right now if we do this we are pretty much saying fsl machine layer can really
not mix with other BSPs. Many people use yocto commonly on more than one kind
of CPU and this does not scale.

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[McClintock Matthew-B29882]

On Mon, Aug 20, 2012 at 2:27 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> I just checked and we do have a few obscure bits in our kernel tree's
>> header files. Nothing that 99.9% would use but it seems reasonable to
>> include these...
>
> Do you want applications for sdk host to be built using these obscure bits ?
> if yes I would like to know why?
>
> since then you are creating a scenariou where nativesdk is dependent on target
> kernel and we need to fix it so that nativesdk can be common again.
>
> if patches you are carrying are good for nativesdk headers can they be made
> available for other kernels like linux-yocto e.g. ?
>
> right now if we do this we are pretty much saying fsl machine layer can really
> not mix with other BSPs. Many people use yocto commonly on more than one kind
> of CPU and this does not scale.

Hmm I think I was just confused. We don't need any modifications for
the headers for nativesdk foo (that is the x86 tools in
meta-toolchain).

So, I think everything is OK as is.. if you look at meta-toolchain you
will see it includes our kernel's headers for cross compiling.

-M

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[McClintock Matthew-B29882]

Adding David back...

-M

On Mon, Aug 20, 2012 at 2:42 PM, Matthew McClintock <msm@freescale.com> wrote:
> On Mon, Aug 20, 2012 at 2:27 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>> I just checked and we do have a few obscure bits in our kernel tree's
>>> header files. Nothing that 99.9% would use but it seems reasonable to
>>> include these...
>>
>> Do you want applications for sdk host to be built using these obscure bits ?
>> if yes I would like to know why?
>>
>> since then you are creating a scenariou where nativesdk is dependent on target
>> kernel and we need to fix it so that nativesdk can be common again.
>>
>> if patches you are carrying are good for nativesdk headers can they be made
>> available for other kernels like linux-yocto e.g. ?
>>
>> right now if we do this we are pretty much saying fsl machine layer can really
>> not mix with other BSPs. Many people use yocto commonly on more than one kind
>> of CPU and this does not scale.
>
> Hmm I think I was just confused. We don't need any modifications for
> the headers for nativesdk foo (that is the x86 tools in
> meta-toolchain).
>
> So, I think everything is OK as is.. if you look at meta-toolchain you
> will see it includes our kernel's headers for cross compiling.
>
> -M

Re: [meta-fsl-ppc][PATCH 2/2] fsl.conf: Let linux-qoriq-sdk-headers-nativesdk provide linux-libc-headers-nativesdk

[David Nyström]

On 08/20/2012 09:50 PM, McClintock Matthew-B29882 wrote:
> Adding David back...
>
> -M
>
> On Mon, Aug 20, 2012 at 2:42 PM, Matthew McClintock <msm@freescale.com> wrote:
>> On Mon, Aug 20, 2012 at 2:27 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>>> I just checked and we do have a few obscure bits in our kernel tree's
>>>> header files. Nothing that 99.9% would use but it seems reasonable to
>>>> include these...
>>> Do you want applications for sdk host to be built using these obscure bits ?
>>> if yes I would like to know why?
>>>
>>> since then you are creating a scenariou where nativesdk is dependent on target
>>> kernel and we need to fix it so that nativesdk can be common again.
>>>
>>> if patches you are carrying are good for nativesdk headers can they be made
>>> available for other kernels like linux-yocto e.g. ?
>>>
>>> right now if we do this we are pretty much saying fsl machine layer can really
>>> not mix with other BSPs. Many people use yocto commonly on more than one kind
>>> of CPU and this does not scale.
>> Hmm I think I was just confused. We don't need any modifications for
>> the headers for nativesdk foo (that is the x86 tools in
>> meta-toolchain).
>>
>> So, I think everything is OK as is.. if you look at meta-toolchain you
>> will see it includes our kernel's headers for cross compiling.
>>
>> -M

Oh, sorry for the misunderstanding

I was under the impression that linux-libc-headers-nativesdk was 
installed under
/opt/poky/1.2/sysroots/<target-sysroot>/..., which it obviously is not.

Br,
David