From: "David Härdeman" <david@hardeman.nu>
To: "David Cimbůrek" <david.cimburek@gmail.com>
Cc: Luis de Bethencourt <luis@debethencourt.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Antti Palosaari <crope@iki.fi>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] media: Pinnacle 73e infrared control stopped working since kernel 3.17
Date: Tue, 24 Feb 2015 11:15:53 +0100 [thread overview]
Message-ID: <67d0fa2066c017a66ad785dc90447d08@hardeman.nu> (raw)
In-Reply-To: <CAEmZozMP1FFN-Y1d+7Mopy1Y9_2FjX2tJmmCne_Gpa2+_yFg0g@mail.gmail.com>
On 2015-02-24 11:08, David Cimbůrek wrote:
>>> Hi,
>>>
>>> I looked at this again and I still don't see why the order is
>>> important.
>>> Plus the code looks like it does what it should be doing when using
>>> RC_SCANCODE_NEC, RC_SCANCODE_NEC32, RC_SCANCODE_NECX and
>>> RC_SCANCODE_RC5.
>>>
>>> Unfortunately I can't review this if I am not sure about it, and I
>>> don't
>>> have the device to be able to properly test your patch.
>>>
>>> Hopefully your print of the scancodes helps.
>>>
>>> Luis
>>
>> Hi,
>>
>> unfortunately I don't understand the code very well but it really
>> works like I described.
>>
>> I tried to get debugging output from the
>> dib0700_core.c:dib0700_rc_urb_completion() function:
>>
>> deb_data("IR ID = %02X state = %02X System = %02X %02X Cmd = %02X %02X
>> (len %d)\n",
>> poll_reply->report_id, poll_reply->data_state,
>> poll_reply->system, poll_reply->not_system,
>> poll_reply->data, poll_reply->not_data,
>> purb->actual_length);
>>
>> And the output after my patch (and before commit
>> af3a4a9bbeb00df3e42e77240b4cdac5479812f9!) looks like this:
>>
>> [ 282.842557] IR ID = 01 state = 01 System = 07 00 Cmd = 0F F0 (len
>> 6)
>> [ 282.955810] IR ID = 01 state = 02 System = 07 00 Cmd = 0F F0 (len
>> 6)
>>
>> But without my patch the output looks after commit
>> af3a4a9bbeb00df3e42e77240b4cdac5479812f9 like this:
>>
>> [ 186.302282] IR ID = 01 state = 01 System = 00 07 Cmd = 0F F0 (len
>> 6)
>> [ 186.415660] IR ID = 01 state = 02 System = 00 07 Cmd = 0F F0 (len
>> 6)
>>
>> You can see that the content of "system" and "not_system" is really
>> switched...
>>
>> Regards,
>> David
>
> Is there anything more I can do? Shall I provide some more debugging
> outputs? There is no response nearly for two weeks...
Sorry, I'm just really busy.
The output that you gave (the actual scancodes that are generated) is
what I was looking for, not the keymap. If I remember correctly my patch
wasn't supposed to change the generated scancodes (or the keymap would
have to be changed as well).
The question is whether the right thing to do is to change back the
scancode calculation or to update the keymap. I'll try to have a closer
look as soon as possible (which might take a few days more, sorry).
Re,
David
next prev parent reply other threads:[~2015-02-24 10:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 10:38 [PATCH] media: Pinnacle 73e infrared control stopped working since kernel 3.17 David Cimbůrek
2015-02-10 10:45 ` Antti Palosaari
2015-02-11 13:24 ` David Härdeman
2015-02-11 13:53 ` David Cimbůrek
2015-02-11 14:40 ` David Härdeman
2015-02-11 16:41 ` David Cimbůrek
2015-02-12 11:50 ` Mauro Carvalho Chehab
2015-02-12 17:34 ` David Cimbůrek
2015-02-12 21:57 ` Luis de Bethencourt
2015-02-13 19:58 ` David Cimbůrek
2015-02-24 10:08 ` David Cimbůrek
2015-02-24 10:15 ` David Härdeman [this message]
2015-02-24 13:44 ` Mauro Carvalho Chehab
2015-02-24 13:47 ` David Härdeman
2015-02-12 0:10 ` Luis de Bethencourt
2015-02-12 7:15 ` David Cimbůrek
2015-02-12 11:11 ` Luis de Bethencourt
-- strict thread matches above, loose matches on Subject: below --
2014-12-20 13:36 David Cimbůrek
2015-01-07 12:51 ` David Cimbůrek
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=67d0fa2066c017a66ad785dc90447d08@hardeman.nu \
--to=david@hardeman.nu \
--cc=crope@iki.fi \
--cc=david.cimburek@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=luis@debethencourt.com \
--cc=mchehab@osg.samsung.com \
/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