mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: "Jiri Kosina" <jkosina@suse.cz>,
	linux-kernel@vger.kernel.org, edouard.tisserant@wanadoo.fr,
	vojtech@ucw.cz
Subject: Re: Acecad USB Tablet: usbmouse takeover and odd motion
Date: Fri, 20 Apr 2007 18:09:55 +0200	[thread overview]
Message-ID: <cb7bb73a0704200909h2f47e04cq87cb3dd91d7144f7@mail.gmail.com> (raw)
In-Reply-To: <d120d5000704200901m44c9a3aei9ee0572c3b0a61ab@mail.gmail.com>

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?

(sorry for the double-send, forgot to reply to all)

-- 
Giuseppe "Oblomov" Bilotta

  reply	other threads:[~2007-04-20 16:09 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 [this message]
2007-04-20 20:47             ` Vojtech Pavlik
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=cb7bb73a0704200909h2f47e04cq87cb3dd91d7144f7@mail.gmail.com \
    --to=giuseppe.bilotta@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=edouard.tisserant@wanadoo.fr \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@ucw.cz \
    /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®