From: Marcel Holtmann <marcel@holtmann.org>
To: pavan_savoy@ti.com
Cc: linux-bluetooth@vger.kernel.org, kobile@ti.com,
pavan savoy <pavan_savoy@yahoo.co.in>
Subject: Re: using hci0 interface without DEVUP
Date: Tue, 06 Jul 2010 09:55:04 -0300 [thread overview]
Message-ID: <1278420904.2789.41.camel@localhost.localdomain> (raw)
In-Reply-To: <250863.34433.qm@web94911.mail.in2.yahoo.com>
Hi Pavan,
> In certain cases, as in using VS commads to communicate with different cores on the combo chips (say, BT, FM, GPS) - we would have to use the hci0 interface without it being UP.
>
> As in the hci0 interface still needs to be invisible (via dbus/bluetoothd) to the system but to be available to be use.
>
> Is there a way we can do this while registering with the hci ?
> say a flag in the struct hci_dev to be by default during registration HCI_DEV_DOWN to be default state ?
it is a pretty simple fact that the HCI device has to up. Otherwise it
is not going to work. Same with an Ethernet interface. That is the
proper state for such interfaces.
What you want is to set RAW mode on the HCI device before bringing it
up. Then bluetoothd will actually ignore it.
However I am not sure what you are really trying to achieve here since
every device will be brought up automatically by bluetoothd. And so you
are already to late to the game at that point.
Regards
Marcel
next prev parent reply other threads:[~2010-07-06 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 12:06 using hci0 interface without DEVUP Pavan Savoy
2010-07-06 12:55 ` Marcel Holtmann [this message]
2010-07-06 13:51 ` Pavan Savoy
2010-07-06 14:08 ` Marcel Holtmann
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=1278420904.2789.41.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=kobile@ti.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pavan_savoy@ti.com \
--cc=pavan_savoy@yahoo.co.in \
/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