From: Marcel Holtmann <marcel@holtmann.org>
To: Deepesh S Gujarathi <d_gujarathi@hotmail.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: blueZ-bthid testing
Date: Tue, 06 Jan 2004 14:16:20 +0100 [thread overview]
Message-ID: <1073394980.2508.59.camel@pegasus> (raw)
In-Reply-To: <LAW11-OE14JMxg22Civ0001db81@hotmail.com>
Hi Deepesh,
> I tried to create the device node using the following commands but I still
> get the same error ( > bthid[2040]: can't open input device: no such file or
> directory (2)) .
> I created a device node using the command
> # mknod /dev/misc/uinput c 10 101
> I hope I an not feeding the wrong MAJOR device number.
yes you do. According to Documentation/devices.txt it is "c 10 223". And
of course the kernel module "uinput" must be loaded.
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
next prev parent reply other threads:[~2004-01-06 13:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LAW11-OE33GHeqXipAS00015cf1@hotmail.com>
2004-01-05 14:54 ` [Bluez-devel] Re: blueZ-bthid testing Marcel Holtmann
2004-01-06 13:03 ` Deepesh S Gujarathi
2004-01-06 13:16 ` Marcel Holtmann [this message]
2004-01-07 12:56 ` Deepesh S Gujarathi
2004-01-07 13:11 ` [Bluez-devel] " Marcel Holtmann
2004-01-08 11:09 ` Deepesh S Gujarathi
2004-01-08 12:07 ` [Bluez-devel] " Charles Bueche
2004-01-10 9:09 ` [Bluez-devel] " Deepesh S Gujarathi
2004-01-10 13:32 ` Charles Bueche
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=1073394980.2508.59.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=d_gujarathi@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox