From: Bastien Nocera <hadess@hadess.net>
To: Alex Deymo <deymo@chromium.org>
Cc: linux-bluetooth@vger.kernel.org, keybuk@chromium.org,
marcel@holtmann.org
Subject: Re: [PATCH 0/6] The Autopair strikes back
Date: Thu, 21 Mar 2013 08:49:14 +0100 [thread overview]
Message-ID: <1363852154.2681.3.camel@novo> (raw)
In-Reply-To: <1363839008-8405-1-git-send-email-deymo@chromium.org>
Hey Alex,
On Wed, 2013-03-20 at 21:10 -0700, Alex Deymo wrote:
> Hello!
> This is a rework of the autopair.c plugin we had at some point in BlueZ 4.
Happy to see it come back!
> The goal of this patch set is to make the pairing process easier for
> devices that have a fixed and dumb pincode (like 0000 or 1234) or that
> accept any pincode as long as the same pincode is entered on the device
> (keyboards/combos). The goal is:
> * Don't ask the user (i.e. the agent) a question if we know the right answer.
> This makes the user happier. =)
Is there any chance you could use:
https://git.gnome.org/browse/gnome-bluetooth/tree/wizard/pin-code-database.xml
even it means converting it to a different format?
This would mean more supported devices out-of-the-box? I'd be happy
maintaining the list outside of the bluez tree if the bluez developers
don't want to take on the burden of maintaining it.
Cheers
next prev parent reply other threads:[~2013-03-21 7:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 4:10 [PATCH 0/6] The Autopair strikes back Alex Deymo
2013-03-21 4:10 ` [PATCH 1/6] core: Convert the pincode callback to an interable list Alex Deymo
2013-03-21 4:10 ` [PATCH 2/6] plugins: Extend the pin code callback with the call number Alex Deymo
2013-03-21 23:12 ` Scott James Remnant
2013-03-22 10:06 ` David Herrmann
2013-03-21 4:10 ` [PATCH 3/6] core: Add support for retrying a bonding Alex Deymo
2013-03-21 4:10 ` [PATCH 4/6] core: retry bonding attempt until the iterator reachs the end Alex Deymo
2013-03-21 4:10 ` [PATCH 5/6] core: Add device_get_class to the public interface Alex Deymo
2013-03-21 4:10 ` [PATCH 6/6] autopair: Add the autopair plugin Alex Deymo
2013-03-21 23:13 ` Scott James Remnant
2013-03-21 7:49 ` Bastien Nocera [this message]
2013-03-21 23:07 ` [PATCH 0/6] The Autopair strikes back Scott James Remnant
2013-03-22 8:23 ` Bastien Nocera
2013-03-22 8:52 ` Bastien Nocera
2013-03-21 9:11 ` Szymon Janc
2013-03-21 15:30 ` Luiz Augusto von Dentz
2013-03-21 15:35 ` Luiz Augusto von Dentz
2013-03-22 17:36 ` Alex Deymo
2013-03-21 23:10 ` Scott James Remnant
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=1363852154.2681.3.camel@novo \
--to=hadess@hadess.net \
--cc=deymo@chromium.org \
--cc=keybuk@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox