From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid vs. hciconfig hci0 up
Date: Wed, 01 Dec 2004 20:05:15 +0100 [thread overview]
Message-ID: <1101927915.15615.13.camel@pegasus> (raw)
In-Reply-To: <BAY102-F210C30E45F8EA3793EF85AD2BF0@phx.gbl>
Hi Theresa,
> I got my server app running on an Axis developer's board 83 with the use of
> an RFCOMM socket on channel one for the BT comm. After flashing my board
> w/the new kernel (for BlueZ to work) I noticed I could not run the hcid
> daemon w/out the board either giving msgs about no kernel access to the
> device or even kernel panics when i put the hcid in a startup script. (For
> those familiar w/this board, I can do a network boot of the same image and
> it all works fine)
>
> I know this issue has nothing to do w/this list, but I wanted to know:
>
> What is the difference between running the hcid and using "hciconfig hci0
> up" to bring up the device. Since I cannot use hcid, I just use hciconfig
> to manually bring up the device and my app works fine. Whats the difference
> between the two? And is it better to use the daemon?
the hcid brings the device up and sets some more settings based on its
config file (for example name etc.).
Regards
Marcel
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-12-01 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 17:18 [Bluez-devel] hcid vs. hciconfig hci0 up theresa g.
2004-12-01 19:05 ` Marcel Holtmann [this message]
2004-12-01 21:02 ` theresa g.
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=1101927915.15615.13.camel@pegasus \
--to=marcel@holtmann.org \
--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