Re: [BUG] 2.6.12-rc1/rc2 mouse0 became mouse1

Hi!

> This doesn't sound right to me. After upgrading from 2.6.11.5/6 to
> 2.6.12-rc1/rc2 I detected that my mouse didn't operate anymore when
> loading up XOrg, I realized that /dev/input/mouse0 (which worked for
> years) had to be changed to /dev/input/mouse1. Anyone care to explain
> why this had to be changed or what the intention behind this was ?
> 

This is a bug where we assume keyboard has scrollwheel, and therefore
we pretend its keyboard and a bit of mouse?

Did we stop generating zero mouse movements during typing?
				Pavel
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [BUG] 2.6.12-rc1/rc2 mouse0 became mouse1
    • From: Ali Akcaagac <[email protected]>

• Prev by Date: Re: [PATCH 1/3] cifs: md5 cleanup - functions
• Next by Date: Re: [PATCH encrypted swsusp 1/3] core functionality
• Previous by thread: Re: [BUG] 2.6.12-rc1/rc2 mouse0 became mouse1
• Next by thread: [PATCH] pm_message_t corrections still missing from 2.6.12-rc2
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]