From: Bastien Nocera <hadess@hadess.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-bluetooth@vger.kernel.org,
linux-input <linux-input@vger.kernel.org>
Subject: Re: Apple Bluetooth devices: Battery level?
Date: Wed, 10 Jun 2009 15:25:43 +0100 [thread overview]
Message-ID: <1244643943.2690.76.camel@cookie.hadess.net> (raw)
In-Reply-To: <alpine.LNX.2.00.0906101023460.7457@wotan.suse.de>
On Wed, 2009-06-10 at 10:25 +0200, Jiri Kosina wrote:
> On Wed, 10 Jun 2009, Bastien Nocera wrote:
<snip>
> > - enabling CONFIG_HID_DEBUG requires rebuilding the kernel
>
> CONFIG_HID_DEBUG has 'default y' for quite some time, but the defconfigs
> haven't unfortunately been updated yet.
>
> > - most distributions build hid into the kernel
>
> hid.debug=2 on the kernel commandline option does the trick.
Or "echo 2 > /sys/modules/hid/parameters/debug" at run-time.
Seems CONFIG_HID_DEBUG is enabled by default in the builds I use as
well, so I'll quit complaining about that :)
Cheers
next prev parent reply other threads:[~2009-06-10 14:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 14:17 Apple Bluetooth devices: Battery level? Bastien Nocera
2009-06-07 15:52 ` Marcel Holtmann
2009-06-07 19:34 ` Iain Hibbert
2009-06-07 21:15 ` David Sainty
2009-06-08 13:33 ` Jiri Kosina
2009-06-09 23:22 ` Bastien Nocera
2009-06-10 7:03 ` Marcel Holtmann
2009-06-12 13:25 ` Jiri Kosina
2009-06-12 13:27 ` [PATCH 2/2] HID: use debugfs for events/reports dumping Jiri Kosina
2009-06-12 13:27 ` [PATCH 1/2] HID: use debugfs for report dumping descriptor Jiri Kosina
2009-06-10 7:14 ` Apple Bluetooth devices: Battery level? Dmitriy Geels
2009-06-10 7:24 ` Marcel Holtmann
2009-06-10 8:25 ` Bastien Nocera
2009-06-10 8:25 ` Jiri Kosina
2009-06-10 14:25 ` Bastien Nocera [this message]
2009-06-10 14:06 ` Bastien Nocera
2009-06-10 18:19 ` Iain Hibbert
2009-06-12 13:31 ` Jiri Kosina
2009-06-13 13:16 ` Iain Hibbert
2009-06-16 9:59 ` Jiri Kosina
2009-06-16 13:37 ` Marcel Holtmann
2010-02-12 15:41 ` Bastien Nocera
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=1244643943.2690.76.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=jkosina@suse.cz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).