From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] Add sdptool option for browsing with L2CAP_UUID
Date: Mon, 11 Apr 2005 18:22:36 +0200 [thread overview]
Message-ID: <1113236556.9655.60.camel@pegasus> (raw)
In-Reply-To: <1598723318.20050407211922@andric.com>
Hi Dimitry,
> > Maybe we should add somekind of short name to UUID translation function,
> > because the numeric values are hard to remember.
>
> Here's an easy hack: I reused the existing uuid16_names array for
> looking up (partial) matches. You can also get a list of recognized
> names. If you think it would be nicer to add a separate name list
> (i.e. made from the names in sdp.h), let me know.
this is really a hack ;)
I think that we need a special table for this, where we add short names
(and I mean short) for some UUIDs. Maybe it is enough to look up the
core protocol names like L2CAP, RFCOMM and OBEX. This would then also
make the --l2cap option obsolete. You can use "--uuid l2cap" for it.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-04-11 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 15:16 [Bluez-devel] [PATCH] Add sdptool option for browsing with L2CAP_UUID Dimitry Andric
2005-04-05 8:20 ` Johan Hedberg
2005-04-05 8:40 ` Peter Wippich
2005-04-05 15:27 ` Marcel Holtmann
2005-04-07 12:08 ` Dimitry Andric
2005-04-07 13:44 ` Marcel Holtmann
2005-04-07 19:19 ` Dimitry Andric
2005-04-11 16:22 ` Marcel Holtmann [this message]
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=1113236556.9655.60.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.