For a new type of device, for example an accelerator, there are not many
options except:
-1. create another lib/librte_MySpecialDev, driver/MySpecialDrv and use it
+1. create another lib/MySpecialDev, driver/MySpecialDrv and use it
through Bus/PMD model.
2. Or, create a vdev and implement necessary custom APIs which are directly
exposed from driver layer. However this may still require changes in bus code
1. Following are some generic operations which can be treated as applicable
to a large subset of device types. None of the operations are mandatory to
- be implemented by a driver. Application should also be design for proper
+ be implemented by a driver. Application should also be designed for proper
handling for unsupported APIs.
* Device Start/Stop - In some cases, 'reset' might also be required which
* Firmware Management - Firmware load/unload/status
2. Application API should be able to pass along arbitrary state information
- to/fro device driver. This can be achieved by maintaining context
+ to/from device driver. This can be achieved by maintaining context
information through opaque data or pointers.
Figure below outlines the layout of the rawdevice library and device vis-a-vis
--vdev 'rawdev_dev1'
-Our using the rte_vdev_init API within the application code.
+Or using the rte_vdev_init API within the application code.
.. code-block:: c