hci_read_remote_name_with_clock_offset vs hci_read_remote_name

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey guys,

Please bare with me as I'm just starting to learn the concepts of
hci-traffic. I hope this is the right place to ask.

I was wondering - is there any performance gain in preferring
'hci_read_remote_name_with_clock_offset' to 'hci_read_remote_name' if
you already know the clock offset (from a previous inquiry).

Looking at the source code it seems as though the latter only calls the
former with the clock offset set to 0?

/Christian

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux