public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Markus Becker <mab@comnets.uni-bremen.de>
Subject: Re: [Bluez-devel] [PATCH] bluez-libs UUID-128 support for Protocol	Descriptor List
Date: Wed, 23 Aug 2006 19:35:54 +0200	[thread overview]
Message-ID: <1156354555.4133.42.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0608211349380.27134-200000@bugs.comnets.uni-bremen.de>

Hi Markus,

> I've created a patch for bluez-libs/src/sdp.c to support the finding of
> UUID128 encoded protocols. So that also kdebluetooth and others can
> recognize those protocols. It changes the display of the Protocol
> Descriptor List for example from:
> 
> Service Name: ATEmulator
> Service RecHandle: 0x10010
> Service Class ID List:
>   "Error: This is UUID-128" (0x7dd6b763-99a9-4a92-87b5-bc8efe565c37)
>   "Error: This is UUID-128" (0x00001101-0000-1000-8000-00805f9b34fb)
> Protocol Descriptor List:
>   "Error: " (0x00000100-0000-1000-8000-00805f9b34fb)
>   "Error: " (0x00000003-0000-1000-8000-00805f9b34fb)
>     Channel: 25
> 
> to:
> 
> Service Name: ATEmulator
> Service RecHandle: 0x10010
> Service Class ID List:
>   UUID 128: 7dd6b763-99a9-4a92-87b5-bc8efe565c37
>   UUID 128: 00001101-0000-1000-8000-00805f9b34fb
> Protocol Descriptor List:
>   "L2CAP" (0x00000100-0000-1000-8000-00805f9b34fb)
>   "RFCOMM" (0x00000003-0000-1000-8000-00805f9b34fb)
>     Channel: 25
> 
> Please consider it for integration into mainline bluez-libs.

the patch is wrong. Before you are doing a lookup against the short
UUIDs of Bluetooth you should check if the base UUID is the Bluetooth
base UUID. Otherwise you can't do the lookup.

Regards

Marcel



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-08-23 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 12:28 [Bluez-devel] [PATCH] bluez-libs UUID-128 support for Protocol Descriptor List Markus Becker
2006-08-23 17:35 ` Marcel Holtmann [this message]
2006-08-24 10:35   ` Markus Becker
2006-08-24 14:43     ` Marcel Holtmann
2006-08-24 13:51       ` Markus Becker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1156354555.4133.42.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=mab@comnets.uni-bremen.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox