Re: [yocto] RFC: Web UI design for bitbake

2011-12-19 Thread Luo Zhenhua-B19537 
Hello, 

"hob" and website UI work in X env, is there a plan to support the Kernel 
configure manner GUI within Yocto to support UI configuration in console env? 


Best Regards,

Zhenhua


> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] 
> On
> Behalf Of Wang, Shane
> Sent: Tuesday, December 20, 2011 11:12 AM
> To: yocto@yoctoproject.org; Uriel Liu
> Subject: [yocto] RFC: Web UI design for bitbake
> 
> Hi all,
> 
> Web UI interface is the next what we are going to do. Uriel drafted the first
> iteration of the architecture design and I posted it onto
> https://wiki.yoctoproject.org/wiki/Web_UI.
> 
> Looking forward to your feedbacks.
> 
> --
> Shane
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


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

[yocto] Query about how Yocto handles the bbclass file when it exists in multi-layers

2011-12-29 Thread Luo Zhenhua-B19537 
If one bbclass exists in multi-layers, which one will Yocto pick up? It seems 
BBFILE_PRIORITY doesn't impact bbclass file.


Best Regards,

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

Re: [yocto] Query about how Yocto handles the bbclass file when it exists in multi-layers

2011-12-29 Thread Luo Zhenhua-B19537 
> -Original Message-
> From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
> Sent: Thursday, December 29, 2011 5:41 PM
>
> > If one bbclass exists in multi-layers, which one will Yocto pick up?
> > It seems BBFILE_PRIORITY doesn't impact bbclass file.
> 
> I believe for bbclass files it's the order in which the layers are listed in
> your bblayers.conf.
> 
> We could fix this, 
[Luo Zhenhua-B19537] Thanks. the function is useful

> however I'm not sure we should be encouraging duplication of
> class files - people should ideally be getting their functionality into the 
> OE-
> Core classes and not just overlaying their own version of the class.
[Luo Zhenhua-B19537] Agree. 


Best Regards,

Zhenhua

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

[yocto] initramfs support in Yocto

2012-03-02 Thread Luo Zhenhua-B19537 
Hello all,

Does Yocto support initramfs build?


Best Regards,

Zhenhua

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

Re: [yocto] [meta-fsl-ppc 02/16] fsl-image-minimal: IMAGE_FSTYPES add jffs2

2012-09-12 Thread Luo Zhenhua-B19537 
The targets with NAND flash need jffs2 rootfs, e.g. mpc8536ds, mpc8572ds, 
p1020utm, pp1020rdb, p1021rdb, p1022ds, p1024rdb p1025rdb


Best Regards,

Zhenhua


> -Original Message-
> From: McClintock Matthew-B29882
> Sent: Thursday, September 13, 2012 5:53 AM
> To: Luo Zhenhua-B19537
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-fsl-ppc 02/16] fsl-image-minimal:
> IMAGE_FSTYPES add jffs2
> 
> On Wed, Sep 12, 2012 at 2:06 AM,   wrote:
> > From: Ting Liu 
> >
> > Signed-off-by: Ting Liu 
> > ---
> >  images/fsl-image-minimal.bb |2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/images/fsl-image-minimal.bb b/images/fsl-image-minimal.bb
> > index b8d3c77..f3d1ad4 100644
> > --- a/images/fsl-image-minimal.bb
> > +++ b/images/fsl-image-minimal.bb
> > @@ -13,4 +13,4 @@ IMAGE_ROOTFS_SIZE = "8192"
> >  # remove not needed ipkg informations  ROOTFS_POSTPROCESS_COMMAND +=
> > "remove_packaging_data_files ; "
> >
> > -IMAGE_FSTYPES = "tar.gz ext2.gz.u-boot"
> > +IMAGE_FSTYPES = "tar.gz ext2.gz.u-boot jffs2"
> 
> Just to confirm, all boards will use the jffs2 image?
> 
> -M
> 
> > --
> > 1.7.9.5
> >
> >
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto

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

Re: [yocto] [meta-fsl-ppc 02/16] fsl-image-minimal: IMAGE_FSTYPES add jffs2

2012-09-13 Thread Luo Zhenhua-B19537 
Yes, jffs2 is required when the rootfs is loaded from NAND flash.


Best Regards,

Zhenhua


> -Original Message-
> From: McClintock Matthew-B29882
> Sent: Thursday, September 13, 2012 10:51 AM
> To: Luo Zhenhua-B19537
> Cc: McClintock Matthew-B29882; yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-fsl-ppc 02/16] fsl-image-minimal:
> IMAGE_FSTYPES add jffs2
> 
> On Wed, Sep 12, 2012 at 9:26 PM, Luo Zhenhua-B19537 
> wrote:
> > The targets with NAND flash need jffs2 rootfs, e.g. mpc8536ds,
> > mpc8572ds, p1020utm, pp1020rdb, p1021rdb, p1022ds, p1024rdb p1025rdb
> 
> I think other's have NAND flash too, they don't need these?
> 
> -M
> 
> >
> >
> > Best Regards,
> >
> > Zhenhua
> >
> >
> >> -----Original Message-
> >> From: McClintock Matthew-B29882
> >> Sent: Thursday, September 13, 2012 5:53 AM
> >> To: Luo Zhenhua-B19537
> >> Cc: yocto@yoctoproject.org
> >> Subject: Re: [yocto] [meta-fsl-ppc 02/16] fsl-image-minimal:
> >> IMAGE_FSTYPES add jffs2
> >>
> >> On Wed, Sep 12, 2012 at 2:06 AM,   wrote:
> >> > From: Ting Liu 
> >> >
> >> > Signed-off-by: Ting Liu 
> >> > ---
> >> >  images/fsl-image-minimal.bb |2 +-
> >> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >> >
> >> > diff --git a/images/fsl-image-minimal.bb
> >> > b/images/fsl-image-minimal.bb index b8d3c77..f3d1ad4 100644
> >> > --- a/images/fsl-image-minimal.bb
> >> > +++ b/images/fsl-image-minimal.bb
> >> > @@ -13,4 +13,4 @@ IMAGE_ROOTFS_SIZE = "8192"
> >> >  # remove not needed ipkg informations  ROOTFS_POSTPROCESS_COMMAND
> >> > += "remove_packaging_data_files ; "
> >> >
> >> > -IMAGE_FSTYPES = "tar.gz ext2.gz.u-boot"
> >> > +IMAGE_FSTYPES = "tar.gz ext2.gz.u-boot jffs2"
> >>
> >> Just to confirm, all boards will use the jffs2 image?
> >>
> >> -M
> >>
> >> > --
> >> > 1.7.9.5
> >> >
> >> >
> >> > ___
> >> > yocto mailing list
> >> > yocto@yoctoproject.org
> >> > https://lists.yoctoproject.org/listinfo/yocto
> >
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto

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

[yocto] Difference of toolchain recipes

2012-12-03 Thread Luo Zhenhua-B19537 
It is a bit confused for the different recipes of toolchian, can somebody help 
to explain what's the difference for those recipes? E.g. gcc-cross, 
gcc-cross-canadian, gcc-cross-initial, gcc-cross-intermediate, gcc-crosssdk, 
gcc-crosssdk-initial, gcc-crosssdk-intermediate, gcc-runtime, etc. 

Is there any document for those description?


Best Regards,

Zhenhua

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

Re: [yocto] Difference of toolchain recipes

2012-12-06 Thread Luo Zhenhua-B19537 
Can anybody shed some light, please?


Best Regards,

Zhenhua


> -Original Message-
> From: Luo Zhenhua-B19537
> Sent: Tuesday, December 04, 2012 11:53 AM
> To: openembedded-c...@lists.openembedded.org; 'yocto@yoctoproject.org'
> Subject: Difference of toolchain recipes
> 
> It is a bit confused for the different recipes of toolchian, can somebody
> help to explain what's the difference for those recipes? E.g. gcc-cross,
> gcc-cross-canadian, gcc-cross-initial, gcc-cross-intermediate, gcc-
> crosssdk, gcc-crosssdk-initial, gcc-crosssdk-intermediate, gcc-runtime,
> etc.
> 
> Is there any document for those description?
> 
> 
> Best Regards,
> 
> Zhenhua

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

[yocto] Issue of external toolchain usage in Yocto

2012-12-06 Thread Luo Zhenhua-B19537 
I tried to use CS external toolchain to build images in Yocto, I met following 
issue when doing configure for package.

configure:2728: checking for powerpc-linux-gnu-gcc  -m32   -mcpu=8548 -mabi=spe 
-mspe -mfloat-gprs=double 
--sysroot=/home/yocto/poky/build_bsc9131rdb_release/tmp/sysroots/bsc9131rdb-tcbootstrap
 option to accept ISO C89
configure:2802: powerpc-linux-gnu-gcc  -m32   -mcpu=8548 -mabi=spe -mspe 
-mfloat-gprs=double 
--sysroot=/home/yocto/poky/build_bsc9131rdb_release/tmp/sysroots/bsc9131rdb-tcbootstrap
  -c 
-isystem/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/powerpc-fsl-linux-gnuspe/include
 -I/home/yocto/poky/build_bsc9131rdb_release/tmp/sysroots/bsc9131rdb -O2 -pipe 
-g -feliminate-unused-debug-types  conftest.c >&5
conftest.c:9:19: fatal error: stdio.h: No such file or directory

Firstly I run above compile command manually, it failed as following: 
$ 
/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu-gcc
 -m32 -mcpu=8548 -mabi=spe -mspe -mfloat-gprs=double 
--sysroot=/home/yocto/poky/build_bsc9131rdb_release/tmp/sysroots/bsc9131rdb-tcbootstrap
 -c 
-isystem/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/powerpc-fsl-linux-gnuspe/include
  -I/home/yocto/poky/build_bsc9131rdb_release/tmp/sysroots/bsc9131rdb  -O2 
-pipe -g -feliminate-unused-debug-types conftest.c
conftest.c:10:19: fatal error: stdio.h: No such file or directory
compilation terminated.

Secondly I removed --sysroot flag, the build process passed. 
$ 
/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu-gcc
 -m32 -mcpu=8548 -mabi=spe -mspe -mfloat-gprs=double -c 
-isystem/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/powerpc-fsl-linux-gnuspe/include
  -I/home/yocto/poky/build_bsc9131rdb_release/tmp/sysroots/bsc9131rdb  -O2 
-pipe -g -feliminate-unused-debug-types conftest.c

I also used the toolchain built by Yocto, the same issue happened.

I did following change in meta/conf/distro/include/tcmode-external-csl.inc, is 
there anything missing to use external toolchain in Yocto?
-EXTERNAL_TOOLCHAIN ?= "/usr/local/csl/${TARGET_ARCH}"
+EXTERNAL_TOOLCHAIN ?= 
"/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu"

Content of my contest.c:
#define PACKAGE_NAME "module-init-tools"
#define PACKAGE_TARNAME "module-init-tools"
#define PACKAGE_VERSION "3.16"
#define PACKAGE_STRING "module-init-tools 3.16"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
#define PACKAGE "module-init-tools"
#define VERSION "3.16"

#include 

int main ()
{
  ;
  return 0;
}


Best Regards,

Zhenhua



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

Re: [yocto] Difference of toolchain recipes

2012-12-06 Thread Luo Zhenhua-B19537 
Hello Mark,

Thanks a lot, this is very helpful for understanding the different recipes of 
toolchain. 


Best Regards,

Zhenhua

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Mark Hatle
> Sent: Friday, December 07, 2012 2:05 AM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] Difference of toolchain recipes
> 
> On 12/6/12 4:00 AM, Luo Zhenhua-B19537 wrote:
> > Can anybody shed some light, please?
> >
> >
> > Best Regards,
> >
> > Zhenhua
> >
> >
> >> -Original Message-
> >> From: Luo Zhenhua-B19537
> >> Sent: Tuesday, December 04, 2012 11:53 AM
> >> To: openembedded-c...@lists.openembedded.org; 'yocto@yoctoproject.org'
> >> Subject: Difference of toolchain recipes
> >>
> >> It is a bit confused for the different recipes of toolchian, can
> >> somebody help to explain what's the difference for those recipes?
> >> E.g. gcc-cross, gcc-cross-canadian, gcc-cross-initial,
> >> gcc-cross-intermediate, gcc- crosssdk, gcc-crosssdk-initial,
> >> gcc-crosssdk-intermediate, gcc-runtime, etc.
> 
> gcc-cross-initial - This is the initial compiler needed to bootstrap the
> toolchain to build software on the host for the target.  (This is a
> 'native'
> package.)
> 
> gcc-cross-intermediate - This is the second stage of the bootstrap
> process to build software on the host for the target. (This is a 'native'
> package.)
> 
> gcc-cross - this is the the final stage of the bootstrap process, and
> results in the cross compiler to build software on the host for the
> target.  (This is a 'native' package.)  If you are replacing the cross
> compiler toolchain with a custom version, this is what you must replace.
> 
> gcc-runtime - these are the runtime libraries, but from the toolchain
> bootstrapping process.  This results in a 'target' binary.
> 
> gcc-crosssdk-initial/intermediate - stage 1 and 2 of the a cross compiler
> to build from the 'host' to the 'sdk'.  Often the SDK is not the same
> target as the host.  (This is a 'native' binary.)
> 
> gcc-crosssdk - this the final stage of the SDK compiler.  Again, this is
> to build on the host, for the sdk.  This is a 'native' binary.
> 
> gcc-cross-canadian - This is the compiler included with the SDK to build
> on the SDK machine creating software for the target.  This is an
> 'nativesdk' package.
> 
> >> Is there any document for those description?
> 
> Not that I know of.. It's one of those things that you kind of need to
> know in order to work with it.  It likely should be documented somewhere
> officially.
> 
> --Mark
> 
> >>
> >>
> >> Best Regards,
> >>
> >> Zhenhua
> >
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto


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

[yocto] Differnt build result of same u-boot source with differnet binutils

2013-05-31 Thread Luo Zhenhua-B19537 
When the u-boot(HEAD of master in git://git.freescale.com/ppc/sdk/u-boot.git) 
of p1022ds is built with different binutils in Yocto, the result is different. 

With binutils-2.23.1(last version in Yocto), u-boot can be built correctly. 
With binutils-2.23.2(current version in Yocto), the build failed as following:
| release.S: Assembler messages:
| release.S:236: Error: value of 4294963524 too large for field of 2 bytes at 
170
| release.S:237: Error: operand out of range (0xf144 is not between 
0x and 0x)
| release.S:237: Error: value of 4294963524 too large for field of 2 bytes at 
174
| release.S:365: Error: value of 4294963524 too large for field of 2 bytes at 
206
| release.S:366: Error: operand out of range (0xf144 is not between 
0x and 0x)
| release.S:366: Error: value of 4294963524 too large for field of 2 bytes at 
210
| release.S:390: Error: value of 4294963520 too large for field of 2 bytes at 
278
| release.S:391: Error: operand out of range (0xf140 is not between 
0x and 0x)
| release.S:391: Error: value of 4294963520 too large for field of 2 bytes at 
282

Below is the failed code section:
[..snip..]
233 #define toreset(x) (x - __secondary_start_page + 0xf000)
234 
235 /* get our PIR to figure out our table entry */
236 lis r3,toreset(__spin_table_addr)@h
237 ori r3,r3,toreset(__spin_table_addr)@l
238 lwz r3,0(r3)
[..snip..]

Seems like the build error is related to binutils, can somebody shed some light 
on the issue? Thanks in advance. 


Best Regards,

Zhenhua

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

[yocto] Can Yocto run on host with other CPU types

2013-06-05 Thread Luo Zhenhua-B19537 
Hi, 

Except x86/x86-64 hosts, can Yocto support to run on hosts with other CPU arch, 
e.g.  ARM, Powerpc, etc?


Best Regards,

Zhenhua

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

Re: [yocto] Can Yocto run on host with other CPU types

2013-06-07 Thread Luo Zhenhua-B19537 
> -Original Message-
> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
> Sent: Friday, June 07, 2013 5:50 PM
> 
> On Thu, 2013-06-06 at 06:48 +0000, Luo Zhenhua-B19537 wrote:
> > Except x86/x86-64 hosts, can Yocto support to run on hosts with other
> > CPU arch, e.g.  ARM, Powerpc, etc?
> 
> You mean as the system to run the builds on? 
[Luo Zhenhua-B19537] Yes

> In theory that would be possible although most people tend to use x86 and the 
> others aren't
> tested afaik.
[Luo Zhenhua-B19537] Does it make sense to log defects in YP bugzilla if issue 
is found on host with those CPU types?

BTW, is there a limitation for maximum parallel number of Yocto build? I don't 
think the number can be arbitrary. 


Best Regards,

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

Re: [yocto] How NOT to include kernel image to the rootfs?

2013-06-24 Thread Luo Zhenhua-B19537 
Insop, 

You can check the actual dependency in the output file of "bitbake -g 
fsl-image-min-net2". 


Best Regards,

Zhenhua

> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Anders Darander
> Sent: Monday, June 24, 2013 5:05 PM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] How NOT to include kernel image to the rootfs?
> 
> * Insop Song  [130624 10:56]:
> > I've tried
> > - by commenting "RDEPENDS_kernel-base ?= "kernel-image"" from
> > kernel.bbclass
> > - and/or adding "RDEPENDS_kernel-base = "" in my image definition
> 
> You should add this line in either your local.conf, or in a .bbappend for
> the kernel recipe in question.
> 
> > But neither worked.
> 
> That should make it work.
> 
> 
> Cheers,
> Anders
> 
> 
> --
> Anders Darander
> ChargeStorm AB / eStorm AB
> ___
> 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] First UBI build

2013-06-27 Thread Luo Zhenhua-B19537 
Add below two variables in conf/local.conf, the value is just for sample and 
might need change.

MKUBIFS_ARGS = " -m 512 -e 15360 -c 3600 "
UBINIZE_ARGS = " -p 16KiB -m 512 -s 512 "


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of DAMARLA Satya Swaroop
Sent: Thursday, June 27, 2013 3:04 PM
To: yocto@yoctoproject.org
Subject: [yocto] First UBI build

Hi Guys,

I had great success and actually feel yocto with building images. Now I want to 
run the image from the flash drive and trying to build a UBIFS but I get 
strange errors which I didnot get when I am building a normal tar.gz file for 
the SDCARD. The error is as follows... Can you guys please tell me what is the 
new stuff I had to add to overcome this issue?

| Size after prelinking 276884.
| Error: min. I/O unit was not specified (use -h for help)
| ERROR: Function failed: do_rootfs (log file is located at 
/home/damarla/openYocto/poky/buildSmartCPU/tmp/work/smartcpu-untersberg-linux-gnueabi/rootfs-smartcpu/1.0-r0/temp/log.do_rootfs.13924)
ERROR: Task 7 
(/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/rootfs-smartcpu.bb,
 do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5188 tasks of which 4394 didn't need to be rerun 
and 1 failed.
No currently running tasks (5187 of 5189)

Summary: 1 task failed:
  
/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/rootfs-smartcpu.bb,
 do_rootfs
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

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

Re: [yocto] First UBI build

2013-06-27 Thread Luo Zhenhua-B19537 
Yes.


Best Regards,

Zhenhua

From: DAMARLA Satya Swaroop [mailto:satyaswaroop.dama...@gmail.com]
Sent: Thursday, June 27, 2013 4:15 PM
To: Luo Zhenhua-B19537
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] First UBI build

Hi Luo,

Thank you  I assume the image type is as follows

IMAGE_FSTYPES += "ubi"

Will you please confirm this?

Cheers,
Sati

On Thu, Jun 27, 2013 at 9:20 AM, Luo Zhenhua-B19537 
mailto:b19...@freescale.com>> wrote:
Add below two variables in conf/local.conf, the value is just for sample and 
might need change.

MKUBIFS_ARGS = " -m 512 -e 15360 -c 3600 "
UBINIZE_ARGS = " -p 16KiB -m 512 -s 512 "


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org> 
[mailto:yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org>] 
On Behalf Of DAMARLA Satya Swaroop
Sent: Thursday, June 27, 2013 3:04 PM
To: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
Subject: [yocto] First UBI build

Hi Guys,

I had great success and actually feel yocto with building images. Now I want to 
run the image from the flash drive and trying to build a UBIFS but I get 
strange errors which I didnot get when I am building a normal tar.gz file for 
the SDCARD. The error is as follows... Can you guys please tell me what is the 
new stuff I had to add to overcome this issue?

| Size after prelinking 276884.
| Error: min. I/O unit was not specified (use -h for help)
| ERROR: Function failed: do_rootfs (log file is located at 
/home/damarla/openYocto/poky/buildSmartCPU/tmp/work/smartcpu-untersberg-linux-gnueabi/rootfs-smartcpu/1.0-r0/temp/log.do_rootfs.13924)
ERROR: Task 7 
(/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/rootfs-smartcpu.bb<http://rootfs-smartcpu.bb>,
 do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5188 tasks of which 4394 didn't need to be rerun 
and 1 failed.
No currently running tasks (5187 of 5189)

Summary: 1 task failed:
  
/home/damarla/openYocto/poky/meta-skidata/recipes-smartcpu/images/rootfs-smartcpu.bb<http://rootfs-smartcpu.bb>,
 do_rootfs
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Cheers.
Sati

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

Re: [yocto] Another in a seemingly infinite chain of errors

2013-07-04 Thread Luo Zhenhua-B19537 
FILES_${PN}_append = " xxx" should useful, xxx is the file which is listed in 
the "were installed but not shipped" message. 

More info of FILES can be found in 
https://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#var-FILES


Best Regards,

Zhenhua


> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Paul D. DeRocco
> Sent: Friday, July 05, 2013 1:47 PM
> To: yocto@yoctoproject.org
> Subject: [yocto] Another in a seemingly infinite chain of errors
> 
> The latest is two things: a warning that the files and directories I
> created in my do_install "were installed but not shipped", followed by an
> error saying that my layer is "not found in the base feeds". Googling
> those two phrases turned up lots of patches intended to fix those errors
> in specific obscure cases, but nothing that explains what they mean, or
> what I should do when it happens to my layer. I don't think I've
> forgotten anything that the Dev Manual says that I need in order to add a
> simple layer.
> 
> --
> 
> Ciao,   Paul D. DeRocco
> Paulmailto:pdero...@ix.netcom.com
> 
> ___
> 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] Another in a seemingly infinite chain of errors

