genode/repos/os/src/drivers/ahci
Christian Prochaska 344f6f9e53 os/include/block: API transition (fix 'deprecated' warnings)
...and adaptation of the users of 'Block::Driver', 'Block::Root' and
'Block::Session_component' to the modified interface.

Issue #1987
2017-01-20 16:46:57 +01:00
..
spec base: rename 'Volatile_object' to 'Reconstructible' 2016-12-01 17:46:50 +01:00
ahci.cc os/include/block: API transition (fix 'deprecated' warnings) 2017-01-20 16:46:57 +01:00
ahci.h os/include/block: API transition (fix 'deprecated' warnings) 2017-01-20 16:46:57 +01:00
ata_driver.h os/include/block: API transition (fix 'deprecated' warnings) 2017-01-20 16:46:57 +01:00
atapi_driver.h os/include/block: API transition (fix 'deprecated' warnings) 2017-01-20 16:46:57 +01:00
main.cc os/include/block: API transition (fix 'deprecated' warnings) 2017-01-20 16:46:57 +01:00
README Make label prefixing more strict 2016-11-30 13:37:07 +01:00
target.mk ahci: transition to the new base API 2016-06-28 11:08:13 +02:00

This directory contains the implementation of Genode's AHCI driver

Behavior
--------

The driver supports x86 32/64 bit platforms and the Exynos5 SOC. If
more than one AHCI controller is present, the first one will be used.
Each active device on each AHCI port will be represented by a Genode
block session. The server must be configured via a policy, that states
which client can access a certain device:


!<start name="ahci">
!  <binary name="ahci_drv" />
!  <resource name="RAM" quantum="10M" />
!  <provides><service name="Block" /></provides> }
!  <route>
!    <any-service> <parent /> <any-child /> </any-service>
!  </route>
!  <config atapi="no">
!    <!-- use model and serial number -->
!    <policy label_prefix="test-ahci" model="QEMU HARDDISK" serial="QM00005" />
!    <!-- use controller port number -->
!    <policy label_prefix="bench" device="1" />
!  </config>
!</start>

In the example above, a session request labeled with "test-ahci" gains access to
a device with certain model and serial numbers, while "bench" gains access to
device at port 1. ATAPI support is by default disabled and can be enabled by
setting the config attribute "atapi" to "yes".