From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: liao jaime <jaimeliao.tw@gmail.com>, Michael Walle <michael@walle.cc>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
jaimeliao@mxic.com.tw, pratyush@kernel.org, richard@nod.at,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: stop printing superfluous debug info
Date: Tue, 28 Nov 2023 09:47:22 +0000 [thread overview]
Message-ID: <756aa94a-3237-4689-885a-1e17504e72b6@linaro.org> (raw)
In-Reply-To: <d7bb4580-00b9-4206-bbfc-bd203c21a877@linaro.org>
On 11/28/23 09:39, Tudor Ambarus wrote:
>
> cut
>
>>>> Maybe we don't need this at all, as long as one message remains about
>>>> the JEDEC ID, but keep in mind that spi-nors are commonly storing the
>>>> rootfs and if your spi-nor does not boot you don't have a userspace yet
>>>> and all the debugfs entries are purely useless.
>>>
>>> Good point.
>>>
>>> Just curious, do you know any boards which has the rootfs writable on
>>> the spi-nor flash?
>> I am also interested.
>>
>
> Having the rootfs stored on SPI NOR is a poor design decision as you're
> better of with a NAND, which is cheaper and faster on writes. I tried in
> the past a ubifs on top of a large (64 and 128MB) SPI NOR flash. But
> they were plug-able flashes, not something that is always tied to the
> board. Microchip's sama7g5ek comes with a 128MB macronix SPI NOR flash
> populated. But there are other vendors that provide large SPI NORs if
> really needed.
>
pressed sent too soon :). What I wanted to say is that it's not uncommon
for vendors to populate large SPI NOR flashes, there are others as well,
thus Miquel's concerns are valid. There may be people out there having
rootfs on top of SPI NORs.
Cheers,
ta
next prev parent reply other threads:[~2023-11-28 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 16:59 Tudor Ambarus
2023-11-27 17:15 ` Miquel Raynal
2023-11-28 8:14 ` Tudor Ambarus
2023-11-28 8:47 ` Michael Walle
2023-11-28 9:03 ` Miquel Raynal
2023-11-28 9:10 ` Michael Walle
2023-11-28 9:24 ` liao jaime
2023-11-28 9:39 ` Tudor Ambarus
2023-11-28 9:47 ` Tudor Ambarus [this message]
2023-11-28 11:04 ` Miquel Raynal
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=756aa94a-3237-4689-885a-1e17504e72b6@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=jaimeliao.tw@gmail.com \
--cc=jaimeliao@mxic.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®