On 9/24/19 3:23 AM, Bedel, Alban wrote:
On Tue, 2019-09-03 at 09:41 +0000, Bedel, Alban wrote:
On Wed, 2019-07-31 at 13:53 +0000, Bedel, Alban wrote:
AArch64 images are not self-decompressing, thus usually much
larger.
Boot times can be reduced by compressing them in FIT and uImages.
This commit is a backport of commit a725d188b5 (kernel-uboot:
compress
arm64 kernels) and commit 60bc7e180e (kernel-uboot: remove useless
special casing of arm64 Image) from master. Both commit were melted
into one to avoid some useless churn.
Was this patch overlooked, or is there a reason it is not considered
in
the next round of update for warrior? Without this patch kernel
images
are too large to fit in the flash of the system I'm using.
Furthermore
it is not trivial to fix this in my own layer.
Please, I really like to get an answer here. I'm fine if there is a
reason why this patch is not considered for warrior, but just getting
ignored is very frustrating.
Add Armin, who maintains warrior.
It seems like he just missed the thread.
There was a 50 patch update posted for warrior last night
but I don't see this patch mentioned.
../Randy
Alban
--
# Randy MacLeod
# Wind River Linux
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
