Hi Lizardo, On Wed, Jun 6, 2012 at 10:26 PM, Anderson Lizardo <anderson.lizardo@xxxxxxxxxxxxx> wrote: > Hi Andre, > > On Wed, Jun 6, 2012 at 8:40 PM, Andre Guedes <andre.guedes@xxxxxxxxxxxxx> wrote: >> 23 octets is the default (and minimum) ATT_MTU value. If someone tries >> to set ATT_MTU less than 23 octets g_attrib_set_mtu should fail (return >> FALSE). Additionally, there is no constraint regarding the maximum value >> of ATT_MTU, so we should not check for it. > > Even though the spec does not mention a maximum ATT_MTU, we now need > to review and fix the ATT operations that mention limits on their PDU > (now that we removed the "artificial" 256 octect limit). Some I found: Yes, we're working on that. > Also, what will happen to the ATT_MTU_MAX definition? Is it still > being used in other places? Yes, we use ATT_MTU_MAX to allocate opdu buffers, but we should replace ATT_MTU_MAX by the current ATT_MTU. BR, Andre -- 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