2013-07-05 Thread Luo Zhenhua-B19537 
> -Original Message-
> From: Paul D. DeRocco [mailto:pdero...@ix.netcom.com]
> Sent: Friday, July 05, 2013 2:20 PM
> 
> > From: Zhenhua-B19537
> >
> > FILES_${PN}_append = " xxx" should useful, xxx is the file which is
> > listed in the "were installed but not shipped" message.
> >
> > More info of FILES can be found in
> >
> https://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-
> manual.ht
> ml#var-FILES
> 
> Thanks for the quick response.
> 
> The problem is that every directory that I create in this one recipe is
> in that list, not just the files. This includes things like
> /lib/systemd/system.
[Luo Zhenhua-B19537] Seems like the similar issue as 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4309

> I have another recipe, which is basically the same as the hello.c example,
> except that it is a real program. It works fine without a FILES_${PN}
> variable. So what is it about my failing recipe that makes it need a
> FILES_${PN} variable? It has no do_compile, just a do_install script with
> a bunch of install and ln commands.
[Luo Zhenhua-B19537] Generally "were installed but not shipped" means those 
files are installed into ${D}, but not placed in any resulting package. FILES 
can solve it. If the folder is empty, you can remove it directly. 

> By the way, I also notice it says to use things like ${bindir} for
> standard directories. Is there a comprehensive list of these anywhere? I
> don't find them in the Yocto Dev Manual or Ref Manual.
[Luo Zhenhua-B19537] I am not sure whether such variables are documented in a 
unified doc, I always check it in meta/conf/bitbake.conf or "bitbake -e | grep 
xxx". 


Best Regards,

Zhenhua

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

Re: [yocto] Enabling SFTP on libcurl package

2013-07-17 Thread Luo Zhenhua-B19537 
Add "--with-libssh2" when configure curl. 


Best Regards,

Zhenhua


> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Saddam Quirem
> Sent: Wednesday, July 17, 2013 9:43 PM
> To: yocto@yoctoproject.org
> Subject: [yocto] Enabling SFTP on libcurl package
> 
> I've developing an application that uses libcurl using SFTP to transfer
> data.
> When I finally cross-compiled my application and and tested it, it would
> print this message: "Protocol sftp not supported or disabled in libcurl".
> This means that the libcurl package I built did not have SSH enabled.
> 
> I'm wondering if there is some way I can get SFTP supported in libcurl?
> 
> I'm using meta-fsl-arm BSP for poky-dylan. Tagetting the i.MX6 processor.
> ___
> 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] Enabling SFTP on libcurl package

2013-07-17 Thread Luo Zhenhua-B19537 
Seems libssh2 is not included in oe-core and meta-oe, you should add recipe for 
libssh2 firstly. 


Best Regards,

Zhenhua


> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of squirem
> Sent: Wednesday, July 17, 2013 11:42 PM
> To: yocto@yoctoproject.org
> Subject: Re: [yocto] Enabling SFTP on libcurl package
> 
> Luo Zhenhua-B19537  writes:
> 
> > Add "--with-libssh2" when configure curl.
> 
> It seems that poky did not come with libssh2.
> I'm also having some issues cross-compiling the library myself.
> Any thoughts?
> 
> ___
> 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] any ETA for when the downloadable toolchains will be updated?

2013-07-30 Thread Luo Zhenhua-B19537 
You can find recent version here 
http://autobuilder.yoctoproject.org/pub/nightly/CURRENT/toolchain/, but not 
sure if below issue is resolved. 


Best Regards,

Zhenhua


> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
> Sent: Tuesday, July 30, 2013 5:15 PM
> To: Yocto discussion list
> Subject: [yocto] any ETA for when the downloadable toolchains will be
> updated?
> 
> 
>   based simply on the timestamps, it would appear that the toolchains
> here:
> 
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.4.1/toolchain/
> 
> still contain the script bug involving the now-dead "find" option in
> fedora 19 where -perm no longer accepts a value starting with "+". is
> there any plan to replace those packages with updated versions that work
> properly on fedora 19?
> 
> rday
> 
> --
> 
> 
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
> 
> Twitter:   http://twitter.com/rpjday
> LinkedIn:   http://ca.linkedin.com/in/rpjday
> 
> ___
> 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] Integrate java with yocto

2013-07-31 Thread Luo Zhenhua-B19537 
Hi Aman,

Following is the procedure.

1.   Edit conf/bblayers to append meta-java in BBLAYERS

2.   Add IMAGE_INSTALL_append = " jre-related-pkg-list" in local.conf or 
your image bb file

3.   Build the rootfs image

Since the build of meta-jave is not verified with FSL toolchain, I am not sure 
if the jre build can finish correctly.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Aman Sharma
Sent: Wednesday, July 31, 2013 6:02 PM
To: yocto@yoctoproject.org
Subject: [yocto] Integrate java with yocto

Hi All,

I am new in Yocto,i  need to port Java based application on Freescale based 
powerpc embedded board.I am using Yocto  and Freescale SDK to build the image.

Currently i am trying to include meta-java in yocto directory and trying to 
build image. Can any one please guide me how to proceed in this content.
What is the way to include JRE on embedded board using Yocto.

Thanks in advance for your help.

--
Regards
Aman

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

Re: [yocto] Integrate java with yocto

2013-07-31 Thread Luo Zhenhua-B19537 
Aman,

"jre-related-pkg-list" is just a description, you need to replace it with 
actually package name(e.g. openjdk-7-jre).


Best Regards,

Zhenhua

From: Aman Sharma [mailto:amansh.shar...@gmail.com]
Sent: Wednesday, July 31, 2013 9:10 PM
To: Luo Zhenhua-B19537
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Integrate java with yocto

Hi Luo,

I am getting this error message.
freescale@freescale-sdk:~/SDK/QorIQ-SDK-V1.4-20130625-yocto/build_t4240qds_release$
 bitbake fsl-image-core
Loading cache: 100% 
|##|
 ETA:  00:00:00
Loaded 3302 entries from dependency cache.

Build Configuration:
BB_VERSION= "1.18.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-10.04"
TARGET_SYS= "powerpc-fsl_networking-linux"
MACHINE   = "t4240qds"
DISTRO= "fsl-networking"
DISTRO_VERSION= "1.4"
TUNE_FEATURES = "m32 fpu-hard e6500 altivec"
TARGET_FPU= "hard"
meta
meta-yocto
meta-yocto-bsp= "sdk-v1.4.x:5a7532143a49f59a5c85b08d3daf574fb1eccd8d"
meta-fsl-ppc  = "sdk-v1.4.x:f9fd0a617eb6913f87335c551918315ff4ebe18c"
meta-fsl-ppc-toolchain = "sdk-v1.4.x:8ec94cec04527cb971c125b1ddd2c5375034d723"
meta-virtualization = "sdk-v1.4.x:ad6df4f59cd7646f61db29e8fa51f878329d6f93"
meta-fsl-networking = "(nobranch):00f7a535029ca7ef8c96ba8e9916d4742166bab0"
meta-oe
meta-networking   = "sdk-v1.4.x:7c8dd8f096b64a709175d37a08a4fb02ca263616"
meta-java = "master:59696d89fd33df6953dcb2dd54ccd3b362513f28"

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'jre-related-pkg-list' (but 
/home/freescale/SDK/QorIQ-SDK-V1.4-20130625-yocto/meta-fsl-networking/images/fsl-image-core.bb<http://fsl-image-core.bb>
 RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'jre-related-pkg-list' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['jre-related-pkg-list']
ERROR: Required build target 'fsl-image-core' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-core', 
'jre-related-pkg-list']

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

I added the following line in local.conf file:
# Java preferences.  Could also be in distro config.
PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"
PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"
PREFERRED_VERSION_openjdk-7-jre = "03b21-2.1.8"
PREFERRED_VERSION_icedtea7-native = "2.1.3"
PREFERRED_PROVIDER_openjdk-7-jre = "openjdk-7-jre"


#By aman
IMAGE_INSTALL_append = "jre-related-pkg-list"

Can you please help me in this.
Thanks for your Response.

--
regards
Aman


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

Re: [yocto] Integrate java with yocto

2013-08-01 Thread Luo Zhenhua-B19537 
Add IMAGE_INSTALL_append = " openjdk-7-jre" and rebuild fsl-image-core, please 
be aware the leading space after first ".


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Aman Sharma
Sent: Thursday, August 01, 2013 5:58 PM
To: yocto@yoctoproject.org
Cc: rahul1991.ar...@gmail.com
Subject: Re: [yocto] Integrate java with yocto

Hi all,

I intend to add java (openjdk) to my root file system. I was able to 
successfully add meta-java layer and build the same, packages were built but 
were not added to the root file system.

Following are the steps which i followed to include java in my powerpc.

1.  export 
PATH=$PATH:/home/vvdn/yocto/QorIQ-SDK-V1.3.2-20130325-yocto/bitbake/bin/
[Luo Zhenhua-B19537] this step is not necessary, steps 3 will set the path for 
you.

2 ./scripts/host-prepare.sh

3 source ./fsl-setup-poky -m p1020rdb

Then i used following command to include meta-java utility.

git clone -b master 
git://github.com/woglinde/meta-java.git<http://github.com/woglinde/meta-java.git>

With this i successfully installed meta-java utility.
The i added meta-java to bblayers.conf.file.

Then i added following lines to local.conf file.

# Java preferences.  Could also be in distro config.
  PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"
  PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"
  PREFERRED_VERSION_openjdk-7-jre = "03b21-2.1.8"
  PREFERRED_VERSION_icedtea7-native = "2.1.3"
  PREFERRED_PROVIDER_openjdk-7-jre = "openjdk-7-jre"

After this i tried.

4 bitbake openjdk-7-jre

5 bitbake fsl-image-core

After this i successfully build a root file system but meta-java was not 
included in this build. Can anyone help me regarding this.

Thanks in advance for the help.

Regards

Aman Sharma
On Thu, Aug 1, 2013 at 7:45 AM, Luo Zhenhua-B19537 
mailto:b19...@freescale.com>> wrote:
Aman,

"jre-related-pkg-list" is just a description, you need to replace it with 
actually package name(e.g. openjdk-7-jre).


Best Regards,

Zhenhua

From: Aman Sharma 
[mailto:amansh.shar...@gmail.com<mailto:amansh.shar...@gmail.com>]
Sent: Wednesday, July 31, 2013 9:10 PM
To: Luo Zhenhua-B19537
Cc: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
Subject: Re: [yocto] Integrate java with yocto

Hi Luo,

I am getting this error message.
freescale@freescale-sdk:~/SDK/QorIQ-SDK-V1.4-20130625-yocto/build_t4240qds_release$
 bitbake fsl-image-core
Loading cache: 100% 
|##|
 ETA:  00:00:00
Loaded 3302 entries from dependency cache.

Build Configuration:
BB_VERSION= "1.18.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-10.04"
TARGET_SYS= "powerpc-fsl_networking-linux"
MACHINE   = "t4240qds"
DISTRO= "fsl-networking"
DISTRO_VERSION= "1.4"
TUNE_FEATURES = "m32 fpu-hard e6500 altivec"
TARGET_FPU= "hard"
meta
meta-yocto
meta-yocto-bsp= "sdk-v1.4.x:5a7532143a49f59a5c85b08d3daf574fb1eccd8d"
meta-fsl-ppc  = "sdk-v1.4.x:f9fd0a617eb6913f87335c551918315ff4ebe18c"
meta-fsl-ppc-toolchain = "sdk-v1.4.x:8ec94cec04527cb971c125b1ddd2c5375034d723"
meta-virtualization = "sdk-v1.4.x:ad6df4f59cd7646f61db29e8fa51f878329d6f93"
meta-fsl-networking = "(nobranch):00f7a535029ca7ef8c96ba8e9916d4742166bab0"
meta-oe
meta-networking   = "sdk-v1.4.x:7c8dd8f096b64a709175d37a08a4fb02ca263616"
meta-java = "master:59696d89fd33df6953dcb2dd54ccd3b362513f28"

NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'jre-related-pkg-list' (but 
/home/freescale/SDK/QorIQ-SDK-V1.4-20130625-yocto/meta-fsl-networking/images/fsl-image-core.bb<http://fsl-image-core.bb>
 RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'jre-related-pkg-list' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['jre-related-pkg-list']
ERROR: Required build target 'fsl-image-core' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-core', 
'jre-related-pkg-list']

Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

I added the following line in local.conf file:
# Java preferences.  Could also be in distro config.
PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"
PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"
PREFERRED_VERSION_openjdk-7-jre = "03b21-2.1.8"
PREFERRED_VERSION_icedtea7-native = "2.1.3"
PREFERRED_PROVIDER_openjdk-7-jre = "openjdk-7-jre"


#By aman
IMAGE_INSTALL_append = "jre-related-pkg-list"

Can you please help me in this.
Thanks for your Response.

--
regards
Aman



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

Re: [yocto] [meta-freescale] [meta-fsl-ppc] MPC8572 Machine with Dylan

2013-08-28 Thread Luo Zhenhua-B19537 
Hi Rudi,

Mpc85xx series is not supported and removed since FSL QorIQ SDK 
1.4(QorIQ-SDK-V1.4-20130625-yocto) which is based on Yocto 1.4(dylan), the 
machine configure files are removed from dylan/master of meta-fsl-ppc layer to 
avoid unexpected issues.  
http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc/commit/?h=dylan&id=ee9e6378f4f2651b78bb5ccc804f7dda627569d6

QorIQ SDK 1.3.2 uses denzil of Poky, you can use danny/denzil/edison for image 
build of mpc85xx series.


Best Regards,

Zhenhua

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Rudolf Streif
Sent: Thursday, August 29, 2013 12:34 AM
To: Yocto Discussion Mailing List
Subject: [yocto] [meta-freescale] [meta-fsl-ppc] MPC8572 Machine with Dylan

I am looking to build for MPC8572 with Dylan and checked out the meta-fsl-ppc 
BSP layer. Seems like support for that machine was removed in May [1]. The 
reason given was " *u-boot code base can not support mpc85xx for sdk 1.3.2". 
Howerver, that was contested in a follow-up e-mail. Interestingly, the 
QorIQ-SDK-V1.3.2-20130325-yocto does contain meta-fsl-ppc with support for that 
machine.

I grepped through the git log but could not even find the commit that removed 
it.

Could someone please comment on the status? Is the BSP layer contained in 
QorIQ-SDK-V1.3.2-20130325-yocto compatible with Dylan?


Thanks,
Rudi


[1] https://lists.yoctoproject.org/pipermail/meta-freescale/2013-May/002679.html
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] "tree" link is broken for some layers in http://layers.openembedded.org/layerindex/branch/master/layers/

2013-09-12 Thread Luo Zhenhua-B19537 
Hi, 

When I click the "tree" links of some layers in 
http://layers.openembedded.org/layerindex/branch/master/layers/, "400 Bad 
Request" error appears, can somebody take a look?
Meta-intel
Meta-fsl-arm
Meta-fsl-ppc
Meta-lsi
Meta-ti
...


Best Regards,

Zhenhua

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

Re: [yocto] "tree" link is broken for some layers in http://layers.openembedded.org/layerindex/branch/master/layers/

2013-09-13 Thread Luo Zhenhua-B19537 
Thanks, Paul. 


Best Regards,

Zhenhua


