Linux bluetooth development
 help / color / mirror / Atom feed
From: Zia Syed <zs@comp.rgu.ac.uk>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] PAN and Device Lookup Problem- Still no luck :(
Date: Fri, 23 Jan 2004 21:53:30 +0000	[thread overview]
Message-ID: <1074894810.6320.16.camel@zs> (raw)

Well guys!, after whole day effort, i still couldn't manage to get PAND
and device discovery to work together. I'm using Zaurus SL5500 with
kernel 2.4.18-rmk7-pxa3-embedix. As i said before, stack works fine
until when I connect to NAP, after that I can't do device lookup. Only
after killing the PANU session, i can do the "hcitool scan". Otherwise
it gives me error saying "Inquiry failed: Device or resource busy".

I'm really stuck now as my application which was working till last night
but now with this problem I can't go any further. My application need
both PAN (for fetching web-contents) and device lookup for discovering
nearby devices. 

What do you guys suggest I should do? I've tried installing different
versions of bluez packages (from sf.net and from community.zaurus.com). 

I'm using Socket CF (G Series) Bluetooth card. Is there anyone out there
using the same device settings with Bluez?

Please advice!

Thanks
Zia



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

                 reply	other threads:[~2004-01-23 21:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1074894810.6320.16.camel@zs \
    --to=zs@comp.rgu.ac.uk \
    --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