Linux bluetooth development
 help / color / mirror / Atom feed
From: "zhu yong" <zhuyong0003@gmail.com>
To: bluez-users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Help me! hciattach have no error msg, but hciconfig have no device msg.
Date: Tue, 28 Feb 2006 23:51:07 +0800	[thread overview]
Message-ID: <f64f4e8a0602280751l642cf100p5fdd6bd1a7413626@mail.gmail.com> (raw)

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

Hi, everyone
  I use one uare bluetooth device on my arm board. operation system is
uclinux, kernel is linux-2.4.24.
  I use hciattach cmd. There have no error msg.but I use hciconfig to
display devices, there have no devices info.
  I don't know why don't find device, any advice will help me!

  In addition, I use the same hciattach cmd on my pc, hciconfig can find the
device.

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

             reply	other threads:[~2006-02-28 15:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 15:51 zhu yong [this message]
2006-02-28 16:05 ` [Bluez-users] Help me! hciattach have no error msg, but hciconfig have no device msg Erwin Authried

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=f64f4e8a0602280751l642cf100p5fdd6bd1a7413626@mail.gmail.com \
    --to=zhuyong0003@gmail.com \
    --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