On 04/04/2013 12:14 PM, Bodke, Kishore K wrote:
Hi Bruce/Darren,
I do not see Linux-yocto-3.0 kernel branch in git repo.
Is it no longer available?
Cedartrail BSP for 1.3 Yocto (danny) supports only 3.0 kernel.
I am not sure how Paul is able to build this bsp?
Do you mean you don't
From: Bodke, Kishore K [mailto:kishore.k.bo...@intel.com]
Yeah, if you want to try a clean build, just keep the
downloads directory alive and have this pointed to your
DL_DIR in your local.conf.
The clean build didn't solve the problem. Here's what I did:
Re-downloaded and extracted
-Original Message-
From: Paul D. DeRocco [mailto:pdero...@ix.netcom.com]
Sent: Friday, April 05, 2013 10:06 AM
To: Bodke, Kishore K; yocto@yoctoproject.org
Subject: RE: [yocto] This one can't be me...
From: Bodke, Kishore K [mailto:kishore.k.bo...@intel.com]
Yeah, if you want to try
From: Bodke, Kishore K
Here are the config parameters for the clean build that I am
doing now.
kishore@kishore-desktop:/usr/local/src/cedartrail/build/tmp/wo
rk/cedartrail_nopvr-poky-linux/linux-yocto-3.0.32+git1
+bf5ee4945ee6d748e6abe16356f2357f76b5e2f0_1+1e79e03d115ed17788
-Original Message-
From: Paul D. DeRocco [mailto:pdero...@ix.netcom.com]
Sent: Friday, April 05, 2013 11:49 AM
To: Bodke, Kishore K; yocto@yoctoproject.org
Subject: RE: [yocto] This one can't be me...
From: Bodke, Kishore K
Here are the config parameters for the clean build that I am
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Paul D. DeRocco
Sent: Friday, April 05, 2013 3:46 PM
To: yocto@yoctoproject.org
Subject: Re: [yocto] This one can't be me...
From: Bodke, Kishore K [mailto:kishore.k.bo
On Fri, 2013-04-05 at 11:48 -0700, Paul D. DeRocco wrote:
From: Bodke, Kishore K
Here are the config parameters for the clean build that I am
doing now.
kishore@kishore-desktop:/usr/local/src/cedartrail/build/tmp/wo
rk/cedartrail_nopvr-poky-linux/linux-yocto-3.0.32+git1
From: Sean Liming
I have the build working with this bblayers listing:
BBLAYERS ?= \
/home/usr/Yocto1.3/poky-danny-8.0/meta \
/home/usr/Yocto1.3/poky-danny-8.0/meta-yocto \
/home/usr/Yocto1.3/poky-danny-8.0/meta-intel \
On 04/03/2013 05:32 PM, Paul D. DeRocco wrote:
From: Bodke, Kishore K
It's surprising that you don't see anything under
/home/pauld/yocto-atom/build/tmp/work/cedartrail_nopvr-poky-li
nux/linux-yoct
o-3.0.32+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+1e79e
03d115ed177882
On 04/03/2013 05:21 PM, Paul D. DeRocco wrote:
From: Darren Hart
Are you building with the rm work setting? Otherwise, that
should not be
empty unless you have more than one linux-yocto* directory
and the other
is populated.
If not, verify rm work is not on and just build the kernel:
-Original Message-
From: Darren Hart [mailto:dvh...@linux.intel.com]
Sent: Thursday, April 04, 2013 10:19 AM
To: Paul D. DeRocco
Cc: yocto@yoctoproject.org; Bodke, Kishore K
Subject: Re: [yocto] This one can't be me...
On 04/03/2013 05:21 PM, Paul D. DeRocco wrote:
From: Darren Hart
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Bodke, Kishore K
Sent: Thursday, April 04, 2013 11:31 AM
To: Darren Hart; Paul D. DeRocco
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] This one can't be me...
-Original
: [yocto] This one can't be me...
Hi Paul,
First off, please CC the relevant maintainers of the recipes and BSPs
you are having trouble with. The README in the cedartrail BSP lists
Kishore as the maintainer, now on CC. This will help improve response
time to your post as well as getting the right
On 04/03/2013 12:57 PM, Paul D. DeRocco wrote:
From: Darren Hart
The most obvious question is whether or not the kernel you built has
ramdisk support. You can do this by analyzing the .config file in your
linux-yocto build tree
(build/tmp/work/cedartrail.../linux-yocto*/linux-cedartrail-st
From: Darren Hart [mailto:dvh...@linux.intel.com]
Are you building with the rm work setting? Otherwise, that
should not be
empty unless you have more than one linux-yocto* directory
and the other is populated.
That option is off, and there is no other linux-yocto* directory.
If not,
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Paul D. DeRocco
Sent: Wednesday, April 03, 2013 1:50 PM
To: 'Darren Hart'
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] This one can't be me...
From: Darren Hart [mailto:dvh
On 04/03/2013 01:50 PM, Paul D. DeRocco wrote:
From: Darren Hart [mailto:dvh...@linux.intel.com]
Are you building with the rm work setting? Otherwise, that
should not be
empty unless you have more than one linux-yocto* directory
and the other is populated.
That option is off, and
From: Darren Hart
Are you building with the rm work setting? Otherwise, that
should not be
empty unless you have more than one linux-yocto* directory
and the other
is populated.
If not, verify rm work is not on and just build the kernel:
$ bitbake linux-yocto -c cleansstate
$
From: Bodke, Kishore K
It's surprising that you don't see anything under
/home/pauld/yocto-atom/build/tmp/work/cedartrail_nopvr-poky-li
nux/linux-yoct
o-3.0.32+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+1e79e
03d115ed177882
I've successfully built core-image-base-cedartrail-nopvr, with NO
modifications, no meta-oe layer to pull in Samba, no attempt to partition
the flash drive, just the .hddimg file dd'ed to /dev/sdb, to see if I can
get something, anything to boot out of the box.
I get a kernel panic when it tries
Followup:
I figured I'd try a sato build, since that's what the example on the BSP
page uses. But core-image-sato-cedartrail-nopvr panics in the same way as
core-image-base-cedartrail-nopvr. For sato, I surmised maybe 1GB wasn't
enough, so I put in a second stick. This time, instead of spewing
21 matches
Mail list logo
