On 12-04-10 08:15 PM, kishore.k.bo...@intel.com wrote:
From: Kishore Bodkekishore.k.bo...@intel.com
Romley machine has builtin 82580 Giga bit Ethernet
Controller. Adding the relavent igb nic driver.
Looks fine for the tree, no risk to other BSPs. Correct me
if you'd rather this wait until
Hi Mark,
I met a strange issue while using RPM to generate the rootfs.
In the installation list, if we have 2 RPM packages, say A.rpm and
B.rpm. package A RDEPENDS on package B. While installing the two
packages? Does RPM ensures to install B first and then install A?
The real issue is: we have
On 04/09/2012 03:27 PM, nitin.a.kam...@intel.com wrote:
From: Nitin A Kamblenitin.a.kam...@intel.com
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
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com]
Sent: Monday, April 09, 2012 11:04 PM
To: Om Prakash PAL
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
On Mon, Apr 9, 2012 at 12:31 PM, Om Prakash PAL
On 4/11/12 10:14 AM, Xu, Dongxiao wrote:
Hi Mark,
I met a strange issue while using RPM to generate the rootfs.
In the installation list, if we have 2 RPM packages, say A.rpm and
B.rpm. package A RDEPENDS on package B. While installing the two
packages? Does RPM ensures to install B first and
On Tue, Apr 10, 2012 at 8:40 PM, Lu, Lianhao lianhao...@intel.com wrote:
Saul Wold wrote on 2012-04-11:
On 04/10/2012 08:16 AM, Lu, Lianhao wrote:
Hi Saul,
I think I might have some clues why the python-nativesdk failed at
Hi Bruce,
I need some more info
[1].I want to add kernel dir path into SRC_URI(in
meta-bsp_name/recipe-kernel/linux/linux_3.0.bb), how can we add it ? i.e.
lets imagine that my kernel is located in dir /local/kernel/*
How we can add this kernel into SRC_URI?.(imagine that we don't have
On Wed, 2012-04-11 at 10:25 -0500, Mark Hatle wrote:
On 4/11/12 10:14 AM, Xu, Dongxiao wrote:
Hi Mark,
I met a strange issue while using RPM to generate the rootfs.
In the installation list, if we have 2 RPM packages, say A.rpm and
B.rpm. package A RDEPENDS on package B. While
On Tue, Apr 10, 2012 at 5:13 PM, Rifenbark, Scott M
scott.m.rifenb...@intel.com wrote:
I have recently added the CentOS distribution to the YP QS. The list now
includes Ubuntu, Fedora, openSUSE, and CentOS. Further down in the manual
there are sections detailing the package requirements for
On 4/11/12 10:37 AM, Xu, Dongxiao wrote:
On Wed, 2012-04-11 at 10:25 -0500, Mark Hatle wrote:
On 4/11/12 10:14 AM, Xu, Dongxiao wrote:
Hi Mark,
I met a strange issue while using RPM to generate the rootfs.
In the installation list, if we have 2 RPM packages, say A.rpm and
B.rpm. package A
On Wed, 2012-04-11 at 10:45 -0500, Mark Hatle wrote:
On 4/11/12 10:37 AM, Xu, Dongxiao wrote:
On Wed, 2012-04-11 at 10:25 -0500, Mark Hatle wrote:
On 4/11/12 10:14 AM, Xu, Dongxiao wrote:
Hi Mark,
I met a strange issue while using RPM to generate the rootfs.
In the installation
On 12-04-11 11:24 AM, Om Prakash PAL wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com]
Sent: Monday, April 09, 2012 11:04 PM
To: Om Prakash PAL
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto.
On Mon, Apr 9,
On 4/11/12 10:51 AM, Xu, Dongxiao wrote:
On Wed, 2012-04-11 at 10:45 -0500, Mark Hatle wrote:
On 4/11/12 10:37 AM, Xu, Dongxiao wrote:
On Wed, 2012-04-11 at 10:25 -0500, Mark Hatle wrote:
On 4/11/12 10:14 AM, Xu, Dongxiao wrote:
Hi Mark,
I met a strange issue while using RPM to generate the
On 12-04-11 01:08 PM, Bodke, Kishore K wrote:
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Wednesday, April 11, 2012 6:25 AM
To: Bodke, Kishore K
Cc: yocto@yoctoproject.org; Bruce Ashfield
Subject: Re: [yocto] [PATCH 0/1] [KERNEL] Add igb driver
This is V2 for a fix for YOCTO 2138. V2 pulls in fixes to dosfstools
which address a Boot Error message when attempting to boot in qemu.
The dosfstools patches were cherry-picked directly from master with no
modifications.
The following changes since commit
Fixes [YOCTO 2138]
The initial directory support (-d) added to mkdosfs has proven to be incomplete
and non-compliant with FAT. Rather than continue to maintain this feature and
work around the various issues, we can use mcopy to construct the image.
bootimg.bbclass already depends on
Fixes [YOCTO #1852]
The bootimg class wasn't accounting for non-trivial amount of space
required by the directory entries and FATs for the FAT filesystem.
This patch attempts to make an accurate prediction of FAT overhead and
adjusts the image size accordingly. It assumes no more than 16
Fixes [YOCTO #1852] ... again.
The conversion from sectors to blocks was multiplying by 2 instead
of dividing by 2. Blocks are 1024 bytes, sectors are 512 bytes. The
result was images being much larger than intended.
Reported-by: Tom Zanussi tom.zanu...@intel.com
(From OE-Core rev:
From: Saul Wold s...@linux.intel.com
(From OE-Core rev: a19bfc10e60ddc7e9317654ca7565d39acbc3987)
Signed-off-by: Saul Wold s...@linux.intel.com
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
.../recipes-devtools/dosfstools/dosfstools_2.10.bb |5 -
1 files changed,
From: Scott Garman scott.a.gar...@intel.com
(From OE-Core rev: 735a3e5d3399e29e4d6fa82dabbdd1687eaa29e9)
Signed-off-by: Scott Garman scott.a.gar...@intel.com
Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
---
.../dosfstools/dosfstools/2.6.20-syscall.patch |7 +++
From: Otavio Salvador ota...@ossystems.com.br
This unify recipes for target and native builds and also drops the the
already merged patches.
(From OE-Core rev: 3a401ddce55e185c8ccfdc43c1440fd77daff9ae)
Signed-off-by: Otavio Salvador ota...@ossystems.com.br
Signed-off-by: Richard Purdie
From: Richard Purdie richard.pur...@linuxfoundation.org
It appears msdos image population and fat32 images are incompatible.
This reverts to the 2.10 behaviour of defaulting to fat16 instead of
using fat32 for large images, allowing image generation to work
correctly. This is a workaround and a
I'm working with the poky tree, master branch. I added a few packages to
IMAGE_INSTALL in core-image-minimal.bb. Everything builds fine, and I can see
the built images in each tmp/work subdirectory for my IMAGE_INSTALL packages.
However, I find that some of the image executables that were
On 04/09/2012 03:15 PM, Yang Shi wrote:
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
Is there a page somewhere that gives a rough idea of how quickly a full build
runs on various systems?
I need a faster build platform, but want to get a reasonable price /
performance balance ;-)
I'm looking at something like an i7-2700K but am not yet tied...
Chris Tapp
On 04/11/2012 04:42 PM, Chris Tapp wrote:
Is there a page somewhere that gives a rough idea of how quickly a full build
runs on various systems?
I need a faster build platform, but want to get a reasonable price /
performance balance ;-)
I'm looking at something like an i7-2700K but am not
On 04/11/2012 01:42 PM, Chris Tapp wrote:
Is there a page somewhere that gives a rough idea of how quickly a full build
runs on various systems?
I need a faster build platform, but want to get a reasonable price /
performance balance ;-)
I'm looking at something like an i7-2700K but
Excellent topic for a wiki page.
On Wed, Apr 11, 2012 at 5:30 PM, Darren Hart dvh...@linux.intel.com wrote:
On 04/11/2012 01:42 PM, Chris Tapp wrote:
Is there a page somewhere that gives a rough idea of how quickly a full
build runs on various systems?
I need a faster build platform, but
/nightly/20120411-2
--
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 04/11/2012 08:30 PM, Darren Hart wrote:
SSDs are one way to
go, but we've been known to chew through them and they aren't priced as
consumables.
Hi Darren,
Could you please elaborate on been known to chew through them?
Are you running into an upper limit on write / erase cycles? Are you
30 matches
Mail list logo
