* [Bluez-devel] hcid vs. hciconfig hci0 up
@ 2004-12-01 17:18 theresa g.
2004-12-01 19:05 ` Marcel Holtmann
0 siblings, 1 reply; 3+ messages in thread
From: theresa g. @ 2004-12-01 17:18 UTC (permalink / raw)
To: bluez-devel
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?
Thanks in advance,
Theresa
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] hcid vs. hciconfig hci0 up
2004-12-01 17:18 [Bluez-devel] hcid vs. hciconfig hci0 up theresa g.
@ 2004-12-01 19:05 ` Marcel Holtmann
2004-12-01 21:02 ` theresa g.
0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2004-12-01 19:05 UTC (permalink / raw)
To: BlueZ Mailing List
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Bluez-devel] hcid vs. hciconfig hci0 up
2004-12-01 19:05 ` Marcel Holtmann
@ 2004-12-01 21:02 ` theresa g.
0 siblings, 0 replies; 3+ messages in thread
From: theresa g. @ 2004-12-01 21:02 UTC (permalink / raw)
To: bluez-devel
Thanks!
theresa
----Original Message Follows----
From: Marcel Holtmann <marcel@holtmann.org>
Reply-To: bluez-devel@lists.sourceforge.net
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
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
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-12-01 21:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-01 17:18 [Bluez-devel] hcid vs. hciconfig hci0 up theresa g.
2004-12-01 19:05 ` Marcel Holtmann
2004-12-01 21:02 ` theresa g.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox