Hi, On Mon, Jul 26, 2010 at 10:55 AM, Jose Antonio Santos Cadenas <santoscadenas@xxxxxxxxx> wrote: > When the remote SDP records that make a driver to be loaded change > (added, remove, or updated) And the driver is not going to be > removed, a notification is sent to the device driver. This > notification is optional annnd does not fail if the driver does > not implemment it. How this is supposed to work? If does seems to me that you guys are planning to keep polling the services records to update the drivers which IMO is not a good idea, DiscoverServices is not meant to update the drivers either it is basically a replacement to sdptool to so application can do it over dbus. Also if you take a closer look in the plugins that use rfcomm channel, which can be changed at any point, they basically fetch the record when attempting to connect, avdtp also work in a similar way, we have to do the discover + get capabilities every time we want to connect to a sink/source since there is no way to keep this information updated locally. In the other hand, this can be useful for LE which we can subscribe to changes, but for sdp I don't see the point. -- Luiz Augusto von Dentz Computer Engineer -- 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
