linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chaogui Zhang <czhang@marywood.edu>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] TiVo USB IR Dongle support
Date: Wed, 13 Jan 2010 20:28:51 -0500	[thread overview]
Message-ID: <2992d57b1001131728l767517bcg851ebd4291b71078@mail.gmail.com> (raw)
In-Reply-To: <2992d57b1001131722p686108acn4f51e94609047c97@mail.gmail.com>

On Wed, Jan 13, 2010 at 8:22 PM, Chaogui Zhang <czhang@marywood.edu> wrote:
> On Wed, Jan 13, 2010 at 2:53 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
>> Hi Chaogui,
>>
>> I was looking at the driver again and I have some concerns with the
>> foolowing fragment:
>>
>> On Tue, Dec 15, 2009 at 07:53:57PM -0500, Chaogui Zhang wrote:
>>> +
>>> +     /* The lower 5 bits of the first byte of each packet indicates the size
>>> +      * of the transferred buffer, not including the first byte itself.
>>> +      */
>>> +
>>> +     length = (remote->in_buffer[0]) & 0x1f;
>>> +     for (i = 0; i <= length; i++)
>>> +             snprintf(codes + i * 3, 4, "%02x ", remote->in_buffer[i]);
>>> +
>>> +     /* 0x80 at the end of a regular packet or in a separate packet
>>> +        indicates key release */
>>> +
>>> +     if (i < TIVOIR_RECV_SIZE && remote->in_buffer[i] == 0x80)
>>> +             snprintf(codes + i * 3, 4, "%02x ", remote->in_buffer[i]);
>>> +
>>
>> So does this mean that 0x80 indicating release is not included in the
>> size of the received packet.
>>
>
> Hi, Dimitry,
>
> Sorry that you are getting this message twice. I accidentally dropped
> the list from the cc again.
>
> You are correct and the 0x80 signals the end of the packet and
>

To finish my sentence: ... and it is NOT included in the packet size.

I don't know what is going on with me today. Silly things like this
keep happening.

My sincere apologies.

--

Chaogui Zhang
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-01-14  1:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 21:45 [PATCH] TiVo USB IR Dongle support Chaogui Zhang
2009-12-12 19:01 ` Chaogui Zhang
2009-12-12 23:32   ` Dmitry Torokhov
2009-12-14 22:00     ` Chaogui Zhang
2009-12-14 22:28       ` Dmitry Torokhov
2009-12-16  0:53         ` Chaogui Zhang
2010-01-13  7:53           ` Dmitry Torokhov
2010-01-13 14:25             ` Jarod Wilson
2010-01-14  1:22             ` Chaogui Zhang
2010-01-14  1:28               ` Chaogui Zhang [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=2992d57b1001131728l767517bcg851ebd4291b71078@mail.gmail.com \
    --to=czhang@marywood.edu \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).