| commit | 4e9adc419ee72c055ee2822d382feaf2b0c461f2 | [log] [tgz] |
|---|---|---|
| author | Mohan Srinivasan <srmohan@google.com> | Fri Sep 21 18:44:20 2018 -0700 |
| committer | Mohan Srinivasan <srmohan@google.com> | Sat Sep 22 05:23:38 2018 +0000 |
| tree | 69d2584db61f634307c6c83d4fc34f9aecc1058a | |
| parent | 213e9b7da9e0ab02736486f608699248f4483b2c [diff] |
[dev][nand][aml-rawnand] Fix uncorrectable ECC handling. 1) Fix handling of uncorrectable ECC errors, For non-randomized data, uncorrectable ECC errors result in an error propagated up to the NAND protocol, which retries the read thrice. For randomized data a further check is necessary (which was previously wrong - reversed). 2) Add verbose error logging to the code handling uncorrectable ECC errors. 3) Fix error handling for the case where we timeout waiting for a read interrupt. 4) Populate the ECC strength from the Page0 read (the ECC strength is used in the handling of ECC uncorrectable errors for the randomized case - not applicable to us right now, but might be later). Bug: ZX-2616. Test: Use Ruchira's code to do SDIO reads at intervals of our choice to generate bus loading, and use Ricardo's tester for data validation. Change-Id: I1be58d291f872cb91018aabd3c0673caa109c507
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.