From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 1 15:09:46 2015 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67210E23 for ; Wed, 1 Apr 2015 15:09:46 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EAB64AD5 for ; Wed, 1 Apr 2015 15:09:45 +0000 (UTC) Received: by wixo5 with SMTP id o5so53008867wix.1 for ; Wed, 01 Apr 2015 08:09:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+qkuXXfCsHNS1ssDulns7NLty4ExPvu/QUVHJByOeWg=; b=Ag4dDBXdhm6+igtgpr4SldxelnmdVCUqum8fzzP/fKaC5PYEGwiTaXWJWrjkdCtqtI +hnNpCgN0OqltMGBZ3ymtaHQj8PfbhX2Pqcor9IHMlQJSYe5MZZ1E8NJ7cfBAjTmKS70 C6WW3z3WR3Cns+9eK5f+L+4IpE86IysmCdCt5b1Vzeauzm4tJGZmzvMGjO9nOkP7va7u Szm7bUk4IM6SIRMtWl2xqk49XA1AFTnUvN1BrJjX3+YwS5fpNWFtlwRIlKuz4ihLrbWp p0VIKLfcDQFjtITPumYH9tjHu4XLmzA+Q9SQsEFyQLmM+p9byl4XquxEBVRnCTwzxnvm opRg== MIME-Version: 1.0 X-Received: by 10.180.104.35 with SMTP id gb3mr15983730wib.60.1427900984478; Wed, 01 Apr 2015 08:09:44 -0700 (PDT) Received: by 10.27.91.75 with HTTP; Wed, 1 Apr 2015 08:09:44 -0700 (PDT) In-Reply-To: References: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> Date: Wed, 1 Apr 2015 08:09:44 -0700 Message-ID: Subject: Re: register HID with SDP error From: Waitman Gobble To: Maksim Yevmenkin Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-bluetooth@freebsd.org" , Iain Hibbert X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 15:09:46 -0000 On Wed, Apr 1, 2015 at 8:05 AM, Maksim Yevmenkin wrote: > Hello, > > [...] > >> Can this 'syntax error' problem be related to the requested MTU? >> >> with essentially the 'same' connection request, >> >> here's the transaction log from an MS Windows client. No syntax >> errors. The requested MTU is 1024 >> >> https://gist.github.com/waitman/2d5a72e9f9544848e832 >> >> L2CAP(d): cid 0x40 len 346 [psm 1] >> >> >> and a log from android client. Requested MTU is 256. >> >> https://gist.github.com/waitman/e365debcd4a96d849153 >> >> L2CAP(d): cid 0x43 len 247 [psm 1] >> >> note it's bombing out with something about aid 0x0200, which isn't >> actually an aid specified in my 0x1124 record. > > just a wild guess. please make sure that you maintain continuation > state properly. when sdp response is bigger than l2cap mtu, response > is chunked. > > thanks, > max Thank you, I was tinkering with things for awhile to try to find out why I was seeing 'syntax errors', but I'm thinking now there isn't a syntax error with the record, it's the hcidump program reading the broken up response. -- Waitman Gobble Los Altos California USA 510-830-7975