Hey Marcel,
> On Sat, 2022-02-19 at 00:38 +, Ziswiler, Marcel wrote:
> I am not sure whether I fully understand the issue(s) you are having.
Same here ;-) I did some more work on this, best described as copying a lot of
commands from my notepad back and forth. I think you confirmed my und
Hi Olli
On Fri, 2022-02-11 at 08:13 +, Westermann, Oliver wrote:
[snip]
> My current setup uses bootm ${loadaddr}#${fit_config} which works fine,
> fit_config containing a configuration
> node name. When calling bootm ${loadaddr}#${fit_config}#bar to apply the bar
> overlay to ${fit_config
Hey,
On Fri, 11 Feb 2022 at 08:54, Heinrich Schuchardt wrote:
> You can pass the name of a configuration and overlays to apply to the
> bootm command. See doc/uImage.FIT/overlay-fdt-boot.txt
>
> Here are examples of usage:
>
> * configs/am65x_hs_evm_a53_defconfig
> * include/configs/ti_armv7_co
On 2/11/22 08:19, Westermann, Oliver wrote:
On Tue, 1 Feb 2022 at 10:50, Oliver Westermann wrote:
Hey,
Is my doubt reasonable or am I missing a step somewhere?
You can pass the name of a configuration and overlays to apply to the
bootm command. See doc/uImage.FIT/overlay-fdt-boot.txt
Here
On Tue, 1 Feb 2022 at 10:50, Oliver Westermann wrote:
> Hey,
>
> Is my doubt reasonable or am I missing a step somewhere?
> I can provide more info (detailed load & boot steps, fit image iminfo) if
> needed.
>
> - Olli
>
Hey,
I'm not sure if this is the correct list or my initial informatio
Hey,
We're supporting a device that has some hardware variants. As those variants
can be of A different kinds on B different interfaces, we end up with A*B = N
different hardware variations.
Currently we have N device trees in the FIT image, but we noticed that it
doesn't scale anymore: Any new
6 matches
Mail list logo