From owner-freebsd-bluetooth@FreeBSD.ORG Sun Sep 2 18:23:50 2007 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89C8D16A418 for ; Sun, 2 Sep 2007 18:23:50 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (muon.bluestop.org [80.68.94.188]) by mx1.freebsd.org (Postfix) with ESMTP id 6DF1713C442 for ; Sun, 2 Sep 2007 18:23:50 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.draftnet (dyn-62-56-57-198.dslaccess.co.uk [62.56.57.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id 9DBBB3000D for ; Sun, 2 Sep 2007 18:58:25 +0100 (BST) Message-ID: <46DAFA61.9020705@cran.org.uk> Date: Sun, 02 Sep 2007 19:01:05 +0100 From: Bruce Cran User-Agent: Thunderbird 2.0.0.6 (X11/20070809) MIME-Version: 1.0 To: bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Warning messages when inserting BCM92045DG dongle 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: Sun, 02 Sep 2007 18:23:50 -0000 Hi, I'm running 7-CURRENT AMD64 (built yesterday) and just tried inserting a Broadcom BCM92045DG dongle after kldloading the ng_ubt module. I got a couple of warning messages: ubt0: on uhub1 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=49; nframes=6, buffer size=294 WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() WARNING: attempt to net_add_domain(netgraph) after domainfinalize() Are these expected? -- Bruce Cran From owner-freebsd-bluetooth@FreeBSD.ORG Sun Sep 2 20:00:09 2007 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 1DAE016A420 for ; Sun, 2 Sep 2007 20:00:09 +0000 (UTC) (envelope-from peter@stuge.se) Received: from foo.birdnet.se (foo.birdnet.se [213.88.146.6]) by mx1.freebsd.org (Postfix) with ESMTP id 7B36E13C459 for ; Sun, 2 Sep 2007 20:00:08 +0000 (UTC) (envelope-from peter@stuge.se) Received: (qmail 15489 invoked by uid 501); 2 Sep 2007 19:33:27 -0000 Message-ID: <20070902193327.15488.qmail@stuge.se> Date: Sun, 2 Sep 2007 21:33:27 +0200 From: Peter Stuge To: gammu-users@lists.sourceforge.net Mail-Followup-To: gammu-users@lists.sourceforge.net, Maksim Yevmenkin , freebsd-bluetooth@freebsd.org, bsam@FreeBSD.org References: <20070816105005.GA24403@harmless.hu> <20070817113053.GA61263@harmless.hu> <20070818133634.GA1448@harmless.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070818133634.GA1448@harmless.hu> Cc: freebsd-bluetooth@freebsd.org, bsam@FreeBSD.org Subject: Re: FBSD bt gammu [was:Nokia 6310i and gammu] 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: Sun, 02 Sep 2007 20:00:09 -0000 On Sat, Aug 18, 2007 at 03:36:34PM +0200, Gergely CZUCZY wrote: > On Sat, Aug 18, 2007 at 02:15:59PM +0200, Michal ??iha?? wrote: > > Gammu does have support for Linux and Win32 bluetooth stack only for > > now, however you're welcome to send patches for others ;-). > > Please consider the following message from Maksim Yevmenkin. > Personally, I haven't checked all the details myself, but he might > have pointed out something important. There are no details, unfortunately. > On Fri, Aug 17, 2007 at 12:00:02PM -0700, Maksim Yevmenkin wrote: > > i just installed gammu-1.12.0 from ports and was able to make it > > work with my se k700i. Sweet! > > there is a problem with the gammu-1.12.0 port because gammu > > developers switched to new configuration system (cmake) and it no > > longer able to detect bluetooth support on freebsd. i had to hack > > gammu port to convince it to detect bluetooth support, and once > > i've done it, it worked. Could you let us know what you needed to do to make bluetooth work on FBSD? I'd be happy to see that included into the source. > > the above is NOT a problem with bluetooth. this is a problem with > > gammu port. Yes, completely correct. I hope noone got the wrong impression from the gammu list. > > please email gammu port maintainer (or possibly gammu developers > > directly) and ask them to address this issue. I don't think any gammu developers know FBSD so hints with technical details about what is needed to make it play are very welcome. //Peter From owner-freebsd-bluetooth@FreeBSD.ORG Mon Sep 3 15:55:37 2007 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63A9616A421 for ; Mon, 3 Sep 2007 15:55:37 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id EB4F013C494 for ; Mon, 3 Sep 2007 15:55:36 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by nf-out-0910.google.com with SMTP id k4so1192259nfd for ; Mon, 03 Sep 2007 08:55:35 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Y6ZTmyhDBLQTlhQXnYc3IRwvHtJQBnL0SFn7l7hB0PXAG6Om6XNhFjG3iuqu4MSKH5iqf4sMPuyh9HwMWO1yw877V4iPccusmJX1+le2E3FlTypWwvuqemM8zB83+nETXNgOOIBgCFWBpFb1bfjKZVXTPRZCIGOsV+lqPtGbe7Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=s+xRubayGOCtKFBWrxCssm7/SBW0D8IQJb7/RI+kLmR4Hn5mY5LhvxHUHPjyMsNzUthEgLmrWruywqWfMHbsKFyu3VWuMtCf8eag4RIusOZjLulLXVBV5WQqGzjD9TmPjvdrtu+6ndyxIfHHjAuph2DshS6txDwlYH0btmMy798= Received: by 10.86.28.5 with SMTP id b5mr3530655fgb.1188834935482; Mon, 03 Sep 2007 08:55:35 -0700 (PDT) Received: by 10.86.63.16 with HTTP; Mon, 3 Sep 2007 08:55:35 -0700 (PDT) Message-ID: Date: Mon, 3 Sep 2007 08:55:35 -0700 From: "Maksim Yevmenkin" To: "Bruce Cran" In-Reply-To: <46DAFA61.9020705@cran.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46DAFA61.9020705@cran.org.uk> Cc: bluetooth@freebsd.org Subject: Re: Warning messages when inserting BCM92045DG dongle 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, 03 Sep 2007 15:55:37 -0000 On 9/2/07, Bruce Cran wrote: > Hi, > > I'm running 7-CURRENT AMD64 (built yesterday) and just tried inserting a > Broadcom BCM92045DG dongle after kldloading the ng_ubt module. I got a > couple of warning messages: > > ubt0: addr 2> on uhub1 > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3; > wMaxPacketSize=49; nframes=6, buffer size=294 > WARNING: attempt to net_add_domain(bluetooth) after domainfinalize() > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > > Are these expected? > yes. as far as i can tell, its not a problem. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Sep 3 16:22:11 2007 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4778316A417 for ; Mon, 3 Sep 2007 16:22:11 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id BFB2313C442 for ; Mon, 3 Sep 2007 16:22:10 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by nf-out-0910.google.com with SMTP id k4so1197312nfd for ; Mon, 03 Sep 2007 09:22:09 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dfX3vKNqSeKSfG/J4AllFGV2cL8+90JC94Eoik39+rcTjqp5Kb23+uXFAKLD5h8rID/YJiIoC7KdFIhdAXni5o3ieDqxr7X1LTCsAIUuzh1fO0ayvYlvjhA3q3SnT01RnTbCjcpFRrm2uhVZtQifstqDHYzOoOOiqwfJxn3poh4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Bed/Q+jgSj6A/Zv1OtkAU7Lgy6GyZhwmq025CfpL45C2PeY1fARXbk5I3lcrRF5/M4QNoW3rC2yCEEqHCjC25kejm4446V/WfIXa7+dpI1Q/UZ7N3E2fPY0GuG0yOzr6kebgrw9BN7bESg9L/38omiKtSXyyFUvFVgdza53+AA8= Received: by 10.86.62.3 with SMTP id k3mr3552922fga.1188836529369; Mon, 03 Sep 2007 09:22:09 -0700 (PDT) Received: by 10.86.63.16 with HTTP; Mon, 3 Sep 2007 09:22:09 -0700 (PDT) Message-ID: Date: Mon, 3 Sep 2007 09:22:09 -0700 From: "Maksim Yevmenkin" To: "Iain Hibbert" In-Reply-To: <1188587788.301999.1317.nullmailer@galant.ukfsn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46D744B3.8080107@ab.ote.we.lv> <1188587788.301999.1317.nullmailer@galant.ukfsn.org> Cc: "Eugene M. Kim" , FreeBSD Bluetooth Mailing List Subject: Re: One AF_* constant for each of sockaddr_{hci,l2cap,rfcomm}? 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, 03 Sep 2007 16:22:11 -0000 On 8/31/07, Iain Hibbert wrote: > On Thu, 30 Aug 2007, Maksim Yevmenkin wrote: > > > On 8/30/07, Eugene M. Kim wrote: > > > Hello, > > > > > > It seems that AF_BLUETOOTH ambiguously identifies three different types > > > of socket?HCI, L2CAP and RFCOMM?each with its own sockaddr_* type. This > > > deviates from the standard practice where there is a 1:1 mapping between > > > an AF_* constant and a corresponding sockaddr_* type, and this may, in > > > turn, break usage of system calls such as getsockname(2) and > > > getpeername(2): These calls return a struct sockaddr whose sa_family > > > should uniquely and unambiguously identify the real sockaddr_* struct to > > > which the returned sockaddr should be type-cast; if sa_family == > > > AF_BLUETOOTH, there are three possibilities and an application that > > > calls get{sock,peer}name(2) cannot choose one of them without extra > > > information (namely, the third argument to the socket() call that > > > created the socket). > > > > the application probably can use sa_len field to figure out which > > sockaddr_ structure it is. it is somewhat a hack but it should work. > > Seems dangerous to me. What if the architecture* does not have byte > aligned memory access, and the compiler expands the uint8_t's to words? > l2cap and rfcomm would become the same length in that case. > > * (I don't know if there exists such an architecture in common use.. :) i did say it was a hack :) > > > In this light, shouldn't a unique AF_* constant be allocated for each > > > Bluetooth socket type, such as AF_BTHCI, AF_BTL2CAP and AF_BTRFCOMM, > > > instead of just one AF_BLUETOOTH? > > > > i'd rather not to it. may be it is better to add sa_proto field to > > bluetooth sockaddr_ structures and have union data field for each > > protocol? > > better (IMHO :) if you are breaking backwards compatibility, to use the > structure that NetBSD is already using for all AF_BLUETOOTH socket > addresses: > > /* > * Socket address used by Bluetooth protocols > */ > struct sockaddr_bt { > uint8_t bt_len; > sa_family_t bt_family; > bdaddr_t bt_bdaddr; > uint16_t bt_psm; > uint8_t bt_channel; > uint8_t bt_zero[5]; > }; > > (unused fields are ignored by protocols and should be set to zero) well, going back to the original email, i'm not sure what author is trying to do. lets say it is for a hypothetical application that has access to the socket file descriptor and wants to identify protocol (socket type) behind the socket and print some information (for example lsof of something like that). if that is the case, then yes, AF_BLUETOOTH does not tell you which protocol (socket type) is used. however, neither does sockaddr_bt from netbsd, and, for that matter, neither does sockaddr_in. getsockname() does not tell you anything about protocol (socket type) (for example IPPROTO_TCP vs. IPPROTO_UDP). that is why i suggested so_proto field. i can see how netbsd's sockaddr_bt could be more convenient (or confusing depending on one's point of view) for a programmer. if author of the original email was simply making an observation, that is ok too. thanks, max > > regards, > iain > From owner-freebsd-bluetooth@FreeBSD.ORG Wed Sep 5 09:18:54 2007 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 126D116A418 for ; Wed, 5 Sep 2007 09:18:54 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id EC7F713C4E1 for ; Wed, 5 Sep 2007 09:18:53 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1ISqmQ-0007Mt-9y for freebsd-bluetooth@freebsd.org; Wed, 05 Sep 2007 02:02:34 -0700 Message-ID: <12494324.post@talk.nabble.com> Date: Wed, 5 Sep 2007 02:02:34 -0700 (PDT) From: susan To: freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: pixinxin@126.com Subject: Do you want to get Bluetooth Software Vista Compatible? 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: Wed, 05 Sep 2007 09:18:54 -0000 Please use Bluesoleil Software .It can transfer your ringtones wirelessly. IVT released its latest Bluetooth PC software BlueSoleil V3.0 supports Windows Vista on April 6,2007. Click http://www.bluesoleil.com/vista_download10.asp for more experience! There are also a lot of high quality Bluetooth hardware products, such as adapter, mouse, carkit, headsets and so on. http://www.bluesoleil.com -- View this message in context: http://www.nabble.com/Do-you-want-to-get-Bluetooth-Software-Vista-Compatible--tf4382901.html#a12494324 Sent from the freebsd-bluetooth mailing list archive at Nabble.com. From owner-freebsd-bluetooth@FreeBSD.ORG Wed Sep 5 16:56:40 2007 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 8807B16A419 for ; Wed, 5 Sep 2007 16:56:40 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 0C45513C442 for ; Wed, 5 Sep 2007 16:56:39 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by nf-out-0910.google.com with SMTP id k4so1747783nfd for ; Wed, 05 Sep 2007 09:56:26 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z3yBv4/hkKpY7x2QYRXhL7pyk86Qu3alijtTrt4AHhNXR+1YnXs6C3wFXFRVAufDnSMGLPUJHTpZ+BqWOeL2kpr6aTzq0wc24vm7WTYGWXwcGSSktetUQOaAPzZpuuj5M47ueUFK7loGvE6Jqpk+3Pl6PBOvbNtyTBy1Lc8PWG0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hVeSZ7RhL2s8qxyVraf74bE+BE7D7hVE8fCukasuL8wM/YoqU9i0jJpjEtxaCsZkn+u96ZSyNceqCADDY0+t9zdjHS404Gst44BDUIsYsylQn/a49//zwy/2bExsHHuIfuwBlUn/D8U+uePKjhwySogXm6pgOjt/RU39ZtYEeWQ= Received: by 10.86.76.16 with SMTP id y16mr5324794fga.1189011386562; Wed, 05 Sep 2007 09:56:26 -0700 (PDT) Received: by 10.86.63.16 with HTTP; Wed, 5 Sep 2007 09:56:26 -0700 (PDT) Message-ID: Date: Wed, 5 Sep 2007 09:56:26 -0700 From: "Maksim Yevmenkin" To: gammu-users@lists.sourceforge.net, freebsd-bluetooth@freebsd.org, bsam@freebsd.org In-Reply-To: <20070902193327.15488.qmail@stuge.se> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070816105005.GA24403@harmless.hu> <20070817113053.GA61263@harmless.hu> <20070818133634.GA1448@harmless.hu> <20070902193327.15488.qmail@stuge.se> Cc: Subject: Re: FBSD bt gammu [was:Nokia 6310i and gammu] 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: Wed, 05 Sep 2007 16:56:40 -0000 Peter, thanks for the reply and sorry for the delay with answering to your email. please read my comments inline. On 9/2/07, Peter Stuge wrote: > On Sat, Aug 18, 2007 at 03:36:34PM +0200, Gergely CZUCZY wrote: > > On Sat, Aug 18, 2007 at 02:15:59PM +0200, Michal ??iha?? wrote: > > > Gammu does have support for Linux and Win32 bluetooth stack only for > > > now, however you're welcome to send patches for others ;-). > > > > Please consider the following message from Maksim Yevmenkin. > > Personally, I haven't checked all the details myself, but he might > > have pointed out something important. > > There are no details, unfortunately. Boris Samorodov (bsam@freebsd.org) did all the work to port gammu bluetooth onto freebsd. he is the gammu's port maintainer. all his patches can be found at http://www.freebsd.org/cgi/cvsweb.cgi/ports/comms/gammu/ (actual patches at http://www.freebsd.org/cgi/cvsweb.cgi/ports/comms/gammu/files/) bsam's patches work on gammu version 1.13.0, however cmake scripts do not have support for detecting bluetooth on freebsd. i'm not familiar with cmake, so i simply applied bsam's patches and hacked cmake generated .h files to enable relevant bluetooth defines. once i compiled hacked version, bluetooth worked fine. > > > there is a problem with the gammu-1.12.0 port because gammu > > > developers switched to new configuration system (cmake) and it no > > > longer able to detect bluetooth support on freebsd. i had to hack > > > gammu port to convince it to detect bluetooth support, and once > > > i've done it, it worked. > > Could you let us know what you needed to do to make bluetooth work on > FBSD? I'd be happy to see that included into the source. please take a look at bsam's patches to see if they can be included into gammu please modify cmake scripts so it can properly detect bluetooth on freebsd > > > please email gammu port maintainer (or possibly gammu developers > > > directly) and ask them to address this issue. > > I don't think any gammu developers know FBSD so hints with technical > details about what is needed to make it play are very welcome. please feel free to ask in freebsd-bluetooth@freebsd.org any questions you might have thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Sep 6 06:05:31 2007 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 856F316A41B for ; Thu, 6 Sep 2007 06:05:31 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from mail.ipt.ru (mail.ipt.ru [194.62.233.102]) by mx1.freebsd.org (Postfix) with ESMTP id 3B5EA13C442 for ; Thu, 6 Sep 2007 06:05:31 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from srv.sem.ipt.ru ([192.168.12.1] helo=ipt.ru) by mail.ipt.ru with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1IT9p7-000BlW-31; Thu, 06 Sep 2007 09:22:37 +0400 Received: from bsam by ipt.ru with local (Exim 4.63 (FreeBSD)) (envelope-from ) id 1IT9ro-0000Ci-14; Thu, 06 Sep 2007 09:25:24 +0400 To: "Maksim Yevmenkin" References: <20070816105005.GA24403@harmless.hu> <20070817113053.GA61263@harmless.hu> <20070818133634.GA1448@harmless.hu> <20070902193327.15488.qmail@stuge.se> From: Boris Samorodov Date: Thu, 06 Sep 2007 09:25:24 +0400 In-Reply-To: (Maksim Yevmenkin's message of "Wed\, 5 Sep 2007 09\:56\:26 -0700") Message-ID: <45283323@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.99 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-bluetooth@freebsd.org, gammu-users@lists.sourceforge.net Subject: Re: FBSD bt gammu 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: Thu, 06 Sep 2007 06:05:31 -0000 On Wed, 5 Sep 2007 09:56:26 -0700 Maksim Yevmenkin wrote: > please modify cmake scripts so it can properly detect bluetooth on freebsd Michal incorporated all FreeBSD patches to svn version. All bluetooth functions except channel searching (switched off for FreeBSD) should work fine. Those who are interested may test it and give a feedback. Those who are interested may look into channel searching problem and produce patches. ;-) Thanks. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve