public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: amateur <ztl.post@gmail.com>,
	BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] on which level does hcidump work?
Date: Sun, 10 Dec 2006 15:20:10 +0100	[thread overview]
Message-ID: <1165760410.20427.4.camel@localhost> (raw)
In-Reply-To: <20061210141620.GB3730@163.com>

Hi,

> > > > > I'm encountering a problem that the data I sent through a L2CAP socket
> > > > > on my local machine doesn't appear in the output of hcidump on the
> > > > > remote machine. But it does appear in the output of hcidump on my
> > > > > local machine.
> > > > > 
> > > > > So I'm wondering on which level does hcidump work. Does it work on the
> > > > > host-dongle interface? What should I do if I want to monitor all the
> > > > > information pass through the host-dongle interface(HCI_USB?). Or can I
> > > > > make such an assumption that all the data showed in the output of
> > > > > hcidump were sent out through the radio? Can I make such a assumption
> > > > > that all the data received was showed up in the output of hcidump?
> > > > 
> > > > you see only HCI packets (hence the name). There is no real way to make
> > > > sure the packet went over the air. In some cases you can make this
> > > > assumption from other stuff that is going on.
> > > > 
> > > Then how can I make sure that the HCI ACL Packet sent by the Host is
> > > *really* received correctly by Host Controller? It seems like there
> > > doesn't exist any packet acknowlegment sent from the Host Controller.
> > > And there isn't a Command-Complete or Command-Status Event for HCI
> > > ACL Packet. So should I ensure that the HCI Transport Layer is reliable?
> > > I just want to make sure that the Packet I sent through HCI actually
> > > reached the Host Controller.
> > 
> > that is the job of the HCI transport layer and not the job of the host
> > stack. The host stack simply assumes that the transport is reliable and
> > handles packet loss etc.
> > 
> > However ACL packets are bound to the HCI flow control and you will see
> > the number of packets acknowledgment.
> This method seems feasible. I'll try it and find whether the packet
> loss be due to the HCI USB transport layer.

the HCI USB transport layer will retransmit packets on errors and have
an acknowledgment mechanism. Depending on the USB controller you use
this might be in hardware or in software. Check the USB specification
for further details.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-12-10 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 18:37 [Bluez-devel] on which level does hcidump work? amateur
2006-12-08 10:23 ` Marcel Holtmann
2006-12-09  1:48   ` amateur
2006-12-10 12:41     ` Marcel Holtmann
2006-12-10 14:16       ` amateur
2006-12-10 14:20         ` 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=1165760410.20427.4.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=ztl.post@gmail.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