From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: "Jagan Teki" <jagan@amarulasolutions.com>,
"Marek Behún" <marek.behun@nic.cz>,
U-Boot-Denx <u-boot@lists.denx.de>
Subject: Re: Proposal: U-Boot MTD (rewriting old story)
Date: Wed, 4 Aug 2021 14:49:05 -0400 [thread overview]
Message-ID: <20210804184905.GD9379@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ0P6pG1z-HHnQbyMt3JKq7_GFHLocWr8iptsWRomWx5jQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]
On Wed, Aug 04, 2021 at 10:09:55AM -0600, Simon Glass wrote:
> Hi Jagan,
>
> On Tue, 3 Aug 2021 at 09:01, Jagan Teki <jagan@amarulasolutions.com> wrote:
> >
> > Yes, this is the old discussion and triggered again now since we had a
> > discussion on the last U-Boot contributor call.
> >
> > I will brief the main points here, as most of the details are
> > mentioned in previous threads.
> >
> > Here are the couple of old and new implementations on the SPI-NOR side.
> >
> > http://u-boot.10912.n7.nabble.com/PATCH-v10-00-27-dm-Generic-MTD-Subsystem-with-SPI-NOR-interface-tt315694.html#none
> > http://u-boot.10912.n7.nabble.com/PATCH-0-5-mtd-Implement-MTD-UCLASS-use-SPINOR-td419538.html#a419541
> > https://patchwork.ozlabs.org/project/uboot/cover/20200709111709.68904-1-jagan@amarulasolutions.com/
> >
> > Idea is to
> > 1. Create MTD_UCLASS, already present
> > 2. Create DM MTD Operations, above patchset does.
> > 3. Create Flash specific MTD UClass's like
> > UCLASS_NAND
> > UCLASS_SPI_NAND
> > UCLASS_SPI_NOR
> > UCLASS_NOR
> > UCLASS_UBI
> > and register to UCLASS_MTD as interface slaves like how MMC, SCSI are
> > registered to UCLASS_BLK
> > 4. Sync only respective flash specific code, and drop __UBOOT__
> > 5. Interface mtd, sf, and nand commands to UCLASS_MTD.
>
> This all seems good to me.
>
> >
> > Hard points:
> > 1. Hard to arrange Linux specific code and drop unneeded _UBOOT_ code,
> > but possible.
> > 2. Requires a lot of testing.
>
> Let's add simple emulators for NAND, SPI_NAND and UBI. We already have
> one for SPI_NOR I believe. That will be a good long-term investment.
What are our viable options here via QEMU?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-08-04 18:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 15:00 Proposal: U-Boot MTD (rewriting old story) Jagan Teki
2021-08-04 16:09 ` Simon Glass
2021-08-04 18:49 ` Tom Rini [this message]
2021-08-05 19:20 ` Simon Glass
2021-08-05 19:39 ` Tom Rini
2021-08-06 1:07 ` Bin Meng
2021-08-12 21:46 ` Simon Glass
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=20210804184905.GD9379@bill-the-cat \
--to=trini@konsulko.com \
--cc=jagan@amarulasolutions.com \
--cc=marek.behun@nic.cz \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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