From: Marcel Holtmann <marcel@holtmann.org>
To: Stephen Crane <steve.crane@rococosoft.com>
Cc: bluez-devel@lists.sourceforge.net, jim.oleary@rococosoft.com
In-Reply-To: <1117032099.5854.56.camel@baroque.rococosoft.com>
References: <1117032099.5854.56.camel@baroque.rococosoft.com>
Content-Type: text/plain
Message-Id: <1117036775.30044.238.camel@pegasus>
Mime-Version: 1.0
Subject: [Bluez-devel] Re: Small fix for L2CAP MTU
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Reply-To: bluez-devel@lists.sourceforge.net
Date: Wed, 25 May 2005 17:59:35 +0200

Hi Steve,

> I've attached a small change to the L2CAP layer which causes it to
> better adhere to a sender's choice of MTU.
> 
> The background is that we have a test here where the client asks for an
> omtu of 50 and tries to send more than this to the server, which in turn
> checks that only 50 bytes were sent.
> 
> With the current kernel code, the omtu is always returned as the default
> MTU (672) which causes our test to fail.

I don't get it. Please show me the "hcidump -X -V" for both cases. With
and without the patch.

Regards

Marcel


-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel