From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Blank events file
Date: Sun, 26 Nov 2006 11:11:57 +0100 [thread overview]
Message-ID: <1164535917.25914.5.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <490dd6310611241234le826f35v5344eb16943b043e@mail.gmail.com>
Hi Andy,
> I've been trying to get a wiimote to work with linux and have been
> able to connect to it using hidd and an eventX file is created in
> /dev/input/ but when I try to read from it I get no data. Using
> hicdump I can recieve data on button presses so I would think that
> data should be sent to the event file and I was wondering why it's
> not.
>
> I don't know if it's important but towards the end of the connection
> output from hcidump and right after the "HIDP: Set protocol: Boot
> protocol" request I get the following message:
> > ACL data: handle 46 flags 0x02 dlen 5
> L2CAP(d): cid 0x0040 len 1 [psm 17]
> HIDP: Handshake: Unsupported request
you might wanna try my -mh kernel patch with the HID report mode
protocol support.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-11-26 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 20:34 [Bluez-users] Blank events file Andy Spencer
2006-11-26 10:11 ` 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=1164535917.25914.5.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox