From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mauro Lima <mauro.lima@eclypsium.com>
Cc: linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: mtd: spi-nor: parsers questions
Date: Thu, 15 Jun 2023 09:38:53 +0200 [thread overview]
Message-ID: <20230615093853.4336862d@xps-13> (raw)
In-Reply-To: <CAArk9MNJnu7zbXLYOh8HX5RQZA47Sdfx3GjUo5HfbeXYdY8WJg@mail.gmail.com>
Hi Mauro,
mauro.lima@eclypsium.com wrote on Wed, 14 Jun 2023 18:19:45 -0300:
> Hey all!
> Looking for some help with mtd.
> I'm working on some changes for Intel's spi controller. We have a
> "BIOS" partition, composed of many parts with different offsets and
> could be spread within two chips in some cases (not necessarily of the
> same size).
> Right now the driver uses one partition that, in my system, is bigger
> than the first chip's size, so I'm getting the "size truncated to
> 0x..." log.
> All drivers using mtd_partitions know the partition information at
> compile time. This is not my case, we need to read the first portion
> of the chip to get the partition parts' offsets. So I found parsers,
> and the drivers using parsers make partitions within the chip's size.
> So my question is whether parsers could solve my truncation issue and
> whether parsers support this kind of multiple chip case.
> Thanks!
There is mtdconcat in the kernel but I don't think it will fit your
purpose. FYI I tried a few years ago to bring support for something
like this, unsuccessfully.
Link: https://lore.kernel.org/linux-devicetree/20191127105522.31445-1-miquel.raynal@bootlin.com/
You would need something like that and on top of it a dynamic partition
parser.
Cheers,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2023-06-15 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 21:19 mtd: spi-nor: parsers questions Mauro Lima
2023-06-15 7:38 ` Miquel Raynal [this message]
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=20230615093853.4336862d@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mauro.lima@eclypsium.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox