[yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

[Bodke, Kishore K]

Hello All,

I am trying to build linux-yocto with rt kernel for sugarbay bsp and it fails 
for the grub recipe.

Attached is the build log.

kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$ bitbake -e | 
egrep "^WARN_QA="
WARN_QA="dev-so rpaths debug-deps dev-deps debug-files arch la2 pkgconfig 
desktop la ldflags perms useless-rpaths"
kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$ bitbake -e | 
egrep "^ERROR_QA="
kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$

Please let me know what could be the issue.

Thanks
Kishore.


buld.log
Description: buld.log
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

[Bodke, Kishore K]

When I do bitbake freetype followed by bitbake grub , the grub build 
successfully.

Attached is the freetype.log and grub.log.

It fails if I first build the bitbake grub.  

Thanks
Kishore.

-Original Message-
From: Hart, Darren 
Sent: Tuesday, August 30, 2011 7:52 PM
To: Richard Purdie
Cc: Bodke, Kishore K; yocto@yoctoproject.org
Subject: Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

On 08/30/2011 05:11 PM, Richard Purdie wrote:
> On Tue, 2011-08-30 at 16:59 -0700, Bodke, Kishore K wrote:
>> Hello All,
>>
>>  
>>
>> I am trying to build linux-yocto with rt kernel for sugarbay bsp and
>> it fails for the grub recipe.
>>
>>  
>>
>> Attached is the build log.  
>>
>>  
>>
>> kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
>> bitbake -e | egrep "^WARN_QA="
>>
>> WARN_QA="dev-so rpaths debug-deps dev-deps debug-files arch la2
>> pkgconfig desktop la ldflags perms useless-rpaths"
>>
>> kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
>> bitbake -e | egrep "^ERROR_QA="
>>
>> kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
>>
>>  
>>
>> Please let me know what could be the issue.
> 
> Could you include the config.log file mentioned in the error report
> please?
> 
> This should be somewhere like
> usr/local/src/crf/test/buildsugarbayrt/tmp/work/x86_64-poky-linux/grub-1.98-r1/*/config.log
> 

I replied with this and a comparison file, but it was rejected due to
being over 200k :(.

Short of it is that Kishore's config.log shows it picking up the
freetype libs from his host system. The patch I proposed adds a DEPENDS
to grub on freetype.

> Cheers,
> 
> Richard
> 
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


freetype.log
Description: freetype.log


grub.log
Description: grub.log
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

[Bodke, Kishore K]

No. 
First I tried without applying the patch by building freetype and then grub as 
per your suggestion in the thread.  
It built.

I will try a fresh build by applying the patch and let you know.

Thanks
Kishore.

-Original Message-
From: Hart, Darren 
Sent: Wednesday, August 31, 2011 10:00 AM
To: Bodke, Kishore K
Cc: Richard Purdie; yocto@yoctoproject.org
Subject: Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe

On 08/31/2011 09:51 AM, Bodke, Kishore K wrote:
> When I do bitbake freetype followed by bitbake grub , the grub build 
> successfully.
> 
> Attached is the freetype.log and grub.log.
> 
> It fails if I first build the bitbake grub.  


Did you apply the patch I provided?

--
Darren


> 
> Thanks
> Kishore.
> 
> -Original Message-
> From: Hart, Darren 
> Sent: Tuesday, August 30, 2011 7:52 PM
> To: Richard Purdie
> Cc: Bodke, Kishore K; yocto@yoctoproject.org
> Subject: Re: [yocto] linux-yocto-rt build fail for sugarbay bsp on grub recipe
> 
> On 08/30/2011 05:11 PM, Richard Purdie wrote:
>> On Tue, 2011-08-30 at 16:59 -0700, Bodke, Kishore K wrote:
>>> Hello All,
>>>
>>>  
>>>
>>> I am trying to build linux-yocto with rt kernel for sugarbay bsp and
>>> it fails for the grub recipe.
>>>
>>>  
>>>
>>> Attached is the build log.  
>>>
>>>  
>>>
>>> kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
>>> bitbake -e | egrep "^WARN_QA="
>>>
>>> WARN_QA="dev-so rpaths debug-deps dev-deps debug-files arch la2
>>> pkgconfig desktop la ldflags perms useless-rpaths"
>>>
>>> kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
>>> bitbake -e | egrep "^ERROR_QA="
>>>
>>> kishore@kishore-desktop:/usr/local/src/crf/test/buildsugarbayrt$
>>>
>>>  
>>>
>>> Please let me know what could be the issue.
>>
>> Could you include the config.log file mentioned in the error report
>> please?
>>
>> This should be somewhere like
>> usr/local/src/crf/test/buildsugarbayrt/tmp/work/x86_64-poky-linux/grub-1.98-r1/*/config.log
>>
> 
> I replied with this and a comparison file, but it was rejected due to
> being over 200k :(.
> 
> Short of it is that Kishore's config.log shows it picking up the
> freetype libs from his host system. The patch I proposed adds a DEPENDS
> to grub on freetype.
> 
>> Cheers,
>>
>> Richard
>>
>>
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> 


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] RT kernel with core-image-sato build failed for sugarbay

[Bodke, Kishore K]

Hi,

I am trying to build core-image-sato with rt kernel for sugarbay and it fails 
for the do_rootfs .

Attached is the build log.

Could you please let me know what went wrong?

Thanks
Kishore.


error.log
Description: error.log
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RT kernel with core-image-sato build failed for sugarbay

[Bodke, Kishore K]

Clean build with the below TOM's two commit IDs worked for me, if I do not add 
IMAGE_INSTALL += "rttests" for sugarbay.

It failed if I add the IMAGE_INSTALL += "rttests"

Thanks
Kishore.
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com] 
Sent: Thursday, September 01, 2011 1:57 PM
To: Zanussi, Tom
Cc: Bodke, Kishore K; yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul
Subject: Re: RT kernel with core-image-sato build failed for sugarbay



On 08/31/2011 09:19 PM, Tom Zanussi wrote:
> 
> On Wed, 2011-08-31 at 16:49 -0700, Bodke, Kishore K wrote:
>> Hi,
>>
>>  
>>
>> I am trying to build core-image-sato with rt kernel for sugarbay and
>> it fails for the do_rootfs .
>>
> 
> FWIW, I was able to build and boot core-image-sato with the rt kernel:
> 
> Linux sugarbay 3.0.3-rt8-yocto-preempt-rt+ #1 SMP PREEMPT RT Wed Aug 31
> 21:33:27 CDT 2011 x86_64 GNU/Linux
> 
> using the following commits:
> 
> poky/master 705ec50edda7f7fb8c132238fe3f1477384a470e
> meta/intel 902d2f3c919cd1d870dc8d35a7521cbba42e53ea
> 
> Actually, meta/intel was that commit with Darren's grub patch on top
> (meta-intel/dvhart/grub-freetype).
> 

Kishore, would you try with a clean build and see if this works for you?

I'm going to try and build first without -rt and then with rt and see if
I can reproduce the issue.

Thanks,

Darren

> Tom
> 
>>  
>>
>> Attached is the build log.
>>
>>  
>>
>> Could you please let me know what went wrong?
>>
>>  
>>
>> Thanks
>>
>> Kishore.
>>
>>
> 
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RT kernel with core-image-sato build failed for sugarbay

[Bodke, Kishore K]

Yeah, it is the same do_rootfs failure I get for both the builds.
Thanks
Kishore.

-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com] 
Sent: Thursday, September 01, 2011 2:08 PM
To: Bodke, Kishore K
Cc: Zanussi, Tom; yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul
Subject: Re: RT kernel with core-image-sato build failed for sugarbay

On 09/01/2011 02:01 PM, Bodke, Kishore K wrote:
> Clean build with the below TOM's two commit IDs worked for me, if I
> do not add IMAGE_INSTALL += "rttests" for sugarbay.
> 
> It failed if I add the IMAGE_INSTALL += "rttests"

Do you get the same error? If so, it's starting to sound like the second
build is what fails since neither of your failure scenarios include
a change that's related to the failure. Perhaps an issue with sstate...

--
Darren

> 
> Thanks Kishore. -Original Message- From: Darren Hart
> [mailto:dvh...@linux.intel.com] Sent: Thursday, September 01, 2011
> 1:57 PM To: Zanussi, Tom Cc: Bodke, Kishore K;
> yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul Subject: Re: RT
> kernel with core-image-sato build failed for sugarbay
> 
> 
> 
> On 08/31/2011 09:19 PM, Tom Zanussi wrote:
>> 
>> On Wed, 2011-08-31 at 16:49 -0700, Bodke, Kishore K wrote:
>>> Hi,
>>> 
>>> 
>>> 
>>> I am trying to build core-image-sato with rt kernel for sugarbay
>>> and it fails for the do_rootfs .
>>> 
>> 
>> FWIW, I was able to build and boot core-image-sato with the rt
>> kernel:
>> 
>> Linux sugarbay 3.0.3-rt8-yocto-preempt-rt+ #1 SMP PREEMPT RT Wed
>> Aug 31 21:33:27 CDT 2011 x86_64 GNU/Linux
>> 
>> using the following commits:
>> 
>> poky/master 705ec50edda7f7fb8c132238fe3f1477384a470e meta/intel
>> 902d2f3c919cd1d870dc8d35a7521cbba42e53ea
>> 
>> Actually, meta/intel was that commit with Darren's grub patch on
>> top (meta-intel/dvhart/grub-freetype).
>> 
> 
> Kishore, would you try with a clean build and see if this works for
> you?
> 
> I'm going to try and build first without -rt and then with rt and see
> if I can reproduce the issue.
> 
> Thanks,
> 
> Darren
> 
>> Tom
>> 
>>> 
>>> 
>>> Attached is the build log.
>>> 
>>> 
>>> 
>>> Could you please let me know what went wrong?
>>> 
>>> 
>>> 
>>> Thanks
>>> 
>>> Kishore.
>>> 
>>> 
>> 
>> 
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RT kernel with core-image-sato build failed for sugarbay

[Bodke, Kishore K]

For the build I removed the rttests in the IMAGE_INSTALL , so it is not showing 
up here.

bitbake -e core-image-sato | egrep "IMAGE_INSTALL=" 
  
# MULTILIB_IMAGE_INSTALL= 
# IMAGE_INSTALL=${POKY_BASE_INSTALL}
IMAGE_INSTALL="task-core-boot task-base-extended"

I will rebuild with rttests and send the output.

Thanks
Kishore.

-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com] 
Sent: Thursday, September 01, 2011 2:52 PM
To: Bodke, Kishore K
Cc: Zanussi, Tom; yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul
Subject: Re: RT kernel with core-image-sato build failed for sugarbay

Can you report the output of:

$ bitbake -e core-image-sato | egrep "^IMAGE_INSTALL="

Thanks,

Darren

On 09/01/2011 02:14 PM, Bodke, Kishore K wrote:
> Yeah, it is the same do_rootfs failure I get for both the builds.
> Thanks
> Kishore.
> 
> -Original Message-
> From: Darren Hart [mailto:dvh...@linux.intel.com] 
> Sent: Thursday, September 01, 2011 2:08 PM
> To: Bodke, Kishore K
> Cc: Zanussi, Tom; yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul
> Subject: Re: RT kernel with core-image-sato build failed for sugarbay
> 
> On 09/01/2011 02:01 PM, Bodke, Kishore K wrote:
>> Clean build with the below TOM's two commit IDs worked for me, if I
>> do not add IMAGE_INSTALL += "rttests" for sugarbay.
>>
>> It failed if I add the IMAGE_INSTALL += "rttests"
> 
> Do you get the same error? If so, it's starting to sound like the second
> build is what fails since neither of your failure scenarios include
> a change that's related to the failure. Perhaps an issue with sstate...
> 
> --
> Darren
> 
>>
>> Thanks Kishore. -----Original Message- From: Darren Hart
>> [mailto:dvh...@linux.intel.com] Sent: Thursday, September 01, 2011
>> 1:57 PM To: Zanussi, Tom Cc: Bodke, Kishore K;
>> yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul Subject: Re: RT
>> kernel with core-image-sato build failed for sugarbay
>>
>>
>>
>> On 08/31/2011 09:19 PM, Tom Zanussi wrote:
>>>
>>> On Wed, 2011-08-31 at 16:49 -0700, Bodke, Kishore K wrote:
>>>> Hi,
>>>>
>>>>
>>>>
>>>> I am trying to build core-image-sato with rt kernel for sugarbay
>>>> and it fails for the do_rootfs .
>>>>
>>>
>>> FWIW, I was able to build and boot core-image-sato with the rt
>>> kernel:
>>>
>>> Linux sugarbay 3.0.3-rt8-yocto-preempt-rt+ #1 SMP PREEMPT RT Wed
>>> Aug 31 21:33:27 CDT 2011 x86_64 GNU/Linux
>>>
>>> using the following commits:
>>>
>>> poky/master 705ec50edda7f7fb8c132238fe3f1477384a470e meta/intel
>>> 902d2f3c919cd1d870dc8d35a7521cbba42e53ea
>>>
>>> Actually, meta/intel was that commit with Darren's grub patch on
>>> top (meta-intel/dvhart/grub-freetype).
>>>
>>
>> Kishore, would you try with a clean build and see if this works for
>> you?
>>
>> I'm going to try and build first without -rt and then with rt and see
>> if I can reproduce the issue.
>>
>> Thanks,
>>
>> Darren
>>
>>> Tom
>>>
>>>>
>>>>
>>>> Attached is the build log.
>>>>
>>>>
>>>>
>>>> Could you please let me know what went wrong?
>>>>
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Kishore.
>>>>
>>>>
>>>
>>>
>>
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] RT kernel with core-image-sato build failed for sugarbay

[Bodke, Kishore K]

Hi Darren,

With the below Tom's commit IDs, the build was success and I am moving ahead 
with this.
I am not blocked.  I was also able to build and boot the Crystalforest BSP.

Thanks
Kishore.


-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com] 
Sent: Tuesday, September 06, 2011 10:42 AM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] RT kernel with core-image-sato build failed for sugarbay

On 09/01/2011 03:05 PM, Bodke, Kishore K wrote:
> For the build I removed the rttests in the IMAGE_INSTALL , so it is not 
> showing up here.
> 
> bitbake -e core-image-sato | egrep "IMAGE_INSTALL="   
> 
> # MULTILIB_IMAGE_INSTALL= 
> # IMAGE_INSTALL=${POKY_BASE_INSTALL}
> IMAGE_INSTALL="task-core-boot task-base-extended"
> 
> I will rebuild with rttests and send the output.

Hi Kishore,

Where are you with this? Are you unblocked and moving ahead?

Thanks,

Darren

> 
> Thanks
> Kishore.
> 
> -Original Message-
> From: Darren Hart [mailto:dvh...@linux.intel.com] 
> Sent: Thursday, September 01, 2011 2:52 PM
> To: Bodke, Kishore K
> Cc: Zanussi, Tom; yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul
> Subject: Re: RT kernel with core-image-sato build failed for sugarbay
> 
> Can you report the output of:
> 
> $ bitbake -e core-image-sato | egrep "^IMAGE_INSTALL="
> 
> Thanks,
> 
> Darren
> 
> On 09/01/2011 02:14 PM, Bodke, Kishore K wrote:
>> Yeah, it is the same do_rootfs failure I get for both the builds.
>> Thanks
>> Kishore.
>>
>> -Original Message-
>> From: Darren Hart [mailto:dvh...@linux.intel.com] 
>> Sent: Thursday, September 01, 2011 2:08 PM
>> To: Bodke, Kishore K
>> Cc: Zanussi, Tom; yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul
>> Subject: Re: RT kernel with core-image-sato build failed for sugarbay
>>
>> On 09/01/2011 02:01 PM, Bodke, Kishore K wrote:
>>> Clean build with the below TOM's two commit IDs worked for me, if I
>>> do not add IMAGE_INSTALL += "rttests" for sugarbay.
>>>
>>> It failed if I add the IMAGE_INSTALL += "rttests"
>>
>> Do you get the same error? If so, it's starting to sound like the second
>> build is what fails since neither of your failure scenarios include
>> a change that's related to the failure. Perhaps an issue with sstate...
>>
>> --
>> Darren
>>
>>>
>>> Thanks Kishore. -Original Message- From: Darren Hart
>>> [mailto:dvh...@linux.intel.com] Sent: Thursday, September 01, 2011
>>> 1:57 PM To: Zanussi, Tom Cc: Bodke, Kishore K;
>>> yocto@yoctoproject.org; Hart, Darren; Saxena, Rahul Subject: Re: RT
>>> kernel with core-image-sato build failed for sugarbay
>>>
>>>
>>>
>>> On 08/31/2011 09:19 PM, Tom Zanussi wrote:
>>>>
>>>> On Wed, 2011-08-31 at 16:49 -0700, Bodke, Kishore K wrote:
>>>>> Hi,
>>>>>
>>>>>
>>>>>
>>>>> I am trying to build core-image-sato with rt kernel for sugarbay
>>>>> and it fails for the do_rootfs .
>>>>>
>>>>
>>>> FWIW, I was able to build and boot core-image-sato with the rt
>>>> kernel:
>>>>
>>>> Linux sugarbay 3.0.3-rt8-yocto-preempt-rt+ #1 SMP PREEMPT RT Wed
>>>> Aug 31 21:33:27 CDT 2011 x86_64 GNU/Linux
>>>>
>>>> using the following commits:
>>>>
>>>> poky/master 705ec50edda7f7fb8c132238fe3f1477384a470e meta/intel
>>>> 902d2f3c919cd1d870dc8d35a7521cbba42e53ea
>>>>
>>>> Actually, meta/intel was that commit with Darren's grub patch on
>>>> top (meta-intel/dvhart/grub-freetype).
>>>>
>>>
>>> Kishore, would you try with a clean build and see if this works for
>>> you?
>>>
>>> I'm going to try and build first without -rt and then with rt and see
>>> if I can reproduce the issue.
>>>
>>> Thanks,
>>>
>>> Darren
>>>
>>>> Tom
>>>>
>>>>>
>>>>>
>>>>> Attached is the build log.
>>>>>
>>>>>
>>>>>
>>>>> Could you please let me know what went wrong?
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> Kishore.
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] build fails if poky-extras added to bblayers.conf

[Bodke, Kishore K]

Hi All,

We get a strange build error all of sudden today.  We did not change any files, 
just started a fresh build and it failed at the very beginning.

If I remove poky-extras/meta-kernel-dev the build works fine though.

Below is the error message.  Could any one let me know what could be the issue?

Pseudo is not present but is required, building this first before the main build
ERROR: Failure expanding variable SRCPV, expression was 
${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher 
failure for URL: 'None'. Fetch command export HOME="/home/kishore"; export 
SSH_AGENT_PID="1692"; export SSH_AUTH_SOCK="/tmp/keyring-EQAQTf/ssh"; export 
no_proxy="localhost,127.0.0.0/8,*.local"; export 
https_proxy="https://proxy.sc.intel.com:911/";; export 
ftp_proxy="http://proxy.sc.intel.com:911/";; export 
http_proxy="http://proxy.sc.intel.com:911/";; export 
GIT_CONFIG="/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/usr/etc/gitconfig";
 export GIT_PROXY_COMMAND="/usr/local/bin/git-proxy"; export 
PATH="/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/usr/bin/x86_64-poky-linux:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/crystalforest/usr/bin/crossscripts:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/usr/sbin:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/usr/bin:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/sbin:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux//bin:/usr/local/src/crf/yocto/bitbake/bin/:/usr/local/src/crf/yocto/scripts:/usr/local/src/crf/yocto/bitbake/bin/:/usr/local/src/crf/yocto/scripts:/usr/local/src/crf/yocto/bitbake/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/src/crf/yocto/scripts";
 git ls-remote 
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git master 
failed with signal 128, output:
nc: read failed (0/10): Broken pipe
fatal: The remote end hung up unexpectedly

ERROR: Command execution failed: Exited with 1

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] build fails if poky-extras added to bblayers.conf

[Bodke, Kishore K]

Yeah. After removing the linux-korg.bb build started working.

Thanks
Kishore.

-Original Message-
From: Zanussi, Tom 
Sent: Wednesday, September 07, 2011 4:29 PM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] build fails if poky-extras added to bblayers.conf

On Wed, 2011-09-07 at 16:19 -0700, Bodke, Kishore K wrote:
> Hi All,
> 
>  
> 
> We get a strange build error all of sudden today.  We did not change
> any files, just started a fresh build and it failed at the very
> beginning.  
> 
>  
> 
> If I remove poky-extras/meta-kernel-dev the build works fine though.
> 
>  
> 
> Below is the error message.  Could any one let me know what could be
> the issue?
> 

Try removing or renaming linux-korg.bb to something without .bb on the
end.  Looks like it's timing out trying to resolve the git.kernel.org
address.

Tom

>  
> 
> Pseudo is not present but is required, building this first before the
> main build
> 
> ERROR: Failure expanding variable SRCPV, expression was
> ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError:
> Fetcher failure for URL: 'None'. Fetch command export
> HOME="/home/kishore"; export SSH_AGENT_PID="1692"; export
> SSH_AUTH_SOCK="/tmp/keyring-EQAQTf/ssh"; export
> no_proxy="localhost,127.0.0.0/8,*.local"; export
> https_proxy="https://proxy.sc.intel.com:911/";; export
> ftp_proxy="http://proxy.sc.intel.com:911/";; export
> http_proxy="http://proxy.sc.intel.com:911/";; export
> GIT_CONFIG="/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/usr/etc/gitconfig";
>  export GIT_PROXY_COMMAND="/usr/local/bin/git-proxy"; export 
> PATH="/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/usr/bin/x86_64-poky-linux:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/crystalforest/usr/bin/crossscripts:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/usr/sbin:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/usr/bin:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux/sbin:/usr/local/src/crf/yocto/buildcrfrtqat4/tmp/sysroots/x86_64-linux//bin:/usr/local/src/crf/yocto/bitbake/bin/:/usr/local/src/crf/yocto/scripts:/usr/local/src/crf/yocto/bitbake/bin/:/usr/local/src/crf/yocto/scripts:/usr/local/src/crf/yocto/bitbake/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/src/crf/yocto/scripts";
>  git ls-remote git://git.kernel.org/pub/scm/linux/kernel/git/torval
 ds/linux-2.6.git master failed with signal 128, output:
> 
> nc: read failed (0/10): Broken pipe
> 
> fatal: The remote end hung up unexpectedly
> 
>  
> 
> ERROR: Command execution failed: Exited with 1
> 
>  
> 
> Thanks
> 
> Kishore.
> 
> 


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

[yocto] No /lib64 directory in yocto

[Bodke, Kishore K]

Hi,

When I boot the Yocto kernel on the target I don't see the /lib64 directory.

Some of my packages I build with Yocto are not working because of no .so or any 
other files  in /lib64/ .

External packages are looking for library files in /lib64 directory.

Is there any way that we can have /lib64 directory on Yocto ?

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] preempt-rt kernel shutdown now command does not work

[Bodke, Kishore K]

Hi,

"shutdown -h now" command is not working on core-image-sato image with 
preempt-rt kernel 3.0.4  on Romley and crystal forest BSP

I get
Warning**: could not initialize ACPI battery.
Xinit: connection to X server lost.
xinit: uexpected signal 15

Does anybody see the same problem on other meta-intel BSPs?

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] preempt-rt kernel shutdown now command does not work

[Bodke, Kishore K]

Hi Darren,

For the non-rt "shutdown now" works perfectly fine. 
For the rt kernel, after the command is issued, it tries to halt the system and 
hangs there  forever after the connection to the X server is lost.

Thanks
Kishore.

-Original Message-
From: Hart, Darren 
Sent: Thursday, September 29, 2011 6:44 PM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: preempt-rt kernel shutdown now command does not work

On 09/29/2011 05:54 PM, Bodke, Kishore K wrote:
> Hi,
> 
> "shutdown -h now" command is not working on core-image-sato image
> with preempt-rt kernel 3.0.4  on Romley and crystal forest BSP
> 
> I get Warning**: could not initialize ACPI battery. Xinit: connection
> to X server lost. xinit: uexpected signal 15

Hi Kishore,


I don't know that I've tried that specific command.

I see the unexpected signal message when shutting down the qemux86 sato
image (non-rt) with that or the halt command, but it does shut all the
way down. In your case does the system continue to be responsive after
issuing the command?


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 1/2] meta-romley: Fix BSP description in romley.conf

[Bodke, Kishore K]

Acked-by: Kishore Bodke  

Thanks
Kishore.

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of tom.zanu...@intel.com
Sent: Friday, October 28, 2011 7:00 AM
To: yocto@yoctoproject.org
Subject: [yocto] [PATCH 1/2] meta-romley: Fix BSP description in romley.conf

From: Tom Zanussi 

The description still had a reference to Sugar Bay; this changes it to
Romley.

Signed-off-by: Tom Zanussi 
---
 meta-romley/conf/machine/romley.conf |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-romley/conf/machine/romley.conf 
b/meta-romley/conf/machine/romley.conf
index 38bd17a..2dcb5db 100644
--- a/meta-romley/conf/machine/romley.conf
+++ b/meta-romley/conf/machine/romley.conf
@@ -1,7 +1,7 @@
 #@TYPE: Machine
 #@NAME: romley
 
-#@DESCRIPTION: Machine configuration for Sugar Bay systems
+#@DESCRIPTION: Machine configuration for Romley systems
 # i.e. Sandy Bridge + Patsburg Chipset
 
 require conf/machine/include/tune-x86_64.inc
-- 
1.7.0.4

___
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: [yocto] [PATCH 2/2] meta-romley: change references to sugarbay in linux-yocto-rt_3.0.bbappend

[Bodke, Kishore K]

Acked-by: Kishore Bodke  

Thanks
Kishore.

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of tom.zanu...@intel.com
Sent: Friday, October 28, 2011 7:00 AM
To: yocto@yoctoproject.org
Subject: [yocto] [PATCH 2/2] meta-romley: change references to sugarbay in 
linux-yocto-rt_3.0.bbappend

From: Tom Zanussi 

There are still references to sugarbay in linux-yocto-rt_3.0.bbappend;
this changes them to romley.

Signed-off-by: Tom Zanussi 
---
 .../linux/linux-yocto-rt_3.0.bbappend  |6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend 
b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
index d630dc4..1551ccf 100644
--- a/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
+++ b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.0.bbappend
@@ -3,6 +3,6 @@ COMPATIBLE_MACHINE_romley = "romley"
 KMACHINE_romley  = "romley"
 
 # Update the following to use a different BSP branch or meta SRCREV
-#KBRANCH_sugarbay  = "yocto/standard/preempt-rt/base"
-#SRCREV_machine_pn-linux-yocto-rt_sugarbay ?= 
-#SRCREV_meta_pn-linux-yocto-rt_sugarbay ?= 
+#KBRANCH_romley  = "yocto/standard/preempt-rt/base"
+#SRCREV_machine_pn-linux-yocto-rt_romley ?= 
+#SRCREV_meta_pn-linux-yocto-rt_romley ?= 
-- 
1.7.0.4

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

[yocto] Chromium browser for Yocto BSPs

[Bodke, Kishore K]

Hi,
I am trying to plugin the Chromium browser for one of meta-intel bsp.

I get the build failure 
flash-plugin_10.3.183.10.bb
 file for trying to fetch the flash plugin from different mirrors and not able 
to find.

I am building with bitbake core-image-m2m-jdk.

Attached is the log.

Does anyone saw the same failure?

Thanks
Kishore.


log.do_fetch.29542
Description: log.do_fetch.29542
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] meta-intel/meta-romley build fail for master branch

[Bodke, Kishore K]

Hi

I see the build fail for the poky/master and meta-intel/master branch for 
Romley BSP for the  poky/meta/recipes-graphics/xorg-lib/libx11-trim_1.4.4.bb 
file.

By seeing the build log it looks like it is failing to apply the 
keysymdef_include.patch in poky/meta/recipes-graphics/xorg-lib/libx11-1.4.4/ 
keysymdef_include.patch

checking keysym definitions... configure: error: Cannot find keysymdef.h
| ERROR: oe_runconf failed

Attached is the full log.

Any clue here please?

Thanks
Kishore.


romley.log
Description: romley.log
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

Hi,

I get failure for the linux-yoctort_3.0.bb file for the poky Edison branch.
Darren told that it was fixed and merged to master.

I wanted to bring to the list about this error message.

ERROR: Function 'do_kernel_configme' failed (see 
/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
 for further information)
ERROR: Logfile of failure stored in: 
/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
Log data follows:
| [INFO] doing kernel configme
| [INFO] Branch yocto/standard/preempt-rt/base used by common-pc-preempt-rt.scc
| [INFO] collecting configs in ./meta/meta-series
| mv: cannot stat 
`/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
 No such file or directory
| creation of pre-processed config data failed
| config of yocto/standard/preempt-rt/base (common-pc-preempt-rt.scc) failed
| ERROR: Function 'do_kernel_configme' failed (see 
/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
 for further information)
NOTE: package 
linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1:
 task do_kernel_configme: Failed
ERROR: Task 716 
(/usr/local/src/yocto_1_1_release/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
 do_kernel_configme) failed with exit code '1'
Waiting for 7 active tasks to finish:
0: acl-native-2.2.51-r2 do_configure (pid 12164)
1: elfutils-native-0.148-r3 do_install (pid 19851)
2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
3: font-util-native-1.2.0-r2.1 do_configure (pid 14632)
4: bison-native-2.5-r1 do_configure (pid 20206)
5: dbus-native-1.4.12-r0 do_configure (pid 20209)
6: opensp-native-1.5-r2 do_configure (pid 20213)
Waiting for 6 active tasks to finish:
0: acl-native-2.2.51-r2 do_configure (pid 12164)
1: elfutils-native-0.148-r3 do_install (pid 19851)
2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
3: font-util-native-1.2.0-r2.1 do_configure (pid 14632)
4: bison-native-2.5-r1 do_configure (pid 20206)
5: dbus-native-1.4.12-r0 do_configure (pid 20209)
NOTE: package opensp-native-1.5-r2: task do_configure: Succeeded
Waiting for 5 active tasks to finish:
0: acl-native-2.2.51-r2 do_configure (pid 12164)
1: elfutils-native-0.148-r3 do_install (pid 19851)
2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
3: bison-native-2.5-r1 do_configure (pid 20206)
4: dbus-native-1.4.12-r0 do_configure (pid 20209)
NOTE: package font-util-native-1.2.0-r2.1: task do_configure: Succeeded
Waiting for 4 active tasks to finish:
0: acl-native-2.2.51-r2 do_configure (pid 12164)
1: elfutils-native-0.148-r3 do_install (pid 19851)
2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
3: bison-native-2.5-r1 do_configure (pid 20206)
NOTE: package dbus-native-1.4.12-r0: task do_configure: Succeeded
Waiting for 3 active tasks to finish:
0: elfutils-native-0.148-r3 do_install (pid 19851)
1: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
2: bison-native-2.5-r1 do_configure (pid 20206)
NOTE: package acl-native-2.2.51-r2: task do_configure: Succeeded
Waiting for 2 active tasks to finish:
0: elfutils-native-0.148-r3 do_install (pid 19851)
1: bison-native-2.5-r1 do_configure (pid 20206)
NOTE: package kbproto-native-1_1.0.5-r0: task do_configure: Succeeded
Waiting for 1 active tasks to finish:
0: bison-native-2.5-r1 do_configure (pid 20206)
NOTE: package elfutils-native-0.148-r3: task do_install: Succeeded
NOTE: package bison-native-2.5-r1: task do_configure: Succeeded
ERROR: 
'/usr/local/src/yocto_1_1_release/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb'
 failed

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

Yeah.  I am using local bare clone for the linux-yocto-3.0 and using 
poky-extras/meta-kernel-dev in my bblayers.conf for my build.
Sorry for not mentioning this before.

Thanks
Kishore.

-Original Message-
From: Hart, Darren 
Sent: Tuesday, December 13, 2011 3:15 PM
To: Bruce Ashfield
Cc: Bodke, Kishore K; yocto@yoctoproject.org
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

On 12/13/2011 03:05 PM, Bruce Ashfield wrote:
> On 11-12-13 5:50 PM, Bodke, Kishore K wrote:
>> Hi,
>>
>> I get failure for the linux-yoctort_3.0.bb file for the poky Edison branch.
>>
>> Darren told that it was fixed and merged to master.
> 
> This shouldn't be happening on edison at all. The changes to the
> kernel recipes/tools to use the merge_config.sh should never have
> showed up in edison. That's yocto 1.2 development work.
> 
> So the fix for this is to find out what leaked into edison and
> revert it. I'll have a look at that later tonight.

No no. Kishore is using meta-kernel-dev. As such he is getting the
latest linux-yocto repository and SRC_REVs. The question, I think, is
really why isn't the kern-tools-native bbappend from meta-kernel-dev
doing this for him.

--
Darren

> 
> Bruce
> 
>>
>> I wanted to bring to the list about this error message.
>>
>> ERROR: Function 'do_kernel_configme' failed (see
>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>> for further information)
>>
>> ERROR: Logfile of failure stored in:
>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>>
>> Log data follows:
>>
>> | [INFO] doing kernel configme
>>
>> | [INFO] Branch yocto/standard/preempt-rt/base used by
>> common-pc-preempt-rt.scc
>>
>> | [INFO] collecting configs in ./meta/meta-series
>>
>> | mv: cannot stat
>> `/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
>> No such file or directory
>>
>> | creation of pre-processed config data failed
>>
>> | config of yocto/standard/preempt-rt/base (common-pc-preempt-rt.scc) failed
>>
>> | ERROR: Function 'do_kernel_configme' failed (see
>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>> for further information)
>>
>> NOTE: package
>> linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1:
>> task do_kernel_configme: Failed
>>
>> ERROR: Task 716
>> (/usr/local/src/yocto_1_1_release/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
>> do_kernel_configme) failed with exit code '1'
>>
>> Waiting for 7 active tasks to finish:
>>
>> 0: acl-native-2.2.51-r2 do_configure (pid 12164)
>>
>> 1: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
>>
>> 3: font-util-native-1.2.0-r2.1 do_configure (pid 14632)
>>
>> 4: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> 5: dbus-native-1.4.12-r0 do_configure (pid 20209)
>>
>> 6: opensp-native-1.5-r2 do_configure (pid 20213)
>>
>> Waiting for 6 active tasks to finish:
>>
>> 0: acl-native-2.2.51-r2 do_configure (pid 12164)
>>
>> 1: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
>>
>> 3: font-util-native-1.2.0-r2.1 do_configure (pid 14632)
>>
>> 4: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> 5: dbus-native-1.4.12-r0 do_configure (pid 20209)
>>
>> NOTE: package opensp-native-1.5-r2: task do_configure: Succeeded
>>
>> Waiting for 5 active tasks to finish:
>>
>> 0: acl-native-2.2.51-r2 do_configure (pid 12164)
>>
>> 1: elfutils-native-0.148-r3 do_install (pid 19851)
>>
>> 2: kbproto-native-1_1.0.5-r0 do_configure (pid 20113)
>>
>> 3: bison-native-2.5-r1 do_configure (pid 20206)
>>
>> 4: dbus-native-1.4.12-r0 do_configu

Re: [yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

Yes. 
Its with poky Edison with poky-extras/meta-kernel-dev master branch I am using 
for my build.

Thanks
Kishore.

-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
Sent: Tuesday, December 13, 2011 3:25 PM
To: Bodke, Kishore K
Cc: Hart, Darren; yocto@yoctoproject.org
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

On 11-12-13 6:17 PM, Bodke, Kishore K wrote:
> Yeah.  I am using local bare clone for the linux-yocto-3.0 and using 
> poky-extras/meta-kernel-dev in my bblayers.conf for my build.
> Sorry for not mentioning this before.

Aha. This is completely different then. As Darren mentioned, the bbappend
should be getting the latest tools, I can look into that.

But to be clear, is this an edison branch + meta-kernel-dev ? That
will cause problems at some point (and I'm not sure if that is what
is happening here yet), since recipe updates to use the new tools
wouldn't be reflected in that branch while you are fed the new tools.

Cheers,

Bruce

>
> Thanks
> Kishore.
>
> -Original Message-
> From: Hart, Darren
> Sent: Tuesday, December 13, 2011 3:15 PM
> To: Bruce Ashfield
> Cc: Bodke, Kishore K; yocto@yoctoproject.org
> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
> branch.
>
> On 12/13/2011 03:05 PM, Bruce Ashfield wrote:
>> On 11-12-13 5:50 PM, Bodke, Kishore K wrote:
>>> Hi,
>>>
>>> I get failure for the linux-yoctort_3.0.bb file for the poky Edison branch.
>>>
>>> Darren told that it was fixed and merged to master.
>>
>> This shouldn't be happening on edison at all. The changes to the
>> kernel recipes/tools to use the merge_config.sh should never have
>> showed up in edison. That's yocto 1.2 development work.
>>
>> So the fix for this is to find out what leaked into edison and
>> revert it. I'll have a look at that later tonight.
>
> No no. Kishore is using meta-kernel-dev. As such he is getting the
> latest linux-yocto repository and SRC_REVs. The question, I think, is
> really why isn't the kern-tools-native bbappend from meta-kernel-dev
> doing this for him.
>
> --
> Darren
>
>>
>> Bruce
>>
>>>
>>> I wanted to bring to the list about this error message.
>>>
>>> ERROR: Function 'do_kernel_configme' failed (see
>>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>>> for further information)
>>>
>>> ERROR: Logfile of failure stored in:
>>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>>>
>>> Log data follows:
>>>
>>> | [INFO] doing kernel configme
>>>
>>> | [INFO] Branch yocto/standard/preempt-rt/base used by
>>> common-pc-preempt-rt.scc
>>>
>>> | [INFO] collecting configs in ./meta/meta-series
>>>
>>> | mv: cannot stat
>>> `/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
>>> No such file or directory
>>>
>>> | creation of pre-processed config data failed
>>>
>>> | config of yocto/standard/preempt-rt/base (common-pc-preempt-rt.scc) failed
>>>
>>> | ERROR: Function 'do_kernel_configme' failed (see
>>> /usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.18502
>>> for further information)
>>>
>>> NOTE: package
>>> linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1:
>>> task do_kernel_configme: Failed
>>>
>>> ERROR: Task 716
>>> (/usr/local/src/yocto_1_1_release/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
>>> do_kernel_configme) failed with exit code '1'
>>>
>>> Waiting for 7 active tasks to finish:
>>>
>>> 0: acl-native-2.2.51-r2 do_configure (pid 12164)
>>>
>>> 1: elfutils-native-0.148-r3 do_install (pid 19851)
>>>
>>> 2: kbproto-native-1_1.0.5-r0 do_config

Re: [yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

Hi,
Just wanted to know if this got fixed?  
Everytime I give the build I have to cerry-pick the patches.
But even after applying the patches, the build went through, but the image does 
not boot.

Thanks
Kishore.

-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
Sent: Wednesday, December 14, 2011 6:07 AM
To: Hart, Darren
Cc: Bodke, Kishore K; yocto@yoctoproject.org
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

On 11-12-14 12:47 AM, Darren Hart wrote:
> On 12/13/2011 09:13 PM, Bruce Ashfield wrote:
>> On 11-12-13 6:26 PM, Bodke, Kishore K wrote:
>>> Yes.
>>> Its with poky Edison with poky-extras/meta-kernel-dev master branch I am 
>>> using for my build.
>>
>> This is likely the problem. I use and test meta-kernel-dev everyday,
>> but that's always against master. I keep them in lockstep, since
>> meta-kernel-dev never really 'releases'.
>>
>> That being said, we can figure out a combination that works. The
>> best thing to do, would be to remove the kern-tools-native bbappend
>> from your meta-kernel-dev layer (for now). You don't want the new
>> tools.
>
> That won't work.  He is using the latest kernel which has needs
> merge_config.sh - as I ran into myself last week. I had Kishore

There's still a way it will work, merge_config.sh is only ever
called from the kern-tools. There shouldn't be any non kern-tools
calls to merge_config.sh, the error:

  mv: cannot stat
  `/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest- 
poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
  No such file or directory

Could only come from using the latest configme script from the
kern-tools. So *something* newer than any SRCREV found on the
edison branch is being used there.

> cherry-pick the last two patches to kern-tools-native from master and
> that got things going for him. So again, the question is: Why didn't the
> kern-tools-native bbappend do that for him?

Aha. I may know the answer to that. The meta variant of the recipe looks
to assign the SRCREV in a way that the bbappend can't change. I did
this change during the day, but completely forgot when sending the
email. Can someone try this to see if it's the fix ?

index fb66211..bc9a6b9 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,8 +4,8 @@ LIC_FILES_CHKSUM = 
"file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d8

  DEPENDS = "git-native guilt-native"

-SRCREV = "eb3ed64cea80d23ffb28dfeaeb02cdfe3fb29340"
-PR = r12
+SRCREV ?= "eb3ed64cea80d23ffb28dfeaeb02cdfe3fb29340"
+PR = r13
  PV = "0.1+git${SRCPV}"

.. and Then I'll do a pull request.

But as to why it's happening, I have no idea, autorev should pick it
up. That's down in the guts of bitbake, and for some reason the old
downloaded variant doesn't seem to be updating.

Bruce

>
> --
> Darren
>
>>
>> If that doesn't fix the problem, look for merge_log.txt in your
>> linux/meta/cfg/ directory structure and that will tell us exactly
>> what is going wrong.
>>
>> Bruce
>>
>>>
>>> Thanks
>>> Kishore.
>>>
>>> -Original Message-
>>> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>>> Sent: Tuesday, December 13, 2011 3:25 PM
>>> To: Bodke, Kishore K
>>> Cc: Hart, Darren; yocto@yoctoproject.org
>>> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
>>> branch.
>>>
>>> On 11-12-13 6:17 PM, Bodke, Kishore K wrote:
>>>> Yeah.  I am using local bare clone for the linux-yocto-3.0 and using 
>>>> poky-extras/meta-kernel-dev in my bblayers.conf for my build.
>>>> Sorry for not mentioning this before.
>>>
>>> Aha. This is completely different then. As Darren mentioned, the bbappend
>>> should be getting the latest tools, I can look into that.
>>>
>>> But to be clear, is this an edison branch + meta-kernel-dev ? That
>>> will cause problems at some point (and I'm not sure if that is what
>>> is happening here yet), since recipe updates to use the new tools
>>> wouldn't be reflected in that branch while you are fed the new tools.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Thanks
>>>> Kishore.
>>>>
>>>> -Original Message-
>>>> From: 

Re: [yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

I will try out with the Bruce's patch.

It stops after these below boot messages.

Failed to execute /init
Kernel panic - Not syncing: No init found. Try passing init=option to kernel
Pid: 1 comm: swapper not tainited. 3.0.12-rt30-yocto-standard-prempt-rt+

Thanks
Kishore.
-Original Message-
From: Hart, Darren 
Sent: Friday, December 16, 2011 11:33 AM
To: Bodke, Kishore K
Cc: Bruce Ashfield; yocto@yoctoproject.org
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

On 12/16/2011 11:27 AM, Bodke, Kishore K wrote:
> Hi,
> Just wanted to know if this got fixed?  

Bruce sent a patch to test, it's included in the history below. Did you
try this without the cherry-picked patches to see if it works for you?
If not, could you please do so and let Bruce know? If it works for you,
we can push it into the meta-kernel-dev layer.

> Everytime I give the build I have to cerry-pick the patches.
> But even after applying the patches, the build went through, but the image 
> does not boot.

Can you provide some more details here? Does the bootloader come up?
Does the kernel output anything? What is the last thing displayed?

--
Darren

> 
> Thanks
> Kishore.
> 
> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
> Sent: Wednesday, December 14, 2011 6:07 AM
> To: Hart, Darren
> Cc: Bodke, Kishore K; yocto@yoctoproject.org
> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
> branch.
> 
> On 11-12-14 12:47 AM, Darren Hart wrote:
>> On 12/13/2011 09:13 PM, Bruce Ashfield wrote:
>>> On 11-12-13 6:26 PM, Bodke, Kishore K wrote:
>>>> Yes.
>>>> Its with poky Edison with poky-extras/meta-kernel-dev master branch I am 
>>>> using for my build.
>>>
>>> This is likely the problem. I use and test meta-kernel-dev everyday,
>>> but that's always against master. I keep them in lockstep, since
>>> meta-kernel-dev never really 'releases'.
>>>
>>> That being said, we can figure out a combination that works. The
>>> best thing to do, would be to remove the kern-tools-native bbappend
>>> from your meta-kernel-dev layer (for now). You don't want the new
>>> tools.
>>
>> That won't work.  He is using the latest kernel which has needs
>> merge_config.sh - as I ran into myself last week. I had Kishore
> 
> There's still a way it will work, merge_config.sh is only ever
> called from the kern-tools. There shouldn't be any non kern-tools
> calls to merge_config.sh, the error:
> 
>   mv: cannot stat
>   `/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest- 
> poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
>   No such file or directory
> 
> Could only come from using the latest configme script from the
> kern-tools. So *something* newer than any SRCREV found on the
> edison branch is being used there.
> 
>> cherry-pick the last two patches to kern-tools-native from master and
>> that got things going for him. So again, the question is: Why didn't the
>> kern-tools-native bbappend do that for him?
> 
> Aha. I may know the answer to that. The meta variant of the recipe looks
> to assign the SRCREV in a way that the bbappend can't change. I did
> this change during the day, but completely forgot when sending the
> email. Can someone try this to see if it's the fix ?
> 
> index fb66211..bc9a6b9 100644
> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
> @@ -4,8 +4,8 @@ LIC_FILES_CHKSUM = 
> "file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d8
> 
>   DEPENDS = "git-native guilt-native"
> 
> -SRCREV = "eb3ed64cea80d23ffb28dfeaeb02cdfe3fb29340"
> -PR = r12
> +SRCREV ?= "eb3ed64cea80d23ffb28dfeaeb02cdfe3fb29340"
> +PR = r13
>   PV = "0.1+git${SRCPV}"
> 
> .. and Then I'll do a pull request.
> 
> But as to why it's happening, I have no idea, autorev should pick it
> up. That's down in the guts of bitbake, and for some reason the old
> downloaded variant doesn't seem to be updating.
> 
> Bruce
> 
>>
>> --
>> Darren
>>
>>>
>>> If that doesn't fix the problem, look for merge_log.txt in your
>>> linux/meta/cfg/ directory structure and that will tell us exactly
>>> what is going wrong.
>>>
>>> Bruce
>>>
>>>>
>>>> Thanks
>>>> Kishore.
&g

Re: [yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

I am building core-image-sato.
I have not changed any boot parameters. 
Everything was default settings.

Thanks
Kishore.

-Original Message-
From: Hart, Darren 
Sent: Friday, December 16, 2011 12:18 PM
To: Bodke, Kishore K
Cc: Bruce Ashfield; yocto@yoctoproject.org
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

On 12/16/2011 11:39 AM, Bodke, Kishore K wrote:
> I will try out with the Bruce's patch.
> 
> It stops after these below boot messages.
> 
> Failed to execute /init
> Kernel panic - Not syncing: No init found. Try passing init=option to kernel
> Pid: 1 comm: swapper not tainited. 3.0.12-rt30-yocto-standard-prempt-rt+

Sounds like it isn't mounting the root filesystem. What image format are
you using? What filesystem are you using for your rootfs? What are the
kernel parameters you pass at boot?

--
Darren

> 
> Thanks
> Kishore.
> -Original Message-
> From: Hart, Darren 
> Sent: Friday, December 16, 2011 11:33 AM
> To: Bodke, Kishore K
> Cc: Bruce Ashfield; yocto@yoctoproject.org
> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
> branch.
> 
> On 12/16/2011 11:27 AM, Bodke, Kishore K wrote:
>> Hi,
>> Just wanted to know if this got fixed?  
> 
> Bruce sent a patch to test, it's included in the history below. Did you
> try this without the cherry-picked patches to see if it works for you?
> If not, could you please do so and let Bruce know? If it works for you,
> we can push it into the meta-kernel-dev layer.
> 
>> Everytime I give the build I have to cerry-pick the patches.
>> But even after applying the patches, the build went through, but the image 
>> does not boot.
> 
> Can you provide some more details here? Does the bootloader come up?
> Does the kernel output anything? What is the last thing displayed?
> 
> --
> Darren
> 
>>
>> Thanks
>> Kishore.
>>
>> -Original Message-
>> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
>> Sent: Wednesday, December 14, 2011 6:07 AM
>> To: Hart, Darren
>> Cc: Bodke, Kishore K; yocto@yoctoproject.org
>> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
>> branch.
>>
>> On 11-12-14 12:47 AM, Darren Hart wrote:
>>> On 12/13/2011 09:13 PM, Bruce Ashfield wrote:
>>>> On 11-12-13 6:26 PM, Bodke, Kishore K wrote:
>>>>> Yes.
>>>>> Its with poky Edison with poky-extras/meta-kernel-dev master branch I am 
>>>>> using for my build.
>>>>
>>>> This is likely the problem. I use and test meta-kernel-dev everyday,
>>>> but that's always against master. I keep them in lockstep, since
>>>> meta-kernel-dev never really 'releases'.
>>>>
>>>> That being said, we can figure out a combination that works. The
>>>> best thing to do, would be to remove the kern-tools-native bbappend
>>>> from your meta-kernel-dev layer (for now). You don't want the new
>>>> tools.
>>>
>>> That won't work.  He is using the latest kernel which has needs
>>> merge_config.sh - as I ran into myself last week. I had Kishore
>>
>> There's still a way it will work, merge_config.sh is only ever
>> called from the kern-tools. There shouldn't be any non kern-tools
>> calls to merge_config.sh, the error:
>>
>>   mv: cannot stat
>>   `/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crystalforest- 
>> poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
>>   No such file or directory
>>
>> Could only come from using the latest configme script from the
>> kern-tools. So *something* newer than any SRCREV found on the
>> edison branch is being used there.
>>
>>> cherry-pick the last two patches to kern-tools-native from master and
>>> that got things going for him. So again, the question is: Why didn't the
>>> kern-tools-native bbappend do that for him?
>>
>> Aha. I may know the answer to that. The meta variant of the recipe looks
>> to assign the SRCREV in a way that the bbappend can't change. I did
>> this change during the day, but completely forgot when sending the
>> email. Can someone try this to see if it's the fix ?
>>
>> index fb66211..bc9a6b9 100644
>> --- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> +++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
>> @@ -4,8 +4,8 @@ LIC_FILES_CHKSUM = 
&g

Re: [yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

Hi,
I still get the same error below after changing the kern-tools-native_git.bb 
file.

SRCREV ?= "364437739c45a5e771d1f7b3ac73c35f1328fd97"
PR = r11


ERROR: Function 'do_kernel_configme' failed (see 
/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
 for further information)
ERROR: Logfile of failure stored in: 
/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
Log data follows:
| [INFO] doing kernel configme
| [INFO] Branch yocto/standard/preempt-rt/base used by common-pc-preempt-rt.scc
| [INFO] collecting configs in ./meta/meta-series
| mv: cannot stat 
`/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
 No such file or directory
| creation of pre-processed config data failed
| config of yocto/standard/preempt-rt/base (common-pc-preempt-rt.scc) failed
| ERROR: Function 'do_kernel_configme' failed (see 
/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
 for further information)
NOTE: package 
linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1:
 task do_kernel_configme: Failed
NOTE: package gcc-cross-4.6.1+svnr175454-r10: task do_configure: Started
ERROR: Task 716 
(/usr/local/src/yocto_1_1/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb, 
do_kernel_configme) failed with exit code '1'

Thanks
Kishore.

-Original Message-
From: Hart, Darren
Sent: Friday, December 16, 2011 3:08 PM
To: Bodke, Kishore K
Cc: Bruce Ashfield; yocto@yoctoproject.org
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

On 12/16/2011 02:12 PM, Bodke, Kishore K wrote:
> I am building core-image-sato.
> I have not changed any boot parameters.
> Everything was default settings.

By image format I mean are you using a live image?
core-image-sato-*.hddimg or are you formatting a disk and copying over
contents of the rootfs? The kernel parameters are specified in
meta-intel and meta-romley.

My guess is something has gone wrong in the kernel config and the kernel
you built is missing things like vfat, ramfs support, etc.

Can you make your .config available as well as the various log.do* from
the linux-yocto temp directory and the meta-series from the linux source
directory?

--
Darren

>
> Thanks
> Kishore.
>
> -Original Message-
> From: Hart, Darren
> Sent: Friday, December 16, 2011 12:18 PM
> To: Bodke, Kishore K
> Cc: Bruce Ashfield; yocto@yoctoproject.org
> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
> branch.
>
> On 12/16/2011 11:39 AM, Bodke, Kishore K wrote:
>> I will try out with the Bruce's patch.
>>
>> It stops after these below boot messages.
>>
>> Failed to execute /init
>> Kernel panic - Not syncing: No init found. Try passing init=option to kernel
>> Pid: 1 comm: swapper not tainited. 3.0.12-rt30-yocto-standard-prempt-rt+
>
> Sounds like it isn't mounting the root filesystem. What image format are
> you using? What filesystem are you using for your rootfs? What are the
> kernel parameters you pass at boot?
>
> --
> Darren
>
>>
>> Thanks
>> Kishore.
>> -Original Message-
>> From: Hart, Darren
>> Sent: Friday, December 16, 2011 11:33 AM
>> To: Bodke, Kishore K
>> Cc: Bruce Ashfield; yocto@yoctoproject.org
>> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
>> branch.
>>
>> On 12/16/2011 11:27 AM, Bodke, Kishore K wrote:
>>> Hi,
>>> Just wanted to know if this got fixed?
>>
>> Bruce sent a patch to test, it's included in the history below. Did you
>> try this without the cherry-picked patches to see if it works for you?
>> If not, could you please do so and let Bruce know? If it works for you,
>> we can push it into the meta-kernel-dev layer.
>>
>>> Everytime I give the build I have to cerry-pick the patches.
>>> But even after applying the patches, the build went through, but the image 
>>> does not boot.
>>
>> Can you provide some more details here? Does the bootloader come up?
>> Does the kernel output anything? What is the last

Re: [yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

With the attached Darren's kern-tools-native_git.bb file, build was success.
Thanks
Kishore.

-Original Message-
From: Bodke, Kishore K
Sent: Friday, December 16, 2011 5:07 PM
To: Hart, Darren
Cc: Bruce Ashfield; yocto@yoctoproject.org
Subject: RE: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

Hi,
I still get the same error below after changing the kern-tools-native_git.bb 
file.

SRCREV ?= "364437739c45a5e771d1f7b3ac73c35f1328fd97"
PR = r11


ERROR: Function 'do_kernel_configme' failed (see 
/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
 for further information)
ERROR: Logfile of failure stored in: 
/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
Log data follows:
| [INFO] doing kernel configme
| [INFO] Branch yocto/standard/preempt-rt/base used by common-pc-preempt-rt.scc
| [INFO] collecting configs in ./meta/meta-series
| mv: cannot stat 
`/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
 No such file or directory
| creation of pre-processed config data failed
| config of yocto/standard/preempt-rt/base (common-pc-preempt-rt.scc) failed
| ERROR: Function 'do_kernel_configme' failed (see 
/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
 for further information)
NOTE: package 
linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1:
 task do_kernel_configme: Failed
NOTE: package gcc-cross-4.6.1+svnr175454-r10: task do_configure: Started
ERROR: Task 716 
(/usr/local/src/yocto_1_1/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb, 
do_kernel_configme) failed with exit code '1'

Thanks
Kishore.

-Original Message-
From: Hart, Darren
Sent: Friday, December 16, 2011 3:08 PM
To: Bodke, Kishore K
Cc: Bruce Ashfield; yocto@yoctoproject.org
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

On 12/16/2011 02:12 PM, Bodke, Kishore K wrote:
> I am building core-image-sato.
> I have not changed any boot parameters.
> Everything was default settings.

By image format I mean are you using a live image?
core-image-sato-*.hddimg or are you formatting a disk and copying over
contents of the rootfs? The kernel parameters are specified in
meta-intel and meta-romley.

My guess is something has gone wrong in the kernel config and the kernel
you built is missing things like vfat, ramfs support, etc.

Can you make your .config available as well as the various log.do* from
the linux-yocto temp directory and the meta-series from the linux source
directory?

--
Darren

>
> Thanks
> Kishore.
>
> -Original Message-----
> From: Hart, Darren
> Sent: Friday, December 16, 2011 12:18 PM
> To: Bodke, Kishore K
> Cc: Bruce Ashfield; yocto@yoctoproject.org
> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
> branch.
>
> On 12/16/2011 11:39 AM, Bodke, Kishore K wrote:
>> I will try out with the Bruce's patch.
>>
>> It stops after these below boot messages.
>>
>> Failed to execute /init
>> Kernel panic - Not syncing: No init found. Try passing init=option to kernel
>> Pid: 1 comm: swapper not tainited. 3.0.12-rt30-yocto-standard-prempt-rt+
>
> Sounds like it isn't mounting the root filesystem. What image format are
> you using? What filesystem are you using for your rootfs? What are the
> kernel parameters you pass at boot?
>
> --
> Darren
>
>>
>> Thanks
>> Kishore.
>> -Original Message-
>> From: Hart, Darren
>> Sent: Friday, December 16, 2011 11:33 AM
>> To: Bodke, Kishore K
>> Cc: Bruce Ashfield; yocto@yoctoproject.org
>> Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
>> branch.
>>
>> On 12/16/2011 11:27 AM, Bodke, Kishore K wrote:
>>> Hi,
>>> Just wanted to know if this got fixed?
>>
>> Bruce sent a patch to test, it's included in the history below. Did you
>> try this without the cherry-picked patches to see if it works for you?
>> If not, could you please do so and let Bruce know? If it works for you,
>> we can push it into the meta-kernel-dev layer.
>>
&g

Re: [yocto] kernel-tools failure for linux-yoctort_3.0.bb for poky/edison branch.

[Bodke, Kishore K]

Yes. I removed the kern-tools-native_git.bb and it built fine.

Thanks
Kishore.

-Original Message-
From: Hart, Darren
Sent: Friday, December 16, 2011 7:18 PM
To: Bruce Ashfield
Cc: Bodke, Kishore K; yocto@yoctoproject.org
Subject: Re: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
branch.

On 12/16/2011 07:03 PM, Bruce Ashfield wrote:
> On 11-12-16 8:34 PM, Darren Hart wrote:
>> On 12/16/2011 05:22 PM, Bodke, Kishore K wrote:
>>>
>>> With the attached Darren's kern-tools-native_git.bb file, build was success.
>>> Thanks
>>> Kishore.
>>
>> See the patch I just sent:kern-tools: Include do_install() in bbappend
>> for what I believe to be the solution.
>>
>> I suppose the proper solution would be to version the kern-tools-native
>> recipe when major things like that change, but given the nature of this
>> layer, I think the above patch is adequate.
>
> That's not the solution to either problem (well, yes, it's a solution
> and there's nothing inherently wrong with it, it's just covering up
> the underlying issue) which is a layer dependency issue. In this case,
> meta-kernel-dev tracks the master branch of poky, not any other branch
> or version. And that is implicit, not explicit, hence why it got into
> this tangle.
>
> We could simply branch meta-kernel-dev and have an edison branch for
> it, not modify the appends to contain something that will just break
> again in the future.
>
> But meta-kernel-dev isn't officially used by much at the moment, so
> I'm not convinced that branching it is worth the trouble (but I can
> be convinced otherwise). I'd rather either just remove the kern-tools
> bbappend (I'm probably the only one on the planet that really needs
> it), or just trust people to know what they are up to with the
> meta-kernel-dev layer.
>
> Alternatively, we wait for layer dependency tooling and use that :)
>

OK, so with that in mind - Kishore would you rename
kern-tools-native_git.bbappend to end in bbappendDONTUSE and try with that?

This should use the old kern-tools and the old install mechanism, so
long as they match (old:old, new:new), I believe it should work.

--
Darren

