From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Richard Zidlicky <rz@linux-m68k.org>
Cc: linux-media@vger.kernel.org, udia@siano-ms.com,
Michael Krufky <mkrufky@kernellabs.com>
Subject: Re: [PATCH 3/6] V4L/DVB: smsusb: enable IR port for Hauppauge WinTV MiniStick
Date: Tue, 03 Aug 2010 10:32:15 -0300 [thread overview]
Message-ID: <4C581A5F.5020403@redhat.com> (raw)
In-Reply-To: <20100803130552.GA9954@linux-m68k.org>
Em 03-08-2010 10:05, Richard Zidlicky escreveu:
> Hi,
>
>> Em 02-08-2010 04:27, Richard Zidlicky escreveu:
>>> On Sun, Aug 01, 2010 at 05:17:18PM -0300, Mauro Carvalho Chehab wrote:
>>>> Add the proper gpio port for WinTV MiniStick, with the information provided
>>>> by Michael.
>>>>
>>>> Thanks-to: Michael Krufky <mkrufky@kernellabs.com>
>>>> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
>>>>
>>>> diff --git a/drivers/media/dvb/siano/sms-cards.c b/drivers/media/dvb/siano/sms-cards.c
>>>> index cff77e2..dcde606 100644
>>>> --- a/drivers/media/dvb/siano/sms-cards.c
>>>> +++ b/drivers/media/dvb/siano/sms-cards.c
>>>> @@ -67,6 +67,7 @@ static struct sms_board sms_boards[] = {
>>>> .board_cfg.leds_power = 26,
>>>> .board_cfg.led0 = 27,
>>>> .board_cfg.led1 = 28,
>>>> + .board_cfg.ir = 9,
>>> ^^^^
>>>
>>> are you sure about this?
>>>
>>> I am using the value of 4 for the ir port and it definitely works.. confused.
>>
>> I got this from a reliable source, and that worked perfectly my with a Model 55009
>> LF Rev B1F7. What's the model of your device?
>
> mine says
>
> Aug 3 14:58:10 localhost kernel: [149778.591862] usb 5-5: New USB device found, idVendor=2040, idProduct=5500
> Aug 3 14:58:10 localhost kernel: [149778.591865] usb 5-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> Aug 3 14:58:10 localhost kernel: [149778.591868] usb 5-5: Product: WinTV MiniStick
> Aug 3 14:58:10 localhost kernel: [149778.591870] usb 5-5: Manufacturer: Hauppauge Computer Works
> Aug 3 14:58:10 localhost kernel: [149778.591872] usb 5-5: SerialNumber: f069684c
>
> not sure what else to report.
The model number is on a label at the back of the stick (at least, mine have it).
> I will compile and try a new kernel tonight.
>
> Wondering - is this
> http://git.sliepen.org/browse?p=inputlirc
> usefull to feed the input events to LIRC when trying the new driver with a slightly older
> LIRC based distro?
The in-kernel lirc support need a new version of LIRC since a few ioctls numbers were changed,
to avoid needing to write a code in kernel to handle compatibility between 32 and 64 bit kernels.
If you're running a 32 bits kernel, it may work.
Btw, you don't need to use lirc if all you want is to replace the IR keycodes. You can use, instead,
the ir-keycode program, available at http://git.linuxtv.org/v4l-utils.git. There are several keycode
tables already mapped there. Of course, lirc offers some extra features.
Cheers,
Mauro.
next prev parent reply other threads:[~2010-08-03 13:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1280693675.git.mchehab@redhat.com>
2010-08-01 20:17 ` [PATCH 1/6] V4L/DVB: dib0700: properly implement IR change_protocol Mauro Carvalho Chehab
2010-08-01 20:17 ` [PATCH 2/6] V4L/DVB: dib0700: Fix RC protocol logic to properly handle NEC/NECx and RC-5 Mauro Carvalho Chehab
2010-08-01 20:17 ` [PATCH 3/6] V4L/DVB: smsusb: enable IR port for Hauppauge WinTV MiniStick Mauro Carvalho Chehab
2010-08-02 7:27 ` Richard Zidlicky
2010-08-03 2:01 ` Mauro Carvalho Chehab
2010-08-03 13:05 ` Richard Zidlicky
2010-08-03 13:32 ` Mauro Carvalho Chehab [this message]
2010-08-03 14:21 ` Jarod Wilson
2010-08-03 14:46 ` Richard Zidlicky
2010-08-03 15:23 ` Mauro Carvalho Chehab
2010-08-04 7:30 ` Richard Zidlicky
2010-08-01 20:21 ` [PATCH 4/6] V4L/DVB: standardize names at rc-dib0700 tables Mauro Carvalho Chehab
2010-08-01 20:21 ` [PATCH 5/6] V4L/DVB: sms: properly initialize IR phys and IR name Mauro Carvalho Chehab
2010-08-01 20:21 ` [PATCH 6/6] V4L/DVB: sms: Convert IR support to use the Remote Controller core 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=4C581A5F.5020403@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mkrufky@kernellabs.com \
--cc=rz@linux-m68k.org \
--cc=udia@siano-ms.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.