All of lore.kernel.org
 help / color / mirror / Atom feed
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:20:39 +0200	[thread overview]
Message-ID: <1082575239.23959.56.camel@pegasus> (raw)
In-Reply-To: <8F95FDA9-93BB-11D8-88A9-00039390D626@pepper.com>

Hi Michael,

> I now have my kernel running bluez and now want to set up the new bthid 
> from CVS.

and you compiled the uinput driver?

> I built libs2 and utils2 and am trying to run the bthidd and get the 
> following errors.
> 
> root@(none):/opt/bluetooth/bluez/sbin# ./bthidd
> Can't open HIDP control socket: Invalid argument
> 
> Did I not compile something into the kernel that I need to support this?

This userspace code is for the HIDP kernel module which is experimental
stuff. What you are looking for is the bthid program.

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

  reply	other threads:[~2004-04-21 19:20 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 [this message]
2004-04-21 19:26   ` Michael Frey
2004-04-21 19:32     ` Marcel Holtmann
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=1082575239.23959.56.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.