From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 2/2] [media] firedtv: Port it to use rc_core
Date: Mon, 28 May 2012 16:14:32 +0200 [thread overview]
Message-ID: <20120528161432.50a6ca45@stein> (raw)
In-Reply-To: <20120528160132.2041d761@stein>
On May 28 Stefan Richter wrote:
> > + idev->phys = "/ir0"; /* FIXME */
>
> Something similar to drivers/media/dvb/dvb-usb/dvb-usb-remote.c::
>
> usb_make_path(d->udev, d->rc_phys, sizeof(d->rc_phys));
> strlcat(d->rc_phys, "/ir0", sizeof(d->rc_phys));
>
> should be implemented for this, right?
PS:
The current input device looks like this:
/sys/devices/pci0000:00/0000:00:02.0/0000:02:00.0/0000:03:01.0/0000:04:00.0/fw7/fw7.0/input/input8/device -> ../../../fw7.0
"fw7.0" is dev_name(dev) in fdtv_register_rc() or dev_name(fdtv->device)
in general in firedtv.
The last numeric name before fw7, i.e. 0000:04:00.0, is the name of the PCI
device of the FireWire controller. fw7 is the name of the FireDTV node;
fw7.0 is the name of the (only) unit within the FireDTV node which
implements the DVB receiver and IR receiver. What would be needed from
this?
FWIW, usb_make_path() results in "usb-%s-%s" % (usb_device.bus.bus_name,
usb_device.devpath).
--
Stefan Richter
-=====-===-- -=-= ===--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2012-05-28 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 13:14 [PATCH 1/2] [media] Add a keymap for FireDTV board Mauro Carvalho Chehab
2012-05-28 13:14 ` [PATCH 2/2] [media] firedtv: Port it to use rc_core Mauro Carvalho Chehab
2012-05-28 14:01 ` Stefan Richter
2012-05-28 14:09 ` Mauro Carvalho Chehab
2012-05-28 14:09 ` Mauro Carvalho Chehab
2012-05-28 14:14 ` Stefan Richter [this message]
2012-05-28 14:41 ` Mauro Carvalho Chehab
2012-05-28 13:29 ` [PATCH 1/2] [media] Add a keymap for FireDTV board Stefan Richter
2012-05-28 13:32 ` Mauro Carvalho Chehab
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=20120528161432.50a6ca45@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
/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.