From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: Logitech diNovo Media Desktop Laser patch
Date: Mon, 07 Nov 2005 07:49:03 +0100 [thread overview]
Message-ID: <1131346143.5824.34.camel@blade> (raw)
In-Reply-To: <e1c464970511062228p1bafdf87mcef1cf3a77deb47c@mail.gmail.com>
Hi Trevor,
> Well, I just upgraded to 2.6.14 with 2.6.14-mh2, and it doesn't work,
> with and without the hci_usb.c patch I used. hciconfig just shows the
> mac address of 00's.
send the patch again.
> Anyways, I went back to 2.6.13, with the hci_usb.c patch. Works fine.
> I'll try it without it, I just have to recompile my kernel with a new
> version of gcc. ( reinstalled gentoo using gcc4 ). I'd do it now, but
> I want to get this email out before I head to work.
>
> I also found out that the patch I sent you earlier for hid2hci.c did
> not work. Apparently, 0x046d:0x0b02 was not the correct device from
> the usb controller to do the switching to. Adding all three:
> { HCI, 0x046d, 0xc70c, switch_logitech },
> { HCI, 0x046d, 0xc70b, switch_logitech },
> { HCI, 0x046d, 0x0b02, switch_logitech },
> worked though. Perhaps it's 0xc70c?
Try to find out which product id is really working.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-11-07 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 6:28 [Bluez-devel] Re: Logitech diNovo Media Desktop Laser patch Trevor Joynson
2005-11-07 6:49 ` 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=1131346143.5824.34.camel@blade \
--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;
as well as URLs for NNTP newsgroup(s).