From owner-freebsd-bluetooth@FreeBSD.ORG Mon Sep 13 11:06:51 2010 Return-Path: Delivered-To: freebsd-bluetooth@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD6BD10656D4 for ; Mon, 13 Sep 2010 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8FB5C8FC08 for ; Mon, 13 Sep 2010 11:06:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o8DB6pmn001832 for ; Mon, 13 Sep 2010 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8DB6pGW001830 for freebsd-bluetooth@FreeBSD.org; Mon, 13 Sep 2010 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 13 Sep 2010 11:06:51 GMT Message-Id: <201009131106.o8DB6pGW001830@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-bluetooth@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-bluetooth@FreeBSD.org X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2010 11:06:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- p kern/140590 bluetooth [bluetooth] ng_ubt(4) ng_l2cap_process_cmd_rej warning 1 problem total. From owner-freebsd-bluetooth@FreeBSD.ORG Mon Sep 13 20:38:07 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAC0D1065696 for ; Mon, 13 Sep 2010 20:38:07 +0000 (UTC) (envelope-from web1@vcvps1364.vcdns.de) Received: from vcvps1364.vcdns.de (vcvps1364.vcdns.de [88.80.215.7]) by mx1.freebsd.org (Postfix) with ESMTP id 9377F8FC27 for ; Mon, 13 Sep 2010 20:38:07 +0000 (UTC) Received: by vcvps1364.vcdns.de (Postfix, from userid 33) id 42CBB10BAE2D; Mon, 13 Sep 2010 22:06:40 +0200 (CEST) To: freebsd-bluetooth@freebsd.org From: Mme Claire Page MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: <20100913200640.42CBB10BAE2D@vcvps1364.vcdns.de> Date: Mon, 13 Sep 2010 22:06:40 +0200 (CEST) Subject: Ramadan heureux mon cher X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mm.chiwe.conte@gmail.com List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2010 20:38:07 -0000 I am Mrs Claire Page sending you this mail from my sick bed in the hospital. Please contact my lawyer, Email:(barr_willam_frank@lawyer.com) Je suis Mme Claire Page vous envoie ce mail de mon lit de malade à l'hôpital. S'il vous plaît communiquer avec mon avocat, Email: (barr_willam_frank@lawyer.com) From owner-freebsd-bluetooth@FreeBSD.ORG Fri Sep 17 09:39:14 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B1C91065670 for ; Fri, 17 Sep 2010 09:39:14 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp02.one2one.net (smtp02.one2one.net [149.254.192.174]) by mx1.freebsd.org (Postfix) with ESMTP id 172848FC19 for ; Fri, 17 Sep 2010 09:39:13 +0000 (UTC) Received: from localhost ([127.0.0.1]) by localhost with esmtp (Exim 4.69) (envelope-from ) id 1OwX2l-00041N-4U; Fri, 17 Sep 2010 10:15:43 +0100 X-Virus-Scanned: Debian amavisd-new at smtpbeckt01.t-mobile.co.uk Received: from localhost ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6BE9y3tQaHT; Fri, 17 Sep 2010 10:15:42 +0100 (BST) Received: from customer44214.102.kt.cust.t-mobile.co.uk ([178.102.172.189] helo=rya-online.net) by localhost with smtp (Exim 4.69) (envelope-from ) id 1OwX2j-00041B-AX; Fri, 17 Sep 2010 10:15:42 +0100 Received: (nullmailer pid 579 invoked by uid 1000); Fri, 17 Sep 2010 09:18:48 -0000 Date: Fri, 17 Sep 2010 10:18:48 +0100 (BST) To: Federico Lorenzi In-Reply-To: References: <4C876C14.2030300@FreeBSD.org> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1284715128.901194.134.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on localhost); SAEximRunCond expanded to false Cc: freebsd-bluetooth@freebsd.org Subject: Re: A2DP ? X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2010 09:39:14 -0000 On Wed, 8 Sep 2010, Federico Lorenzi wrote: > I seem to recall that getting it to work in userspace wouldn't be "much" > effort. Last I heard, the code for SCO sockets was a bit unstable, but > worked. You could in theory hook this up to something like gstreamer with > its sbc codec built in, or write your own program that encodes and send the > audio data. The SCO sockets are not required, since A2DP uses RFCOMM to transport data that I recall I'm not sure how audio management works in FreeBSD, wether just feeding the data to /dev/audio is enough or really if you need to make it available some other way. I have thought of doing something on NetBSD using the pad(4) driver[*] which would enable a daemon to provide a system standard audio interface (eg on /dev/audio2) that you can use with your favourite music player but have been distracted by other things. I have a pair of A2DP headphones that I can use to listen to music from my phone and it is kind of nice but I guess that there needs to be remote control interfaces with different music players too, perhaps they have them already..? iain [*] http://www.freebsd.org/cgi/man.cgi?query=pad&apropos=0&sektion=4&manpath=NetBSD+5.0&format=html From owner-freebsd-bluetooth@FreeBSD.ORG Fri Sep 17 18:16:17 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D1C7106566C for ; Fri, 17 Sep 2010 18:16:17 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id B88618FC16 for ; Fri, 17 Sep 2010 18:16:16 +0000 (UTC) Received: by gwb15 with SMTP id 15so1016025gwb.13 for ; Fri, 17 Sep 2010 11:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=gs0KXIVw3BNJMYV46MqDgRb/vwcwq2XGq2R/X8X9KHM=; b=fNYUPGwYR1HokrNBuQsOBcJ3X1rD6W/lfAeqykYxh7pEbjbhYlGwhH7+qnnYogWwc6 5qICNFOzJ26Ctc7mzjrjjGRsdsirAXqHY4TJEn1XasD13qFSrnaPl+wXaY6v7hEDoFmM FBlm1xhlhAbgp0PxzT8+QyJNL/zPLIJ0x7AkM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ZE23O56G+NyfQWTKb6jUJbebgyUwy+GUCsnQ3I1LVuhyocDjc3EQppz58IaQV6YmXF kaKN47lv5Np4BQZukKHI7lGjBr/CFNm/7MT/Po2002kmK7tSJUEvxxEnrivTkg+m7nyH +ZtTRut52x32KjSygkk6X0PPWkV4vCnx6EC4E= MIME-Version: 1.0 Received: by 10.150.190.9 with SMTP id n9mr6220783ybf.34.1284747375716; Fri, 17 Sep 2010 11:16:15 -0700 (PDT) Received: by 10.231.208.1 with HTTP; Fri, 17 Sep 2010 11:16:15 -0700 (PDT) In-Reply-To: <1284715128.901194.134.nullmailer@galant.ukfsn.org> References: <4C876C14.2030300@FreeBSD.org> <1284715128.901194.134.nullmailer@galant.ukfsn.org> Date: Fri, 17 Sep 2010 11:16:15 -0700 Message-ID: From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-bluetooth@freebsd.org Subject: Re: A2DP ? X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Sep 2010 18:16:17 -0000 On Fri, Sep 17, 2010 at 2:18 AM, Iain Hibbert wrote= : > On Wed, 8 Sep 2010, Federico Lorenzi wrote: > >> I seem to recall that getting it to work in userspace wouldn't be "much" >> effort. Last I heard, the code for SCO sockets was a bit unstable, but >> worked. You could in theory hook this up to something like gstreamer wit= h >> its sbc codec built in, or write your own program that encodes and send = the >> audio data. > > The SCO sockets are not required, since A2DP uses RFCOMM to transport dat= a > that I recall on later, i believe its l2cap actually :) on former, i agree, the exact quo= te =3D=3D The Advanced Audio Distribution Profile (A2DP) defines the protocols and procedures that realize distribution of audio content of high-quality in mono or stereo on ACL channels. The term =93advanced audio=94, therefore, should be distinguished from =93Bluetooth audio=94, which indicates distribution of narrow band voice on SCO channels as defined in Chapter 12 of Bluetooth Baseband specification. =3D=3D > I'm not sure how audio management works in FreeBSD, wether just feeding > the data to /dev/audio is enough or really if you need to make it i doubt it. audio said to be encoded in SBC (mandatory) with optional support for MPEG-1,2 Audio, MPEG-2,4 AAC and ATRAC (whatever that is). so decoding is needed, imo. > available some other way. I have thought of doing something on NetBSD > using the pad(4) driver[*] which would enable a daemon to provide a syste= m > standard audio interface (eg on /dev/audio2) that you can use with your > favourite music player but have been distracted by other things. yeah, i would do something like this too. no pad(4) on freebsd though :( > I have a pair of A2DP headphones that I can use to listen to music from m= y > phone and it is kind of nice but I guess that there needs to be remote > control interfaces with different music players too, perhaps they have > them already..? another exact quote :) =3D=3D Note also that the A2DP does not include remote control functions. Devices may support remote control features by implementing both A2DP and the control profile as depicted, for example, in the usage scenario of Audio/Video Remote Control Profile. =3D=3D thanks max From owner-freebsd-bluetooth@FreeBSD.ORG Sat Sep 18 08:46:42 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2317106566C for ; Sat, 18 Sep 2010 08:46:41 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smtp02.one2one.net (smtp02.one2one.net [149.254.192.174]) by mx1.freebsd.org (Postfix) with ESMTP id ACD058FC0A for ; Sat, 18 Sep 2010 08:46:36 +0000 (UTC) Received: from localhost ([127.0.0.1]) by localhost with esmtp (Exim 4.69) (envelope-from ) id 1Owt41-0000VW-3k; Sat, 18 Sep 2010 09:46:29 +0100 X-Virus-Scanned: Debian amavisd-new at smtpbeckt01.t-mobile.co.uk Received: from localhost ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SywujFloWI6k; Sat, 18 Sep 2010 09:46:28 +0100 (BST) Received: from customer26512.100.kt.cust.t-mobile.co.uk ([178.100.103.151] helo=rya-online.net) by localhost with smtp (Exim 4.69) (envelope-from ) id 1Owt3x-0000VL-V5; Sat, 18 Sep 2010 09:46:28 +0100 Received: (nullmailer pid 1070 invoked by uid 1000); Sat, 18 Sep 2010 08:49:25 -0000 Date: Sat, 18 Sep 2010 09:49:25 +0100 (BST) To: Maksim Yevmenkin In-Reply-To: References: <4C876C14.2030300@FreeBSD.org> <1284715128.901194.134.nullmailer@galant.ukfsn.org> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1284799765.805051.828.nullmailer@galant.ukfsn.org> From: Iain Hibbert X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: plunky@rya-online.net X-SA-Exim-Scanned: No (on localhost); SAEximRunCond expanded to false Cc: freebsd-bluetooth@freebsd.org Subject: Re: A2DP ? X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Sep 2010 08:46:42 -0000 On Fri, 17 Sep 2010, Maksim Yevmenkin wrote: > On Fri, Sep 17, 2010 at 2:18 AM, Iain Hibbert wrote: > > The SCO sockets are not required, since A2DP uses RFCOMM to transport data > > that I recall > > on later, i believe its l2cap actually :) on former, i agree, the exact quote Oops yes, seems that both AVCTP and AVDTP are plain L2CAP according to the SDP records on my phone: ServiceRecordHandle: 0x00010001 ServiceClassIDList: A/V Remote Control Target ProtocolDescriptorList: L2CAP (PSM 0x0017) AVCTP (v1.0) BluetoothProfileDescriptorList: A/V Remote Control, v1.0 AttributeID 0x0100: str8(34) "Audio Video Remote Control Profile" SupportedFeatures: Category 1 ServiceRecordHandle: 0x00010002 ServiceClassIDList: Audio Source ProtocolDescriptorList: L2CAP (PSM 0x0019) AVDTP (v1.0) BluetoothProfileDescriptorList: Advanced Audio Distribution, v1.0 AttributeID 0x0100: str8(4) "A2DP" I don't know if the AVDTP has any inbuilt flow control or if it relies upon a perfect link or advanced L2CAP features (I was always impressed with the RFCOMM credit based flow control) > i doubt it. audio said to be encoded in SBC (mandatory) with optional > support for MPEG-1,2 Audio, MPEG-2,4 AAC and ATRAC (whatever that is). > so decoding is needed, imo. Yes, my thought was that the daemon handles the Bluetooth connection and decoding to 16-bit signed linear (or, however the audio device wants to receive the raw data). This also conforms to the SBC algorithm licencing which if I recall covers Bluetooth applications only. > > available some other way. I have thought of doing something on NetBSD > > using the pad(4) driver[*] which would enable a daemon to provide a system > > standard audio interface (eg on /dev/audio2) that you can use with your > > favourite music player but have been distracted by other things. > > yeah, i would do something like this too. no pad(4) on freebsd though :( as I recall, Jared wrote pad(4) in a surprisingly short time and it doesn't look very complex though I think FreeBSDs kernel audio API is somewhat different. Additionally there is the issue of feeding audio data through userland but I think that even limited hardware devices (that are likely to be running BSD as an OS) are significantly more capable than the general purpose computers that were available 20 years ago and I'm not sure that its a serious issue any longer. Even my 3yr old phone runs at 233Mhz and seems to multitask in WM6 while playing music without skipping (much :) iain