All of lore.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] HID initiated connections and input service
Date: Mon, 18 Jun 2007 17:08:02 +0100	[thread overview]
Message-ID: <1182182882.3161.59.camel@cookie.hadess.net> (raw)
In-Reply-To: <1182021864.30934.5.camel@aeonflux.inter-touch.com>

On Sat, 2007-06-16 at 21:24 +0200, Marcel Holtmann wrote:
<snip>
> something like that and I have no idea how to do that for Logitech
> devices. I have strange code for pure CSR dongles, but it is so ugly
> that I am not going to share it. It is mostly CSR vendor stuff.

Shame. Is there any reason to run hid2hci by default then? As in,
shouldn't be opt-in, rather than opt-out?

> > > Getting the HID report descriptor over USB makes always the assumption
> > > that it is exactly the same as on Bluetooth. This should be checked.
> > 
> > How can I verify that?
> 
> I don't have code for that. Need to write a tool that does this.

My version of sixpair gets the report descriptor over usb, and stuff it
in a hci_connadd_req, but the point is moot for HCI proxy dongles, and I
don't know how to get the Bluetooth one for the sixaxis.

-- 
Bastien Nocera <hadess@hadess.net> 


-------------------------------------------------------------------------
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-06-18 16:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-15 16:44 [Bluez-devel] HID initiated connections and input service Bastien Nocera
2007-06-16  7:05 ` Marcel Holtmann
2007-06-16 16:35   ` Bastien Nocera
2007-06-16 19:35     ` Marcel Holtmann
2007-06-17 20:25       ` Bastien Nocera
2007-06-18 13:06         ` Bastien Nocera
2007-06-18 14:00           ` Pascal
2007-06-18 14:36             ` Bastien Nocera
2007-06-18 16:00               ` Bastien Nocera
2007-06-18 17:30                 ` Pascal
2007-06-18 19:23                   ` Bastien Nocera
2007-06-18 20:16                     ` Pascal
2007-06-18 22:40                       ` Bastien Nocera
2007-06-16  7:25 ` Marcel Holtmann
2007-06-16 16:44   ` Bastien Nocera
2007-06-16 19:24     ` Marcel Holtmann
2007-06-18 16:08       ` Bastien Nocera [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=1182182882.3161.59.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.