Looking good to me. The revised patch would ideally be sent to
bitbake-de...@lists.openembedded.org
Hi, Josh
Thanks for the review. I will rebase to the latest poky master and resend the
patch to the bitbake-devel list too!
criping
___
yocto
From: Liping Ke liping...@intel.com
The two patches are the implmentation of Hob Cache for accelarating
UI switching. If one configuration has been saved before, when user
switch back to the same configuration combination, we will use the
cache content instead of re-triggering parsing/loading
From: Liping Ke liping...@intel.com
This patch is the centralized place for storing Hob attributes.
Most of informations in Prefs will be used when caching user-select
packages information. Those information will be the cache hash-key
which is useful in deciding whether the configuration
From: Liping Ke liping...@intel.com
This patch is to cache target dependency tree for Hob (cache impl).
Hob User might switch between different configuration combinations
(machine, sdk-machine, distro, etc). Each dependency re-calcuation
might be time consuming. We use a hashset to cache those
From: Liping Ke liping...@intel.com
The series of patch are for mplementing multiple extra cache fields
request support.If user needs to request extra cache fields besides
CoreRecipeInfo fields, just add a new XXXRecipeInfo class definition
as Image Creator UI Hob Does.
For implementing this new
From: Liping Ke liping...@intel.com
This patch is for refactorying current cache implementation, the
main reason is for introducing extra cache fields requests for
image creator as well as other users. The refactory parts include:
Move cache data retrieve methods out of Cache Data Fields
From: Liping Ke liping...@intel.com
Extra RecipeInfo will be all defined in this file. Currently,
Only Hob (Image Creator) Requests some extra fields. So
HobRecipeInfo is defined. It's named HobRecipeInfo because it
is introduced by 'hob'. Users could also introduce other
RecipeInfo or simply use
From: Liping Ke liping...@intel.com
This patch is to support extra cache. If user needs to request
extra cache fields besides CoreRecipeInfo fields, just add a new
XXXRecipeInfo class definition as Hob Does.
Currently supported Extra RecipeInfo name is an array. We can
support multiple extra
to finish this refactory.
Thanks Regards,
criping
-Original Message-
From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org]
Sent: Thursday, May 19, 2011 8:10 AM
To: Ke, Liping
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] [PATCH 0/4][Image Creator]Put extra requested
Creator]Put extra requested fields into
different cache files
From: Liping Ke liping...@intel.com
Below four patches are for putting extra requested fields inito different
cache files instead of using only on bb_cache.dat. Now image creator need
extra three fields. And in the future
Hi, Josh
Thanks for your very careful review indeed! I will correct them and resend the
patch!
Regards,
criping
-Original Message-
From: Joshua Lock [mailto:j...@linux.intel.com]
Sent: Friday, April 29, 2011 4:32 AM
To: Ke, Liping
Cc: yocto@yoctoproject.org
Subject: Re: [yocto
, Ke, Liping wrote:
Hi, Jessica and Josh
After looking into the cache.py, as well as the bug 770 description, I have
following questions:
1. Valid Cache Problem: we only have one cache file, right?
Use scenario 1: If developer firstly use ui mode, and then non-ui mode, the
cache file
Hi, Travaglia
1. Our our java code and eclipse code is in TCF upstream community
already (both Agent C code and java code part). Yet the community code is
slightly different with our poky-TCF. TCF upstream disable login process, yet
our local poky-TCF have login authentication.
So if
To: Ke, Liping; Lu, Lianhao
Cc: yocto@yoctoproject.org
Subject: RE: current status for ADT
Liping and Lianhao,
Attached is the updated 1.0 test template, feel free to add more test
cases.
I think we're building RC3 over the weekend, and once the build is done,
we should test against
Hi, Jessica
We use today's latest poky master which includes all our own fixes to build
(arm, i586, mips) target fs and cross toolchains. And then we run below test:
Test environment:
1. For the available repo, use adt-installer installed toolchain: i686-arm.
2. For meta-toolchainsdk
Hi, Jessica
I am trying the adt-installer. The temporary repo contains some testing file,
yet there're no
short symbolic names for them. For example: under
adtrepo.yoctoproject.org/1.0/rootfs/qemuarm/
there's no symbolic file of zImage-qemuarm.bin or
poky-image-minimal-qemuarm.tar.bz2.
All
Hi, all
When I redo bitbake linux-libc-headers today, I repeatedly meet below do_fetch
error, anybody could help to have a look?
Thanks a lot!
criping
-Original Message-
From: Ke, Liping
Sent: Thursday, February 17, 2011 5:07 PM
To: Ke, Liping
Subject: fetch_error
Loading cache
Hi, Jiajun
since sanity test works fine now, just want to know if there's any possible for
adding some test cases for SDK side.
1. We want to know whether unfs qemu could work fine. Since we only support
booting unfs qemu in with our SDK plugins (Eclipse, ANJUTA)
2. When our SDK installer is
-
From: Lu, Lianhao
Sent: Thursday, January 06, 2011 10:12 AM
To: Flanagan, Elizabeth; Zhang, Jessica
Cc: Ke, Liping; yocto@yoctoproject.org
Subject: Setup repository for ADT installer
Hi Beth and Jessica,
Here is a summary of how I set up the IPK repo for ADT installer on my
local
Hi, Jessica
I verified that if we use git from shell to clone a tree first, create the new
project, and then use egit to manage the project,
everything is fine.
It will detect that .git repository is there and will not repeatedly create
one.
So egit will not conflict with native command line
Hi, Jessica
I have tried the existing egit plugin. It is a true powerful plugin, but I am
afraid it can't be communicating well with poky-meta-project plugin.
Below is some details
advantages:
1. EGIT support all sorts of protocols, including ftp, ssh, git, http, so we
can easily pull/push the
[Summary]
1. OSEL SDK related jobs
2. Others
[Details]
SDK related jobs:
1. Modified sdk installer scripts according to Josh's feedback, including
a. Folder reorganization per Josh's suggestion, make the structure more user
friendly
b. Move sudo to a smaller granularity, so that
firstly.
Thanks Regards,
criping
On 10-12-14 02:40 AM, Ke, Liping wrote:
Hi, Jessica
I found qemu bin file name convention is different for different
archs, for example, for x86, it is bzImage-qemuXXX.
For arm, it is zImage-qemuXXX. My question is why it is bzXXX or zXXX
[Summary]
1. OSEL SDK related jobs
2. Others
[Details]
SDK related jobs:
1. Modified the first installer script according to Jessica and RP's input,
including:
1) all sorts of echo message formalization.
2) Make script could be run anywhere.
3) solve the privilege level
Hi, all
Apart from Ke's suggestion that I need to add chksum for download file,
any other feedbacks?
Thanks Regards,
criping
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Ke, Liping
Sent: Friday, December 17, 2010 11:39
Hi, Jessica and all
If anyone who want to try installer scripts, we will have a poweroff tomorrow,
so I am not sure whether lianhao's repository still works or not.
Just for your info!
Thanks Regards,
criping
___
yocto mailing list
Hi, Jessica
Another thing is that after we bitbake the tarball, since bitbake will help us
to do_unpack, so untar opkg is not needed actually. After bitbake job is
finished,
I will change the installer script code to remove untar opkg tarball steps.
Thanks Regards,
criping
Hi, Jessica and Josh
This is a simple bb class file for generating installer tarball. And thanks for
Lianhao/ke/Dexuan...'s
help which saves me lots of efforts...
It contains below steps:
1. fetch opkg source tarball to download location and copy other six files
(opkg conf, scripts, user
Thanks Regards,
criping
-Original Message-
From: Zhang, Jessica
Sent: Wednesday, December 15, 2010 5:10 PM
To: Ke, Liping; Lu, Lianhao
Cc: yocto@yoctoproject.org
Subject: RE: [yocto] Try latest yocto adt script installer
Liping,
The newly update scripts are at:
http
Then can you modify the code before downloading each file, check
whether its
already exist or not, if so, prompt the user to confirm re-download or
skip?
And remove the existing checking for the download directory?
Hi, Jessica
Sure. I will change it and send you the updated patch a little
: Zhang, Jessica
Sent: Thursday, December 16, 2010 12:44 PM
To: Ke, Liping; Lu, Lianhao
Cc: yocto@yoctoproject.org
Subject: RE: [yocto] Try latest yocto adt script installer
Ke, Liping wrote:
Hi, Jessica
I have tested newly added image types (sato minimal) in the user
configuration
] On Behalf Of Ke, Liping
Sent: Tuesday, December 14, 2010 2:40 PM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Try latest yocto adt script installer
Why we must run the script under the adt-installer directory?
Actually
I
tried to run under $HOME or / but specifying
about what kinds of echo message is most wanted by user. I
temporarily put
It under folder ${POKYBASE}/scripts/adt_installer
For testing, Lianhao temporarily make SDK_VERSION=0.9-post, it's now defined
in Yocto_installer.conf.
Thanks Regards,
criping
-Original Message-
From: Ke, Liping
Hi, Scott
Thanks for the review! Sure, I will use the script following distro-team
conventions.
And also, $MYNAME will be used in the final patch. And the debug line for
building will be
removed when I send the final patch.
Thanks Regards,
criping
One final thing - when you resubmit your
to be changed. It will be not good.
Thanks Regards,
criping
We'll sync later tonight...
Thanks,
Jessica
Ke, Liping wrote:
Hi, Jessica
For tracing the file, I temporarily checked in all needed files into
my branch:
http://git.pokylinux.org/cgit/cgit.cgi/poky-
contrib/log/?h
.
Any problem, just let me know.
Thanks Regards,
criping
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Ke, Liping
Sent: Wednesday, December 15, 2010 1:03 PM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org
Subject: Re
: Monday, December 13, 2010 10:16 AM
To: Ke, Liping
Cc: Richard Purdie; Zhang, Jessica; Lu, Lianhao; Cui, Dexuan;
yocto@yoctoproject.org
Subject: Re: Add extra parameters for qemu script
On 12/12/2010 05:43 PM, Ke, Liping wrote:
I tend to feel that this approach is more flexible, and scales
Why we must run the script under the adt-installer directory? Actually
I
tried to run under $HOME or / but specifying the full path to
yocto_installer, and got the error:
[ADT_INST] script file util is not found!
Oh, it's caused by the include grammar. I need to check how to solve the
...@yoctoproject.org] On Behalf Of Ke, Liping
Sent: Tuesday, December 14, 2010 3:41 PM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org
Subject: [yocto] Questions about the name of qemu bin file for
different archs
Hi, Jessica
I found qemu bin file name convention is different for different archs
Hi, Jessica Josh
When we are trying to run installer script on lianhao's x86_64 machine, we
found if the images are build in two days, according to current version naming
convention, some of the packages will be installed to
/opt/poky/0.9+snapshot-20101210, some will be to
Hi, Jessica
I have put the installer script tar ball in the below links:
http://llu-piketon.sh.intel.com/installer.tar
You can have a try. Below is some key notes:
1. since now version has problems, we have submit bug 586
http://bugzilla.pokylinux.org/show_bug.cgi?id=586
So currently we have
Hi, Scott
The patch is in the attachment for your review. Below is some notes:
1) Basically I wouldn't like to change any logic of the original code.
2) -serial stdio and -nographic options are removed since they're be covered by
the extra parameters.
3) User input would be $poky-qemu qemux86
The first thing I read was in the patch was:
+# following are for testing in my machine. it will be moved when
+# going into code repository
+export http_proxy=
+export HTTP_PROXY=
+export HTTPS_PROXY=
+export https_proxy=
+export ftp_proxy=
+export FTP_PROXY=
which it
Hi, Jessica
FYI.
TCF terminal/shell java code part is now in upstream.
Thanks Regards,
criping
-Original Message-
From: bugzilla-dae...@eclipse.org [mailto:bugzilla-dae...@eclipse.org]
Sent: Wednesday, December 08, 2010 11:54 PM
To: Ke, Liping
Subject: [Bug 246987] [tcf] Would
Hi, Jessica
I have updated the script file which modifies all your input (prompts and the
discussion result in the weekly meeting such as logfile, go on installing when
/var/lib/opkg exists, etc).
I have tested with lianhao's repository (x86_64 native sdk has some problem,
he's now fixing
-
From: Ke, Liping
Sent: Monday, December 06, 2010 6:15 PM
To: Ke, Liping; Zhang, Jessica; Lu, Lianhao; Tian, Kevin
Cc: yocto@yoctoproject.org
Subject: RE: yocto_installer test script update
Just one thing, if directly tee, check_result will get wrong output
result.
So I did not tee opkg
Ops. Seems I made concurrent changes again
Seems I need to redo today's work
I will update the final files a little later. Just wait.
criping
-Original Message-
From: Zhang, Jessica
Sent: Tuesday, December 07, 2010 9:34 AM
To: Ke, Liping; Lu, Lianhao
Cc: yocto
the final files a little later. Just wait.
why don't you setup a master repo on git.pokylinux.org? anyway we
need such thing finally and now you have multiple people touching
same code...
Yes, realize the issue from today's situation, I'll setup a repo for
the
installer once Liping's
Hi, Jessica Scott
I am now look...@the task of User specified qemu config support, desc We'll
provide user an edit box which allows advanced qemu user to specify arbitrary
qemu configuration to meet their needs, which the poky-qemu scrip will just
append the config list towards the end of
Liping,
I think this is consistent with the current SDK tarball installation
that by
default going under /opt/poky. Since our installer script will install
things under /opt/poky as well, using sudo to run the script should be
fine
till we can install the host cross toolchain under user
50 matches
Mail list logo