> Cheers,
>
> Bruce
>
>>
>> --
>> Darren
>>
>>>
>>> -Original Message-
>>> From: Bodke, Kishore K
>>> Sent: Friday, December 16, 2011 5:07 PM
>>> To: Hart, Darren
>>> Cc: Bruce Ashfield; yocto@yoctoproject.org
>>> Subject: RE: kernel-tools failure for linux-yoctort_3.0.bb for poky/edison 
>>> branch.
>>>
>>> Hi,
>>> I still get the same error below after changing the 
>>> kern-tools-native_git.bb file.
>>>
>>> SRCREV ?= "364437739c45a5e771d1f7b3ac73c35f1328fd97"
>>> PR = r11
>>>
>>>
>>> ERROR: Function 'do_kernel_configme' failed (see 
>>> /usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
>>>  for further information)
>>> ERROR: Logfile of failure stored in: 
>>> /usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
>>> Log data follows:
>>> | [INFO] doing kernel configme
>>> | [INFO] Branch yocto/standard/preempt-rt/base used by 
>>> common-pc-preempt-rt.scc
>>> | [INFO] collecting configs in ./meta/meta-series
>>> | mv: cannot stat 
>>> `/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*':
>>>  No such file or directory
>>> | creation of pre-processed config data failed
>>> | config of yocto/standard/preempt-rt/base (common-pc-preempt-rt.scc) failed
>>> | ERROR: Function 'do_kernel_configme' failed (see 
>>> /usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/temp/log.do_kernel_configme.27942
>>>  for further information)
>>> NOTE: package 
>>> linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1:
>>>  task do_kernel_configme: Failed
>>> NOTE: package gcc-cross-4.6.1+svnr175454-

Re: [yocto] qemu EFI build failure

[Bodke, Kishore K]

I have only 
MACHINE_FEATURES += "efi"
KERNEL_FEATURES_append_cedartrail += "cfg/efi-ext.scc".

I am not having IMAGE_FSTYPES += "live".

Thanks
Kishore.
-Original Message-
From: Hart, Darren 
Sent: Thursday, January 12, 2012 1:20 PM
To: Ahmad, Josef
Cc: yocto@yoctoproject.org; Bodke, Kishore K; Kamble, Nitin A
Subject: Re: [yocto] qemu EFI build failure

On 01/12/2012 10:27 AM, Darren Hart wrote:
> 
> 
> On 01/12/2012 08:19 AM, Josef Ahmad wrote:
>> I tried to build a qemux86 EFI image, by setting:
>> - in my local.conf: IMAGE_FSTYPES += "live"
>> - in poly/meta/conf/machine/qemux86.conf: MACHINE_FEATURES += "efi"
>>
> 
> I haven't tried live images with QEMU. For one thing, they aren't really
> necessary as you can specify all the boot parameters on the qemu command
> line. Is there are reason you want to use the live image specifically?
> 
> Also, in order to properly test EFI in QEMU, you will need to use an EFI
> BIOS - I believe you're aware of this already - but this isn't currently
> supported by the runqemu scripts that ship with yocto.
> 
>> The build gave me the following error:
> 
> 
> I'll do some test builds - it isn't clear to me what is going on here.
> 
> 
> 
>>
>>
>> Has anyone encountered the same error?  I'm not sure I set up the
>> correct configuration. Also, is there another way to append "efi" to
>> MACHINE_FEATURES rather than by modifying qemux86.conf?
> 
> You should be able to do something like:
> MACHINE_FEATURES_append_qemux86 = "efi"
> 
> Note that you will also need to enable the efi support in the kernel,
> which is done with the KERNEL_FEATURES variable, something like:
> KERNEL_FEATURES_append_qemux86 = "conf/efi-ext.scc"
> 
> Either of these can be set in your local.conf.
> 

More accurately:

MACHINE_FEATURES_append_qemux86=" efi pcbios"
KERNEL_FEATURES_append_qemux86=" cfg/efi-ext.scc"
IMAGE_FSTYPES += "live"

With these added to local.conf and building for qemux86 I see the same
configure failures reported by Kishore and Josef:

| ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
| acinclude.m4:363: grub_CHECK_STACK_ARG_PROBE is expanded from...

I've discussed in IRC with Nitin and he thinks this may be related to
the automake update and is looking into it.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Linux RT build fail

[Bodke, Kishore K]

Hi,

I get build failure for the rt.

ERROR: Function 'do_patch' failed (see 
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
 for further information)
ERROR: Logfile of failure stored in: 
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
Log data follows:
| ERROR: Function 'do_patch' failed (see 
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
 for further information)
| Deleted branch meta-temp (was 620917d).
|
| ERROR: patch 
/usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch
 is not available
|
| ERROR. Could not find an excutable target for yocto/standard/preempt-rt/base
| ERROR. Could not locate meta series for preempt-rt-standard
| ERROR. Could not modify yocto/standard/preempt-rt/base
NOTE: package 
linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1:
 task do_patch: Failed
NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded
ERROR: Task 3 
(/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb, 
do_patch) failed with exit code '1'

Is this anything to do with meta-kernel-dev I am using or something else?

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Linux RT build fail

[Bodke, Kishore K]

I get the same build ERRORS without meta-kernel-dev as well.

Thanks
Kishore.

-Original Message-
From: Hart, Darren 
Sent: Monday, January 16, 2012 11:14 AM
To: Bruce Ashfield
Cc: Bodke, Kishore K; yocto@yoctoproject.org
Subject: Re: Linux RT build fail

On 01/16/2012 10:44 AM, Bruce Ashfield wrote:
> On 12-01-16 01:40 PM, Bodke, Kishore K wrote:
>> Hi,
>>
>> I get build failure for the rt.
>>
>> ERROR: Function 'do_patch' failed (see
>> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
>> for further information)
>>
>> ERROR: Logfile of failure stored in:
>> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
>>
>> Log data follows:
>>
>> | ERROR: Function 'do_patch' failed (see
>> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
>> for further information)
>>
>> | Deleted branch meta-temp (was 620917d).
>>
>> |
>>
>> | ERROR: patch
>> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch
>> is not available
> 
> This is the problem. But I could have sworn that I fixed this, and
> send a merge request. When I just checked now, it still looks broken.
> 
> That being said, we should have seen this before now. Are any -rt
> kernels being build regularly on master ?

I just checked with Beth and we are not. I will open a bug against the
autobuilder, we need to do this regularly.

--
Darren

> 
> It is partially due to meta-kernel-dev picking up new kernel tools that
> do strict checking on patches by default (hence my question about
> anyone else building this on master).
> 
> I'm pushing a fix out now to the meta branch and will send it along
> with my next consolidated pull request.
> 
> Cheers,
> 
> Bruce
> 
>>
>> |
>>
>> | ERROR. Could not find an excutable target for
>> yocto/standard/preempt-rt/base
>>
>> | ERROR. Could not locate meta series for preempt-rt-standard
>>
>> | ERROR. Could not modify yocto/standard/preempt-rt/base
>>
>> NOTE: package
>> linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1:
>> task do_patch: Failed
>>
>> NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded
>>
>> ERROR: Task 3
>> (/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
>> do_patch) failed with exit code '1'
>>
>> Is this anything to do with meta-kernel-dev I am using or something else?
>>
>> Thanks
>>
>> Kishore.
>>
> 


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Linux RT build fail

[Bodke, Kishore K]

Hi Bruce,

Could you please let me know if the fix is available for this?

Thanks
Kishore.

-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
Sent: Monday, January 16, 2012 10:44 AM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org; Hart, Darren
Subject: Re: Linux RT build fail

On 12-01-16 01:40 PM, Bodke, Kishore K wrote:
> Hi,
>
> I get build failure for the rt.
>
> ERROR: Function 'do_patch' failed (see
> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
> for further information)
>
> ERROR: Logfile of failure stored in:
> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
>
> Log data follows:
>
> | ERROR: Function 'do_patch' failed (see
> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
> for further information)
>
> | Deleted branch meta-temp (was 620917d).
>
> |
>
> | ERROR: patch
> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch
> is not available

This is the problem. But I could have sworn that I fixed this, and
send a merge request. When I just checked now, it still looks broken.

That being said, we should have seen this before now. Are any -rt
kernels being build regularly on master ?

It is partially due to meta-kernel-dev picking up new kernel tools that
do strict checking on patches by default (hence my question about
anyone else building this on master).

I'm pushing a fix out now to the meta branch and will send it along
with my next consolidated pull request.

Cheers,

Bruce

>
> |
>
> | ERROR. Could not find an excutable target for
> yocto/standard/preempt-rt/base
>
> | ERROR. Could not locate meta series for preempt-rt-standard
>
> | ERROR. Could not modify yocto/standard/preempt-rt/base
>
> NOTE: package
> linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1:
> task do_patch: Failed
>
> NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded
>
> ERROR: Task 3
> (/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
> do_patch) failed with exit code '1'
>
> Is this anything to do with meta-kernel-dev I am using or something else?
>
> Thanks
>
> Kishore.
>

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

Re: [yocto] Linux RT build fail

[Bodke, Kishore K]

I am building from master branch.

Below is the error I see.

ERROR: Function failed: do_patch (see 
/usr/local/src/juan/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+73dafd44ea875df654129b32b2877f342d5573e4_1+f1cc220f4ddf434bf254707c83a45794a63f117f-r1/temp/log.do_patch.25589
 for further information)
ERROR: Logfile of failure stored in: 
/usr/local/src/juan/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+73dafd44ea875df654129b32b2877f342d5573e4_1+f1cc220f4ddf434bf254707c83a45794a63f117f-r1/temp/log.do_patch.25589
Log data follows:
| ERROR: Function failed: do_patch (see 
/usr/local/src/juan/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+73dafd44ea875df654129b32b2877f342d5573e4_1+f1cc220f4ddf434bf254707c83a45794a63f117f-r1/temp/log.do_patch.25589
 for further information)
| checkpoint is already restored, nothing to do
| 
| ERROR: patch 
/usr/local/src/juan/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+73dafd44ea875df654129b32b2877f342d5573e4_1+f1cc220f4ddf434bf254707c83a45794a63f117f-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch
 is not available
| 
| ERROR. Could not find an excutable target for yocto/standard/preempt-rt/base
| ERROR. Could not locate meta series for preempt-rt-standard
| ERROR. Could not modify yocto/standard/
NOTE: package 
linux-yocto-rt-3.0.14+git1+73dafd44ea875df654129b32b2877f342d5573e4_1+f1cc220f4ddf434bf254707c83a45794a63f117f-r1:
 task do_patch: Failed
ERROR: Task 714 
(/usr/local/src/juan/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb, 
do_patch) failed with exit code '1'

Thanks
Kishore.

-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
Sent: Monday, January 23, 2012 10:06 AM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org; Hart, Darren
Subject: Re: Linux RT build fail

On 12-01-23 12:51 PM, Bodke, Kishore K wrote:
> Hi Bruce,
>
> Could you please let me know if the fix is available for this?

The 3.0 pull request was held up behind 3.2 work. But I just pushed
out a meta branch update that contained:

commit f1ef128bff854ce2614e655283ecca92d22f0b88
Author: Bruce Ashfield 
Date:   Mon Jan 16 13:45:11 2012 -0500

 meta/rt: fix reference to non-existent patch

 Signed-off-by: Bruce Ashfield 

:100644 100644 8c4d748... 4b9e9ed... M 
meta/cfg/kernel-cache/features/rt/rt.scc

Which is the error you are seeing. The change is destined
for master. If you are on another branch, it needs to be cherry
picked into your local meta branch.

Cheers,

Bruce

>
> Thanks
> Kishore.
>
> -Original Message-
> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
> Sent: Monday, January 16, 2012 10:44 AM
> To: Bodke, Kishore K
> Cc: yocto@yoctoproject.org; Hart, Darren
> Subject: Re: Linux RT build fail
>
> On 12-01-16 01:40 PM, Bodke, Kishore K wrote:
>> Hi,
>>
>> I get build failure for the rt.
>>
>> ERROR: Function 'do_patch' failed (see
>> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
>> for further information)
>>
>> ERROR: Logfile of failure stored in:
>> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
>>
>> Log data follows:
>>
>> | ERROR: Function 'do_patch' failed (see
>> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
>> for further information)
>>
>> | Deleted branch meta-temp (was 620917d).
>>
>> |
>>
>> | ERROR: patch
>> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch
>> is not available
>
> This is the problem. But I could have sworn that I fixed this, and
> send a merge request. When I just checked now, it still looks broken.
>
> That being said, we should have seen this before now. Are any -rt
> kernels being build regularly on master ?
>
> It is partially due to meta-kernel-dev picking up new kernel tools that
> do strict checking on patches by default (hence my question about
> anyone else building this on master).
>
> I'm pushing a fix out now to the meta branch and will send it along
> with my next consolidated pull request.
>
> Cheers,
>
&g

Re: [yocto] [KERNEL][PATCH 1/1] enable pvr features.

[Bodke, Kishore K]

Ok.  I sent a new pull request after removing the merge line.

Thanks
Kishore.

-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
Sent: Sunday, February 26, 2012 9:26 PM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: [KERNEL][PATCH 1/1] enable pvr features.

On 12-02-24 7:35 PM, kishore.k.bo...@intel.com wrote:
> From: Kishore Bodke
>
> Cedartrail has pvr kernel features and patches.
>
> Signed-off-by: Kishore Bodke
> ---
>   meta/cfg/kernel-cache/cfg/drm-cdvpvr.cfg |9 +
>   meta/cfg/kernel-cache/cfg/drm-cdvpvr.scc |2 ++
>   2 files changed, 11 insertions(+), 0 deletions(-)
>   create mode 100644 meta/cfg/kernel-cache/cfg/drm-cdvpvr.cfg
>   create mode 100644 meta/cfg/kernel-cache/cfg/drm-cdvpvr.scc
>
> diff --git a/meta/cfg/kernel-cache/cfg/drm-cdvpvr.cfg 
> b/meta/cfg/kernel-cache/cfg/drm-cdvpvr.cfg
> new file mode 100644
> index 000..0ab4488
> --- /dev/null
> +++ b/meta/cfg/kernel-cache/cfg/drm-cdvpvr.cfg
> @@ -0,0 +1,9 @@
> +CONFIG_HIGHMEM4G=y
> +CONFIG_STAGING=y
> +CONFIG_DRM=y
> +CONFIG_SND_HDA_CODEC_HDMI=y
> +CONFIG_DRM_INTEL_CDV=y
> +CONFIG_DRM_CDV_RELEASE=y
> +
> +# CONFIG_DRM_CDV_DEBUG is not set
> +# CONFIG_DRM_PVR_PDUMP is not se
> diff --git a/meta/cfg/kernel-cache/cfg/drm-cdvpvr.scc 
> b/meta/cfg/kernel-cache/cfg/drm-cdvpvr.scc
> new file mode 100644
> index 000..fbb8316
> --- /dev/null
> +++ b/meta/cfg/kernel-cache/cfg/drm-cdvpvr.scc
> @@ -0,0 +1,2 @@
> +kconf hardware drm-cdvpvr.cfg
> +git merge yocto/pvr

I was just completing the merge on this, and I realized that we
should put the branch merge in the BSP/machine, not in the generic
feature. The configs are good, but we want the cedartrail to do that
merge, not the config.

How does that sound to you ? If it is ok, spin me a patch with that
merge line removed and I'll push it out right away.

Cheers,

Bruce

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

Re: [yocto] [PATCH 0/1] [KERNEL] enable Cedarview config parameters

[Bodke, Kishore K]

Hi Bruce,

We got the patches from Cedartrail Meego team and applied to Yocto/pvr branch.  
Below is the link where we have taken the patches from.

http://build.meego.com/package/files?package=kernel-adaptation-pc&project=MeeGo%3A1.2.0%3ACedarTrail%3Aoss&rev=10

We have tested it on 3.0, but not yet tried on 3.2.

Thanks
Kishore.


-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
Sent: Thursday, March 01, 2012 1:00 PM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 0/1] [KERNEL] enable Cedarview config parameters

On 12-02-29 07:13 PM, kishore.k.bo...@intel.com wrote:
> From: Kishore Bodke
>
> Hi,
>
> This patch is to enable Cedarview config parameters and add the kernel 
> patches to the yocto/pvr branch in linux-yocto-3.0 and linux-yocto-3.2 tree.

The patch itself looks ok. When merging features like this, we
typically want the upstream reference. That makes carrying them
much easier as we march forward.

Where did these come from ? If we can get that in the header, that
would be great.

Often these patches can be broken up into subsystem chunks, but looking
through this, the breaks would largely be artificial (unless there's
an upstream repo we can leverage), so we can take a pass on breaking
these into smaller parts.

And you've tested the same content on 3.0 and 3.2 ?

Cheers,

Bruce

>
> Thanks
> Kishore.
>
>
> The following changes since commit 07e83cbd3e62a0bf91f558337aa7e37bc09f100b:
>
>Merge commit 'v3.0.22' into yocto/base (2012-02-26 00:02:48 -0500)
>
> are available in the git repository at:
>
>git://git.pokylinux.org/linux-yocto-2.6.37-contrib kishore/pvr-patch
>
> http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=kishore/pvr-patch
>
> Kishore Bodke (1):
>enable Cedarview config parameters.
>
>   drivers/staging/Kconfig|2 +
>   drivers/staging/Makefile   |1 +
>   drivers/staging/cdv/Kconfig|   50 +
>   drivers/staging/cdv/Makefile   |  198 +
>   drivers/staging/cdv/bc_video/bufferclass_video.c   |  327 ++
>   drivers/staging/cdv/bc_video/bufferclass_video.h   |  171 +
>   .../staging/cdv/bc_video/bufferclass_video_linux.c |  838 
>   .../staging/cdv/bc_video/bufferclass_video_linux.h |   67 +
>   drivers/staging/cdv/drv/psb_bl.c   |  135 +
>   drivers/staging/cdv/drv/psb_dpst.c |  283 ++
>   drivers/staging/cdv/drv/psb_dpst.h |   98 +
>   drivers/staging/cdv/drv/psb_drm.h  |  562 +++
>   drivers/staging/cdv/drv/psb_drv.c  | 1881 
>   drivers/staging/cdv/drv/psb_drv.h  | 1203 +
>   drivers/staging/cdv/drv/psb_fb.c   |  812 
>   drivers/staging/cdv/drv/psb_fb.h   |   59 +
>   drivers/staging/cdv/drv/psb_gtt.c  | 1045 +
>   drivers/staging/cdv/drv/psb_gtt.h  |  112 +
>   drivers/staging/cdv/drv/psb_hotplug.c  |  439 ++
>   drivers/staging/cdv/drv/psb_hotplug.h  |   90 +
>   drivers/staging/cdv/drv/psb_intel_bios.c   |  289 ++
>   drivers/staging/cdv/drv/psb_intel_bios.h   |  470 ++
>   drivers/staging/cdv/drv/psb_intel_crt.c|  353 ++
>   drivers/staging/cdv/drv/psb_intel_display.c| 1675 +++
>   drivers/staging/cdv/drv/psb_intel_display.h|   25 +
>   drivers/staging/cdv/drv/psb_intel_dpll_cdv.c   |  262 ++
>   drivers/staging/cdv/drv/psb_intel_drv.h|  252 +
>   drivers/staging/cdv/drv/psb_intel_hdmi.c   |  684 +++
>   drivers/staging/cdv/drv/psb_intel_hdmi.h   |  935 
>   drivers/staging/cdv/drv/psb_intel_hdmi_edid.h  | 1057 +
>   drivers/staging/cdv/drv/psb_intel_hdmi_reg.h   |  130 +
>   drivers/staging/cdv/drv/psb_intel_i2c.c|  171 +
>   drivers/staging/cdv/drv/psb_intel_lvds.c   |  701 +++
>   drivers/staging/cdv/drv/psb_intel_modes.c  |   77 +
>   drivers/staging/cdv/drv/psb_intel_opregion.c   |  340 ++
>   drivers/staging/cdv/drv/psb_intel_reg.h| 1461 ++
>   drivers/staging/cdv/drv/psb_irq.c  |  681 +++
>   drivers/staging/cdv/drv/psb_irq.h  |   49 +
>   drivers/staging/cdv/drv/psb_powermgmt.c|  875 
>   drivers/staging/cdv/drv/psb_powermgmt.h|   98 +
>   drivers/staging/cdv/drv/psb_pvr_glue.c |   74 +
>   drivers/staging/cdv/drv/psb_pvr_glue.h |   26 +
>   drivers/staging/cdv/drv/psb_reg.h  |  596 +++
>   drivers/staging/cdv/drv/psb_reset.c|  144 +
>   drivers/staging/cdv/drv/psb_schedule.c 

[yocto] mesa 7.9.1 version fails for master branch

[Bodke, Kishore K]

Hi,

I have mesa 7.9.1 overriding in my machine.conf with PREFERRED_VERSION_mesa-dri 
?= "7.9.1"
And  building with poky/master and meta-intel/master, however the mesa recipe 
build fails while applying the patches.

Below is the details of the error.

mesa/mesa-dri_7.9.1.bb, do_patch)
NOTE: package mesa-dri-2_7.9.1-r2: task do_patch: Started
ERROR: Command Error: exit status: 1  Output:
Applying patch crossfix.patch
can't find file to patch at input line 7
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|Upstream-Status: Pending
|
|Index: Mesa-7.5/bin/mklib
|===
|--- Mesa-7.5.orig/bin/mklib2009-08-12 13:01:34.0 +0100
|+++ Mesa-7.5/bin/mklib2009-08-12 13:04:19.0 +0100
--
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
Patch crossfix.patch does not apply (enforce with -f)
ERROR: Function failed: patch_do_patch


Could any one point what went wrong here?  Do we need a different patches for 
7.9.1 version?

The same mesa 7.9.1 recipe works fine with Edison branch.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [KERNEL][PATCH 0/1] meta: Create scc file for pvr merge

[Bodke, Kishore K]

Yes, Please go ahead and merge this to 3.0 kernel.  
We will be releasing the Cedartrail BSP both for Edison and master branch in 
another couple of weeks.

Thanks
Kishore.

-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] 
Sent: Tuesday, March 13, 2012 9:04 PM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org
Subject: Re: [KERNEL][PATCH 0/1] meta: Create scc file for pvr merge

On 12-03-13 2:12 PM, kishore.k.bo...@intel.com wrote:
> From: Kishore Bodke
>
> Hi,
>
> This patch is to create a new scc file for merging the yocto/pvr branch for 
> the targets
> with the appropriate hardware support.

Just so I'm clear, there are no current users of this in the tree, but
we want to stage this for future work, or work that isn't ready yet ?

I'll merge this into the 3.0 kernel and await your confirmation.

Cheers,

Bruce

>
> Adding it into the existing cedartrail.scc, the non-pvr build was not 
> booting. So we had to separate it out.
>
> Thanks
> Kishore.
>
>
> The following changes since commit e559129b4a6f39f68b75141096b2d516cf7a7f35:
>
>fri2: Add SMP and EFI support (2012-03-02 16:02:35 -0500)
>
> are available in the git repository at:
>git://git.pokylinux.org/linux-yocto-2.6.37-contrib 
> kishore/meta-cedartrail/pvr-merge
>
> http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-contrib/log/?h=kishore/meta-cedartrail/pvr-merge
>
> Kishore Bodke (1):
>meta: Create scc file for pvr merge
>
>   .../bsp/cedartrail/cedartrail-pvr-merge.scc|1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
>   create mode 100644 
> meta/cfg/kernel-cache/bsp/cedartrail/cedartrail-pvr-merge.scc
>

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

Re: [yocto] [PATCH 1/1] [meta-intel] Romley: Add new bbappend file for 3.2 kernel

[Bodke, Kishore K]

Hi Darren,

Answers embedded.

-Original Message-
From: Hart, Darren 
Sent: Thursday, April 05, 2012 4:21 PM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org; Zanussi, Tom
Subject: Re: [yocto] [PATCH 1/1] [meta-intel] Romley: Add new bbappend file for 
3.2 kernel

On 04/04/2012 03:33 PM, kishore.k.bo...@intel.com wrote:
> From: Kishore Bodke 
> 
> Switching Romley to 3.2 kernel.
> 

Hi Kishore,

A couple questions for you.

1) This is boot tested I presume?
[KISHORE]:  Yes. Booted, and ran basic test cases as well.
2) Do you intend to leave the 3.0 recipes in place?
   It's fine if you do, I just wanted to know.
[KISHORE]: I would like to follow with other meta-intel BSPs.

3) Do you have any patches in the common-pc-64/romley branch?
   If so, these are not being used when building -rt.
[KISHORE]: No patches.

Thanks
Kishore.
--
Darren

> Signed-off-by: Kishore Bodke 
> ---
>  meta-romley/conf/machine/romley.conf   |3 +++
>  .../linux/linux-yocto-rt_3.2.bbappend  |8 
>  .../recipes-kernel/linux/linux-yocto_3.2.bbappend  |9 +
>  3 files changed, 20 insertions(+), 0 deletions(-)
>  create mode 100644 
> meta-romley/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
>  create mode 100644 meta-romley/recipes-kernel/linux/linux-yocto_3.2.bbappend
> 
> diff --git a/meta-romley/conf/machine/romley.conf 
> b/meta-romley/conf/machine/romley.conf
> index aa334c0..e6a755b 100644
> --- a/meta-romley/conf/machine/romley.conf
> +++ b/meta-romley/conf/machine/romley.conf
> @@ -4,6 +4,9 @@
>  #@DESCRIPTION: Machine configuration for Romley systems
>  # i.e. Sandy Bridge + Patsburg Chipset
>  
> +
> +PREFERRED_VERSION_linux-yocto ?= "3.2%"
> +
>  require conf/machine/include/tune-x86_64.inc
>  require conf/machine/include/ia32-base.inc
>  
> diff --git a/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend 
> b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
> new file mode 100644
> index 000..7a61749
> --- /dev/null
> +++ b/meta-romley/recipes-kernel/linux/linux-yocto-rt_3.2.bbappend
> @@ -0,0 +1,8 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +COMPATIBLE_MACHINE_romley = "romley"
> +KMACHINE_romley  = "romley"
> +
> +# Update the following to use a different BSP branch or meta SRCREV
> +#KBRANCH_romley  = "standard/preempt-rt/base"
> +#SRCREV_machine_pn-linux-yocto-rt_romley ?= 
> +#SRCREV_meta_pn-linux-yocto-rt_romley ?= 
> diff --git a/meta-romley/recipes-kernel/linux/linux-yocto_3.2.bbappend 
> b/meta-romley/recipes-kernel/linux/linux-yocto_3.2.bbappend
> new file mode 100644
> index 000..803e772
> --- /dev/null
> +++ b/meta-romley/recipes-kernel/linux/linux-yocto_3.2.bbappend
> @@ -0,0 +1,9 @@
> +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> +
> +COMPATIBLE_MACHINE_romley = "romley"
> +
> +KMACHINE_romley  = "romley"
> +KBRANCH_romley  = "standard/default/common-pc-64/romley"
> +
> +SRCREV_machine_pn-linux-yocto_romley ?= 
> "5c7f1c53b5b367858ae6a86c1d4de36d8c71bedb"
> +SRCREV_meta_pn-linux-yocto_romley ?= 
> "59f350ec3794e19fa806c1b73749d851f8ebf364"


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/7] [meta-intel] Cedartrail BSP updates with pvr Graphics driver

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, April 09, 2012 10:47 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: [PATCH 0/7] [meta-intel] Cedartrail BSP updates with pvr
>Graphics driver
>
>
>On Tue, 2012-04-03 at 16:43 -0700, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke 
>>
>> These patches are for adding the PVR graphics driver, EFI Support,
>> and to add Cedartrail Audio and Video files .
>>
>> These also updates the SRCREVS for build with pvr and no-pvr versions.
>>
>> Please pull into meta-intel/master.
>>
>
>Hi Kishore,
>
>Sorry this has been delayed, just getting back to things now after being
>out last week for conferences.
>
>In general, thanks for breaking things up more this time, but there are
>still a couple things I think should be done, which I'll comment on in
>those patches.
>
>Also, I don't think it makes sense to pull in the audio recipe since
>that has changed between edison and master - I think the way to do the
>same thing you're doing there is using asound.state (see
>meta-intel/meta-n450/recipes-bsp/alsa-state/alsa-state/n450/asound.state
>as an example).

I will change this audio recipe as per the new changes in the master.

>
>Also, I'm wondering if it makes sense to have the image bbappends rather
>than just differently-named image recipes - otherwise, you can't build a
>regular sato image for example without also including all the test
>files.

We put these in image bbappends because we wanted a regular sato image has 
all the needed files builtin by default. 

>
>Finally, as a new BSP in master, I think there should also be support
>for the 3.2 kernel, or is there some reason you couldn't do that?

Pvr patches have not yet got into 3.2 kernel, as this has not been tested for 
3.2.
So, currently we are supporting 3.0 kernel only. 
For the current release we are only targeting 3.0 kernel.
With 3.2 kernel we are planning to add couple of new features added.

Thanks
Kishore.

>
>Thanks,
>
>Tom
>
>> Thanks
>> Kishore.
>>
>> The following changes since commit
>f89405e115d73426c8a6450b6e795b5885d6bdf3:
>>
>>   MAINTAINERS: Add FRI2 maintainer (2012-03-23 09:46:15 -0700)
>>
>> are available in the git repository at:
>>   git://git.pokylinux.org/meta-intel-contrib kishore/cedartrail-pvr-
>updates
>>   http://git.pokylinux.org/cgit.cgi/meta-intel-
>contrib/log/?h=kishore/cedartrail-pvr-updates
>>
>> Kishore Bodke (7):
>>   Cedartrail: Add PVR graphics support.
>>   Cedartrail: Update SRCREVS and add EFI Support.
>>   Cedartrail: Add new recipes for audio and video samples.
>>   Cedartrail: Add bbappend files to install Audio and Video files.
>>   Cedartrail: Separte out machine.conf files.
>>   Cedartrail: Add a new recipe for Audio.
>>   Cedartrail: Update the README.
>>
>>  conf/machine/include/ia32-base.inc |2 +
>>  meta-cedartrail/README |   41 -
>>  meta-cedartrail/conf/machine/cedartrail-nopvr.conf |   21 
>>  meta-cedartrail/conf/machine/cedartrail.conf   |   13 ++-
>>  .../cedartrail-audio/cedartrail-audio.bb   |   30 ++
>>  .../cedartrail-audio/cedartrail-audio  |   42 
>>  .../formfactor/cedartrail-nopvr/machconfig |3 +
>>  .../tasks/task-core-tools-profile.bbappend |2 +-
>>  .../xorg-driver/cdv-pvr-driver.inc |   39 
>>  .../xorg-driver/cdv-pvr-driver_1.0.bb  |  101
>
>>  .../xserver-xf86-config/cedartrail-nopvr/xorg.conf |   26 +
>>  .../xserver-xf86-config/cedartrail/xorg.conf   |   24 ++---
>>  .../linux/linux-yocto-rt_3.0.bbappend  |8 ++
>>  .../recipes-kernel/linux/linux-yocto_3.0.bbappend  |   16 +++-
>>  .../ogg-CC-BY-3.0-music-samples_0.1.bb |   23 +
>>  .../video-samples/bigbuckbunny-ogg.bb  |   24 +
>>  .../images/core-image-sato-dev.bbappend|2 +
>>  .../images/core-image-sato-sdk.bbappend|2 +
>>  .../recipes-sato/images/core-image-sato.bbappend   |1 +
>>  19 files changed, 396 insertions(+), 24 deletions(-)
>>  create mode 100644 meta-cedartrail/conf/machine/cedartrail-nopvr.conf
>>  create mode 100644 meta-cedartrail/recipes-bsp/cedartrail-
>audio/cedartrail-audio.bb
>>  create mode 100644 meta-cedartrail/recipes-bsp/cedartrail-
>audio/cedartrail-audio/cedartrail-audio
>>  create mode 100644 meta-cedartrail/recipes-
>bsp/formfactor/formfactor/cedartrail-nopvr/machconfig
&g

Re: [yocto] [PATCH 1/7] Cedartrail: Add PVR graphics support.

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, April 09, 2012 10:56 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: [PATCH 1/7] Cedartrail: Add PVR graphics support.
>
>Hi Kishore,
>
>Comments below...
>
>On Tue, 2012-04-03 at 16:43 -0700, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke 
>>
>> Adding PVR Graphics support and separate out
>> xorg.conf for building both with pvr and no-pvr.
>>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  conf/machine/include/ia32-base.inc |2 +
>>  .../xorg-driver/cdv-pvr-driver.inc |   39 
>>  .../xorg-driver/cdv-pvr-driver_1.0.bb  |  101
>
>>  .../xserver-xf86-config/cedartrail-nopvr/xorg.conf |   26 +
>>  .../xserver-xf86-config/cedartrail/xorg.conf   |   24 ++---
>>  5 files changed, 176 insertions(+), 16 deletions(-)
>>  create mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-
>pvr-driver.inc
>>  create mode 100644 meta-cedartrail/recipes-graphics/xorg-driver/cdv-
>pvr-driver_1.0.bb
>>  create mode 100644 meta-cedartrail/recipes-graphics/xorg-
>xserver/xserver-xf86-config/cedartrail-nopvr/xorg.conf
>>
>> diff --git a/conf/machine/include/ia32-base.inc
>b/conf/machine/include/ia32-base.inc
>> index 9b2ef5a..d1bd0d7 100644
>> --- a/conf/machine/include/ia32-base.inc
>> +++ b/conf/machine/include/ia32-base.inc
>> @@ -64,3 +64,5 @@ XSERVER_IA32_EMGD = "emgd-driver-bin \
>> "
>>
>>  XSERVER_IA32_VESA = "xf86-video-vesa"
>> +
>> +XSERVER_IA32_PVR = "cdv-pvr-driver"
>
>Since this is modifying a common file, can you please add this as a
>separate commit?
>
>Also, since you're adding this to common code, it won't work for any
>other BSP since the recipe is in meta-cedartrail only.  Is this meant to
>be usable by other BSPs, maybe in the near future?  If so, you should
>move this to common/ to match the above definition, otherwise, just keep
>it all local to your BSP.

At this point, only Cedartrail uses this.  So, I think it is better make 
this local to BSP.  
I will change this.

>
>Also, either way, since the cdv-pvr-driver is a new recipe, please keep
>that as a separate commit as well.

I will make this as a separate commit.

Thanks
Kishore.

>
>> diff --git a/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-
>driver.inc b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-
>driver.inc
>> new file mode 100644
>> index 000..0de6cbe
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver.inc
>> @@ -0,0 +1,39 @@
>> +SUMMARY = "Cedartrail PowerVR Graphics Driver version [Gold] 1.0
>binaries"
>> +DESCRIPTION = "2D, 3D and Media user space driver for Cedartrail
>platform \
>> +The binaries are covered by the Intel Free Distribution Binary
>License. \
>> +The user must make himself/herself aware of the Licensing terms \
>> +before enabling build of the Cedartrail PowerVR Graphics Driver via \
>> +this recipe.  Please see the README in meta-cedartrail for
>instructions \
>> +for enabling the build of the driver "
>> +
>> +MEEGO_MIRROR =
>"http://download.meego.com/live/MeeGo:/1.2.0:/CedarTrail:";
>> +
>> +LICENSE_FLAGS = "license_${PN}_${PV}"
>> +LICENSE = "Intel Free Distribution Binary License"
>> +LIC_FILES_CHKSUM = " \
>> +file://${S}/usr/share/doc/psb-video-cdv-
>0.12/license.txt;md5=b14d99f8d4ed664e9ce95057f0bb5b65  \
>> +file://${S}/usr/share/doc/pvr-bin-cdv-
>1.7.788837_05/license.txt;md5=b14d99f8d4ed664e9ce95057f0bb5b65"
>> +
>> +
>> +INC_PR = "r0"
>> +
>> +DEPENDS = "rpm-native"
>> +
>> +FILES_${PN} += "${libdir}/dri ${libdir}/pvr/cdv/dri ${libdir}/pvr/cdv
>${libdir}/xorg/modules/drivers"
>> +FILES_${PN}-dev += "${libdir}/dri ${libdir}/pvr/cdv/dri
>${libdir}/xorg/modules/drivers"
>> +FILES_${PN}-dbg += "${libdir}/xorg/modules/drivers/.debug
>${libdir}/dri/.debug ${libdir}/pvr/cdv/dri/.debug"
>> +
>> +FILES_${PN} += "${base_libdir}/firmware"
>> +FILES_${PN} += "${sysconfdir}/X11/xorg.conf.d"
>> +
>> +FILES_${PN} += "${libdir}/lib*.so"
>> +FILES_${PN}-dev += "${libdir}/lib*.so"
>> +FILES_${PN}-dbg += "${libdir}/.debug"
>> +
>> +FILES_${PN} += "${libdir}/pvr/cdv/xorg/modules/drivers"
>> +
>> +FILES_${PN} += "${datadir}/doc/psb-video-cdv-0.12

Re: [yocto] [PATCH 3/7] Cedartrail: Add new recipes for audio and video samples.

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, April 09, 2012 10:57 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: [PATCH 3/7] Cedartrail: Add new recipes for audio and video
>samples.
>
>On Tue, 2012-04-03 at 16:43 -0700, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke 
>>
>> This recipe adds sample Audio files and Video files
>> for testing with pvr Acceleration driver.
>>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  .../ogg-CC-BY-3.0-music-samples_0.1.bb |   23
>+++
>>  .../video-samples/bigbuckbunny-ogg.bb  |   24
>
>>  2 files changed, 47 insertions(+), 0 deletions(-)
>>  create mode 100644 meta-cedartrail/recipes-mediasamples/music-
>samples/ogg-CC-BY-3.0-music-samples_0.1.bb
>>  create mode 100644 meta-cedartrail/recipes-mediasamples/video-
>samples/bigbuckbunny-ogg.bb
>>
>> diff --git a/meta-cedartrail/recipes-mediasamples/music-samples/ogg-
>CC-BY-3.0-music-samples_0.1.bb b/meta-cedartrail/recipes-
>mediasamples/music-samples/ogg-CC-BY-3.0-music-samples_0.1.bb
>> new file mode 100644
>> index 000..fd65cc7
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-mediasamples/music-samples/ogg-CC-BY-
>3.0-music-samples_0.1.bb
>> @@ -0,0 +1,23 @@
>> +SUMMARY = "ogg file format music samples"
>> +DESCRIPTION = "Installs ogg file format music samples in /home/Music
>dir"
>> +
>> +LICENSE = "CC-BY-3.0"
>> +LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/CC-BY-
>3.0;md5=dfa02b5755629022e267f10b9c0a2ab7"
>> +
>> +DEPENDS += " "
>> +
>
>Does this empty DEPENDS do anything?  Same thing in a couple other
>places...

It does nothing. I might have forgotten this to remove.

Thanks
Kishore.

>
>Tom
>
>
>> +PR = "r0"
>> +
>> +SRC_URI =
>"http://downloads.yoctoproject.org/releases/media/music/ogg-CC-BY-3.0-
>music-samples-${PV}.tar.bz2 \
>> +"
>> +
>> +SRC_URI[md5sum] = "dc3dd4adca69996edaffe8828e1ee165"
>> +SRC_URI[sha256sum] =
>"86381f8474d5ac2c80f54c951a8c22f67d352daa977341d3dfb4161e39ca3975"
>> +
>> +do_install() {
>> +
>> +install -d ${D}${base_prefix}/home/music
>> +install -m 0644  ${WORKDIR}/ogg-CC-BY-3.0-music-samples-${PV}/*/*.ogg
>${D}${base_prefix}/home/music
>> +}
>> +
>> +FILES_${PN} += "${base_prefix}/home/music/*.ogg"
>> diff --git a/meta-cedartrail/recipes-mediasamples/video-
>samples/bigbuckbunny-ogg.bb b/meta-cedartrail/recipes-
>mediasamples/video-samples/bigbuckbunny-ogg.bb
>> new file mode 100644
>> index 000..036721c
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-mediasamples/video-samples/bigbuckbunny-
>ogg.bb
>> @@ -0,0 +1,24 @@
>> +SUMMARY = "Big Buck Bunny video OGG sample "
>> +DESCRIPTION = "Installs Big Buck Bunny Video OGG file samples in
>/home/video dir "
>> +
>> +LICENSE = "CC-BY-3.0"
>> +LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/CC-BY-
>3.0;md5=dfa02b5755629022e267f10b9c0a2ab7"
>> +
>> +DEPENDS += " "
>> +
>> +PR = "r0"
>> +
>> +SRC_URI = "http://blender-
>mirror.kino3d.org/peach/bigbuckbunny_movies/big_buck_bunny_720p_stereo.o
>gg \
>> +"
>> +
>> +
>> +SRC_URI[md5sum] = "576424c653da53e31b86c027e55758ae"
>> +SRC_URI[sha256sum] =
>"785b09a585be55f81326a3fcef2cdeeb7ebbc33932b6305fd84209928df67f28"
>> +
>> +do_install() {
>> +
>> +install -d ${D}${base_prefix}/home/Videos
>> +install -m 0644  ${WORKDIR}/*.ogg ${D}${base_prefix}/home/Videos
>> +}
>> +
>> +FILES_${PN} += "${base_prefix}/home/Videos/*.ogg"
>

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

Re: [yocto] [PATCH 4/7] Cedartrail: Add bbappend files to install Audio and Video files.

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, April 09, 2012 11:01 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: [PATCH 4/7] Cedartrail: Add bbappend files to install Audio
>and Video files.
>
>On Tue, 2012-04-03 at 16:43 -0700, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke 
>>
>> These bbappend files pulls in the Audio, Video and Web Kit
>> into the Image with IMAGE_INSTALL.
>>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  .../images/core-image-sato-dev.bbappend|2 ++
>>  .../images/core-image-sato-sdk.bbappend|2 ++
>>  .../recipes-sato/images/core-image-sato.bbappend   |1 +
>>  3 files changed, 5 insertions(+), 0 deletions(-)
>>  create mode 100644 meta-cedartrail/recipes-sato/images/core-image-
>sato-dev.bbappend
>>  create mode 100644 meta-cedartrail/recipes-sato/images/core-image-
>sato-sdk.bbappend
>>  create mode 100644 meta-cedartrail/recipes-sato/images/core-image-
>sato.bbappend
>>
>> diff --git a/meta-cedartrail/recipes-sato/images/core-image-sato-
>dev.bbappend b/meta-cedartrail/recipes-sato/images/core-image-sato-
>dev.bbappend
>> new file mode 100644
>> index 000..33283f4
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-sato/images/core-image-sato-dev.bbappend
>> @@ -0,0 +1,2 @@
>> +IMAGE_INSTALL += "web-webkit bigbuckbunny-ogg ogg-CC-BY-3.0-music-
>samples"
>> +
>> diff --git a/meta-cedartrail/recipes-sato/images/core-image-sato-
>sdk.bbappend b/meta-cedartrail/recipes-sato/images/core-image-sato-
>sdk.bbappend
>> new file mode 100644
>> index 000..33283f4
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-sato/images/core-image-sato-sdk.bbappend
>> @@ -0,0 +1,2 @@
>> +IMAGE_INSTALL += "web-webkit bigbuckbunny-ogg ogg-CC-BY-3.0-music-
>samples"
>> +
>> diff --git a/meta-cedartrail/recipes-sato/images/core-image-
>sato.bbappend b/meta-cedartrail/recipes-sato/images/core-image-
>sato.bbappend
>> new file mode 100644
>> index 000..4c1ccac
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-sato/images/core-image-sato.bbappend
>> @@ -0,0 +1 @@
>> +IMAGE_INSTALL += "web-webkit bigbuckbunny-ogg  ogg-CC-BY-3.0-music-
>samples"
>
>These will always add the media files etc whenever anyone builds any of
>these.  Is that really what you want?

Yes. By default we wanted to have all these included when customer builds
a regular sato image.
So, I think it would be good if it remains unchanged.

Thanks
Kishore.

>
>Maybe creating separate test image recipes that do this would be more
>along the lines of what you wanted...
>
>Tom

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

Re: [yocto] [PATCH 6/7] Cedartrail: Add a new recipe for Audio.

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, April 09, 2012 11:04 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: [PATCH 6/7] Cedartrail: Add a new recipe for Audio.
>
>On Tue, 2012-04-03 at 16:43 -0700, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke 
>>
>> Adding a new recipe for including a Audio
>> feature for the cedartrail bsp.
>>
>
>As mentioned, I think the new way to do this is using asound.state (see
>meta-intel/meta-n450/recipes-bsp/alsa-state/alsa-state/n450/asound.state
>as an example).

I will modify this recipe as per the new changes in the master.

Thanks
Kishore.

>
>Tom
>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  .../cedartrail-audio/cedartrail-audio.bb   |   30
>++
>>  .../cedartrail-audio/cedartrail-audio  |   42
>
>>  2 files changed, 72 insertions(+), 0 deletions(-)
>>  create mode 100644 meta-cedartrail/recipes-bsp/cedartrail-
>audio/cedartrail-audio.bb
>>  create mode 100644 meta-cedartrail/recipes-bsp/cedartrail-
>audio/cedartrail-audio/cedartrail-audio
>>
>> diff --git a/meta-cedartrail/recipes-bsp/cedartrail-audio/cedartrail-
>audio.bb b/meta-cedartrail/recipes-bsp/cedartrail-audio/cedartrail-
>audio.bb
>> new file mode 100644
>> index 000..9a43f02
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-bsp/cedartrail-audio/cedartrail-audio.bb
>> @@ -0,0 +1,30 @@
>> +SUMMARY = "Provide a basic init script to enable audio"
>> +DESCRIPTION = "Set the volume and unmute the Front mixer setting
>during boot."
>> +SECTION = "base"
>> +LICENSE = "MIT"
>> +LIC_FILES_CHKSUM =
>"file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58"
>> +
>> +PR = "r0"
>> +
>> +inherit update-rc.d
>> +
>> +RDEPENDS = "alsa-utils-amixer"
>> +
>> +SRC_URI = "file://cedartrail-audio"
>> +
>> +INITSCRIPT_NAME = "cedartrail-audio"
>> +INITSCRIPT_PARAMS = "defaults 90"
>> +
>> +do_install() {
>> +install -d ${D}${sysconfdir} \
>> +   ${D}${sysconfdir}/init.d
>> +install -m 0755 ${WORKDIR}/cedartrail-audio
>${D}${sysconfdir}/init.d
>> +cat ${WORKDIR}/${INITSCRIPT_NAME} | \
>> +sed -e 's,/etc,${sysconfdir},g' \
>> +-e 's,/usr/sbin,${sbindir},g' \
>> +-e 's,/var,${localstatedir},g' \
>> +-e 's,/usr/bin,${bindir},g' \
>> +-e 's,/usr,${prefix},g' >
>${D}${sysconfdir}/init.d/${INITSCRIPT_NAME}
>> +chmod 755 ${D}${sysconfdir}/init.d/${INITSCRIPT_NAME}
>> +}
>> +
>> diff --git a/meta-cedartrail/recipes-bsp/cedartrail-audio/cedartrail-
>audio/cedartrail-audio b/meta-cedartrail/recipes-bsp/cedartrail-
>audio/cedartrail-audio/cedartrail-audio
>> new file mode 100644
>> index 000..efd08d3
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-bsp/cedartrail-audio/cedartrail-
>audio/cedartrail-audio
>> @@ -0,0 +1,42 @@
>> +#!/bin/sh
>> +### BEGIN INIT INFO
>> +# Provides:  cedartrail mixer setup
>> +# Required-Start:$syslog
>> +# Required-Stop: $syslog
>> +# Default-Start: 2 3 4 5
>> +# Default-Stop:  0 1 6
>> +# Short-Description: Initialize the cedartrail audio mixer
>> +# Description:   Unmute FRONT and set volume
>> +### END INIT INFO
>> +
>> +# Author: Darren Hart 
>> +# Based on /etc/init.d/skeleton
>> +
>> +PATH=/sbin:/usr/sbin:/bin:/usr/bin
>> +DESC="Audio mixer settings"
>> +NAME=cedartrail-audio
>> +AMIXER=`which amixer`
>> +SCRIPTNAME=/etc/init.d/$NAME
>> +
>> +# Exit if amixer is not installed
>> +[ -x "$AMIXER" ] || exit 0
>> +
>> +do_start() {
>> +# Enable the "Front" simple controls (black phones jack)
>> +$AMIXER sset Front 90 on > /dev/null
>> +}
>> +
>> +case "$1" in
>> +start)
>> +echo "$NAME: setting default mixer settings."
>> +do_start
>> +;;
>> +stop)
>> +;;
>> +*)
>> +echo "Usage: $SCRIPTNAME {start|stop}" >&2
>> +exit 3
>> +;;
>> +esac
>> +
>> +exit 0
>

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

Re: [yocto] [PATCH 7/7] Cedartrail: Update the README.

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, April 09, 2012 11:07 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: [PATCH 7/7] Cedartrail: Update the README.
>
>On Tue, 2012-04-03 at 16:43 -0700, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke 
>>
>> Update the README file with instructions to build
>> with pvr graphics driver.
>>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  meta-cedartrail/README |   41
>+++--
>>  1 files changed, 39 insertions(+), 2 deletions(-)
>>
>> diff --git a/meta-cedartrail/README b/meta-cedartrail/README
>> index 295e9ff..f482cca 100755
>> --- a/meta-cedartrail/README
>> +++ b/meta-cedartrail/README
>> @@ -52,10 +52,23 @@ common metadata shared between BSPs) e.g.:
>>  yocto/meta-intel \
>>  yocto/meta-intel/meta-cedartrail \
>>
>> -To enable the cedartrail layer, add the cedartrail MACHINE to
>local.conf:
>> +To enable the cedartrail layer that supports Power VR graphics,
>> +add the cedartrail MACHINE to local.conf:
>>
>>MACHINE ?= "cedartrail"
>>
>> +
>> +Power VR Graphics user-space driver binaries are covered by a
>> +"Intel Free Distribution Binary License". The build of this driver
>> +can be enabled by adding the following line to the local.conf file:
>> +
>> +LICENSE_FLAGS_WHITELIST += "license_cdv-pvr-driver_1.0"
>> +
>> +To enable the layer that does not support Power VR graphics
>> +add the following to the local.conf file:
>> +
>> + MACHINE ?= "cedartrail-nopvr"
>> +
>>  You should then be able to build a cedartrail image as such:
>>
>>$ source oe-init-build-env
>> @@ -85,7 +98,7 @@ Under Linux, insert a USB flash drive.  Assuming the
>USB flash drive
>>  takes device /dev/sdf, use dd to copy the live image to it.  For
>>  example:
>>
>> -# dd if=core-image-sato-cedartrail-20120105232035.hddimg of=/dev/sdf
>> +# dd if=core-image-sato-cedartrail-20120403210525.hddimg of=/dev/sdf
>>  # sync
>>  # eject /dev/sdf
>>
>> @@ -109,3 +122,27 @@ the syslinux boot: prompt, or the boot: prompt
>contains strange
>>  characters), try doing this first:
>>
>>  # dd if=/dev/zero of=/dev/sdf bs=1M count=512
>> +
>> +Miscellaneous Notes
>> +
>> +
>> +Video and Music Samples
>> +---
>> +This BSP includes recipes to download Ogg format video and
>> +music files that can be played-back with the Video and music players
>> +included in the sato images.  The sample files are installed in
>> +/home/Music and /home/Videos directories.
>> +
>> +
>> +Adding Glxgears to image
>> +-
>> +Glxgears can be added to the generated image by adding "debug-tweaks"
>> +option to the extra image features variable in the default local.conf
>> +before building the BSP.
>
>I think the thing that adds glxgears is tools-testapps and not
>debug-tweaks.  You have tools-testapps below which is probably why it
>works, but you might want to verify that and change the README text if
>so.

Yeah, you are right.  I copied from Edison branch.

Rahul, could you also change this README in the Edison branch.

Thanks
Kishore.

>
>Tom
>
>> +
>> +e.g. to add Glxgears, locate the following line in local.conf
>> +EXTRA_IMAGE_FEATURES = "debug-tweaks"
>> +
>> +and change above line to..
>> +
>> +EXTRA_IMAGE_FEATURES = "debug-tweaks tools-testapps"
>

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

Re: [yocto] [PATCH 4/7] Cedartrail: Add bbappend files to install Audio and Video files.

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, April 09, 2012 11:42 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: RE: [PATCH 4/7] Cedartrail: Add bbappend files to install Audio
>and Video files.
>
>On Mon, 2012-04-09 at 11:29 -0700, Bodke, Kishore K wrote:
>>
>> >-Original Message-
>> >From: Zanussi, Tom
>> >Sent: Monday, April 09, 2012 11:01 AM
>> >To: Bodke, Kishore K
>> >Cc: yocto@yoctoproject.org
>> >Subject: Re: [PATCH 4/7] Cedartrail: Add bbappend files to install
>Audio
>> >and Video files.
>> >
>> >On Tue, 2012-04-03 at 16:43 -0700, kishore.k.bo...@intel.com wrote:
>> >> From: Kishore Bodke 
>> >>
>> >> These bbappend files pulls in the Audio, Video and Web Kit
>> >> into the Image with IMAGE_INSTALL.
>> >>
>> >> Signed-off-by: Kishore Bodke 
>> >> ---
>> >>  .../images/core-image-sato-dev.bbappend|2 ++
>> >>  .../images/core-image-sato-sdk.bbappend|2 ++
>> >>  .../recipes-sato/images/core-image-sato.bbappend   |1 +
>> >>  3 files changed, 5 insertions(+), 0 deletions(-)
>> >>  create mode 100644 meta-cedartrail/recipes-sato/images/core-image-
>> >sato-dev.bbappend
>> >>  create mode 100644 meta-cedartrail/recipes-sato/images/core-image-
>> >sato-sdk.bbappend
>> >>  create mode 100644 meta-cedartrail/recipes-sato/images/core-image-
>> >sato.bbappend
>> >>
>> >> diff --git a/meta-cedartrail/recipes-sato/images/core-image-sato-
>> >dev.bbappend b/meta-cedartrail/recipes-sato/images/core-image-sato-
>> >dev.bbappend
>> >> new file mode 100644
>> >> index 000..33283f4
>> >> --- /dev/null
>> >> +++ b/meta-cedartrail/recipes-sato/images/core-image-sato-
>dev.bbappend
>> >> @@ -0,0 +1,2 @@
>> >> +IMAGE_INSTALL += "web-webkit bigbuckbunny-ogg ogg-CC-BY-3.0-music-
>> >samples"
>> >> +
>> >> diff --git a/meta-cedartrail/recipes-sato/images/core-image-sato-
>> >sdk.bbappend b/meta-cedartrail/recipes-sato/images/core-image-sato-
>> >sdk.bbappend
>> >> new file mode 100644
>> >> index 000..33283f4
>> >> --- /dev/null
>> >> +++ b/meta-cedartrail/recipes-sato/images/core-image-sato-
>sdk.bbappend
>> >> @@ -0,0 +1,2 @@
>> >> +IMAGE_INSTALL += "web-webkit bigbuckbunny-ogg ogg-CC-BY-3.0-music-
>> >samples"
>> >> +
>> >> diff --git a/meta-cedartrail/recipes-sato/images/core-image-
>> >sato.bbappend b/meta-cedartrail/recipes-sato/images/core-image-
>> >sato.bbappend
>> >> new file mode 100644
>> >> index 000..4c1ccac
>> >> --- /dev/null
>> >> +++ b/meta-cedartrail/recipes-sato/images/core-image-sato.bbappend
>> >> @@ -0,0 +1 @@
>> >> +IMAGE_INSTALL += "web-webkit bigbuckbunny-ogg  ogg-CC-BY-3.0-
>music-
>> >samples"
>> >
>> >These will always add the media files etc whenever anyone builds any
>of
>> >these.  Is that really what you want?
>>
>> Yes. By default we wanted to have all these included when customer
>builds
>> a regular sato image.
>> So, I think it would be good if it remains unchanged.
>>
>
>But what if I wanted to build a sato image that didn't include those
>media files?  I can no longer type 'bitbake core-image-sato' and get
>that.

Ok. I will change this to a new test image recipe.
Thanks
Kishore.

>
>Tom
>
>> Thanks
>> Kishore.
>>
>> >
>> >Maybe creating separate test image recipes that do this would be more
>> >along the lines of what you wanted...
>> >
>> >Tom
>>
>

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

[yocto] 1.2_M2 build fails for syslinux_4.03.bb for Romley BSP

[Bodke, Kishore K]

Hi ,

Poky and meta-intel for 1.2_M2 build is failing for syslinux_4.03 recipe.

Did anyone saw this for other BSPs?


ERROR: Function 'do_compile' failed (see 
/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/temp/log.do_compile.53231
 for further information)
ERROR: Logfile of failure stored in: 
/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/temp/log.do_compile.53231
Log data follows:
| ERROR: Function 'do_compile' failed (see 
/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/temp/log.do_compile.53231
 for further information)
| NOTE: make -j 8 
BINDIR=/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/bin
 
SBINDIR=/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/sbin
 
LIBDIR=/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/lib
 
DATADIR=/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/share
 
MANDIR=/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/share/man
 
INCDIR=/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/include
 CC=ccache gcc  installer
| make -r installer-local
| make[1]: Entering directory 
`/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/syslinux-4.03'
| make[1]: Nothing to be done for `installer-local'.
| make[1]: Leaving directory 
`/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/syslinux-4.03'
| set -e ; for i in libinstaller mtools linux extlinux utils; do make -r -C $i 
all ; done
| make[1]: Entering directory 
`/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/syslinux-4.03/libinstaller'
| make[1]: Nothing to be done for `all'.
| make[1]: Leaving directory 
`/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/syslinux-4.03/libinstaller'
| make[1]: Entering directory 
`/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/syslinux-4.03/mtools'
| make[1]: Nothing to be done for `all'.
| make[1]: Leaving directory 
`/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/syslinux-4.03/mtools'
| make[1]: Entering directory 
`/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/syslinux-4.03/linux'
| ccache gcc  -Wp,-MT,syslinux.o,-MMD,./.syslinux.o.d -W -Wall 
-Wstrict-prototypes -D_FILE_OFFSET_BITS=64 -g -O0 -Dalloca=malloc -I. -I.. 
-I../libinstaller -c -o syslinux.o syslinux.c
| ccache gcc  -Wp,-MT,syslxcom.o,-MMD,./.syslxcom.o.d -W -Wall 
-Wstrict-prototypes -D_FILE_OFFSET_BITS=64 -g -O0 -Dalloca=malloc -I. -I.. 
-I../libinstaller -c -o syslxcom.o ../libinstaller/syslxcom.c
| In file included from ../libinstaller/linuxioctl.h:22:0,
|  from ../libinstaller/syslxcom.c:33:
| /usr/include/linux/ext2_fs.h:178:41: error: unknown type name 'umode_t'
| make[1]: *** [syslxcom.o] Error 1
| make[1]: *** Waiting for unfinished jobs
| In file included from ../libinstaller/linuxioctl.h:22:0,
|  from syslinux.c:50:
| /usr/include/linux/ext2_fs.h:178:41: error: unknown type name 'umode_t'
| make[1]: *** [syslinux.o] Error 1
| make[1]: Leaving directory 
`/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-linux/syslinux-native-4.03-r3/syslinux-4.03/linux'
| make: *** [installer] Error 2
| ERROR: oe_runmake failed
NOTE: package syslinux-native-4.03-r3: task do_compile: Failed
NOTE: package mtools-native-4.0.17-r0: task do_install: Started
NOTE: package 
linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4:
 task do_validate_branches: Started
