From: Marcel Holtmann <marcel@holtmann.org>
To: Jiri Kosina <jikos@jikos.cz>
Cc: bluez-devel@lists.sourceforge.net,
linux-usb-devel@lists.sourceforge.net,
Simone Malacarne <s.malacarne@gmail.com>
Subject: Re: [Bluez-devel] [linux-usb-devel] dmesg warning on hid core
Date: Wed, 31 Oct 2007 17:33:06 +0100 [thread overview]
Message-ID: <1193848386.32459.62.camel@violet> (raw)
In-Reply-To: <Pine.LNX.4.64.0710261526020.18815@twin.jikos.cz>
Hi Jiri,
> the problem is that some userspace utility (I guess hid2hci from
> bluez-utils) issues hiddev ioctl() with inappropriate out-of-bounds value.
>
> As far as I know Logitech bluetooth keyboards are problematic, as Marcel
> doesn't have any specification for them, so switching between HID and HCI
> modes is reverse engineering and guessing.
there exists a patch that might make this work again. Didn't have the
time to properly test it, but it can't make it worse.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-10-31 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1193350427.11632.8.camel@simo-desktop>
2007-10-26 13:29 ` [linux-usb-devel] dmesg warning on hid core Jiri Kosina
2007-10-31 16:33 ` Marcel Holtmann [this message]
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=1193848386.32459.62.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jikos@jikos.cz \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=s.malacarne@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.