Alexander Graf wrote:
On 14.05.2010, at 18:17, Jan Kiszka wrote:
Alexander Graf wrote:
Now that I can finally reproduce the bug with --enable-io-thread, I can
verify that it does *not* fix the issue.
I do not trust your tests. :p
I just tried to reproduce with --enable-io-thread and the
On 15.05.2010, at 10:36, Jan Kiszka wrote:
Alexander Graf wrote:
On 14.05.2010, at 18:17, Jan Kiszka wrote:
Alexander Graf wrote:
Now that I can finally reproduce the bug with --enable-io-thread, I can
verify that it does *not* fix the issue.
I do not trust your tests. :p
I just tried
Alexander Graf wrote:
On 15.05.2010, at 10:36, Jan Kiszka wrote:
Alexander Graf wrote:
On 14.05.2010, at 18:17, Jan Kiszka wrote:
Alexander Graf wrote:
Now that I can finally reproduce the bug with --enable-io-thread, I can
verify that it does *not* fix the issue.
I do not trust your
On 12.05.2010, at 20:51, Jan Kiszka wrote:
Alexander Graf wrote:
Jan Kiszka wrote:
Alexander Graf wrote:
Jan Kiszka wrote:
Move the buffer flush from mux_chr_read to mux_chr_can_read. While the
latter is called periodically, the former will only be invoked when new
characters arrive
Alexander Graf wrote:
On 12.05.2010, at 20:51, Jan Kiszka wrote:
Alexander Graf wrote:
Jan Kiszka wrote:
Alexander Graf wrote:
Jan Kiszka wrote:
Move the buffer flush from mux_chr_read to mux_chr_can_read. While the
latter is called periodically, the former will only be invoked when new
On 14.05.2010, at 18:17, Jan Kiszka wrote:
Alexander Graf wrote:
On 12.05.2010, at 20:51, Jan Kiszka wrote:
Alexander Graf wrote:
Jan Kiszka wrote:
Alexander Graf wrote:
Jan Kiszka wrote:
Move the buffer flush from mux_chr_read to mux_chr_can_read. While the
latter is called
Alexander Graf wrote:
Jan Kiszka wrote:
Alexander Graf wrote:
Jan Kiszka wrote:
Move the buffer flush from mux_chr_read to mux_chr_can_read. While the
latter is called periodically, the former will only be invoked when new
characters arrive at the back-end. This caused problems to
Jan Kiszka wrote:
Move the buffer flush from mux_chr_read to mux_chr_can_read. While the
latter is called periodically, the former will only be invoked when new
characters arrive at the back-end. This caused problems to front-end
drivers whenever they were unable to read data immediately, e.g.
Alexander Graf wrote:
Jan Kiszka wrote:
Move the buffer flush from mux_chr_read to mux_chr_can_read. While the
latter is called periodically, the former will only be invoked when new
characters arrive at the back-end. This caused problems to front-end
drivers whenever they were unable to read
Jan Kiszka wrote:
Alexander Graf wrote:
Jan Kiszka wrote:
Move the buffer flush from mux_chr_read to mux_chr_can_read. While the
latter is called periodically, the former will only be invoked when new
characters arrive at the back-end. This caused problems to front-end
drivers
10 matches
Mail list logo