Linux bluetooth development
 help / color / mirror / Atom feed
From: Ka Kin Cheung <michaelhku2002@yahoo.com.hk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] adding a sdp service with a 128bit uuid
Date: Tue, 8 Mar 2005 20:35:26 +0800 (CST)	[thread overview]
Message-ID: <20050308123527.49819.qmail@web60910.mail.yahoo.com> (raw)
In-Reply-To: 6667

[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]

Hi Marco!
    Can you send the program you wrote to me for reference? Or can you tell briefly the algorithm about the program you wrote about adding a service profile, especially for which functions in sdptool.c are nneded? Thank you very much.
Michael

Marco Trudel <mtrudel@gmx.ch> wrote:
Hello everybody

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]?

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.

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?
I asked google and he (she?) told me this:
http://www.xgarreau.org/aide/devel/bluetooth/timeserver.c
but it seems a little big for me...


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



---------------------------------
Yahoo! 工具列 - 內置防止彈出視窗工能!

[-- Attachment #2: Type: text/html, Size: 2601 bytes --]

             reply	other threads:[~2005-03-08 12:35 UTC|newest]

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