public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Webster <pjwebster@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Porting BlueZ on embedded uClinux
Date: Mon, 15 Aug 2005 15:38:33 +1000	[thread overview]
Message-ID: <dc98d8d905081422386b5a5ae2@mail.gmail.com> (raw)
In-Reply-To: <E64BAD5A8AD46740828069A678D9DD73011A8C@netbe01.net.unimis>

>      You are right about BlueZ was not initilized. After I force define M=
ODULE in
> af_bluetooth.c , creating bluetooth socket using hciconfig is OK. But com=
mand "hciconfig
> -a" still can't read the bluetooth USB dongle information.

What about "hciconfig -a hci0"?


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-08-15  5:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15  5:10 [Bluez-devel] Porting BlueZ on embedded uClinux Al
2005-08-15  5:38 ` Paul Webster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-17  5:15 Al
2005-08-18  5:28 ` durai
2005-08-18  9:42 ` durai
2005-08-17  4:32 durai
2005-08-17  2:28 Al
2005-08-15 10:01 Al
2005-08-15 10:16 ` Peter Wippich
2005-08-15  6:13 Al
2005-08-15  7:22 ` durai
2005-08-15  2:44 Al
2005-08-12 10:02 Al
2005-08-12 12:34 ` Peter Wippich
2005-08-12  9:25 Al
2005-08-12  9:38 ` Peter Wippich
2005-08-12  8:39 Al
2005-08-12  9:01 ` Peter Wippich

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=dc98d8d905081422386b5a5ae2@mail.gmail.com \
    --to=pjwebster@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox