From owner-freebsd-bluetooth@FreeBSD.ORG Thu Dec 9 18:10:19 2004 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BCDC16A4CE for ; Thu, 9 Dec 2004 18:10:19 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36AC943D1F for ; Thu, 9 Dec 2004 18:10:19 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])iB9IA4sH007130; Thu, 9 Dec 2004 12:10:04 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 9 Dec 2004 12:09:58 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 9 Dec 2004 12:09:48 -0600 Message-ID: <41B894EB.5000908@savvis.net> Date: Thu, 09 Dec 2004 10:09:47 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tuc at Beach House References: <200412091738.iB9HcXUV014010@himinbjorg.tucs-beachin-obx-house.com> In-Reply-To: <200412091738.iB9HcXUV014010@himinbjorg.tucs-beachin-obx-house.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Dec 2004 18:09:48.0769 (UTC) FILETIME=[45609510:01C4DE1A] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org cc: Tuc at Beach House Subject: Re: sdpcontrol issues (LONG) X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 18:10:19 -0000 Tuc at Beach House wrote: >>could you please attach hcidump? >> > Sorry. no problem. but,i think, you did not comment out original code, i.e you just added SDP_ATTR_RANGE( 0, 1 ), SDP_ATTR_RANGE( 3, 4 ), SDP_ATTR_RANGE( 8, 9 ), on top. you *need* to *comment out* (or remove) the following part SDP_ATTR_RANGE( SDP_ATTR_SERVICE_RECORD_HANDLE, SDP_ATTR_SERVICE_RECORD_HANDLE), SDP_ATTR_RANGE( SDP_ATTR_SERVICE_CLASS_ID_LIST, SDP_ATTR_SERVICE_CLASS_ID_LIST), SDP_ATTR_RANGE( SDP_ATTR_PROTOCOL_DESCRIPTOR_LIST, SDP_ATTR_PROTOCOL_DESCRIPTOR_LIST), SDP_ATTR_RANGE( SDP_ATTR_BLUETOOTH_PROFILE_DESCRIPTOR_LIST, SDP_ATTR_BLUETOOTH_PROFILE_DESCRIPTOR_LIST) the dump shows < ACL data: handle 0x002a flags 0x02 dlen 56 L2CAP(d): cid 0x40 len 52 [psm 1] SDP SSA Req: tid 0x0 len 0x2f pat uuid-16 0x1105 (OBEXObjPush) max 0xffff aid(s) 0x0000 - 0x0001 0x0003 - 0x0004 0x0008 - 0x0009 0x0000 - 0x0000 0x0001 - 0x0001 0x0004 - 0x0004 0x0009 - 0x0009 cont 00 i.e. sdpcontrol(8) still sends attribute id ranges that consist of only one attribute - the problem still there. i want to see something like < ACL data: handle 0x002a flags 0x02 dlen 56 L2CAP(d): cid 0x40 len 52 [psm 1] SDP SSA Req: tid 0x0 len 0x2f pat uuid-16 0x1105 (OBEXObjPush) max 0xffff aid(s) 0x0000 - 0x0001 0x0003 - 0x0004 0x0008 - 0x0009 cont 00 thanks, max