All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] bccmd reading clock
Date: Tue, 28 Jun 2005 17:42:44 +0200	[thread overview]
Message-ID: <1119973364.15397.77.camel@pegasus> (raw)
In-Reply-To: <20050627223919.793D83BC@arbetsmyra.dyndns.org>

Hi Ronny,

> I was in the need for an enhancement of the bccmd tool and thus made a 
> small change. The supplied patch adds a command for reading the the 
> BT-clock of local device. In the process I also made some minor changes 
> to utils/tools/csr.c to reuse existing code. Besided reading 16-bit 
> variables it can now also read 32- and 8-bits alike.

don't do type conversion like this. Use varid_complex for it if you
wanna support uint32 and unit8 without copying code.

> No changes has (yet) been made to hcidump. Should it be done?

Of course ;)

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-06-28 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 22:37 [Bluez-devel] bccmd reading clock Ronny L Nilsson
2005-06-28 15:42 ` Marcel Holtmann [this message]
2005-06-29  8:26   ` Ronny L Nilsson
2005-07-01  8:43     ` Ronny L Nilsson
2005-07-03 10:16     ` Marcel Holtmann
2005-07-03 16:33       ` Ronny L Nilsson
2005-07-03 16:56         ` 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=1119973364.15397.77.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.