From: Thomas Nemeth <thomas.nemeth@betatech.fr>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Logitech MX900 and hid2hci/hidp
Date: Wed, 13 Apr 2005 13:03:40 +0000 (UTC) [thread overview]
Message-ID: <loom.20050413T144754-221@post.gmane.org> (raw)
Hi !
I've got a quite big problem. I need to make a logitech mouse MX900 work
with a 2.4.20 kernel (because my customer ask me to : he don't want to
change the kernel because of validation his company has made).
I got the 2.4.20 sources and the config used by my customer, applyed the
-mh18 patch to it, selected all bluetooth drivers and input core, usb stuff...
Compiled it, installed it and its modules, all went ok.
When I modprobe hidp (after all other needed modules), all seems ok. I run
hid2hci and it reports to have successfully switched device 046d:c705 to HCI
mode.
Anyway, hcid does not report hci0 (I only have 1 bluetooth device by now)
beeing seen neither configured. hcitool scan reports :
"Device is not available: Success" witch is a bit strange.
I have all the /dev stuff needed (I think) :
/dev/usb/hiddev*
/dev/input/uinput (just in case)
(can't remember if I created some other device)
I mounted /proc/bus/usb too...
I looked at the hcitool sources, bluetooth library and found that the
HCIGETDEVLIST ioctl command gave no results. So the problem seems to be
between hidp, hcid and hid2hci...
Is there any mean to make this mouse work with a 2.4.20 ?
Did I miss something ?
Thank you in advance...
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2005-04-13 13:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=loom.20050413T144754-221@post.gmane.org \
--to=thomas.nemeth@betatech.fr \
--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