Hi Johan, On Mon, Nov 22, 2010 at 9:12 AM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > Hi Arun, > > On Mon, Nov 22, 2010, Arun K. Singh wrote: >> > The code will work sub-optimally with userspace versions that still >> > do the name requesting themselves (it shouldn't break anything >> > though) so it is recommended to combine this with a userspace >> > software version that doesn't have automated name requests. >> >> Could you be bit more explicit about such user space versions that you >> recommend? Would latest bluez versions such as 4.80 qualify for your >> recommendation? > > The automated name requests upon "connect complete" events were removed > in 4.78 so any version from there onwards would qualify. Maybe there is some way to detect that the kernel is not doing it, or at least force bluetoothd to resolve once to make sure it can be used with older kernel versions so it doesn't have to always update as it was used to be but if we are to authenticate or authorize a device it should have a name so the ui can display it to the user. -- 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
