Hi Tom, > > diff --git a/hwdb/20-bluetooth-vendor-product.hwdb > > b/hwdb/20-bluetooth-vendor-product.hwdb > > new file mode 100644 > > index 0000000..c8cb322 > > --- /dev/null > > +++ b/hwdb/20-bluetooth-vendor-product.hwdb > > @@ -0,0 +1,541 @@ > > +# This file is part of systemd. > > +# > > +# Data imported from: > > +# http://www.bluetooth.org/Technical/AssignedNumbers/identifiers.htm > > + > > +bluetooth:v0000* > > + ID_VENDOR_FROM_DATABASE=Ericsson Technology Licensing > [...] > > How did you generate this? Might it make sense to patch ids-update.pl > to generate the new .hwdb file so we make sure it stays up-to-date?
it is actual manual labor. We have the database inside BlueZ which is manually updated. I added tools/hwdb utility to BlueZ that allows us to create the database from the BlueZ included data. The Bluetooth company identifiers update rather infrequently so that there was no need to automate anything. At least not so far. I update them as part of the BlueZ release process. I have started to also add product identifiers now. First one is the Nike+ FuelBand where they actually use Bluetooth vendor and product ids. There is no central database around these. I am tracking them inside BlueZ at the moment. Regards Marcel _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
