Lines Matching full:will
15 can see "qemu-char.h" for the full interface, but here we will only describe
28 on the underlying implementation (some of them will just return 0 instead).
38 to a CS object. We will ignore "events" here and focus on the
42 two functions that will be called whenever the object has something for
51 - a 'read' function that will send you bytes from the CharDriverState
144 - The hardware serial port emulation (e.g. hw/goldfish_tty.c) will read data
149 which will in most cases be an emulated serial port.
162 This function returns a new CS object that will buffer in the heap any data
164 iteration, the CharBuffer will try to send data to the endpoint until it
170 Note also that calling qemu_chr_add_handler() on the CharBuffer will do the
185 pipe, and this function will return the two endpoints to you:
191 When you write to one end of the pipe (with qemu_chr_write()), the charpipe will
195 The charpipe will try to re-send the buffered data on the next event loop
