On 17.11.2010, at 12:58, Jan Kiszka wrote:
> Am 17.11.2010 12:55, Alexander Graf wrote:
>>
>> On 17.11.2010, at 11:18, Jan Kiszka wrote:
>>
>>> Am 19.10.2010 17:04, Jan Kiszka wrote:
Move the buffer flush from mux_chr_read to mux_chr_can_read. While the
latter is called periodically,
Am 17.11.2010 12:55, Alexander Graf wrote:
>
> On 17.11.2010, at 11:18, Jan Kiszka wrote:
>
>> Am 19.10.2010 17:04, 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
>>> characte
On 17.11.2010, at 11:18, Jan Kiszka wrote:
> Am 19.10.2010 17:04, 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 fr
Am 19.10.2010 17:04, 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 rea
Am 19.10.2010 um 17:04 schrieb Jan Kiszka :
> 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
Am 19.10.2010 17:22, Alexander Graf wrote:
>
> Am 19.10.2010 um 17:04 schrieb Jan Kiszka :
>
>> 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 probl
