[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <271114315.250800.1668667808308.JavaMail.zimbra@nod.at>
Date: Thu, 17 Nov 2022 07:50:08 +0100 (CET)
From: Richard Weinberger <richard@....at>
To: Christoph Hellwig <hch@...radead.org>
Cc: Daniel Golle <daniel@...rotopia.org>, Jens Axboe <axboe@...nel.dk>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Vignesh Raghavendra <vigneshr@...com>,
Matthew Wilcox <willy@...radead.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Chaitanya Kulkarni <kch@...dia.com>,
Michal Orzel <michalorzel.eng@...il.com>,
linux-block <linux-block@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mtd <linux-mtd@...ts.infradead.org>
Subject: Re: [PATCH v5 3/4] partitions/efi: add support for uImage.FIT
sub-partitions
----- Ursprüngliche Mail -----
> Von: "Christoph Hellwig" <hch@...radead.org>
> On Thu, Nov 17, 2022 at 12:19:10AM +0000, Daniel Golle wrote:
>> While weirdness is certainly subjective, uImage.FIT is not just a
>> random image format but used by a great majority of headless embedded
>> Linux devices out there. It's the default image format of many of the
>> SDKs distributed by chip vendors such as Allwinner, Marvell, MediaTek,
>> NXP, Qualcomm/Atheros, ...
>
> "Look see, my weird format is used by all these companies building
> crappy SOCs, it is not weird.."
Well, FIT is not something strange invented by SoC companies, it comes from u-boot
and is more or less a de-facto standard.
While I agree that using the block layer for partition parsing is questionable
I think supporting these images in Linux is a worthwhile goal.
Thanks,
//richard
Powered by blists - more mailing lists