From: Marcel Holtmann <marcel@holtmann.org>
To: mark <gress2k1@copper.net>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcidump-1.6, Intellimouse, and HID Parser
Date: Tue, 02 Mar 2004 09:25:51 +0100 [thread overview]
Message-ID: <1078215951.1942.177.camel@pegasus> (raw)
In-Reply-To: <1078172702.2065.25.camel@localhost>
Hi Mark,
> Following that link, I read through it real quick, and that seems like
> it's going to be what I need(straight forward and not necessarily
> complex). Thanks much. But I don't have the uinput.o file that is
> needed. I followed the instructions here
> http://www.bueche.ch/comp/mx900/bthid-msmouse_howto.txt which explain
> specifically for the M$ mouse, and one line specifically I followed was
> this
>
> if you miss the device file, create it with
> # mknod /dev/misc/uinput c 10 223
>
> Which gave me the uinput device I was missing. From there, I started
> over, re-installed bluez, but I seem to be missing something. Your
> kernel patch worked fine on 2.4.22.(or seemed to) when I get home
> tomorrow, I'll give it a try again. thanks for your reply.
the uinput driver is part of my kernel patches, but you have to select
and compile it. You can found the option under input subsystem.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-03-02 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 14:06 [Bluez-users] hcidump-1.6, Intellimouse, and HID Parser mark
2004-03-01 14:51 ` Marcel Holtmann
[not found] ` <1078172702.2065.25.camel@localhost>
2004-03-02 8:25 ` 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=1078215951.1942.177.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=gress2k1@copper.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox