linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: What's hcitrace?
Date: Tue, 29 Dec 2009 03:41:06 -0800	[thread overview]
Message-ID: <1262086866.16627.104.camel@localhost.localdomain> (raw)
In-Reply-To: <20091229111734.4aaec550@strolchi.home.s3e.de>

Hi Stefan,

> I found hcitrace in the bluez-4.59 tarball.
> What is it? Should it be packaged? Maybe in the bluez-test package?

eventually it should be, but right now, you better don't.

So the hcitrace daemon (when I finish it), will allow per advanced
tracing capabilities with multiple HCI controllers per stream (that is
needed for AMPs). And of course it will use D-Bus activation etc. All
fancy stuff, but as of of now, it is not finished yet.

Regards

Marcel



      reply	other threads:[~2009-12-29 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 10:17 What's hcitrace? Stefan Seyfried
2009-12-29 11:41 ` Marcel Holtmann [this message]

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=1262086866.16627.104.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=stefan.seyfried@googlemail.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;
as well as URLs for NNTP newsgroup(s).