From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>,
"QEMU Trivial" <qemu-trivial@nongnu.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Max Reitz" <mreitz@redhat.com>
Subject: Re: [PATCH v3] hw/block/nand: Decommission the NAND museum
Date: Tue, 15 Dec 2020 16:53:13 +0100 [thread overview]
Message-ID: <20201215155313.GH8185@merkur.fritz.box> (raw)
In-Reply-To: <CAFEAcA8eB=EC2=_BJYrg3kPWi9U7tqrgg2M0UiOjKcyzgJN10A@mail.gmail.com>
Am 14.12.2020 um 11:02 hat Peter Maydell geschrieben:
> On Mon, 14 Dec 2020 at 00:26, Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
> >
> > This is the QEMU equivalent of this Linux commit (but 7 years later):
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f7025a43a9da2
> >
> > The MTD subsystem has its own small museum of ancient NANDs
> > in a form of the CONFIG_MTD_NAND_MUSEUM_IDS configuration option.
> > The museum contains stone age NANDs with 256 bytes pages, as well
> > as iron age NANDs with 512 bytes per page and up to 8MiB page size.
> >
> > It is with great sorrow that I inform you that the museum is being
> > decommissioned. The MTD subsystem is out of budget for Kconfig
> > options and already has too many of them, and there is a general
> > kernel trend to simplify the configuration menu.
> >
> > We remove the stone age exhibits along with closing the museum,
> > but some of the iron age ones are transferred to the regular NAND
> > depot. Namely, only those which have unique device IDs are
> > transferred, and the ones which have conflicting device IDs are
> > removed.
> >
> > The machine using this device are:
> > - axis-dev88
> > - tosa (via tc6393xb_init)
> > - spitz based (akita, borzoi, terrier)
> >
> > Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> > Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> > ---
> > v3: Do not manually convert tabs to space to avoid mistakes...
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2020-12-15 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 0:26 [PATCH v3] hw/block/nand: Decommission the NAND museum Philippe Mathieu-Daudé
2020-12-14 10:02 ` Peter Maydell
2020-12-15 15:53 ` Kevin Wolf [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=20201215155313.GH8185@merkur.fritz.box \
--to=kwolf@redhat.com \
--cc=f4bug@amsat.org \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).