From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Brian Magnuson" Subject: Fwd: [PATCH 3/4] xpad.c - support for xbox360 wireless receiver Date: Sun, 3 Jun 2007 13:03:49 -0400 Message-ID: References: <20070603153723.GA14913@rcn.com> <20070603155330.GB14913@rcn.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_24608_2195546.1180890229693" Return-path: In-Reply-To: Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: linux-input@atrey.karlin.mff.cuni.cz, Dmitry Torokhov , Jan Kratochvil List-Id: linux-input@vger.kernel.org ------=_Part_24608_2195546.1180890229693 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Accidentally dropped the cc: ---------- Forwarded message ---------- From: Brian Magnuson Date: Jun 3, 2007 1:03 PM Subject: Re: [PATCH 3/4] xpad.c - support for xbox360 wireless receiver To: Jan Kratochvil On 6/3/07, Jan Kratochvil wrote: > > Hello, > > On Sun, 3 Jun 2007, Brian Magnuson wrote: > > * Brian Magnuson [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 ------=_Part_24608_2195546.1180890229693 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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


------=_Part_24608_2195546.1180890229693--