Lines Matching refs:CharDriverState

3 I. CharDriverState objects:
6 One of the strangest abstraction in QEMU is the "CharDriverState"
23        int  qemu_chr_write( CharDriverState*  cs,
32     There is no way to know in advance how many bytes a given CharDriverState
46           that you are ready to accept from the CharDriverState. Its
51         - a 'read' function that will send you bytes from the CharDriverState
63          void qemu_chr_add_handlers(CharDriverState *s,
69   - qemu_chr_open() is used to create a new CharDriverState object from a
72          CharDriverState*  qemu_chr_open(const char*  filename);
106             A CharDriverState that is used to receive kernel log messages
110             A CharDriverState that is used to exchange messages between the
122             A CharDriverState that is used to connect the emulated system to
128             A CharDriverState that is used to connect the emulated system to a
134 II. CharDriverState users:
137 As described above, a CharDriverState "user" is a piece of code that can write
138 to a CharDriverState (by calling qemu_chr_write() explicitely) and can also
156 a CharDriverState object that implements a *write* buffer to send data to a
160     CharDriverState*  qemu_chr_open_buffer( CharDriverState*  endpoint );
179 used to connect two CharDriverState users together. For example, this is used
188     int  qemu_chr_open_pipe(CharDriverState* *pfirst,
189                             CharDriverState* *psecond);
200 and writing to it is never blocking. This simplifies CharDriverState