Re: [patch] IR-remote control support for SAA7134 based Cinergy 400

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Es schrieb Enrico Scholz:
> 
> Hello,
> 
> I have attached a patch which adds support for the IR-control of the
> SAA7134 based Terratec Cinergy 400 tv-card (and probably 600, too). It
> is relative to the saa7134-20030910 snapshot.
> 
> The first two hunks are just copied-and-pasted from the Flyvideo
> part.
> 
> About the third one (setting SAA7134_IRQ2), I am wondering how it works
> on the Flyvideo without this patch. In saa7134_core.c there will be done
> 
> | static int __devinit saa7134_initdev(...)
> | {
> |    saa7134_hwinit1();
> |       saa_writel(SAA7134_IRQ2, /* lots of bits */);
> |         /* unrelated stuff */
> |
> |    saa_writel(SAA7134_IRQ2, 0);
> 
> which means that the actions of SAA7134_IRQ2 in hwinit1() will be
> nullified. But since I do not have the datasheet, I might be wrong and
> the "unrelated stuff" is related somehow.
> 
> I am setting GPIO18A and GPIO18 bits only (one causes signaling of
> press-key, the other one of release-key events); but it works with '~0
> & ~..INTE_PE' also (setting PE causes interrupt-looping). The position
> where I set IRQ2 might be wrong too...
> 
> The cinergy_codes array is my personal and working setup; when there are
> better/standardized values, please tell me.
> 
> I have not followed the discussion about the input-event implementation
> of the v4l drivers completely, and the 'input_report_key()' hunk is just
> a quick hack to use the control here.  The '(gpio&0x40000)==0' part
> should be parameterized also to support different hardware.
> 

Hi Enrico,

your patch made it into the saa7134-20030922 snapshot. With this one I
get hard lockups on 2.6.0-test5 when I load all the driver modules and
then finally the saa7134. Can see that with a FV3K on a SiS 746fx and a
md9717 on a A7V133. Both kernel are preempt and acpi enabled and using
nvidia 4496. With the saa7134-20030910 both are fine, but yes it seems
there is no input coming through from the remote. For the freezes I have
absolutely nothing on debug info in the logs. Only "Linux video capture
interface: v1.00" and then nothing. Can you confirm, if it works or not
with your Cinergy 400?

Greetings

Hermann




[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux