From: Hector Martin <hector@marcansoft.com>
To: linux-bluetooth@vger.kernel.org
Cc: Bastien Nocera <hadess@hadess.net>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: Wiimote pairing?
Date: Mon, 07 Dec 2009 18:10:44 +0100 [thread overview]
Message-ID: <4B1D3714.9080003@marcansoft.com> (raw)
Sorry for the lack of proper thread headers. I subscribed to ask about
this very issue and it turns out it was asked two days ago in the
already, after I checked out the archives :)
Seeing as everything is done using strings everywhere, including the
storage (which is a text file), I think it might be easier to just
define a hex format. Something like $0011deadbeef for raw binary
pincodes expressed as hex. This will let all the existing tools handle a
raw PIN.
The Bluetooth spec talks about numeric and alphanumeric PIN codes, but I
haven't seen mention of special characters. I think the likelihood of
having issues with real PINs with a starting $ sign is fairly low (and
they could always be expressed as hex).
An alternative would be to use a more traditional backslash escape
sequence type format, but that's harder to parse.
--
Hector Martin (hector@marcansoft.com)
Public Key: http://www.marcansoft.com/marcan.asc
next reply other threads:[~2009-12-07 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:10 Hector Martin [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-05 13:57 Wiimote pairing? Bastien Nocera
2009-12-05 14:50 ` Marcel Holtmann
2009-12-05 15:02 ` Bastien Nocera
2009-12-05 15:07 ` Marcel Holtmann
2009-12-05 15:43 ` Bastien Nocera
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=4B1D3714.9080003@marcansoft.com \
--to=hector@marcansoft.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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.