NOTE: package 
linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r4:
 task do_validate_branches: Succeeded
NOTE: package gcc-cross-initial-4.6.2+svnr181430-r20: task do_populate_sysroot: 
Started
NOTE: Running task 2732 of 4771 (ID: 1998, 
/home/tmelab/yocto/poky/poky-1.2_M2.final/meta/recipes-kernel/linux-libc-headers/linux-libc-headers-yocto_git.bb,
 do_patch)
NOTE: Running task 2733 of 4771 (ID: 4286, 
/home/tmelab/yocto/poky/poky-1.2_M2.final/meta/recipes-devtools/gcc/gcc-cross-initial_4.6.bb,
 do_package_write_rpm)
ERROR: Task 152 
(virtual:native:/home/tmelab/yocto/poky/poky-1.2_M2.final/meta/recipes-devtools/syslinux/syslinux_4.03.bb,
 do_compile) failed with exit code '1'
Waiting for 2 active tasks to finish:
0: mtools-native-4.0.17-r0 do_install (pid 53232)
1: gcc-cross-initial-4.6.2+svnr181430-r20 do_populate_sysroot (pid 52951)
Waiting for 3 active tasks to finish:
0: mtools-native-4.0.17-r0 do_install (pid 53232)
1: 
linux-libc-headers-yocto-2.6.37+git-1+69cfbdf9f1f

Re: [yocto] 1.2_M2 build fails for syslinux_4.03.bb for Romley BSP

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Mark Hatle
>Sent: Monday, April 09, 2012 3:41 PM
>To: yocto@yoctoproject.org
>Subject: Re: [yocto] 1.2_M2 build fails for syslinux_4.03.bb for Romley
>BSP
>
>On 4/9/12 5:36 PM, Bodke, Kishore K wrote:
>> Hi ,
>>
>> Poky and meta-intel for 1.2_M2 build is failing for syslinux_4.03
>recipe.
>>
>> Did anyone saw this for other BSPs?
>>
>> ERROR: Function 'do_compile' failed (see
>> /home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/temp/log.do_compile.53231
>> for further information)
>>
>> ERROR: Logfile of failure stored in:
>> /home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/temp/log.do_compile.53231
>>
>> Log data follows:
>>
>> | ERROR: Function 'do_compile' failed (see
>> /home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/temp/log.do_compile.53231
>> for further information)
>>
>> | NOTE: make -j 8
>> BINDIR=/home/tmelab/yocto/poky/poky-
>1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/bin
>> SBINDIR=/home/tmelab/yocto/poky/poky-
>1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/sbin
>> LIBDIR=/home/tmelab/yocto/poky/poky-
>1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/lib
>> DATADIR=/home/tmelab/yocto/poky/poky-
>1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/share
>> MANDIR=/home/tmelab/yocto/poky/poky-
>1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/share/man
>> INCDIR=/home/tmelab/yocto/poky/poky-
>1.2_M2.final/build/tmp/sysroots/x86_64-linux/usr/include
>> CC=ccache gcc installer
>>
>> | make -r installer-local
>>
>> | make[1]: Entering directory
>> `/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/syslinux-4.03'
>>
>> | make[1]: Nothing to be done for `installer-local'.
>>
>> | make[1]: Leaving directory
>> `/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/syslinux-4.03'
>>
>> | set -e ; for i in libinstaller mtools linux extlinux utils; do make
>-r -C $i
>> all ; done
>>
>> | make[1]: Entering directory
>> `/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/syslinux-4.03/libinstaller'
>>
>> | make[1]: Nothing to be done for `all'.
>>
>> | make[1]: Leaving directory
>> `/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/syslinux-4.03/libinstaller'
>>
>> | make[1]: Entering directory
>> `/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/syslinux-4.03/mtools'
>>
>> | make[1]: Nothing to be done for `all'.
>>
>> | make[1]: Leaving directory
>> `/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/syslinux-4.03/mtools'
>>
>> | make[1]: Entering directory
>> `/home/tmelab/yocto/poky/poky-1.2_M2.final/build/tmp/work/x86_64-
>linux/syslinux-native-4.03-r3/syslinux-4.03/linux'
>>
>> | ccache gcc -Wp,-MT,syslinux.o,-MMD,./.syslinux.o.d -W -Wall
>> -Wstrict-prototypes -D_FILE_OFFSET_BITS=64 -g -O0 -Dalloca=malloc -I.
>-I..
>> -I../libinstaller -c -o syslinux.o syslinux.c
>>
>> | ccache gcc -Wp,-MT,syslxcom.o,-MMD,./.syslxcom.o.d -W -Wall
>> -Wstrict-prototypes -D_FILE_OFFSET_BITS=64 -g -O0 -Dalloca=malloc -I.
>-I..
>> -I../libinstaller -c -o syslxcom.o ../libinstaller/syslxcom.c
>>
>> | In file included from ../libinstaller/linuxioctl.h:22:0,
>>
>> | from ../libinstaller/syslxcom.c:33:
>>
>> | /usr/include/linux/ext2_fs.h:178:41: error: unknown type name
>'umode_t'
>
>This looks like a bug in the libinstaller component of syslinux.  It is
>relying
>on the include files from the host system's kernel to gain access to
>kernel
>specific headers.
>
>Instead this thing should be cleaned of references to
>/usr/include/linux, and
>local versions (that are known to be correct) should be provided.
>
>Please be sure to file a bug in the bugzilla.yoctoproject.org system --
>or if
>you can't do that for some reason, let me know and I'll file it.
>

Filed a bug.  BUG:2269.

Thanks
Kishore.

>--Mark
>
>> | make[1]: *** [syslxcom.o] Error 1
>>
>> | make[1]: *** Waiting for unfinished jobs

Re: [yocto] [PATCH 0/1] [KERNEL] Add igb driver to Romley Machine

[Bodke, Kishore K]

>-Original Message-
>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>Sent: Wednesday, April 11, 2012 6:25 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; Bruce Ashfield
>Subject: Re: [yocto] [PATCH 0/1] [KERNEL] Add igb driver to Romley
>Machine
>
>On 12-04-10 08:15 PM, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke
>>
>> Romley machine has builtin 82580 Giga bit Ethernet
>> Controller. Adding the relavent igb nic driver.
>
>Looks fine for the tree, no risk to other BSPs. Correct me
>if you'd rather this wait until after the 1.2 release.

Yeah, its Romley machine specific.
Please make it available for 1.2 release.

Thanks
Kishore.

>
>I'll have this pushed out later today.
>
>Cheers,
>
>Bruce
>
>>
>> Please pull into linux-yocto-3.2/meta
>>
>> Thanks
>> Kishore.
>>
>> The following changes since commit
>59f350ec3794e19fa806c1b73749d851f8ebf364:
>>
>>meta: Add common-pc-tiny.scc (2012-03-31 23:43:34 -0400)
>>
>> are available in the git repository at:
>>git://git.pokylinux.org/linux-yocto-2.6.37-contrib
>kishore/romley/meta
>>http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-
>contrib/log/?h=kishore/romley/meta
>>
>> Kishore Bodke (1):
>>meta: Add igb.scc to Romley
>>
>>   meta/cfg/kernel-cache/bsp/romley/romley.scc |3 +--
>>   1 files changed, 1 insertions(+), 2 deletions(-)
>>

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

Re: [yocto] [PATCH 2/9] [meta-intel] Cedartrail: Update SRCREVS and add EFI Support.

[Bodke, Kishore K]

>>  KERNEL_FEATURES_append_cedartrail += " cfg/smp.scc"
>> +KERNEL_FEATURES_append_cedartrail += " cfg/drm-cdvpvr.scc"
>> +KERNEL_FEATURES_append_cedartrail += " bsp/cedartrail/cedartrail-pvr-
>merge.scc"
>> +KERNEL_FEATURES_append_cedartrail += " cfg/efi-ext.scc"
>
>
>I suggest moving all of this into the cedartrail.scc file in the
>linux-yocto meta branch. These are all core bits required for the BSP,
>they don't need to be easily changed from recipe-space.
>
>The exception would be the pvr bits. You can make a single
>cedartrail.scc that supports both configs (with and without pvr) and
>only modify the pvr one here in recipe space - the rest belongs in
>linux-yocto/meta

Hi Darren,

All the above are specific to pvr only.  (cfg/drm-cdvpvr.scc , 
bsp/cedartrail/cedartrail-pvr-merge.scc, and cfg/efi-ext.scc)
These are not needed for without pvr versions of the BSP.
I think if I move them to Cedartrail.scc, these will get pulled in for no-pvr 
version of the build and may cause the build to fail.

Thanks
Kishore.


>
>
>> +COMPATIBLE_MACHINE_cedartrail-nopvr = "cedartrail"
>> +KMACHINE_cedartrail-nopvr  = "cedartrail"
>> +KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc"
>
>Same here.
>
>--
>Darren
>
>--
>Darren Hart
>Intel Open Source Technology Center
>Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 2/9] [meta-intel] Cedartrail: Update SRCREVS and add EFI Support.

[Bodke, Kishore K]

>-Original Message-
>From: Hart, Darren
>Sent: Monday, April 23, 2012 12:33 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; Zanussi, Tom
>Subject: Re: [yocto] [PATCH 2/9] [meta-intel] Cedartrail: Update SRCREVS
>and add EFI Support.
>
>On 04/23/2012 11:31 AM, Bodke, Kishore K wrote:
>>
>>>>  KERNEL_FEATURES_append_cedartrail += " cfg/smp.scc"
>>>> +KERNEL_FEATURES_append_cedartrail += " cfg/drm-cdvpvr.scc"
>>>> +KERNEL_FEATURES_append_cedartrail += " bsp/cedartrail/cedartrail-
>pvr-
>>> merge.scc"
>>>> +KERNEL_FEATURES_append_cedartrail += " cfg/efi-ext.scc"
>>>
>>>
>>> I suggest moving all of this into the cedartrail.scc file in the
>>> linux-yocto meta branch. These are all core bits required for the
>BSP,
>>> they don't need to be easily changed from recipe-space.
>>>
>>> The exception would be the pvr bits. You can make a single
>>> cedartrail.scc that supports both configs (with and without pvr) and
>>> only modify the pvr one here in recipe space - the rest belongs in
>>> linux-yocto/meta
>>
>> Hi Darren,
>>
>> All the above are specific to pvr only.
>
>You can't use EFI to boot the system with the pvr driver?

EFI is also for pvr build only.  For without pvr builds EFI boot is not 
supported.

Thanks
Kishore.

>
>--
>Darren
>
>> (cfg/drm-cdvpvr.scc , bsp/cedartrail/cedartrail-pvr-merge.scc, and
>cfg/efi-ext.scc)
>> These are not needed for without pvr versions of the BSP.
>> I think if I move them to Cedartrail.scc, these will get pulled in for
>no-pvr version of the build and may cause the build to fail.
>>
>> Thanks
>> Kishore.
>>
>>
>>>
>>>
>>>> +COMPATIBLE_MACHINE_cedartrail-nopvr = "cedartrail"
>>>> +KMACHINE_cedartrail-nopvr  = "cedartrail"
>>>> +KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc"
>>>
>>> Same here.
>>>
>>> --
>>> Darren
>>>
>>> --
>>> Darren Hart
>>> Intel Open Source Technology Center
>>> Yocto Project - Linux Kernel
>
>
>--
>Darren Hart
>Intel Open Source Technology Center
>Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] KERNEL build failure for Master

[Bodke, Kishore K]

Hi,
Linux-yocto  build is failing for Cedartrail for the Master and denzil branch.
Is it failing for any other BSPs?
Below is the error.

ERROR: Function failed: Fetcher failure: Fetch command export 
HOME="/home/kishore"; export https_proxy="https://proxy.sc.intel.com:911/";; 
export ftp_proxy="http://proxy.sc.intel.com:911/";; export 
http_proxy="http://proxy.sc.intel.com:911/";; export 
GIT_CONFIG="/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/etc/gitconfig";
 export GIT_PROXY_COMMAND="/usr/local/bin/git-proxy"; export 
PATH="/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/usr/local/src/may_9/build/tmp/sysroots/cedartrail/usr/bin/crossscripts:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/bin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux//bin:/usr/local/src/may_9/scripts:/usr/local/src/may_9/bitbake/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/src/may_9/scripts";
 git clone -s -n --mirror 
/usr/local/src/may_9/build/downloads/git2/git.yoctoproject.org.linux-yocto-3.0/ 
/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/git/
 could not be run:
None
ERROR: Logfile of failure stored in: 
/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_unpack.4250
Log data follows:
| DEBUG: Running export HOME="/home/kishore"; export 
https_proxy="https://proxy.sc.intel.com:911/";; export 
ftp_proxy="http://proxy.sc.intel.com:911/";; export 
http_proxy="http://proxy.sc.intel.com:911/";; export 
GIT_CONFIG="/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/etc/gitconfig";
 export GIT_PROXY_COMMAND="/usr/local/bin/git-proxy"; export 
PATH="/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/usr/local/src/may_9/build/tmp/sysroots/cedartrail/usr/bin/crossscripts:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/bin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux//bin:/usr/local/src/may_9/scripts:/usr/local/src/may_9/bitbake/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/src/may_9/scripts";
 git clone -s -n --mirror 
/usr/local/src/may_9/build/downloads/git2/git.yoctoproject.org.linux-yocto-3.0/ 
/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/git/
| ERROR: Function failed: Fetcher failure: Fetch command export 
HOME="/home/kishore"; export https_proxy="https://proxy.sc.intel.com:911/";; 
export ftp_proxy="http://proxy.sc.intel.com:911/";; export 
http_proxy="http://proxy.sc.intel.com:911/";; export 
GIT_CONFIG="/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/etc/gitconfig";
 export GIT_PROXY_COMMAND="/usr/local/bin/git-proxy"; export 
PATH="/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/usr/local/src/may_9/build/tmp/sysroots/cedartrail/usr/bin/crossscripts:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/usr/bin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-linux//bin:/usr/local/src/may_9/scripts:/usr/local/src/may_9/bitbake/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/src/may_9/scripts";
 git clone -s -n --mirror 
/usr/local/src/may_9/build/downloads/git2/git.yoctoproject.org.linux-yocto-3.0/ 
/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/git/
 could not be run:
| None
NOTE: package 
linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4:
 task do_unpack: Failed
ERROR: Task 858 
(/usr/local/src/may_9/meta/recipes-kernel/linux/linux-yocto_3.0.bb, do_unpack) 
failed with exit code '1'

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] KERNEL build failure for Master

[Bodke, Kishore K]

Is this error also proxy setup issue?

ERROR: Function failed: do_patch (see 
/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_patch.7982
 for further information)
ERROR: Logfile of failure stored in: 
/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_patch.7982
Log data follows:
| ERROR: Function failed: do_patch (see 
/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_patch.7982
 for further information)
| WARNING: addon feature "features/netfilter" was not found
| WARNING: addon feature "features/taskstats" was not found
| WARNING: addon feature "cfg/smp" was not found
| WARNING: addon feature "cfg/drm-cdvpvr" was not found
| WARNING: addon feature "bsp/cedartrail/cedartrail-pvr-merge" was not found
| WARNING: addon feature "cfg/efi-ext" was not found
| WARNING: addon feature "features/power/intel" was not found
| ERROR: required features were not found. aborting
| ERROR. Could not update yocto/standard/base
NOTE: package 
linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4:
 task do_patch: Failed

Thanks
Kishore.

>-Original Message-
>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>Sent: Wednesday, May 09, 2012 3:36 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: KERNEL build failure for Master
>
>On 12-05-09 4:37 PM, Bodke, Kishore K wrote:
>> Hi,
>>
>> Linux-yocto build is failing for Cedartrail for the Master and denzil
>> branch.
>>
>> Is it failing for any other BSPs?
>
>Everything is fine here, this looks to be something specific with your
>proxy setup injecting bad commands into the subshell.
>
>Bruce
>
>>
>> Below is the error.
>>
>> ERROR: Function failed: Fetcher failure: Fetch command export
>> HOME="/home/kishore"; export
>> https_proxy="https://proxy.sc.intel.com:911/";; export
>> ftp_proxy="http://proxy.sc.intel.com:911/";; export
>> http_proxy="http://proxy.sc.intel.com:911/";; export
>> GIT_CONFIG="/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/etc/gitconfig";
>> export GIT_PROXY_COMMAND="/usr/local/bin/git-proxy"; export
>> PATH="/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/usr/bin/core2-poky-
>linux:/usr/local/src/may_9/build/tmp/sysroots/cedartrail/usr/bin/crosssc
>ripts:/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/usr/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/usr/bin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux//bin:/usr/local/src/may_9/scripts:/usr/local/src/may_9/bitbake/bin
>/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/game
>s:/usr/local/src/may_9/scripts";
>> git clone -s -n --mirror
>> /usr/local/src/may_9/build/downloads/git2/git.yoctoproject.org.linux-
>yocto-3.0/
>> /usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-
>3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37
>916828dc8b4ef72f5d35a94-r4/git/
>> could not be run:
>>
>> None
>>
>> ERROR: Logfile of failure stored in:
>> /usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-
>3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37
>916828dc8b4ef72f5d35a94-r4/temp/log.do_unpack.4250
>>
>> Log data follows:
>>
>> | DEBUG: Running export HOME="/home/kishore"; export
>> https_proxy="https://proxy.sc.intel.com:911/";; export
>> ftp_proxy="http://proxy.sc.intel.com:911/";; export
>> http_proxy="http://proxy.sc.intel.com:911/";; export
>> GIT_CONFIG="/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/etc/gitconfig";
>> export GIT_PROXY_COMMAND="/usr/local/bin/git-proxy"; export
>> PATH="/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/usr/bin/core2-poky-
>linux:/usr/local/src/may_9/build/tmp/sysroots/cedartrail/usr/bin/crosssc
>ripts:/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/usr/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/usr/bin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux/sbin:/usr/local/src/may_9/build/tmp/sysroots/x86_64-
>linux//bin:/usr/local/src/may_9/scr

Re: [yocto] KERNEL build failure for Master

[Bodke, Kishore K]

>-Original Message-
>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>Sent: Wednesday, May 09, 2012 4:04 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: KERNEL build failure for Master
>
>On 12-05-09 7:01 PM, Bodke, Kishore K wrote:
>> Is this error also proxy setup issue?
>
>Nope. I sent a fix for it today, and Richard merged it to master
>a few hours ago. An update should fix your issue.

I have updated. But I still see the error.
If it is a proxy setup issue, I should not be able to build any BSPs.
But I am able to build ROMLEY successfully.
It is only failing for Cedartrail.

WARNING: Failed to fetch URL 
git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=yocto/standard/base,meta,yocto/pvr;name=machine,meta,pvr
NOTE: package kmod-native-8-r0.0: task do_patch: Started
ERROR: Fetcher failure: Fetch command export HOME="/home/kishore"; export 
https_proxy="https://proxy.sc.intel.com:911/";; export 
ftp_proxy="http://proxy.sc.intel.com:911/";; export 
http_proxy="http://proxy.sc.intel.com:911/";; export 
GIT_CONFIG="/usr/local/src/may10/build/tmp/sysroots/x86_64-linux/etc/gitconfig";
 export GIT_PROXY_COMMAND="/usr/local/bin/git-proxy"; export 
PATH="/usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/core2-poky-linux:/usr/local/src/may10/build/tmp/sysroots/cedartrail/usr/bin/crossscripts:/usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/sbin:/usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin:/usr/local/src/may10/build/tmp/sysroots/x86_64-linux/sbin:/usr/local/src/may10/build/tmp/sysroots/x86_64-linux//bin:/usr/local/src/may10/scripts:/usr/local/src/may10/bitbake/bin/:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/src/may10/scripts";
 tar -xzf /usr/local/src/may10/build/downloads/git2_git.yo
 ctoproject.org.linux-yocto-3.0.tar.gz could not be run:
None
ERROR: Function failed: Fetcher failure for URL: 
'git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=yocto/standard/base,meta,yocto/pvr;name=machine,meta,pvr'.
 Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: 
/usr/local/src/may10/build/tmp/work/cedartrail-poky-linux/linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4/temp/log.do_fetch.26424
NOTE: package 
linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4:
 task do_fetch: Failed
ERROR: Task 6 
(/usr/local/src/may10/meta/recipes-kernel/linux/linux-yocto_3.0.bb, do_fetch) 
failed with exit code '1'

Thanks
Kishore.

>
>Bruce
>
>>
>> ERROR: Function failed: do_patch (see
>/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-
>3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37
>916828dc8b4ef72f5d35a94-r4/temp/log.do_patch.7982 for further
>information)
>> ERROR: Logfile of failure stored in:
>/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-
>3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37
>916828dc8b4ef72f5d35a94-r4/temp/log.do_patch.7982
>> Log data follows:
>> | ERROR: Function failed: do_patch (see
>/usr/local/src/may_9/build/tmp/work/cedartrail-poky-linux/linux-yocto-
>3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37
>916828dc8b4ef72f5d35a94-r4/temp/log.do_patch.7982 for further
>information)
>> | WARNING: addon feature "features/netfilter" was not found
>> | WARNING: addon feature "features/taskstats" was not found
>> | WARNING: addon feature "cfg/smp" was not found
>> | WARNING: addon feature "cfg/drm-cdvpvr" was not found
>> | WARNING: addon feature "bsp/cedartrail/cedartrail-pvr-merge" was not
>found
>> | WARNING: addon feature "cfg/efi-ext" was not found
>> | WARNING: addon feature "features/power/intel" was not found
>> | ERROR: required features were not found. aborting
>> | ERROR. Could not update yocto/standard/base
>> NOTE: package linux-yocto-
>3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37
>916828dc8b4ef72f5d35a94-r4: task do_patch: Failed
>>
>> Thanks
>> Kishore.
>>
>>> -Original Message-
>>> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>>> Sent: Wednesday, May 09, 2012 3:36 PM
>>> To: Bodke, Kishore K
>>> Cc: yocto@yoctoproject.org
>>> Subject: Re: KERNEL build failure for Master
>>>
>>> On 12-05-09 4:37 PM, Bodke, Kishore K wrote:
>>>> Hi,
>>>>
>>>> Linux-yocto build is failing

Re: [yocto] KERNEL build failure for Master

[Bodke, Kishore K]

94-r4/temp/log.do_patch.31865
 for further information)
| cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| /usr/local/src/may10/build/tmp/sysroots/x86_64-linux/usr/bin/scc: line 399: 
yocto/standard/cedartrail-standard: No such file or directory
| ERROR. Could not find an excutable target for yocto/standard/base
| ERROR. Could not locate meta series for yocto/standard/cedartrail
| ERROR. Could not modify yocto/standard/base
NOTE: package 
linux-yocto-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+81fd8c307997aff37916828dc8b4ef72f5d35a94-r4:
 task do_patch: Failed
ERROR: Task 3 
(/usr/local/src/may10/meta/recipes-kernel/linux/linux-yocto_3.0.bb, do_patch) 
failed with exit code '1'

Thanks
Kishore.

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Bodke, Kishore K
>Sent: Thursday, May 10, 2012 11:08 AM
>To: Bruce Ashfield
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] KERNEL build failure for Master
>
>
>
>>-Original Message-
>>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>>Sent: Wednesday, May 09, 2012 4:04 PM
>>To: Bodke, Kishore K
>>Cc: yocto@yoctoproject.org
>>Subject: Re: KERNEL build failure for Master
>>
>>On 12-05-09 7:01 PM, Bodke, Kishore K wrote:
>>> Is this error also proxy setup issue?
>>
>>Nope. I sent a fix for it today, and Richard merged it to master
>>a few hours ago. An update should fix your issue.
>
>I have updated. But I still see the error.
>If it is a proxy setup issue, I should not be able to build any BSPs.
>But I am able to build ROMLEY successfully.
>It is only failing for Cedartrail.
>
>WARNING: Failed to fetch URL git://git.yoctoproject.org/linux-yocto-
>3.0;protocol=git;bareclone=1;branch=yocto/standard/base,meta,yocto/pvr;n
>ame=machine,meta,pvr
>NOTE: package kmod-native-8-r0.0: task do_patch: Started
>ERROR: Fetcher failure: Fetch command export HOME="/home/kishore";
>export https_proxy="https://proxy.sc.intel.com:911/";; export
>ftp_proxy="http://proxy.sc.intel.com:911/";; export
>http_proxy="http://proxy.sc.intel.com:911/";; export
>GIT_CONFIG="/usr/local/src/may10/build/tmp/sysroots/x86_64-
>linux/etc/gitconfig"; export GIT_PROXY_COMMAND="/usr/local/bin/git-
&

Re: [yocto] Unable to fetch URL from any source

[Bodke, Kishore K]

Yes.
I saw the same failures too.
For some reason 3.0 kernel fetch failures started showing up for Cedartrail.
There is a discussion thread on this in the mailing list.
Bruce might be able to give some pointers on this.

-Kishore.

From: yocto-boun...@linux.intel.com [mailto:yocto-boun...@linux.intel.com] On 
Behalf Of Chiang, Terence
Sent: Friday, May 11, 2012 3:05 AM
To: Yocto Project Discussions (yo...@linux.intel.com)
Subject: [Yocto] Unable to fetch URL from any source

Hi
While I build the image for cedartrail with "denzil"
With meta-cedartrail and distro = "poky". the error is following and the detail 
log is attached.

Function failed: Fetcher failure for URL: 
'git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=yocto/standard/cedartrail,meta,yocto/pvr;name=machine,meta,pvr'.
 Unable to fetch URL from any source.

Do you encounter similar issue?

Regard,
-Terence

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

Re: [yocto] Unable to fetch URL from any source

[Bodke, Kishore K]

>-Original Message-
>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>Sent: Friday, May 11, 2012 11:42 AM
>To: Bodke, Kishore K
>Cc: Yocto Project Discussions; yocto@yoctoproject.org
>Subject: Re: Unable to fetch URL from any source
>
>On 12-05-11 01:04 PM, Bodke, Kishore K wrote:
>> Yes.
>>
>> I saw the same failures too.
>>
>> For some reason 3.0 kernel fetch failures started showing up for
>Cedartrail.
>>
>> There is a discussion thread on this in the mailing list.
>>
>> Bruce might be able to give some pointers on this.
>
>Unfortunately not. From what I hear, it's server issues. Which will be
>resolved ASAP.

Does anyone have update on this?

Thanks
Kishore.

>
>Cheers,
>
>Bruce
>
>>
>> -Kishore.
>>
>> *From:*yocto-boun...@linux.intel.com
>> [mailto:yocto-boun...@linux.intel.com] *On Behalf Of *Chiang, Terence
>> *Sent:* Friday, May 11, 2012 3:05 AM
>> *To:* Yocto Project Discussions (yo...@linux.intel.com)
>> *Subject:* [Yocto] Unable to fetch URL from any source
>>
>> Hi
>>
>> While I build the image for cedartrail with "denzil"
>>
>> With meta-cedartrail and distro = "poky". the error is following and
>the
>> detail log is attached.
>>
>> Function failed: Fetcher failure for URL:
>> 'git://git.yoctoproject.org/linux-yocto-
>3.0;protocol=git;bareclone=1;branch=yocto/standard/cedartrail,meta,yocto
>/pvr;name=machine,meta,pvr'.
>> Unable to fetch URL from any source.
>>
>> Do you encounter similar issue?
>>
>> /Regard,/
>>
>> -Terence
>>

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

Re: [yocto] [PATCH 0/1] meta-intel: update README.sources for all BSPs

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Friday, May 25, 2012 2:00 PM
>To: yocto@yoctoproject.org; Bodke, Kishore K; dvh...@linux.intel.com;
>Saxena, Rahul
>Cc: Zanussi, Tom
>Subject: [PATCH 0/1] meta-intel: update README.sources for all BSPs
>
>From: Tom Zanussi 
>
>I took the liberty of updating all the BSPs in meta-intel with the denzil
>sources URL.
>
>To those on the To list: please let me know if you don't want this for
>your BSP(s).
>

Acked-by:  Kishore Bodke 


>The following changes since commit
>a62c485edffed30ea95658760948fd50925adfb0:
>  Darren Hart (1):
>linux-yocto_3.0: Update KMACHINE and KBRANCH to play nice with new
>kerntools
>
>are available in the git repository at:
>
>  git://git.yoctoproject.org/meta-intel.git tzanussi/denzil-README.sources-
>update
>  http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/denzil-
>README.sources-update
>
>Tom Zanussi (1):
>  meta-intel: update README.sources with denzil link
>
> meta-cedartrail/README.sources   |2 +-
> meta-crownbay/README.sources |2 +-
> meta-emenlow/README.sources  |2 +-
> meta-fishriver/README.sources|2 +-
> meta-fri2/README.sources |2 +-
> meta-jasperforest/README.sources |2 +-
> meta-n450/README.sources |2 +-
> meta-romley/README.sources   |2 +-
> meta-sugarbay/README.sources |2 +-
> meta-sys940x/README.sources  |3 +--
> 10 files changed, 10 insertions(+), 11 deletions(-)

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

Re: [yocto] meta-cedartrail - serial console

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of jfabernathy
>Sent: Thursday, May 31, 2012 9:12 AM
>To: yocto@yoctoproject.org
>Subject: [yocto] meta-cedartrail - serial console
>
>Using a DN2800MT (Marshalltown) Intel board, I'm testing the
>meta-cedartrail using edison branch and noticed an issues with the
>serial console.
>
>The cedartrail.conf in the machine directory has the following statements:
>
>SYSLINUX_OPTS = "serial 0 115200"
>SERIAL_CONSOLE = "115200 ttyS0"
>APPEND += "console=ttyS0,115200 console=tty0"
>

I just saw that Edison branch has ttyS3 enabled.

SYSLINUX_OPTS = "serial 3 115200"
SERIAL_CONSOLE = "115200 ttyS3"
APPEND += "console=ttyS3,115200 console=tty3"

Are you looking into right branch?

Thanks
-Kishore.
 
>However, when the image booted, I had no serial console on ttyS0.  I
>checked /etc/inittab and noticed that the following line existed:
>
>S:2345:respawn:/sbin/getty 115200 ttyS3
>
>I changed the ttyS3 to ttyS0 and then I have a serial console on the
>next reboot.  So it appears the override in the .conf file is not
>working.  Also I only have the console from getty, and not the kernel
>logging console.
>
>Anyone have a solution??
>
>If this is considered a bug I can put it on bugzilla.
>
>Jim A
>
>___
>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: [yocto] meta-cedartrail - serial console

[Bodke, Kishore K]

>-Original Message-
>From: Hart, Darren
>Sent: Thursday, May 31, 2012 12:43 PM
>To: jfabernathy
>Cc: Bodke, Kishore K; yocto@yoctoproject.org
>Subject: Re: [yocto] meta-cedartrail - serial console
>
>On 05/31/2012 12:32 PM, jfabernathy wrote:
>> On 05/31/2012 02:18 PM, Bodke, Kishore K wrote:
>>>
>>>> -Original Message-
>>>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>>> boun...@yoctoproject.org] On Behalf Of jfabernathy
>>>> Sent: Thursday, May 31, 2012 9:12 AM
>>>> To: yocto@yoctoproject.org
>>>> Subject: [yocto] meta-cedartrail - serial console
>>>>
>>>> Using a DN2800MT (Marshalltown) Intel board, I'm testing the
>>>> meta-cedartrail using edison branch and noticed an issues with the
>>>> serial console.
>>>>
>>>> The cedartrail.conf in the machine directory has the following statements:
>>>>
>>>> SYSLINUX_OPTS = "serial 0 115200"
>>>> SERIAL_CONSOLE = "115200 ttyS0"
>>>> APPEND += "console=ttyS0,115200 console=tty0"
>>>>
>>> I just saw that Edison branch has ttyS3 enabled.
>>>
>>> SYSLINUX_OPTS = "serial 3 115200"
>>> SERIAL_CONSOLE = "115200 ttyS3"
>>> APPEND += "console=ttyS3,115200 console=tty3"
>>>
>>> Are you looking into right branch?
>>>
>>> Thanks
>>> -Kishore.
>>>
>>
>> So how do you get changes in the cedartrail.conf file to take affect??
>> I edited the file and did the bitbake again, but nothing changed.  I'm
>> guessing I need a bitbake -c cleansstate "somthing"  But I don't know
>> what to put there to make rebuild with ttyS0.
>>
>
>Ah yes, this rebuild is a bit frustrating. I believe it is the
>task_core* tasks you need to rebuild. bitbake -u depexp -g
>core-image-base (whatever your image is) will allow you to view which
>task_ tasks it is building, try cleansstate'ing those and rebuilding the
>image.

I had to remove the above 3 lines from cedartrail.conf and 
SERIAL_CONSOLE ?= "115200 ttyS0" line from conf/machine/include/ia32-base.inc
rebuild the image.
It is disabled now.

I edited grub and added back console=ttyS0,115200 console=tty0
Serial console got active, but I could not get the login prompt on serial 
console, only boot messages and serial console hangs after these messages.

EXT3-fs (loop0): recovery complete
EXT3-fs (loop0): mounted filesystem with ordered data mode
udev[469]: starting version 164
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)


Gfx desktop came up though with no issues.

Thanks
Kishore.

>
>--
>Darren
>
>> Jim A
>>>> However, when the image booted, I had no serial console on ttyS0.  I
>>>> checked /etc/inittab and noticed that the following line existed:
>>>>
>>>> S:2345:respawn:/sbin/getty 115200 ttyS3
>>>>
>>>> I changed the ttyS3 to ttyS0 and then I have a serial console on the
>>>> next reboot.  So it appears the override in the .conf file is not
>>>> working.  Also I only have the console from getty, and not the kernel
>>>> logging console.
>>>>
>>>> Anyone have a solution??
>>>>
>>>> If this is considered a bug I can put it on bugzilla.
>>>>
>>>> Jim A
>>>>
>>>> ___
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>--
>Darren Hart
>Intel Open Source Technology Center
>Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] meta-cedartrail - serial console

[Bodke, Kishore K]

>-Original Message-
>From: Hart, Darren
>Sent: Friday, June 01, 2012 11:12 AM
>To: Bodke, Kishore K
>Cc: jfabernathy; yocto@yoctoproject.org
>Subject: Re: [yocto] meta-cedartrail - serial console
>
>On 06/01/2012 11:03 AM, Bodke, Kishore K wrote:
>>
>>
>>> -Original Message-
>>> From: Hart, Darren
>>> Sent: Thursday, May 31, 2012 12:43 PM
>>> To: jfabernathy
>>> Cc: Bodke, Kishore K; yocto@yoctoproject.org
>>> Subject: Re: [yocto] meta-cedartrail - serial console
>>>
>>> On 05/31/2012 12:32 PM, jfabernathy wrote:
>>>> On 05/31/2012 02:18 PM, Bodke, Kishore K wrote:
>>>>>
>>>>>> -Original Message-
>>>>>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>>>>> boun...@yoctoproject.org] On Behalf Of jfabernathy
>>>>>> Sent: Thursday, May 31, 2012 9:12 AM
>>>>>> To: yocto@yoctoproject.org
>>>>>> Subject: [yocto] meta-cedartrail - serial console
>>>>>>
>>>>>> Using a DN2800MT (Marshalltown) Intel board, I'm testing the
>>>>>> meta-cedartrail using edison branch and noticed an issues with the
>>>>>> serial console.
>>>>>>
>>>>>> The cedartrail.conf in the machine directory has the following
>statements:
>>>>>>
>>>>>> SYSLINUX_OPTS = "serial 0 115200"
>>>>>> SERIAL_CONSOLE = "115200 ttyS0"
>>>>>> APPEND += "console=ttyS0,115200 console=tty0"
>>>>>>
>>>>> I just saw that Edison branch has ttyS3 enabled.
>>>>>
>>>>> SYSLINUX_OPTS = "serial 3 115200"
>>>>> SERIAL_CONSOLE = "115200 ttyS3"
>>>>> APPEND += "console=ttyS3,115200 console=tty3"
>>>>>
>>>>> Are you looking into right branch?
>>>>>
>>>>> Thanks
>>>>> -Kishore.
>>>>>
>>>>
>>>> So how do you get changes in the cedartrail.conf file to take affect??
>>>> I edited the file and did the bitbake again, but nothing changed.  I'm
>>>> guessing I need a bitbake -c cleansstate "somthing"  But I don't know
>>>> what to put there to make rebuild with ttyS0.
>>>>
>>>
>>> Ah yes, this rebuild is a bit frustrating. I believe it is the
>>> task_core* tasks you need to rebuild. bitbake -u depexp -g
>>> core-image-base (whatever your image is) will allow you to view which
>>> task_ tasks it is building, try cleansstate'ing those and rebuilding the
>>> image.
>>
>> I had to remove the above 3 lines from cedartrail.conf and
>> SERIAL_CONSOLE ?= "115200 ttyS0" line from conf/machine/include/ia32-
>base.inc
>> rebuild the image.
>> It is disabled now.
>
>Did you try with SERIAL_CONSOLE="" in cedartrail.conf ?

Yes. I tried this.  It is disabled.

I again added back in the grub.cfg, serial console hangs.

Thanks
Kishore.


>
>
>--
>Darren Hart
>Intel Open Source Technology Center
>Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] meta-cedartrail - serial console

[Bodke, Kishore K]

>-Original Message-
>From: Hart, Darren
>Sent: Friday, June 01, 2012 2:17 PM
>To: Bodke, Kishore K
>Cc: jfabernathy; yocto@yoctoproject.org
>Subject: Re: [yocto] meta-cedartrail - serial console
>
>On 06/01/2012 02:02 PM, Bodke, Kishore K wrote:
>>
>>
>>> -Original Message-
>>> From: Hart, Darren
>>> Sent: Friday, June 01, 2012 11:12 AM
>>> To: Bodke, Kishore K
>>> Cc: jfabernathy; yocto@yoctoproject.org
>>> Subject: Re: [yocto] meta-cedartrail - serial console
>>>
>>> On 06/01/2012 11:03 AM, Bodke, Kishore K wrote:
>>>>
>>>>
>>>>> -Original Message-
>>>>> From: Hart, Darren
>>>>> Sent: Thursday, May 31, 2012 12:43 PM
>>>>> To: jfabernathy
>>>>> Cc: Bodke, Kishore K; yocto@yoctoproject.org
>>>>> Subject: Re: [yocto] meta-cedartrail - serial console
>>>>>
>>>>> On 05/31/2012 12:32 PM, jfabernathy wrote:
>>>>>> On 05/31/2012 02:18 PM, Bodke, Kishore K wrote:
>>>>>>>
>>>>>>>> -Original Message-
>>>>>>>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>>>>>>> boun...@yoctoproject.org] On Behalf Of jfabernathy
>>>>>>>> Sent: Thursday, May 31, 2012 9:12 AM
>>>>>>>> To: yocto@yoctoproject.org
>>>>>>>> Subject: [yocto] meta-cedartrail - serial console
>>>>>>>>
>>>>>>>> Using a DN2800MT (Marshalltown) Intel board, I'm testing the
>>>>>>>> meta-cedartrail using edison branch and noticed an issues with the
>>>>>>>> serial console.
>>>>>>>>
>>>>>>>> The cedartrail.conf in the machine directory has the following
>>> statements:
>>>>>>>>
>>>>>>>> SYSLINUX_OPTS = "serial 0 115200"
>>>>>>>> SERIAL_CONSOLE = "115200 ttyS0"
>>>>>>>> APPEND += "console=ttyS0,115200 console=tty0"
>>>>>>>>
>>>>>>> I just saw that Edison branch has ttyS3 enabled.
>>>>>>>
>>>>>>> SYSLINUX_OPTS = "serial 3 115200"
>>>>>>> SERIAL_CONSOLE = "115200 ttyS3"
>>>>>>> APPEND += "console=ttyS3,115200 console=tty3"
>>>>>>>
>>>>>>> Are you looking into right branch?
>>>>>>>
>>>>>>> Thanks
>>>>>>> -Kishore.
>>>>>>>
>>>>>>
>>>>>> So how do you get changes in the cedartrail.conf file to take affect??
>>>>>> I edited the file and did the bitbake again, but nothing changed.  I'm
>>>>>> guessing I need a bitbake -c cleansstate "somthing"  But I don't know
>>>>>> what to put there to make rebuild with ttyS0.
>>>>>>
>>>>>
>>>>> Ah yes, this rebuild is a bit frustrating. I believe it is the
>>>>> task_core* tasks you need to rebuild. bitbake -u depexp -g
>>>>> core-image-base (whatever your image is) will allow you to view which
>>>>> task_ tasks it is building, try cleansstate'ing those and rebuilding the
>>>>> image.
>>>>
>>>> I had to remove the above 3 lines from cedartrail.conf and
>>>> SERIAL_CONSOLE ?= "115200 ttyS0" line from conf/machine/include/ia32-
>>> base.inc
>>>> rebuild the image.
>>>> It is disabled now.
>>>
>>> Did you try with SERIAL_CONSOLE="" in cedartrail.conf ?
>>
>> Yes. I tried this.  It is disabled.
>>
>
>Meaning you do not have to modify ia32-base.inc?

I removed the  SERIAL_CONSOLE ?= "115200 ttyS0" from ia32-base.inc too.

>
>> I again added back in the grub.cfg, serial console hangs.
>
>Added what back in grub.cfg?

I added back console=ttyS0,115200 console=tty0 to the grub.cfg file and 
rebooted 
to see if I can get the serial console back, but after below boot messages the 
serial
console hangs.

Freeing unused kernel memory: 496k freed
udev[77]: starting version 164
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (loop0): using internal journal
EXT3-fs (loop0): recovery complete
EXT3-fs (loop0): mounted filesystem with ordered data mode
udev[487]: starting version 164
NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth0: link is not ready
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)

>
>I thought you were disabling the serial port...

I wanted to enable and disable the serial console through grub.cfg file.

Thanks
Kishore.

>
>Where does the serial console hang? In grub? During boot? At the login
>prompt?
>
>
>
>--
>Darren Hart
>Intel Open Source Technology Center
>Yocto Project - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] grub-efi-native_1.99.bb fails in master branch

[Bodke, Kishore K]

Hi,

I see a build fail for grub-efi-native_1.99 recipe in master branch for 
Cedartrail BSP.


NOTE: package grub-efi-i586-native-1.99-r9: task do_compile: Started
ERROR: Function failed: do_compile (see 
/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/temp/log.do_compile.1788
 for further information)
ERROR: Logfile of failure stored in: 
/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/temp/log.do_compile.1788
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 12
| make  all-recursive
| make[1]: Entering directory 
`/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/grub-1.99'
| Making all in grub-core/gnulib
| make[2]: Entering directory 
`/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/grub-1.99/grub-core/gnulib'
| make  all-recursive
| make[3]: Entering directory 
`/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/grub-1.99/grub-core/gnulib'
| make[4]: Entering directory 
`/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/grub-1.99/grub-core/gnulib'
| make[4]: Nothing to be done for `all-am'.
| make[4]: Leaving directory 
`/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/grub-1.99/grub-core/gnulib'
| make[3]: Leaving directory 
`/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/grub-1.99/grub-core/gnulib'
| make[2]: Leaving directory 
`/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/grub-1.99/grub-core/gnulib'
| Making all in .
| make[2]: Entering directory 
`/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/grub-1.99'
| rm -f libgrubkern.a
| ar cru libgrubkern.a   util/libgrubkern_a-misc.o 
grub-core/kern/libgrubkern_a-command.o grub-core/kern/libgrubkern_a-device.o 
grub-core/kern/libgrubkern_a-disk.o grub-core/kern/emu/libgrubkern_a-getroot.o 
grub-core/kern/emu/libgrubkern_a-hostdisk.o 
grub-core/kern/emu/libgrubkern_a-misc.o grub-core/kern/emu/libgrubkern_a-mm.o 
grub-core/kern/libgrubkern_a-env.o grub-core/kern/libgrubkern_a-err.o 
grub-core/kern/libgrubkern_a-file.o grub-core/kern/libgrubkern_a-fs.o 
grub-core/kern/libgrubkern_a-list.o grub-core/kern/libgrubkern_a-misc.o 
grub-core/kern/libgrubkern_a-partition.o
| rm -f libgrubmods.a
| ar cru libgrubmods.a   grub-core/commands/libgrubmods_a-blocklist.o 
grub-core/commands/libgrubmods_a-extcmd.o grub-core/commands/libgrubmods_a-ls.o 
grub-core/disk/libgrubmods_a-dmraid_nvidia.o 
grub-core/disk/libgrubmods_a-loopback.o grub-core/disk/libgrubmods_a-lvm.o 
grub-core/disk/libgrubmods_a-mdraid_linux.o 
grub-core/disk/libgrubmods_a-mdraid1x_linux.o 
grub-core/disk/libgrubmods_a-raid5_recover.o 
grub-core/disk/libgrubmods_a-raid6_recover.o 
grub-core/disk/libgrubmods_a-raid.o grub-core/fs/libgrubmods_a-affs.o 
grub-core/fs/libgrubmods_a-afs_be.o grub-core/fs/libgrubmods_a-afs.o 
grub-core/fs/libgrubmods_a-befs_be.o grub-core/fs/libgrubmods_a-befs.o 
grub-core/fs/libgrubmods_a-btrfs.o grub-core/fs/libgrubmods_a-cpio.o 
grub-core/fs/libgrubmods_a-ext2.o grub-core/fs/libgrubmods_a-fat.o 
grub-core/fs/libgrubmods_a-fshelp.o grub-core/fs/libgrubmods_a-hfs.o 
grub-core/fs/libgrubmods_a-hfsplus.o grub-core/fs/libgrubmods_a-iso9660.o 
grub-core/fs/libgrubmods_a-jfs.o grub-core/fs/libgrubmods_a-minix.o 
grub-core/fs/libgrubmods_a-minix2.o grub-core/fs/libgrubmods_a-nilfs2.o 
grub-core/fs/libgrubmods_a-ntfs.o grub-core/fs/libgrubmods_a-ntfscomp.o 
grub-core/fs/libgrubmods_a-reiserfs.o grub-core/fs/libgrubmods_a-sfs.o 
grub-core/fs/libgrubmods_a-tar.o grub-core/fs/libgrubmods_a-udf.o 
grub-core/fs/libgrubmods_a-ufs2.o grub-core/fs/libgrubmods_a-ufs.o 
grub-core/fs/libgrubmods_a-xfs.o grub-core/fs/zfs/libgrubmods_a-zfs.o 
grub-core/fs/zfs/libgrubmods_a-zfs_lzjb.o 
grub-core/fs/zfs/libgrubmods_a-zfs_sha256.o 
grub-core/fs/zfs/libgrubmods_a-zfs_fletcher.o grub-core/lib/libgrubmods_a-arg.o 
grub-core/lib/libgrubmods_a-crypto.o grub-core/lib/libgrubmods_a-envblk.o 
grub-core/lib/libgrubmods_a-hexdump.o 
grub-core/lib/libgcrypt-grub/cipher/libgrubmods_a-sha512.o 
grub-core/lib/libgcrypt-grub/cipher/libgrubmods_a-crc.o 
grub-core/lib/libgrubmods_a-LzFind.o grub-core/lib/libgrubmods_a-LzmaEnc.o 
grub-core/lib/libgrubmods_a-pbkdf2.o grub-core/lib/libgrubmods_a-crc.o 
grub-core/normal/libgrubmods_a-datetime.o grub-core/normal/libgrubmods_a-misc.o 
grub-core/partmap/libgrubmods_a-acorn.o grub-core/partmap/libgrubmods_a-amiga.o 
grub-core/partmap/libgrubmods_a-apple.o grub-core/partmap/libgrubmods_a-gpt.o 
grub-core/partmap/libgrubmoERROR: Function failed: do_compile (see 
/usr/local/src/gst-master/build/tmp/work/x86_64-linux/grub-efi-i586-native-1.99-r9/temp/log.do_compile.1788
 for further information)
| ds_a-msdos.o grub-core/partmap/libgrubmods_a-sun.o 
grub-core/partmap/libgrubmods_a-sunpc.o 
grub-core/partmap/

[yocto] master build fail for Cedartrail

[Bodke, Kishore K]

Hi,

I get build failure for the master branch for the Cedartrail BSP.

Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| ERROR: Function failed: do_configure (see 
/usr/local/src/master-chrome/build/tmp/work/core2-poky-linux/cdv-pvr-driver-1.0-r1.1/temp/log.do_configure.6978
 for further information)
| rpm2cpio.real: signature.c:860: verifyDSA: Assertion `sigp->pubkey_algo == 
(rpmuint8_t)PGPPUBKEYALGO_DSA' failed.
| cpio: premature end of archive


I don't see this build fail in Denzil branch.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] master build fail for Cedartrail

[Bodke, Kishore K]

Hi Mark,

The rpm verions different in master and denzil.
This is causing the rpm2cpio failure in master.

Thanks
Kishore.


From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Bodke, Kishore K
Sent: Thursday, June 21, 2012 10:36 AM
To: yocto@yoctoproject.org
Subject: [yocto] master build fail for Cedartrail

Hi,

I get build failure for the master branch for the Cedartrail BSP.

Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| ERROR: Function failed: do_configure (see 
/usr/local/src/master-chrome/build/tmp/work/core2-poky-linux/cdv-pvr-driver-1.0-r1.1/temp/log.do_configure.6978
 for further information)
| rpm2cpio.real: signature.c:860: verifyDSA: Assertion `sigp->pubkey_algo == 
(rpmuint8_t)PGPPUBKEYALGO_DSA' failed.
| cpio: premature end of archive


I don't see this build fail in Denzil branch.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] UART test for Yocto

[Bodke, Kishore K]

Hi All,

Can we disable the serial console by deleting "console=tty0 
console=ttyS0,115200n8" from the grub.cfg?  Looks like it is not disabled.

I have been reported this issue for the Cedartrail serial port is always 
enabled regardless of serial console option in the grub.cfg.

Is this due to it is always enabled in cedartrail.conf file below, How do we 
make sure that serial port can be enabled or disabled by editing the grub.cfg?

SYSLINUX_OPTS = "serial 0 115200"
SERIAL_CONSOLE = "115200 ttyS0"
APPEND += "console=ttyS0,115200 console=tty0"

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Display issue with EFI BOOTING

[Bodke, Kishore K]

>-Original Message-
>From: Khem Raj [mailto:raj.k...@gmail.com]
>Sent: Friday, June 22, 2012 5:06 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; Darren Hart (dvh...@linux.intel.com)
>Subject: Re: [yocto] Display issue with EFI BOOTING
>
>On Fri, Jun 22, 2012 at 3:28 PM, Bodke, Kishore K
> wrote:
>> Hi,
>>
>>
>>
>> Yocto logo displays fines when booted with BIOS.
>>
>> But I see the Logo Display issue when booted with EFI.
>>
>> Attached are the screen shot.
>>
>> Any Idea why?
>>
>>
>
>may be screen refresh rate ? just shooting in dark here

Hi Darren,

Do you also see the Yocto logo distorted while booting with EFI?
I don't see this distorted logo with BIOS.

Thanks
Kishore.
>>
>> Thanks
>>
>> Kishore.
>>
>>
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] ERROR: QA Issue: Architecture did not match (62 to 3) for linux-yocto_3.2.bb

[Bodke, Kishore K]

Hi,

I am using local clone for 3.2 kernel and I get build fail for 
Linux-yocto_3.2.bb.

WARNING: For recipe linux-yocto, the following files/directories were installed 
but not shipped in any package:
WARNING:   /etc
ERROR: QA Issue: Architecture did not match (62 to 3) on 
/work/<>/linux-yocto-3.2.18+git1+20958298c233d15b1d705e7b0eb93282d6ecb5de_1+7d26ac083cb255888536b42b622b97fb438753ad-r1/packages-split/kernel-vmlinux/boot/vmlinux-3.2.18-yocto-standard
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa

Any idea why I get this?

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] ERROR: QA Issue: Architecture did not match (62 to 3) for linux-yocto_3.2.bb

[Bodke, Kishore K]

>-Original Message-
>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>Sent: Tuesday, July 17, 2012 5:21 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for linux-
>yocto_3.2.bb
>
>On 12-07-17 8:16 PM, Bodke, Kishore K wrote:
>> Hi,
>>
>> I am using local clone for 3.2 kernel and I get build fail for
>> Linux-yocto_3.2.bb.
>>
>> WARNING: For recipe linux-yocto, the following files/directories were
>> installed but not shipped in any package:
>>
>> WARNING: /etc
>>
>> ERROR: QA Issue: Architecture did not match (62 to 3) on
>> /work/<>/linux-yocto-
>3.2.18+git1+20958298c233d15b1d705e7b0eb93282d6ecb5de_1+7d26ac083cb2
>55888536b42b622b97fb438753ad-r1/packages-split/kernel-
>vmlinux/boot/vmlinux-3.2.18-yocto-standard
>>
>> ERROR: QA run found fatal errors. Please consider fixing them.
>>
>> ERROR: Function failed: do_package_qa
>>
>> Any idea why I get this?
>
>It means you've managed to get a 32 bit object in a 64 bit build.
>Have you tweaked the configuration ?

I have not edited any configuration.  I am using all 64 bit only.

>
>Cheers,
>
>Bruce
>
>>
>> Thanks
>>
>> Kishore.
>>

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

Re: [yocto] ERROR: QA Issue: Architecture did not match (62 to 3) for linux-yocto_3.2.bb

[Bodke, Kishore K]

>-Original Message-
>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>Sent: Tuesday, July 17, 2012 5:30 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; Zanussi, Tom; Darren Hart
>Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for linux-
>yocto_3.2.bb
>
>On 12-07-17 8:25 PM, Bodke, Kishore K wrote:
>>
>>
>>> -Original Message-
>>> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>>> Sent: Tuesday, July 17, 2012 5:21 PM
>>> To: Bodke, Kishore K
>>> Cc: yocto@yoctoproject.org
>>> Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for
>linux-
>>> yocto_3.2.bb
>>>
>>> On 12-07-17 8:16 PM, Bodke, Kishore K wrote:
>>>> Hi,
>>>>
>>>> I am using local clone for 3.2 kernel and I get build fail for
>>>> Linux-yocto_3.2.bb.
>>>>
>>>> WARNING: For recipe linux-yocto, the following files/directories were
>>>> installed but not shipped in any package:
>>>>
>>>> WARNING: /etc
>>>>
>>>> ERROR: QA Issue: Architecture did not match (62 to 3) on
>>>> /work/<>/linux-yocto-
>>>
>3.2.18+git1+20958298c233d15b1d705e7b0eb93282d6ecb5de_1+7d26ac083cb2
>>> 55888536b42b622b97fb438753ad-r1/packages-split/kernel-
>>> vmlinux/boot/vmlinux-3.2.18-yocto-standard
>>>>
>>>> ERROR: QA run found fatal errors. Please consider fixing them.
>>>>
>>>> ERROR: Function failed: do_package_qa
>>>>
>>>> Any idea why I get this?
>>>
>>> It means you've managed to get a 32 bit object in a 64 bit build.
>>> Have you tweaked the configuration ?
>>
>> I have not edited any configuration.  I am using all 64 bit only.
>
>Can anyone else confirm this ? What BSP is this ? either it isn't
>listed above .. or I missed it. Tom ? Darren ? I don't have a build
>handy to check.

I am building a new BSP which is not listed here.  That is the reason I am 
using local clone.
I cloned 3.2 kernel and created a new BSP based on ROMLEY.

Thanks
Kishore.

>
>I can start a build overnight to try and see what is happening, if you
>send the details about what you are building here.
>
>Cheers,
>
>Bruce
>
>>
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Thanks
>>>>
>>>> Kishore.
>>>>
>>

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

Re: [yocto] ERROR: QA Issue: Architecture did not match (62 to 3) for linux-yocto_3.2.bb

[Bodke, Kishore K]

>-Original Message-
>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>Sent: Tuesday, July 17, 2012 5:35 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; Zanussi, Tom; Darren Hart
>Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for linux-
>yocto_3.2.bb
>
>On 12-07-17 8:32 PM, Bodke, Kishore K wrote:
>>
>>
>>> -Original Message-
>>> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>>> Sent: Tuesday, July 17, 2012 5:30 PM
>>> To: Bodke, Kishore K
>>> Cc: yocto@yoctoproject.org; Zanussi, Tom; Darren Hart
>>> Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for
>linux-
>>> yocto_3.2.bb
>>>
>>> On 12-07-17 8:25 PM, Bodke, Kishore K wrote:
>>>>
>>>>
>>>>> -Original Message-
>>>>> From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>>>>> Sent: Tuesday, July 17, 2012 5:21 PM
>>>>> To: Bodke, Kishore K
>>>>> Cc: yocto@yoctoproject.org
>>>>> Subject: Re: ERROR: QA Issue: Architecture did not match (62 to 3) for
>>> linux-
>>>>> yocto_3.2.bb
>>>>>
>>>>> On 12-07-17 8:16 PM, Bodke, Kishore K wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I am using local clone for 3.2 kernel and I get build fail for
>>>>>> Linux-yocto_3.2.bb.
>>>>>>
>>>>>> WARNING: For recipe linux-yocto, the following files/directories were
>>>>>> installed but not shipped in any package:
>>>>>>
>>>>>> WARNING: /etc
>>>>>>
>>>>>> ERROR: QA Issue: Architecture did not match (62 to 3) on
>>>>>> /work/<>/linux-yocto-
>>>>>
>>>
>3.2.18+git1+20958298c233d15b1d705e7b0eb93282d6ecb5de_1+7d26ac083cb2
>>>>> 55888536b42b622b97fb438753ad-r1/packages-split/kernel-
>>>>> vmlinux/boot/vmlinux-3.2.18-yocto-standard
>>>>>>
>>>>>> ERROR: QA run found fatal errors. Please consider fixing them.
>>>>>>
>>>>>> ERROR: Function failed: do_package_qa
>>>>>>
>>>>>> Any idea why I get this?
>>>>>
>>>>> It means you've managed to get a 32 bit object in a 64 bit build.
>>>>> Have you tweaked the configuration ?
>>>>
>>>> I have not edited any configuration.  I am using all 64 bit only.
>>>
>>> Can anyone else confirm this ? What BSP is this ? either it isn't
>>> listed above .. or I missed it. Tom ? Darren ? I don't have a build
>>> handy to check.
>>
>> I am building a new BSP which is not listed here.  That is the reason I am
>using local clone.
>> I cloned 3.2 kernel and created a new BSP based on ROMLEY.
>
>Without seeing your configuration, I can't say more. It looks like the
>tuning for userspace is 64 and you've built a 32 bit kernel, or vice
>versa.

I tried rebuilding from scratch. It built fine.
Not sure why it failed for the first time, Though it was the same 
configurations settings I had.

Thanks
Kishore.

>
>Darren/Tom may be able to help more.
>
>Cheers,
>
>Bruce
>
>>
>> Thanks
>> Kishore.
>>
>>>
>>> I can start a build overnight to try and see what is happening, if you
>>> send the details about what you are building here.
>>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Bruce
>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Kishore.
>>>>>>
>>>>
>>

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

[yocto] How to set environment variables inside a recipe?

[Bodke, Kishore K]

Hi,

I am writing a recipe to build a driver specific for  my BSP.

The driver needs a bunch of environmental variables to be set ( specific to 
driver only ) to build.

Right now to move forward I am doing like below in my recipe to build it.

export  AAA = "${S}"
export BBB = "${B}"
export CCC = "{S}/build-system"
export DDD = "{S}/env-files"

Is this right way to do?  Are there any other ways to set the environment 
variables inside a recipe?

Any suggestions would be helpful.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to set environment variables inside a recipe?

[Bodke, Kishore K]

>-Original Message-
>From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
>Sent: Friday, July 20, 2012 3:14 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] How to set environment variables inside a recipe?
>
>On Thursday 19 July 2012 18:16:45 Bodke, Kishore K wrote:
>> The driver needs a bunch of environmental variables to be set ( specific to
>> driver only ) to build.
>>
>> Right now to move forward I am doing like below in my recipe to build it.
>>
>> export  AAA = "${S}"
>> export BBB = "${B}"
>> export CCC = "{S}/build-system"
>> export DDD = "{S}/env-files"
>>
>> Is this right way to do?  Are there any other ways to set the environment
>> variables inside a recipe?
>
>This is valid; I would recommend setting them within the function though (e.g.
>do_configure) rather than at the recipe level, assuming that works for your
>case.

If I set outside the do_configure it builds fine. 
But If I do inside 
do_confiugre() {
 export  AAA = "${S}"
 export BBB = "${B}"
 export CCC = "{S}/build-system"
 export DDD = "{S}/env-files"
}

run.do_configure.20832: line 78: export: `=': not a valid identifier
NOTE: task do_configure: Failed

Is the syntax wrong here? What is the correct syntax?

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to set environment variables inside a recipe?

[Bodke, Kishore K]

>-Original Message-
>From: Robert P. J. Day [mailto:rpj...@crashcourse.ca]
>Sent: Friday, July 20, 2012 10:13 AM
>To: Bodke, Kishore K
>Cc: Paul Eggleton; yocto@yoctoproject.org
>Subject: Re: [yocto] How to set environment variables inside a recipe?
>
>On Fri, 20 Jul 2012, Bodke, Kishore K wrote:
>
>>
>>
>> >-Original Message-
>> >From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
>> >Sent: Friday, July 20, 2012 3:14 AM
>> >To: Bodke, Kishore K
>> >Cc: yocto@yoctoproject.org
>> >Subject: Re: [yocto] How to set environment variables inside a recipe?
>> >
>> >On Thursday 19 July 2012 18:16:45 Bodke, Kishore K wrote:
>> >> The driver needs a bunch of environmental variables to be set ( specific
>to
>> >> driver only ) to build.
>> >>
>> >> Right now to move forward I am doing like below in my recipe to build it.
>> >>
>> >> export  AAA = "${S}"
>> >> export BBB = "${B}"
>> >> export CCC = "{S}/build-system"
>> >> export DDD = "{S}/env-files"
>> >>
>> >> Is this right way to do?  Are there any other ways to set the environment
>> >> variables inside a recipe?
>> >
>> >This is valid; I would recommend setting them within the function though
>(e.g.
>> >do_configure) rather than at the recipe level, assuming that works for your
>> >case.
>>
>> If I set outside the do_configure it builds fine.
>> But If I do inside
>> do_confiugre() {
>>  export  AAA = "${S}"
>>  export BBB = "${B}"
>>  export CCC = "{S}/build-system"
>>  export DDD = "{S}/env-files"
>> }
>>
>> run.do_configure.20832: line 78: export: `=': not a valid identifier
>> NOTE: task do_configure: Failed
>
>  pretty sure you can't have spaces around the "=".

Yes, the spaces was an issue. 
Works fine now.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] ERROR: Function failed: do_install_perf

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Tom Zanussi
>Sent: Friday, July 20, 2012 7:20 PM
>To: Saxena, Rahul
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] ERROR: Function failed: do_install_perf
>
>On Sat, 2012-07-21 at 00:02 +, Saxena, Rahul wrote:
>> Hi,
>>
>>
>>
>> I suddenly started to get the following error when  running bitbake. I
>> am using Denzil branches of poky, meta-intel and poky-extras. I
>> installed libper-dev as suggested by the error message, but it made no
>> difference.
>>
>>
>>
>> Any suggestions ?
>>
>I think the meta-kernel-dev with denzil is causing the problem i.e the
>AUTOREV is causing the tip of linux-yocto-3.0 to get picked up.  So just
>removing poky-extras from your layers should fix the problem.

Is there any work around if we want to use meta-kernel-dev with denzil?
I see the same issue now with these combination on Linux-yocto-3.2 as well.

Thanks
Kishore.

>
>Using the meta-kernel-dev AUTOREV with master should be fine though, and
>in fact I did update the cedartrail SRCREVs in master to catch the perf
>updates in linux-yocto-3.0, so advancing them won't hurt anything.  I
>guess master is where you want to make new kernel changes anyway...
>
>Tom
>
>>
>>
>> Thanks
>>
>> Rahul
>>
>>
>>
>> ERROR: Function failed: do_install_perf
>> (see /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-
>poky-linux/linux-yocto-
>3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff
>37916828dc8b4ef72f5d35a94-r4/temp/log.do_install_perf.69672 for further
>information)
>>
>> NOTE: make
>> -C /home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-
>linux/linux-yocto-
>3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff
>37916828dc8b4ef72f5d35a94-r4/linux/tools/perf CC=i586-poky-linux-gcc  -m32
>-march=core2 -msse3 -mtune=generic -mfpmath=sse --
>sysroot=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/cedartrail
>LD=i586-poky-linux-ld --
>sysroot=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/sysroots/cedartrail
>prefix=/usr
>DESTDIR=/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-
>poky-linux/linux-yocto-
>3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff
>37916828dc8b4ef72f5d35a94-r4/image install NO_NEWT=1 NO_DWARF=1
>>
>> make: Entering directory
>> `/home/rsaxena/YoctoWork3x/cedartraiv12p/tmp/work/cedartrail-poky-
>linux/linux-yocto-
>3.0.32+git1+46e8fc2bbbe73514e8d99101adaaa373f760ffa7_1+81fd8c307997aff
>37916828dc8b4ef72f5d35a94-r4/linux/tools/perf'
>>
>> Makefile:484: libperl not found, disables Perl scripting support.
>> Please install libperl-dev or perl-devel
>>
>> * new build flags or prefix
>>
>> CC perf.o
>>
>> CC builtin-annotate.o
>>
>> CC builtin-bench.o
>>
>> CC bench/sched-messaging.o
>>
>> CC bench/sched-pipe.o
>>
>> CC bench/mem-memcpy.o
>>
>> CC builtin-diff.o
>>
>> CC builtin-evlist.o
>>
>> CC builtin-help.o
>>
>> CC builtin-sched.o
>>
>> CC builtin-buildid-list.o
>>
>> CC builtin-buildid-cache.o
>>
>> CC builtin-list.o
>>
>> CC builtin-record.o
>>
>> CC builtin-report.o
>>
>> CC builtin-stat.o
>>
>> CC builtin-timechart.o
>>
>> CC builtin-top.o
>>
>> CC builtin-script.o
>>
>> CC builtin-probe.o
>>
>> CC builtin-kmem.o
>>
>> CC builtin-lock.o
>>
>> CC builtin-kvm.o
>>
>> CC builtin-test.o
>>
>> CC builtin-inject.o
>>
>> CC util/abspath.o
>>
>> CC util/alias.o
>>
>> CC util/annotate.o
>>
>> CC util/build-id.o
>>
>> CC util/config.o
>>
>> CC util/ctype.o
>>
>> CC util/debugfs.o
>>
>> CC util/environment.o
>>
>> CC util/event.o
>>
>> CC util/evlist.o
>>
>> CC util/evsel.o
>>
>> CC util/exec_cmd.o
>>
>> CC util/help.o
>>
>> CC util/levenshtein.o
>>
>> CC util/parse-options.o
>>
>> CC util/parse-events.o
>>
>> CC util/path.o
>>
>> CC util/rbtree.o
>>
>> CC util/bitmap.o
>>
>> CC util/hweight.o
>>
>> CC util/run-command.o
>>
>> CC util/quote.o
>>
>> CC util/strbuf.o
>>
>> CC util/string.o
>>
>> CC util/strlist.o
>>
>> CC util/strfilter.o
>>
>> CC util/top.o
>>
>> CC util/usage.o
>>
>> CC util/wrapper.o
>>
>> CC util/sigchain.o
>>
>> CC util/symbol.o
>>
>> CC util/color.o
>>
>> CC util/pager.o
>>
>> CC util/header.o
>>
>> CC util/callchain.o
>>
>> CC util/values.o
>>
>> CC util/debug.o
>>
>> CC util/map.o
>>
>> CC util/pstack.o
>>
>> CC util/session.o
>>
>> CC util/thread.o
>>
>> CC util/thread_map.o
>>
>> CC util/trace-event-parse.o
>>
>> CC util/trace-event-read.o
>>
>> CC util/trace-event-info.o
>>
>> CC util/trace-event-scripting.o
>>
>> CC util/svghelper.o
>>
>> CC util/sort.o
>>
>> CC util/hist.o
>>
>> CC util/probe-event.o
>>
>> CC util/util.o
>>
>> CC util/xyarray.o
>>
>> CC util/cp

[yocto] ERROR: install: omitting directory

[Bodke, Kishore K]

Hi,

I have a recipe wherein I am trying to put all the Yocto built files of my 
driver into the final Image like below.

B = "${WORKDIR}/build-${TARGET_SYS}"

FILES_${PN} += "/mydriver_build/*"

install -m 0755 -d ${D}/mydriver_build
for bin_obj in ${B};
do
install -D -m 640 $bin_obj ${D}/mydriver_build/
done

But I get the below error.

