Linux bluetooth development
 help / color / mirror / Atom feed
From: "Tom Allebrandi" <tom@ytram.com>
To: "'BlueZ users'" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] link manager protocol monitoring.
Date: Fri, 17 Nov 2006 11:28:53 -0500	[thread overview]
Message-ID: <000001c70a65$79b99a90$1300a8c0@fte.local> (raw)
In-Reply-To: <2c894a800611162307w1a0edca3lddd75783f3d5ba90@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1784 bytes --]

Or Frontline's FTS4BT 

 

www.fte.com/getfts4bt

 

 

--- tom

tom allebrandi

tom@ytram.com

 

(Frontline Test Equipment, Inc.)

(tallebrandi@fte.com)

 

  _____  

From: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] On Behalf Of Matteo
Pelati
Sent: Friday, November 17, 2006 2:08 AM
To: BlueZ users
Subject: Re: [Bluez-users] link manager protocol monitoring.

 

The only way to see LMP traffic is by using a BT sniffer like the Merlin. 

 

Matteo

 

On 11/16/06, Uichin (Eugene) Lee <netssenger@gmail.com> wrote: 

Dear All,

Is there any way that we can figure out what's going on in the LMP. I
tried to dump activities using "hcidump lmp" but I was not able to 
capture anything (I was only able to capture hci and data packets). Is
it really true that we have no idea of seeing what's going on inside
the chipset?

The main reason that I want to do this, we'd like to know how CQDDR 
works in Bluetooth 1.2 and 2.0 as well as Power Control. If you give
me any tip, I would really appreciate that.

Thank you!

--
Uichin (Eugene) Lee
Ph.D. Student UCLA CS Dept.

------------------------------------------------------------------------- 
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
<http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV>
&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/bluez-users




-- 
Matteo Pelati
E-mail: matteo@dolce.it
Phone: +39-338-6168872 


[-- Attachment #1.2: Type: text/html, Size: 7193 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2006-11-17 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17  1:59 [Bluez-users] link manager protocol monitoring Uichin (Eugene) Lee
2006-11-17  2:06 ` Marcel Holtmann
2006-11-17  7:07 ` Matteo Pelati
2006-11-17 16:28   ` Tom Allebrandi [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='000001c70a65$79b99a90$1300a8c0@fte.local' \
    --to=tom@ytram.com \
    --cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox