All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: This one can't be me...
Date: Fri, 05 Apr 2013 18:34:31 -0500	[thread overview]
Message-ID: <1365204871.17697.6.camel@empanada> (raw)
In-Reply-To: <83730A512373431B95CA2E526DB84A99@PAULD>

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>
> +bf5ee4945ee6d748e6abe16356f2357f76b5e2f0_1+1e79e03d115ed17788
> 2ab53909a4f3555e434833-r4.1/linux-cedartrail-nopvr-standard-build$ grep >
> BLK_DEV_RAM .config
> > CONFIG_BLK_DEV_RAM=y
> > CONFIG_BLK_DEV_RAM_COUNT=16
> > CONFIG_BLK_DEV_RAM_SIZE=4096
> > 
> > I don't understand how these are missing in your build?  
> > BLK_DEV_RAM are enabled for Cedartrail-nopvr build.
> > 
> > What did you do different?
> 
> I don't know. I detailed the steps I took. I still have
> 
> 	# CONFIG_BLK_DEV_RAM is not set
> 
> Does the order of the layers in bblayers.conf matter? Is it possible that
> something in the past fetched a different version of something, and it's
> sitting in my downloads tree and screwing things up?
> 
> I'm sending you the two build log files separately, so that they don't go
> out to the entire list.
> 

Can you send those to me as well, along with your entire bblayers.conf
and local.conf?

Thanks,

Tom




  parent reply	other threads:[~2013-04-05 23:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 21:27 This one can't be me Paul D. DeRocco
2013-04-02 23:57 ` Paul D. DeRocco
2013-04-03 16:04   ` Marc Ferland
2013-04-03 15:38 ` Darren Hart
2013-04-03 17:47   ` Bodke, Kishore K
2013-04-03 19:57   ` Paul D. DeRocco
2013-04-03 20:24     ` Darren Hart
2013-04-03 20:50       ` Paul D. DeRocco
2013-04-03 22:01         ` Bodke, Kishore K
2013-04-04  0:32           ` Paul D. DeRocco
2013-04-04 17:17             ` Darren Hart
2013-04-03 22:09         ` Darren Hart
2013-04-04  0:21       ` Paul D. DeRocco
2013-04-04 17:18         ` Darren Hart
2013-04-04 18:31           ` Bodke, Kishore K
2013-04-04 19:14             ` Bodke, Kishore K
2013-06-20 14:58               ` Darren Hart
     [not found]             ` <13F417252F8B4CB5BB755BB07928D20C@PAULD>
     [not found]               ` <D956029D25CF204F948EA0FB515E1EE258405AC4@ORSMSX105.amr.corp.intel.com>
     [not found]                 ` <2FD1BA69DE1E491C839CA26A7D2CA32A@PAULD>
     [not found]                   ` <D956029D25CF204F948EA0FB515E1EE258405C96@ORSMSX105.amr.corp.intel.com>
2013-04-05 17:06                     ` Paul D. DeRocco
2013-04-05 18:15                       ` Bodke, Kishore K
2013-04-05 18:48                         ` Paul D. DeRocco
2013-04-05 22:32                           ` Bodke, Kishore K
2013-04-05 22:45                             ` Paul D. DeRocco
2013-04-05 23:17                               ` Sean Liming
2013-04-05 23:54                                 ` Paul D. DeRocco
2013-04-05 23:34                           ` Tom Zanussi [this message]
2013-04-06  4:03                             ` Tom Zanussi
2013-04-06  4:15                               ` Paul D. DeRocco
2013-04-06  4:48                                 ` Tom Zanussi
2013-04-06  5:55                                   ` Bruce Ashfield
2013-04-06 14:00                                   ` Tom Zanussi
2013-04-06 18:20                                     ` Paul D. DeRocco
2013-04-06 19:20                                       ` Tom Zanussi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1365204871.17697.6.camel@empanada \
    --to=tom.zanussi@intel.com \
    --cc=pderocco@ix.netcom.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.