From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: bluez and dbus
Date: Fri, 10 Feb 2006 08:12:52 +0100 [thread overview]
Message-ID: <1139555572.22066.4.camel@localhost> (raw)
In-Reply-To: <43EC3341.6010100@gmail.com>
Hi Doug,
> >since you are creating the connection the value in /etc/bluetooth/pin is
> >never used. It is for incoming connection that request an authentication
> >and if security is set to auto.
>
> The way this is working right now, I need a second keyboard attached. When I reboot
> I can not get a connection with the bt keyboard without doing a hidd --search?
>
> you stated in your previous reply to run hidd --server
> it is started from my rc.local, so should I not have a connection once I get to my login
> prompt?
it should be started from /etc/init.d/bluetooth depending on your Linux
distribution. You get a connection once you press a key on your
keyboard.
> If thing's were setup to require a key, and this key was stored on the chip, would this
> not allow me to have a connection bt_kb<---->dongle as soon as there is power at the dongle
> on a reboot, so perhap's I could have a keyboard available at my grub prompt? Or am I right
> out to lunch on this one. :)
To have a keyboard at BIOS time you need a HID proxy dongle. Check the
various mailing list archives for details on it.
> Here's probably a more retarded question. If it was working like I mention above, would my
> bios know there was a keyboard connected to the dongle, so it didn't spit "no keyboard found"
> at me. My desk has one to many keyboard's on it,
The HID proxy dongle will also take care of this.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-02-10 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 6:31 [Bluez-users] Re: bluez and dbus nix4me
2006-02-10 7:12 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-10 20:44 nix4me
2006-02-11 3:47 ` Marcel Holtmann
2006-02-10 2:19 nix4me
2006-02-10 2:32 ` Marcel Holtmann
2006-02-09 20:09 Doug Chalmers
2006-02-10 0:59 ` Marcel Holtmann
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=1139555572.22066.4.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).