From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] logitech mx 5000
Date: Wed, 09 Aug 2006 23:48:48 +0200 [thread overview]
Message-ID: <1155160128.4492.0.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <44D9CCF1.9060102@prolly.org>
Hi Douglas,
> here... this makes (046d:0b02) switch to HCI mode. I'm not sure why
> but it requires that the switch command be sent to both the emulated
> keyboard and mouse devices. switching one seems to make the hci device
> show up, but it doesn't actually function. I don't know enough about
> bluez to do anymore then this. my mx 5000 combo have been working in
> bluetooth mode for quite some time now and i even reported my success
> on this mailing list. the other keyboard set (dinovo?) with this
> dongle may need its emulated devices added as well.
can you send in the content from /proc/bus/usb/devices before switching
into HCI mode. Why do you removed the other line?
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-08-09 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 11:54 [Bluez-devel] logitech mx 5000 Douglas Ward
2006-08-09 21:48 ` Marcel Holtmann [this message]
2006-08-09 20:41 ` Douglas Ward
2006-08-09 22:48 ` 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=1155160128.4492.0.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@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