linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo70@gmail.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: pekon <pekon@pek-sem.com>
Subject: Re: UBI ECC errors on kernel 3.16.2
Date: Mon, 06 Oct 2014 22:35:40 +0200	[thread overview]
Message-ID: <5432FD1C.7080608@gmail.com> (raw)
In-Reply-To: <5432F7CE.3010002@pek-sem.com>

Dear Pekon,


> (1) mkfs.ubifs  -m (min-io-size=2048)   [-s (subpage-size=2048)]
> (2) ubinize     -m (min-io-size=2048)
> (3) ubiformat   -O 2048  (indicates that offset of volume-ID header 
> from start of block)
>
Yes, this is the configuration i alwaus used. But with this last kernel 
was not working.
>> 2) So how does it works this subpages-write support if the nand flash
>> does not
>> supports subpages write ?
>>
> You can disable sub-page write by adding following in your driver probe.
> +    chip->options |= NAND_NO_SUBPAGE_WRITE
>
Thansk, this is much more elegant.
Anyway, mtd probe should be able to detect that my flash (mt28f1g08abb) 
does not support
sub-pages.

I opened a bug.

https://bugzilla.kernel.org/show_bug.cgi?id=85481

Many thanks
Angelo

      parent reply	other threads:[~2014-10-06 20:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 20:41 UBI ECC errors on kernel 3.16.2 Angelo Dureghello
2014-10-01 20:51 ` Richard Weinberger
2014-10-01 21:35   ` Angelo Dureghello
2014-10-02  9:19     ` Fwd: " Angelo Dureghello
2014-10-02 17:26       ` Angelo Dureghello
2014-10-03  8:15         ` Richard Weinberger
2014-10-06  4:49         ` Pekon Gupta
2014-10-06  9:02           ` Angelo Dureghello
2014-10-06 20:13             ` pekon
2014-10-06 20:31               ` Angelo Dureghello
2014-10-06 20:35               ` Angelo Dureghello [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=5432FD1C.7080608@gmail.com \
    --to=angelo70@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@pek-sem.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;
as well as URLs for NNTP newsgroup(s).