Rob Shortt ([EMAIL PROTECTED]) wrote:
>Ian Campbell wrote:
>> See also my post to l-k:
>> http://marc.theaimsgroup.com/?l=linux-kernel&m=112539129023088&w=2
>> I didn't get any reply, I'll probably resend before long.
>
> Ian, did you get a reply yet? Thanks for the fix guys, I just started
> gett
Hi guys,
Ian Campbell wrote:
On Thu, 2005-09-01 at 16:18 +0200, Gert wrote:
I use my PVR350 remote as follows:
# modprobe ivtv # version 0.3.7k
# modprobe ir-kbd-i2c # remote is accessible via /dev/input/event1
# input-kbd -f keymap 1 # load keymap (see attachment) for the remote
That way, I d
On Thu, 2005-09-01 at 16:18 +0200, Gert wrote:
> I use my PVR350 remote as follows:
> # modprobe ivtv # version 0.3.7k
> # modprobe ir-kbd-i2c # remote is accessible via /dev/input/event1
> # input-kbd -f keymap 1 # load keymap (see attachment) for the remote
> That way, I don't need LIRC to contro
Ivtv only uses the evdev driver. We have nothing to do with it's development,
maintenance, or bugs. You should email whoever submitted that patch or whoever
maintains that driver these days.
--Brian
Gert wrote:
I use my PVR350 remote as follows:
# modprobe ivtv # version 0.3.7k
# modprobe ir-
I use my PVR350 remote as follows:
# modprobe ivtv # version 0.3.7k
# modprobe ir-kbd-i2c # remote is accessible via /dev/input/event1
# input-kbd -f keymap 1 # load keymap (see attachment) for the remote
That way, I don't need LIRC to control MythTV since the remote produces
keyboard-like events.
