* Understanding UART bluetooth ..
@ 2008-07-28 12:59 pavan_savoy
2008-08-18 5:14 ` Marcel Holtmann
0 siblings, 1 reply; 3+ messages in thread
From: pavan_savoy @ 2008-07-28 12:59 UTC (permalink / raw)
To: Majordomo, linux-bluetooth
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?
Thanks..
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Understanding UART bluetooth ..
2008-07-28 12:59 Understanding UART bluetooth pavan_savoy
@ 2008-08-18 5:14 ` Marcel Holtmann
2008-08-18 9:22 ` pavan_savoy
0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2008-08-18 5:14 UTC (permalink / raw)
To: pavan_savoy; +Cc: linux-bluetooth
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Understanding UART bluetooth ..
2008-08-18 5:14 ` Marcel Holtmann
@ 2008-08-18 9:22 ` pavan_savoy
0 siblings, 0 replies; 3+ messages in thread
From: pavan_savoy @ 2008-08-18 9:22 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: linux-bluetooth
Hi,
Thanks got it clarified. It was basically on the notify mechanism of the bluetooth, and user-space kernel-space interaction.
On hciattach, the HCIUARTSETPROTO ioctl causes "hci_uart_register_dev" to be called [in the line discipline driver], which causes "hci_register_dev" to be called which calls the "hci_notify", which notifies the in-kernel HCI socket layer, which then passes the same to the socket on the user-space.
I hope my understanding is correct.
Thanks.
----- Original Message -----
From: Marcel Holtmann <marcel@holtmann.org>
To: pavan savoy <pavan_savoy@indiatimes.com>
Cc: linux-bluetooth@vger.kernel.org
Sent: Mon, 18 Aug 2008 10:44:00 +0530 (IST)
Subject: Re: Understanding UART bluetooth ..
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-08-18 9:22 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-28 12:59 Understanding UART bluetooth pavan_savoy
2008-08-18 5:14 ` Marcel Holtmann
2008-08-18 9:22 ` pavan_savoy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox