Re: [yocto] [Yocto] Build Failure in beecrypt-4.2.1-r1 package with poky-1.2_M4.rc2 on Open Suse 12.1

[Ashish Pandey]

I have installed java-1.6.0-openjdk and then build again and build was 
successful. 
I think , It should give package dependency error instead of  compilation 
error. 
Please give your suggestion on this ? 

Regards,

Ashish

Huawei Technology



This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
e-mail in error, please notify the sender by phone or email immediately and 
delete it!


From: Khem Raj [raj.k...@gmail.com]
Sent: 09 April 2012 11:08:57
To: Ashish Pandey
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [Yocto] Build Failure in beecrypt-4.2.1-r1 package with 
poky-1.2_M4.rc2 on Open Suse 12.1

On Sun, Apr 8, 2012 at 9:07 PM, Ashish Pandey  wrote:
>
>  I tried woth " --disable-java" option but it is giving same error.
> Please check once again and help me to build.

post your configure logs somewhere disabling java should have disabled
any JNI detection
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] managing layer priorities

[Gary Thomas]

On 2012-04-09 00:18, Tomas Frydrych wrote:

On 08/04/12 23:28, Tomas Frydrych wrote:

Is there a way to change the priority that a layer assigns itself in its
layer.conf? E.g., I want to add meta-oe alongside of meta-yocto, but I
want it to have a lower priority than the latter. Currently meta-yocto
gives itself "5" and meta-oe "6", I'd like to change this without having
to modify meta-oe/conf/layer.conf, but can't find a way to do this.


Never mind, it is possible to override these in the last layer listed in
BBLAYERS.


How so?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] managing layer priorities

[Tomas Frydrych]

On 09/04/12 14:04, Gary Thomas wrote:
> On 2012-04-09 00:18, Tomas Frydrych wrote:
>> On 08/04/12 23:28, Tomas Frydrych wrote:
>>> Is there a way to change the priority that a layer assigns itself in its
>>> layer.conf? E.g., I want to add meta-oe alongside of meta-yocto, but I
>>> want it to have a lower priority than the latter. Currently meta-yocto
>>> gives itself "5" and meta-oe "6", I'd like to change this without having
>>> to modify meta-oe/conf/layer.conf, but can't find a way to do this.
>>
>> Never mind, it is possible to override these in the last layer listed in
>> BBLAYERS.
> 
> How so?

You can set the various BBFILE_PRIORITY_ and other variables in the
layer.conf for the last layer listed in your bblayers.conf. The layer
priorities get evaluated only after all of the layer.conf files have
been parsed, so anything that is set in the last layer.conf will be the
final value. I use the Yocto model where (unlike with OE layers) the
layer.conf prepends its layer path to BBPATH, so my custom layer is
last, but I imagine it would be possible to create a fake layer with no
recipes just for this specific purpose.

Tomas

> 

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

Re: [yocto] managing layer priorities

[Paul Eggleton]

On Monday 09 April 2012 14:58:49 Tomas Frydrych wrote:
> On 09/04/12 14:04, Gary Thomas wrote:
> > On 2012-04-09 00:18, Tomas Frydrych wrote:
> >> On 08/04/12 23:28, Tomas Frydrych wrote:
> >>> Is there a way to change the priority that a layer assigns itself in its
> >>> layer.conf? E.g., I want to add meta-oe alongside of meta-yocto, but I
> >>> want it to have a lower priority than the latter. Currently meta-yocto
> >>> gives itself "5" and meta-oe "6", I'd like to change this without having
> >>> to modify meta-oe/conf/layer.conf, but can't find a way to do this.
> >> 
> >> Never mind, it is possible to override these in the last layer listed in
> >> BBLAYERS.
> > 
> > How so?
> 
> You can set the various BBFILE_PRIORITY_ and other variables in the
> layer.conf for the last layer listed in your bblayers.conf. The layer
> priorities get evaluated only after all of the layer.conf files have
> been parsed, so anything that is set in the last layer.conf will be the
> final value. I use the Yocto model where (unlike with OE layers) the
> layer.conf prepends its layer path to BBPATH, so my custom layer is
> last, but I imagine it would be possible to create a fake layer with no
> recipes just for this specific purpose.

I realise what you're trying to do, but you should bear in mind when you do 
this you are relying on unintentional behaviour that may change in future.

There were some discussions at the recent BSP summit about improving bitbake 
so that layer priorities work in a more helpful manner. Also worth noting is 
that work to split up meta-oe is ongoing, so it may be in the near future that 
you don't have to shuffle layers around such that meta-oe doesn't have any 
undesired effects.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] managing layer priorities

[Tomas Frydrych]

Hi Paul,

On 09/04/12 15:09, Paul Eggleton wrote:
> On Monday 09 April 2012 14:58:49 Tomas Frydrych wrote:
> I realise what you're trying to do, but you should bear in mind when you do 
> this you are relying on unintentional behaviour that may change in future.

I am not sure whether unintentional is an accurate description; layer
priority is explicitly and intentionally the function of other layers
due to inter-layer dependency. So I prefer to think of it as an
undocumented feature. :-) But I know, if it does not work, it's my own
fault.

The reason for doing this is that I'd like to be able to treat an
external layer as a read-only entity, and to enforce this. My experience
suggests that if you fork external layers alongside your custom layers,
this over time leads to unnecessary maintenance costs. On the other
hand, if each external layer is a read-only entity, it can be integrated
as a read-only git submodule, and no naughty developers will then make
changes to it.

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

[yocto] Yocto weekly bug trend charts -- WW14

[Xu, Jiajun]

Hi all,
This is the weekly bug trend for WW14. The new submitted vs. fixed bug 
number is 42 vs. 32. By comparing with WW13, open bug number for "Critical", 
"Major" and "Normal" increased a lot. WDD number and Open Bug number are 955 
and 187. Bug status of WW14 could be found on 
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend.

Best Regards,
Jiajun


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

Re: [yocto] Porting of specific Kernel/Driver into yocto.

[Om Prakash PAL]

Hi Bruce,
Thanks for you help.
As you have mentioned, its working properly.
I want to know that is there any better way of doing same thing for my scenario 
?:
here is my scenario:
We have development branch where we write/modify our kernel/driver code i.e. 
thats our local kernel repository(git rep)
and lots of driver/files being modified everyday-->so I have to take the same 
effect into yocto kernel also> so except  creating patches for all modified 
drivers and creating .bbappend files, is there any better way of doing same 
thing .  

Is there anyway that  instead of using yocto-kernel tree,  can we use our local 
kernel-tree for building images?. (should  I create separate BSP ?)

Thanks in advance.
Best Regards,
Om Prakash Pal

From: Bruce Ashfield [bruce.ashfi...@windriver.com]
Sent: Monday, April 09, 2012 9:32 AM
To: Om Prakash PAL
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.

On 12-04-08 10:04 AM, Om Prakash PAL wrote:
> Hi Bruce,
> Thanks for your reply.
> I am totally new to Yocto.
> I have gone through the section BSP/Linux kernel configuration and if I am 
> not wrong then it explains how can we configure the kernel, not the how we 
> can add/replace a  component(driver etc).
> lets take the example of UART driver, I want to add my own UART driver code.
> Should I write a separate recipe file (.bb) for UART Driver?.
> if yes then I have to write the recipe files for all my drivers that will be 
> very time consuming.
> Is there any other way that I can port all my desired drivers into Yocto 
> kernel?.

No recipes are required per-driver, unless you are building them all
as out of tree modules.

The typical way this is done is to simply work in the extracted linux
src tree (build/tmp/work//linux-yocto-/linux), manually
patch, or copy your drivers into the tree. At this point, you'll port
the drivers, doing test builds (bitbake -f -c compile linux-yocto) to
ensure that your port is working. When you've completed the build phase,
boot tests would be in order. (Do not do a 'clean' or you'll lose in
progress changes).

When you are happy with the changes, the directory where you were working
is with the kernel git repository. So you can simply commit your
changes, and generate patches.

git format-patch -o  HEAD^ (or however many commits
you have)

Take those patches, create a layer with a bbappend and add them like
any other patch to any package. They'll be applied to subsequent builds
of the kernel.

I'm skipping a lot of detail there, but it is all found in the various
manuals, and I don't want to repeat it here.

Cheers,

Bruce

> Please help me.
> Thanks a lot in advance.
>
> Best Regards,
> Om Prakash Pal
> 
> From: Bruce Ashfield [bruce.ashfi...@windriver.com]
> Sent: Wednesday, April 04, 2012 6:17 PM
> To: Om Prakash PAL
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>
> On 12-04-04 04:46 AM, Om Prakash PAL wrote:
>> Hi,
>> I want to build my local kernel/Driver code, not the default one.
>> please help how can i do it ?.
>> any wiki/docs on this?.
>
> The BSP developer guides show how to extend the yocto kernels, and
> also have sections on custom/different kernel versions. Have you
> seen that doc yet ? Or have you seen it, and have specific questions ?
>
> Bruce
>
>>
>> Best Regards,
>> Om Prakash Pal
>> ___
>> 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] sato: Remove questioned ISO image

[Darren Hart]

On 03/26/2012 02:19 PM, Yang Shi wrote:
> [YOCTO #1487]
> 
> For the liveCD image, interactive bootup is needed, but psplash prevents from
> booting interactively. In such case ISO image is not usable, so remove ISO 
> image
> and the corresponding link and throw error info to warn outside to enable
> unionfs in kenrel.


The psplash only prevents interaction on the vga console right? If the
BSP supports a serial console as well there is not a problem right?

--
Darren

> 
> Signed-off-by: Yang Shi 
> ---
>  meta/recipes-sato/images/core-image-sato.bb |   16 
>  1 files changed, 16 insertions(+), 0 deletions(-)
> 
> diff --git a/meta/recipes-sato/images/core-image-sato.bb 
> b/meta/recipes-sato/images/core-image-sato.bb
> index 11c3318..10e2239 100644
> --- a/meta/recipes-sato/images/core-image-sato.bb
> +++ b/meta/recipes-sato/images/core-image-sato.bb
> @@ -9,3 +9,19 @@ IMAGE_FEATURES += "apps-console-core ${SATO_IMAGE_FEATURES}"
>  LICENSE = "MIT"
>  
>  inherit core-image
> +
> +LIVE = "${@base_contains('IMAGE_FSTYPES', 'live', 'yes', 'no', d)}"
> +
> +do_check_unionfs() {
> +if [ "${NOISO}" = "1" ]; then
> +return
> +fi
> +
> +if [ "${LIVE}" = "yes" ] && ! grep -q "CONFIG_UNION_FS=y" 
> ${STAGING_KERNEL_DIR}/.config; then
> +rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.iso
> +rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso
> +bbfatal "Building LIVE CD without UNION FS enabled in kernel"
> +fi
> +}
> +
> +addtask check_unionfs before do_build after do_bootimg

-- 
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] initrdscripts: fix init-live.sh and use unionfs

[Darren Hart]

On 03/26/2012 02:19 PM, Yang Shi wrote:
> [YOCTO #1487]
> 
> Use unionfs to mount rootfs and make root file system can be writen when 
> using liveCD to boot up.
> Set UNION_FS variable depending on kenrel config, so that it can work with 
> kernel which doesn't

s/kenrel/kernel/

> have unionfs feature.

This doesn't explain what the problem was. Someone reading this commit
message would not know WHY this change was needed.

The approach looks good though. Minor spelling issues below...

> 
> Signed-off-by: Yang Shi 
> ---
>  meta/recipes-core/initrdscripts/files/init-live.sh |   21 +--
>  .../initrdscripts/initramfs-live-boot_1.0.bb   |9 +++-
>  2 files changed, 26 insertions(+), 4 deletions(-)
> 
> diff --git a/meta/recipes-core/initrdscripts/files/init-live.sh 
> b/meta/recipes-core/initrdscripts/files/init-live.sh
> index eb5ab5b..abaf16c 100644
> --- a/meta/recipes-core/initrdscripts/files/init-live.sh
> +++ b/meta/recipes-core/initrdscripts/files/init-live.sh
> @@ -7,6 +7,7 @@ ROOT_IMAGE="rootfs.img"
>  MOUNT="/bin/mount"
>  UMOUNT="/bin/umount"
>  ISOLINUX=""
> +UNIONFS="no"
>  
>  early_setup() {
>  mkdir /proc
> @@ -89,10 +90,24 @@ case $label in
>   mkdir $ROOT_MOUNT
>   mknod /dev/loop0 b 7 0 2>/dev/null
>  
> - if ! $MOUNT -o rw,loop,noatime,nodiratime 
> /media/$i/$ISOLINUX/$ROOT_IMAGE $ROOT_MOUNT ; then
> - fatal "Couldnt mount rootfs image"

s/Couldnt/Could not/

> + 
> + if [ "$UNIONFS" = "yes" ]; then
> + mkdir /rootfs-tmp
> +
> + if ! $MOUNT -o rw,loop,noatime,nodiratime 
> /media/$i/$ISOLINUX/$ROOT_IMAGE /rootfs-tmp ; then
> + fatal "Couldnt mount rootfs image"

s/Couldnt/Could not/

> + else
> + mkdir /cow
> + mount -t tmpfs -o rw,noatime,mode=755 tmpfs /cow
> + mount -t unionfs -o dirs=/cow:/rootfs-tmp=ro unionfs $ROOT_MOUNT
> + boot_live_root
> + fi
>   else
> - boot_live_root
> + if ! $MOUNT -o rw,loop,noatime,nodiratime 
> /media/$i/$ISOLINUX/$ROOT_IMAGE $ROOT_MOUNT ; then
> + fatal "Couldnt mount rootfs image"

s/Couldnt/Could not/

> + else
> + boot_live_root
> + fi
>   fi
>   ;;
>  install)
> diff --git a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb 
> b/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
> index e85a0e1..f7f0c9d 100644
> --- a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
> +++ b/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
> @@ -2,10 +2,17 @@ DESCRIPTION = "A live image init script"
>  LICENSE = "MIT"
>  LIC_FILES_CHKSUM = 
> "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
>  RDEPENDS = "udev"
> +DEPENDS = "virtual/kernel"
>  SRC_URI = "file://init-live.sh"
>  
> -PR = "r7"
> +PR = "r8"
>  
> +do_compile() {
> + if grep -q "CONFIG_UNION_FS=y" ${STAGING_KERNEL_DIR}/.config; then
> + sed -i 's/UNIONFS="no"/UNIONFS="yes"/g' ${WORKDIR}/init-live.sh
> + fi
> +}
> + 
>  do_install() {
>  install -m 0755 ${WORKDIR}/init-live.sh ${D}/init
>  }

-- 
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] Porting of specific Kernel/Driver into yocto.

[Bruce Ashfield]

On Mon, Apr 9, 2012 at 12:31 PM, Om Prakash PAL
 wrote:
> Hi Bruce,
> Thanks for you help.
> As you have mentioned, its working properly.
> I want to know that is there any better way of doing same thing for my 
> scenario ?:
> here is my scenario:
> We have development branch where we write/modify our kernel/driver code i.e. 
> thats our local kernel repository(git rep)
> and lots of driver/files being modified everyday-->so I have to take the same 
> effect into yocto kernel also> so except  creating patches for all 
> modified drivers and creating .bbappend files, is there any better way of 
> doing same thing .

Aha. Missed that.

Just create a simple recipe that points at your git repository in the SRC_URI.
If all the changes are in the tree, and you have a defconfig and you
are building
the master branch. Then pretty much everything you need can be specified in
the SRC_URI .. and that's the entire recipe.

If you look in oe-classic, meta-ti or any one of a number of other
layers, you'll
find recipes that do just that.

The meta-kernel-dev (in the poky extras) layer has an example of using the
kernel.org tree with the yocto kern tools, and once yocto 1.3 opens up for
submissions, I have a set of changes prep'd that make it relatively simple to
use the yocto kern tools against different types of repository.

So the summary is: Depending on the type of tooling you need, and what baseline
you need for your work .. there are a number of ways to do things.

>
> Is there anyway that  instead of using yocto-kernel tree,  can we use our 
> local kernel-tree for building images?. (should  I create separate BSP ?)

You should definitely create a BSP, that way you can tune the system specific
to your board,

Cheers,

Bruce

>
> Thanks in advance.
> Best Regards,
> Om Prakash Pal
> 
> From: Bruce Ashfield [bruce.ashfi...@windriver.com]
> Sent: Monday, April 09, 2012 9:32 AM
> To: Om Prakash PAL
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>
> On 12-04-08 10:04 AM, Om Prakash PAL wrote:
>> Hi Bruce,
>> Thanks for your reply.
>> I am totally new to Yocto.
>> I have gone through the section BSP/Linux kernel configuration and if I am 
>> not wrong then it explains how can we configure the kernel, not the how we 
>> can add/replace a  component(driver etc).
>> lets take the example of UART driver, I want to add my own UART driver code.
>> Should I write a separate recipe file (.bb) for UART Driver?.
>> if yes then I have to write the recipe files for all my drivers that will be 
>> very time consuming.
>> Is there any other way that I can port all my desired drivers into Yocto 
>> kernel?.
>
> No recipes are required per-driver, unless you are building them all
> as out of tree modules.
>
> The typical way this is done is to simply work in the extracted linux
> src tree (build/tmp/work//linux-yocto-/linux), manually
> patch, or copy your drivers into the tree. At this point, you'll port
> the drivers, doing test builds (bitbake -f -c compile linux-yocto) to
> ensure that your port is working. When you've completed the build phase,
> boot tests would be in order. (Do not do a 'clean' or you'll lose in
> progress changes).
>
> When you are happy with the changes, the directory where you were working
> is with the kernel git repository. So you can simply commit your
> changes, and generate patches.
>
>    git format-patch -o  HEAD^ (or however many commits
> you have)
>
> Take those patches, create a layer with a bbappend and add them like
> any other patch to any package. They'll be applied to subsequent builds
> of the kernel.
>
> I'm skipping a lot of detail there, but it is all found in the various
> manuals, and I don't want to repeat it here.
>
> Cheers,
>
> Bruce
>
>> Please help me.
>> Thanks a lot in advance.
>>
>> Best Regards,
>> Om Prakash Pal
>> 
>> From: Bruce Ashfield [bruce.ashfi...@windriver.com]
>> Sent: Wednesday, April 04, 2012 6:17 PM
>> To: Om Prakash PAL
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
>>
>> On 12-04-04 04:46 AM, Om Prakash PAL wrote:
>>> Hi,
>>> I want to build my local kernel/Driver code, not the default one.
>>> please help how can i do it ?.
>>> any wiki/docs on this?.
>>
>> The BSP developer guides show how to extend the yocto kernels, and
>> also have sections on custom/different kernel versions. Have you
>> seen that doc yet ? Or have you seen it, and have specific questions ?
>>
>> Bruce
>>
>>>
>>> Best Regards,
>>> Om Prakash Pal
>>> ___
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and ma

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

[Tom Zanussi]

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).

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.

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?

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
>  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
>  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
>  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
> 


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

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

