844c42f079
There is a quirk needed to switch the controller to standard SD mode (copied from FreeBSD). The response type configuration for R7 response was incorrect, this response type does not have a data phase. This made the Ricoh SDHCI implementation generate an unexpected "transfer complete" interrupt, while apparently the implementation in QEMU didn't. The interrupt generation is a bit different from what I got in QEMU when developping the driver, for some commands, we get only a "transfer complete" and no "command complete" interrupt as I'd expect when the command completes. This is handled in the following way: - The interrupt always releases the semaphore to notify that something has happened (once per event) - When the main thread waits for an event, it always uses the same pattern: while (!condition) acquire_sem(...) This pattern makes it not wait at all if the condition is already satisfied. If the interrupt triggers later or already happened when the code gets to execute this while loop, the semaphore can be left with some tokens in it. These will be emptied the next time the thread waits on something. To make sure ths works properly and everything is synchronizing as expected, some extra checks are added before execution of a command to make sure the hardware is in the expected state. There is also lots of extra tracing, I prefer to leave this enabled initially and wait for some other users to test this new driver on their hardware. When we are confident enough that it is compatible with several implementations, we can reduce the tracing or turn it off. Change-Id: Ib9617dbea62f87124dbaad0027b53a13d949641f Reviewed-on: https://review.haiku-os.org/c/haiku/+/3600 Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com> |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| lgtm.yml | ||
| License.md | ||
| ReadMe.Compiling.md | ||
| ReadMe.md | ||
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.