From: Marcel Holtmann <marcel@holtmann.org>
To: Olivier Bornet <Olivier.Bornet@smartdata.ch>
Cc: Charles Bueche <charles@bueche.ch>,
Edd Dumbill <edd@usefulinc.com>,
Peter Klausler <peter@klausler.com>,
BlueZ Developers List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600
Date: Thu, 04 Dec 2003 18:03:52 +0100 [thread overview]
Message-ID: <1070557432.24162.221.camel@pegasus> (raw)
In-Reply-To: <20031204163551.GG7164@smartdata.ch>
Hi Olivier,
> > Do you know how to access the display of the diNovo mediapad?
>
> Unfortunately, no. Has far as I known, this is not part of the HID
> profile. This is a "special" modified version by Logitech. I already
> have asked for this, without success at this time.
maybe someone with very good HID knowledge can decode the HID descriptor
and find an answer. Or we must use a protocol analyser to sniff the HIDP
packets.
> Also, for switching from USB to BT the "Bluetooth HUB", I will look with
> Logitech if we can have the specification for doing this switch. Hope I
> will have more success.
I have some response from CSR according the switch from HID to HCI mode.
This fits perfect for the EPoX dongle, but the Logitech dongle is quite
more complex. It presents a USB hub, two USB HID devices and four extra
HID devices with Windows XP.
However I actually don't how to implement the switch in Linux by now,
but I will take a look at it.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-12-04 17:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 14:12 [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600 Charles Bueche
2003-11-30 18:51 ` Charles Bueche
2003-12-01 15:38 ` Peter Klausler
2003-12-02 15:55 ` Edd Dumbill
2003-12-02 16:01 ` Edd Dumbill
2003-12-03 20:18 ` Charles Bueche
2003-12-03 20:35 ` Marcel Holtmann
2003-12-04 8:53 ` Olivier Bornet
2003-12-04 13:52 ` Marcel Holtmann
2003-12-04 13:57 ` Olivier Bornet
2003-12-04 14:10 ` Marcel Holtmann
2003-12-04 16:35 ` Olivier Bornet
2003-12-04 17:03 ` Marcel Holtmann [this message]
2003-12-09 20:31 ` Charles Bueche
2003-12-09 22:42 ` Olivier Bornet
2003-12-10 8:12 ` Charles Bueche
2003-12-10 8:30 ` Olivier Bornet
2003-12-13 15:56 ` Charles Bueche
2003-12-13 16:39 ` Marcel Holtmann
2003-12-13 18:51 ` Charles Bueche
2003-12-13 19:04 ` Marcel Holtmann
2003-12-14 13:55 ` Charles Bueche
2003-12-14 14:22 ` Marcel Holtmann
2003-12-14 20:01 ` Charles Bueche
2003-12-14 20:09 ` Marcel Holtmann
2003-12-10 1:41 ` Marcel Holtmann
2003-12-02 17:39 ` Marcel Holtmann
2003-12-02 17:42 ` Peter Klausler
2003-12-02 17:56 ` Marcel Holtmann
2003-12-03 10:10 ` Stephen Crane
2003-12-03 13:06 ` 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=1070557432.24162.221.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Olivier.Bornet@smartdata.ch \
--cc=bluez-devel@lists.sourceforge.net \
--cc=charles@bueche.ch \
--cc=edd@usefulinc.com \
--cc=peter@klausler.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