kdrive probes a lot of PS/2 protocols for the mouse device, which
makes the mouse unusable for some seconds after X startup.
This new "protocol" option allows forcing the mouse protocol.
It can be used this way:
Xfbdev -mouse mouse,,protocol=ps/2 -keybd keyboard
Signed-off-by: Ol
Peter Hutterer writes:
> On Wed, May 27, 2009 at 07:04:16PM +0200, Olivier Blin wrote:
>> Peter Hutterer writes:
>>
>> > On Tue, May 26, 2009 at 03:30:08PM +0200, Olivier Blin wrote:
>> >> kdrive probes a lot of PS/2 protocols for the mouse device, which
>
Peter Hutterer writes:
> On Tue, May 26, 2009 at 03:30:14PM +0200, Olivier Blin wrote:
>> The mouse driver had some code to unconditionnally disable debug, even
>> if configured with --enable-debug. This adds back the mouse driver
>> debug output when built with debug opti
Peter Hutterer writes:
> On Tue, May 26, 2009 at 03:30:08PM +0200, Olivier Blin wrote:
>> kdrive probes a lot of PS/2 protocols for the mouse device, which
>> makes the mouse unusable for some seconds after X startup.
>> This new "protocol" option allows forcing t
The mouse driver had some code to unconditionnally disable debug, even
if configured with --enable-debug. This adds back the mouse driver
debug output when built with debug option.
Signed-off-by: Olivier Blin
---
hw/kdrive/linux/mouse.c |1 -
1 files changed, 0 insertions(+), 1 deletions
kdrive probes a lot of PS/2 protocols for the mouse device, which
makes the mouse unusable for some seconds after X startup.
This new "protocol" option allows forcing the mouse protocol.
It can be used this way:
Xfbdev -mouse mouse,,protocol=ps/2 -keybd keyboard
Signed-off-by: Ol
