Linux bluetooth development
 help / color / mirror / Atom feed
From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] adding a sdp service with a 128bit uuid
Date: Sat, 05 Mar 2005 14:24:30 +0100	[thread overview]
Message-ID: <4229B30E.8080803@gmx.ch> (raw)
In-Reply-To: <1110021688.8058.108.camel@pegasus>



Marcel Holtmann wrote:
> Hi Marco,
> 
> 
>>by reading sdptool.c, I was able to write a little program that promotes my 
>>service. Realising this, 3 questions arised:
>>
>>1. general:
>>how to browse the local sdp services?
>>[sdptool browse dev] seems to be only for remote devices. I now always did 
>>it from another device to see the local seervices. how to [sdptool browse 
>>localhost]?
> 
> 
> sdptool browse local

nice :-)
maybe something that should/could be mentioned in the manpage or in --help

>>2. from add_sp(...) in sdptool.c, changing:
>>  # sdp_uuid16_create(&sp_uuid, SERIAL_PORT_SVCLASS_ID);
>>into:
>>  # sdp_uuid128_create(&sp_uuid, a128bitUUID);
>>gives me (if I do [sdptool browse from the other device]):
>>  # Service Class ID List:
>>  #   "Error: This is uuid128" (0x0a333444-5556-6677-7888-9aa99000a1a1)
>>Actually it works well. But why is it saying "Error: ..."? I noticed that 
>>using the avetana jsr82 implementation (that uses bluez), and creating a 
>>sdp entry with a 128bit uuid, it shows the same error.
> 
> 
> This is because the friend display (without --tree) don't understand
> UUID 128 and don't knows how to translate it into a service.

nice again. this solves my proglem that never existed :-)
maybee another thing to mention in the manpage...

>>3. actually this is more a c then a bluez question, but i'd appreciate if 
>>someone could tell it nevertheless:
>>  # sdp_uuid32_create(uuid_t *uuid, uint32_t data);
>>  # sdp_uuid128_create(uuid_t *uuid, const void *data);
>>the second function takes the uuid as "const void *data". What is the 
>>appropriate way to give a uuid like 2c3ef0c843674369b1dfb7315e76332a to 
>>that function?
> 
> 
> Using "unsigned char uuid[16]" and then casting with "(void *)" worked
> for me.

actually, i've a long representation of my uuid. but i'm willing to try!
using 0x233438787A233438787A233438787A23 as long uuid and an ascii table 
gives me: "#48xz#48xz#48xz#" for a char representation of the uuid and it 
works! :-)

but unfortunately that's an invented uuid to avoid control-chars. my uuid 
has values as 0x0F -> that's a SI (left shift) in the ascii table.
so i did:

unsigned char uuid[] = { 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08,
                          0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10 };

and it works as too. is this what you meant?


thanks a lot for the short and precise answers! it's always a pleasure!

regards
Marco


-------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-03-05 13:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05  1:50 [Bluez-users] adding a sdp service with a 128bit uuid Marco Trudel
2005-03-05 11:21 ` Marcel Holtmann
2005-03-05 13:24   ` Marco Trudel [this message]
2005-03-05 13:38     ` Marcel Holtmann
2005-03-06  8:11       ` Taneli Vähäkangas
2005-03-06 11:19         ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2005-03-08 12:35 Ka Kin Cheung
2005-03-08 13:03 ` Marco Trudel
2005-03-08 13:39 ` Xavier Garreau

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=4229B30E.8080803@gmx.ch \
    --to=mtrudel@gmx.ch \
    --cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox