Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
A NILFS2 score card
Posted Nov 7, 2012 14:34 UTC (Wed) by mpr22 (subscriber, #60784)
Posted Nov 7, 2012 14:43 UTC (Wed) by mirabilos (subscriber, #84359)
In that case, storing data NOT’d might make sense,
though no idea about the performance impact.
Posted Nov 7, 2012 16:47 UTC (Wed) by cmorgan (guest, #71980)
Also keep in mind that some flash chips may not support flipping single bits inside of bytes or flipping individual bytes etc and warn against it. I've personally done this and it worked (and we had error correction) but for some reason the manufacturer said specifically not to. Maybe this is a serial flash only issue though. Can't say I've had that much experience with a range of flash parts.
Posted Nov 8, 2012 16:30 UTC (Thu) by mirabilos (subscriber, #84359)
But alas, if it isn’t… someone has to deal with it. (And the other comments suggest that the state may not be the same everywhere, so blindly XORing with FFh in the kernel will also not be a solution.)
Posted Nov 9, 2012 18:09 UTC (Fri) by BenHutchings (subscriber, #37955)
Posted Nov 7, 2012 14:41 UTC (Wed) by hmh (subscriber, #3838)
So, a page full of 0xff is ready for writing. One full of 0x00 has to be erased to receive any other data. Only, you must erase a full block at a time, and blocks are (much) larger than pages.
Posted Nov 7, 2012 18:46 UTC (Wed) by zlynx (subscriber, #2285)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds