linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth protocol question
Date: Mon, 03 Jul 2006 17:15:53 +0200	[thread overview]
Message-ID: <1151939753.12125.18.camel@localhost> (raw)
In-Reply-To: <be976db60606301615j2f7fe75n3ec26ead68ef724a@mail.gmail.com>

Hi Mark,

> I am somewhat new to Bluetooth and Bluez so this may be somewhat of a
> newbie question.
> 
> I have a bluetooth device that I am trying to write code to work with
> it on my Suse box.   In my log
> file, I see link_key_request, and then pin_code_request and then
> link_key_notify.  All seems successful. 
> And then after a few minutes I get this line in my system log:
> 
>   sdpd[8619]: close_sock:  Read error: Connection timed out
> 
> What is sdpd trying to do?  I think there must be something about the
> bluetooth protocol that I am missing. 
> Is sdpd trying to read data out of the device?   Is there a good doc
> somewhere I can understand the bluetooth protocol (handshake etc...)

run "hcidump -X -V" in another terminal and show us its output.

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

      reply	other threads:[~2006-07-03 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-30 23:15 [Bluez-users] bluetooth protocol question Mark S. Townsley
2006-07-03 15:15 ` 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=1151939753.12125.18.camel@localhost \
    --to=marcel@holtmann.org \
    --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;
as well as URLs for NNTP newsgroup(s).