On Sat, 2011-07-30 at 15:02 +0200, Lukasz Stelmach wrote: > Hi. > > I am investigating ways to set the device class (computer/laptop > etc) of a bluetooth device. There is a key in main.conf named > Class to set the class but aparently it is overridden by the > class field of /var/lib/bluetooth/<bdaddr>/config. Once the class > is stored there changes in main.conf don't affect the actual class > the device presents. IMHO it is quite obutse and it took me an hour > or more with a debugger to find out how to change it so I'd like to > propose the following patch. Are there any reasons that the config > file in /var should override the value from /etc? I'm not sure what we're trying to achieve with per-adapter classes (if not for debugging purposes). I would simply never write the class of the adapter to disk, and use the DMI information, with the value in the options file as fallback if a class could not be gathered. If the formfactor plugin isn't in use, use the options value. eg. your patch, plus a change in formfactor.c to not overwrite the class, and another to never actually write the class to disk. Cheers -- 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
