From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5344] Implement a HCI passthrough to host.
Date: Tue, 30 Sep 2008 09:56:54 -0500 [thread overview]
Message-ID: <48E23E36.70308@codemonkey.ws> (raw)
In-Reply-To: <fb249edb0809291934v7d79cfb3hd68874b0e1d58f44@mail.gmail.com>
andrzej zaborowski wrote:
> 2008/9/29 Anthony Liguori <anthony@codemonkey.ws>:
>
>> Andrzej Zaborowski wrote:
>>
>>> Revision: 5344
>>> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5344
>>> Author: balrog
>>> Date: 2008-09-28 23:49:55 +0000 (Sun, 28 Sep 2008)
>>>
>>> Log Message:
>>> -----------
>>> Implement a HCI passthrough to host.
>>>
>>> This allows using a host's physical HCI as one of the HCIs attached
>>> to the virtual machine. This brings various limitations because not
>>> all commands/events are passed through by Linux kernel, some are
>>> interpreted by the host's kernel for a speed gain.
>>>
>>>
>> This broke the Windows build. The whole file should probably be build
>> conditionally on CONFIG_BLUEZ.
>>
>
> Is that because of uio.h? writev() seems to be posix. Does win32
> have it under a different name?
>
Yeah, there is no uio in win32. win32 isn't posix fwiw so a lot is missing.
> Added a stronger check for bluez, hopefully will cross-compile better now.
>
I think the best solution is to not compile in the entire file if
CONFIG_BLUEZ isn't set. Then we don't have to worry about dealing with
things like uio.
Regards,
Anthony Liguori
> Cheers
>
>
>
next prev parent reply other threads:[~2008-09-30 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 23:49 [Qemu-devel] [5344] Implement a HCI passthrough to host Andrzej Zaborowski
2008-09-29 15:15 ` Blue Swirl
2008-09-29 16:16 ` Anthony Liguori
2008-09-29 16:23 ` Anthony Liguori
2008-09-30 2:34 ` andrzej zaborowski
2008-09-30 14:56 ` Anthony Liguori [this message]
2008-09-30 16:00 ` Blue Swirl
2008-09-30 16:10 ` andrzej zaborowski
2008-09-30 16:12 ` Anthony Liguori
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=48E23E36.70308@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.