6a1f97581f
Most common values for interrupt-cells are 1 or 2. - one cell: the single cell defines the index of the interrupt within the controller. - two cells: the first cell defines the index of the interrupt within the controller, while the second cell is specifies interrupt flags like active-high/active-low, edge triggered or level-sensitive. ARM Generic Interrupt Controller uses 3 cells: - the 1st cell is the interrupt type: 0 for SPI, 1 for PPI - the 2nd cell contains the interrupt number - the 3rd cell contains interrupt flags, similarly to the 2-cell format SPI interrupts are numbered from 0 in the device tree but they start from 32 on the GIC so an offset should be applied. On the other hand, ACPI tables contain interrupt numbers as they are expected by the GIC so no offset should be applied when interrupts are read from ACPI. see: https://www.kernel.org/doc/Documentation/devicetree/bindings/interrupt-controller/interrupts.txt https://www.kernel.org/doc/Documentation/devicetree/bindings/interrupt-controller/arm%2Cgic.txt https://developer.arm.com/documentation/198123/0301/Arm-CoreLink-GIC-fundamentals Change-Id: Ia41371bd965347f89c17d62e391480d7b2083bae Reviewed-on: https://review.haiku-os.org/c/haiku/+/5490 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk> |
||
|---|---|---|
| 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.