From: Marcel Holtmann <marcel@holtmann.org>
To: Michael Frey <mfrey@pepper.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BTHID setup...
Date: Wed, 21 Apr 2004 21:32:45 +0200 [thread overview]
Message-ID: <1082575965.23959.63.camel@pegasus> (raw)
In-Reply-To: <CAE1625E-93C9-11D8-88A9-00039390D626@pepper.com>
Hi Michael,
> I understand, and I now have my keyboard working using bthid. However
> search and list does not work for me. It never prints anything out. I
> had to find out the btaddr of my keyboard and use bthid -c after
> launching bthid -d. That works. I would now love to have bthid find
> and connect automatically.
the search and list are not implemented and maybe never will be. However
most HID device are designed to reconnect. This means that starting
bthid -d at boot is enough and after you press a key, your keyboard will
connect to the latest used host device.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-04-21 19:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 17:44 [Bluez-devel] BTHID setup Michael Frey
2004-04-21 19:20 ` Marcel Holtmann
2004-04-21 19:26 ` Michael Frey
2004-04-21 19:32 ` Marcel Holtmann [this message]
2004-04-21 20:44 ` Michael Frey
2004-04-21 20:50 ` 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=1082575965.23959.63.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=mfrey@pepper.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.