[wellylug] SAA7134

[David Antliff]

On Tue, 20 Apr 2004, David Zanetti wrote:
> I did have some carrier detection problems with 0.2.8 or so, and hacked
> the code to stop probing the carrier and just use whatever I insmod'd it
> with (since we're always 5.5MHz here). But I did have to do that with
> 0.2.10, it seems to be fine for detecting the carrier okay. Certainly I
> haven't had the problem (and it gets a fair amount of work-out, given it's
> in my PVR)

Hmm, I wonder if it's related to received signal strength. I'll have to
try boosting the signal and see if it happens so often (if I change the
channel at every ad break, it happens one or two times an hour).

Can you send me a diff for your carrier hack please?

> I have had one problem with the remote: held keys are treated as seperate
> key press events, and lirc seems to ignore one of the bits of the event
> stucture and treats up and down events as two seperate presses. Or
> something.
>
> Are you using lirc, or treating as a keyboard under X? The latter I want
> to try out, but haven't had the inclination to break a mostly working
> system :)

I'm using the /dev/input interface with LIRC (modprobe evdev). I modprobe
'ir-common' with 'repeat=0'. It's been a while since I looked at this, but
if I remember correctly LIRC handles the up and down events separately -
just put the 'down' code in lircd.conf:

$ cat /etc/lircd.conf
begin remote

  name  flyvideo3000

  begin codes

    AIR_CATV            0x00010182
    VIDEO               0x00010189
    AUDIO               0x00010188
    POWER               0x00010074
    AV_SOURCE           0x000100b0
    FULLSCREEN          0x00010174
    STEREO              0x00010079
    MUTE                0x00010071
    VOLUME_UP           0x00010073
    VOLUME_DOWN         0x00010072
    CHANNEL_UP          0x00010192
    CHANNEL_DOWN        0x00010193
    RECALL              0x00010081
    ENTER               0x00010060
    1                   0x0001004f
    2                   0x00010050
    3                   0x00010051
    4                   0x0001004b
    5                   0x0001004c
    6                   0x0001004d
    7                   0x00010047
    8                   0x00010048
    9                   0x00010049
    0                   0x00010052

  end codes

end remote

When I was setting this all up, there was no support for the FlyVideo3000
remote in the driver, so I actually went through the entire process of
converting the GPIO codes into events within the driver. Unfortunately the
day I got it all working, someone else had submitted a patch that did
exactly the same thing. At least I got a good idea of how it all works
(which I've now largely forgotten).

It all works very well, controlling mplayer, xmms, xawtv, mozilla and
smartmenu (a great XML-based overlay menu). The only issue is that holding
a key down generates repeated events, but that's easy to live with unless
you're used to mashing down on worn out remotes...  ;)

-- 
David.