From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Joshua Immanuel <josh@hipro.co.in>
Cc: Yocto Project <yocto@yoctoproject.org>,
Darren Hart <dvhart@linux.intel.com>
Subject: Re: missing kernel in rootfs image
Date: Fri, 24 Feb 2012 09:45:07 -0500 [thread overview]
Message-ID: <4F47A273.5030701@windriver.com> (raw)
In-Reply-To: <1330072145.3803.25.camel@babel.joshhome>
On 12-02-24 03:29 AM, Joshua Immanuel wrote:
> On Tue, 2012-02-21 at 15:10 +0530, Joshua Immanuel wrote:
>> While trying to generate my custom rootfs image, I added the
>> linux_yocto_3.0.bbappend file to my custom layer and specified the
>> KMACHINE, SRCREV and COMPATIBLE_MACHINE variables. I find the
>> generated
>> kernel image (bzImage-ekino.bin) in the tmp/deploy/images directory.
>>
>> But, the rootfs image does not contain the kernel (in /boot
>> directory).
>> My machine configuration file has the following kernel specific lines
>>
>> PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
>> PREFERRED_VERSION_linux-yocto ?= "3.0%"
>
> Can someone explain the work flow behind the process of installing the
> kernel into the rootfs image? My custom image has the IMAGE_INSTALL for
> "task-core-boot". In turn, the task-core-boot recipe DEPENDS on
> "virtual/kernel" this ensures that the kernel is staged.
>
> But, I am not sure which recipe/class is responsible for installing the
> kernel in the final rootfs image. Should I explicitly add the
> "linux-yocto" to RDEPENDS?
Are you past this issue yet ? I'm not sure, since you did have some
other email that looked to be past this .. or maybe they weren't.
Darren went through the process of documenting these variables and
was looking into some related issues. Darren: is this something that
you ran into ?
Cheers,
Bruce
>
> Please guide me.
>
> Regards
> Joshua
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2012-02-24 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 9:40 missing kernel in rootfs image Joshua Immanuel
2012-02-24 8:29 ` Joshua Immanuel
2012-02-24 14:45 ` Bruce Ashfield [this message]
2012-02-24 15:43 ` Darren Hart
2012-02-24 15:48 ` Joshua Immanuel
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=4F47A273.5030701@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=josh@hipro.co.in \
--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.