Hi Luiz, On Tuesday 14 January 2014 17:49:54 Luiz Augusto von Dentz wrote: > Hi Szymon, > > On Tue, Jan 14, 2014 at 1:11 PM, Szymon Janc <szymon.janc@xxxxxxxxx> wrote: > > Cache is limited to DEVICES_CACHE_MAX. Devices are sorted with > > timestamp so if cache is full olderst device is removed. > > --- > > > > android/bluetooth.c | 69 > > ++++++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 55 > > insertions(+), 14 deletions(-) > > > > diff --git a/android/bluetooth.c b/android/bluetooth.c > > index 8c91d87..df442a3 100644 > > --- a/android/bluetooth.c > > +++ b/android/bluetooth.c > > @@ -70,6 +70,8 @@ > > > > /* Default discoverable timeout 120sec as in Android */ > > #define DEFAULT_DISCOVERABLE_TIMEOUT 120 > > > > +#define DEVICES_CACHE_MAX 100 > > Is this being limited because Android UI cannot handle more than that? > Or perhaps because our IPC/MTU cannot carry more than that? If the > latter I believe we can actually calculate the maximun e.g. MTU / pdu > size. This is not related to Android UI nor MTU. This is just to limit max resources usage. Value is totally arbitrary. If device is not in cache some HAL functions might fail (notably set/get device property). -- Szymon K. Janc szymon.janc@xxxxxxxxx -- 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
