public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Mathieu Malaterre <malat@debian.org>
Cc: MIPS Creator CI20 Development
	<mips-creator-ci20-dev@googlegroups.com>,
	linux-mtd@lists.infradead.org, boris.brezillon@bootlin.com
Subject: Re: ubi: refuse attaching mtd3 - MLC NAND is not supported
Date: Mon, 28 May 2018 22:15:35 +0200	[thread overview]
Message-ID: <9878779.9ArrsalhVU@blindfold> (raw)
In-Reply-To: <CA+7wUsx27-K+XFt0_TqzeAdpydQ8cr7rXbCa8S8tDhGonzO-kQ@mail.gmail.com>

Mathieu,

Am Freitag, 25. Mai 2018, 12:12:02 CEST schrieb Mathieu Malaterre:
> > No. MLC is simply not supported and not safe to use.
> > With that commit we reflect the state of the code and stop giving wrong promises.
> 
> ACK. Would you recommend an alternate filesystem then ?

There is none.

One option you have is putting the MLC NAND into SLC mode, some support this.
This needs to be achieved by a vendor specific command which is often undocumented.

Boris and I experimented also with software SLC mode in UBI.
If you want you can revive our work.
 
> > I can hardly believe that it has been working great so far, did you
> > ever do power-cut tests?
> > Or are there other mechanisms on your board that make MLC usable by UBI?
> > For example SLC-emulation.
> 
> Looking quickly at the tech specs:
> 
> https://www.elinux.org/CI20_Hardware#ROM.2FNAND
> 
> ...
> Is provided by a single Samsung K9GBG08UOA NAND flash, using an 8bit
> data interface to the SoC.
> ...
> 
> So my understanding is that "it just worked" so far. I've tried
> contacting some of the people involved with the design of CI20 to get
> confirmation.

"just worked" in terms of nobody gave it a decent testing, I fear. ;-\

Thanks,
//richard

      reply	other threads:[~2018-05-28 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 19:28 ubi: refuse attaching mtd3 - MLC NAND is not supported Mathieu Malaterre
2018-05-24 19:42 ` Richard Weinberger
2018-05-25 10:12   ` Mathieu Malaterre
2018-05-28 20:15     ` Richard Weinberger [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=9878779.9ArrsalhVU@blindfold \
    --to=richard@nod.at \
    --cc=boris.brezillon@bootlin.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=malat@debian.org \
    --cc=mips-creator-ci20-dev@googlegroups.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