All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Olivier Bornet <Olivier.Bornet@smartdata.ch>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-users] bthid cvs question
Date: Wed, 10 Dec 2003 15:18:42 +0100	[thread overview]
Message-ID: <1071065922.10655.60.camel@pegasus> (raw)
In-Reply-To: <20031210080259.GF26896@smartdata.ch>

Hi Olivier,

> > the code is in CVS under utils2/hid/ now.
> 
> And do you have some tips on how to use it. I have try without success.
> I will be happy to switch from bthid to the hid from BlueZ.

you need to install libs2 and I propose that you install it somewhere
else. For example with prefix /opt/bluetooth or so. After that you have
to tweak the Makefile.am files from utils2 to find the includes and the
library under that specific prefix. Compile it with the same prefix and
you get the bthid and hid2hci program. I will work on getting the config
part of libs2 and utils2 finished this weekend, so it will be easy to
install it with a different prefix and not breaking your current setup.

To use bthid you must make sure that uinput kernel module is loaded and
that you have /dev/input/uinput. Start "bthid -d" and you have the HID
server. Watch the syslog for connection events.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2003-12-10 14:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09 17:28 [Bluez-users] bthid cvs question Jeffrey Arbuckle
2003-12-10  1:43 ` Marcel Holtmann
2003-12-10  8:02   ` Olivier Bornet
2003-12-10 14:18     ` Marcel Holtmann [this message]
2003-12-20 23:01       ` Florian Echtler
2003-12-21  1:25         ` [Bluez-devel] " Marcel Holtmann
2003-12-21 10:52           ` Florian Echtler
2003-12-21 11:56             ` [Bluez-devel] " Marcel Holtmann
2003-12-21 12:48               ` Florian Echtler
2003-12-21 13:14                 ` [Bluez-devel] " Marcel Holtmann
2004-01-05 16:44           ` Steven Singer
2004-01-05 19:02             ` [Bluez-devel] " Marcel Holtmann
2004-01-05 21:21               ` Steven Singer

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=1071065922.10655.60.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=Olivier.Bornet@smartdata.ch \
    --cc=bluez-devel@lists.sourceforge.net \
    --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 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.