From: Marcel Holtmann <marcel@holtmann.org>
To: Charles Bueche <charles@bueche.ch>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Getting in touch with libs2 and utils2
Date: Wed, 17 Dec 2003 23:02:57 +0100 [thread overview]
Message-ID: <1071698576.21803.65.camel@pegasus> (raw)
In-Reply-To: <1071695000.6361.13.camel@bluez.bueche.ch>
Hi Charles,
> success !!! Works much better than the hacked bthid under gentoo
> 2.6test11.
>
> I followed your guide below (preceded by a cvs checkout of course). I
> then ran
>
> - hcid (from the gentoo bluez packages)
> - /opt/bluetooth/sbin/bthid --daemon
> - moving mouse --> discover message in syslog : WORKS. YOUPI !!!
this is good to hear.
> I don't have any other Bluetooth hardware (beside my Ericsson T68 which
> isn't a HID device AFAIK), so I can't make much more tests.
I have and even 7 HID devices in one piconet are working fine.
> Apparently, gentoo creates the uinput device in /dev/misc instead of the
> usual /dev/input. Thanks to Marcel for testing both in parser.c !
It is the normal way of doing this ;)
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2003-12-17 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 21:08 [Bluez-devel] Getting in touch with libs2 and utils2 Marcel Holtmann
2003-12-17 21:03 ` Charles Bueche
2003-12-17 22:02 ` Marcel Holtmann [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=1071698576.21803.65.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=charles@bueche.ch \
/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.