[Tom Zanussi]

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.

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

> 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/license.txt"
> +FILES_${PN} += "${datadir}/doc/pvr-bin-cdv-1.7.788837_05/license.txt"
> +
> +
> +
> diff --git 
> a/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.bb 
> b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.bb
> new file mode 100644
> index 000..496da1e
> --- /dev/null
> +++ b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-driver_1.0.bb
> @@ -0,0 +1,101 @@
> +require cdv-pvr-driver.inc
> +
> +PR = "${INC_PR}.0"
> +
> +DEPENDS = "libva"
> +
> +SRC_URI = 
> "${MEEGO_MIRROR}/non-oss/MeeGo_1.2.0_CedarTrail/i586/psb-video-cdv-0.12-1.1.i586.rpm;name=psbrpm
>  \ 
> +
> ${MEEGO_MIRROR}/oss/standard/i586/libwsbm-cdv-1.1.0-3.1.i586.rpm;name=wsbmrpm 
> \
> +
> ${MEEGO_MIRROR}/non-oss/MeeGo_1.2.0_CedarTrail/i586/pvr-bin-cdv-1.7.788837_05-1.1.i586.rpm;name=pvrrpm
>  \
> +   "
> +
> +SRC_URI[pvrrpm.md5sum] = "951fa9edcbc2a3ddb30450079869362e"
> +SRC_URI[pvrrpm.sha256sum] = 
> "537dd8a98ac2e3a101063abc62682c3be8c37ac29782a876eafce113ffa5b421"
> +
> +SRC_URI[psbrpm.md5sum] =  "d4b6b383722264f3b781aeb240c88037"
> +SRC_URI[psbrpm.sha256sum] = 
> "e88f95fc73a79adf76ee33d3d9874cec23bb1afe8149d7dc584

[yocto] [PATCH 0/1] meta-skeleton: Move hello-mod example kernel module to meta-skeleton

[Darren Hart]

The following changes since commit 190f6d791d51aaa4cfb9f1cf932bc205ff674fb5:

  runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:47 
+0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib dvhart/skeleton
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/skeleton

Darren Hart (1):
  meta-skeleton: Move hello-mod example kernel module to meta-skeleton

 .../recipes-kernel/hello-mod/files/COPYING |  340 
 .../recipes-kernel/hello-mod/files/Makefile|   14 +
 .../recipes-kernel/hello-mod/files/hello.c |   33 ++
 .../recipes-kernel/hello-mod/hello-mod_0.1.bb  |   15 +
 4 files changed, 402 insertions(+), 0 deletions(-)
 create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/COPYING
 create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/Makefile
 create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/hello.c
 create mode 100644 meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb

-- 
1.7.5.4

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

[yocto] [PATCH 1/1] meta-skeleton: Move hello-mod example kernel module to meta-skeleton

[Darren Hart]

Fixes [YOCTO #1501]

hello-mod is an example kernel module, and does not provide any real
functionality. As such, it would be better placed under meta-skeleton than in
meta.

I am posting a separate patch to oe-core removing hello-mod.

Signed-off-by: Darren Hart 
---
 .../recipes-kernel/hello-mod/files/COPYING |  340 
 .../recipes-kernel/hello-mod/files/Makefile|   14 +
 .../recipes-kernel/hello-mod/files/hello.c |   33 ++
 .../recipes-kernel/hello-mod/hello-mod_0.1.bb  |   15 +
 4 files changed, 402 insertions(+), 0 deletions(-)
 create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/COPYING
 create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/Makefile
 create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/hello.c
 create mode 100644 meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb

diff --git a/meta-skeleton/recipes-kernel/hello-mod/files/COPYING 
b/meta-skeleton/recipes-kernel/hello-mod/files/COPYING
new file mode 100644
index 000..6d45519
--- /dev/null
+++ b/meta-skeleton/recipes-kernel/hello-mod/files/COPYING
@@ -0,0 +1,340 @@
+   GNU GENERAL PUBLIC LICENSE
+  Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+   51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+   Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+   GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running t

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

[Tom Zanussi]

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...

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.ogg
>  \
> +"
> +
> +
> +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

[yocto] Yocto Project 1.2 M4 schedule

[Liu, Song]

Hi all,

This is to restate and clarify the schedule for Yocto Project 1.2 M4 (milestone 
4). If you are concerned or have patches you would like to merge, please see 
the following dates:


1.   RC3 official patch cut-off time: 12:00AM April 8th, 2012, PDT

2.   RC3 build: April 11th, 2012, PDT

3.   RC4 official patch cut-off time: 12:00AM April 15th, 2012, PDT

4.   RC4 build: April 18th, 2012, PDT

5.   YP 1.2 release: April 27th, 2012, PDT

You can also check out the schedule here: 
https://www.google.com/calendar/embed?height=600&wkst=1&bgcolor=%23FF&src=mg0m150m30gs891eqqhtfu5jgg%40group.calendar.google.com&color=%238C500B&src=sc7rov4ck552t2f0pav120t7r0%40group.calendar.google.com&color=%23528800&src=theyoctoproject%40gmail.com&color=%23182C57&ctz=America%2FLos_Angeles

Please feel free to let me and Beth know if you have any concerns or questions.

Thanks!
Song
PM, Yocto Project
___
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.

[Tom Zanussi]

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?

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.

[Tom Zanussi]

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).

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.

[Tom Zanussi]

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.

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 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
>>  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
>>  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/bigbu

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/license.txt"
>> +FILES_${PN} += "${datadir}/doc/pvr-bin-cdv-1.7.788837_05/license.txt"
>> +
>> +
>> +
>> diff --git a/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-
>driver_1.0.bb b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-
>driver_1.0.bb
>> new file mode 100644
>> index 000..496da1e
>> --- /dev/null
>> +++ b/meta-cedartrail/recipes-graphics/xorg-driver/cdv-pvr-
>driver_1.0.bb
>> @@ -0,0 +1,101 @@
>> +require cdv-pvr-driver.inc
>> +
>> +PR = "${INC_PR}.0"
>> +
>> +DEPENDS = "libva"
>> +
>> +SRC_URI = "${MEEGO_MIRROR}/non-oss/MeeGo_1.2.0_CedarTrail/i586/psb-
>video-cdv-0.12-1.1.i586.rpm;name=psbrpm \
>> +   ${MEEGO_MIRROR}/oss/standard/i586/libwsbm-cdv-1.1.0-
>3.1.i586.rpm;name=wsbmrpm \
>> +   ${MEEGO_MIRROR}/no

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 1/2] initrdscripts: fix init-live.sh and use unionfs

[Yang Shi]

On 4/9/2012 9:35 AM, Darren Hart wrote:


On 03/26/2012 02:19 PM, Yang Shi wrote:

[YOCTO #1487]

Use unionfs to mount rootfs and make root file system can be writen when using 
liveCD to boot up.
Set UNION_FS variable depending on kenrel config, so that it can work with 
kernel which doesn't

s/kenrel/kernel/


have unionfs feature.

This doesn't explain what the problem was. Someone reading this commit
message would not know WHY this change was needed.

The approach looks good though. Minor spelling issues below...


OK, thanks Darren. I will refine the log and fix the spelling errors soon.

Yang




Signed-off-by: Yang Shi
---
  meta/recipes-core/initrdscripts/files/init-live.sh |   21 +--
  .../initrdscripts/initramfs-live-boot_1.0.bb   |9 +++-
  2 files changed, 26 insertions(+), 4 deletions(-)

diff --git a/meta/recipes-core/initrdscripts/files/init-live.sh 
b/meta/recipes-core/initrdscripts/files/init-live.sh
index eb5ab5b..abaf16c 100644
--- a/meta/recipes-core/initrdscripts/files/init-live.sh
+++ b/meta/recipes-core/initrdscripts/files/init-live.sh
@@ -7,6 +7,7 @@ ROOT_IMAGE="rootfs.img"
  MOUNT="/bin/mount"
  UMOUNT="/bin/umount"
  ISOLINUX=""
+UNIONFS="no"

  early_setup() {
  mkdir /proc
@@ -89,10 +90,24 @@ case $label in
mkdir $ROOT_MOUNT
mknod /dev/loop0 b 7 0 2>/dev/null

-   if ! $MOUNT -o rw,loop,noatime,nodiratime 
/media/$i/$ISOLINUX/$ROOT_IMAGE $ROOT_MOUNT ; then
-   fatal "Couldnt mount rootfs image"

s/Couldnt/Could not/


+   
+   if [ "$UNIONFS" = "yes" ]; then
+   mkdir /rootfs-tmp
+
+   if ! $MOUNT -o rw,loop,noatime,nodiratime 
/media/$i/$ISOLINUX/$ROOT_IMAGE /rootfs-tmp ; then
+   fatal "Couldnt mount rootfs image"

s/Couldnt/Could not/


+   else
+   mkdir /cow
+   mount -t tmpfs -o rw,noatime,mode=755 tmpfs /cow
+   mount -t unionfs -o dirs=/cow:/rootfs-tmp=ro unionfs $ROOT_MOUNT
+   boot_live_root
+   fi
else
-   boot_live_root
+   if ! $MOUNT -o rw,loop,noatime,nodiratime 
/media/$i/$ISOLINUX/$ROOT_IMAGE $ROOT_MOUNT ; then
+   fatal "Couldnt mount rootfs image"

s/Couldnt/Could not/


+   else
+   boot_live_root
+   fi
fi
;;
  install)
diff --git a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb 
b/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
index e85a0e1..f7f0c9d 100644
--- a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
+++ b/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
@@ -2,10 +2,17 @@ DESCRIPTION = "A live image init script"
  LICENSE = "MIT"
  LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
  RDEPENDS = "udev"
+DEPENDS = "virtual/kernel"
  SRC_URI = "file://init-live.sh"

-PR = "r7"
+PR = "r8"

+do_compile() {
+   if grep -q "CONFIG_UNION_FS=y" ${STAGING_KERNEL_DIR}/.config; then
+   sed -i 's/UNIONFS="no"/UNIONFS="yes"/g' ${WORKDIR}/init-live.sh
+   fi
+}
+
  do_install() {
  install -m 0755 ${WORKDIR}/init-live.sh ${D}/init
  }


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

Re: [yocto] [PATCH 2/2] sato: Remove questioned ISO image

[Yang Shi]

On 4/9/2012 9:31 AM, Darren Hart wrote:


On 03/26/2012 02:19 PM, Yang Shi wrote:

[YOCTO #1487]

For the liveCD image, interactive bootup is needed, but psplash prevents from
booting interactively. In such case ISO image is not usable, so remove ISO image
and the corresponding link and throw error info to warn outside to enable
unionfs in kenrel.


The psplash only prevents interaction on the vga console right? If the
BSP supports a serial console as well there is not a problem right?


Yes, I think so. When I was doing the test, I disabled splash so that I 
can type 'enter' to make interaction move forward.


Thanks,
Yang



--
Darren


Signed-off-by: Yang Shi
---
  meta/recipes-sato/images/core-image-sato.bb |   16 
  1 files changed, 16 insertions(+), 0 deletions(-)

diff --git a/meta/recipes-sato/images/core-image-sato.bb 
b/meta/recipes-sato/images/core-image-sato.bb
index 11c3318..10e2239 100644
--- a/meta/recipes-sato/images/core-image-sato.bb
+++ b/meta/recipes-sato/images/core-image-sato.bb
@@ -9,3 +9,19 @@ IMAGE_FEATURES += "apps-console-core ${SATO_IMAGE_FEATURES}"
  LICENSE = "MIT"

  inherit core-image
+
+LIVE = "${@base_contains('IMAGE_FSTYPES', 'live', 'yes', 'no', d)}"
+
+do_check_unionfs() {
+if [ "${NOISO}" = "1" ]; then
+return
+fi
+
+if [ "${LIVE}" = "yes" ]&&  ! grep -q "CONFIG_UNION_FS=y" 
${STAGING_KERNEL_DIR}/.config; then
+rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.iso
+rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso
+bbfatal "Building LIVE CD without UNION FS enabled in kernel"
+fi
+}
+
+addtask check_unionfs before do_build after do_bootimg


___
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.

[Tom Zanussi]

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.

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

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

Re: [yocto] [PATCH 2/2] sato: Remove questioned ISO image

[Darren Hart]

On 04/09/2012 11:34 AM, Yang Shi wrote:
> On 4/9/2012 9:31 AM, Darren Hart wrote:
>>
>> On 03/26/2012 02:19 PM, Yang Shi wrote:
>>> [YOCTO #1487]
>>>
>>> For the liveCD image, interactive bootup is needed, but psplash prevents 
>>> from
>>> booting interactively. In such case ISO image is not usable, so remove ISO 
>>> image
>>> and the corresponding link and throw error info to warn outside to enable
>>> unionfs in kenrel.
>>
>> The psplash only prevents interaction on the vga console right? If the
>> BSP supports a serial console as well there is not a problem right?
> 
> Yes, I think so. When I was doing the test, I disabled splash so that I 
> can type 'enter' to make interaction move forward.
> 

In that case, deleting the iso links if Unionfs is not configured in
does not seem appropriate. A bbwarn might be appropriate, but failing
and destroying the deploy data is certainly not.

--
Darren

> Thanks,
> Yang
> 
>>
>> --
>> Darren
>>
>>> Signed-off-by: Yang Shi
>>> ---
>>>   meta/recipes-sato/images/core-image-sato.bb |   16 
>>>   1 files changed, 16 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/meta/recipes-sato/images/core-image-sato.bb 
>>> b/meta/recipes-sato/images/core-image-sato.bb
>>> index 11c3318..10e2239 100644
>>> --- a/meta/recipes-sato/images/core-image-sato.bb
>>> +++ b/meta/recipes-sato/images/core-image-sato.bb
>>> @@ -9,3 +9,19 @@ IMAGE_FEATURES += "apps-console-core 
>>> ${SATO_IMAGE_FEATURES}"
>>>   LICENSE = "MIT"
>>>
>>>   inherit core-image
>>> +
>>> +LIVE = "${@base_contains('IMAGE_FSTYPES', 'live', 'yes', 'no', d)}"
>>> +
>>> +do_check_unionfs() {
>>> +if [ "${NOISO}" = "1" ]; then
>>> +return
>>> +fi
>>> +
>>> +if [ "${LIVE}" = "yes" ]&&  ! grep -q "CONFIG_UNION_FS=y" 
>>> ${STAGING_KERNEL_DIR}/.config; then
>>> +rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.iso
>>> +rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso
>>> +bbfatal "Building LIVE CD without UNION FS enabled in 
>>> kernel"
>>> +fi
>>> +}
>>> +
>>> +addtask check_unionfs before do_build after do_bootimg
> 

-- 
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 error on core-image-sato-sdk

[jfabernathy]

at the end of the build of core-image-sato-sdk I got the following 
error.  I'm using the edison branch with the latest changes and also 
building the meta-cedartrail.  I had previously built core-image-sato 
successfully with this setup.


Any ideas?

ERROR: Function 'build_boot_bin' failed (see 
/build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810 
for further information)
ERROR: Logfile of failure stored in: 
/build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810

Log data follows:
| mkdosfs: seek failed
| mkdosfs 2.10 (22 Sep 2003)
| ERROR: Function 'build_boot_bin' failed (see 
/build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810 
for further information)

NOTE: package core-image-sato-sdk-1.0-r0: task do_bootimg: Failed
ERROR: Task 9 
(/home/jim/poky/meta/recipes-sato/images/core-image-sato-sdk.bb, 
do_bootimg) failed with exit code '1'
ERROR: '/home/jim/poky/meta/recipes-sato/images/core-image-sato-sdk.bb' 
failed

jim@ubuntu-x64:/build/cdv-edison$

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

Re: [yocto] [PATCH 2/2] sato: Remove questioned ISO image

[Yang Shi]

On 4/9/2012 12:49 PM, Darren Hart wrote:


On 04/09/2012 11:34 AM, Yang Shi wrote:

On 4/9/2012 9:31 AM, Darren Hart wrote:

On 03/26/2012 02:19 PM, Yang Shi wrote:

[YOCTO #1487]

For the liveCD image, interactive bootup is needed, but psplash prevents from
booting interactively. In such case ISO image is not usable, so remove ISO image
and the corresponding link and throw error info to warn outside to enable
unionfs in kenrel.

The psplash only prevents interaction on the vga console right? If the
BSP supports a serial console as well there is not a problem right?

Yes, I think so. When I was doing the test, I disabled splash so that I
can type 'enter' to make interaction move forward.


In that case, deleting the iso links if Unionfs is not configured in
does not seem appropriate. A bbwarn might be appropriate, but failing
and destroying the deploy data is certainly not.


OK, will make it throw a warning instead of removing iso images.

Thanks,
Yang



--
Darren


Thanks,
Yang


--
Darren


Signed-off-by: Yang Shi
---
   meta/recipes-sato/images/core-image-sato.bb |   16 
   1 files changed, 16 insertions(+), 0 deletions(-)

diff --git a/meta/recipes-sato/images/core-image-sato.bb 
b/meta/recipes-sato/images/core-image-sato.bb
index 11c3318..10e2239 100644
--- a/meta/recipes-sato/images/core-image-sato.bb
+++ b/meta/recipes-sato/images/core-image-sato.bb
@@ -9,3 +9,19 @@ IMAGE_FEATURES += "apps-console-core ${SATO_IMAGE_FEATURES}"
   LICENSE = "MIT"

   inherit core-image
+
+LIVE = "${@base_contains('IMAGE_FSTYPES', 'live', 'yes', 'no', d)}"
+
+do_check_unionfs() {
+if [ "${NOISO}" = "1" ]; then
+return
+fi
+
+if [ "${LIVE}" = "yes" ]&&   ! grep -q "CONFIG_UNION_FS=y" 
${STAGING_KERNEL_DIR}/.config; then
+rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_LINK_NAME}.iso
+rm -f ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.iso
+bbfatal "Building LIVE CD without UNION FS enabled in kernel"
+fi
+}
+
+addtask check_unionfs before do_build after do_bootimg


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

[yocto] [PATCH 0/1][meta-intel] Cover letter for fixing meta-cedartrail README for Glxgears build

[rahul . saxena]

From: Rahul Saxena 

Cover letter for fixing the Cedar Trail BSP README file.

Existing README incorrectly states that "debug-tweaks" is needed to be added
to EXTRA_IMAGE_FEATURES to include Glxgears in build. This patch fixes the 
README to indicate
that correct feature to be included is "tools-testapps".

Signed-off-by: Rahul Saxena 
--

The following changes since commit 072c6e99616c25c31521e05560433c67fb2a0292:

  meta-cedartrail: change libva license to MIT (2012-03-26 17:42:56 -0500)

are available in the git repository at:
  git://git.pokylinux.org/meta-intel-contrib rsaxena-cedartrail-edison
  
http://git.pokylinux.org/cgit.cgi/meta-intel-contrib/log/?h=rsaxena-cedartrail-edison

Rahul Saxena (1):
  meta-cedartrail: fix README to state tools-testapps needed for
Glxgears

 meta-cedartrail/README |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

-- 
1.7.4.1

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

[yocto] [PATCH 1/1] meta-cedartrail: fix README to state tools-testapps needed for Glxgears

[rahul . saxena]

From: Rahul Saxena 

Existing README incorrectly states that "debug-tweaks" is needed to be added
to EXTRA_IMAGE_FEATURES to include Glxgears in build. The correct feature
to be included is "tools-testapps" and not "debug-tweaks"

Signed-off-by: Rahul Saxena 
---
 meta-cedartrail/README |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/meta-cedartrail/README b/meta-cedartrail/README
index f17410c..30df320 100755
--- a/meta-cedartrail/README
+++ b/meta-cedartrail/README
@@ -117,7 +117,7 @@ included in the sato images.  The sample files are 
installed in
 
 Adding Glxgears to image
 -
-Glxgears can be added to the generated image by adding "debug-tweaks"
+Glxgears can be added to the generated image by adding "tools-testapps"
 option to the extra image features variable in the default local.conf
 before building the BSP.
 
-- 
1.7.4.1

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

[yocto] [PATCH 1/1] syslinux: Update distro-tracking fields

[Darren Hart]

Add reason for not updating syslinux this release.

Signed-off-by: Darren Hart 
---
 .../conf/distro/include/distro_tracking_fields.inc |5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta/conf/distro/include/distro_tracking_fields.inc 
b/meta/conf/distro/include/distro_tracking_fields.inc
index caaf1bc..ce640f4 100644
--- a/meta/conf/distro/include/distro_tracking_fields.inc
+++ b/meta/conf/distro/include/distro_tracking_fields.inc
@@ -1518,15 +1518,16 @@ RECIPE_COMMENTS_pn-bash = ""
 
 RECIPE_STATUS_pn-syslinux = "yellow"
 # need mangling on LDFLAGS
-RECIPE_LAST_UPDATE_pn-syslinux = "Nov 16, 2010"
+RECIPE_LAST_UPDATE_pn-syslinux = "Apr 4, 2012"
 RECIPE_MAINTAINER_pn-syslinux = "Darren Hart "
 RECIPE_DEPENDENCY_CHECK_pn-syslinux = "not done"
-RECIPE_LATEST_VERSION_pn-syslinux = "3.86"
+RECIPE_LATEST_VERSION_pn-syslinux = "4.03"
 RECIPE_PATCH_pn-syslinux+cross-build = "use poky toolchain instead of host"
 RECIPE_INTEL_SECTION_pn-syslinux = "base utils"
 RECIPE_TIME_BETWEEN_LAST_TWO_RELEASES_pn-syslinux = "2 months"
 RECIPE_LATEST_RELEASE_DATE_pn-syslinux = "Apr 01, 2010"
 RECIPE_COMMENTS_pn-syslinux = ""
+RECIPE_NO_UPDATE_REASON_pn-syslinux-"Waiting for 4.06 for 3.3 kernel headers 
support"
 
 RECIPE_STATUS_pn-sysvinit = "green"
 RECIPE_LAST_UPDATE_pn-sysvinit = "Jun 18, 2010"
-- 
1.7.6.5

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

[yocto] [PATCH 0/1] syslinux: Update distro-tracking fields

[Darren Hart]

The following changes since commit 190f6d791d51aaa4cfb9f1cf932bc205ff674fb5:

  runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:47 
+0100)

are available in the git repository at:
  git://git.yoctoproject.org/poky-contrib dvhart/distro-tracking
  
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=dvhart/distro-tracking

Darren Hart (1):
  syslinux: Update distro-tracking fields

 .../conf/distro/include/distro_tracking_fields.inc |5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

-- 
1.7.6.5

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

Re: [yocto] build error on core-image-sato-sdk

[Darren Hart]

On 04/09/2012 01:33 PM, jfabernathy wrote:
> at the end of the build of core-image-sato-sdk I got the following 
> error.  I'm using the edison branch with the latest changes and also 
> building the meta-cedartrail.  I had previously built core-image-sato 
> successfully with this setup.
> 
> Any ideas?
> 
> ERROR: Function 'build_boot_bin' failed (see 
> /build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810
>  
> for further information)
> ERROR: Logfile of failure stored in: 
> /build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810
> Log data follows:
> | mkdosfs: seek failed

Interesting.

Can you provide the "OE Build Configuration" blob that prints at the
start of the build - I'm mostly interested in your commit IDs for.

Also, please include the HEAD of your poky edison tree.

Thanks,

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

[yocto] [V2 PATCH 0/2] Fix init-live.sh to use unionfs for live CD and remove questioned ISO image

[Yang Shi]

Changelog V1 -> V2:
* Refined patch 1/2 log
* Fixed some spelling erros in patch 1/2
* Instead of removing questioned ISO images, just throw warning info in patch 
2/2


When booting up with liveCD image, init scripts can't work well on read-only 
filesystem. Unionfs,
which is supported in Yocto kernel, allows a filesystem to appear as writeable, 
but without
actually allowing writes to change the filesystem.

Use unionfs to mount rootfs and make root file system can be writen when using 
liveCD to boot up.
Set UNION_FS variable depending on kernel config, so that it can work with 
kernel which doesn't
have unionfs feature.

For the liveCD image, interactive bootup is needed, but psplash prevents from
booting interactively. In such case ISO image is not usable, so throw warning
info when building ISO image without unionfs enabled in kernel.

We tried a lot of different ways to achieve this:

1. Check if ISO image is built in initramfs-live-boot.bb or not, then prevent 
from generating ISO image.
But, we can't distinguish minimal image or sato image.

2. Check if x11 feature is included in initramfs-live-boot.bb or not, then 
prevent from generating ISO image.
But, x11 feature is contained in minimal image as well even though the package 
is not built.

3. Tried to append some check code in build_iso() in core-image-sato.bb, but 
poky can't support append code
in build_xxx functions like what we do for do_xxx funcitons.

So, we came up with current solution. Any new suggestion is appreciated.

One more thing is that if IMAGE_FSTYPE += "live" is not set in conf/local.conf 
with this fix, we will get below
error when building sato image:

ERROR: Running idle function
Traceback (most recent call last):
  File "/home/yshi/yocto/poky/bitbake/lib/bb/server/process.py", line
122, in ProcessServer.idle_commands(delay=0.1):
 try:
>retval = function(self, data, False)
 if retval is False:
  File "/home/yshi/yocto/poky/bitbake/lib/bb/cooker.py", line 1130, in
buildTargetsIdle(server=,
rq=, abort=False):
 try:
>retval = rq.execute_runqueue()
 except runqueue.TaskFailure as exc:
  File "/home/yshi/yocto/poky/bitbake/lib/bb/runqueue.py", line 947,
in RunQueue.execute_runqueue():
 self.rqexe = RunQueueExecuteDummy(self)
>if self.rqdata.prepare() == 0:
 self.state = runQueueComplete
  File "/home/yshi/yocto/poky/bitbake/lib/bb/runqueue.py", line 719,
in RunQueueData.prepare():

procdep.append(self.taskData.fn_index[self.runq_fnid[dep]] + "." +
self.runq_task[dep])
>self.runq_hash[task] =
bb.parse.siggen.get_taskhash(self.taskData.fn_index[self.runq_fnid[task]],
self.runq_task[task], procdep, self.dataCache)

  File "/home/yshi/yocto/poky/bitbake/lib/bb/siggen.py", line 153, in
SignatureGeneratorOEBasicHash.get_taskhash(fn='/home/yshi/yocto/poky/meta/recipes-sato/images/core-image-sato.bb',
task='do_bootimg', deps=[], dataCache=):
 k = fn + "." + task
>data = dataCache.basetaskhash[k]
 self.runtaskdeps[k] = []
KeyError: 
'/home/yshi/yocto/poky/meta/recipes-sato/images/core-image-sato.bb.do_bootimg'

NOTE: Preparing runqueue

Bruce pointed out there was a large discussion about this on hte list last 
week, so this should be a known issue in poky.

The following changes since commit f81b0593e74a31cb2d992df0583948ff57e3ed98:

  gdbm: Activate -enable-libgdbm-compat and add symlinks to headers in 
include/gdbm (2012-03-23 17:56:29 +0200)

are available in the git repository at:
  git://git.yoctoproject.org/poky-contrib yshi/1487v2
  http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=yshi/1487v2

Yang Shi (2):
  initrdscripts: fix init-live.sh and use unionfs
  sato:  Throw warning when building ISO image without unionfs enabled

 meta/recipes-core/initrdscripts/files/init-live.sh |   23 ---
 .../initrdscripts/initramfs-live-boot_1.0.bb   |9 +++-
 meta/recipes-sato/images/core-image-sato.bb|   14 
 3 files changed, 41 insertions(+), 5 deletions(-)
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 2/2] sato: Throw warning when building ISO image without unionfs enabled

[Yang Shi]

[YOCTO #1487]

For the liveCD image, interactive bootup is needed, but psplash prevents from
booting interactively. In such case ISO image is not usable, so throw warning
info when building ISO image without unionfs enabled in kernel.

Signed-off-by: Yang Shi 
---
 meta/recipes-sato/images/core-image-sato.bb |   14 ++
 1 files changed, 14 insertions(+), 0 deletions(-)

diff --git a/meta/recipes-sato/images/core-image-sato.bb 
b/meta/recipes-sato/images/core-image-sato.bb
index 11c3318..871b227 100644
--- a/meta/recipes-sato/images/core-image-sato.bb
+++ b/meta/recipes-sato/images/core-image-sato.bb
@@ -9,3 +9,17 @@ IMAGE_FEATURES += "apps-console-core ${SATO_IMAGE_FEATURES}"
 LICENSE = "MIT"
 
 inherit core-image
+
+LIVE = "${@base_contains('IMAGE_FSTYPES', 'live', 'yes', 'no', d)}"
+
+do_check_unionfs() {
+if [ "${NOISO}" = "1" ]; then
+return
+fi
+
+if [ "${LIVE}" = "yes" ] && ! grep -q "CONFIG_UNION_FS=y" 
${STAGING_KERNEL_DIR}/.config; then
+bbwarn "Building LIVE CD without UNION FS enabled in kernel"
+fi
+}
+
+addtask check_unionfs before do_build after do_bootimg
-- 
1.7.5.4

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

[yocto] [PATCH 1/2] initrdscripts: fix init-live.sh and use unionfs

[Yang Shi]

[YOCTO #1487]

When booting up with liveCD image, init scripts can't work well on read-only 
filesystem. Unionfs,
which is supported in Yocto kernel, allows a filesystem to appear as writeable, 
but without
actually allowing writes to change the filesystem.

Use unionfs to mount rootfs and make root file system can be writen when using 
liveCD to boot up.
Set UNION_FS variable depending on kernel config, so that it can work with 
kernel which doesn't
have unionfs feature.

Signed-off-by: Yang Shi 
---
 meta/recipes-core/initrdscripts/files/init-live.sh |   23 ---
 .../initrdscripts/initramfs-live-boot_1.0.bb   |9 +++-
 2 files changed, 27 insertions(+), 5 deletions(-)

diff --git a/meta/recipes-core/initrdscripts/files/init-live.sh 
b/meta/recipes-core/initrdscripts/files/init-live.sh
index eb5ab5b..737dae4 100644
--- a/meta/recipes-core/initrdscripts/files/init-live.sh
+++ b/meta/recipes-core/initrdscripts/files/init-live.sh
@@ -7,6 +7,7 @@ ROOT_IMAGE="rootfs.img"
 MOUNT="/bin/mount"
 UMOUNT="/bin/umount"
 ISOLINUX=""
+UNIONFS="no"
 
 early_setup() {
 mkdir /proc
@@ -89,17 +90,31 @@ case $label in
mkdir $ROOT_MOUNT
mknod /dev/loop0 b 7 0 2>/dev/null
 
-   if ! $MOUNT -o rw,loop,noatime,nodiratime 
/media/$i/$ISOLINUX/$ROOT_IMAGE $ROOT_MOUNT ; then
-   fatal "Couldnt mount rootfs image"
+   
+   if [ "$UNIONFS" = "yes" ]; then
+   mkdir /rootfs-tmp
+
+   if ! $MOUNT -o rw,loop,noatime,nodiratime 
/media/$i/$ISOLINUX/$ROOT_IMAGE /rootfs-tmp ; then
+   fatal "Could not mount rootfs image"
+   else
+   mkdir /cow
+   mount -t tmpfs -o rw,noatime,mode=755 tmpfs /cow
+   mount -t unionfs -o dirs=/cow:/rootfs-tmp=ro unionfs $ROOT_MOUNT
+   boot_live_root
+   fi
else
-   boot_live_root
+   if ! $MOUNT -o rw,loop,noatime,nodiratime 
/media/$i/$ISOLINUX/$ROOT_IMAGE $ROOT_MOUNT ; then
+   fatal "Could not mount rootfs image"
+   else
+   boot_live_root
+   fi
fi
;;
 install)
if [ -f /media/$i/$ISOLINUX/$ROOT_IMAGE ] ; then
./install.sh $i/$ISOLINUX $ROOT_IMAGE $video_mode $vga_mode
else
-   fatal "Couldnt find install script"
+   fatal "Could not find install script"
fi
 
# If we're getting here, we failed...
diff --git a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb 
b/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
index e85a0e1..f7f0c9d 100644
--- a/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
+++ b/meta/recipes-core/initrdscripts/initramfs-live-boot_1.0.bb
@@ -2,10 +2,17 @@ DESCRIPTION = "A live image init script"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = 
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
 RDEPENDS = "udev"
+DEPENDS = "virtual/kernel"
 SRC_URI = "file://init-live.sh"
 
-PR = "r7"
+PR = "r8"
 
+do_compile() {
+   if grep -q "CONFIG_UNION_FS=y" ${STAGING_KERNEL_DIR}/.config; then
+   sed -i 's/UNIONFS="no"/UNIONFS="yes"/g' ${WORKDIR}/init-live.sh
+   fi
+}
+ 
 do_install() {
 install -m 0755 ${WORKDIR}/init-live.sh ${D}/init
 }
-- 
1.7.5.4

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

Re: [yocto] [PATCH 0/1] meta-skeleton: Move hello-mod example kernel module to meta-skeleton

[Darren Hart]

DO NOT APPLY

This needs to be done in oe-core.

On 04/09/2012 10:57 AM, Darren Hart wrote:
> The following changes since commit 190f6d791d51aaa4cfb9f1cf932bc205ff674fb5:
> 
>   runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:47 
> +0100)
> 
> are available in the git repository at:
>   git://git.pokylinux.org/poky-contrib dvhart/skeleton
>   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/skeleton
> 
> Darren Hart (1):
>   meta-skeleton: Move hello-mod example kernel module to meta-skeleton
> 
>  .../recipes-kernel/hello-mod/files/COPYING |  340 
> 
>  .../recipes-kernel/hello-mod/files/Makefile|   14 +
>  .../recipes-kernel/hello-mod/files/hello.c |   33 ++
>  .../recipes-kernel/hello-mod/hello-mod_0.1.bb  |   15 +
>  4 files changed, 402 insertions(+), 0 deletions(-)
>  create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/COPYING
>  create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/Makefile
>  create mode 100644 meta-skeleton/recipes-kernel/hello-mod/files/hello.c
>  create mode 100644 meta-skeleton/recipes-kernel/hello-mod/hello-mod_0.1.bb
> 

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

[yocto] [PATCH 0/2] Misc bugfixes

[nitin . a . kamble]

From: Nitin A Kamble 

The following changes since commit 190f6d791d51aaa4cfb9f1cf932bc205ff674fb5:

  runqemu-internal: Add console=tty for qemuppc and NFS (2012-04-06 01:12:47 
+0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib nitin/bugfixes
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/bugfixes

Nitin A Kamble (2):
  tclibc-eglibc.inc: make locale packages dependency conditional
  poky-tiny.conf: adjust eglibc options for poky-tiny

 meta-yocto/conf/distro/poky-tiny.conf  |6 ++
 meta/conf/distro/include/tclibc-eglibc.inc |   23 ---
 2 files changed, 22 insertions(+), 7 deletions(-)

-- 
1.7.7

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

[yocto] [PATCH 1/2] tclibc-eglibc.inc: make locale packages dependency conditional

[nitin . a . kamble]

From: Nitin A Kamble 

Only add locale package dependencies if the eglibc is configured
with locale support.
  This avoids dependencies issues for distros such as poky-tiny

Signed-off-by: Nitin A Kamble 
---
 meta/conf/distro/include/tclibc-eglibc.inc |   23 ---
 1 files changed, 16 insertions(+), 7 deletions(-)

diff --git a/meta/conf/distro/include/tclibc-eglibc.inc 
b/meta/conf/distro/include/tclibc-eglibc.inc
index 8b8a214..aed82d1 100644
--- a/meta/conf/distro/include/tclibc-eglibc.inc
+++ b/meta/conf/distro/include/tclibc-eglibc.inc
@@ -23,10 +23,19 @@ LIBC_DEPENDENCIES = "libsegfault \
 eglibc-dev \
 eglibc-utils \
 eglibc-thread-db \
-eglibc-localedata-i18n \
-eglibc-gconv-ibm850 \
-eglibc-gconv-cp1252 \
-eglibc-gconv-iso8859-1 \
-eglibc-gconv-iso8859-15 \
-locale-base-en-us \
-locale-base-en-gb "
+${@get_libc_locales_dependencies(d)}"
+
+LIBC_LOCALE_DEPENDENCIES = "\
+   eglibc-localedata-i18n \
+   eglibc-gconv-ibm850 \
+   eglibc-gconv-cp1252 \
+   eglibc-gconv-iso8859-1 \
+   eglibc-gconv-iso8859-15 \
+   locale-base-en-us \
+   locale-base-en-gb"
+
+def get_libc_locales_dependencies(d):
+if 'libc-locales' in (d.getVar('DISTRO_FEATURES', True) or '').split() :
+return d.getVar('LIBC_LOCALE_DEPENDENCIES', True) or ''
+else:
+return ''
-- 
1.7.7

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

[yocto] [PATCH 2/2] poky-tiny.conf: adjust eglibc options for poky-tiny

[nitin . a . kamble]

From: Nitin A Kamble 

Avoid errors for building meta-toolchain for poky-tiny

This Fixes Bug: [YOCTO #2259]

Signed-off-by: Nitin A Kamble 
---
 meta-yocto/conf/distro/poky-tiny.conf |6 ++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/meta-yocto/conf/distro/poky-tiny.conf 
b/meta-yocto/conf/distro/poky-tiny.conf
index 395c6fb..58d64ec 100644
--- a/meta-yocto/conf/distro/poky-tiny.conf
+++ b/meta-yocto/conf/distro/poky-tiny.conf
@@ -63,6 +63,12 @@ ASSUME_PROVIDED += "pkgconfig$"
 # Reconfigure eglibc for a smaller installation
 # Comment out any of the lines below to disable them in the build
 DISTRO_FEATURES_LIBC_TINY = "libc-libm libc-crypt"
+# for gettext
+DISTRO_FEATURES_LIBC_TINY += "libc-posix-clang-wchar"
+# for m4
+DISTRO_FEATURES_LIBC_TINY += "libc-spawn libc-locale-code"
+# for elfutils
+DISTRO_FEATURES_LIBC_TINY += "libc-ftraverse"
 # Required for "who"
 DISTRO_FEATURES_LIBC_MINIMAL = "libc-utmp libc-getlogin"
 DISTRO_FEATURES_LIBC_REGEX = "libc-posix-regexp"
-- 
1.7.7

___
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

[Mark Hatle]

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.


--Mark


| 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

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
>>
>> | 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+69cfbdf9f1ff461a75e5b77d

Re: [yocto] build error on core-image-sato-sdk

[James Abernathy]

On Mon, Apr 9, 2012 at 6:15 PM, Darren Hart  wrote:

>
>
> On 04/09/2012 01:33 PM, jfabernathy wrote:
> > at the end of the build of core-image-sato-sdk I got the following
> > error.  I'm using the edison branch with the latest changes and also
> > building the meta-cedartrail.  I had previously built core-image-sato
> > successfully with this setup.
> >
> > Any ideas?
> >
> > ERROR: Function 'build_boot_bin' failed (see
> >
> /build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810
> > for further information)
> > ERROR: Logfile of failure stored in:
> >
> /build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810
> > Log data follows:
> > | mkdosfs: seek failed
>
> Interesting.
>
> Can you provide the "OE Build Configuration" blob that prints at the
> start of the build - I'm mostly interested in your commit IDs for.
>
> Also, please include the HEAD of your poky edison tree.
>
> Is there a way to retreive the OE-Build Configuration blob after it rolls
off the screen? Or should I just rerun and capture it then?


> Thanks,
>
> --
> 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] build error on core-image-sato-sdk

[Christopher Larson]

See the cooker.log.* files in the tmp (or build) directory.

-- 
Christopher Larson


On Monday, April 9, 2012 at 5:01 PM, James Abernathy wrote:

> 
> 
> On Mon, Apr 9, 2012 at 6:15 PM, Darren Hart  (mailto:dvh...@linux.intel.com)> wrote:
> > 
> > 
> > On 04/09/2012 01:33 PM, jfabernathy wrote:
> > > at the end of the build of core-image-sato-sdk I got the following
> > > error.  I'm using the edison branch with the latest changes and also
> > > building the meta-cedartrail.  I had previously built core-image-sato
> > > successfully with this setup.
> > >
> > > Any ideas?
> > >
> > > ERROR: Function 'build_boot_bin' failed (see
> > > /build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810
> > > for further information)
> > > ERROR: Logfile of failure stored in:
> > > /build/cdv-edison/tmp/work/cedartrail-poky-linux/core-image-sato-sdk-1.0-r0/temp/log.do_bootimg.25810
> > > Log data follows:
> > > | mkdosfs: seek failed
> > 
> > Interesting.
> > 
> > Can you provide the "OE Build Configuration" blob that prints at the
> > start of the build - I'm mostly interested in your commit IDs for.
> > 
> > Also, please include the HEAD of your poky edison tree.
> > 
> Is there a way to retreive the OE-Build Configuration blob after it rolls off 
> the screen? Or should I just rerun and capture it then? 
>  
> > Thanks,
> > 
> > --
> > Darren Hart
> > Intel Open Source Technology Center
> > Yocto Project - Linux Kernel
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org (mailto:yocto@yoctoproject.org)
> https://lists.yoctoproject.org/listinfo/yocto
> 
> 


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

[yocto] ADT Manual v1.1.1 Issues - 1 of 3

[Andy Gikling]

All,

There's a broken link in the ADT manual.  In section 4.1.3.1, the path 
"http://downloads.yoctoproject.org/releases/eclipse-plugin/1.1.1"; does not 
exist.  I think this is the desired path but the files aren't there...

Just an FYI - not sure if this merits filing a bug really.

~Andy Gikling
LasX Industries Inc.

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

[yocto] ADT Manual v1.1.1 Issues - 2 of 3

[Andy Gikling]

All,

I've had very mixed results during the three or four times I've run through the 
ADT manual from scratch.  There seems to be a real problem I keep encountering 
that I'd like to describe to the community with the hope that someone 
understands why I keep getting stuck.  I'm running a 32bit Ubuntu 11.10 VM and 
trying to build for a x86_64 sugarbay target machine.

The issue is that no matter which "route" I take to setup my toolchain (be it 
via the installer script or a premade toolchain I've downloaded) I always get 
"configure: error: C compiler cannot create executables" when I try to use 
Project->Reconfigure Project after starting a new HelloWorld example in 
Eclipse.  The ADT manual explicitly steps the user through to this point but 
using the Reconfigure Project feature (that puts together your Makefile for 
you) never completes.  When looking closer at the config.log I always find 
something that looks like this:

configure:3285: $? = 0
configure:3274: x86_64-poky-linux-gcc -v >&5
Using built-in specs.
COLLECT_GCC=x86_64-poky-linux-gcc
COLLECT_LTO_WRAPPER=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.6.3/lto-wrapper
Target: x86_64-poky-linux
Configured with: 
/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build/build/tmp/work-shared/gcc-4.6.2+svnr181430-r17/gcc-4_6-branch/configure
 --build=x86_64-linux --host=i686-pokysdk-linux --target=x86_64-poky-linux 
--prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr 
--exec_prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr 
--bindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-poky-linux 
--sbindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-poky-linux 
--libexecdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/libexec/x86_64-poky-linux
 --datadir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share 
--sysconfdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/etc 
--sharedstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/com 
--localstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/var 
--libdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/lib/x86_64-poky-linux 
--includedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/include 
--oldincludedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/include 
--infodir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/info 
--mandir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/man 
--disable-silent-rules 
--with-libtool-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk
 --with-gnu-ld --enable-shared --enable-languages=c,c++ --enable-threads=posix 
--disable-multilib --enable-c99 --enable-long-long --enable-symvers=gnu 
--enable-libstdcxx-pch --program-prefix=x86_64-poky-linux- 
--enable-target-optspace --enable-lto --enable-libssp --disable-bootstrap 
--disable-libgomp --disable-libmudflap --enable-cheaders=c_global 
--with-local-prefix=/opt/poky/1.1.1/sysroots/x86_64-poky-linux/usr 
--with-gxx-include-dir=/usr/include/c++ 
--with-build-time-tools=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build/build/tmp/sysroots/x86_64-linux/usr/x86_64-poky-linux/bin
 --with-sysroot=/opt/poky/1.1.1/sysroots/x86_64-poky-linux 
--with-build-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build/build/tmp/sysroots/qemux86-64
 --disable-libunwind-exceptions --disable-libssp --disable-libgomp 
--disable-libmudflap 
--with-mpfr=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk
 
--with-mpc=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk
 --enable-nls --enable-__cxa_atexit
Thread model: posix
gcc version 4.6.3 2017 (prerelease) (GCC)
configure:3285: $? = 0
configure:3274: x86_64-poky-linux-gcc -V >&5
x86_64-poky-linux-gcc: error: unrecognized option '-V'
x86_64-poky-linux-gcc: fatal error: no input files
compilation terminated.
configure:3285: $? = 1
configure:3274: x86_64-poky-linux-gcc -qversion >&5
x86_64-poky-linux-gcc: error: unrecognized option '-qversion'
x86_64-poky-linux-gcc: fatal error: no input files
compilation terminated.

I've tried to figure out what this error means but haven't had any luck.  
People have made some suggestions that I've tried and they haven't worked 
either.  So, I've been told to file a bug about this but I wasn't sure which 
category it goes under and I've never filed a bug in the Yocto project before.  
I'll try to get to it this week.

In the meantime, if anyone has tried to get through the ADT manual and is cross 
compiling I'd love to hear about how it went for you.

Thanks,

~Andy Gikling
LasX Industries Inc.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] ADT Manual v1.1.1 Issues - 3 of 3

[Andy Gikling]

All,

I ran through the ADT manual and ran into some goofynees in section 2.1.1.2. 
Configuring and Running the ADT Installer Script.

My adt_installer.conf contains:
YOCTOADT_REPO="http://adtrepo.yoctoproject.org/1.1.1";
YOCTOADT_TARGETS="x86_64"
YOCTOADT_QEMU="Y"
YOCTOADT_NFS_UTIL="Y"
YOCTOADT_ROOTFS_x86_64="minimal"
YOCTOADT_TARGET_SYSROOT_IMAGE_x86_64="minimal"
YOCTOADT_TARGET_SYSROOT_LOC_x86_64="$HOME/Desktop/ADT_Try2/sysroot"

Which should all be just fine.  When you run the installer script with these 
settings you will come to a 404 Not Found Error.

The image that was supposed to be downloaded to the /download_image/ folder is 
not there and eventually you will get an error from the script when it tries to 
extract the sysroot image it thought it downloaded.  I've found the sysroot 
file it's looking for in the Yocto downloads and put it in /download_image/ 
folder manually.  Once that's done the ADT installer script will then complete 
successfully.  There's a broken link there.

Does the YOCTOADT_REPO="http://adtrepo.yoctoproject.org/1.1.1"; need to contain 
a more exact path.  I'll try again with 
YOCTOADT_REPO="http://adtrepo.yoctoproject.org/1.1.1/adt-ipk/x86_64/";  or 
something like that...

Just an FYI,

~Andy Gikling
LasX Industries Inc.

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

Re: [yocto] ADT Manual v1.1.1 Issues - 2 of 3

[Lu, Lianhao]

Andy,

Could you please attach both the config.log file and the environment file under 
the directory /opt/poky/1.1.1/ ?

Andy Gikling wrote on 2012-04-10:
> All,
> 
> 
> 
> I've had very mixed results during the three or four times I've run through 
> the ADT manual from scratch.  There seems to be a real
> problem I keep encountering that I'd like to describe to the community with 
> the hope that someone understands why I keep getting stuck.
> I'm running a 32bit Ubuntu 11.10 VM and trying to build for a x86_64 sugarbay 
> target machine.
> 
> 
> 
> The issue is that no matter which "route" I take to setup my toolchain (be it 
> via the installer script or a premade toolchain I've
> downloaded) I always get "configure: error: C compiler cannot create 
> executables" when I try to use Project->Reconfigure Project after
> starting a new HelloWorld example in Eclipse.  The ADT manual explicitly 
> steps the user through to this point but using the Reconfigure
> Project feature (that puts together your Makefile for you) never completes.  
> When looking closer at the config.log I always find something
> that looks like this:
> 
> 
> 
> configure:3285: $? = 0
> 
> configure:3274: x86_64-poky-linux-gcc -v >&5
> 
> Using built-in specs.
> 
> COLLECT_GCC=x86_64-poky-linux-gcc
> 
> COLLECT_LTO_WRAPPER=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/libex
> ec/x86_64-poky-linux/gcc/x86_64-poky-linux/4.6.3/lto-wra pper
> 
> Target: x86_64-poky-linux
> 
> Configured with:
> /srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-64/build/bu
> ild/tmp/work-shared/gcc-4.6.2+svnr181430-r17/gcc-4_6-branc h/configure
> --build=x86_64-linux --host=i686-pokysdk-linux
> --target=x86_64-poky-linux
> --prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr
> --exec_prefix=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr
> --bindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-poky-
> linux
> --sbindir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/bin/x86_64-poky
> -linux
> --libexecdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/libexec/x86_
> 64-poky-linux
> --datadir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share
> --sysconfdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/etc
> --sharedstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/com
> --localstatedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/var
> --libdir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/lib/x86_64-poky-
> linux
> --includedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/include
> --oldincludedir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/include
> --infodir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/info
> --mandir=/opt/poky/1.1.1/sysroots/i686-pokysdk-linux/usr/share/man
> --disable-silent-rules
> --with-libtool-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/
> nightly-x86-64/build/build/tmp/sysroots/i686-pokysdk-linux-nativ esdk
> --with-gnu-ld --enable-shared --enable-languages=c,c++
> --enable-threads=posix --disable-multilib --enable-c99
> --enable-long-long --enable-symvers=gnu --enable-libstdcxx-pch
> --program-prefix=x86_64-poky-linux- --enable-target-optspace
> --enable-lto --enable-libssp --disable-bootstrap --disable-libgomp
> --disable-libmudflap --enable-cheaders=c_global
> --with-local-prefix=/opt/poky/1.1.1/sysroots/x86_64-poky-linux/usr
> --with-gxx-include-dir=/usr/include/c++
> --with-build-time-tools=/srv/home/pokybuild/yocto-autobuilder/yocto-slave
> /nightly-x86-64/build/build/tmp/sysroots/x86_64-linux/usr/x86_
> 64-poky-linux/bin
> --with-sysroot=/opt/poky/1.1.1/sysroots/x86_64-poky-linux
> --with-build-sysroot=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/ni
> ghtly-x86-64/build/build/tmp/sysroots/qemux86-64
> --disable-libunwind-exceptions --disable-libssp --disable-libgomp
> --disable-libmudflap
> --with-mpfr=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86
> -64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk
> --with-mpc=/srv/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86-
> 64/build/build/tmp/sysroots/i686-pokysdk-linux-nativesdk --enable-nls
> --enable-__cxa_atexit
> 
> Thread model: posix
> 
> gcc version 4.6.3 2017 (prerelease) (GCC)
> 
> configure:3285: $? = 0
> 
> configure:3274: x86_64-poky-linux-gcc -V >&5
> 
> x86_64-poky-linux-gcc: error: unrecognized option '-V'
> 
> x86_64-poky-linux-gcc: fatal error: no input files
> 
> compilation terminated.
> 
> configure:3285: $? = 1
> 
> configure:3274: x86_64-poky-linux-gcc -qversion >&5
> 
> x86_64-poky-linux-gcc: error: unrecognized option '-qversion'
> 
> x86_64-poky-linux-gcc: fatal error: no input files
> 
> compilation terminated.
> 
> 
> 
> I've tried to figure out what this error means but haven't had any luck.  
> People have made some suggestions that I've tried and they
> haven't worked either.  So, I've been told to file a bug about this but I 
> wasn't sure which category it goes under and I've never filed a
> bug in the Yocto project before.  I'll try to get

Re: [yocto] ADT Manual v1.1.1 Issues - 3 of 3

[Lu, Lianhao]

Hi Beth,

Looks like the 1.1.1 rootfs on adtrepo was populated into a wrong URL. It 
should be http://adtrepo.yoctoproject.org/1.1.1/rootfs/ instead of 
http://adtrepo.yoctoproject.org/1.1.1/adt-ipk/rootfs/.

Hi Andy,

Please file a bug against 1.1.1. Before we got that fixed, you may tweak the 
adt-installer to work around the issue.


1.   Open adt-installer script, find the function "download_file"

2.   Find the last statement: wget "$YOCTOADT_REPO/rootfs/$1" ..., and 
change that to wget "$YOCTOADT_REPO/adt-ipk/rootfs/$1".

Best Regards,
Lianhao

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Andy Gikling
Sent: Tuesday, April 10, 2012 12:43 PM
To: yocto@yoctoproject.org
Subject: [yocto] ADT Manual v1.1.1 Issues - 3 of 3

All,

I ran through the ADT manual and ran into some goofynees in section 2.1.1.2. 
Configuring and Running the ADT Installer Script.

My adt_installer.conf contains:
YOCTOADT_REPO="http://adtrepo.yoctoproject.org/1.1.1";
YOCTOADT_TARGETS="x86_64"
YOCTOADT_QEMU="Y"
YOCTOADT_NFS_UTIL="Y"
YOCTOADT_ROOTFS_x86_64="minimal"
YOCTOADT_TARGET_SYSROOT_IMAGE_x86_64="minimal"
YOCTOADT_TARGET_SYSROOT_LOC_x86_64="$HOME/Desktop/ADT_Try2/sysroot"

Which should all be just fine.  When you run the installer script with these 
settings you will come to a 404 Not Found Error.

The image that was supposed to be downloaded to the /download_image/ folder is 
not there and eventually you will get an error from the script when it tries to 
extract the sysroot image it thought it downloaded.  I've found the sysroot 
file it's looking for in the Yocto downloads and put it in /download_image/ 
folder manually.  Once that's done the ADT installer script will then complete 
successfully.  There's a broken link there.

Does the YOCTOADT_REPO="http://adtrepo.yoctoproject.org/1.1.1"; need to contain 
a more exact path.  I'll try again with 
YOCTOADT_REPO="http://adtrepo.yoctoproject.org/1.1.1/adt-ipk/x86_64/";  or 
something like that...

Just an FYI,

~Andy Gikling
LasX Industries Inc.

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