| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to avoid some bogus transfers
|
| |
|
| |
|
| |
|
|
|
|
| |
type. SAMA5 NAND: Fix for read nand in smaller chunks
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
be able to support NAND
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
might just be a NAND uncorrectable bit error. Make scanning of the device on startup optional. This might have introduced some NXFFS issure -- To be determined
|
| |
|
| |
|
|
|
|
| |
the read error probably just means that an uncorrectable ECC was encountered
|
|
|
|
| |
failures. NXFFS can't just give up in these cases and must treat read failures like bad blocks
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
endpoints)
|
|
|
|
| |
function
|
|
|
|
| |
function
|
|
|
|
| |
function
|
|
|
|
| |
function
|
|
|
|
| |
mysterious race conditions
|
| |
|
| |
|
| |
|
| |
|