Log data follows:
| DEBUG: Executing shell function do_install
| install: omitting directory 
`/usr/local/src/master/build/tmp/work/x86_64-poky-linux/my-driver-1.0-r12/build-x86_64-poky-linux'
| ERROR: Function failed: do_install (see 
/usr/local/src/master/build/tmp/work/x86_64-poky-linux/my-driver-1.0-r12/temp/log.do_install.952
 for further information)
NOTE: package my-driver-1.0-r12: task do_install: Failed.

What is the error means?  Anything wrong in the recipe above?
Any suggestions please?

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] INSANE_SKIP

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Dallas Clement
>Sent: Friday, July 20, 2012 3:07 PM
>To: yocto@yoctoproject.org
>Subject: [yocto] INSANE_SKIP
>
>Is there a way to skip a QA check for more than one package or all packages?
>
>I'd like to avoid having to add a INSANE_SKIP_${PN} += "ldflags" for
>every package that fails due to ERROR: QA Issue: No GNU_HASH in the
>elf binary.
>
>There are gobs of python and perl packages failing with this error
>when I try to build a distro.

Try exporting the below line before compiling with this works I guess.
export LD="${LD} --hash-style=gnu" 

-Kishore.

>___
>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: [yocto] [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created.

[Bodke, Kishore K]

>-Original Message-
>From: Darren Hart [mailto:dvh...@linux.intel.com]
>Sent: Wednesday, August 01, 2012 3:58 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; bruce.ashfi...@windriver.com
>Subject: Re: [yocto] [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine
>Created.
>
>Hi Kishore,
>
>On 08/01/2012 12:15 PM, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke 
>>
>> Initial checkin for the new Crystal Forest Machine Branch.
>>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  .../bsp/crystalforest/crystalforest-preempt-rt.scc |   15 +
>>  .../bsp/crystalforest/crystalforest-standard.scc   |   10 
>>  .../bsp/crystalforest/crystalforest.cfg|   63 
>> 
>>  .../bsp/crystalforest/crystalforest.scc|   14 +
>>  4 files changed, 102 insertions(+)
>>  create mode 100644 meta/cfg/kernel-
>cache/bsp/crystalforest/crystalforest-preempt-rt.scc
>>  create mode 100644 meta/cfg/kernel-
>cache/bsp/crystalforest/crystalforest-standard.scc
>>  create mode 100644 meta/cfg/kernel-
>cache/bsp/crystalforest/crystalforest.cfg
>>  create mode 100644 meta/cfg/kernel-
>cache/bsp/crystalforest/crystalforest.scc
>>
>> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-
>rt.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-
>rt.scc
>> new file mode 100644
>> index 000..6c250af
>> --- /dev/null
>> +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-preempt-
>rt.scc
>> @@ -0,0 +1,15 @@
>> +define KMACHINE crystalforest
>> +define KTYPE preempt-rt
>> +define KARCH x86_64
>> +
>> +# no new branch required, re-use the ktypes/preempt-rt branch
>> +include ktypes/preempt-rt
>> +include bsp/common-pc-64/common-pc-64.scc
>> +
>> +include crystalforest.scc
>> +
>> +# default policy for preempt-rt kernels
>> +include cfg/usb-mass-storage.scc
>> +include cfg/boot-live.scc
>> +include features/latencytop/latencytop.scc
>> +include features/profiling/profiling.scc
>> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-
>standard.scc b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-
>standard.scc
>> new file mode 100644
>> index 000..9d24c76
>> --- /dev/null
>> +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest-standard.scc
>> @@ -0,0 +1,10 @@
>> +define KMACHINE crystalforest
>> +define KTYPE standard
>> +define KARCH x86_64
>> +
>> +include bsp/common-pc-64/common-pc-64-standard
>> +branch crystalforest
>> +
>> +include crystalforest.scc
>> +
>> +# default policy for standard kernels
>> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg
>b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg
>> new file mode 100644
>> index 000..341cc20
>> --- /dev/null
>> +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.cfg
>> @@ -0,0 +1,63 @@
>> +CONFIG_PRINTK=y
>> +
>> +# Basic hardware support for the box - network, USB, PCI, sound
>> +CONFIG_NETDEVICES=y
>> +CONFIG_ATA=y
>> +CONFIG_ATA_GENERIC=y
>> +CONFIG_ATA_SFF=y
>> +CONFIG_PCI=y
>> +CONFIG_MMC=y
>> +CONFIG_MMC_SDHCI=y
>> +CONFIG_USB_SUPPORT=y
>> +CONFIG_USB=y
>
>USB support should be pulled in using the various usb scc files Tom
>created relatively recently.
>
>> +CONFIG_USB_ARCH_HAS_EHCI=y
>> +CONFIG_R8169=y
>> +CONFIG_PATA_SCH=y
>> +CONFIG_MMC_SDHCI_PCI=y
>> +CONFIG_USB_EHCI_HCD=y
>> +CONFIG_PCIEPORTBUS=y
>> +CONFIG_NET=y
>> +CONFIG_USB_UHCI_HCD=y
>> +CONFIG_BLK_DEV_SD=y
>> +CONFIG_CHR_DEV_SG=y
>> +CONFIG_SOUND=y
>> +CONFIG_SND=y
>> +CONFIG_SND_HDA_INTEL=y
>> +
>> +# Make sure these are on, otherwise the bootup won't be fun
>> +CONFIG_UNIX=y
>> +CONFIG_INET=y
>> +CONFIG_MODULES=y
>> +CONFIG_SHMEM=y
>> +CONFIG_TMPFS=y
>> +CONFIG_PACKET=y
>> +
>> +# These are needed for the Poulsbo kernel modules
>> +CONFIG_I2C=y
>> +CONFIG_AGP=y
>> +CONFIG_VFAT_FS=y
>
>VFAT_FS is required for Poulsbo kernel modules?
>
>This would make more sense as a poulsbo.scc and .cfg file.
>
>> +CONFIG_PM=y
>> +CONFIG_FB=y
>> +CONFIG_BACKLIGHT_LCD_SUPPORT=y
>> +CONFIG_BACKLIGHT_CLASS_DEVICE=y
>> +CONFIG_INPUT=y
>> +CONFIG_VIDEO_V4L2=y
>> +CONFIG_VIDEO_IVTV=y
>> +CONFIG_MEDIA_SUPPORT=y
>> +CONFIG_VIDEO_CAPTURE_DRIVERS=y
>> +CONFIG_VIDEO_DEV=y
>> +CONFIG_VIDEO_V4L2_COMMON=y
>> +CONFIG_I2C_ALG

Re: [yocto] [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created.

[Bodke, Kishore K]

>-Original Message-
>From: Darren Hart [mailto:dvh...@linux.intel.com]
>Sent: Thursday, August 02, 2012 1:00 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; bruce.ashfi...@windriver.com
>Subject: Re: [PATCH 1/1] [KERNEL] meta: Crystal Forest Machine Created.
>
>Looks a lot better. One question still pending from my previous review
>though:
>
>On 08/02/2012 11:35 AM, kishore.k.bo...@intel.com wrote:
>
>> diff --git a/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc
>b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc
>> new file mode 100644
>> index 000..140a4d5
>> --- /dev/null
>> +++ b/meta/cfg/kernel-cache/bsp/crystalforest/crystalforest.scc
>> @@ -0,0 +1,23 @@
>> +kconf hardware crystalforest.cfg
>> +
>> +include cfg/x86_64.scc
>> +include cfg/8250.scc
>> +
>> +include features/i915/i915.scc
>
>Is this (i915) required for the Poulsbo graphics?

I am not quite sure on this.

Thanks
Kishore.

>
>--
>Darren Hart
>Intel Open Source Technology Center
>Yocto Project - Technical Lead - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch

[Bodke, Kishore K]

>-Original Message-
>From: Darren Hart [mailto:dvh...@linux.intel.com]
>Sent: Friday, August 03, 2012 8:56 AM
>To: Bruce Ashfield
>Cc: Bodke, Kishore K; yocto@yoctoproject.org
>Subject: Re: [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch
>
>
>
>On 08/03/2012 08:26 AM, Bruce Ashfield wrote:
>> On 12-08-02 02:35 PM, kishore.k.bo...@intel.com wrote:
>>> From: Kishore Bodke
>>>
>>> Hi,
>>>
>>> This is a revised patch set is for creating the new Crystal Forest Machine.
>>> Crystal Forest Machine is Sandybridge CPU with Cave Creek Chipset.
>>>
>>> This machine is based on standard/default/common-pc-64.
>>>
>>> Please create a new branch called standard/default/common-pc-
>64/crystalforest
>>> for linux-yocto-3.4 kernel and push this new meta branch.
>>
>> I'd rather not push this out right on the M3 pull request deadline,
>> but there is very little risk to it .. so I'm not really opinionated
>> on it.
>>
>> Can this wait a few days, or do we want/need it in M3 ?
>
>
>Kishore still needs to address the i915 question.


Hi Bruce,

This could wait until after M3, if it has to.  

Hi Darren,

I have no idea if i915 is needed, I just derived from Romley since this is 
close to it.
I can try without this feature, but I would still keep it until I test with all 
the 4 different versions of Crystal Forest Boards and remove it if it is not 
needed.

Thanks
Kishore.

>
>--
>Darren
>
>>
>> Cheers,
>>
>> Bruce
>>
>>>
>>> Thanks
>>> Kishore.
>>>
>>> The following changes since commit
>459165c1dd61c4e843c36e6a1abeb30949a20ba7:
>>>
>>>kconf: add 8250 Kconfig to hardware listing audit (2012-07-26 16:23:26 -
>0400)
>>>
>>> are available in the git repository at:
>>>
>>>git://git.pokylinux.org/linux-yocto-2.6.37-contrib kishore/meta-
>crystalforest
>>>http://git.pokylinux.org/cgit.cgi/linux-yocto-2.6.37-
>contrib/log/?h=kishore/meta-crystalforest
>>>
>>> Kishore Bodke (1):
>>>meta: Crystal Forest Machine Created.
>>>
>>>   .../bsp/crystalforest/crystalforest-preempt-rt.scc |9 ++
>>>   .../bsp/crystalforest/crystalforest-standard.scc   |8 +
>>>   .../bsp/crystalforest/crystalforest.cfg|   32
>
>>>   .../bsp/crystalforest/crystalforest.scc|   23 ++
>>>   4 files changed, 72 insertions(+)
>>>   create mode 100644 meta/cfg/kernel-
>cache/bsp/crystalforest/crystalforest-preempt-rt.scc
>>>   create mode 100644 meta/cfg/kernel-
>cache/bsp/crystalforest/crystalforest-standard.scc
>>>   create mode 100644 meta/cfg/kernel-
>cache/bsp/crystalforest/crystalforest.cfg
>>>   create mode 100644 meta/cfg/kernel-
>cache/bsp/crystalforest/crystalforest.scc
>>>
>>
>
>--
>Darren Hart
>Intel Open Source Technology Center
>Yocto Project - Technical Lead - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch

[Bodke, Kishore K]

>-Original Message-
>From: Darren Hart [mailto:dvh...@linux.intel.com]
>Sent: Wednesday, August 08, 2012 11:14 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; bruce.ashfi...@windriver.com
>Subject: Re: [PATCH 0/1] [KERNEL] meta: New Crystal Forest Machine Branch
>
>n 08/08/2012 10:56 AM, kishore.k.bo...@intel.com wrote:
>> From: Kishore Bodke 
>>
>> Hi,
>>
>> This is a revised patch set is for creating the new Crystal Forest Machine.
>> Crystal Forest Machine is Sandybridge CPU with Cave Creek Chipset.
>>
>> This machine is based on standard/default/common-pc-64.
>>
>> Please create a new branch called standard/default/common-pc-
>64/crystalforest
>> for linux-yocto-3.4 kernel and pull this new meta branch.
>>
>> Thanks
>> Kishore.
>
>Hi Kishore, please note that as these patches are for the linux-yocto
>sources, they should be sent to the linux-yocto mailing list:
>
>https://lists.yoctoproject.org/listinfo/linux-yocto
>
>This is a relatively new list, please keep it in mind for the future.

Hi Darren,

Thanks for letting me know this.
A quick question.
Do we need to send all the kernel related patches only to Linux-yocto mailing 
list or to both Linux-yocto and Yocto mailing list too?

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 1/1] meta-cedartrail: fixed PREFERRED_VERSION_linux-yocto

[Bodke, Kishore K]

>-Original Message-
>From: Mihai Lindner [mailto:mihaix.lind...@linux.intel.com]
>Sent: Friday, August 17, 2012 8:54 AM
>To: yocto@yoctoproject.org; Bodke, Kishore K
>Subject: [PATCH 1/1] meta-cedartrail: fixed PREFERRED_VERSION_linux-yocto
>
>Missing PREFERRED_VERSION_linux-yocto generated NOTEs when building.
>"""
>NOTE: preferred version 3.4% of linux-yocto not available (for item
>virtual/kernel)
>"""

Acked-by: Kishore Bodke 

>
>[YOCTO #2962]
>
>Signed-off-by: Mihai Lindner 
>---
> meta-cedartrail/conf/machine/cedartrail.conf |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
>diff --git a/meta-cedartrail/conf/machine/cedartrail.conf b/meta-
>cedartrail/conf/machine/cedartrail.conf
>index dbd7d95..d6e7a57 100644
>--- a/meta-cedartrail/conf/machine/cedartrail.conf
>+++ b/meta-cedartrail/conf/machine/cedartrail.conf
>@@ -13,6 +13,7 @@ XSERVER ?= "${XSERVER_IA32_BASE} \
>${XSERVER_IA32_EXT} \
>cdv-pvr-driver \
>"
>+PREFERRED_VERSION_linux-yocto ?= "3.0%"
> PREFERRED_VERSION_xserver-xorg ?= "1.9.3"
> PREFERRED_VERSION_mesa-dri ?= "7.11"
> PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0"
>--
>1.7.8.6

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

Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0 kernel ?

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Bruce Ashfield
>Sent: Wednesday, August 29, 2012 10:47 AM
>To: Hart, Darren
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] Poky 1.3_M3 branch does not work with linux-yocto 3.0
>kernel ?
>
>On Tue, Aug 28, 2012 at 3:34 PM, Darren Hart  wrote:
>> On 08/27/2012 08:18 PM, Bruce Ashfield wrote:
>>> On 12-08-27 8:14 PM, Saxena, Rahul wrote:
 Hi,

 I am building a BSP (meta-cedartrail) using 1.3 M3 branch of Poky.

 When I try to boot a image such as core-image-sato, I get kernel panic
 and errors such as:

 VFS: Cannot open root device "ram0" or unkown-block(0,0)

 Please append a correct "root=" boot option; here are the available

 partitions:

 VFS: unable to mount root fs on unknown block(0,0)

 User configuration error - no valid rootfilesystem found

 I do see that the root file system exists in
 cedartrail-poky-linux/core-image-sato-1.0-r0/rootfs dir..

 I did not see this problem when I uses a earlier commit of the Poky
 master branch.

 It seems like something broke with 1.3 M3 branch that prevents a proper
 build with 3.0 kernel. I do need to build my BSP with 3.0 kernel.

 (I was also told by Laurentiu Serban that 1.3 M3 Full Pass testing does
 not include testing with the 3.0 kernel)

 Any suggestions would be most welcome. I do need to build my BSP with
 the 3.0 kernel.
>>>
>>> Hmm. It should work, I booted one not that long ago. Can you force
>>> qemux86 to prefer the 3.0 kernel and see if that boots ? That would
>>> at least start to isolate the potential problem areas.
>>
>> However, won't 3.0 be removed for the 1.3 release? Keeping with 3.4 and
>3.2?
>
>For 1.3 the 3 kernel sliding window plan was 3.4, 3.2 and 3.0 with 2.6.37 being
>voted off the island. Or did you mean 1.4 ? Regardless, anything using 3.0
>needs
>to be updated since it's time is running short! :)
>

Cedartrail BSP has PVR Graphics drivers which works only with 3.0 Kernel.

Thanks
Kishore.
>Cheers,
>
>Bruce
>
>>
>> --
>> Darren
>>
>>>
>>> Bruce
>>>

 Thanks

 Rahul

>>>
>>
>>
>> --
>> Darren Hart
>> Intel Open Source Technology Center
>> Yocto Project - Linux Kernel
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>--
>"Thou shalt not follow the NULL pointer, for chaos and madness await
>thee at its end"
>___
>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: [yocto] [PATCH 0/1] Fix X issue on crownbay

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Kamble, Nitin A
>Sent: Wednesday, September 12, 2012 1:14 PM
>To: Zanussi, Tom
>Cc: Hart, Darren; yocto@yoctoproject.org
>Subject: Re: [yocto] [PATCH 0/1] Fix X issue on crownbay
>
>FYI While testing on the fishriver platform, I also find that there is no X 
>log, and
>looking further found out that xorg executable is not on the image. I think the
>same thing is also happening on crownbay.

FYI.. I also see the similar issue for Romley.  
There is no Xlog and X does not comes up.

Thanks
Kishore.

>
>Nitin
>
>
>
>> -Original Message-
>> From: Kamble, Nitin A
>> Sent: Wednesday, September 12, 2012 9:18 AM
>> To: Zanussi, Tom
>> Cc: Hart, Darren; yocto@yoctoproject.org
>> Subject: RE: [PATCH 0/1] Fix X issue on crownbay
>>
>> Hi Tom,
>>   Thanks for looking into the matter. I will try to reproduce the issue you 
>> are
>> seeing with master. And send another pull request with all the fixes.
>>
>> Regards,
>> Nitin
>>
>>
>> > -Original Message-
>> > From: Zanussi, Tom
>> > Sent: Monday, September 10, 2012 4:34 PM
>> > To: Kamble, Nitin A
>> > Cc: Hart, Darren; yocto@yoctoproject.org
>> > Subject: Re: [PATCH 0/1] Fix X issue on crownbay
>> >
>> > On Wed, 2012-09-05 at 17:59 -0700, nitin.a.kam...@intel.com wrote:
>> > > From: Nitin A Kamble 
>> > >
>> > > The following changes since commit
>> > 66b516f3d3a287eecbf8804b2221bfc27e36db63:
>> > >
>> > >   README: add info explaining meta-tlk layer purpose (2012-09-06
>> > > 10:36:02 -0500)
>> > >
>> > > are available in the git repository at:
>> > >   git://git.yoctoproject.org/meta-intel-contrib nitin/work
>> > >
>> > > http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin
>> > > /w
>> > > ork
>> > >
>> >
>> > I built and tried this, but it still didn't boot into X, and now
>> > there's not even an Xorg.log to look at:
>> >
>> > root@crownbay:/var/log# ls -al
>> > drwxr-xr-x2 root root80 Sep 10 20:15 .
>> > drwxrwxrwt7 root root   140 Jan  6  2009 ..
>> > -rw-r--r--1 root root 78429 Sep 10 20:17 messages
>> > -rw-rw-r--1 root root  4224 Sep 10 20:17 wtmp
>> >
>> > I assume this is a different X problem related to recent changes in mater.
>> > Can you update the bug report with the commits that you tested with so
>> > I can verify that your patch at least works?
>> >
>> > Thanks,
>> >
>> > Tom
>> >
>> >
>> >
>> > > Nitin A Kamble (1):
>> > >   emgd-driver-bin: Fix package naming issue
>> > >
>> > >  .../xorg-xserver/emgd-driver-bin_1.14.bb   |8 +++-
>> > >  1 files changed, 7 insertions(+), 1 deletions(-)
>> > >
>> >
>
>___
>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: [yocto] [PATCH 0/1] Fix X issue on crownbay

[Bodke, Kishore K]

>-Original Message-
>From: Kamble, Nitin A
>Sent: Thursday, September 13, 2012 12:58 PM
>To: Bodke, Kishore K; Zanussi, Tom
>Cc: Hart, Darren; yocto@yoctoproject.org
>Subject: RE: [PATCH 0/1] Fix X issue on crownbay
>
>Thanks Kishore for reporting it. I am trying to get to bottom of this by today 
>or
>tomorrow.

Hi Nitin,

I still cannot see the X with the latest poky/master and meta-intel/master for 
Romley.
No /usr/bin/Xorg and /usr/bin/X .

Thanks
Kishore.

>
>Thanks,
>Nitin
>
>
>> -Original Message-
>> From: Bodke, Kishore K
>> Sent: Wednesday, September 12, 2012 1:57 PM
>> To: Kamble, Nitin A; Zanussi, Tom
>> Cc: Hart, Darren; yocto@yoctoproject.org
>> Subject: RE: [PATCH 0/1] Fix X issue on crownbay
>>
>>
>>
>> >-Original Message-
>> >From: yocto-boun...@yoctoproject.org [mailto:yocto-
>> >boun...@yoctoproject.org] On Behalf Of Kamble, Nitin A
>> >Sent: Wednesday, September 12, 2012 1:14 PM
>> >To: Zanussi, Tom
>> >Cc: Hart, Darren; yocto@yoctoproject.org
>> >Subject: Re: [yocto] [PATCH 0/1] Fix X issue on crownbay
>> >
>> >FYI While testing on the fishriver platform, I also find that there is
>> >no X log, and looking further found out that xorg executable is not on
>> >the image. I think the same thing is also happening on crownbay.
>>
>> FYI.. I also see the similar issue for Romley.
>> There is no Xlog and X does not comes up.
>>
>> Thanks
>> Kishore.
>>
>> >
>> >Nitin
>> >
>> >
>> >
>> >> -Original Message-
>> >> From: Kamble, Nitin A
>> >> Sent: Wednesday, September 12, 2012 9:18 AM
>> >> To: Zanussi, Tom
>> >> Cc: Hart, Darren; yocto@yoctoproject.org
>> >> Subject: RE: [PATCH 0/1] Fix X issue on crownbay
>> >>
>> >> Hi Tom,
>> >>   Thanks for looking into the matter. I will try to reproduce the
>> >> issue you are seeing with master. And send another pull request with all
>> the fixes.
>> >>
>> >> Regards,
>> >> Nitin
>> >>
>> >>
>> >> > -Original Message-
>> >> > From: Zanussi, Tom
>> >> > Sent: Monday, September 10, 2012 4:34 PM
>> >> > To: Kamble, Nitin A
>> >> > Cc: Hart, Darren; yocto@yoctoproject.org
>> >> > Subject: Re: [PATCH 0/1] Fix X issue on crownbay
>> >> >
>> >> > On Wed, 2012-09-05 at 17:59 -0700, nitin.a.kam...@intel.com wrote:
>> >> > > From: Nitin A Kamble 
>> >> > >
>> >> > > The following changes since commit
>> >> > 66b516f3d3a287eecbf8804b2221bfc27e36db63:
>> >> > >
>> >> > >   README: add info explaining meta-tlk layer purpose (2012-09-06
>> >> > > 10:36:02 -0500)
>> >> > >
>> >> > > are available in the git repository at:
>> >> > >   git://git.yoctoproject.org/meta-intel-contrib nitin/work
>> >> > >
>> >> > > http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=ni
>> >> > > tin
>> >> > > /w
>> >> > > ork
>> >> > >
>> >> >
>> >> > I built and tried this, but it still didn't boot into X, and now
>> >> > there's not even an Xorg.log to look at:
>> >> >
>> >> > root@crownbay:/var/log# ls -al
>> >> > drwxr-xr-x2 root root80 Sep 10 20:15 .
>> >> > drwxrwxrwt7 root root   140 Jan  6  2009 ..
>> >> > -rw-r--r--1 root root 78429 Sep 10 20:17 messages
>> >> > -rw-rw-r--1 root root  4224 Sep 10 20:17 wtmp
>> >> >
>> >> > I assume this is a different X problem related to recent changes in
>> mater.
>> >> > Can you update the bug report with the commits that you tested with
>> >> > so I can verify that your patch at least works?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Tom
>> >> >
>> >> >
>> >> >
>> >> > > Nitin A Kamble (1):
>> >> > >   emgd-driver-bin: Fix package naming issue
>> >> > >
>> >> > >  .../xorg-xserver/emgd-driver-bin_1.14.bb   |8 +++-
>> >> > >  1 files changed, 7 insertions(+), 1 deletions(-)
>> >> > >
>> >> >
>> >
>> >___
>> >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: [yocto] [PATCH 0/3][meta-intel] Add new Corpus recipes to Crystal Forest BSP.

[Bodke, Kishore K]

>-Original Message-
>From: Przemysław Czesnowicz [mailto:czesiek...@gmail.com]
>Sent: Thursday, September 20, 2012 3:58 AM
>To: Bodke, Kishore K
>Cc: Zanussi, Tom; Kamble, Nitin A; yocto@yoctoproject.org; Samson, Don;
>Czesnowicz, PrzemyslawX
>Subject: Re: [yocto] [PATCH 0/3][meta-intel] Add new Corpus recipes to
>Crystal Forest BSP.
>
>2012/9/19  :
>> From: Kishore Bodke 
>>
>> Hi,
>>
>> This patch set adds three different types of Corpus files
>> to Crystal Forest BSP, which are basically used to test the
>> Lossless Compression algorithms.
>>
>> 1. calgary-corpus
>> 2. canterbury-corpus
>> 3. silesia-corpus
>>
>> These have been tested on both Crystal Forest Platforms.
>>
>
>Hi
>
>Are those for the sample code of QA driver?
>If so  the sample code needs the corpus to be in one file
>
>tar -xf calgary.tar.gz -O > calgary
>
>Also the CrystalForest software package includes the
> calgary and canterbury corpus files, at least in 0.9.0 version
>

Yes. These are for the QuickAssist Driver.
All the sample corpus data files will be installed under /lib/firmware, at 
least with the 0.9.0-144  version QA driver, that I had tested.

Instead of having all of files in one package and having one recipe, I had 
split them to multiple recipes.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 0/3][meta-intel] Add new Corpus recipes to Crystal Forest BSP.

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Bodke, Kishore K
>Sent: Thursday, September 20, 2012 9:21 AM
>To: Przemyslaw Czesnowicz
>Cc: Samson, Don; Czesnowicz, PrzemyslawX; yocto@yoctoproject.org
>Subject: Re: [yocto] [PATCH 0/3][meta-intel] Add new Corpus recipes to
>Crystal Forest BSP.
>
>
>
>>-Original Message-
>>From: Przemysław Czesnowicz [mailto:czesiek...@gmail.com]
>>Sent: Thursday, September 20, 2012 3:58 AM
>>To: Bodke, Kishore K
>>Cc: Zanussi, Tom; Kamble, Nitin A; yocto@yoctoproject.org; Samson, Don;
>>Czesnowicz, PrzemyslawX
>>Subject: Re: [yocto] [PATCH 0/3][meta-intel] Add new Corpus recipes to
>>Crystal Forest BSP.
>>
>>2012/9/19  :
>>> From: Kishore Bodke 
>>>
>>> Hi,
>>>
>>> This patch set adds three different types of Corpus files
>>> to Crystal Forest BSP, which are basically used to test the
>>> Lossless Compression algorithms.
>>>
>>> 1. calgary-corpus
>>> 2. canterbury-corpus
>>> 3. silesia-corpus
>>>
>>> These have been tested on both Crystal Forest Platforms.
>>>
>>
>>Hi
>>
>>Are those for the sample code of QA driver?
>>If so  the sample code needs the corpus to be in one file
>>
>>tar -xf calgary.tar.gz -O > calgary
>>
>>Also the CrystalForest software package includes the
>> calgary and canterbury corpus files, at least in 0.9.0 version
>>
>
>Yes. These are for the QuickAssist Driver.
>All the sample corpus data files will be installed under /lib/firmware, at 
>least
>with the 0.9.0-144  version QA driver, that I had tested.
>
>Instead of having all of files in one package and having one recipe, I had 
>split
>them to multiple recipes.
>

If you are talking about the Calgary and Canterbury files that are part of QAT 
Software package,
that are present in the sample_code/performance/compression, then, Yes, they 
will stay inside the QAT Software Package.

But these are the external to the QAT package.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] do_package_write_rpm failed.

[Bodke, Kishore K]

Hi,

I have a modified version of zlib package and trying to build and I get error 
while doing the packaging.
Any idea what this error is?

ERROR: Logfile of failure stored in: 
/usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-linux/zlib-qat-1.2.7-r9/temp/log.do_package_write_rpm.5284
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing python function do_package_write_rpm
| DEBUG: Executing python function read_subpackage_metadata
| DEBUG: Python function read_subpackage_metadata finished
| DEBUG: Executing python function do_package_rpm
| DEBUG: Executing python function write_specfile
| NOTE: Creating RPM package for zlib-qat
| NOTE: Creating RPM package for zlib-qat
| NOTE: Creating RPM package for zlib-qat-dev
| NOTE: Creating RPM package for zlib-qat-dbg
| NOTE: Creating RPM package for zlib-qat-staticdev
| NOTE: Creating RPM package for zlib-qat-doc
| DEBUG: Python function write_specfile finished
| DEBUG: Executing shell function BUILDSPEC
| Building target platforms: x86_64-poky-linux
| Processing files: zlib-qat-1.2.7-r9.x86_64
| Finding  Provides: 
/usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-linux/zlib-qat-1.2.7-r9/zlib-qat.provides
| Finding  Requires: 
/usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-linux/zlib-qat-1.2.7-r9/zlib-qat.requires
| Provides: libz.so.1(ZLIB_1.2.0.2)(64bit) libz.so.1(ZLIB_1.2.2.4)(64bit) 
libz.so.1(ZLIB_1.2.0)(64bit) libz.so.1(ZLIB_1.2.5.1)(64bit) 
libz.so.1(ZLIB_1.2.2.3)(64bit) libz.so.1(ZLIB_1.2.3.4)(64bit) 
libz.so.1(ZLIB_1.2.7)(64bit) libz.so.1(ZLIB_1.2.2)(64bit) 
libz.so.1(ZLIB_1.2.3.3)(64bit) libz.so.1(ZLIB_1.2.5.2)(64bit) 
libz.so.1(ZLIB_1.2.3.5)(64bit) libz.so.1(ZLIB_1.2.0.8)(64bit) libz.so.1()(64bit)
| Requires: rtld(GNU_HASH) libc.so.6(GLIBC_2.14)(64bit) 
libcrypto.so.1.0.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) 
libpthread.so.0(GLIBC_2.3.4)(64bit) libc.so.6()(64bit) 
libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) 
libpthread.so.0(GLIBC_2.3.2)(64bit) libdl.so.2()(64bit) 
librt.so.1(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) 
libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit) librt.so.1()(64bit) 
libc.so.6(GLIBC_2.3.2)(64bit)
| Provides: libz.so.1(ZLIB_1.2.0.2)(64bit) libz.so.1(ZLIB_1.2.2.4)(64bit) 
libz.so.1(ZLIB_1.2.0)(64bit) libz.so.1(ZLIB_1.2.5.1)(64bit) 
libz.so.1(ZLIB_1.2.2.3)(64bit) libz.so.1(ZLIB_1.2.3.4)(64bit) 
libz.so.1(ZLIB_1.2.7)(64bit) libz.so.1(ZLIB_1.2.2)(64bit) 
libz.so.1(ZLIB_1.2.3.3)(64bit) libz.so.1(ZLIB_1.2.5.2)(64bit) 
libz.so.1(ZLIB_1.2.3.5)(64bit) libz.so.1(ZLIB_1.2.0.8)(64bit) libz.so.1()(64bit)
| Requires: rtld(GNU_HASH) libc.so.6(GLIBC_2.14)(64bit) 
libcrypto.so.1.0.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) 
libpthread.so.0(GLIBC_2.3.4)(64bit) libc.so.6()(64bit) 
libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) 
libpthread.so.0(GLIBC_2.3.2)(64bit) libdl.so.2()(64bit) 
librt.so.1(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit) 
libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit) librt.so.1()(64bit) 
libc.so.6(GLIBC_2.3.2)(64bit)
| Processing files: zlib-qat-dev-1.2.7-r9.x86_64
| Finding  Provides: 
/usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-linux/zlib-qat-1.2.7-r9/zlib-qat.provides
| error: line 164: Illegal char '-' in EVR:
|
| error: Failed to find Provides:
|
|
| RPM build errors:
| line 164: Illegal char '-' in EVR:
|
| Failed to find Provides:
| DEBUG: Python function do_package_rpm finished
| DEBUG: Python function do_package_write_rpm finished
| ERROR: Function failed: BUILDSPEC (see 
/usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-linux/zlib-qat-1.2.7-r9/temp/log.do_package_write_rpm.5284
 for further information)
ERROR: Task 11 
(/usr/local/src/shumway/sep12/meta-intel/meta-crystalforest/recipes-quickassist/intel-zlib-qat/zlib-qat_1.2.7.bb,
 do_package_write_rpm) failed with exit code '1'
NOTE: Tasks Summary: Attempted 944 tasks of which 934 didn't need to be rerun 
and 1 failed.
Summary: 1 task failed:
  
/usr/local/src/shumway/sep12/meta-intel/meta-crystalforest/recipes-quickassist/intel-zlib-qat/zlib-qat_1.2.7.bb,
 do_package_write_rpm
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] do_package_write_rpm failed.

[Bodke, Kishore K]

>-Original Message-
>From: McClintock Matthew-B29882 [mailto:b29...@freescale.com]
>Sent: Monday, September 24, 2012 5:49 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] do_package_write_rpm failed.
>
>On Mon, Sep 24, 2012 at 6:44 PM, Bodke, Kishore K
> wrote:
>> Hi,
>>
>>
>>
>> I have a modified version of zlib package and trying to build and I get
>> error while doing the packaging.
>>
>> Any idea what this error is?
>>
>>
>>
>> ERROR: Logfile of failure stored in:
>> /usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-
>linux/zlib-qat-1.2.7-r9/temp/log.do_package_write_rpm.5284
>>
>> Log data follows:
>>
>> | DEBUG: Executing python function sstate_task_prefunc
>>
>> | DEBUG: Python function sstate_task_prefunc finished
>>
>> | DEBUG: Executing python function do_package_write_rpm
>>
>> | DEBUG: Executing python function read_subpackage_metadata
>>
>> | DEBUG: Python function read_subpackage_metadata finished
>>
>> | DEBUG: Executing python function do_package_rpm
>>
>> | DEBUG: Executing python function write_specfile
>>
>> | NOTE: Creating RPM package for zlib-qat
>>
>> | NOTE: Creating RPM package for zlib-qat
>>
>> | NOTE: Creating RPM package for zlib-qat-dev
>>
>> | NOTE: Creating RPM package for zlib-qat-dbg
>>
>> | NOTE: Creating RPM package for zlib-qat-staticdev
>>
>> | NOTE: Creating RPM package for zlib-qat-doc
>>
>> | DEBUG: Python function write_specfile finished
>>
>> | DEBUG: Executing shell function BUILDSPEC
>>
>> | Building target platforms: x86_64-poky-linux
>>
>> | Processing files: zlib-qat-1.2.7-r9.x86_64
>>
>> | Finding  Provides:
>> /usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-
>linux/zlib-qat-1.2.7-r9/zlib-qat.provides
>>
>> | Finding  Requires:
>> /usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-
>linux/zlib-qat-1.2.7-r9/zlib-qat.requires
>>
>> | Provides: libz.so.1(ZLIB_1.2.0.2)(64bit) libz.so.1(ZLIB_1.2.2.4)(64bit)
>> libz.so.1(ZLIB_1.2.0)(64bit) libz.so.1(ZLIB_1.2.5.1)(64bit)
>> libz.so.1(ZLIB_1.2.2.3)(64bit) libz.so.1(ZLIB_1.2.3.4)(64bit)
>> libz.so.1(ZLIB_1.2.7)(64bit) libz.so.1(ZLIB_1.2.2)(64bit)
>> libz.so.1(ZLIB_1.2.3.3)(64bit) libz.so.1(ZLIB_1.2.5.2)(64bit)
>> libz.so.1(ZLIB_1.2.3.5)(64bit) libz.so.1(ZLIB_1.2.0.8)(64bit)
>> libz.so.1()(64bit)
>>
>> | Requires: rtld(GNU_HASH) libc.so.6(GLIBC_2.14)(64bit)
>> libcrypto.so.1.0.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit)
>> libpthread.so.0(GLIBC_2.3.4)(64bit) libc.so.6()(64bit)
>> libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit)
>> libpthread.so.0(GLIBC_2.3.2)(64bit) libdl.so.2()(64bit)
>> librt.so.1(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit)
>> libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit) librt.so.1()(64bit)
>> libc.so.6(GLIBC_2.3.2)(64bit)
>>
>> | Provides: libz.so.1(ZLIB_1.2.0.2)(64bit) libz.so.1(ZLIB_1.2.2.4)(64bit)
>> libz.so.1(ZLIB_1.2.0)(64bit) libz.so.1(ZLIB_1.2.5.1)(64bit)
>> libz.so.1(ZLIB_1.2.2.3)(64bit) libz.so.1(ZLIB_1.2.3.4)(64bit)
>> libz.so.1(ZLIB_1.2.7)(64bit) libz.so.1(ZLIB_1.2.2)(64bit)
>> libz.so.1(ZLIB_1.2.3.3)(64bit) libz.so.1(ZLIB_1.2.5.2)(64bit)
>> libz.so.1(ZLIB_1.2.3.5)(64bit) libz.so.1(ZLIB_1.2.0.8)(64bit)
>> libz.so.1()(64bit)
>>
>> | Requires: rtld(GNU_HASH) libc.so.6(GLIBC_2.14)(64bit)
>> libcrypto.so.1.0.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit)
>> libpthread.so.0(GLIBC_2.3.4)(64bit) libc.so.6()(64bit)
>> libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit)
>> libpthread.so.0(GLIBC_2.3.2)(64bit) libdl.so.2()(64bit)
>> librt.so.1(GLIBC_2.2.5)(64bit) libpthread.so.0()(64bit)
>> libcrypto.so.1.0.0(OPENSSL_1.0.0)(64bit) librt.so.1()(64bit)
>> libc.so.6(GLIBC_2.3.2)(64bit)
>>
>> | Processing files: zlib-qat-dev-1.2.7-r9.x86_64
>>
>> | Finding  Provides:
>> /usr/local/src/shumway/sep12/build-shumway2/tmp/work/x86_64-poky-
>linux/zlib-qat-1.2.7-r9/zlib-qat.provides
>>
>> | error: line 164: Illegal char '-' in EVR:
>>
>> |
>>
>> | error: Failed to find Provides:
>>
>> |
>>
>> |
>>
>> | RPM build errors:
>>
>> | line 164: Illegal char '-' in EVR:
>
>I've found RPM does not like - in it's variable names. Did you add a
>'-' anywhere? Maybe in your arch or package name? What did you change
>in the recipe?
>

I have added my patches and renamed the zlib recipe

Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Chris Tapp
>Sent: Monday, October 08, 2012 12:59 AM
>To: Bruce Ashfield
>Cc: yocto@yoctoproject.org Project
>Subject: Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in 
>the
>kernel
>
>On 7 Oct 2012, at 22:41, Bruce Ashfield wrote:
>
>> On Sun, Oct 7, 2012 at 6:08 PM, Chris Tapp 
>wrote:
>>> On 7 Oct 2012, at 03:00, Saxena, Rahul wrote:
>>>
 Try adding the unionfs feature (below) to your kernel:

 http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-
>3.0/tree/meta/cfg/kernel-cache/features/unionfs?h=meta

 create a file my_cedartrail.scc with following line:
 include features/unionfs/unionfs.scc

 put this file in a dir linux-yocto, the dir being created in

 meta-cedartrail/recipes-kernel/linux

 add following line in  meta-cedartrail/recipes-kernel/Linux/linux-
>yocto_3.0.bbappend

 SRC_URI +="file://my_cedartrail.scc"
>>>
>>> Thanks - I thought just running 'menuconfig' would allow me to enable it
>(for a quick test).
>>>
>>> However, this still doesn't seem to be working. I can see that
>'my_cedartrail.scc' gets fetched in to the build area, but I still don't see
>CONFIG_UNION_FS if I run 'menuconfig'. There is also no 'unionfs' folder in
>fs/ of the build tree.
>>>
>>> Also, if I specify an invalid feature (e.g. feature2/unionfs/unionfs.scc) 
>>> I'm
>not seeing any diagnostic.
>>
>> unionfs was never merged to the 3.0 kernel, I re-added it to the
>development
>> trees for 3.2 and the 3.4 kernel (aufs for the 3.6 tree at the moment). The
>meta
>> data is carried forward from the older kernels as a placeholder and is
>> documented
>> in the .scc file itself:
>>
>> ---
>> kconf non-hardware unionfs.cfg
>>
>> # commented pending update to a newer version ported to 2.6.35+
>> # patch unionfs-2.5.4-integration.patch
>> ---
>>
>> So to get unionfs in the 3.0 kernel, we'd need a port .. but since
>> we've moved on
>> quite a bit past 3.0, I don't know of any pending ports myself.
>
>Thanks Bruce.
>
>I guess I need to ask the Intel guys if there are any plans to move Cedartrail 
>on
>from 3.0 ?

If the interest is to have unionfs, you can still get it from 3.2 or 3.4 Kernel.

But the downside is you will be missing the PVR Graphics and will be falling 
back to the 
basic vesa graphics mode.

PVR graphics has support only for  3.0 kernel only, so we had only put the 3.0 
kernel recipe in the meta-intel.

We do not have plans to port PVR graphics to 3.4 kernel.

We can update the Cedartrail BSP to have 3.2 and 3.4 kernel but it will be vesa 
graphics support only.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

[Bodke, Kishore K]

>-Original Message-
>From: Chris Tapp [mailto:opensou...@keylevel.com]
>Sent: Monday, October 08, 2012 1:03 PM
>To: Bodke, Kishore K
>Cc: Bruce Ashfield; yocto@yoctoproject.org Project
>Subject: Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in 
>the
>kernel
>
>On 8 Oct 2012, at 17:35, Bodke, Kishore K wrote:
>
>>
>>
>>> -Original Message-
>>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>> boun...@yoctoproject.org] On Behalf Of Chris Tapp
>>> Sent: Monday, October 08, 2012 12:59 AM
>>> To: Bruce Ashfield
>>> Cc: yocto@yoctoproject.org Project
>>> Subject: Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs 
>>> in
>the
>>> kernel
>>>
>>> On 7 Oct 2012, at 22:41, Bruce Ashfield wrote:
>>>
>>>> On Sun, Oct 7, 2012 at 6:08 PM, Chris Tapp 
>>> wrote:
>>>>> On 7 Oct 2012, at 03:00, Saxena, Rahul wrote:
>>>>>
>>>>>> Try adding the unionfs feature (below) to your kernel:
>>>>>>
>>>>>> http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-
>>> 3.0/tree/meta/cfg/kernel-cache/features/unionfs?h=meta
>>>>>>
>>>>>> create a file my_cedartrail.scc with following line:
>>>>>> include features/unionfs/unionfs.scc
>>>>>>
>>>>>> put this file in a dir linux-yocto, the dir being created in
>>>>>>
>>>>>> meta-cedartrail/recipes-kernel/linux
>>>>>>
>>>>>> add following line in  meta-cedartrail/recipes-kernel/Linux/linux-
>>> yocto_3.0.bbappend
>>>>>>
>>>>>> SRC_URI +="file://my_cedartrail.scc"
>>>>>
>>>>> Thanks - I thought just running 'menuconfig' would allow me to enable it
>>> (for a quick test).
>>>>>
>>>>> However, this still doesn't seem to be working. I can see that
>>> 'my_cedartrail.scc' gets fetched in to the build area, but I still don't see
>>> CONFIG_UNION_FS if I run 'menuconfig'. There is also no 'unionfs' folder in
>>> fs/ of the build tree.
>>>>>
>>>>> Also, if I specify an invalid feature (e.g. feature2/unionfs/unionfs.scc)
>I'm
>>> not seeing any diagnostic.
>>>>
>>>> unionfs was never merged to the 3.0 kernel, I re-added it to the
>>> development
>>>> trees for 3.2 and the 3.4 kernel (aufs for the 3.6 tree at the moment). The
>>> meta
>>>> data is carried forward from the older kernels as a placeholder and is
>>>> documented
>>>> in the .scc file itself:
>>>>
>>>> ---
>>>> kconf non-hardware unionfs.cfg
>>>>
>>>> # commented pending update to a newer version ported to 2.6.35+
>>>> # patch unionfs-2.5.4-integration.patch
>>>> ---
>>>>
>>>> So to get unionfs in the 3.0 kernel, we'd need a port .. but since
>>>> we've moved on
>>>> quite a bit past 3.0, I don't know of any pending ports myself.
>>>
>>> Thanks Bruce.
>>>
>>> I guess I need to ask the Intel guys if there are any plans to move 
>>> Cedartrail
>on
>>> from 3.0 ?
>>
>> If the interest is to have unionfs, you can still get it from 3.2 or 3.4 
>> Kernel.
>>
>> But the downside is you will be missing the PVR Graphics and will be falling
>back to the
>> basic vesa graphics mode.
>
>Tricky. One of the reasons for specifying Cedartrail was the accelerated
>graphics. However, I've got code running without acceleration and it looks like
>it should be fast enough to do what I need without it.
>
>> PVR graphics has support only for  3.0 kernel only, so we had only put the 
>> 3.0
>kernel recipe in the meta-intel.
>>
>> We do not have plans to port PVR graphics to 3.4 kernel.
>
>That's a pity, as this platform has a very good level of performance. I guess 
>I'll
>have to be patient and wait for Ivy Bridge graphics ;-)
>
>> We can update the Cedartrail BSP to have 3.2 and 3.4 kernel but it will be
>vesa graphics support only.
>
>How much work would this take? It looks like there is no unification FS support
>in 3.0 that I could use instead, but this is only for a low-volume project and 
>I
>wouldn't like to think it was using resource that could be deployed more
>

Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in the kernel

[Bodke, Kishore K]

>-Original Message-
>From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
>Sent: Wednesday, October 10, 2012 6:48 AM
>To: Chris Tapp
>Cc: Bodke, Kishore K; yocto@yoctoproject.org Project
>Subject: Re: [yocto] Meta Intel / Cedartrail / Denzil - how to get unionfs in 
>the
>kernel
>
>On 12-10-08 05:03 PM, Chris Tapp wrote:
>> On 8 Oct 2012, at 21:30, Bodke, Kishore K wrote:
>>
>> <  snip ...>
>>
>> Thanks for the really fast response on this :-)
>>
>>> For denzil, try with this by creating a new file in meta-cedartrail/recipes-
>kernel/linux/linux-yocto_3.2.bbappend.
>>>
>>> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
>>>
>>> SRC_URI_cedartrail-nopvr = "git://git.yoctoproject.org/linux-yocto-
>3.2;protocol=git;nocheckout=1;branch=${KBRANCH},meta;name=machine,m
>eta"
>>
>> I had to add 'bareclone=1' to this to get it to run.
>>
>>> COMPATIBLE_MACHINE_cedartrail-nopvr = "cedartrail"
>>> KMACHINE_cedartrail-nopvr  = "cedartrail"
>>> KBRANCH_cedartrail-nopvr  = "yocto/standard/cedartrail"
>>> KERNEL_FEATURES_append_cedartrail-nopvr += " cfg/smp.scc"
>>>
>>> SRCREV_machine_pn-linux-yocto_cedartrail-nopvr ?=
>"8b8cfaaab2b8d79ac56e8c9a85bad9ae7bca399c"
>>> SRCREV_meta_pn-linux-yocto_cedartrail-nopvr ?=
>"486f7aec824b4127e91ef53228823e996b3696f0"
>>
>> I think it's nearly there, but I get a failure when validating the branch:
>
>I'm back to the office now. Is this issue still lurking/active ?
>

Issue of validating the branches is resolved.

Thanks
Kishore.

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

Re: [yocto] Finding root cause of "host include and/or library paths were used"

[Bodke, Kishore K]

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Chris Tapp
>Sent: Wednesday, October 10, 2012 9:50 AM
>To: yocto@yoctoproject.org Project
>Subject: [yocto] Finding root cause of "host include and/or library paths were
>used"
>
>I'm trying to get libsdl_gfx to build. I've created a .bb file which runs and
>installs the relevant headers and libs in tmp/sysroots.
>
>However, I'm getting a QA failure:
>
>NOTE: package libsdl-gfx-2.0.24-r1: task do_populate_sysroot: Succeeded
>WARNING: libsdl-gfx: The compile log indicates that host include and/or library
>paths were used.
> Please check the log '/media/SSD-RAID/build-denzil-git-sjs-
>cedartrail/tmp/work/core2-sjs-linux/libsdl-gfx-2.0.24-
>r1/temp/log.do_compile' for more information.
>
>The compile log has instances of:
>
>cc1: warning: include location "/usr/include/SDL" is unsafe for cross-
>compilation [-Wpoison-system-directories]
>
>The source uses autotools. I've had a look round the files, but it's not 
>obvious
>to me where the above path is set (I'm definitely not an autotools expert).
>Can anyone give me an idea what I should be looking for? I suspect it may
>have something to do with a line from Makefile.am:
>
>libSDL_gfxincludedir = $(includedir)/SDL

Did you inherit autotools in your recipe?
You may have to patch your makefile not to use host header files.
Or, I think you can use ${STAGING_INCDIR} to override, at the time of your 
configure.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Finding root cause of "host include and/or library paths were used"

[Bodke, Kishore K]

>-Original Message-
>From: Chris Tapp [mailto:opensou...@keylevel.com]
>Sent: Wednesday, October 10, 2012 2:34 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org Project
>Subject: Re: [yocto] Finding root cause of "host include and/or library paths
>were used"
>
>
>On 10 Oct 2012, at 20:51, Chris Tapp wrote:
>
>> On 10 Oct 2012, at 18:26, Bodke, Kishore K wrote:
>>
>>>
>>>
>>>> -Original Message-
>>>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>>>> boun...@yoctoproject.org] On Behalf Of Chris Tapp
>>>> Sent: Wednesday, October 10, 2012 9:50 AM
>>>> To: yocto@yoctoproject.org Project
>>>> Subject: [yocto] Finding root cause of "host include and/or library paths
>were
>>>> used"
>>>>
>>>> I'm trying to get libsdl_gfx to build. I've created a .bb file which runs 
>>>> and
>>>> installs the relevant headers and libs in tmp/sysroots.
>>>>
>>>> However, I'm getting a QA failure:
>>>>
>>>> NOTE: package libsdl-gfx-2.0.24-r1: task do_populate_sysroot: Succeeded
>>>> WARNING: libsdl-gfx: The compile log indicates that host include and/or
>library
>>>> paths were used.
>>>>   Please check the log '/media/SSD-RAID/build-denzil-git-sjs-
>>>> cedartrail/tmp/work/core2-sjs-linux/libsdl-gfx-2.0.24-
>>>> r1/temp/log.do_compile' for more information.
>>>>
>>>> The compile log has instances of:
>>>>
>>>> cc1: warning: include location "/usr/include/SDL" is unsafe for cross-
>>>> compilation [-Wpoison-system-directories]
>>>>
>>>> The source uses autotools. I've had a look round the files, but it's not
>obvious
>>>> to me where the above path is set (I'm definitely not an autotools
>expert).
>>>> Can anyone give me an idea what I should be looking for? I suspect it may
>>>> have something to do with a line from Makefile.am:
>>>>
>>>> libSDL_gfxincludedir = $(includedir)/SDL
>>>
>>> Did you inherit autotools in your recipe?
>>
>> Yes, that's in there.
>>
>>> You may have to patch your makefile not to use host header files.
>>> Or, I think you can use ${STAGING_INCDIR} to override, at the time of your
>configure.
>>
>> Thanks. Are there any examples I can look at to see how to do this? I've not
>been able to find which file I need to change after 'unpack'.
>
>I seem to have 'fixed' it, but I'm not sure I understand how! I've added:
>
>EXTRA_OECONF = "--prefix=/any-old-thing"
>
>to the .bb file. No warnings, compile log shows the correct include path:
>
>-I/media/SSD-RAID/build-denzil-git-sjs-cedartrail/tmp/sysroots/cedartrail-
>nopvr/usr/include/SDL

Yeah, EXTRA_OECONF with ${STAGING_INCDIR} would do that I guess, 
But not exactly sure with the syntax here.  

You might want to take a look other recipes in poky using this I guess to find 
how it is done.

Thanks
Kishore.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Cedar Trail and gst-vaapi fixes

[Bodke, Kishore K]

>-Original Message-
>From: Ross Burton [mailto:ross.bur...@intel.com]
>Sent: Wednesday, October 17, 2012 8:21 AM
>To: Bodke, Kishore K; Kamble, Nitin A; dvh...@linux.intel.com
>Cc: yocto@yoctoproject.org
>Subject: Cedar Trail and gst-vaapi fixes
>
>Hi,
>
>Make gst-vaapi work on Cedar Trail, upgrade the gst-vaapi to the latest
>version
>which doesn't need ffmpeg anymore, and remove the commercial restriction
>on
>gst-vaapi.
>
>The new gst-vaapi was tested on Cedar Trail, and played the Sintel 720p trailer
>smoothly.  ffmpeg was required for the audio (MPEG4 AAC), but without that
>present the video still plays.

Hi,

Wanted to check if you had a chance to look into the cpu uitilization?
We had less than 15% cpu uitilization, with the acceleration while playing the 
video.

Thanks
Kishore.
>
>Ross
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH 2/3][meta-intel] meta-intel/common: Add new recipe for libcrypto module.

[Bodke, Kishore K]

>-Original Message-
>From: Kamble, Nitin A
>Sent: Friday, October 19, 2012 11:25 AM
>To: Bodke, Kishore K; Zanussi, Tom; yocto@yoctoproject.org
>Subject: RE: [PATCH 2/3][meta-intel] meta-intel/common: Add new recipe for
>libcrypto module.
>
>Hi Kishore,
>   Will this recipe is being used for multiple BSPs? If not then it can go in 
> the
>BSP specific layer.
>

Hi Nitin,

Yes, these will be used by both Crystal Forest and Rangely.  So I put them in 
common.

Thanks
Kishore.

>Thanks,
>Nitin
>
>> -Original Message-
>> From: Bodke, Kishore K
>> Sent: Thursday, October 18, 2012 11:19 AM
>> To: Zanussi, Tom; Kamble, Nitin A; yocto@yoctoproject.org
>> Cc: Bodke, Kishore K
>> Subject: [PATCH 2/3][meta-intel] meta-intel/common: Add new recipe for
>> libcrypto module.
>>
>> From: Kishore Bodke 
>>
>> This adds a new recipe to include the Intel Quick Assist Technology libcrypto
>> Memory Management Module.
>>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  .../openssl-qat-module/openssl-qat-module.bb   |   54
>> 
>>  .../openssl-qat-module/openssl_qat_module.patch|   43
>> 
>>  2 files changed, 97 insertions(+)
>>  create mode 100644 common/recipes-connectivity/openssl-qat-
>> module/openssl-qat-module.bb
>>  create mode 100644 common/recipes-connectivity/openssl-qat-
>> module/openssl-qat-module/openssl_qat_module.patch
>>
>> diff --git a/common/recipes-connectivity/openssl-qat-module/openssl-qat-
>> module.bb b/common/recipes-connectivity/openssl-qat-module/openssl-
>> qat-module.bb
>> new file mode 100644
>> index 000..a4fe3c5
>> --- /dev/null
>> +++ b/common/recipes-connectivity/openssl-qat-module/openssl-qat-
>> module.
>> +++ bb
>> @@ -0,0 +1,54 @@
>> +SUMMARY = "libcrypto* (OpenSSL*) QAT_MEM Memory Management
>> Module \ for
>> +Intel Quick Assist Technology"
>> +DESCRIPTION = "This software adds an engine that accelerates some of \
>> +the libcrypto algorithms via the Intel QuickAssist Technology \
>> +implemented on Intel Communications Chipset 89xx Series based
>> platforms."
>> +
>> +HOMEPAGE = "http://www.openssl.org/";
>> +SECTION = "libs/network"
>> +
>> +LICENSE = "openssl"
>> +LIC_FILES_CHKSUM = "file://${WORKDIR}/openssl-
>> ${PV}/LICENSE;md5=f9a8f968107345e0b75aa8c2ecaa7ec8"
>> +
>> +PV = "1.0.1"
>> +PR = "r0"
>> +
>> +OPENSSL_QAT_VERSION = "0.4.0-012"
>> +
>> +SRC_URI = "http://www.openssl.org/source/openssl-
>> ${PV}.tar.gz;name=openssl \
>> +http://downloadmirror.intel.com/19368/eng/libcrypto-openssl-
>> ${PV}-qat.L.${OPENSSL_QAT_VERSION}.tar.gz;name=libcrypto \
>> +file://openssl_qat_module.patch"
>> +
>> +SRC_URI[openssl.md5sum]="134f168bc2a8333f19f81d684841710b"
>>
>+SRC_URI[openssl.sha256sum]="4d9f0a594a9a89b28e1a04a9504c04104f6508
>> ee27ad1e0efdd17a7a6dbb"
>> +
>> +SRC_URI[libcrypto.md5sum] = "e4e131fa56d3aa1a52b5bdb9f8fe5a69"
>> +SRC_URI[libcrypto.sha256sum] =
>>
>"19a80ae6e78548934295d312148e4254c18dabd25e2fd72de5796d8ac15b1cfb"
>> +
>> +S = "${WORKDIR}/openssl-${PV}/engines/qat_engine/qat_mem"
>> +
>> +export KERNEL_SOURCE_ROOT = "${STAGING_KERNEL_DIR}"
>> +inherit module
>> +
>> +do_patch() {
>> +cd ${WORKDIR}/openssl-${PV}
>> +patch -p2 <
>> +${WORKDIR}/libcrypto-openssl-${PV}-
>> qat.L.${OPENSSL_QAT_VERSION}.patch
>> +
>> +cd ${WORKDIR}
>> +patch -p1 <${WORKDIR}/openssl_qat_module.patch
>> +}
>> +
>> +do_compile(){
>> +cd ${S}
>> +oe_runmake  KERNEL_CC="${KERNEL_CC}"
>> +}
>> +
>> +do_install_append() {
>> +install -m 0755 -d ${D}${bindir} \
>> +   ${D}${includedir}/engines/qat_engine/qat_mem
>> +
>> +install -m 0755 ${S}/qat_mem_test  ${D}${bindir}
>> +install -m 0750 ${S}/*.h
>> ${D}${includedir}/engines/qat_engine/qat_mem/
>> +}
>> +
>> +FILES_${PN} += "${bindir}/qat_mem_test"
>> diff --git a/common/recipes-connectivity/openssl-qat-module/openssl-qat-
>> module/openssl_qat_module.patch b/common/recipes-
>> connectivity/openssl-qat-module/openssl-qat-
>> module/openssl_qat_module.patch
>> new file mode 100644
>> index 000..dfed3c0
>> --- /dev/null
>> +++ b/c

Re: [yocto] [PATCH 1/3] [meta-intel] meta-intel/common:Add a new recipe for Zlib qat_mem Module.

[Bodke, Kishore K]

>-Original Message-
>From: Kamble, Nitin A
>Sent: Friday, October 19, 2012 11:28 AM
>To: Bodke, Kishore K; Zanussi, Tom; yocto@yoctoproject.org
>Subject: RE: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new recipe
>for Zlib qat_mem Module.
>
>Hi Kishore,
>  Same here, if it is not used by multiple BSPs yet, then it should go in the 
> BSP
>specific layer.
>
Yes, these too will be used by both Crystal Forest and Rangely.

Thanks
Kishore.

>Thanks,
>Nitin
>
>
>> -Original Message-
>> From: Bodke, Kishore K
>> Sent: Thursday, October 18, 2012 11:19 AM
>> To: Zanussi, Tom; Kamble, Nitin A; yocto@yoctoproject.org
>> Cc: Bodke, Kishore K
>> Subject: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new recipe for
>> Zlib qat_mem Module.
>>
>> From: Kishore Bodke 
>>
>> This adds a new recipe to build the Intel Quick Assist Technology Memory
>> Management Module for Zlib.
>>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  .../zlib-qat-module/zlib-qat-module.bb |   52
>> 
>>  .../zlib-qat-module/zlib_qat_module.patch  |   43 
>>  2 files changed, 95 insertions(+)
>>  create mode 100644 common/recipes-core/zlib-qat-module/zlib-qat-
>> module.bb
>>  create mode 100644 common/recipes-core/zlib-qat-module/zlib-qat-
>> module/zlib_qat_module.patch
>>
>> diff --git a/common/recipes-core/zlib-qat-module/zlib-qat-module.bb
>> b/common/recipes-core/zlib-qat-module/zlib-qat-module.bb
>> new file mode 100644
>> index 000..5ade06e
>> --- /dev/null
>> +++ b/common/recipes-core/zlib-qat-module/zlib-qat-module.bb
>> @@ -0,0 +1,52 @@
>> +SUMMARY="Zlib QAT_MEM Memory Management Module for Intel Quick
>> Assist \
>> +Technology"
>> +DESCRIPTION="This software acelerates the data compression algorithm \
>> +in the zlib software library via the Intel QuickAssist Technology \
>> +implemented on Intel Communications Chipset 89xx Series based
>> platforms."
>> +
>> +HOMEPAGE = "http://zlib.net/";
>> +SECTION = "libs"
>> +LICENSE = "Zlib & GPLv2 & BSD"
>> +
>> +LIC_FILES_CHKSUM = "file://${WORKDIR}/zlib-
>> ${PV}/zlib.h;beginline=4;endline=23;md5=94d1b5a40dadd127f3351471727e6
>> 6a9 \
>> +file://${COMMON_LICENSE_DIR}/GPL-
>> 2.0;md5=801f80980d171dd6425610833a22dbe6 \
>> +
>>  file://${COMMON_LICENSE_DIR}/BSD;md5=3775480a712fc46a696476
>> 78acb234cb"
>> +PV = "1.2.7"
>> +ZLIB_QAT_VERSION = "0.4.0-011"
>> +
>> +PR="r0"
>> +
>> +SRC_URI = "http://www.zlib.net/zlib-${PV}.tar.gz;name=zlib \
>> +http://downloadmirror.intel.com/20294/eng/zlib-${PV}-
>> qat.L.${ZLIB_QAT_VERSION}.tar.gz;name=zlib_qat \
>> +file://zlib_qat_module.patch"
>> +
>> +SRC_URI[zlib.md5sum]="60df6a37c56e7c1366cca812414f7b85"
>> +SRC_URI[zlib.sha256sum]="fa9c9c8638efb8cb8ef5e4dd5453e455751e1c530
>> b1595eed466e1be9b7e26c5"
>> +
>> +SRC_URI[zlib_qat.md5sum]="88e4140f98d2f9e170bf473f20e1a8d4"
>>
>+SRC_URI[zlib_qat.sha256sum]="3c360878127f3930e64640ef5a5822719a5059
>> 143326bb4c396645ae37b704a6"
>> +
>> +S = "${WORKDIR}/zlib-${PV}/contrib/qat/qat_mem"
>> +
>> +inherit module
>> +export KERNEL_SOURCE_ROOT = "${STAGING_KERNEL_DIR}"
>> +
>> +do_patch()  {
>> +cd ${WORKDIR}/zlib-${PV}
>> +patch -p0  < ${WORKDIR}/zlib-${PV}-
>> qat.L.${ZLIB_QAT_VERSION}.patch
>> +
>> +cd ${WORKDIR}
>> +patch -p1   < ${WORKDIR}/zlib_qat_module.patch
>> +}
>> +
>> +do_compile(){
>> +cd ${S}
>> +oe_runmake KERNEL_CC="${KERNEL_CC}"
>> +}
>> +
>> +do_install_append() {
>> +install -m 0755 -d  ${D}${bindir}
>> +install -m 0755 ${S}/qat_mem_test   ${D}${bindir}
>> +}
>> +
>> +FILES_${PN} += "${bindir}/qat_mem_test"
>> diff --git a/common/recipes-core/zlib-qat-module/zlib-qat-
>> module/zlib_qat_module.patch b/common/recipes-core/zlib-qat-
>> module/zlib-qat-module/zlib_qat_module.patch
>> new file mode 100644
>> index 000..a30f8b0
>> --- /dev/null
>> +++ b/common/recipes-core/zlib-qat-module/zlib-qat-
>> module/zlib_qat_modul
>> +++ e.patch
>> @@ -0,0 +1,43 @@
>> +Index: zlib-qat-module-1.2.7-r0/zlib-1.2.7/contrib/qat/qat_mem/Makefile
>> +===

Re: [yocto] [PATCH 1/3] [meta-intel] meta-intel/common:Add a new recipe for Zlib qat_mem Module.

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Friday, October 19, 2012 11:35 AM
>To: Bodke, Kishore K
>Cc: Kamble, Nitin A; yocto@yoctoproject.org
>Subject: Re: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new recipe
>for Zlib qat_mem Module.
>
>Hi Kishore,
>
>I've built these and they look ok as far as that goes.
>
>But I'm wondering, which kernel did you test with and which kernel(s)
>are these modules designed for i.e. will they work with all the kernels
>supported for 1.3?

Hi Tom,

I have tested them for 3.4 Kernel for Yocto, since for Crystal Forest we only 
have 3.4 for now.
Apart from that, it should work with all the kernel versions.
I have tested 3.0 and 3.5 on Fedora. 

Thanks
Kishore.

>
>Tom
>
>On Fri, 2012-10-19 at 13:28 -0500, Bodke, Kishore K wrote:
>>
>> >-Original Message-----
>> >From: Kamble, Nitin A
>> >Sent: Friday, October 19, 2012 11:28 AM
>> >To: Bodke, Kishore K; Zanussi, Tom; yocto@yoctoproject.org
>> >Subject: RE: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new
>recipe
>> >for Zlib qat_mem Module.
>> >
>> >Hi Kishore,
>> >  Same here, if it is not used by multiple BSPs yet, then it should go in 
>> > the
>BSP
>> >specific layer.
>> >
>> Yes, these too will be used by both Crystal Forest and Rangely.
>>
>> Thanks
>> Kishore.
>>
>> >Thanks,
>> >Nitin
>> >
>> >
>> >> -Original Message-
>> >> From: Bodke, Kishore K
>> >> Sent: Thursday, October 18, 2012 11:19 AM
>> >> To: Zanussi, Tom; Kamble, Nitin A; yocto@yoctoproject.org
>> >> Cc: Bodke, Kishore K
>> >> Subject: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new recipe
>for
>> >> Zlib qat_mem Module.
>> >>
>> >> From: Kishore Bodke 
>> >>
>> >> This adds a new recipe to build the Intel Quick Assist Technology Memory
>> >> Management Module for Zlib.
>> >>
>> >> Signed-off-by: Kishore Bodke 
>> >> ---
>> >>  .../zlib-qat-module/zlib-qat-module.bb |   52
>> >> 
>> >>  .../zlib-qat-module/zlib_qat_module.patch  |   43
>
>> >>  2 files changed, 95 insertions(+)
>> >>  create mode 100644 common/recipes-core/zlib-qat-module/zlib-qat-
>> >> module.bb
>> >>  create mode 100644 common/recipes-core/zlib-qat-module/zlib-qat-
>> >> module/zlib_qat_module.patch
>> >>
>> >> diff --git a/common/recipes-core/zlib-qat-module/zlib-qat-module.bb
>> >> b/common/recipes-core/zlib-qat-module/zlib-qat-module.bb
>> >> new file mode 100644
>> >> index 000..5ade06e
>> >> --- /dev/null
>> >> +++ b/common/recipes-core/zlib-qat-module/zlib-qat-module.bb
>> >> @@ -0,0 +1,52 @@
>> >> +SUMMARY="Zlib QAT_MEM Memory Management Module for Intel
>Quick
>> >> Assist \
>> >> +Technology"
>> >> +DESCRIPTION="This software acelerates the data compression
>algorithm \
>> >> +in the zlib software library via the Intel QuickAssist Technology \
>> >> +implemented on Intel Communications Chipset 89xx Series based
>> >> platforms."
>> >> +
>> >> +HOMEPAGE = "http://zlib.net/";
>> >> +SECTION = "libs"
>> >> +LICENSE = "Zlib & GPLv2 & BSD"
>> >> +
>> >> +LIC_FILES_CHKSUM = "file://${WORKDIR}/zlib-
>> >>
>${PV}/zlib.h;beginline=4;endline=23;md5=94d1b5a40dadd127f3351471727e6
>> >> 6a9 \
>> >> + file://${COMMON_LICENSE_DIR}/GPL-
>> >> 2.0;md5=801f80980d171dd6425610833a22dbe6 \
>> >> +
>> >>   file://${COMMON_LICENSE_DIR}/BSD;md5=3775480a712fc46a696476
>> >> 78acb234cb"
>> >> +PV = "1.2.7"
>> >> +ZLIB_QAT_VERSION = "0.4.0-011"
>> >> +
>> >> +PR="r0"
>> >> +
>> >> +SRC_URI = "http://www.zlib.net/zlib-${PV}.tar.gz;name=zlib \
>> >> + http://downloadmirror.intel.com/20294/eng/zlib-${PV}-
>> >> qat.L.${ZLIB_QAT_VERSION}.tar.gz;name=zlib_qat \
>> >> + file://zlib_qat_module.patch"
>> >> +
>> >> +SRC_URI[zlib.md5sum]="60df6a37c56e7c1366cca812414f7b85"
>> >>
>+SRC_URI[zlib.sha256sum]="fa9c9c8638efb8cb8ef5e4dd5453e455751e1c530
>> >>

Re: [yocto] [PATCH 1/3] [meta-intel] meta-intel/common:Add a new recipe for Zlib qat_mem Module.

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Friday, October 19, 2012 11:49 AM
>To: Bodke, Kishore K
>Cc: Kamble, Nitin A; yocto@yoctoproject.org
>Subject: Re: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new recipe
>for Zlib qat_mem Module.
>
>On Fri, 2012-10-19 at 13:40 -0500, Bodke, Kishore K wrote:
>>
>> >-Original Message-
>> >From: Zanussi, Tom
>> >Sent: Friday, October 19, 2012 11:35 AM
>> >To: Bodke, Kishore K
>> >Cc: Kamble, Nitin A; yocto@yoctoproject.org
>> >Subject: Re: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new
>recipe
>> >for Zlib qat_mem Module.
>> >
>> >Hi Kishore,
>> >
>> >I've built these and they look ok as far as that goes.
>> >
>> >But I'm wondering, which kernel did you test with and which kernel(s)
>> >are these modules designed for i.e. will they work with all the kernels
>> >supported for 1.3?
>>
>> Hi Tom,
>>
>> I have tested them for 3.4 Kernel for Yocto, since for Crystal Forest we only
>have 3.4 for now.
>> Apart from that, it should work with all the kernel versions.
>> I have tested 3.0 and 3.5 on Fedora.
>>
>
>OK, for something in common, we have to think about someone using them
>with any yocto kernel, not just 3.4.  Since you're saying they work with
>3.0, 3.4 and 3.5, I guess there's not too much risk that they'll break
>with 3.2.  If that's not the case, you should probably restrict them to
>your BSP (but we don't want multiple copies) either.
>
>The best thing would be to move them into the linux-yocto kernel(s) they
>have been tested with - that way users know those features work and are
>safe to use in their BSPs.
>

These modules just need the configured kernel for them to build with.
It is not specific to particular kernel version. 

Also, every time the Kernel version moves, this whole set needs to be moved too.
Instead have it in the BSP and we do not have to run around moving around with 
the different kernels.
Instead it is nice to have one copy in common.

Thanks
Kishore.

>Tom
>
>> Thanks
>> Kishore.
>>
>> >
>> >Tom
>> >
>> >On Fri, 2012-10-19 at 13:28 -0500, Bodke, Kishore K wrote:
>> >>
>> >> >-Original Message-
>> >> >From: Kamble, Nitin A
>> >> >Sent: Friday, October 19, 2012 11:28 AM
>> >> >To: Bodke, Kishore K; Zanussi, Tom; yocto@yoctoproject.org
>> >> >Subject: RE: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new
>> >recipe
>> >> >for Zlib qat_mem Module.
>> >> >
>> >> >Hi Kishore,
>> >> >  Same here, if it is not used by multiple BSPs yet, then it should go in
>the
>> >BSP
>> >> >specific layer.
>> >> >
>> >> Yes, these too will be used by both Crystal Forest and Rangely.
>> >>
>> >> Thanks
>> >> Kishore.
>> >>
>> >> >Thanks,
>> >> >Nitin
>> >> >
>> >> >
>> >> >> -Original Message-
>> >> >> From: Bodke, Kishore K
>> >> >> Sent: Thursday, October 18, 2012 11:19 AM
>> >> >> To: Zanussi, Tom; Kamble, Nitin A; yocto@yoctoproject.org
>> >> >> Cc: Bodke, Kishore K
>> >> >> Subject: [PATCH 1/3] [meta-intel] meta-intel/common:Add a new
>recipe
>> >for
>> >> >> Zlib qat_mem Module.
>> >> >>
>> >> >> From: Kishore Bodke 
>> >> >>
>> >> >> This adds a new recipe to build the Intel Quick Assist Technology
>Memory
>> >> >> Management Module for Zlib.
>> >> >>
>> >> >> Signed-off-by: Kishore Bodke 
>> >> >> ---
>> >> >>  .../zlib-qat-module/zlib-qat-module.bb |   52
>> >> >> 
>> >> >>  .../zlib-qat-module/zlib_qat_module.patch  |   43
>> >
>> >> >>  2 files changed, 95 insertions(+)
>> >> >>  create mode 100644 common/recipes-core/zlib-qat-module/zlib-qat-
>> >> >> module.bb
>> >> >>  create mode 100644 common/recipes-core/zlib-qat-module/zlib-qat-
>> >> >> module/zlib_qat_module.patch
>> >> >>
>> >> >> diff --git a/common/recipes-core/zlib-qat-module/zlib-qat-module.bb
>> >> >> b/common/recipes-core/zlib-qat

Re: [yocto] [PATCH 1/2] meta-intel: update kernel SRCREVs and pin LINUX_VERSION

[Bodke, Kishore K]

Why are we not doing this LINUX_VERSION for the RT Kernel bbappend files?

Thanks
Kishore.

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, October 29, 2012 4:12 PM
>To: yocto@yoctoproject.org; dvh...@linux.intel.com; Kamble, Nitin A; Bodke,
>Kishore K; Saxena, Rahul
>Cc: Zanussi, Tom
>Subject: [PATCH 1/2] meta-intel: update kernel SRCREVs and pin
>LINUX_VERSION
>
>From: Tom Zanussi 
>
>Update all the linux-yocto .bbappends with the latest kernel SRCREVs
>and add explicit LINUX_VERSIONs for the 1.3 release, to prevent a
>mismatch between the kernel version actually used in the machine
>branch vs the version the recipe uses for the kernel image, which can
>change with stable updates.
>
>Signed-off-by: Tom Zanussi 
>---
> meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend  |  2 ++
> meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend  |  6 --
> meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend| 10
>++
> meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend| 10
>++
> .../recipes-kernel/linux/linux-yocto_3.4.bbappend  | 10 ++
> meta-emenlow/recipes-kernel/linux/linux-yocto_3.2.bbappend |  6 --
> meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend |  6 --
> meta-fri2/recipes-kernel/linux/linux-yocto_3.2.bbappend| 10 ++
> meta-fri2/recipes-kernel/linux/linux-yocto_3.4.bbappend|  2 ++
> .../recipes-kernel/linux/linux-yocto_3.2.bbappend  |  2 ++
> .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |  6 --
> meta-romley/recipes-kernel/linux/linux-yocto_3.2.bbappend  |  6 --
> meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend|  6 --
> meta-sugarbay/recipes-kernel/linux/linux-yocto_3.4.bbappend|  6 --
> meta-sys940x/recipes-kernel/linux/linux-yocto_3.2.bbappend | 10
>++
> 15 files changed, 64 insertions(+), 34 deletions(-)
>
>diff --git a/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>b/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>index d4e2ee6..3b07968 100644
>--- a/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>+++ b/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>@@ -8,3 +8,5 @@ KERNEL_FEATURES_append_chiefriver = "
>features/amt/mei"
>
> SRCREV_machine_pn-linux-yocto_chiefriver ?=
>"56d1c9ec36287350d154a3abef339598ef4028c2"
> SRCREV_meta_pn-linux-yocto_chiefriver ?=
>"486f7aec824b4127e91ef53228823e996b3696f0"
>+
>+LINUX_VERSION = "3.2.18"
>diff --git a/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
>b/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
>index 413dc74..f023a54 100644
>--- a/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
>+++ b/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
>@@ -6,5 +6,7 @@ KBRANCH_chiefriver  = "standard/common-pc-
>64/chiefriver"
>
> KERNEL_FEATURES_append_chiefriver = " features/amt/mei"
>
>-SRCREV_machine_pn-linux-yocto_chiefriver ?=
>"449f7f520350700858f21a5554b81cc8ad23267d"
>-SRCREV_meta_pn-linux-yocto_chiefriver ?=
>"9e3bdb7344054264b750e53fbbb6394cc1c942ac"
>+SRCREV_machine_pn-linux-yocto_chiefriver ?=
>"218bd8d2022b9852c60d32f0d770931e3cf343e2"
>+SRCREV_meta_pn-linux-yocto_chiefriver ?=
>"68a635bf8dfb64b02263c1ac80c948647cc76d5f"
>+
>+LINUX_VERSION = "3.4.11"
>diff --git a/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
>b/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
>index fbe13a8..6478c6b 100644
>--- a/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
>+++ b/meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend
>@@ -8,8 +8,10 @@ COMPATIBLE_MACHINE_crownbay-noemgd =
>"crownbay-noemgd"
> KMACHINE_crownbay-noemgd  = "crownbay"
> KBRANCH_crownbay-noemgd  = "standard/default/crownbay"
>
>-SRCREV_machine_pn-linux-yocto_crownbay ?=
>"ddcccbf870485c835f9b4b94823ca0c4186d78df"
>-SRCREV_meta_pn-linux-yocto_crownbay ?=
>"07ee09b520579b9f29bd15fefb01fd28b34c6064"
>+SRCREV_machine_pn-linux-yocto_crownbay ?=
>"f5a22aa0b14bb998d88ad4732f85b66c347631f8"
>+SRCREV_meta_pn-linux-yocto_crownbay ?=
>"486f7aec824b4127e91ef53228823e996b3696f0"
>
>-SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?=
>"ddcccbf870485c835f9b4b94823ca0c4186d78df"
>-SRCREV_meta_pn-linux-yocto_crownbay-noemgd ?=
>"07ee09b520579b9f29bd15fefb01fd28b34c6064"
>+SRCREV_machine_pn-linux-yocto_crownbay-noemgd ?=
>"f5a22aa0b14bb998d88ad4732f85b66c347631f8

Re: [yocto] [PATCH 1/2] meta-intel: update kernel SRCREVs and pin LINUX_VERSION

[Bodke, Kishore K]

>-Original Message-
>From: Zanussi, Tom
>Sent: Monday, October 29, 2012 5:30 PM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org; dvh...@linux.intel.com; Kamble, Nitin A; Saxena,
>Rahul
>Subject: Re: [PATCH 1/2] meta-intel: update kernel SRCREVs and pin
>LINUX_VERSION
>
>On Mon, 2012-10-29 at 18:57 -0500, Bodke, Kishore K wrote:
>> Why are we not doing this LINUX_VERSION for the RT Kernel bbappend
>files?
>>
>
>Oh, did I miss something?  The rt recipes I looked at didn't define any
>SRCREVs...
>
>But if you want to change that, sure, go ahead and send a patch...
>
Yeah, I have them for Crystal Forest, but I don't see these in all BSPs.
May be I can send a patch for the Crystal Forest?

Thanks
Kishore.

>Thanks,
>
>Tom
>
>> Thanks
>> Kishore.
>>
>> >-Original Message-
>> >From: Zanussi, Tom
>> >Sent: Monday, October 29, 2012 4:12 PM
>> >To: yocto@yoctoproject.org; dvh...@linux.intel.com; Kamble, Nitin A;
>Bodke,
>> >Kishore K; Saxena, Rahul
>> >Cc: Zanussi, Tom
>> >Subject: [PATCH 1/2] meta-intel: update kernel SRCREVs and pin
>> >LINUX_VERSION
>> >
>> >From: Tom Zanussi 
>> >
>> >Update all the linux-yocto .bbappends with the latest kernel SRCREVs
>> >and add explicit LINUX_VERSIONs for the 1.3 release, to prevent a
>> >mismatch between the kernel version actually used in the machine
>> >branch vs the version the recipe uses for the kernel image, which can
>> >change with stable updates.
>> >
>> >Signed-off-by: Tom Zanussi 
>> >---
>> > meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend  |  2 ++
>> > meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend  |  6
>--
>> > meta-crownbay/recipes-kernel/linux/linux-yocto_3.2.bbappend| 10
>> >++
>> > meta-crownbay/recipes-kernel/linux/linux-yocto_3.4.bbappend| 10
>> >++
>> > .../recipes-kernel/linux/linux-yocto_3.4.bbappend  | 10 
>> > ++
>> > meta-emenlow/recipes-kernel/linux/linux-yocto_3.2.bbappend |  6
>--
>> > meta-emenlow/recipes-kernel/linux/linux-yocto_3.4.bbappend |  6
>--
>> > meta-fri2/recipes-kernel/linux/linux-yocto_3.2.bbappend| 10
>++
>> > meta-fri2/recipes-kernel/linux/linux-yocto_3.4.bbappend|  2 ++
>> > .../recipes-kernel/linux/linux-yocto_3.2.bbappend  |  2 ++
>> > .../recipes-kernel/linux/linux-yocto_3.4.bbappend  |  6 --
>> > meta-romley/recipes-kernel/linux/linux-yocto_3.2.bbappend  |  6 -
>-
>> > meta-sugarbay/recipes-kernel/linux/linux-yocto_3.2.bbappend|  6
>--
>> > meta-sugarbay/recipes-kernel/linux/linux-yocto_3.4.bbappend|  6
>--
>> > meta-sys940x/recipes-kernel/linux/linux-yocto_3.2.bbappend | 10
>> >++
>> > 15 files changed, 64 insertions(+), 34 deletions(-)
>> >
>> >diff --git a/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>> >b/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>> >index d4e2ee6..3b07968 100644
>> >--- a/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>> >+++ b/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.2.bbappend
>> >@@ -8,3 +8,5 @@ KERNEL_FEATURES_append_chiefriver = "
>> >features/amt/mei"
>> >
>> > SRCREV_machine_pn-linux-yocto_chiefriver ?=
>> >"56d1c9ec36287350d154a3abef339598ef4028c2"
>> > SRCREV_meta_pn-linux-yocto_chiefriver ?=
>> >"486f7aec824b4127e91ef53228823e996b3696f0"
>> >+
>> >+LINUX_VERSION = "3.2.18"
>> >diff --git a/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
>> >b/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
>> >index 413dc74..f023a54 100644
>> >--- a/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
>> >+++ b/meta-chiefriver/recipes-kernel/linux/linux-yocto_3.4.bbappend
>> >@@ -6,5 +6,7 @@ KBRANCH_chiefriver  = "standard/common-pc-
>> >64/chiefriver"
>> >
>> > KERNEL_FEATURES_append_chiefriver = " features/amt/mei"
>> >
>> >-SRCREV_machine_pn-linux-yocto_chiefriver ?=
>> >"449f7f520350700858f21a5554b81cc8ad23267d"
>> >-SRCREV_meta_pn-linux-yocto_chiefriver ?=
>> >"9e3bdb7344054264b750e53fbbb6394cc1c942ac"
>> >+SRCREV_machine_pn-linux-yocto_chiefriver ?=
>> >"218bd8d2022b9852c60d

Re: [yocto] [PATCH 1/1] [meta-intel] meta-intel/common: Add License info for openssl-qat-module

[Bodke, Kishore K]

>-Original Message-
>From: Flanagan, Elizabeth [mailto:elizabeth.flana...@intel.com]
>Sent: Tuesday, October 30, 2012 11:20 AM
>To: Bodke, Kishore K
>Cc: Zanussi, Tom; Kamble, Nitin A; yocto@yoctoproject.org
>Subject: Re: [yocto] [PATCH 1/1] [meta-intel] meta-intel/common: Add
>License info for openssl-qat-module
>
>On Tue, Oct 30, 2012 at 10:11 AM,   wrote:
>> From: Kishore Bodke 
>>
>> openssl-qat-module has the dual license. So add GPLv2 and BSD
>> License to openssl qat Module.
>>
>> Signed-off-by: Kishore Bodke 
>> ---
>>  .../openssl-qat-module/openssl-qat-module.bb   |6 --
>>  1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/common/recipes-connectivity/openssl-qat-module/openssl-qat-
>module.bb b/common/recipes-connectivity/openssl-qat-module/openssl-
>qat-module.bb
>> index a4fe3c5..fdeebbb 100644
>> --- a/common/recipes-connectivity/openssl-qat-module/openssl-qat-
>module.bb
>> +++ b/common/recipes-connectivity/openssl-qat-module/openssl-qat-
>module.bb
>> @@ -7,8 +7,10 @@ implemented on Intel Communications Chipset 89xx
>Series based platforms."
>>  HOMEPAGE = "http://www.openssl.org/";
>>  SECTION = "libs/network"
>>
>> -LICENSE = "openssl"
>> -LIC_FILES_CHKSUM = "file://${WORKDIR}/openssl-
>${PV}/LICENSE;md5=f9a8f968107345e0b75aa8c2ecaa7ec8"
>> +LICENSE = "openssl & GPLv2 & BSD"
>
>I'd actually make this:
>
>LICENSE = "OpenSSL & GPLv2 & BSD"
>
>as there is no SPDXLICENSEMAP to map openssl to OpenSSL, so this
>should be throwing warnings.
>

I see LICENSE = "openssl" in poky/meta/recipes-connectivity/openssl/openssl.inc.
So I followed the same here.

Thanks
Kishore.

>> +LIC_FILES_CHKSUM = "file://${WORKDIR}/openssl-
>${PV}/LICENSE;md5=f9a8f968107345e0b75aa8c2ecaa7ec8 \
>> +   file://${COMMON_LICENSE_DIR}/GPL-
>2.0;md5=801f80980d171dd6425610833a22dbe6 \
>> +
>file://${COMMON_LICENSE_DIR}/BSD;md5=3775480a712fc46a69647678acb23
>4cb"
>>
>>  PV = "1.0.1"
>>  PR = "r0"
>> --
>> 1.7.9.5
>>
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>--
>Elizabeth Flanagan
>Yocto Project
>Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH meta-intel] meta-cedartrail: really fix mesa-dri version (typo'd)

[Bodke, Kishore K]

Is this patch for danny?

-Kishore.

>-Original Message-
>From: Ross Burton [mailto:ross.bur...@intel.com]
>Sent: Monday, November 05, 2012 4:31 AM
>To: Bodke, Kishore K
>Cc: yocto@yoctoproject.org
>Subject: [PATCH meta-intel] meta-cedartrail: really fix mesa-dri version
>(typo'd)
>
>Signed-off-by: Ross Burton 
>---
> meta-cedartrail/conf/machine/cedartrail.conf |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/meta-cedartrail/conf/machine/cedartrail.conf b/meta-
>cedartrail/conf/machine/cedartrail.conf
>index aa2a46a..a5fa0f0 100644
>--- a/meta-cedartrail/conf/machine/cedartrail.conf
>+++ b/meta-cedartrail/conf/machine/cedartrail.conf
>@@ -17,7 +17,7 @@ XSERVER ?= "${XSERVER_IA32_BASE} \
>"
> PREFERRED_VERSION_linux-yocto ?= "3.0%"
> PREFERRED_VERSION_xserver-xorg ?= "1.9.3"
>-PREFERRED_VERSION_mesa-dri ?= "8.04"
>+PREFERRED_VERSION_mesa-dri ?= "8.0.4"
> PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0"
>
> SYSLINUX_OPTS = "serial 0 115200"
>--
>1.7.10

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