All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Christoph Hellwig <hch@infradead.org>
Cc: Daniel Golle <daniel@makrotopia.org>,
	Jens Axboe <axboe@kernel.dk>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Matthew Wilcox <willy@infradead.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Michal Orzel <michalorzel.eng@gmail.com>,
	linux-block <linux-block@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v5 3/4] partitions/efi: add support for uImage.FIT sub-partitions
Date: Thu, 17 Nov 2022 07:50:08 +0100 (CET)	[thread overview]
Message-ID: <271114315.250800.1668667808308.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <Y3XN+fDTjHz09qEE@infradead.org>

----- Ursprüngliche Mail -----
> Von: "Christoph Hellwig" <hch@infradead.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

WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Christoph Hellwig <hch@infradead.org>
Cc: Daniel Golle <daniel@makrotopia.org>,
	Jens Axboe <axboe@kernel.dk>,
	 Miquel Raynal <miquel.raynal@bootlin.com>,
	 Vignesh Raghavendra <vigneshr@ti.com>,
	 Matthew Wilcox <willy@infradead.org>,
	 "Martin K. Petersen" <martin.petersen@oracle.com>,
	 Chaitanya Kulkarni <kch@nvidia.com>,
	 Michal Orzel <michalorzel.eng@gmail.com>,
	 linux-block <linux-block@vger.kernel.org>,
	 linux-kernel <linux-kernel@vger.kernel.org>,
	 linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v5 3/4] partitions/efi: add support for uImage.FIT sub-partitions
Date: Thu, 17 Nov 2022 07:50:08 +0100 (CET)	[thread overview]
Message-ID: <271114315.250800.1668667808308.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <Y3XN+fDTjHz09qEE@infradead.org>

----- Ursprüngliche Mail -----
> Von: "Christoph Hellwig" <hch@infradead.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

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2022-11-17  6:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 21:45 [PATCH v5 0/4] partition parser for U-Boot's uImage.FIT Daniel Golle
2022-11-15 21:45 ` Daniel Golle
2022-11-15 21:45 ` [PATCH v5 1/4] block: add new flag to add partitions read-only Daniel Golle
2022-11-15 21:45   ` Daniel Golle
2022-11-15 21:46 ` [PATCH v5 2/4] block: add partition parser for U-Boot uImage.FIT Daniel Golle
2022-11-15 21:46   ` Daniel Golle
2022-11-15 21:47 ` [PATCH v5 3/4] partitions/efi: add support for uImage.FIT sub-partitions Daniel Golle
2022-11-15 21:47   ` Daniel Golle
2022-11-16  6:01   ` Christoph Hellwig
2022-11-16  6:01     ` Christoph Hellwig
2022-11-17  0:19     ` Daniel Golle
2022-11-17  0:19       ` Daniel Golle
2022-11-17  6:00       ` Christoph Hellwig
2022-11-17  6:00         ` Christoph Hellwig
2022-11-17  6:50         ` Richard Weinberger [this message]
2022-11-17  6:50           ` Richard Weinberger
2022-11-17  6:59           ` Christoph Hellwig
2022-11-17  6:59             ` Christoph Hellwig
2022-11-17 13:59         ` Daniel Golle
2022-11-17 13:59           ` Daniel Golle
2022-11-15 21:47 ` [PATCH v5 4/4] mtd: add option to enable scanning for partitions Daniel Golle
2022-11-15 21:47   ` Daniel Golle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=271114315.250800.1668667808308.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=axboe@kernel.dk \
    --cc=daniel@makrotopia.org \
    --cc=hch@infradead.org \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=martin.petersen@oracle.com \
    --cc=michalorzel.eng@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=vigneshr@ti.com \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.