From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5344] Implement a HCI passthrough to host.
Date: Tue, 30 Sep 2008 18:10:04 +0200 [thread overview]
Message-ID: <fb249edb0809300910p637edebg22bdee31994ac82f@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580809300900m7f6d766dwc09e7de957671f4f@mail.gmail.com>
2008/9/30 Blue Swirl <blauwirbel@gmail.com>:
> On 9/30/08, andrzej zaborowski <balrogg@gmail.com> 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?
>>
>> Added a stronger check for bluez, hopefully will cross-compile better now.
>
> You are still relying that the host pkg-config exists and gives
> information that is valid for cross-compiling.
Not really -- the information will be (likely) wrong for
cross-compiling and configure will disable bluez, which is what we
want -- unless the user sets PKG_CONFIG_PATH correctly.
Cheers
next prev parent reply other threads:[~2008-09-30 16:10 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
2008-09-30 16:00 ` Blue Swirl
2008-09-30 16:10 ` andrzej zaborowski [this message]
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=fb249edb0809300910p637edebg22bdee31994ac82f@mail.gmail.com \
--to=balrogg@gmail.com \
--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 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).