public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Pascal <pascal@pabr.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Increasing HIDP_DEFAULT_MTU ?
Date: Wed, 30 May 2007 00:12:04 +0200	[thread overview]
Message-ID: <f3i8fk$tfv$1@sea.gmane.org> (raw)
In-Reply-To: <1180411455.21432.114.camel@aeonflux.holtmann.net>

Marcel Holtmann wrote:
> Actually we are not really supporting segmentation by ourself. If I had
> one of the devices for testing, I might be able to fix that easily. Hint
> hint :)

It's that wireless joystick from Sony.  Be sure to ask for the
console that goes with it, it makes debugging much easier :-)

Note: when polled with HIDP_TRANS_GET_REPORT on the control channel,
it does use DATC (unlike what happens on the interrupt channel).
So maybe it would be a good platform for testing reassembly code.


> I fixed the input service now. We will see how this works out. In
> addition the 2.6.22-rc3 kernel contains a patch to fix a bug in the
> L2CAP config handling.

Thanks; the device now works out-of-the box with ps3-linux 2.6.22-rc3
and bluetoothd-service-input from bluez-utils-cvs (except I couldn't
figure how the new authorization framework works, so I renamed
/var/lib/bluetooth/*/hidd to /var/lib/bluetooth/*/input instead).

Pascal


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-05-29 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28 16:14 [Bluez-devel] Increasing HIDP_DEFAULT_MTU ? Pascal
2007-05-29  4:04 ` Marcel Holtmann
2007-05-29 22:12   ` Pascal [this message]
2007-05-30  7:31     ` Marcel Holtmann
2007-05-30 10:52       ` Pascal
2007-05-30 11:51         ` 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='f3i8fk$tfv$1@sea.gmane.org' \
    --to=pascal@pabr.org \
    --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