genode

History

Emery Hemingway 1fce8d0d74 default ahci_drv and part_blk Block sessions to read-only Add a "writeable" policy option to the ahci_drv and part_blk Block servers and default from writeable to ready-only. Should a policy permit write acesss the session request argument "writeable" may still downgrade a session to ready-only. Fix #2469		2017-08-28 16:49:51 +02:00
..
main.cc	default ahci_drv and part_blk Block sessions to read-only	2017-08-28 16:49:51 +02:00
README	ram_blk: transition to the new base API	2016-07-11 12:04:52 +02:00
target.mk	block layer: transition to new API	2016-08-29 17:23:20 +02:00

README

RAM block device is an implementation of the block-session interface
running as a client of a RAM session. It either populates the RAM dataspace
by using a ROM dataspace, similiar to loop devices. For example to use
an ISO file the component has to be configured as follows:

! <config file="image.iso" block_size="2048"/>

To use a empty RAM dataspace that is 256MiB large and has a block size
of 4KiB the configuration looks like this:

! <config size="256M" block_size="4096"/>

Either 'size' or 'file' has to specified. If both are declared the 'file'
attribute is soley evaluated.