Re: [PATCH] Fix incoming attrib-server connection MTUs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Brian,

On Thu, Jan 20, 2011, Brian Gix wrote:
> It is important for the Attribute Server to be aware of and completely
> fill response packets up to the full MTU when reading long attributes.
> Some remote devices will only request additional (READ_BLOB) data if
> the preceding read sent the maximum amount of data.
> 
> Incoming connections are identified as L2CAP or LE by pointers to the
> Service IO channel the incoming connection was recieved on in the
> user_data parameter. L2CAP channels are set to the BR/EDR minimum MTU
> of 48, and LE channels to the LE payload size of 23.
> ---
>  attrib/att.h        |    3 ++-
>  attrib/gatt.c       |   28 ++++++++++++++--------------
>  src/attrib-server.c |   13 +++++++++----
>  3 files changed, 25 insertions(+), 19 deletions(-)

Thanks for the updated patch. It looks good now and has been pushed
upstream.

Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux