locked flash bits handling
alfred.hitch at gmail.com
Thu Jan 12 06:15:41 EST 2006
If my flash blocks are locked and someone tries to write to those blocks.
I see an error returned back saying
Not marking space as dirty XXXX flash driver returned retlen zero.
So does it means that mtd code doesnt happens to handle the lock'ing
and unlocking of flash blocks when user plane wants to write back ?
In my case flash is Intel J3 ver C and reason for locking is to
prevent and accidental hardware errors / reset related flahs
So, for some specific user plane segments, we would have liked to
accept user writting as acceptable valid writes. So, was wondering on
1) Why wouldn't MTD handle this ? any option / patch available to do so ?
2) From user plane cp A B for example, I will have to unlock , then
issue copy command and then lock.
As I dont know which flash sector / block it will be for destination
file at user level. I cannot unlock that block specifcally ?
More information about the linux-mtd