When using Hob in Yocto Project, I found a issue when deleting layers. I
think I ever raised this problem before.
Let me briefly introduce how layer removal works in Hob. When user
changes a layer, it will following the below steps
1) init the cooker.
2) set new layers to cooker.
3) parse configu
On Mon, 26 Mar 2012 22:45:16 +0100
Richard Purdie wrote:
> I'm still a little surprised we don't make any system() calls though.
> I just tried putting a os.system("true") call into the "breakit"
> class and it doesn't trigger the warnings. Could that be down to the
> lack of a popen wrapper?
I
my sutdent.
On Tue, Mar 27, 2012 at 10:33 AM, Ni Qingliang
wrote:
> who are using archlinux? I want to talk about gconf compile fail
> problem.
>
>
> --
> Yi Qingliang
> niqingli...@insigma.com.cn
> https://niqingliang2003.wordpress.com
>
> ___
> yocto
who are using archlinux? I want to talk about gconf compile fail
problem.
--
Yi Qingliang
niqingli...@insigma.com.cn
https://niqingliang2003.wordpress.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Thanks, Richard. Clearer now but not entirely.
> >> BBMASK removes recipes from being parsed. It does not remove them from
> >> images although that would I guess be an indirect result since you could
> >>no longer build them.
>
> Yes, it removes it from being parsed. I used, for test although no
On Mon, 2012-03-26 at 12:42 -0700, Rudolf Streif wrote:
> Another variable that seems to be dropped from the latest 1.1.1
> revision of the Reference Manual is BBMASK. In previous versions of
> the manual it was explained that this variable can be used to remove
> packages from images. However, tha
Rudi,
Great comments! Thanks very much. I will immediately update the revision
history tables to show the 1.2 release as WIP. Not having it there did cause
you confusion. Good suggestion.
Regarding your other observations. If you have the time I would appreciate you
looking at the YP Deve
Scott,
**
>
> >>
> http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html
> .
>
> ** **
>
> Yes, I looked at that one but I now noticed that I referenced it
incorrectly. This is the latest version, however, in the revision history
it shows "Revision 1.1, October 6, 2011,
From: Rahul Saxena
The Cedar Trail PVR driver consists of user-space binaries that enable
the Video and Graphics acceleration capabilites of the Power VR SGX545
Integrated Graphics Controller in the Cedarview processor.
The driver binaries are provided under "Intel Free Distribution Binary Licen
From: Rahul Saxena
The license type in libva recipe was incorrect. Changed it to MIT
Signed-off-by: Rahul Saxena
---
.../recipes-multimedia/libva/libva_1.0.15.bb |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-cedartrail/recipes-multimedia/libva/libva_1
From: Rahul Saxena
SRC_REV_meta for no-pvr case updated to be same as that used for pvr build
Signed-off-by: Rahul Saxena
---
.../recipes-kernel/linux/linux-yocto_3.0.bbappend |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/meta-cedartrail/recipes-kernel/linux/linux-
From: Rahul Saxena
Current poky/edison points to linux-yocto-3.0-1.1.x.git repo. However this repo
does not have
cedartrail branch. Hence point to linux-yocto_3.0 via kernel recipe append
files
Signed-off-by: Rahul Saxena
---
.../linux/linux-yocto-rt_3.0.bbappend |3 +++
..
From: Rahul Saxena
Update sato images to include web-webkit and audio & video samples
Signed-off-by: Rahul Saxena
---
.../images/core-image-sato-dev.bbappend|3 +++
.../images/core-image-sato-sdk.bbappend|3 +++
.../recipes-sato/images/core-image-sato.bbappend
From: Rahul Saxena
Seperate machconfig files for pvr and no-pvr case
Signed-off-by: Rahul Saxena
---
.../formfactor/cedartrail-nopvr/machconfig |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
create mode 100644
meta-cedartrail/recipes-bsp/formfactor/formfactor/cedartrail
From: Rahul Saxena
Install Ogg format audio and video sample files
Signed-off-by: Rahul Saxena
---
.../ogg-CC-BY-3.0-music-samples_0.1.bb | 20
.../video-samples/bigbuckbunny-ogg.bb | 20
2 files changed, 40 insertions(+),
From: Rahul Saxena
The libva recipe is based on libva recipe published by Tom Zanussi
in meta-intel/common area in the 1.2_Mx branches. The main difference is
that this recipe sources the packages from the Cedar Trail section of
the MeeGo download website.
Signed-off-by: Rahul Saxena
---
meta-
From: Rahul Saxena
Modify kernel recipes to enable pvr kernel patches and to include
additional Kernel config files for pvr driver
Signed-off-by: Rahul Saxena
---
.../linux/linux-yocto-rt_3.0.bbappend | 13 -
.../recipes-kernel/linux/linux-yocto_3.0.bbappend | 15
From: Rahul Saxena
Seperate xserver configuration files, one file each for the case of with pvr
graphics
driver and for "no pvr" (i.e. with VESA driver)
Signed-off-by: Rahul Saxena
---
.../xserver-xf86-config/cedartrail-nopvr/xorg.conf | 26
.../xserver-xf86-config/ced
From: Rahul Saxena
Recipe is copied from n450-audio.bb with a few parameters changed
to adjust volume settings for Front mixer during boot.
Signed-off-by: Rahul Saxena
---
.../cedartrail-audio/cedartrail-audio.bb | 30 ++
.../cedartrail-audio/cedartrail-audio
From: Rahul Saxena
Update README file with information on building image with PVR graphics driver.
Also provide info on enabling build of recipes for glxgears demo apps,
video and music samples.
Signed-off-by: Rahul Saxena
---
meta-cedartrail/README | 50
From: Rahul Saxena
Update BBFILES to include the path to xserver-xf86-dri-lite_1.9.3.bb
Cedar Trail PVR driver is dependent on Version 1.9.3 of xserver.
Signed-off-by: Rahul Saxena
---
meta-cedartrail/conf/layer.conf |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/m
From: Rahul Saxena
Seperate Cedar Trail machine configuration files, one file each for build
with pvr graphics driver and without pvr driver (with VESA driver)
The Cedar Trail platform is based on the Cedarview processor (Intel® Atom™
N2600, N2800 and D2700 processor)and Tiger Point Chipset (Inte
From: Rahul Saxena
Cover letter for updating the Cedar Trail BSP (meta-cedartrail) with
PVR Graphics driver. This patch set updates meta-cedartrail (edison branch)
to include Power VR driver for Graphics and Video hardware acceleration.
The patches enable BSP build with PVR driver or VESA driver
On Mon, 2012-03-26 at 12:18 -0500, Peter Seebach wrote:
> On Mon, 26 Mar 2012 17:47:29 +0100
> Richard Purdie wrote:
>
> > This is pretty much what we do at the moment, it gets unset after we
> > load. Pseudo is of course disabled at this point.
> >
> > I guess we just got lucky to this point an
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
have unionfs feature.
Without UNION FS enabled in kernel, minimal liveCD image can be bootup to
igno
[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.
Signed-off-by: Yang Shi
---
m
[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
have unionfs feature.
Signed-off-by: Yang Shi
---
meta/recipes-core/initrdscripts/fil
Rudi,
I would like you to examine the "latest" documents (the ones under
development). I have added some new licensing information and would like your
feedback for this upcoming version. There are licensing discussions in both
the latest versions of the BSP Guide and the reference manual. Si
>
> >> there's *way* too much coverage of licensing sprinkled throughout.
> >> most people are not going to care about licensing until the time comes
> >> to maybe start distributing their BSP.
>
> The ability of collecting licensing information, tracking license changes
and providing the license i
Oh, nevermind, I just realized: We use antimagic as the implementation
goo for PSEUDO_DISABLED.
So a call to os.popen() from a program which has PSEUDO_DISABLED set is
going to think it's in antimagic mode.
And suddenly, the trick is revealed:
os.popen() is bypassing all the runqueue stuff whic
On Sat, 24 Mar 2012 17:15:15 +
Richard Purdie wrote:
> What puzzles me is we get this value from envbackup[key] =
> os.environ.get("PSEUDO_PREFIX") so its already not in the environment.
>
> So basically if we read "PSEUDO_PREFIX" from the environment we get
> nothing. If we unset the value
Another variable that seems to be dropped from the latest 1.1.1 revision of
the Reference Manual is BBMASK. In previous versions of the manual it was
explained that this variable can be used to remove packages from images.
However, that did not work for me and it did not surprise me either.
To inc
On Mon, 26 Mar 2012 17:47:29 +0100
Richard Purdie wrote:
> This is pretty much what we do at the moment, it gets unset after we
> load. Pseudo is of course disabled at this point.
>
> I guess we just got lucky to this point and avoided "Bad Things"?
I suspect so. What's weird to me is that PSE
Hi,
I am looking for recipe of glibc-2.11.1 version. I googled for it but no
success. Can anyone please suggest me the link from where i can download
the same?
Thanks and Regards
Navani Kamal Srivastava
___
yocto mailing list
yocto@yoctoproject.org
http
Hi All,
Experience survey of Using Yocto 1.2
Q: Which architecture did you choose to build?
A: qemu x86 (minimal) & atom-pc (minimal)
Q: How easily were you able to build an image and boot an image?
A: Reasonably easy to create and boot up an image the "as-is" way(terminal).
Q: Is there any sur
On Mon, 2012-03-26 at 11:44 -0500, Peter Seebach wrote:
> On Sat, 24 Mar 2012 17:41:43 +
> Richard Purdie wrote:
>
> > One or the other of the above on their own doesn't do this. Funky.
>
> That's very strange. I wouldn't have expected LOCALSTATEDIR to have
> any effect either way; it might
On Sat, 24 Mar 2012 17:41:43 +
Richard Purdie wrote:
> One or the other of the above on their own doesn't do this. Funky.
That's very strange. I wouldn't have expected LOCALSTATEDIR to have
any effect either way; it might change how pseudo runs, but it shouldn't
affect whether it's being en
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
> Sent: Sunday, March 25, 2012 9:17 AM
> To: Yocto discussion list
> Subject: [yocto] meta-x32: disagreement between ref manual and
> README.TXT
>
>
> p
On Mon, 2012-03-26 at 14:26 +, Rifenbark, Scott M wrote:
> Is BSP licensing different than non-BSP licensing? If not, then licensing
> could be combined into a single section. Can someone answer this for me?
>
The focus of those sections are different and should probably be in
separate sec
Typo fixed. Nitin needs to respond on the apparent core inconsistency.
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Robert P. J. Day
Sent: Sunday, March 25, 2012 10:17 AM
To: Yocto discussion list
Subject: [yocto] met
Is BSP licensing different than non-BSP licensing? If not, then licensing
could be combined into a single section. Can someone answer this for me?
Also, good point on the BSP guide appearing as a chapter in the reference
manual. I have not liked this. Is there any rational reason to have it
On 12-03-23 05:52 PM, Darren Hart wrote:
In support of the self-hosted-image, add CONFIG_PCNET32 to the common-pc BSP
default cfg. This enables the qemux86 image to be run on both qemux86 machines
as well as the vmware 32b machine. Since the qemux86 machine optionally supports
pcnet, this seems a
On Monday 26 March 2012 14:19:56 Paul Eggleton wrote:
> On Monday 26 March 2012 14:55:40 Samuel Stirtzel wrote:
> > meta-kde has no mailing list, so I'm looking for a list to host the
> > discussion, any suggestions?
>
> Probably just the oe-devel list - if the volume of commits gets too high
Er,
On Monday 26 March 2012 14:55:40 Samuel Stirtzel wrote:
> the development of meta-kde has come to a point where kde-applications
> can be tested (and maybe used).
>
> Status of meta-kde:
> Most common applications work, for example:
> Calligra (not all of the toolkit), Kate, KCalc, Konqueror, Kwin
Op 26 mrt. 2012, om 07:55 heeft Samuel Stirtzel het volgende geschreven:
> Hi,
> the development of meta-kde has come to a point where kde-applications
> can be tested (and maybe used).
>
> Status of meta-kde:
> Most common applications work, for example:
> Calligra (not all of the toolkit), Kat
Hi,
the development of meta-kde has come to a point where kde-applications
can be tested (and maybe used).
Status of meta-kde:
Most common applications work, for example:
Calligra (not all of the toolkit), Kate, KCalc, Konqueror, Kwin &
Kwin_gles (KDE window manager), Okular and the applications f
could have mentioned this in my previous post, but there are
numerous uses of the phrase "poky" in, for instance, the yocto
reference manual that need to be scrapped.
as one example, toolchains that used to be untarred under /opt/poky
now appear to belong (more reasonably) under /usr/local.
currently, ch 5 of the reference manual claims that a generated
"meta-toolchain" tarball should be unpacked under /opt/poky, which
might be *historically* correct but i just baked a meta-toolchain and
its tarball contents are all prefixed with "./usr/local/", which seems
inconsistent with that.
still clawing my way through the ref manual and it seems that
there's *way* too much coverage of licensing sprinkled throughout.
most people are not going to care about licensing until the time comes
to maybe start distributing their BSP.
as it stands, in the *development* version of the ref
Hi Song,
Just wondering how many volunteers for the Beta release you have. Do you
think it would be possible to add some usability testing of Hob to the
Beta programme? This would involve us contacting a few of the volunteers
and asking them to do a couple of simple things with Hob while we watch
On Mon, 2012-03-26 at 02:43 -0500, Peter Seebach wrote:
> On Sat, 24 Mar 2012 17:15:15 +
> Richard Purdie wrote:
>
> > This implies that once we enable pseudo for a child, there is some
> > change in the parent which persists.
>
> Hmm.
>
> Is the parent running with pseudo loaded? If it we
Hello,
On Thu, 2012-03-15 at 18:37 +0530, Joshua Immanuel wrote:
> In yocto I find that the live image (hddimg) is generated
> using syslinux (in bootimg.bbclass). But, I find there has been no
> check enforced to find whether the filesystem size exceeds 1 GB. The
> image will not boot if
On Sat, 24 Mar 2012 17:15:15 +
Richard Purdie wrote:
> This implies that once we enable pseudo for a child, there is some
> change in the parent which persists.
Hmm.
Is the parent running with pseudo loaded? If it were, then I would
expect this -- pseudo does some environment magic that ca
53 matches
Mail list logo
