public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Daro <ghost-rider@aster.pl>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: Jean Delvare <khali@linux-fr.org>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	LMML <linux-media@vger.kernel.org>,
	Roman Kellner <muzungu@gmx.net>
Subject: Re: [PATCH] saa7134: Fix IR support of some ASUS TV-FM 7135   	variants
Date: Wed, 10 Feb 2010 17:38:18 +0100	[thread overview]
Message-ID: <4B72E0FA.5000303@aster.pl> (raw)
In-Reply-To: <1265153571.3194.14.camel@pc07.localdom.local>

W dniu 03.02.2010 00:32, hermann pitton pisze:
> Hi Jean, Mauro and all,
>
> Am Dienstag, den 02.02.2010, 08:54 +0100 schrieb Jean Delvare:
>    
>> Hi Hermann,
>>
>> On Tue, 02 Feb 2010 02:47:53 +0100, hermann pitton wrote:
>>      
>>> Hi Jean,
>>>
>>> Am Montag, den 01.02.2010, 10:56 +0100 schrieb Jean Delvare:
>>>        
>>>> Hi Hermann,
>>>>
>>>> On Mon, 01 Feb 2010 02:16:35 +0100, hermann pitton wrote:
>>>>          
>>>>> For now, I only faked a P7131 Dual with a broken IR receiver on a 2.6.29
>>>>> with recent, you can see that gpio 0x40000 doesn't go high, but your
>>>>> patch should enable the remote on that P7131 analog only.
>>>>>            
>>>> I'm not sure why you had to fake anything? What I'd like to know is
>>>> simply if my first patch had any negative effect on other cards.
>>>>          
>>> because I simply don't have that Asus My Cinema analog only in question.
>>>
>>> To recap, you previously announced a patch, tested by Daro, claiming to
>>> get the remote up under auto detection for that device and I told you
>>> having some doubts on it.
>>>        
>> My first patch was not actually tested by Daro. What he tested was
>> loading the driver with card=146. At first I thought it was equivalent,
>> but since then I have realized it wasn't. That's the reason why the
>> "Tested-by:" was turned into a mere "Cc:" on my second and third
>> patches.
>>
>>      
>>> Mauro prefers to have a fix for that single card in need for now.
>>>
>>> Since nobody else cares, "For now", see above, I can confirm that your
>>> last patch for that single device should work to get IR up with auto
>>> detection in delay after we change the card such late with eeprom
>>> detection.
>>>
>>> The meaning of that byte in use here is unknown to me, we should avoid
>>> such as much we can! It can turn out to be only some pseudo service.
>>>
>>> If your call for testers on your previous attempt, really reaches some
>>> for some reason, I'm with you, but for now I have to keep the car
>>> operable within all such snow.
>>>        
>> That I understand. What I don't understand is: if you have a
>> SAA7134-based card, why don't you test my second patch (the one moving
>> the call to saa7134_input_init1 to saa7134_hwinit2) on it, without
>> faking anything? This would be a first, useful data point.
>>
>>      
> sorry, the snow fall did not stop and we will need trucks next day to
> get it out of town. No place left.
>
> I did not reread any single line of code until now, but told you that
> Roman has tested a equivalent patch on his P7131_ANALOG already and I
> can confirm that it also had no side effects on a FlyVideo3000 card=2.
>
> For now, I would at least need some time to see, if input_init can be
> decoupled from all other hardware init, what you seem to suggest, and
> looking closer to Mauro's concerns.
>
> Thought you are asking for some test with a i2c remote next to confirm
> your analysis there. No such card in any machine currently, but can be
> done.
>
> Cheers,
> Hermann
>
>
>
>
>    
Hi All,

If some tests on my machine could be helpfull just let me know.

Best regards
Darek

  reply	other threads:[~2010-02-10 16:38 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 11:02 [PATCH] saa7134: Fix IR support of some ASUS TV-FM 7135 variants Jean Delvare
2010-01-29 15:40 ` Mauro Carvalho Chehab
2010-01-30  0:47   ` hermann pitton
2010-01-30 10:56     ` Jean Delvare
2010-02-01  1:16       ` hermann pitton
2010-02-01  9:56         ` Jean Delvare
2010-02-02  1:47           ` hermann pitton
2010-02-02  7:54             ` Jean Delvare
2010-02-02 11:50               ` Mauro Carvalho Chehab
2010-02-10 18:09                 ` Jean Delvare
2010-02-10 18:40                   ` Mauro Carvalho Chehab
2010-02-10 19:36                     ` Jean Delvare
2010-02-11  0:58                       ` hermann pitton
2010-02-15  5:31                         ` hermann pitton
2010-02-20  3:07                           ` hermann pitton
2010-02-25 13:12                             ` Jean Delvare
2010-02-25 21:50                               ` hermann pitton
2010-02-02 23:32               ` hermann pitton
2010-02-10 16:38                 ` Daro [this message]
2010-02-10 17:00                   ` Jean Delvare
2010-02-02 19:09       ` Mauro Carvalho Chehab
2010-02-10 17:01         ` Jean Delvare
     [not found] <E1Nl2po-000877-Di@services.gcu-squad.org>
2010-03-12  9:38 ` Jean Delvare
2010-03-14  2:38   ` Daro
2010-03-14  5:08     ` hermann pitton
2010-03-14  8:26     ` Jean Delvare
2010-03-14 19:34       ` Daro
2010-03-14 20:48         ` Jean Delvare

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=4B72E0FA.5000303@aster.pl \
    --to=ghost-rider@aster.pl \
    --cc=hermann-pitton@arcor.de \
    --cc=khali@linux-fr.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=muzungu@gmx.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox