public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anssi Hannula <anssi.hannula@gmail.com>
To: Parag Warudkar <parag.lkml@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] USBHID: Make Boot Protocol drivers depend on EMBEDDED
Date: Mon, 22 Dec 2008 00:17:38 +0200	[thread overview]
Message-ID: <494EC082.2010207@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0812211708450.7101@parag-desktop>

Parag Warudkar wrote:
> 
> On Sun, 21 Dec 2008, Jiri Kosina wrote:
> 
>> On Sun, 21 Dec 2008, Andrew Morton wrote:
>>
>>>> So do I get it right that the only reason of the problem you were 
>>>> seeing was that in the 2.6.27 kernel you have compiled usbhid module, 
>>>> which was then used for driving your mouse,but in 2.6.28-rcX you 
>>>> compiled and used 'usbmouse' instead, and therefore this is not a 
>>>> regression?
>>> Shouldn't usbmouse support two-dimensional mice as well?
>> Yup, but that's a separate issue on my TODO. I first want to know whether 
>> this is a regression or not.
>>
> 
> I have always compiled usbmouse as a module - the problem or regression 
> here was that it was loaded instead of usbhid when both were compiled as 
> modules - but I don't think this is a kernel regression, here is why -
> 
> The problem happened with Fedora 10 - when I booted into Ubuntu 8.10 with 
> the same kernel compiled with same config, usbhid was correctly loaded and 
> mouse worked. So I would forget this as a Fedora specific issue.

It may well be that Ubuntu has usbmouse blacklisted or employs udev
rules that force usbhid to be loaded before usbmouse.

On Mandriva it was handled in a similar way, before usbmouse was
disabled from the kernel (no reason to have it in a "normal" kernel).

> Thanks for the pointers.

-- 
Anssi Hannula

  reply	other threads:[~2008-12-21 22:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-21  3:11 2.6.28-rc9: USB Mouse unhappy Parag Warudkar
2008-12-21  6:12 ` Andrew Morton
2008-12-21  6:26   ` Parag Warudkar
2008-12-21 10:56     ` Anssi Hannula
2008-12-21 15:17       ` Parag Warudkar
2008-12-21 17:30         ` Jiri Kosina
2008-12-21 18:39           ` Jiri Kosina
2009-01-09 23:11             ` Rafael J. Wysocki
2009-01-09 23:18               ` Parag Warudkar
2009-01-09 23:19               ` Jiri Kosina
2009-01-10  0:19                 ` Rafael J. Wysocki
2008-12-21 19:49           ` [PATCH] USBHID: Make Boot Protocol drivers depend on EMBEDDED Parag Warudkar
2008-12-21 21:48             ` Jiri Kosina
2008-12-21 22:02               ` Andrew Morton
2008-12-21 22:03                 ` Jiri Kosina
2008-12-21 22:12                   ` Parag Warudkar
2008-12-21 22:17                     ` Anssi Hannula [this message]
2008-12-21 22:23                       ` Parag Warudkar
2008-12-21 22:44                         ` Jiri Kosina
2008-12-21 23:55                           ` Parag Warudkar
2008-12-22 21:52             ` Jiri Kosina
2008-12-21 17:24 ` 2.6.28-rc9: USB Mouse unhappy Jiri Kosina
2008-12-21 18:22   ` Parag Warudkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=494EC082.2010207@gmail.com \
    --to=anssi.hannula@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=parag.lkml@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox