From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Alexander Shiyan <shc_work@mail.ru>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Re[4]: [PATCH 02/12] mtd: remove museum NAND ID's support
Date: Tue, 05 Mar 2013 11:03:57 +0200 [thread overview]
Message-ID: <1362474237.2943.34.camel@sauron> (raw)
In-Reply-To: <1362473407.874036293@f171.mail.ru>
On Tue, 2013-03-05 at 12:50 +0400, Alexander Shiyan wrote:
> > On Tue, 2013-03-05 at 12:32 +0400, Alexander Shiyan wrote:
> > > > On Mon, 2013-03-04 at 20:59 +0400, Alexander Shiyan wrote:
> > > > > >From: Artem Bityutskiy <artem.bityutskiy at linux.intel.com>
> > > > > >
> > > > > >It is probably OK to remove support for really old NAND chips of 8MiB or
> > > > > >smaller size. We had a separate configuration option for them:
> > > > > >CONFIG_MTD_NAND_MUSEUM_IDS, which we remove along with this patch.
> > > > > >
> > > > > >Signed-off-by: Artem Bityutskiy <artem.bityutskiy at linux.intel.com>
> > > > > >---
> > > > > > drivers/mtd/nand/Kconfig | 8 --------
> > > > > > drivers/mtd/nand/nand_ids.c | 19 -------------------
> > > > > > 2 files changed, 27 deletions(-)
> > > > >
> > > > > Hello.
> > > > > This change break systems with these NAND-chips, for example
> > > > > these IDs is used in old DiskOnChip devices.
> > > >
> > > > Do you have one of those and use them with modern kernels ? Which one is
> > > > that?
> > >
> > > Yes. ID used in the MD2800-D08. I specifically included a configuration option
> > > to support this chip ;) Unfortunately, I can not say the exact device ID now because
> > > all of such devices sent in production, and I have no more now.
> > > Of course, these devices are not in production at the moment, but they are still
> > > being sold.
> >
> > Or probably, we can kill NANDs with 256 byte page - they are really from
> > the stone age, while the 512 bytes ones are at least from the copper
> > age.
>
> Hehe :)
> But, i suggest keep these definitions in the comments.
I want to go even further and just kill 256-bytes NAND p ages support
altogether, as I believe this is completely useless. Being in linux MTD
since 2005, I've never seen anyone using those.
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2013-03-05 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1362416362.801083474@f211.mail.ru>
2013-03-05 8:18 ` [PATCH 02/12] mtd: remove museum NAND ID's support Artem Bityutskiy
2013-03-05 8:32 ` Re[2]: " Alexander Shiyan
2013-03-05 8:41 ` Artem Bityutskiy
2013-03-05 8:46 ` Re[4]: " Alexander Shiyan
2013-03-05 8:45 ` Re[2]: " Artem Bityutskiy
2013-03-05 8:50 ` Re[4]: " Alexander Shiyan
2013-03-05 9:03 ` Artem Bityutskiy [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=1362474237.2943.34.camel@sauron \
--to=artem.bityutskiy@linux.intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shc_work@mail.ru \
/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