Linux Input/HID development
 help / color / mirror / Atom feed
From: "Brian Magnuson" <bdmagnuson@gmail.com>
To: linux-input@atrey.karlin.mff.cuni.cz,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Jan Kratochvil <honza@jikos.cz>
Subject: Fwd: [PATCH 3/4] xpad.c - support for xbox360 wireless receiver
Date: Sun, 3 Jun 2007 13:03:49 -0400	[thread overview]
Message-ID: <bafd4ab0706031003w6fd262dbs57a3c874904fccb7@mail.gmail.com> (raw)
In-Reply-To: <bafd4ab0706031003n23c30e1ah3fdf82bf0e586aa8@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]

Accidentally dropped the cc:

---------- Forwarded message ----------
From: Brian Magnuson <bdmagnuson@gmail.com>
Date: Jun 3, 2007 1:03 PM
Subject: Re: [PATCH 3/4] xpad.c - support for xbox360 wireless receiver
To: Jan Kratochvil <honza@jikos.cz>


On 6/3/07, Jan Kratochvil <honza@jikos.cz> wrote:
>
> Hello,
>
> On Sun, 3 Jun 2007, Brian Magnuson wrote:
> > * Brian Magnuson <bdmagnuson@gmail.com> [2007-06-03 11:37]:
> >> I can tell you without even testing that it's not going to work.  The
> data
> >> length returned by the wireless controller is alway 29 bytes, but as
> far
> >> as I can tell there is no field that indicates that length.
> >
> > Ok, looks like I was a bit hasty.  Looking at the data again there does
> > appear to be a length field in the returned data however.
> >
> > 1) It's 19 bytes rather than 20.  This is a internel data format length
> > though.  The USB data returned is still 29 bytes long.
> > 2) You still need to apply to four byte shift for it to be in the
> "right"
> > place.
>
> Oic. I somehow missed the shift. Sorry for that. So in your process packet
> function you got 19 on position 5?


Yup.

And what is on last five bytes? I
> suppose that the rest is the same as in wired controller.


I'm not someplace where I can check for sure right now, but it didn't seem
to
be useful data.  Might have even been all 0s.  I'll be able to check on that
later tonight.

-Brian

[-- Attachment #2: Type: text/html, Size: 2439 bytes --]

  parent reply	other threads:[~2007-06-03 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 14:10 [PATCH 3/4] xpad.c - support for xbox360 wireless receiver Jan Kratochvil
2007-06-03 15:37 ` Brian Magnuson
2007-06-03 15:53   ` Brian Magnuson
2007-06-03 16:23     ` Jan Kratochvil
     [not found]       ` <bafd4ab0706031003n23c30e1ah3fdf82bf0e586aa8@mail.gmail.com>
2007-06-03 17:03         ` Brian Magnuson [this message]
2007-06-03 17:54           ` Fwd: " Jan Kratochvil

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=bafd4ab0706031003w6fd262dbs57a3c874904fccb7@mail.gmail.com \
    --to=bdmagnuson@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=honza@jikos.cz \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    /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