From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kkgfp-0000iP-Uc for qemu-devel@nongnu.org; Tue, 30 Sep 2008 10:58:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kkgfp-0000ht-Bc for qemu-devel@nongnu.org; Tue, 30 Sep 2008 10:58:01 -0400 Received: from [199.232.76.173] (port=56952 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kkgfp-0000hd-4n for qemu-devel@nongnu.org; Tue, 30 Sep 2008 10:58:01 -0400 Received: from mail-gx0-f19.google.com ([209.85.217.19]:44470) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kkgfo-0001m3-Hz for qemu-devel@nongnu.org; Tue, 30 Sep 2008 10:58:00 -0400 Received: by gxk12 with SMTP id 12so12804512gxk.10 for ; Tue, 30 Sep 2008 07:57:59 -0700 (PDT) Message-ID: <48E23E36.70308@codemonkey.ws> Date: Tue, 30 Sep 2008 09:56:54 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [5344] Implement a HCI passthrough to host. References: <48E10106.5060203@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org andrzej zaborowski wrote: > 2008/9/29 Anthony Liguori : > >> 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 > > >