Lines Matching refs:character

67 for Linux based on character devices, SocketCAN uses the Berkeley
80 are based on character devices and provide comparatively little
82 driver which provides a character device interface to send and
86 character-device implementations support only one single process to
115 character device, too, but this would lead to a technically inelegant
122 * Code duplication.  A character device cannot make use of the Linux
126 * Abstraction.  In most existing character-device implementations, the
128   provides the character device for the application to work with.
130   block devices.  For example you don't have a character device for a
134   which provide a unified character or block device interface to the
140   The easiest way to implement a CAN device driver is as a character
423   known access to CAN character devices. To meet the new possibilities
921   CAN character device driver. Similar to other known network device