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.
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
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-thr
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_
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
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 whe
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. Th
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
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
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
10 matches
Mail list logo