All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
To: Christian Ege <christian.ege@familie-ege.net>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: FW: YP Linux Kernel Development Manual
Date: Tue, 22 Jan 2013 11:14:14 -0800	[thread overview]
Message-ID: <50FEE506.1020002@intel.com> (raw)
In-Reply-To: <8389da1c972242f1c69900ba7f48db4e-EhVcXlhFQwBWRwoYGgwbZ1dfaANWUkNeXENbAF9TNkFcVEYOV0F1AUtXXl8wQEYHV1JdRVlTWw==-webmailer2@server04.webmailer.hosteurope.de>

On 01/22/2013 12:59 AM, Christian Ege wrote:
>  Hi,
>  I am not sure if this is the problem you are struggling with.
>  I am wondering why class module.bbclass behaves completely different
>  than kernel.bbclacc
> 
>>  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
> 
>  If you hello-mod_0.1.bb inherits module class there is no mechanism
>  to create the kernel-module package. This only applies to the 
>  kernel.bbclass
> 
>  http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/module.bbclass
>  http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/module-base.bbclass
> 
>  Have a look at kernel.bbclass instead shows some pathon code which 
>  handles the module package creation:
>  http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/classes/kernel.bbclass#n301
> 
>  I've fixed this in my layer by stealing the code from kernel.bbclass
>  https://github.com/project-magpie/meta-stlinux/blob/master/recipes-bsp/tdt-driver/tdt-driver.inc
> 
>  With this you can also use the following extends with your module:
>  module_autoload_aotom = "aotom"
>  and
>  module_conf_stmfb = "options stmfb 
>  display0=1280x720-32@50:8m:pal:yuv:yuv"

Christian, this is a really good point I hadn't considered. Would you
care to take a stab at adding this to module.bbclass and sending the
patch to the oe-core list for review? CC'ing myself?

Thanks,

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


  reply	other threads:[~2013-01-22 19:14 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 [this message]
2013-01-22 21:26     ` Christian Ege
2013-01-22 19:11 ` Darren Hart

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=50FEE506.1020002@intel.com \
    --to=darren.hart@intel.com \
    --cc=christian.ege@familie-ege.net \
    --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.