All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Leeber <florian@ubports.com>
To: Bastien Nocera <hadess@hadess.net>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] plugins: Do not try to autopair with Nissan Connect devices
Date: Thu, 1 Sep 2022 18:10:32 +0000	[thread overview]
Message-ID: <01070182fa3f5ac6-66cb5385-fab0-4916-9e97-bdf54ef3a3f6-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <1ef5e51d2103b6f02826777ebf5415f74018e317.camel@hadess.net>

Am 01.09.2022 um 12:46 schrieb Bastien Nocera:
> On Wed, 2022-08-31 at 13:18 -0700, Luiz Augusto von Dentz wrote:
>> Hi Florian,
>>
>> On Wed, Aug 31, 2022 at 12:44 PM Florian Leeber <florian@ubports.com>
>> wrote:
>> gs as default). 
> FWIW, gnome-bluetooth has its own database on top of bluez, which we
> prefer to the code in bluez. I'd be happy getting rid of it.
>
> Loads of devices that need pairing despite their class and Bluetooth
> version, and devices that need special handling like the Navman GPS
> that expects a non-numerical PIN.
>
> The database:
> https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/blob/master/lib/pin-code-database.xml
> The code to parse it:
> https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/blob/master/lib/pin.c

Oh my, this escalated quickly ;) - tbh implementing this as a fully 
fledged config-based feature might be over my head. I am not proficient 
with the Bluez code at all, and my main work currently is being the OTA 
release manager for Ubuntu Touch. I could only work on this with some 
support to get the basics established.

Thanks for the hint with the database, we did not know about this.



  reply	other threads:[~2022-09-01 18:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31 19:30 [PATCH] plugins: Do not try to autopair with Nissan Connect devices Florian Leeber
2022-08-31 19:42 ` bluez.test.bot
2022-08-31 20:18 ` [PATCH] " Luiz Augusto von Dentz
2022-09-01 10:46   ` Bastien Nocera
2022-09-01 18:10     ` Florian Leeber [this message]
2022-09-01 23:56       ` Luiz Augusto von Dentz
2022-09-02 18:50         ` Florian Leeber
2022-09-29 16:49 ` bluez.test.bot
2022-09-29 17:44 ` bluez.test.bot
2022-09-29 18:40 ` bluez.test.bot
2022-09-29 19:01 ` bluez.test.bot
2022-09-29 19:29 ` bluez.test.bot
2022-09-29 19:47 ` bluez.test.bot
2022-09-29 20:34 ` bluez.test.bot
2022-09-29 20:53 ` bluez.test.bot
2022-09-29 21:30 ` bluez.test.bot
2022-09-29 21:52 ` bluez.test.bot
2022-09-29 22:32 ` bluez.test.bot
2022-09-29 22:52 ` bluez.test.bot
2022-09-29 23:40 ` bluez.test.bot
2022-09-29 23:59 ` bluez.test.bot

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=01070182fa3f5ac6-66cb5385-fab0-4916-9e97-bdf54ef3a3f6-000000@eu-central-1.amazonses.com \
    --to=florian@ubports.com \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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.