All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: FW: YP Linux Kernel Development Manual
Date: Tue, 22 Jan 2013 11:11:46 -0800	[thread overview]
Message-ID: <50FEE472.5050102@intel.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237957D27592@ORSMSX101.amr.corp.intel.com>

On 01/21/2013 06:05 PM, Rifenbark, Scott M wrote:
> Hi,
> 
> I am reposting this to the discussion list and copying Darren Hart.
> 
> Scott
> 
> From: Eddy Lai GMail [mailto:eddy.lai.tw@gmail.com]
> Sent: Monday, January 21, 2013 3:36 PM
> To: Rifenbark, Scott M
> Subject: Re: [yocto] YP Linux Kernel Development Manual
> 
> hi
> 
> hi, I follow the kernel development manual "2.5. Incorporating Out-of-Tree Modules",
> copy the "hello-mod_0.1.bb" and "files" folder into my taget layer "meta-intel/meta-jasperforest/recipe-kernel", then add "MACHINE_EXTRA_ RDEPENDS += "kernel-module-hello" in the conf/local.conf
> after build and boot, there's no "hello.ko" found in the binary image
> also there's no hello.ko in the "tmp/work/..." folder

From the description below that would be because you have to place the
entire hello-mod directory into
meta-intel/meta-jasperforest/recipes-kernel in order for the stock
layer.conf BBFILES variables to include in the bitbake search path.

If you do indeed have have a space in "MACHINE_EXTRA_ RDEPENDS" as in
your message below, that will also lead to failure.

Thanks,

--
Darren

> 
> Eddy
> 
> All,
> 
> 
> 
> There is a new YP manual under development.  It is a development manual for Linux kernels in the YP.  Darren Hart is the original author of the manual as you probably know.  It is still being worked on but it is in HTML form and now part of the yocto-docs/master branch.  It is published at http://www.yoctoproject.org/docs/1.4/kernel-dev/kernel-dev.html.  Feel free to access it and comment.
> 
> 
> 
> Thanks,
> 
> Scott
> 
> 
> 
> Scott Rifenbark
> 
> Intel Corporation
> 
> Yocto Project Documentation
> 
> 503.712.2702
> 
> 503.341.0418 (cell)
> 
> 
> 
> 
> 
> _______________________________________________
> 
> yocto mailing list
> 
> yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
> 
> https://lists.yoctoproject.org/listinfo/yocto
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


      parent reply	other threads:[~2013-01-22 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22  2:05 FW: YP Linux Kernel Development Manual Rifenbark, Scott M
2013-01-22  8:59 ` Christian Ege
2013-01-22 19:14   ` Darren Hart
2013-01-22 21:26     ` Christian Ege
2013-01-22 19:11 ` Darren Hart [this message]

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=50FEE472.5050102@intel.com \
    --to=darren.hart@intel.com \
    --cc=scott.m.rifenbark@intel.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.