From: Peter Hurley <peter@hurleysoftware.com>
To: "thilo@cestona.ro" <thilo@cestona.ro>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Support for 0489:e031 Foxconn / Hon Hai
Date: Mon, 27 Jun 2011 14:26:57 -0400 [thread overview]
Message-ID: <1309199217.2143.23.camel@THOR> (raw)
In-Reply-To: <44c0c13.6e1d3014b80fb8f0331e4275187e6b1d@1oca1host.de>
On Mon, 2011-06-27 at 10:57 -0400, thilo@cestona.ro wrote:
> Hey again,
>
> >>As Virtualbox does a direct usb passthrough to the client I could install the bluetooth adapter in windows with the original broadcom bluetooth driver.
> >>Once I opened the settings there and "saved" theses, the adapter finds bluetooth devices nicely under windows AND linux.
> >>
> >>Sadly I have no idea what the broadcom driver did to "activate" the adapter.
....
> I still have no idea how I might figure out what is done during the init of the windows driver. Since I need to unload the btusb module so windows can use the device, I have no chance to use hcidump.
> Any ideas what I should try?
There are several decent usb sniffers for windows - although I've never
tried them in a vm. This is a tough route to go though - even with a
complete device capture, separating what's relevant to your problem will
be *very* difficult.
Peter
next prev parent reply other threads:[~2011-06-27 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 14:57 Support for 0489:e031 Foxconn / Hon Hai thilo
2011-06-27 18:26 ` Peter Hurley [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-09 20:23 Michael Markusch
2011-06-10 11:17 thilo
2011-06-08 13:33 thilo
2011-06-09 10:21 ` Marcel Holtmann
2011-06-01 11:48 thilo
2011-06-02 1:03 ` Marcel Holtmann
2011-06-02 7:23 ` Thilo Cestonaro
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=1309199217.2143.23.camel@THOR \
--to=peter@hurleysoftware.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=thilo@cestona.ro \
/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).