> -Original Message-
> From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com]
> Sent: Friday, September 13, 2013 6:48 PM
> To: Luo Zhenhua-B19537
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] "tree" link is broken for some layers in
> http://layers.openembedded.org/layerindex/branch/master/layers/
> 
> Hi Zhenhua,
> 
> On Friday 13 September 2013 02:29:41 Luo Zhenhua-B19537 wrote:
> > When I click the "tree" links of some layers in
> > http://layers.openembedded.org/layerindex/branch/master/layers/, "400
> > Bad Request" error appears, can somebody take a look? Meta-intel
> > Meta-fsl-arm Meta-fsl-ppc Meta-lsi Meta-ti ...
> 
> Oops, this was my fault. The generated URL is now correct, and I also
> fixed a bug where the URL fields were being cleared when editing a layer
> (and the change history showed that meta-kde was affected by this; I've
> now restored the values for its entry as well).
> 
> Cheers,
> Paul
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre


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

Re: [yocto] [meta-freescale] The updated proposal of FSL Yocto layers reorg - 4-Mar

2013-09-29 Thread Luo Zhenhua-B19537 
Hi Bob,

We are working on the recipes of Layerscape, the first LS SDK will be released 
in the early of 2014. The LS common recipes will be submitted to 
meta-fsl-ppc/meta-fsl-arm when LS is formally released. 

Regarding meta-fsl-layerscape, it can be published in YP official git 
repository(http://git.yoctoproject.org/cgit/cgit.cgi/) and FSL official git 
repository(http://git.yoctoproject.org/cgit/cgit.cgi/)?) if no internal git url 
is referred. 


Best Regards,

Zhenhua

> -Original Message-
> From: Bob Cochran [mailto:yo...@mindchasers.com]
> Sent: Monday, September 30, 2013 9:54 AM
> To: Luo Zhenhua-B19537
> Cc: Yocto discussion list
> Subject: Re: [meta-freescale] The updated proposal of FSL Yocto layers
> reorg - 4-Mar
> 
> Hi Zhenhua,
> 
> Can we get an update on Layerscape?  It's been about 6 months since the
> Yocto layers organization for Layerscape was last talked about on this
> board.
> 
> When will we first see an instance of the stage 2 organization (e.g.,
> meta-fsl-layerscape) in the yocto project source repos
> (http://git.yoctoproject.org/cgit/cgit.cgi/)?
> 
> Thanks,
> 
> Bob
> 
> 
> 
> 
> On 03/03/2013 10:48 PM, Luo Zhenhua-B19537 wrote:
> > Hello all,
> >
> > I have incorporated the comments of previous discussion into the reorg
> > design document, please take a look.
> >
> > *Summary of Yocto reorg*
> >
> > * To support Layerscape release, both ARM architecture and PPC
> > architecture are required to be supported by Yocto.
> >
> > * Currently Yocto support for i.MX SDK and QorIQ SDK are developed and
> > maintained separately, some duplicated packages are not shared between
> > ARM SDK and PPC SDK. And will not be efficient and effective
> > maintained for Layerscape support.
> >
> > * More clear naming of Yocto layers for FSL specific will be helpful
> > for PPC, ARM and Layercape support simultaneously.
> >
> > * Subsequent slides introduces the plan and design of FSL Yocto layers
> > re-org.
> >
> > *FSL Yocto Layers Reorg Diagram*
> >
> > yocto-re-org.png
> >
> > *FSL Yocto Layers Reorg - Stage1*
> >
> > * Stage1:  ~ Jun-2013
> >
> > * Following layers will coexist:
> >
> >poky: the opensource version
> >
> >meta-oe: the opensource branch corresponding to poky
> >
> >meta-virtualization: the opensource virtualization layer
> >
> >meta-fsl-ppc-toolchain: fsl toolchain recipes
> >
> >meta-fsl-ppc: fsl public packages for PPC targets
> >
> >meta-fsl-ppc-private: fsl private packages for PPC targets
> >
> >meta-fsl-arm: fsl packages for ARM targets
> >
> >meta-fsl-demos: demo rootfs recipes of ARM targets
> >
> >meta-fsl-networking: recipes specific to networking SDK
> >
> >Other necessary upstream layers
> >
> > *FSL Yocto Layers Reorg - Stage2*
> >
> > * Stage2: Jul-2013 ~ Dec-2013
> >
> > * Following change will be made:
> >
> >Poky/meta-oe/meta-virtualization for opensource are reused
> >
> >   Following architecture specific layers are maintained in
> > git.am.freescale.net,   git.freescale.com and git.yoctoproject.org
> >
> >  meta-fsl-arm: layer for FSL arm machines
> >
> > meta-fsl-ppc: layer for FSL ppc machines
> >
> >Following SDK specific layers are maintained in
> > git.am.freescale.net and git.freescale.com
> >
> >  meta-fsl-toolchain: layer for fsl toolchain recipes
> >
> >  meta-fsl-multimedia: layer for multimedia SDK
> >
> >  meta-fsl-networking: layer for networking SDK
> >
> >  meta-fsl-layerscape: layer for layerscape SDK
> >
> > *FSL Yocto Layers Reorg - More info*
> >
> > * Layer of getting layers specific to Freescale SDK
> >
> >* Layer name: meta-freescale-sdk
> >
> >* The function of this layer is similar as
> > https://github.com/Freescale/fsl-community-bsp-platform and it is
> > maintained in FSL internal/external git tree
> >
> >* A branch is created for each FSL SDK release to include the
> > scripts to fetch necessary layers of specified version
> >
> > * Multiple branch maintain
> >
> >* Align with the branch policy of poky: denzil, danny, master ...
> >
> >* A tag of sub-layers will be created for each FSL release
> >
> >* Upstream / public branches will try to work with all Yocto
> > releases, while SDK releases could contain a lot of hacks to more
> > things working, or pre-re