From: Jelle de Jong <jelledejong@powercraft.nl>
To: Iain Hibbert <plunky@rya-online.net>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
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: Thu, 09 Jul 2009 10:00:31 +0200 [thread overview]
Message-ID: <4A55A39F.50307@powercraft.nl> (raw)
In-Reply-To: <1246716212.336777.600.nullmailer@galant.ukfsn.org>
Iain Hibbert schreef:
> On Sat, 4 Jul 2009, Luiz Augusto von Dentz wrote:
>
>>> 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.
>
> see HIDNormallyConnectable attribute in the HID spec (7.11.13)
>
> I certainly find with my Apple bluetooth keyboard and mouse that the host
> OS (not using BlueZ btw) can connect to them at boot without my
> intervention.
>
> iain
Thanks you for providing this information it helps to see that apple
does provide this behavior for usability to its users. Would a developer
be willing to investigate this feature and place this on his/her to do list?
Thanks in advance,
Jelle
prev parent reply other threads:[~2009-07-09 8:00 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
2009-07-04 14:03 ` Iain Hibbert
2009-07-09 8:00 ` Jelle de Jong [this message]
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=4A55A39F.50307@powercraft.nl \
--to=jelledejong@powercraft.nl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=plunky@rya-online.net \
/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