* is there OE support for building multi-image/component FIT image files?
@ 2017-03-28 22:22 Robert P. J. Day
2017-03-28 22:37 ` Rick Altherr
0 siblings, 1 reply; 6+ messages in thread
From: Robert P. J. Day @ 2017-03-28 22:22 UTC (permalink / raw)
To: OE Core mailing list
not sure i even know if i'm asking the right question, but i already
know that i can build a *basic* FIT image file for (as an example) a
mpc8315e-rdb target, just goofing around. the .its file contains a
node for the kernel, and the dtb file, and the corresponding
configuration node, so everything is fine.
however, let's say i was building for a beaglebone black, for which,
when you build the kernel. you get *multiple* dtb files for numerous
related targets.
is there OE support for defining .its files that contain multiple
kernels, and/or multiple dtb files, that automatically generates
multiple configurations nodes to cover those possibilities?
i realize you can do all that manually with the "mkimage" command,
i'm just not sure how far you can push creating FIT image files with
stock OE support.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: is there OE support for building multi-image/component FIT image files?
2017-03-28 22:22 is there OE support for building multi-image/component FIT image files? Robert P. J. Day
@ 2017-03-28 22:37 ` Rick Altherr
2017-03-29 9:33 ` Robert P. J. Day
2017-03-29 10:52 ` Robert P. J. Day
0 siblings, 2 replies; 6+ messages in thread
From: Rick Altherr @ 2017-03-28 22:37 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: OE Core mailing list
kernel-fitimage.bbclass loops through all the DTBs listed in
KERNEL_DEVICETREE and adds a FIT section for each one. It looks like
only the first one is put into a config section though.
On Tue, Mar 28, 2017 at 3:22 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
> not sure i even know if i'm asking the right question, but i already
> know that i can build a *basic* FIT image file for (as an example) a
> mpc8315e-rdb target, just goofing around. the .its file contains a
> node for the kernel, and the dtb file, and the corresponding
> configuration node, so everything is fine.
>
> however, let's say i was building for a beaglebone black, for which,
> when you build the kernel. you get *multiple* dtb files for numerous
> related targets.
>
> is there OE support for defining .its files that contain multiple
> kernels, and/or multiple dtb files, that automatically generates
> multiple configurations nodes to cover those possibilities?
>
> i realize you can do all that manually with the "mkimage" command,
> i'm just not sure how far you can push creating FIT image files with
> stock OE support.
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: is there OE support for building multi-image/component FIT image files?
2017-03-28 22:37 ` Rick Altherr
@ 2017-03-29 9:33 ` Robert P. J. Day
2017-03-29 15:30 ` Rick Altherr
2017-03-29 10:52 ` Robert P. J. Day
1 sibling, 1 reply; 6+ messages in thread
From: Robert P. J. Day @ 2017-03-29 9:33 UTC (permalink / raw)
To: Rick Altherr; +Cc: OE Core mailing list
On Tue, 28 Mar 2017, Rick Altherr wrote:
> kernel-fitimage.bbclass loops through all the DTBs listed in
> KERNEL_DEVICETREE and adds a FIT section for each one. It looks like
> only the first one is put into a config section though.
maybe i just haven't read far enough, but what value would that
have? as i read it, "bootm" can either boot based on an actual image
reference, or a configuration entry. i don't see how you can select
from among DTBs unless they're referenced in a configuration entry.
can someone clarify this?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: is there OE support for building multi-image/component FIT image files?
2017-03-28 22:37 ` Rick Altherr
2017-03-29 9:33 ` Robert P. J. Day
@ 2017-03-29 10:52 ` Robert P. J. Day
2017-03-29 15:33 ` Rick Altherr
1 sibling, 1 reply; 6+ messages in thread
From: Robert P. J. Day @ 2017-03-29 10:52 UTC (permalink / raw)
To: Rick Altherr; +Cc: OE Core mailing list
On Tue, 28 Mar 2017, Rick Altherr wrote:
> kernel-fitimage.bbclass loops through all the DTBs listed in
> KERNEL_DEVICETREE and adds a FIT section for each one. It looks
> like only the first one is put into a config section though.
that's not what i'm seeing based on a test with YP-provided
beaglebone reference board. that machine config file includes the
line for two dtb files:
KERNEL_DEVICETREE="am335x-bone.dtb am335x-boneblack.dtb"
and the resulting .its file generated contains two configurations --
using the same kernel, and for each dtb file. i just need to read the
code more carefully to verify that it appears to loop through all the
dtb files.
images {
kernel@1 {
description = "Linux kernel";
data = /incbin/("linux.bin");
type = "kernel";
arch = "arm";
os = "linux";
compression = "none";
load = <0x80008000>;
entry = <0x80008000>;
hash@1 {
algo = "sha1";
};
};
fdt@am335x-bone.dtb {
description = "Flattened Device Tree blob";
data = /incbin/("arch/arm/boot/dts/am335x-bone.dtb");
type = "flat_dt";
arch = "arm";
compression = "none";
hash@1 {
algo = "sha1";
};
};
fdt@am335x-boneblack.dtb {
description = "Flattened Device Tree blob";
data = /incbin/("arch/arm/boot/dts/am335x-boneblack.dtb");
type = "flat_dt";
arch = "arm";
compression = "none";
hash@1 {
algo = "sha1";
};
};
};
configurations {
default = "conf@am335x-bone.dtb";
conf@am335x-bone.dtb {
description = "1 Linux kernel, FDT blob";
kernel = "kernel@1";
fdt = "fdt@am335x-bone.dtb";
hash@1 {
algo = "sha1";
};
};
conf@am335x-boneblack.dtb {
description = "0 Linux kernel, FDT blob";
kernel = "kernel@1";
fdt = "fdt@am335x-boneblack.dtb";
hash@1 {
algo = "sha1";
};
};
};
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: is there OE support for building multi-image/component FIT image files?
2017-03-29 9:33 ` Robert P. J. Day
@ 2017-03-29 15:30 ` Rick Altherr
0 siblings, 0 replies; 6+ messages in thread
From: Rick Altherr @ 2017-03-29 15:30 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: OE Core mailing list
On Wed, Mar 29, 2017 at 2:33 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Tue, 28 Mar 2017, Rick Altherr wrote:
>
>> kernel-fitimage.bbclass loops through all the DTBs listed in
>> KERNEL_DEVICETREE and adds a FIT section for each one. It looks like
>> only the first one is put into a config section though.
>
> maybe i just haven't read far enough, but what value would that
> have? as i read it, "bootm" can either boot based on an actual image
> reference, or a configuration entry. i don't see how you can select
> from among DTBs unless they're referenced in a configuration entry.
>
bootm takes 3 arguments: kernel, initrd, fdt. Each of those can
reference a specific image within the FIT using
<fit-address>:<image-name> format.
> can someone clarify this?
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: is there OE support for building multi-image/component FIT image files?
2017-03-29 10:52 ` Robert P. J. Day
@ 2017-03-29 15:33 ` Rick Altherr
0 siblings, 0 replies; 6+ messages in thread
From: Rick Altherr @ 2017-03-29 15:33 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: OE Core mailing list
Looks like this was changed 8 days ago:
http://git.openembedded.org/openembedded-core/commit/meta/classes/kernel-fitimage.bbclass?id=cd2ed7f80b555add07795cc0cbaee866e6c193a3.
I was looking at an old local repo.
On Wed, Mar 29, 2017 at 3:52 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Tue, 28 Mar 2017, Rick Altherr wrote:
>
>> kernel-fitimage.bbclass loops through all the DTBs listed in
>> KERNEL_DEVICETREE and adds a FIT section for each one. It looks
>> like only the first one is put into a config section though.
>
> that's not what i'm seeing based on a test with YP-provided
> beaglebone reference board. that machine config file includes the
> line for two dtb files:
>
> KERNEL_DEVICETREE="am335x-bone.dtb am335x-boneblack.dtb"
>
> and the resulting .its file generated contains two configurations --
> using the same kernel, and for each dtb file. i just need to read the
> code more carefully to verify that it appears to loop through all the
> dtb files.
>
>
> images {
> kernel@1 {
> description = "Linux kernel";
> data = /incbin/("linux.bin");
> type = "kernel";
> arch = "arm";
> os = "linux";
> compression = "none";
> load = <0x80008000>;
> entry = <0x80008000>;
> hash@1 {
> algo = "sha1";
> };
> };
> fdt@am335x-bone.dtb {
> description = "Flattened Device Tree blob";
> data = /incbin/("arch/arm/boot/dts/am335x-bone.dtb");
> type = "flat_dt";
> arch = "arm";
> compression = "none";
> hash@1 {
> algo = "sha1";
> };
> };
> fdt@am335x-boneblack.dtb {
> description = "Flattened Device Tree blob";
> data = /incbin/("arch/arm/boot/dts/am335x-boneblack.dtb");
> type = "flat_dt";
> arch = "arm";
> compression = "none";
> hash@1 {
> algo = "sha1";
> };
> };
> };
>
> configurations {
> default = "conf@am335x-bone.dtb";
> conf@am335x-bone.dtb {
> description = "1 Linux kernel, FDT blob";
> kernel = "kernel@1";
> fdt = "fdt@am335x-bone.dtb";
>
>
> hash@1 {
> algo = "sha1";
> };
> };
>
> conf@am335x-boneblack.dtb {
> description = "0 Linux kernel, FDT blob";
> kernel = "kernel@1";
> fdt = "fdt@am335x-boneblack.dtb";
>
>
> hash@1 {
> algo = "sha1";
> };
> };
> };
>
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-03-29 15:33 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-28 22:22 is there OE support for building multi-image/component FIT image files? Robert P. J. Day
2017-03-28 22:37 ` Rick Altherr
2017-03-29 9:33 ` Robert P. J. Day
2017-03-29 15:30 ` Rick Altherr
2017-03-29 10:52 ` Robert P. J. Day
2017-03-29 15:33 ` Rick Altherr
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.