From: Paul Collins <paul@burly.ondioline.org>
To: "Phil Endecott" <phil_tuhck_endecott@chezphil.org>
Cc: <linux-input@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <marcel@holtmann.org>,
<jkosina@suse.cz>
Subject: Re: [PATCH] [RESEND] fix HID quirks for aluminium apple wireless keyboards
Date: Fri, 13 Jun 2008 02:55:43 +1200 [thread overview]
Message-ID: <87prqmk8i8.fsf@burly.wgtn.ondioline.org> (raw)
In-Reply-To: <1213276636216@dmwebmail.dmwebmail.chezphil.org> (Phil Endecott's message of "Thu, 12 Jun 2008 14:17:16 +0100")
"Phil Endecott" <phil_tuhck_endecott@chezphil.org> writes:
> Did you see my messages about this a few weeks ago?
> http://thread.gmane.org/gmane.linux.kernel.input/4984
Alas, no! That would have been very helpful.
> I didn't post a patch because I believe that this stuff has all moved
> as a result of Jiri Slaby's patch "HID: move apple quirks" posted to
> linux-input on 2008-05-16. One of us should prepare a patch against
> the tree after that patch.
I'm happy to do this, although the only tree I track closely is Linus's.
> Do you know what happens if you have a USB bluetooth dongle with HID
> proxy mode? My assumption was that the vendor and product IDs from
> the keyboard would then appear to the kernel as USB IDs. If this is
> true, then you should keep the existing entries for these devices in
> the USB quirks tables. Does anyone know if HID proxy dongles actually
> do this? In any case, leaving the existing entries in the USB quirks
> table can't do any harm.
Hmm, no idea. Absent confirmation I guess I'll drop the USB HID changes
to be on the safe side.
> I wrote this up at http://chezphil.org/apple-alu-bluetooth-kb-linux/
> and I'll just post that URL again to help the search engines...
Nice writeup! Small correction: when the quirk is active, you can
generate forward delete by pressing Fn-backspace.
--
Paul Collins
Wellington, New Zealand
Dag vijandelijk luchtschip de huismeester is dood
next prev parent reply other threads:[~2008-06-12 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 12:26 [PATCH] " Paul Collins
2008-06-12 12:57 ` [PATCH] [RESEND] " Paul Collins
2008-06-12 13:17 ` Phil Endecott
2008-06-12 14:55 ` Paul Collins [this message]
2008-06-12 20:08 ` Marcel Holtmann
2008-06-14 8:03 ` Paul Collins
2008-06-14 12:22 ` Marcel Holtmann
2008-06-17 13:54 ` Jiri Kosina
2008-06-14 12:51 ` Phil Endecott
2008-06-18 10:19 ` Paul Collins
2008-06-18 10:47 ` Phil Endecott
2008-06-27 16:32 ` Jan Scholz
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=87prqmk8i8.fsf@burly.wgtn.ondioline.org \
--to=paul@burly.ondioline.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=phil_tuhck_endecott@chezphil.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®