From: Artem Bityutskiy <dedekind1@gmail.com>
To: Iwo Mergler <Iwo.Mergler@netcommwireless.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: RE: UBIFS fails to mount on second boot
Date: Sun, 15 Jul 2012 11:25:30 +0300 [thread overview]
Message-ID: <1342340730.25457.3.camel@brekeke> (raw)
In-Reply-To: <6871BC8982B258468985EE735D2C575243C0F088B6@ntcex01.corp.netcomm.com.au>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Mon, 2012-07-02 at 17:49 +1000, Iwo Mergler wrote:
> It's similar to a BeagleBone, but with NAND FLASH, I'm using the
> omap2 ECC driver.
>
> So, if I set NAND_NO_SUBPAGE_WRITE in chip.options, UBI will
> leave the subpages alone?
I think so, but it is better to dig and find out why sub-pages to not
work - this sounds like a bug. With sub-pages support you'll waste less
flash space because UBI overhead will be smaller.
> So I had to make two debug runs, one each for ubi and ubifs debugging
> enabled.
I've reproduced this bug using nandsim and fixed it. I've sent you the
fix few minutes ago. Could you please test it? After I've got a
"Tested-by:", I'll send it to Linus and it will also go to -stable.
Thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-07-15 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 5:23 UBIFS fails to mount on second boot Iwo
2012-06-27 14:10 ` Artem Bityutskiy
2012-06-29 6:05 ` Iwo Mergler
2012-06-29 13:46 ` Artem Bityutskiy
2012-07-02 7:49 ` Iwo Mergler
2012-07-03 1:16 ` Iwo Mergler
2012-07-14 4:39 ` Artem Bityutskiy
2012-07-18 7:05 ` Iwo Mergler
2012-07-18 7:21 ` Artem Bityutskiy
2012-07-19 1:06 ` Iwo Mergler
2012-07-15 8:25 ` 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=1342340730.25457.3.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=Iwo.Mergler@netcommwireless.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