The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: add appleir USB driver
Date: Thu, 15 May 2008 06:20:44 +0000 (UTC)	[thread overview]
Message-ID: <g0gkns$f5g$1@ger.gmane.org> (raw)
In-Reply-To: 20080514234909.GA20084@kroah.com

On Wed, 14 May 2008 16:49:09 -0700, Greg KH wrote:

> On Thu, May 15, 2008 at 12:27:22AM +0100, Matthew Garrett wrote:
>> On Wed, May 14, 2008 at 03:15:19PM -0700, Greg KH wrote:
>> 
>> > +	{ USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_IRCONTROL,
>> > HID_QUIRK_IGNORE },
>> >  	{ USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_IRCONTROL4,
>> >  	HID_QUIRK_HIDDEV | HID_QUIRK_IGNORE_HIDINPUT },
>> 
>> Hm. How is the IRCONTROL4 handled? Is the protocol completely
>> different?
> 
> I know nothing about that device, sorry.  I think it is a totally
> different protocol from what I can tell looking at the code.
> 
>> > +	  Say Y here if you want to use a Apple USB remote control.  This 
+
>> >   device is traditionally inside an Intel Apple Mac Mini, but might +
>> >   show up in other places.
>> 
>> Minor nit, but it's supported on all the desktop Intel Macs and not
>> just the Mini.
> 
> Ah, didn't realize that, nice to know, we should have a wider userbase
> then :)

I'm not 100% sure whether Mac Pro desktops support the remote controls. 
Additionally saying USB remote makes it sound like a tethered device - 
perhaps it should be "USB IR remote" (although maybe that's acronym 
overload).

Do modern Mac Laptops (MacBook / MacBook Pro) support their IR remotes 
some other way?

-- 
Sitsofe | http://sucs.org/~sits/


  reply	other threads:[~2008-05-15  6:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 22:15 [PATCH] Input: add appleir USB driver Greg KH
2008-05-14 23:27 ` Matthew Garrett
2008-05-14 23:49   ` Greg KH
2008-05-15  6:20     ` Sitsofe Wheeler [this message]
2008-05-15  3:50 ` Dmitry Torokhov
2008-05-15 13:21 ` Tino Keitel
2008-05-15 13:45   ` Dmitry Torokhov
2008-05-15 17:49     ` Tino Keitel
2008-05-15 18:35       ` Dmitry Torokhov
2008-05-15 20:59         ` Tino Keitel
2008-05-16  7:19           ` Jiri Kosina
2008-05-16  7:26             ` Tino Keitel
2008-05-16 13:13           ` Dmitry Torokhov
2008-05-16 13:32             ` Tino Keitel
2008-05-16 13:53               ` Dmitry Torokhov
2008-05-16 14:07                 ` Tino Keitel
2008-05-15 18:40     ` Greg KH
2008-05-15 20:59       ` Tino Keitel
2008-05-15 21:11         ` Greg KH
2008-05-15 23:27           ` Tino Keitel
2008-05-16  2:32             ` Greg KH
2008-05-16  5:44               ` Tino Keitel
2008-05-15 13:40 ` Tino Keitel
2008-05-15 18:41   ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2008-05-16 21:46 Scott D. Davilla

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='g0gkns$f5g$1@ger.gmane.org' \
    --to=sitsofe@yahoo.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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