From: Marcel Holtmann <marcel@holtmann.org>
To: pavan_savoy@indiatimes.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Understanding UART bluetooth ..
Date: Mon, 18 Aug 2008 07:14:00 +0200 [thread overview]
Message-ID: <1219036440.7591.19.camel@violet.holtmann.net> (raw)
In-Reply-To: <673335200.654421217249991946.JavaMail.root@mbv7.indiatimes.com>
Hi,
> I had a question on hciattach / hcid & related to hci-core.c, If I know I have a bluetooth device on ttyS0.. and I do a
> #hciattach ttyS0 <with_relevant_parameters>
>
> will the whole system know [using dbus & hcid, that a new device has been added, if so who exactly does this ? ]
>
> I mean I could only find hci_open_dev, but no other dbus or hcid functions to notify...
>
> does hci_notify does the same ? which is being called on hci_open_dev?
what is your actual question here? I don't have the slightest idea.
Regards
Marcel
next prev parent reply other threads:[~2008-08-18 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 12:59 Understanding UART bluetooth pavan_savoy
2008-08-18 5:14 ` Marcel Holtmann [this message]
2008-08-18 9:22 ` pavan_savoy
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=1219036440.7591.19.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pavan_savoy@indiatimes.com \
/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