From owner-freebsd-bluetooth@FreeBSD.ORG Fri Dec 10 10:23:02 2010 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 1005A106564A for ; Fri, 10 Dec 2010 10:23:02 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from mail.ukfsn.org (mail.ukfsn.org [77.75.108.10]) by mx1.freebsd.org (Postfix) with ESMTP id A008F8FC25 for ; Fri, 10 Dec 2010 10:23:00 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id C2B67DEC2E for ; Fri, 10 Dec 2010 09:59:57 +0000 (GMT) Received: from mail.ukfsn.org ([192.168.54.25]) by localhost (smtp-filter.ukfsn.org [192.168.54.205]) (amavisd-new, port 10024) with ESMTP id GHIIIVJpP8K4 for ; Fri, 10 Dec 2010 09:59:57 +0000 (GMT) Received: from galant.ukfsn.org (unknown [89.194.197.127]) by mail.ukfsn.org (Postfix) with ESMTP id C233DDEC3A for ; Fri, 10 Dec 2010 09:59:54 +0000 (GMT) Received: by galant.ukfsn.org (Postfix, from userid 1000) id 85B6C260261; Fri, 10 Dec 2010 09:59:49 +0000 (GMT) Date: Fri, 10 Dec 2010 09:59:49 +0000 (GMT) From: Iain Hibbert To: bluetooth@freebsd.org Message-ID: User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-609162667-1291975189=:1298" Cc: Subject: obexapp: handle 32-bit uuid in ProtocolDescriptorList 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, 10 Dec 2010 10:23:02 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-609162667-1291975189=:1298 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi I found that Mac OS X (10.3.5 at least, more recent probably not) provides a 32-bit UUID for L2CAP in the OBEX records, this defeats obexapp trying to send a file, eg from hcidump output < ACL data: handle 13 flags 0x02 dlen 24 L2CAP(d): cid 0x0040 len 20 [psm 1] SDP SSA Req: tid 0x1 len 0xf pat uuid-16 0x1106 (OBEXObjTrnsf) max 653 aid(s) 0x0004 - 0x0004 cont 00 > ACL data: handle 13 flags 0x02 dlen 40 L2CAP(d): cid 0x0044 len 36 [psm 1] SDP SSA Rsp: tid 0x1 len 0x1f count 28 record #0 aid 0x0004 (ProtocolDescList) < < uuid-32 0x0100 (L2CAP) > < uuid-16 0x0003 (RFCOMM) uint 0xf > < uuid-16 0x0008 (OBEX) > > cont 00 which returns 'Could not obtain RFCOMM channel' error patch attached fixes this.. regards, iain --0-609162667-1291975189=:1298 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=uuid.diff Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=uuid.diff LS0tIHNkcC5jCTIwMTAtMTAtMTkgMTg6NDg6MjcuMDAwMDAwMDAwICswMTAw DQorKysgc2RwLmMJMjAxMC0xMi0xMCAwOTozNDoxNS4wMDAwMDAwMDAgKzAw MDANCkBAIC0yMzAsNyArMjMwLDE2IEBAIHJmY29tbV9wcm90b19saXN0X3Bh cnNlKHVpbnQ4X3QgKnN0YXJ0LCANCiAJCQkJZ290byBuZXh0X3Byb3RvY29s Ow0KIAkJCWJyZWFrOw0KIA0KLQkJY2FzZSBTRFBfREFUQV9VVUlEMzI6ICAv KiBYWFggRklYTUUgY2FuIHdlIGhhdmUgMzItYml0IFVVSUQgKi8NCisJCWNh c2UgU0RQX0RBVEFfVVVJRDMyOg0KKwkJCWlmIChlbmQgLSBzdGFydCA8IDUp DQorCQkJCXJmY29tbV9wcm90b19saXN0X3BhcnNlX2V4aXQoRUlOVkFMKTsN CisNCisJCQlTRFBfR0VUMzIodmFsdWUsIHN0YXJ0KTsgbGVuIC09IHNpemVv Zih1aW50MzJfdCk7DQorCQkJaWYgKHZhbHVlICE9IFNEUF9VVUlEX1BST1RP Q09MX1JGQ09NTSkNCisJCQkJZ290byBuZXh0X3Byb3RvY29sOw0KKw0KKwkJ CWJyZWFrOw0KKw0KIAkJY2FzZSBTRFBfREFUQV9VVUlEMTI4OiAvKiBYWFgg RklYTUUgY2FuIHdlIGhhdmUgMTI4LWJpdCBVVUlEICovDQogCQlkZWZhdWx0 Og0KIAkJCXJmY29tbV9wcm90b19saXN0X3BhcnNlX2V4aXQoRU5PQVRUUik7 DQo= --0-609162667-1291975189=:1298--