All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Darren Hart <dvhart@linux.intel.com>
Subject: Re: Updated Yocto Hands-on Kernel Lab available
Date: Mon, 18 Feb 2013 23:31:02 -0600	[thread overview]
Message-ID: <1361251862.1868.3.camel@empanada> (raw)
In-Reply-To: <CAHUNapT64nNKXw5Hb0NFMn2BOxV60qTZZLszgFgDD20-RpiTNw@mail.gmail.com>

On Mon, 2013-02-18 at 18:50 -0500, Trevor Woerner wrote:
> I can't figure out what I'm doing wrong, but I can't get lab3 to work.
> 
> Following the instructions in the pdf I first tried doing lab3
> incrementally (build/test, build/test, build/test) and it didn't work.
> Then I tried deleting (tmp, sstate, etc), trying again, and it still
> didn't work.
> 
> Build Configuration:
> BB_VERSION        = "1.16.0"
> TARGET_ARCH       = "i586"
> TARGET_OS         = "linux"
> MACHINE           = "lab3-qemux86"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.3"
> TUNE_FEATURES     = "m32 i586"
> TARGET_FPU        = ""
> meta
> meta-yocto
> meta-yocto-bsp
> meta-lab3-qemux86 = "danny:45f95b5f3381097672dd43077f267aa716a02b4c"
> 
> I then copied the meta-lab3-qemux86 layer to where I was working with
> the master branch of poky (hmm... I guess I could have just edited
> bblayers.conf without needing the hassle of the copy), retried the
> exercise, and it worked.
> 
> Build Configuration:
> BB_VERSION        = "1.17.1"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "SUSE-LINUX-12.2"
> TARGET_SYS        = "i586-poky-linux"
> MACHINE           = "lab3-qemux86"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.3+snapshot-20130218"
> TUNE_FEATURES     = "m32 i586"
> TARGET_FPU        = ""
> meta
> meta-yocto
> meta-yocto-bsp
> meta-lab3-qemux86 = "master:c7b23ab68aafc04d9830ef318015912e5d4f0672"
> 
> Note that the above information is a bit misleading.
> "meta-lab3-qemux86" is just a plain directory without any .git so
> there is no "master" or "danny" of "meta-lab3-qemux86". The "master"
> and "danny" branches are of the enclosing poky repository.
> 
> In the case where it doesn't work, the module is built and included in
> the image, but it isn't loaded automatically during boot. Working off
> master, the module is loaded during boot automatically.

So when you say it doesn't work, you mean the module autoload didn't
work, but everything else did?  Did you do the 'bump the PR' step after
you uncommmented the module autoload statement?

If that's not it, then I don't know what you say - I tested it with
danny and it worked fine for me.  I can try running through it again to
verify again, but it really should work...

Tom




  reply	other threads:[~2013-02-19  5:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16  2:29 Updated Yocto Hands-on Kernel Lab available Tom Zanussi
2013-02-16  2:54 ` Stewart, David C
     [not found] ` <CAHUNapRsL+R2+inZztqdTBfVM9EZNtgTWayjLWXE_6tQnd+6Mw@mail.gmail.com>
2013-02-18  2:16   ` Trevor Woerner
2013-02-18  6:28     ` Tom Zanussi
2013-02-18 23:50 ` Trevor Woerner
2013-02-19  5:31   ` Tom Zanussi [this message]
2013-02-19 10:31     ` Trevor Woerner
2013-02-19 17:45       ` Tom Zanussi
2013-02-20  3:34         ` Trevor Woerner
2013-02-20 18:48           ` 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=1361251862.1868.3.camel@empanada \
    --to=tom.zanussi@intel.com \
    --cc=dvhart@linux.intel.com \
    --cc=twoerner@gmail.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.