2380fc442f
Instead of fixing the missing dynamic facilities of the AHCI driver backends for x86 and Exynos5, just avoid to create/destroy the backend for every new connection, but always use one and the same object. The AHCI drivers need to be re-written anyway, see issue #1352 for instance, we can make it more robust for the dynamic case then. Fixes #786 Fixes #1133 |
||
---|---|---|
.. | ||
exynos5 | ||
include | ||
x86 | ||
empty.cc | ||
main.cc | ||
README | ||
target.mk |
This directory contains an implementation of a simple AHCI driver. Behavior -------- The server implements Genode's new block-driver API ('os/include/block'), thus exposing the block-session interface as front-end. AHCI depends on Genode's PCI driver as well as the timer server. For a usage example see: 'os/run/ahci.run'. Limitations and known issues ---------------------------- Currently, the server scans the PCI bus at startup and retrieves the first available AHCI controller, scans the controller ports and uses the first non-ATAPI port where a device is present. On real hardware and on kernels taking advantage of I/O APICs (namely NOVA and Fiasco.OC) we still lack support for ACPI parsing and thus for interrupts, leading to a non-working driver.