From: Vojtech Pavlik <vojtech@suse.cz>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, edouard.tisserant@wanadoo.fr
Subject: Re: Acecad USB Tablet: usbmouse takeover and odd motion
Date: Fri, 20 Apr 2007 22:47:24 +0200 [thread overview]
Message-ID: <20070420204724.GB5334@suse.cz> (raw)
In-Reply-To: <cb7bb73a0704200909h2f47e04cq87cb3dd91d7144f7@mail.gmail.com>
On Fri, Apr 20, 2007 at 06:09:55PM +0200, Giuseppe Bilotta wrote:
> On 4/20/07, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> >On 4/20/07, Giuseppe Bilotta <giuseppe.bilotta@gmail.com> wrote:
> >>
> >> Sorry, it seems I was wrong, it's not usbhid but usbmouse taking over.
> >> After a fresh plug (e.g. at bootup) I get the following:
> >>
> >
> >Well, the question is - why do you have usbmouse module on your system?
>
> Stock Debian kernel 2.6.18 comes with it.
>
> With my custom kernels I can probably skip compiling it at all, if you
> so suggest; should I blacklist it for the distro kernel? Or is there a
> chance that some random USB mouse plugged in would fail to function by
> doing so?
usbmouse and usbkbd are only intended for embedded systems where the
full usbhid doesn't fit and for testing purposes: Normal distros
shouldn't have them enabled.
--
Vojtech Pavlik
Director SuSE Labs
next prev parent reply other threads:[~2007-04-20 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 2:40 Giuseppe Bilotta
2007-04-20 7:06 ` Jiri Kosina
2007-04-20 8:26 ` Giuseppe Bilotta
2007-04-20 13:35 ` Jiri Kosina
2007-04-20 15:55 ` Giuseppe Bilotta
2007-04-20 16:01 ` Dmitry Torokhov
2007-04-20 16:09 ` Giuseppe Bilotta
2007-04-20 20:47 ` Vojtech Pavlik [this message]
2007-04-20 21:40 ` Giuseppe Bilotta
2007-04-20 23:56 ` Jiri Kosina
2007-04-21 0:38 ` Giuseppe Bilotta
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=20070420204724.GB5334@suse.cz \
--to=vojtech@suse.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=edouard.tisserant@wanadoo.fr \
--cc=giuseppe.bilotta@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®