All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manjunath Prabhu <manjunath.mp@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Link Quality
Date: Mon, 6 Dec 2004 19:20:23 +0530	[thread overview]
Message-ID: <2de46576041206055023c98e57@mail.gmail.com> (raw)
In-Reply-To: <1102339845.9644.23.camel@pegasus>

Hi Marcel,


On Mon, 06 Dec 2004 14:30:45 +0100, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Manjunath,
> 
> > The LM decides which packets to use to send data based on link quality.
> > How can I read or trace the  packet type I am using currently? Or
> > rather if the packet type changes...will an event be generated? Do the
> > packet types change dynamically......as the link quality varies???
> 
> the link manager has a list of packet types it is able to use and it
> will use them. There exists a command to change the packet types of an
> already created connection and this command will also create an event
> that informs you that the packet types have changed. Besides this you
> can only guess from the size of ACL data packets what packet type the
> link manager is using and this is not an exact science.
> 
> > Can I somehow avoid FEC checks???May be by using DH packets......but I
> > know you say I shouldn't change packet types??? Is there someother
> > method to do so.
> 
> No, because DM1 is always allowed.
After a connection is established, I can change the packet to any of
the DH types and avoid FEC........did you mean that even then DM1 is
allowed.

Does, opening a socket and then connect() at the
L2CAP......automatically establish an HCI connection first and then an
L2CAP connection on top of it??  This is what HCI dump shows..

Can I in someway just create an HCI connection and then pump HCI data
packet with some known payload??? In a way, just pump raw bits.....

Thanks,
Regards,
Manjunath
> 
> Regards
> 
> Marcel
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-12-06 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 13:23 [Bluez-users] Link Quality Manjunath Prabhu
2004-12-06 13:30 ` Marcel Holtmann
2004-12-06 13:50   ` Manjunath Prabhu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-20  5:16 [Bluez-users] RFComm library William Pettersson
2005-05-20  9:32 ` Marcel Holtmann
2005-05-21  8:34   ` [Bluez-users] Link quality Pieter De Mil

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=2de46576041206055023c98e57@mail.gmail.com \
    --to=manjunath.mp@gmail.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 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.