Hi Alecrim, On Mon, Mar 29, 2010, Francisco Alecrim wrote: > >> IMO, it should be the same list as we export in extended inquiry > >> response, so perhaps we could use the data from > >> create_ext_inquiry_response which already filter those away. Perhaps > >> some refactoring could also be done since this code seems to be called > >> multiple times in case of new services because it also changes class > >> which then triggers create_ext_inquiry_response again. > > I'm not so sure about it but create_ext_inquiry_response list all > services to any adapters. Shouldn't it list just services per > adapter(access_db)? It should be per-adapter (or records registered to BDADDR_ANY) since EIR is also per-adapter, so looks like a possible bug in the current implementation. Btw, another restriction to note with the current EIR UUID list implementation is that it only supports 16-bit UUIDs. The EIR format itself would support also 32 and 128 bit formats but probably for simplicity these have been left out. The Adapter UUIDs list should however contain all UUIDs (with the exceptions that we already discussed). 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
