Re: [PATCH BlueZ 2/2] core/device: Don't set MTU when acting as a peripheral

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

 



Hi Lukasz,

On Thu, Mar 10, 2016 at 11:17 AM, Łukasz Rymanowski
<lukasz.rymanowski@xxxxxxxxxxx> wrote:
>> Not only we cannot be configured as server, but even if we do the
>> roles are only relevant for PTS because otherwise there is no way to
>> tell the roles of the remote device.
>
> If device sends request that means it is a Client. If not that means
> it is a Server.

Well if it send it can be a Client/Server as well, btw some systems
including Android appear to have support to send Exchange MTU at any
point so detecting a server only pretty hard, besides our current
design split Server and Client functionality so waiting to see if
anything has been received before starting sending anything is not so
trivial and we had still to choose an arbitrary timeout to wait for
detecting the role but if both are based on BlueZ this would just
delay each other.
--
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