linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] bluetoothd: add option to automatically power on the first adapter found
Date: Sat, 25 Apr 2015 12:26:13 +0200	[thread overview]
Message-ID: <553B6BC5.4060407@ahsoftware.de> (raw)
In-Reply-To: <552EA70F.9050706@ahsoftware.de>

Am 15.04.2015 um 19:59 schrieb Alexander Holler:
> Am 14.04.2015 um 15:50 schrieb Marcel Holtmann:
>
>> Your race power on vs keys and known devices programmed into the
>> kernel. It needs to be done in the right order.
>
> Hmm, I still seem to function, no sign of races, besides that I'm
> happily working without a Linux kernel.
>
> But in regard to the patch. Maybe. No idea. It works for me (tm) and is
> faster and more reliable here than other stuff.

To pick up that thread again, if you want that I remove a race in that 
patch I don't see by looking at it, you have to be a bit more verbose 
about the race.

For me it currently reads like you're more talking about an existing 
problem in the kernel. If the kernel doesn't like it that a bt-device 
will be turned on before something like keys and known devices have been 
setup, then the kernel should throw an error back to userspace.

But that's just an assumption from me, I haven't read through all the 
source in bluetoothd or the kernel, but instead just turned on a knob 
like it would be turned on by issuing "power on" in bluetoothctl.

Regards,

Alexander Holler

  reply	other threads:[~2015-04-25 10:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 16:57 [PATCH] bluetoothd: add option to automatically power on the first adapter found Alexander Holler
2015-04-10 17:10 ` Marcel Holtmann
2015-04-10 17:15   ` Alexander Holler
2015-04-11  4:06     ` Alexander Holler
2015-04-11  5:07       ` Alexander Holler
2015-04-11 16:48         ` Alexander Holler
2015-04-11 17:55           ` Marcel Holtmann
2015-04-12  9:23             ` Alexander Holler
2015-04-12 18:50               ` Marcel Holtmann
2015-04-13  9:10                 ` Alexander Holler
2015-04-13 14:32                   ` Marcel Holtmann
2015-04-13 19:08                     ` Alexander Holler
2015-04-13 20:22                       ` Marcel Holtmann
2015-04-14  8:33                         ` Alexander Holler
2015-04-14 13:50                           ` Marcel Holtmann
2015-04-14 14:14                             ` Szymon Janc
2015-04-14 15:56                               ` Szymon Janc
2015-04-15 17:59                             ` Alexander Holler
2015-04-25 10:26                               ` Alexander Holler [this message]
2015-04-27  4:40                                 ` Marcel Holtmann
2015-04-27  9:11                                   ` Alexander Holler
2015-04-27 18:53                                     ` Marcel Holtmann
2015-04-27 20:36                                       ` Alexander Holler
2015-04-10 17:15   ` Szymon Janc

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=553B6BC5.4060407@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --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;
as well as URLs for NNTP newsgroup(s).