Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Stephen Crane <steve.crane@rococosoft.com>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] More SDP UUIDs...
Date: 17 Sep 2003 01:42:27 +0200	[thread overview]
Message-ID: <1063755753.29942.9.camel@pegasus> (raw)
In-Reply-To: <20030916195333.GA25068@bougret.hpl.hp.com>

Hi Jean,

> 	While you are at it, would you mid to do the following :
> 	o rename sdp_uuid_cmp() to sdp_uuid128_cmp(). The current name
> totally confused me.

who are the current users of sdp_uuid_cmp() ?

> 	Or make it two libraries.

The goal is to have only one Bluetooth library. But we care about the
embedded people, so comments are welcome.

> 	I hope you will keep the --tree browsing option in sdptool,
> because the default browsing is useless for advanced stuff. The
> display might be ugly, but at least it display everything and the
> basic infrastructure is sound.

Of course, because that is the only output that matters to me and I
don't find the tree output so ugly. This is an example output of my
Bluespoon headset from my code:

Sequence
        Attribute 0x0000 - Service record handle
                UINT32 0x00010000
        Attribute 0x0001 - Service class ID list
                Sequence
                        UUID16 0x1108 - Headset
                        UUID16 0x1203 - Generic Audio
        Attribute 0x0004 - Protocol descriptor list
                Sequence
                        Sequence
                                UUID16 0x0100 - L2CAP
                        Sequence
                                UUID16 0x0003 - RFCOMM
                                UINT8 0x01
        Attribute 0x0009 - Bluetooth profile descriptor list
                Sequence
                        Sequence
                                UUID16 0x1108 - Headset
                                UINT16 0x0100
        Attribute 0x0100
                String Headset
        Attribute 0x0302
                Bool True

Regards

Marcel




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2003-09-16 23:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 22:16 [Bluez-devel] [PATCH] More SDP UUIDs Jean Tourrilhes
2003-09-16 11:33 ` Marcel Holtmann
2003-09-16 13:03   ` David Woodhouse
2003-09-16 15:40     ` Fred Schättgen
2003-09-16 23:45       ` Marcel Holtmann
2003-09-17 11:34         ` Fred Schättgen
2003-09-19 16:52           ` Marcel Holtmann
2003-09-16 23:49     ` Marcel Holtmann
2003-09-17  6:22       ` David Woodhouse
2003-09-16 19:53   ` Jean Tourrilhes
2003-09-16 23:42     ` Marcel Holtmann [this message]
2003-09-17  0:06       ` Jean Tourrilhes
2003-09-17  0:28         ` Marcel Holtmann
2003-09-17  0:36           ` Jean Tourrilhes
2003-09-17  0:58             ` Marcel Holtmann

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=1063755753.29942.9.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=jt@hpl.hp.com \
    --cc=steve.crane@rococosoft.com \
    /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