From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Stefan Seyfried <seife@suse.de>
Cc: BlueZ devel list <linux-bluetooth@vger.kernel.org>
Subject: Re: Feature request: boolean properties to auto reconnect list of MAC's at daemon start up
Date: Sat, 4 Jul 2009 10:37:39 -0300 [thread overview]
Message-ID: <2d5a2c100907040637s73791batd85327f31cb4f1ee@mail.gmail.com> (raw)
In-Reply-To: <20090704135747.05efc95c@stoetzler>
Hi,
On Sat, Jul 4, 2009 at 8:57 AM, Stefan Seyfried<seife@suse.de> wrote:
> On Sat, 04 Jul 2009 13:15:52 +0200
> Jelle de Jong <jelledejong@powercraft.nl> wrote:
>
>> Use-case: I have a lot of systems with successful connected bluetooth
>> keyboards. The boot-up of these systems are around 5 seconds with full
>> GUI. But the devices is not usable yet, because when you press a key
>> it first start connection... this takes almost the same time as the
>> complete boot-up and it forces an extra key press of the user every
>> time they start the system. Maybe some org.bluez.Input interface
>> thing?
>
> IIUC that's just how bluetooth input devices work: they do connect to
> the host - not the other way round. So it is really a problem that
> cannot be solved on bluez' side.
Yep, most hid devices will just refuse the connection if the 'virtual
cable plug' was already stabilised, in general this is also a bad idea
for any connection attempt during the startup as we have no guarantee
that the connection will complete.
--
Luiz Augusto von Dentz
Engenheiro de Computação
next prev parent reply other threads:[~2009-07-04 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-04 11:15 Feature request: boolean properties to auto reconnect list of MAC's at daemon start up Jelle de Jong
2009-07-04 11:57 ` Stefan Seyfried
2009-07-04 13:37 ` Luiz Augusto von Dentz [this message]
2009-07-04 14:03 ` Iain Hibbert
2009-07-09 8:00 ` Jelle de Jong
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=2d5a2c100907040637s73791batd85327f31cb4f1ee@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=seife@suse.de \
/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