From: "David Härdeman" <david@hardeman.nu>
To: Patrick Boettcher <pboettcher@kernellabs.com>
Cc: linux-media@vger.kernel.org
Subject: Re: dib0700 NEC scancode question
Date: Fri, 28 Mar 2014 00:43:57 +0100 [thread overview]
Message-ID: <20140327234357.GA22491@hardeman.nu> (raw)
In-Reply-To: <1464013.AGHbqAynQ4@lappi3>
On Thu, Mar 27, 2014 at 11:13:35PM +0100, Patrick Boettcher wrote:
>Hi David,
>
>On Thursday 27 March 2014 22:40:41 David Härdeman wrote:
>> On Thu, Mar 27, 2014 at 01:07:28PM +0100, David Härdeman wrote:
>> >Hi Patrick,
>> >
>> >a quick question regarding the dib0700 driver:
>>
>> >in ./media/usb/dvb-usb/dib0700_core.c the RC RX packet is defined as:
>> ...
>>
>> >The NEC protocol transmits in the order:
>> ...
>>
>> >Does the dib0700 fw really reorder the bytes, or could the order of
>> >not_system and system in struct dib0700_rc_response have been
>> >accidentally reversed?
>
>It feels like a hundred years I haven't work on that. I'm not sure whether
>this knowledge can still be retrieved as of today or not. I would lie if I
>told you that I look the archives... and I can't want to do that (lying and
>looking).
>
>However, I realize that your assumption might not be totally far-fetched. If
>you can find another IR-receiver just check whether the same remote control
>delivers swapped bytes or not (if I understood it correctly, that's your real
>question). Then you have you answer, haven't you?
If I had the hardware, yes :)
I don't, I just want to refactor some parts of the IR handling code
across several drivers, which is why I came across this...I guess there
are others who do have the hardware who will complain loudly if I try
changing it and my assumptions turn out to be incorrect though...
--
David Härdeman
prev parent reply other threads:[~2014-03-27 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 12:07 dib0700 NEC scancode question David Härdeman
2014-03-27 21:40 ` David Härdeman
2014-03-27 22:13 ` Patrick Boettcher
2014-03-27 23:43 ` David Härdeman [this message]
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=20140327234357.GA22491@hardeman.nu \
--to=david@hardeman.nu \
--cc=linux-media@vger.kernel.org \
--cc=pboettcher@kernellabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.