From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] MTU in l2test
Date: Sun, 02 Jan 2005 15:05:21 +0100 [thread overview]
Message-ID: <1104674721.8894.10.camel@pegasus> (raw)
In-Reply-To: <2de4657604123007015c2c9461@mail.gmail.com>
Hi Manjunath,
> I am varying the mtu and data size variables in the l2test program.
> From the docs, I learnt that maximum L2CAP payload is 65535 bytes. I
> am unable to set the data size above 45000 bytes inspite of setting my
> MTU to 65535 (both on the sender and the receiver).
> I get an error saying "Send failed. Resource temporarily unavailable".
> Hope you can help me with this one.
the MTU is different for incoming and outgoing side. With what kind of
device and what commands lines are you testing these.
> Also, in the l2test, is the data channel connectionless(6 byte L2CAP
> header) or connection oriented(4 byte L2CAP header).I am asking this
> because the code seems to have a 6-byte offset for the header which
> means the data channel might be connectionless but i am also able to
> see the "connection request" and "configuration request" which is a
> feature of connection oriented data channels.
Actually the connectionless L2CAP is not really supported and maybe
somekind of buggy. Feel free to send in any improvements.
> Also, how is that I am able to see the packet size of ACL Data in "HCI
> dump", say a 339 byte packet for DH5 packets. Isn't this supposed to
> happen at the Baseband?
The HCI sends up the ACL data and actually for most chips it is the same
size as on the baseband. As far as I know this is not recommanded, but
it is a good way to not introduce too much overhead for the chip. The
final SAR is done by the L2CAP layer.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-02 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 15:01 [Bluez-users] MTU in l2test Manjunath Prabhu
2005-01-02 14:05 ` Marcel Holtmann [this message]
2005-01-03 10:47 ` Manjunath Prabhu
2005-01-03 11:00 ` Marcel Holtmann
2005-01-03 11:28 ` Manjunath Prabhu
2005-01-03 11:43 ` 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=1104674721.8894.10.camel@pegasus \
--to=marcel@holtmann.org \
--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