oschista@xxxxxxxxx wrote:
> Okay, finally got my replacement card after first buying a new
> Hauppauge PCI that turned out to be completely useless with the
> current status of the CX2388xx drivers and I've now got xawtv working
> on the Terratec Cinergy 400.
>
> Sadly there does not seem to be any support for the attached IR
> remote sensor, at least not in LIRC. I did manage to google up a
> patch that I think originated on this list, originally developed to
> support the FlyVideo 3K board but supposedly also known to work with
> the terratecs. The patch slid right in (with a little fuzz, using a
> slightly newer version of the SAA driver) and compiled with no
> problems, but I am unable to get any sort of data with irrecord/irw
> after insmodding the new saa/lirc drivers. Irrecord starts up fine,
> prompts me to hold down a button and then exits after 10 seconds
> complaining about no data, while irw did absolutely nothing. This
> leads me to believe that there's some minor problem with either my
> specific setup, or with the patched driver for lirc.
It sounds like it was probably my site you found.
(http://users.tpg.com.au/atko/gpf/ir/)
I've been quite busy recently and haven't had time to update the site.
The drivers that were posted didn't work, and should have been marked
experimental. After experimenting for a while with the Cinergy 400s I
was able to get them working in polling mode, but not using interrupts.
If you try the latest files then you might have better luck. It may not
work if you use any version of saa7134 other than 0.2.7. Let me know how
this goes.
HTH,
- David.
> After dmesg'ing I did notice a strange message when modprobing
> lirc_gpio; "lirc is not a directory" or something very similar, which
> is truly a strange thing for a kernel module to say..
>
>
> Anyway, it would be much appreciated if someone could give me a
> heads-up on when to expect a working lirc driver for this particular
> chipset; so far I've only been able to find this one patch to lirc,
> but there may be others that aren't in google's cache, if so please
> let me know.
>
> Now to question 2; I stumbled across a few references to using DMA to
> read audio from the tuner rather than using the (very noisy) looped
> mini-jack to mike in, and this sounds like a brilliant idea but how
> does it work? Does the SAA7134 driver create a new dsp device under
> /dev which can be used as any other OSS sound source, does this
> require special parameters at load time etc? I haven't seen any
> documentation on this but maybe I just haven't looked hard enough.
>
>
>
> -- video4linux-list mailing list Unsubscribe
> mailto:video4linux-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list
>
> .
>
