public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org,
	linux-usb-users@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.5-rc3-mm4
Date: Thu, 1 Apr 2004 07:16:18 -0800	[thread overview]
Message-ID: <20040401151618.GA25910@kroah.com> (raw)
In-Reply-To: <200404011402.44875@WOLK>

On Thu, Apr 01, 2004 at 02:02:44PM +0200, Marc-Christian Petersen wrote:
> On Thursday 01 April 2004 12:05, Andrew Morton wrote:
> 
> Hi 
> 
> >  bk-usb.patch
> 
> hmm, did something changed in handling USB mice? starting with 2.6.5-rc3-mm1 
> and the included bk-usb.patch my USB mouse won't work anymore. Using 
> bk-usb.patch from 2.6.5-rc2-mm5 in 2.6.5-rc3-mm4 all works fine for me.
> 
> Attached are 2 files, one from 2.6.5-rc2-mm5 bk-usb and the other one is 
> 2.6.5-rc3-mm4 bk-usb. Seems the latter one does not proper init hid though 
> the module is loaded.

The hid.ko module was renamed to usbhid.ko.  Are you sure that you are
still loading the proper driver?  I don't see the messages:

> Apr  1 13:52:20 codeman kernel: usbcore: registered new driver hiddev
> Apr  1 13:52:20 codeman kernel: usbcore: registered new driver hid
> Apr  1 13:52:20 codeman kernel: drivers/usb/input/hid-core.c: v2.0:USB HID core driver

In your second set of messages.

thanks,

greg k-h

  reply	other threads:[~2004-04-01 15:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 10:05 2.6.5-rc3-mm4 Andrew Morton
2004-04-01 12:02 ` 2.6.5-rc3-mm4 Marc-Christian Petersen
2004-04-01 15:16   ` Greg KH [this message]
2004-04-01 15:32     ` 2.6.5-rc3-mm4 Marc-Christian Petersen
2004-04-01 14:12 ` 2.6.5-rc3-mm4 Norberto Bensa
2004-04-02  1:35   ` 2.6.5-rc3-mm4 Joshua Kwan
2004-04-02  2:09     ` 2.6.5-rc3-mm4 Norberto Bensa
2004-04-01 23:12 ` 2.6.5-rc3-mm4 (compile stats) John Cherry
2004-04-02 19:04 ` 2.6.5-rc3-mm4 markw
2004-04-02 19:56   ` 2.6.5-rc3-mm4 Andrew Morton
2004-04-02 20:46     ` 2.6.5-rc3-mm4 markw
2004-04-02 23:43     ` 2.6.5-rc3-mm4 Nick Piggin
2004-04-03  0:10       ` 2.6.5-rc3-mm4 Mark Wong
2004-04-03  0:12         ` 2.6.5-rc3-mm4 Nick Piggin
2004-04-06 15:20           ` 2.6.5-rc3-mm4 markw
  -- strict thread matches above, loose matches on Subject: below --
2004-04-02  3:09 2.6.5-rc3-mm4 Sid Boyce
2004-04-03 11:08 ` 2.6.5-rc3-mm4 Sid Boyce
2004-04-04  1:15 2.6.5-rc3-mm4 Paul Blazejowski
2004-04-04 23:34 ` 2.6.5-rc3-mm4 Trond Myklebust
2004-04-05  1:25   ` 2.6.5-rc3-mm4 Paul Blazejowski

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=20040401151618.GA25910@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-users@lists.sourceforge.net \
    --cc=m.c.p@wolk-project.de \
    /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