eeb2d95b1f
Until now, block drivers had to deal with a pointer to the client session component, e.g.: to acknowledge block packets already processed. When a session was closed, the driver object wasn't informed explicitly, which leads to defensive programming, or lastly to a race-condition in test-blk-srv. To prevent from this class of errors, the pointer is now private to the generic block driver base class, and not accessible to the concrete driver implementation. Moreover, the driver gets explicitly informed when a session got invalidated. Ref #113 |
||
|---|---|---|
| .. | ||
| main.cc | ||
| README | ||
| target.mk | ||
ROM loop device is an implementation of the block-session interface running as a client of a ROM session. It exports the requested ROM file as a block device, similiar to loop devices known in Linux. The example shows how to choose the right ROM file in its configuration and how to configure the exported block size. ! <config file="image.iso" block_size="2048"/>