All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Wiimote pairing?
Date: Sat, 05 Dec 2009 15:50:58 +0100	[thread overview]
Message-ID: <1260024658.3041.14.camel@violet> (raw)
In-Reply-To: <1260021437.3311.1899.camel@localhost.localdomain>

Hi Bastien,

> I was under the impression that the Wiimote simply didn't use a PIN
> code, but it seems there's a way to pair it and associate it with a
> particular host by doing:
> http://wiibrew.org/wiki/Wiimote#Sync_Button
> 
> I looked through my dongles, and couldn't find one that would allow me
> to pass the modified host address as a PIN code as they all have "00" as
> part of the address.
> 
> bluetoothd uses strings everywhere for PIN code handling. It would be
> possible to change the RequestPinCode to also allow:
> {string,len} RequestPinCode(object device)
> without modifying the current behaviour.

that is no really how D-Bus would handle strings. From a D-Bus point of
view, the only way would be using a Byte array.

Potentially we could allow implementing a passkey agent as a plugin and
then you could implement special handling via a plugin. Problem then
again is how to identify that it is a Wiimote. Or did they actually
added a PnP SDP record to it. It has been so long that I hacked on these
devices.

Regards

Marcel



  reply	other threads:[~2009-12-05 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05 13:57 Wiimote pairing? Bastien Nocera
2009-12-05 14:50 ` Marcel Holtmann [this message]
2009-12-05 15:02   ` Bastien Nocera
2009-12-05 15:07     ` Marcel Holtmann
2009-12-05 15:43 ` Bastien Nocera
  -- strict thread matches above, loose matches on Subject: below --
2009-12-07 17:10 Hector Martin

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=1260024658.3041.14.camel@violet \
    --to=marcel@holtmann.org \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    /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.