Re: [PATCH] mos7840: fix chars_in_buffer() return value

On Fri, Sep 30, 2016 at 12:00:30AM +0300, Stas Sergeev wrote: > 29.09.2016 13:09, Johan Hovold пишет: > > On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: > >> The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on > >> a correct behaviour of that. > >> mos7840 implements

Re: [PATCH] mos7840: fix chars_in_buffer() return value

On Fri, Sep 30, 2016 at 12:00:30AM +0300, Stas Sergeev wrote: > 29.09.2016 13:09, Johan Hovold пишет: > > On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: > >> The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on > >> a correct behaviour of that. > >> mos7840 implements

Re: [PATCH] mos7840: fix chars_in_buffer() return value

29.09.2016 13:09, Johan Hovold пишет: On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch

Re: [PATCH] mos7840: fix chars_in_buffer() return value

29.09.2016 13:09, Johan Hovold пишет: On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch

Re: [PATCH] mos7840: fix chars_in_buffer() return value

On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: > The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on > a correct behaviour of that. > mos7840 implements it wrongly: if you write just one char, TIOCOUTQ > will return 32. > This patch should fix it by accounting the

Re: [PATCH] mos7840: fix chars_in_buffer() return value

On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: > The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on > a correct behaviour of that. > mos7840 implements it wrongly: if you write just one char, TIOCOUTQ > will return 32. > This patch should fix it by accounting the

[PATCH] mos7840: fix chars_in_buffer() return value

The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually written. This patch, unfortunately, misses the

[PATCH] mos7840: fix chars_in_buffer() return value

The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually written. This patch, unfortunately, misses the

Re: [PATCH] mos7840: fix chars_in_buffer() return value

24.09.2016 16:57, Sergei Shtylyov пишет: Hello. On 9/24/2016 4:47 PM, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix

Re: [PATCH] mos7840: fix chars_in_buffer() return value

24.09.2016 16:57, Sergei Shtylyov пишет: Hello. On 9/24/2016 4:47 PM, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix

Re: [PATCH] mos7840: fix chars_in_buffer() return value

Hello. On 9/24/2016 4:47 PM, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars

Re: [PATCH] mos7840: fix chars_in_buffer() return value

Hello. On 9/24/2016 4:47 PM, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars

[PATCH] mos7840: fix chars_in_buffer() return value

The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually written. This patch, unfortunately, misses the

[PATCH] mos7840: fix chars_in_buffer() return value

The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually written. This patch, unfortunately, misses the

[PATCH] mos7840: fix chars_in_buffer() return value

The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually writCaylan Van Larson ten. This

[PATCH] mos7840: fix chars_in_buffer() return value

The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually writCaylan Van Larson ten. This patch,