public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Gudjon I. Gudjonsson" <gudjon@gudjon.org>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ECC configuration of NAND from Linux  (MEMSETOOBSEL)
Date: Fri, 12 Jan 2018 19:50:00 +0100	[thread overview]
Message-ID: <2581607.A7Zl2yeV5U@fessender> (raw)
In-Reply-To: <20180112154639.63a8d133@bbrezillon>

Hi Boris

Thanks for the answer.
> > I read your FAQ and found the reference to ioctl (MEMSETOOBSEL) [1]
> > but it seems to be removed from the kernel.
> > /*
> >  * Note, the following ioctl existed in the past and was removed:
> >  * #define MEMSETOOBSEL           _IOW('M', 9, struct nand_oobinfo)
> >  * Try to avoid adding a new ioctl with the same ioctl number.
> >  */
> > I assume this is an error in the documentation but I wonder if you
> > know any solution to my problem?
> 
> It's not something you can change dynamically. When you change the ECC
> config, it makes existing content unreadable. In order to change this
> setting you'll have to erase the whole flash and then change the ECC
> config in your DT or board file (note that not all drivers support
> adjusting the ECC strength/step-size).
I will have to accept that but can you please tell me how to change the
ECC strength if my driver supports it? My plan is to use swupdate and
update the system using an SD-card that is already installed but I could
not find any reference to changing the ECC strength.
I am using the Atmel SAMA5d36 CPU and Micron mt29F2G08abaeawp 
NAND flash. 

Regards
Gudjon

  reply	other threads:[~2018-01-12 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12  0:29 ECC configuration of NAND from Linux (MEMSETOOBSEL) Gudjon I. Gudjonsson
2018-01-12 14:46 ` Boris Brezillon
2018-01-12 18:50   ` Gudjon I. Gudjonsson [this message]
2018-01-13  2:41     ` Steve deRosier
2018-01-13  8:24       ` Boris Brezillon
2018-01-13 17:34         ` Steve deRosier
2018-01-14 15:10           ` Boris Brezillon

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=2581607.A7Zl2yeV5U@fessender \
    --to=gudjon@gudjon.org \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linux-mtd@lists.infradead.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