From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: bluez patch : Modify OPUSH sdp record when use sdptool for GOEP v2.0 From: Marcel Holtmann To: hui li Cc: linux-bluetooth , "haijun.liu" , steven.li@atheros.com, ruiyi.zhang@atheros.com, yang.wu@atheros.com, costa.yao@atheros.com, nami.li@atheros.com In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Fri, 20 May 2011 11:42:09 -0700 Message-ID: <1305916929.2681.12.camel@aeonflux> Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Hui, > Since GOEP v2.0 has some changes in sdp record, I`d like to add the > two changes in bluez for backwards compatibility with GOEP v1.x: > • The profile version number in the BluetoothProfileDescriptorList > attribute shall be incremented to match the version number of the > enhanced profile specification. If earlier versions of the profile do > not include this SDP attribute it shall be included in revised > versions. > • The SDP records shall include the GoepL2capPsm attribute. > > The upper text references Generic Object Exchange Profile v2.0. > The GoepL2capPsm attribute value can be found in Bluetooth SIG > Assigned Numbers – Service Discovery, and this value is 0x0200. > > My patch only define GoepL2capPsm and change OPUSH sdp record in > sdptool. I didn`t assign a new variable in svc_info_t struct to > indicate the new l2cap psm value, I used its original psm member to > indicate l2cap psm value. > Also, I didn`t found OPUSH l2cap psm default value in Bluetooth SIG > Assigned Numbers or its spec, so I just choose 0x1015 as its default > value. please do not update opush record details since we are using that one for qualification and I don't wanna redo all my SDP data. Just add an opush2 command to sdptool to add a GOEP 2.0 SDP record. Regards Marcel