public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: paolo2278@freemail.it
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] absolute clock
Date: Wed, 31 Mar 2004 12:56:04 +0200	[thread overview]
Message-ID: <1080730564.2674.2.camel@pegasus> (raw)
In-Reply-To: <20040331104607.18049.qmail@mail.supereva.it>

Hi Paolo,

> I have a great problem, I'd like to know wich is the structure where I can find the value of the bluetooth's absolute clock, or the function that I could call for read this value.
> I created the hci command packet to get this information, but what I can see is only the lenght of the event parameters but not their values.

about what clock are you talking? With Bluetooth 1.1 you can only read
the clock offset of a remote device. With 1.2 you can also read the
local and remote clock values. Look at the HCI specification.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-03-31 10:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31 10:46 [Bluez-devel] absolute clock paolo2278
2004-03-31 10:56 ` Marcel Holtmann [this message]
2004-03-31 11:58 ` Steven Singer
2004-03-31 12:14   ` Marcel Holtmann
     [not found] <20040331113603.3852.qmail@mail.supereva.it>
2004-03-31 11:41 ` 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=1080730564.2674.2.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=paolo2278@freemail.it \
    /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