RTEMS 6.1-rc1
|
Macros | |
#define | RTEMS_GENERIC_BLOCK_DEVICE_DRIVER_ENTRIES |
Functions | |
RTEMS_DEPRECATED rtems_device_driver | rtems_blkdev_generic_read (rtems_device_major_number major, rtems_device_minor_number minor, void *arg) |
RTEMS_DEPRECATED rtems_device_driver | rtems_blkdev_generic_write (rtems_device_major_number major, rtems_device_minor_number minor, void *arg) |
RTEMS_DEPRECATED rtems_device_driver | rtems_blkdev_generic_open (rtems_device_major_number major, rtems_device_minor_number minor, void *arg) |
RTEMS_DEPRECATED rtems_device_driver | rtems_blkdev_generic_close (rtems_device_major_number major, rtems_device_minor_number minor, void *arg) |
RTEMS_DEPRECATED rtems_device_driver | rtems_blkdev_generic_ioctl (rtems_device_major_number major, rtems_device_minor_number minor, void *arg) |
Variables | |
RTEMS_DEPRECATED const rtems_driver_address_table | rtems_blkdev_generic_ops |
Generic disk device operations for standard RTEMS IO drivers.
#define RTEMS_GENERIC_BLOCK_DEVICE_DRIVER_ENTRIES |
The device driver interface conventions suppose that a driver may contain an initialize, open, close, read, write and IO control entry points. These primitives (except initialize) can be implemented in a generic fashion based upon the supplied block device driver IO control handler. Every block device driver should provide an initialize entry point, which registers the appropriate IO control handler.