linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@jikos.cz>
To: Tino Keitel <tino.keitel@tikei.de>
Cc: Soeren Sonnenburg <kernel@nn7.de>, linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: HID blacklist for the Apple IR sensor
Date: Tue, 10 Jul 2007 22:29:55 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707102227020.31463@twin.jikos.cz> (raw)
In-Reply-To: <20070710182636.GA12522@dose.home.local>

On Tue, 10 Jul 2007, Tino Keitel wrote:

> in commit a417a21e10831bca695b4ba9c74f4ddf5a95ac06, the Apple IR sensor 
> was added to a blacklist so that no HID device is created anymore. 
> However, as of lirc 0.8.2, there is a lirc driver called "macmini" that 
> requires that HID device to work. There is also a driver that creates an 
> input device for the Apple IR sensor. It can be found in the 
> mactel-linux patches[1], but it is not in the kernel yet. I also don't 
> know how both sides behave if they are used concurrently.

Hi Tino,

so do I understand it correctly that there are two ways to use this device

- through lirc, which of course requires input device to be created by hid
- using appleir.patch, but this one is not yet upstream (what are the 
  obstacles?)

If it is so, and the device is not handled properly by any other in-tree 
driver, we should remove the ignore quirk.

> I think that the blacklist entry for USB_DEVICE_ID_APPLE_IR should be 
> removed at least as long as the appleir.patch is not part of the 
> mainline kernel.

Would you care to send me a patch with proper changelog and Signed-off-by 
line?

Thanks,

-- 
Jiri Kosina

  reply	other threads:[~2007-07-10 20:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 18:26 HID blacklist for the Apple IR sensor Tino Keitel
2007-07-10 20:29 ` Jiri Kosina [this message]
2007-07-11  6:00   ` Tino Keitel
2007-07-11  6:52     ` Tino Keitel
2007-07-11 14:48 ` Soeren Sonnenburg
2007-07-11 21:37   ` Tino Keitel
2007-07-12  4:40     ` Soeren Sonnenburg

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=Pine.LNX.4.64.0707102227020.31463@twin.jikos.cz \
    --to=jikos@jikos.cz \
    --cc=kernel@nn7.de \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=tino.keitel@tikei.de \
    /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).