From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kyzyz-0000yI-Bn for qemu-devel@nongnu.org; Sat, 08 Nov 2008 21:24:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kyzyy-0000xz-Nr for qemu-devel@nongnu.org; Sat, 08 Nov 2008 21:24:57 -0500 Received: from [199.232.76.173] (port=52840 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kyzyy-0000xv-Id for qemu-devel@nongnu.org; Sat, 08 Nov 2008 21:24:56 -0500 Received: from savannah.gnu.org ([199.232.41.3]:47051 helo=sv.gnu.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Kyzyy-0000It-AA for qemu-devel@nongnu.org; Sat, 08 Nov 2008 21:24:56 -0500 Received: from cvs.savannah.gnu.org ([199.232.41.69]) by sv.gnu.org with esmtp (Exim 4.63) (envelope-from ) id 1Kyzyx-000053-JI for qemu-devel@nongnu.org; Sun, 09 Nov 2008 02:24:55 +0000 Received: from balrog by cvs.savannah.gnu.org with local (Exim 4.63) (envelope-from ) id 1Kyzyx-00004z-6r for qemu-devel@nongnu.org; Sun, 09 Nov 2008 02:24:55 +0000 MIME-Version: 1.0 Errors-To: balrog Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Andrzej Zaborowski Message-Id: Date: Sun, 09 Nov 2008 02:24:55 +0000 Subject: [Qemu-devel] [5654] Document bluetooth support in qemu-doc. 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 Revision: 5654 http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5654 Author: balrog Date: 2008-11-09 02:24:54 +0000 (Sun, 09 Nov 2008) Log Message: ----------- Document bluetooth support in qemu-doc. Modified Paths: -------------- trunk/hw/usb-bt.c trunk/qemu-doc.texi Modified: trunk/hw/usb-bt.c =================================================================== --- trunk/hw/usb-bt.c 2008-11-09 00:28:40 UTC (rev 5653) +++ trunk/hw/usb-bt.c 2008-11-09 02:24:54 UTC (rev 5654) @@ -623,6 +623,8 @@ { struct USBBtState *s; + if (!hci) + return NULL; s = qemu_mallocz(sizeof(struct USBBtState)); if (!s) return NULL; Modified: trunk/qemu-doc.texi =================================================================== --- trunk/qemu-doc.texi 2008-11-09 00:28:40 UTC (rev 5653) +++ trunk/qemu-doc.texi 2008-11-09 02:24:54 UTC (rev 5654) @@ -782,6 +782,62 @@ @end table +Bluetooth(R) options: +@table @option + +@item -bt hci[...] +Defines the function of the corresponding Bluetooth HCI. -bt options +are matched with the HCIs present in the chosen machine type. For +example when emulating a machine with only one HCI built into it, only +the first @code{-bt hci[...]} option is valid and defines the HCI's +logic. The Transport Layer is decided by the machine type. Currently +the machines @code{n800} and @code{n810} have one HCI and all other +machines have none. + +@anchor{bt-hcis} +The following three types are recognized: + +@table @code +@item -bt hci,null +(default) The corresponding Bluetooth HCI assumes no internal logic +and will not respond to any HCI commands or emit events. + +@item -bt hci,host[:@var{id}] +(@code{bluez} only) The corresponding HCI passes commands / events +to / from the physical HCI identified by the name @var{id} (default: +@code{hci0}) on the computer running QEMU. Only available on @code{bluez} +capable systems like Linux. + +@item -bt hci[,vlan=@var{n}] +Add a virtual, standard HCI that will participate in the Bluetooth +scatternet @var{n} (default @code{0}). Similarly to @option{-net} +VLANs, devices inside a bluetooth network @var{n} can only communicate +with other devices in the same network (scatternet). +@end table + +@item -bt vhci[,vlan=@var{n}] +(Linux-host only) Create a HCI in scatternet @var{n} (default 0) attached +to the host bluetooth stack instead of to the emulated target. This +allows the host and target machines to participate in a common scatternet +and communicate. Requires the Linux @code{vhci} driver installed. Can +be used as following: + +@example +qemu [...OPTIONS...] -bt hci,vlan=5 -bt vhci,vlan=5 +@end example + +@item -bt device:@var{dev}[,vlan=@var{n}] +Emulate a bluetooth device @var{dev} and place it in network @var{n} +(default @code{0}). QEMU can only emulate one type of bluetooth devices +currently: + +@table @code +@item keyboard +Virtual wireless keyboard implementing the HIDP bluetooth profile. +@end table + +@end table + Linux boot specific: When using these options, you can use a given Linux kernel without installing it in the disk image. It can be useful for easier testing of various kernels. @@ -1767,6 +1823,15 @@ qemu [...OPTIONS...] -net user,vlan=0 -usbdevice net:vlan=0 @end example Currently this cannot be used in machines that support PCI NICs. +@item bt[:@var{hci-type}] +Bluetooth dongle whose type is specified in the same format as with +the @option{-bt hci} option, @pxref{bt-hcis,,allowed HCI types}. If +no type is given, the HCI logic corresponds to @code{-bt hci,vlan=0}. +This USB device implements the USB Transport Layer of HCI. Example +usage: +@example +qemu [...OPTIONS...] -usbdevice bt:hci,vlan=3 -bt device:keyboard,vlan=3 +@end example @end table @node host_usb_devices @@ -2664,6 +2729,8 @@ @item Three OMAP on-chip UARTs and on-chip STI debugging console @item +A Bluetooth(R) transciever and HCI connected to an UART +@item Mentor Graphics "Inventra" dual-role USB controller embedded in a TI TUSB6010 chip - only USB host mode is supported @item