All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Rankin <rankincj@yahoo.com>
To: v4l-dvb-maintainer@linuxtv.org
Cc: linux-dvb@linuxtv.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Register the bus, vendor and product IDs for dvb-usb remote device
Date: Sun, 21 Jan 2007 02:47:20 +0000 (GMT)	[thread overview]
Message-ID: <879469.96393.qm@web52901.mail.yahoo.com> (raw)

Hi,

This patch writes the USB vendor and product IDs into the /sys/class/input/inputX/id/ files, so
that udev can find them. A rule like this does the trick for me:

KERNEL="event*", SYSFS{../id/vendor}=="2040", SYSFS{../id/product}=="9301",
SYMLINK+="input/dvb-remote"

--- linux-2.6.18/drivers/media/dvb/dvb-usb/dvb-usb-remote.c.old 2007-01-21 02:43:11.000000000
+0000
+++ linux-2.6.18/drivers/media/dvb/dvb-usb/dvb-usb-remote.c     2007-01-21 02:39:02.000000000
+0000
@@ -107,6 +107,9 @@
        d->rc_input_dev->keycodemax = KEY_MAX;
        d->rc_input_dev->name = "IR-receiver inside an USB DVB receiver";
        d->rc_input_dev->phys = d->rc_phys;
+       d->rc_input_dev->id.bustype = BUS_USB;
+       d->rc_input_dev->id.vendor = d->udev->descriptor.idVendor;
+       d->rc_input_dev->id.product = d->udev->descriptor.idProduct;

        /* set the bits for the keys */
        deb_rc("key map size: %d\n", d->props.rc_key_map_size);

Cheers,
Chris



		
___________________________________________________________ 
What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship. 
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk 

             reply	other threads:[~2007-01-21  2:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21  2:47 Chris Rankin [this message]
2007-01-21 19:12 ` [v4l-dvb-maintainer] [PATCH] Register the bus, vendor and product IDs for dvb-usb remote device Michael Krufky

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=879469.96393.qm@web52901.mail.yahoo.com \
    --to=rankincj@yahoo.com \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=v4l-dvb-maintainer@linuxtv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.