On Thu, 2014-01-16 at 07:44 +, Gupta, Pekon wrote:
However, *assuming NAND driver can identify erased-page correctly*,
I don't want UBI/UBIFS to re-check the read_buf for 0xff again, because
underlying NAND driver has already identified as erased-page, and
fixed the data before passing
On Wed, 2014-01-15 at 21:29 +, Gupta, Pekon wrote:
Hi Artem,
From: Artem Bityutskiy [mailto:artem.bityuts...@linux.intel.com]
snip
Conclusion: all UBIFS needs is a way to ask the driver - is this NAND
page blank or not? UBIFS does not really has to compare to all 0xFFs.
Thanks for
Hi,
On Fri, Jan 3, 2014 at 6:29 PM, Artem Bityutskiy
artem.bityuts...@linux.intel.com wrote:
Hi Pekon,
On Fri, 2014-01-03 at 11:45 +, Gupta, Pekon wrote:
*_Case-1_ Flashing UBIFS image from u-boot using 'nand write' utility*
For a partially written erased-block..
(a) 1st page is
On Mon, 2014-01-13 at 17:49 +0530, Calvin Johnson wrote:
If the 4th to last-page are left blank and not covered with ECC, what
will happen in case of bit flips on the blank pages? There was an
issue reported some time back.
Hi Calvin,
From: Artem Bityutskiy [mailto:artem.bityuts...@linux.intel.com]
On Mon, 2014-01-13 at 17:49 +0530, Calvin Johnson wrote:
If the 4th to last-page are left blank and not covered with ECC, what
will happen in case of bit flips on the blank pages? There was an
issue reported some time
On Mon, 2014-01-13 at 13:16 +, Gupta, Pekon wrote:
Currently both UBI and UBIFS layer checks for erased-page to be
all(0xff),
But I think its over-kill to put this burden on UBI or UBIFS layer,
because
low-level controller drivers can handle this easily.
So, if Artem and Brian agree to
Hi Artem,
I wanted to check the 'white-space-fixup' and re-reading your
documentation before, so got delayed in replying.
+ my mail got moderated again by mailman..
From: Artem Bityutskiy [mailto:artem.bityuts...@linux.intel.com]
[...]
If you are worried about fragmentation, we can discuss
Hi All,
I have been facing a weird problem, may be someone has a solution.
*_Case-1_ Flashing UBIFS image from u-boot using 'nand write' utility*
For a partially written erased-block..
(a) 1st page is written with 'erase-header'
(b) 2nd page is written with 'volume-header'
(c) '3rd page' is
Hi Pekon,
On Fri, 2014-01-03 at 11:45 +, Gupta, Pekon wrote:
*_Case-1_ Flashing UBIFS image from u-boot using 'nand write' utility*
For a partially written erased-block..
(a) 1st page is written with 'erase-header'
(b) 2nd page is written with 'volume-header'
(c) '3rd page' is written
Hi Gupta,
On 03/01/2014 13:59, Artem Bityutskiy wrote:
Basically, ubiformat is the correct UBI-aware flasher, while
u-boot's nand write seems to be a dumb flasher.
It is, it is *not* recommended for UBI volume without ubinizing your
image.
I guess you have 2
options:
1. Teach u-boot's
10 matches
Mail list logo
