public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dave Young" <hidave.darkstar@gmail.com>
To: "Jiri Kosina" <jikos@jikos.cz>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
	bgsmith@bendcable.com,
	"BlueZ users" <bluez-users@lists.sourceforge.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Bluez-users] Lost connections - mouse and keyboard
Date: Fri, 30 Nov 2007 09:06:52 +0800	[thread overview]
Message-ID: <a8e1da0711291706h68d1d19ajc3819f8836cf51e8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711292141220.19853@twin.jikos.cz>

On Nov 30, 2007 4:43 AM, Jiri Kosina <jikos@jikos.cz> wrote:
> On Thu, 29 Nov 2007, Marcel Holtmann wrote:
>
> > > >Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
> [ ... ]
>
> > > Does bluetooth input devices have something to do with usbhid? I don't
> > > know, perhaps this is another problem in kernel.
> > in case you have a HID proxy dongle the usbhid driver can be involved. And
> > since this is hiddev, then it will be caused by the hid2hci program.
>
> Absolutely.
>
> This particular warning means, that someone (usually indeed hid2hci)
> passed usage through hiddev that was out of bounds, with respect to the
> device's report descriptor.

Is this behaviour the normal one? IMHO, userspace program should not
cause kernel warnings like this no mater what input from users.

>
> This usually means that hid2hci has chosen the wrong method to switch the
> modes. Unfortunately, it's not easy to implement always the switching
> properly, if we don't know the vendor-specific packet that has to be sent.
>
> --
> Jiri Kosina
>

  reply	other threads:[~2007-11-30  1:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 16:43 [Bluez-users] Lost connections - mouse and keyboard Brad Smith
2007-11-26  5:49 ` Marcel Holtmann
2007-11-29  3:03   ` Brad Smith
2007-11-29  8:06     ` Dave Young
2007-11-29 20:19       ` Marcel Holtmann
2007-11-29 20:43         ` Jiri Kosina
2007-11-30  1:06           ` Dave Young [this message]
2007-11-30  9:15             ` Jiri Kosina
2007-12-07 23:42             ` Didier Link
2007-12-08 10:25               ` Fabrice Ménard
2007-12-08 12:57                 ` Didier Link
2007-12-09 16:45                   ` Fabrice Ménard
2007-12-10 12:36                     ` Didier Link

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=a8e1da0711291706h68d1d19ajc3819f8836cf51e8@mail.gmail.com \
    --to=hidave.darkstar@gmail.com \
    --cc=bgsmith@bendcable.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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