public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Sony PS3 sixaxis & bluez
Date: Tue, 27 Nov 2007 10:52:38 +0000	[thread overview]
Message-ID: <1196160759.10878.504.camel@cookie.hadess.net> (raw)
In-Reply-To: <1196152368.17196.23.camel@aeonflux>


On Tue, 2007-11-27 at 09:32 +0100, Marcel Holtmann wrote:
> Hi Bastien,
> 
> > > sixpair2.c has a couple of bugs:
> > > - country is wrong
> > 
> > Doesn't matter.
> > 
> > > - version is wrong
> > 
> > That was my mistake.
> > 
> > > - report is missing 4 bytes
> > 
> > Doesn't seem to matter. I think it might be hidd being broken...
> 
> can you extract the full HID report descriptor from SDP and simply put
> it statically into the code? I think that makes it easier.

The report descriptor says length is 148 (in lsusb and my code) and my
"truncated" version has 296 characters, so it look fine.

> > Attaching a new version of sixpair2.c that seems to work:
> > sudo ./sixpair2 --store-info <local bdaddr>
> > 
> > It needs to be compiled from the input/ subdir of bluez-utils, using the
> > command-line at the top of the file.
> 
> I would like to include this one into the CVS. Can you get me a version
> without GLib stuff? It is not really needed as I can tell. You only use
> it for option parsing.

You mentioned that already last time I sent the script. I'd really like
to be sure it works as expected before I trim it though, so if you or
Frederic could test it, I even have a udev rule, and some code to look
at to implement using hiddev instead lsusb so the device doesn't
disconnect on plugging it in.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-11-27 10:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24  0:37 [Bluez-devel] Sony PS3 sixaxis & bluez Frédéric Blain
2007-11-25  2:02 ` Bastien Nocera
2007-11-24 14:00   ` Frédéric Blain
2007-11-26  6:17     ` Marcel Holtmann
2007-11-26  6:15   ` Marcel Holtmann
2007-11-26 17:38     ` Bastien Nocera
2007-11-26 18:59       ` Bastien Nocera
2007-11-26 21:04         ` Frédéric Blain
2007-11-27  8:32         ` Marcel Holtmann
2007-11-27 10:52           ` Bastien Nocera [this message]
2007-11-27 11:08             ` Marcel Holtmann
2007-11-26  5:55 ` Marcel Holtmann

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=1196160759.10878.504.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --cc=bluez-devel@lists.sourceforge.net \
    /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