From: Jorden Mauro <jrm8005@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jan Scholz <Scholz@fias.uni-frankfurt.de>,
"jirislaby@gmail.com" <jirislaby@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tobias Mueller <Tobias_Mueller@twam.info>
Subject: Re: [PATCH 0/1] HID: hid_apple is not used for apple alu wireless keyboards
Date: Fri, 28 Nov 2008 09:48:20 -0500 [thread overview]
Message-ID: <D0C5E070-309C-47A9-B0D3-530E48B475FD@gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0811281509450.19853@jikos.suse.cz>
On Nov 28, 2008, at 9:11, Jiri Kosina <jkosina@suse.cz> wrote:
> On Wed, 26 Nov 2008, Jan Scholz wrote:
>
>> While parsing 'hid_blacklist' in hid-core.c my apple alu wireless
>> keyboard is not found. This happens because in the blacklist it
>> is declared with HID_USB_DEVICE although the keyboards are really
>> bluetooth devices. The same holds for 'apple_devices' list in
>> hid-apple.c
>> This patch fixes it by changing HID_USB_DEVICE to
>> HID_BLUETOOTH_DEVICE in those two lists.
>
> OK, I have done some googling in addition to what Tobias and J.R. have
> written, and your patch seems to be indeed the correct thing to do for
> these three product IDs. So I have queued it in my tree for 2.6.28,
> thanks.
Jiri,
I can test this patch hopefully next week on the wireless keyboard.
I'll let you know of any issues.
Thanks,
J.R.
>
>
> --
> Jiri Kosina
> SUSE Labs
prev parent reply other threads:[~2008-11-28 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 14:33 Jan Scholz
2008-11-26 14:33 ` [PATCH 1/1] HID: Apple alu wireless keyboards are bluetooth devices Jan Scholz
2008-11-26 14:54 ` Jiri Kosina
2008-11-26 15:17 ` Jan Scholz
2008-11-26 15:33 ` Jiri Kosina
2008-11-26 16:35 ` J.R. Mauro
2008-11-26 21:06 ` Tobias Müller
2008-11-27 0:57 ` several messages Jiri Kosina
2008-11-28 14:11 ` [PATCH 0/1] HID: hid_apple is not used for apple alu wireless keyboards Jiri Kosina
2008-11-28 14:48 ` Jorden Mauro [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=D0C5E070-309C-47A9-B0D3-530E48B475FD@gmail.com \
--to=jrm8005@gmail.com \
--cc=Scholz@fias.uni-frankfurt.de \
--cc=Tobias_Mueller@twam.info \
--cc=jirislaby@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®