Openembedded Devel Discussions
 help / color / mirror / Atom feed
* generate a named kernel in ${DEPLOY_DIR_IMAGE}
@ 2010-09-28 16:54 Frans Meulenbroeks
  2010-09-28 17:20 ` Denys Dmytriyenko
  2010-09-28 23:23 ` Andrea Adami
  0 siblings, 2 replies; 11+ messages in thread
From: Frans Meulenbroeks @ 2010-09-28 16:54 UTC (permalink / raw)
  To: openembedded-devel

Hi,

As I needed to generate two different kernels for the same machine I
had some kind of problem (as emailed yesterday).
For now I've solved it as follows:

I created a 2nd recipe (in an overlay):
linux-small_2.6.34.bb
this one essentially only requires linux_2.6.34.bb and sets S to the linux_${PN}
Then I can just add a dir linux-small and add the small defconfig in it.

That way bitbake linux-small should give me the 2nd kernel.
And actually it builds the kernel but this one is also packaged in a
kernel-*.ipk.
I could have made two different machines, but that seemed somewhat
overkill, so in the end I decided to modify do_install_append in
linux.inc.

This function currently reads:

do_install_append() {
	oe_runmake headers_install
INSTALL_HDR_PATH=${D}${exec_prefix}/src/linux-${KERNEL_VERSION}
ARCH=$ARCH
}

And I just added a line:
    cp ${D}/boot/uImage ${DEPLOY_DIR_IMAGE}/uImage-${PN}

That way both kernels end up with different names in the deploy dir.
In the image recipe I can then just copy them in a post process
command to the proper location.
(btw that is also why I went for uImage-${PN} and not for
uImage-${PN}-${KERNEL_VERSION}, the kernel version is not known in the
image recipe so it is much harder to copy the right/latest uImage to
the kernel.

Rationale for typing this message is threefold:
- first of all I wanted to record and share what I have done, so
others can use it
- secondly I would appreciate feedback on my solutions (and maybe
someone sees a way to improve it)
- and lastly I would like to inquire if people feel the above line
would be a nice addition to the stock linux.inc. If so I'l happily
prepare a patch.

Your feedback is appreciated.

Frans



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-28 16:54 generate a named kernel in ${DEPLOY_DIR_IMAGE} Frans Meulenbroeks
@ 2010-09-28 17:20 ` Denys Dmytriyenko
  2010-09-28 17:59   ` Frans Meulenbroeks
  2010-09-28 23:23 ` Andrea Adami
  1 sibling, 1 reply; 11+ messages in thread
From: Denys Dmytriyenko @ 2010-09-28 17:20 UTC (permalink / raw)
  To: openembedded-devel

On Tue, Sep 28, 2010 at 06:54:38PM +0200, Frans Meulenbroeks wrote:
> Hi,
> 
> As I needed to generate two different kernels for the same machine I
> had some kind of problem (as emailed yesterday).
> For now I've solved it as follows:
> 
> I created a 2nd recipe (in an overlay):
> linux-small_2.6.34.bb
> this one essentially only requires linux_2.6.34.bb and sets S to the linux_${PN}
> Then I can just add a dir linux-small and add the small defconfig in it.
> 
> That way bitbake linux-small should give me the 2nd kernel.
> And actually it builds the kernel but this one is also packaged in a
> kernel-*.ipk.
> I could have made two different machines, but that seemed somewhat
> overkill, so in the end I decided to modify do_install_append in
> linux.inc.
> 
> This function currently reads:
> 
> do_install_append() {
> 	oe_runmake headers_install
> INSTALL_HDR_PATH=${D}${exec_prefix}/src/linux-${KERNEL_VERSION}
> ARCH=$ARCH
> }
> 
> And I just added a line:
>     cp ${D}/boot/uImage ${DEPLOY_DIR_IMAGE}/uImage-${PN}
> 
> That way both kernels end up with different names in the deploy dir.
> In the image recipe I can then just copy them in a post process
> command to the proper location.
> (btw that is also why I went for uImage-${PN} and not for
> uImage-${PN}-${KERNEL_VERSION}, the kernel version is not known in the
> image recipe so it is much harder to copy the right/latest uImage to
> the kernel.
> 
> Rationale for typing this message is threefold:
> - first of all I wanted to record and share what I have done, so
> others can use it
> - secondly I would appreciate feedback on my solutions (and maybe
> someone sees a way to improve it)
> - and lastly I would like to inquire if people feel the above line
> would be a nice addition to the stock linux.inc. If so I'l happily
> prepare a patch.

Frans,

May I suggest you to look at the existing multi-kernel.inc implementation[1] 
for building multiple versions of the same kernel with slightly different 
defconfigs and slightly different resulting names in the deploy. I use it in 
Arago[2][3] for linux-davinci machines, while Koen uses it in OE with 
linux-omap-psp for beagleboard[4][5]...

[1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/multi-kernel.inc
[2] http://arago-project.org/git/?p=arago.git;a=blob;f=recipes/linux/linux-davinci-staging_git.bb;hb=HEAD
[3] http://arago-project.org/git/?p=arago.git;a=tree;f=recipes/linux/linux-davinci-staging/dm355-evm;hb=HEAD
[4] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap-psp_2.6.32.bb
[5] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap-psp-2.6.32/beagleboard

-- 
Denys



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-28 17:20 ` Denys Dmytriyenko
@ 2010-09-28 17:59   ` Frans Meulenbroeks
  0 siblings, 0 replies; 11+ messages in thread
From: Frans Meulenbroeks @ 2010-09-28 17:59 UTC (permalink / raw)
  To: openembedded-devel

2010/9/28 Denys Dmytriyenko <denis@denix.org>:

>
> Frans,
>
> May I suggest you to look at the existing multi-kernel.inc implementation[1]
> for building multiple versions of the same kernel with slightly different
> defconfigs and slightly different resulting names in the deploy. I use it in
> Arago[2][3] for linux-davinci machines, while Koen uses it in OE with
> linux-omap-psp for beagleboard[4][5]...
>
> [1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/multi-kernel.inc
> [2] http://arago-project.org/git/?p=arago.git;a=blob;f=recipes/linux/linux-davinci-staging_git.bb;hb=HEAD
> [3] http://arago-project.org/git/?p=arago.git;a=tree;f=recipes/linux/linux-davinci-staging/dm355-evm;hb=HEAD
> [4] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap-psp_2.6.32.bb
> [5] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap-psp-2.6.32/beagleboard
>
> --
> Denys
>
Denys, thanks for the pointers.
I did peek into multi-kernel (although I didn't test it).
Apparently I missed the fact that it copies the generated images to
the deploy dir, but your message triggered me to reread the file and I
now found that it *does* copy to deploy.
I'll give multikernel a try tomorrow or so.

Thanks again, Frans.

PS: what caused the misinterpretation at my side was the comment in
the beginning that said:
# Note that this include will NOT stage anything nor create packages
Guess I interpreted this as does not put anything in deploy and did
not search for evidence.
Maybe the comment could be made slightly more explicit that the image
*is* put in deploy.



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-28 16:54 generate a named kernel in ${DEPLOY_DIR_IMAGE} Frans Meulenbroeks
  2010-09-28 17:20 ` Denys Dmytriyenko
@ 2010-09-28 23:23 ` Andrea Adami
  2010-09-29  6:28   ` Frans Meulenbroeks
  2010-09-29  6:54   ` Frans Meulenbroeks
  1 sibling, 2 replies; 11+ messages in thread
From: Andrea Adami @ 2010-09-28 23:23 UTC (permalink / raw)
  To: openembedded-devel

On Tue, Sep 28, 2010 at 6:54 PM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> Hi,
>
> As I needed to generate two different kernels for the same machine I
> had some kind of problem (as emailed yesterday).
> For now I've solved it as follows:
>
> I created a 2nd recipe (in an overlay):
> linux-small_2.6.34.bb
> this one essentially only requires linux_2.6.34.bb and sets S to the linux_${PN}
> Then I can just add a dir linux-small and add the small defconfig in it.
>
> That way bitbake linux-small should give me the 2nd kernel.
> And actually it builds the kernel but this one is also packaged in a
> kernel-*.ipk.
> I could have made two different machines, but that seemed somewhat
> overkill, so in the end I decided to modify do_install_append in
> linux.inc.
>

We solved same issues with linux-kexecboot.inc including linux.inc and
redefining vars/tasks.
In particular
...
PACKAGES = ""
PROVIDES = ""
...
KERNEL_IMAGE_BASE_NAME = "${KERNEL_IMAGETYPE}-kexecboot-${PV}-${PR}-${MACHINE}"
KERNEL_IMAGE_SYMLINK_NAME = "${KERNEL_IMAGETYPE}-kexecboot-${MACHINE}"
...

do_populate_sysroot() {
}

do_install() {
}

python do_package() {
}

So we end having in e.g.
/oe/build/tmp/deploy/glibc/images/c7x0
zImage-2.6.26-r13-c7x0.bin                        1351824│Sep 25 04:37
@zImage-c7x0.bin                                             26│Sep 25 04:38
zImage-kexecboot-2.6.26-r20.0-c7x0.bin      1113112│Sep 25 04:40
@zImage-kexecboot-c7x0.bin                             38│Sep 25 04:40



> This function currently reads:
>
> do_install_append() {
>        oe_runmake headers_install
> INSTALL_HDR_PATH=${D}${exec_prefix}/src/linux-${KERNEL_VERSION}
> ARCH=$ARCH
> }
>
> And I just added a line:
>    cp ${D}/boot/uImage ${DEPLOY_DIR_IMAGE}/uImage-${PN}

I don't think patch is necessari, though you should use
${KERNEL_IMAGETYPE} and not uImage


>
> That way both kernels end up with different names in the deploy dir.
> In the image recipe I can then just copy them in a post process
> command to the proper location.
> (btw that is also why I went for uImage-${PN} and not for
> uImage-${PN}-${KERNEL_VERSION}, the kernel version is not known in the
> image recipe so it is much harder to copy the right/latest uImage to
> the kernel.
>
> Rationale for typing this message is threefold:
> - first of all I wanted to record and share what I have done, so
> others can use it
> - secondly I would appreciate feedback on my solutions (and maybe
> someone sees a way to improve it)
> - and lastly I would like to inquire if people feel the above line
> would be a nice addition to the stock linux.inc. If so I'l happily
> prepare a patch.

Remember that most work is done in kernel.bbclass
Copy of kernel is done in do_deploy()

...
install -m 0644 ${KERNEL_OUTPUT}
${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE_BASE_NAME}.bin
...

>
> Your feedback is appreciated.
>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Regards

Andrea



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-28 23:23 ` Andrea Adami
@ 2010-09-29  6:28   ` Frans Meulenbroeks
  2010-09-29 17:47     ` Denys Dmytriyenko
  2010-09-29  6:54   ` Frans Meulenbroeks
  1 sibling, 1 reply; 11+ messages in thread
From: Frans Meulenbroeks @ 2010-09-29  6:28 UTC (permalink / raw)
  To: openembedded-devel

2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
> On Tue, Sep 28, 2010 at 6:54 PM, Frans Meulenbroeks
> <fransmeulenbroeks@gmail.com> wrote:
>> Hi,
>>
>> As I needed to generate two different kernels for the same machine I
>> had some kind of problem (as emailed yesterday).
>> For now I've solved it as follows:
>>
>> I created a 2nd recipe (in an overlay):
>> linux-small_2.6.34.bb
>> this one essentially only requires linux_2.6.34.bb and sets S to the linux_${PN}
>> Then I can just add a dir linux-small and add the small defconfig in it.
>>
>> That way bitbake linux-small should give me the 2nd kernel.
>> And actually it builds the kernel but this one is also packaged in a
>> kernel-*.ipk.
>> I could have made two different machines, but that seemed somewhat
>> overkill, so in the end I decided to modify do_install_append in
>> linux.inc.
>>
>
> We solved same issues with linux-kexecboot.inc including linux.inc and
> redefining vars/tasks.
> In particular
> ...
> PACKAGES = ""
> PROVIDES = ""
> ...
> KERNEL_IMAGE_BASE_NAME = "${KERNEL_IMAGETYPE}-kexecboot-${PV}-${PR}-${MACHINE}"
> KERNEL_IMAGE_SYMLINK_NAME = "${KERNEL_IMAGETYPE}-kexecboot-${MACHINE}"
> ...
>
> do_populate_sysroot() {
> }
>
> do_install() {
> }
>
> python do_package() {
> }
>
> So we end having in e.g.
> /oe/build/tmp/deploy/glibc/images/c7x0
> zImage-2.6.26-r13-c7x0.bin                        1351824│Sep 25 04:37
> @zImage-c7x0.bin                                             26│Sep 25 04:38
> zImage-kexecboot-2.6.26-r20.0-c7x0.bin      1113112│Sep 25 04:40
> @zImage-kexecboot-c7x0.bin                             38│Sep 25 04:40
>
>
>
>> This function currently reads:
>>
>> do_install_append() {
>>        oe_runmake headers_install
>> INSTALL_HDR_PATH=${D}${exec_prefix}/src/linux-${KERNEL_VERSION}
>> ARCH=$ARCH
>> }
>>
>> And I just added a line:
>>    cp ${D}/boot/uImage ${DEPLOY_DIR_IMAGE}/uImage-${PN}
>
> I don't think patch is necessari, though you should use
> ${KERNEL_IMAGETYPE} and not uImage
>
>

Andrea,

Thanks for the info.
I was unaware of  ${KERNEL_IMAGETYPE}.
That definitely makes things more generic
And indeed the code could go into do_deploy instead of do_install.
Both work, but it is more appropriate in do_deploy than in do_install

Wrt  KERNEL_IMAGE_BASE_NAME and  KERNEL_IMAGE_SYMLINK_NAME: didn't
know about these either. They are not in the OE manual; searching for
it gave me an angstrom doc on it though. Guess the OE manual could use
a list of all vars and their purpose.
With them I can avoid the copy line, so this is a nice improvement.

Frans

PS: referring to Denys' message about multi-linux.inc: still haven't
tested it, but what isslightly nasty about it is that it does not
package, so I cannot easily include modules in an image
(as my kernels are from the same recipe the modules are compatible,
and it helps to be able to say in an image recipe that you want to add
kernel-module-xyz)



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-28 23:23 ` Andrea Adami
  2010-09-29  6:28   ` Frans Meulenbroeks
@ 2010-09-29  6:54   ` Frans Meulenbroeks
  2010-09-29 11:44     ` Andrea Adami
  1 sibling, 1 reply; 11+ messages in thread
From: Frans Meulenbroeks @ 2010-09-29  6:54 UTC (permalink / raw)
  To: openembedded-devel

2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
> On Tue, Sep 28, 2010 at 6:54 PM, Frans Meulenbroeks
> <fransmeulenbroeks@gmail.com> wrote:

> We solved same issues with linux-kexecboot.inc including linux.inc and
> redefining vars/tasks.
> In particular
> ...
> PACKAGES = ""
> PROVIDES = ""
> ...
> KERNEL_IMAGE_BASE_NAME = "${KERNEL_IMAGETYPE}-kexecboot-${PV}-${PR}-${MACHINE}"
> KERNEL_IMAGE_SYMLINK_NAME = "${KERNEL_IMAGETYPE}-kexecboot-${MACHINE}"
> ...
>
> do_populate_sysroot() {
> }
>
> do_install() {
> }
>
> python do_package() {
> }
>

Tried this. works nice.
Two small remarks:

I would have expected you had to add something like:
FILESPATHPKG_append = ":linux-${PV}"
I had to add this to get access to the linux patches.

And this:
S = "${WORKDIR}/linux-${PV}"
might perhaps better end up in the base recipe (in my case linux_2.6.34.bb)
(actually thinking of it the FILESPATHPKG might also be moved into there).

Should I prepare a patch for that ?

Frans.



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-29  6:54   ` Frans Meulenbroeks
@ 2010-09-29 11:44     ` Andrea Adami
  2010-09-29 13:10       ` Frans Meulenbroeks
  0 siblings, 1 reply; 11+ messages in thread
From: Andrea Adami @ 2010-09-29 11:44 UTC (permalink / raw)
  To: openembedded-devel

On Wed, Sep 29, 2010 at 8:54 AM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> 2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
>> On Tue, Sep 28, 2010 at 6:54 PM, Frans Meulenbroeks
>> <fransmeulenbroeks@gmail.com> wrote:
>
>> We solved same issues with linux-kexecboot.inc including linux.inc and
>> redefining vars/tasks.
>> In particular
>> ...
>> PACKAGES = ""
>> PROVIDES = ""
>> ...
>> KERNEL_IMAGE_BASE_NAME = "${KERNEL_IMAGETYPE}-kexecboot-${PV}-${PR}-${MACHINE}"
>> KERNEL_IMAGE_SYMLINK_NAME = "${KERNEL_IMAGETYPE}-kexecboot-${MACHINE}"
>> ...
>>
>> do_populate_sysroot() {
>> }
>>
>> do_install() {
>> }
>>
>> python do_package() {
>> }
>>
>
> Tried this. works nice.
> Two small remarks:
>
> I would have expected you had to add something like:
> FILESPATHPKG_append = ":linux-${PV}"
> I had to add this to get access to the linux patches.

No need to extend FILESPATHPKG being we keep the patches in the
kernel-specific dirs: e.g. /linux-2.6.34 and /linux-kexecboot-2.6.34

>
> And this:
> S = "${WORKDIR}/linux-${PV}"
> might perhaps better end up in the base recipe (in my case linux_2.6.34.bb)

I misunderstand perhaps: this is in each recipe (e.g.
linux-kexecboot_2.6.34.bb). Do you mean moving it in
linux-kexecboot.inc?


> (actually thinking of it the FILESPATHPKG might also be moved into there).
>
> Should I prepare a patch for that ?
Sorry, not sure about the question.

>
> Frans.
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Regards

Andrea

P.S: : I feel sorry for the 400 files of the linux-kexecboot merge.
While I'm working on zaurus in order to remove as many recipes as
possible, I hope the same happens for omap3 and qemu people.
Compatibility for those machines was added long ago and the kernels
became very old.
If I don't see any change I propose to move many linux-kexecboot
recipes to obsolete.



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-29 11:44     ` Andrea Adami
@ 2010-09-29 13:10       ` Frans Meulenbroeks
  2010-09-29 15:18         ` Andrea Adami
  0 siblings, 1 reply; 11+ messages in thread
From: Frans Meulenbroeks @ 2010-09-29 13:10 UTC (permalink / raw)
  To: openembedded-devel

2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
> On Wed, Sep 29, 2010 at 8:54 AM, Frans Meulenbroeks
> <fransmeulenbroeks@gmail.com> wrote:
>> 2010/9/29 Andrea Adami <andrea.adami@gmail.com>:

>> I would have expected you had to add something like:
>> FILESPATHPKG_append = ":linux-${PV}"
>> I had to add this to get access to the linux patches.
>
> No need to extend FILESPATHPKG being we keep the patches in the
> kernel-specific dirs: e.g. /linux-2.6.34 and /linux-kexecboot-2.6.34

Ah ok, I understand. As I am building different versions of the
standard kernel, I am using those patches
I assumed kexecboot also used the same patches as the kernel does.
I expected these would apply to the kexecboot kernel with the same name.

>
>>
>> And this:
>> S = "${WORKDIR}/linux-${PV}"
>> might perhaps better end up in the base recipe (in my case linux_2.6.34.bb)
>
> I misunderstand perhaps: this is in each recipe (e.g.
> linux-kexecboot_2.6.34.bb). Do you mean moving it in
> linux-kexecboot.inc?

No. My recipe is slightly different and does a require linux_${PV} but
as the requiring recipe is named differently ${PN} and hence ${S} is
differently from the required recipe.
I had to define S in my recipe, and I was wondering whether it would
be better to move that line to the base linux_${PN}} recipe
>
>
>> (actually thinking of it the FILESPATHPKG might also be moved into there).
>>
>> Should I prepare a patch for that ?
> Sorry, not sure about the question.
>
The question was whether it would be better to explicitly say
 S = "${WORKDIR}/linux-${PV}"
in linux_${PN}.bb
then S is always automatically ok for everyone who includes it.

not a big change and not very important either.

Frans



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-29 13:10       ` Frans Meulenbroeks
@ 2010-09-29 15:18         ` Andrea Adami
  0 siblings, 0 replies; 11+ messages in thread
From: Andrea Adami @ 2010-09-29 15:18 UTC (permalink / raw)
  To: openembedded-devel

On Wed, Sep 29, 2010 at 3:10 PM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> 2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
>> On Wed, Sep 29, 2010 at 8:54 AM, Frans Meulenbroeks
>> <fransmeulenbroeks@gmail.com> wrote:
>>> 2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
>
>>> I would have expected you had to add something like:
>>> FILESPATHPKG_append = ":linux-${PV}"
>>> I had to add this to get access to the linux patches.
>>
>> No need to extend FILESPATHPKG being we keep the patches in the
>> kernel-specific dirs: e.g. /linux-2.6.34 and /linux-kexecboot-2.6.34
>
> Ah ok, I understand. As I am building different versions of the
> standard kernel, I am using those patches
> I assumed kexecboot also used the same patches as the kernel does.
> I expected these would apply to the kexecboot kernel with the same name.
>
Sure, the patches are the same and FILESPATHPKG could avoid patch
duplication: only defconfig differ.
At first I moved the kernels here, as second step I'll lead the
obsoleted to rest, finally I'll take care of this duplicated patches.

> The question was whether it would be better to explicitly say
>  S = "${WORKDIR}/linux-${PV}"
> in linux_${PN}.bb
> then S is always automatically ok for everyone who includes it.
>
> not a big change and not very important either.
>
> Frans

Well, or having it once in linux.inc. Recipes can override after
'require linux.inc' if needed.
Feel free to propose a patch, thx.

Regards

Andrea

>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-29  6:28   ` Frans Meulenbroeks
@ 2010-09-29 17:47     ` Denys Dmytriyenko
  2010-09-29 19:19       ` Frans Meulenbroeks
  0 siblings, 1 reply; 11+ messages in thread
From: Denys Dmytriyenko @ 2010-09-29 17:47 UTC (permalink / raw)
  To: openembedded-devel

On Wed, Sep 29, 2010 at 08:28:37AM +0200, Frans Meulenbroeks wrote:
> 2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
> > On Tue, Sep 28, 2010 at 6:54 PM, Frans Meulenbroeks
> >> As I needed to generate two different kernels for the same machine I
> >> had some kind of problem (as emailed yesterday).
> >> For now I've solved it as follows:
> >>
> >> I created a 2nd recipe (in an overlay):
> >> linux-small_2.6.34.bb
> >> this one essentially only requires linux_2.6.34.bb and sets S to the linux_${PN}
> >> Then I can just add a dir linux-small and add the small defconfig in it.
> >>
> >> That way bitbake linux-small should give me the 2nd kernel.
> >> And actually it builds the kernel but this one is also packaged in a
> >> kernel-*.ipk.
> >> I could have made two different machines, but that seemed somewhat
> >> overkill, so in the end I decided to modify do_install_append in
> >> linux.inc.
> 
> PS: referring to Denys' message about multi-linux.inc: still haven't
> tested it, but what isslightly nasty about it is that it does not
> package, so I cannot easily include modules in an image
> (as my kernels are from the same recipe the modules are compatible,
> and it helps to be able to say in an image recipe that you want to add
> kernel-module-xyz)

Frans,

It packages only the main kernel and all the related modules, configured by 
the usual defconfig file. But it doesn't do it for the additional kernels that 
were built using configuration files from configs/ directory...

-- 
Denys



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: generate a named kernel in ${DEPLOY_DIR_IMAGE}
  2010-09-29 17:47     ` Denys Dmytriyenko
@ 2010-09-29 19:19       ` Frans Meulenbroeks
  0 siblings, 0 replies; 11+ messages in thread
From: Frans Meulenbroeks @ 2010-09-29 19:19 UTC (permalink / raw)
  To: openembedded-devel

2010/9/29 Denys Dmytriyenko <denis@denix.org>:
> On Wed, Sep 29, 2010 at 08:28:37AM +0200, Frans Meulenbroeks wrote:
>> 2010/9/29 Andrea Adami <andrea.adami@gmail.com>:
>> > On Tue, Sep 28, 2010 at 6:54 PM, Frans Meulenbroeks
>> >> As I needed to generate two different kernels for the same machine I
>> >> had some kind of problem (as emailed yesterday).
>> >> For now I've solved it as follows:
>> >>
>> >> I created a 2nd recipe (in an overlay):
>> >> linux-small_2.6.34.bb
>> >> this one essentially only requires linux_2.6.34.bb and sets S to the linux_${PN}
>> >> Then I can just add a dir linux-small and add the small defconfig in it.
>> >>
>> >> That way bitbake linux-small should give me the 2nd kernel.
>> >> And actually it builds the kernel but this one is also packaged in a
>> >> kernel-*.ipk.
>> >> I could have made two different machines, but that seemed somewhat
>> >> overkill, so in the end I decided to modify do_install_append in
>> >> linux.inc.
>>
>> PS: referring to Denys' message about multi-linux.inc: still haven't
>> tested it, but what isslightly nasty about it is that it does not
>> package, so I cannot easily include modules in an image
>> (as my kernels are from the same recipe the modules are compatible,
>> and it helps to be able to say in an image recipe that you want to add
>> kernel-module-xyz)
>
> Frans,
>
> It packages only the main kernel and all the related modules, configured by
> the usual defconfig file. But it doesn't do it for the additional kernels that
> were built using configuration files from configs/ directory...
>
> --

Ah ok, had to spent too much time on another issue today, but it is
still on my todo list to dive into this.

Frans.



^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2010-09-29 19:19 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-09-28 16:54 generate a named kernel in ${DEPLOY_DIR_IMAGE} Frans Meulenbroeks
2010-09-28 17:20 ` Denys Dmytriyenko
2010-09-28 17:59   ` Frans Meulenbroeks
2010-09-28 23:23 ` Andrea Adami
2010-09-29  6:28   ` Frans Meulenbroeks
2010-09-29 17:47     ` Denys Dmytriyenko
2010-09-29 19:19       ` Frans Meulenbroeks
2010-09-29  6:54   ` Frans Meulenbroeks
2010-09-29 11:44     ` Andrea Adami
2010-09-29 13:10       ` Frans Meulenbroeks
2010-09-29 15:18         ` Andrea Adami

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox