From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kkhnd-0000Ua-TC for qemu-devel@nongnu.org; Tue, 30 Sep 2008 12:10:09 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KkhnZ-0000TD-P3 for qemu-devel@nongnu.org; Tue, 30 Sep 2008 12:10:09 -0400 Received: from [199.232.76.173] (port=56779 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KkhnZ-0000TA-Kg for qemu-devel@nongnu.org; Tue, 30 Sep 2008 12:10:05 -0400 Received: from wf-out-1314.google.com ([209.85.200.169]:55647) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KkhnZ-0001qT-6C for qemu-devel@nongnu.org; Tue, 30 Sep 2008 12:10:05 -0400 Received: by wf-out-1314.google.com with SMTP id 27so99521wfd.4 for ; Tue, 30 Sep 2008 09:10:04 -0700 (PDT) Message-ID: Date: Tue, 30 Sep 2008 18:10:04 +0200 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] [5344] Implement a HCI passthrough to host. In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <48E10106.5060203@codemonkey.ws> 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 2008/9/30 Blue Swirl : > On 9/30/08, 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? >> >> 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