[systemd-devel] [PATCH] hwdb: Add database for Bluetooth company identifiers
--- Makefile.am | 1 + hwdb/20-bluetooth-vendor-product.hwdb | 541 ++ 2 files changed, 542 insertions(+) create mode 100644 hwdb/20-bluetooth-vendor-product.hwdb diff --git a/Makefile.am b/Makefile.am index 477b3a6..94ae549 100644 --- a/Makefile.am +++ b/Makefile.am @@ -1905,6 +1905,7 @@ dist_udevhwdb_DATA = \ hwdb/20-pci-classes.hwdb \ hwdb/20-usb-vendor-product.hwdb \ hwdb/20-usb-classes.hwdb \ + hwdb/20-bluetooth-vendor-product.hwdb \ hwdb/20-acpi-vendor.hwdb \ hwdb/20-OUI.hwdb diff --git a/hwdb/20-bluetooth-vendor-product.hwdb b/hwdb/20-bluetooth-vendor-product.hwdb new file mode 100644 index 000..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:v* + ID_VENDOR_FROM_DATABASE=Ericsson Technology Licensing + +bluetooth:v0001* + ID_VENDOR_FROM_DATABASE=Nokia Mobile Phones + +bluetooth:v0002* + ID_VENDOR_FROM_DATABASE=Intel Corp. + +bluetooth:v0003* + ID_VENDOR_FROM_DATABASE=IBM Corp. + +bluetooth:v0004* + ID_VENDOR_FROM_DATABASE=Toshiba Corp. + +bluetooth:v0005* + ID_VENDOR_FROM_DATABASE=3Com + +bluetooth:v0006* + ID_VENDOR_FROM_DATABASE=Microsoft + +bluetooth:v0007* + ID_VENDOR_FROM_DATABASE=Lucent + +bluetooth:v0008* + ID_VENDOR_FROM_DATABASE=Motorola + +bluetooth:v0009* + ID_VENDOR_FROM_DATABASE=Infineon Technologies AG + +bluetooth:v000A* + ID_VENDOR_FROM_DATABASE=Cambridge Silicon Radio + +bluetooth:v000B* + ID_VENDOR_FROM_DATABASE=Silicon Wave + +bluetooth:v000C* + ID_VENDOR_FROM_DATABASE=Digianswer A/S + +bluetooth:v000D* + ID_VENDOR_FROM_DATABASE=Texas Instruments Inc. + +bluetooth:v000E* + ID_VENDOR_FROM_DATABASE=Ceva, Inc. (formerly Parthus Technologies Inc.) + +bluetooth:v000F* + ID_VENDOR_FROM_DATABASE=Broadcom Corporation + +bluetooth:v0010* + ID_VENDOR_FROM_DATABASE=Mitel Semiconductor + +bluetooth:v0011* + ID_VENDOR_FROM_DATABASE=Widcomm, Inc. + +bluetooth:v0012* + ID_VENDOR_FROM_DATABASE=Zeevo, Inc. + +bluetooth:v0013* + ID_VENDOR_FROM_DATABASE=Atmel Corporation + +bluetooth:v0014* + ID_VENDOR_FROM_DATABASE=Mitsubishi Electric Corporation + +bluetooth:v0015* + ID_VENDOR_FROM_DATABASE=RTX Telecom A/S + +bluetooth:v0016* + ID_VENDOR_FROM_DATABASE=KC Technology Inc. + +bluetooth:v0017* + ID_VENDOR_FROM_DATABASE=Newlogic + +bluetooth:v0018* + ID_VENDOR_FROM_DATABASE=Transilica, Inc. + +bluetooth:v0019* + ID_VENDOR_FROM_DATABASE=Rohde Schwartz GmbH Co. KG + +bluetooth:v001A* + ID_VENDOR_FROM_DATABASE=TTPCom Limited + +bluetooth:v001B* + ID_VENDOR_FROM_DATABASE=Signia Technologies, Inc. + +bluetooth:v001C* + ID_VENDOR_FROM_DATABASE=Conexant Systems Inc. + +bluetooth:v001D* + ID_VENDOR_FROM_DATABASE=Qualcomm + +bluetooth:v001E* + ID_VENDOR_FROM_DATABASE=Inventel + +bluetooth:v001F* + ID_VENDOR_FROM_DATABASE=AVM Berlin + +bluetooth:v0020* + ID_VENDOR_FROM_DATABASE=BandSpeed, Inc. + +bluetooth:v0021* + ID_VENDOR_FROM_DATABASE=Mansella Ltd + +bluetooth:v0022* + ID_VENDOR_FROM_DATABASE=NEC Corporation + +bluetooth:v0023* + ID_VENDOR_FROM_DATABASE=WavePlus Technology Co., Ltd. + +bluetooth:v0024* + ID_VENDOR_FROM_DATABASE=Alcatel + +bluetooth:v0025* + ID_VENDOR_FROM_DATABASE=Philips Semiconductors + +bluetooth:v0026* + ID_VENDOR_FROM_DATABASE=C Technologies + +bluetooth:v0027* + ID_VENDOR_FROM_DATABASE=Open Interface + +bluetooth:v0028* + ID_VENDOR_FROM_DATABASE=R F Micro Devices + +bluetooth:v0029* + ID_VENDOR_FROM_DATABASE=Hitachi Ltd + +bluetooth:v002A* + ID_VENDOR_FROM_DATABASE=Symbol Technologies, Inc. + +bluetooth:v002B* + ID_VENDOR_FROM_DATABASE=Tenovis + +bluetooth:v002C* + ID_VENDOR_FROM_DATABASE=Macronix International Co. Ltd. + +bluetooth:v002D* + ID_VENDOR_FROM_DATABASE=GCT Semiconductor + +bluetooth:v002E* + ID_VENDOR_FROM_DATABASE=Norwood Systems + +bluetooth:v002F* + ID_VENDOR_FROM_DATABASE=MewTel Technology Inc. + +bluetooth:v0030* + ID_VENDOR_FROM_DATABASE=ST Microelectronics + +bluetooth:v0031* + ID_VENDOR_FROM_DATABASE=Synopsys + +bluetooth:v0032* + ID_VENDOR_FROM_DATABASE=Red-M (Communications) Ltd + +bluetooth:v0033* + ID_VENDOR_FROM_DATABASE=Commil Ltd + +bluetooth:v0034* + ID_VENDOR_FROM_DATABASE=Computer Access Technology Corporation (CATC) + +bluetooth:v0035* + ID_VENDOR_FROM_DATABASE=Eclipse (HQ Espana) S.L. + +bluetooth:v0036* + ID_VENDOR_FROM_DATABASE=Renesas Technology Corp. + +bluetooth:v0037* + ID_VENDOR_FROM_DATABASE=Mobilian Corporation + +bluetooth:v0038* + ID_VENDOR_FROM_DATABASE=Terax + +bluetooth:v0039* + ID_VENDOR_FROM_DATABASE=Integrated System Solution Corp. + +bluetooth:v003A* + ID_VENDOR_FROM_DATABASE=Matsushita Electric Industrial Co., Ltd. + +bluetooth:v003B* + ID_VENDOR_FROM_DATABASE=Gennum Corporation + +bluetooth:v003C* + ID_VENDOR_FROM_DATABASE=Research In Motion + +bluetooth:v003D* + ID_VENDOR_FROM_DATABASE=IPextreme, Inc. + +bluetooth:v003E* +
Re: [systemd-devel] [PATCH] hwdb: Add database for Bluetooth company identifiers
Hi Marcel, On Fri, Dec 28, 2012 at 8:53 AM, Marcel Holtmann mar...@holtmann.org wrote: diff --git a/hwdb/20-bluetooth-vendor-product.hwdb b/hwdb/20-bluetooth-vendor-product.hwdb new file mode 100644 index 000..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:v* + 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? Cheers, Tom ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] hwdb: Add database for Bluetooth company identifiers
Hi Tom, diff --git a/hwdb/20-bluetooth-vendor-product.hwdb b/hwdb/20-bluetooth-vendor-product.hwdb new file mode 100644 index 000..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:v* + 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 systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] localed: create /etc/X11/xorg.conf.d if needed
Use mkdir_p_label instead of mkdir_parents_label, so that the final
directory component is created too.
---
src/locale/localed.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/locale/localed.c b/src/locale/localed.c
index 04268a1..bb2a3a2 100644
--- a/src/locale/localed.c
+++ b/src/locale/localed.c
@@ -567,7 +567,7 @@ static int write_data_x11(void) {
return 0;
}
-mkdir_parents_label(/etc/X11/xorg.conf.d, 0755);
+mkdir_p_label(/etc/X11/xorg.conf.d, 0755);
r = fopen_temporary(/etc/X11/xorg.conf.d/00-keyboard.conf, f,
temp_path);
if (r 0)
--
1.8.0.2
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] man: fix parameter in systemd-fstab-generator(8)
There is no parameter named luks.fstab. --- man/systemd-fstab-generator.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/systemd-fstab-generator.xml b/man/systemd-fstab-generator.xml index 2decec6..b265b6c 100644 --- a/man/systemd-fstab-generator.xml +++ b/man/systemd-fstab-generator.xml @@ -96,7 +96,7 @@ filename/etc/fstab/filename. varnamerd.fstab=/varname is honored only by initial RAM disk (initrd) while -varnameluks.fstab=/varname is +varnamefstab=/varname is honored by both the main system and the initrd. /para/listitem /varlistentry -- 1.8.0.2 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] use static_assert instead of assert_cc
Another item from the todo 0001-use-static_assert-instead-of-assert_cc.patch Description: Binary data ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] add sprezzos as alias for debian in autoconf script
Hello there! This patch adds sprezzos as an alias for debian in the configuration script. It also adds a comment exhorting other Debian derivatives to do this when possible, in the hope of keeping identifier bloat localized to autoconf while providing maximal future-proofing and making the correct choice explicit to the largest number of users. I went this route after first adding a TARGET_SPREZZOS autoconf #define, and realizing that this meant multiple files now had #if defined(TARGET_DEBIAN) || defined(TARGET_ANGSTROM) || defined(TARGET_SPREZZOS) which is getting pretty clearly ridiculous. Should there come a time when Debian needs radically unexpected changes here to conform with *new* behavior, it might behoove us to make sprezzos an alias of TARGET_DEBIAN_CLASSIC_DERIVATIVE or some other horror, allowing exlusive TARGET_DEBIAN-guarding of this hypothetical new code. Until that unhappy and unlikely day, this will work for Debian derivatives until they explicitly diverge from Debian, at which point changes elsewhere are rather more expected. Ångström, I notice that the semantics of TARGET_ANGSTROM are currently equivalent to those of TARGET_DEBIAN. I thus recommend that you convert to an alias similarly, allowing removal of TARGET_ANGSTROM #ifdefs scattered throughout the systemd code proper. Systemd maintainers, if you agree with this approach, please apply my patch. It can, of course, be applied independently of Ångström's takeup of this method. Pull from https://github.com/Sprezzatech/systemd/commit/43571179a9effdde3365c5bd72f66f7712b68f5e. Thanks, everyone. Hack on! diff --git a/configure.ac b/configure.ac index d0003bb..e0e9dca 100644 --- a/configure.ac +++ b/configure.ac @@ -640,7 +640,7 @@ AM_CONDITIONAL(ENABLE_MANPAGES, [test x$have_manpages = xyes]) # -- -AC_ARG_WITH(distro, AS_HELP_STRING([--with-distro=DISTRO],[Specify the distribution to target: One of fedora, suse, debian, arch, gentoo, slackware, altlinux, mandriva, mageia, angstrom or other])) +AC_ARG_WITH(distro, AS_HELP_STRING([--with-distro=DISTRO],[Specify the distribution to target: One of fedora, suse, debian, arch, gentoo, slackware, altlinux, mandriva, mageia, angstrom, sprezzos or other])) if test z$with_distro = z; then if test $cross_compiling = yes; then AC_MSG_WARN([Target distribution cannot be reliably detected when cross-compiling. You should specify it with --with-distro (see $0 --help for recognized distros)]) @@ -660,6 +660,9 @@ SYSTEM_SYSVRCND_PATH=/etc/rc.d M4_DEFINES= +# If you are Debian-derived, and the set of Debian-associated conditionals +# apply to you, make yourself an alias of debian here rather than introducing +# an entire new set of identifiers. case $with_distro in fedora) SYSTEM_SYSVINIT_PATH=/etc/rc.d/init.d @@ -671,7 +674,7 @@ case $with_distro in AC_DEFINE(TARGET_SUSE, [], [Target is openSUSE/SLE]) M4_DEFINES=-DTARGET_SUSE=1 ;; -debian) +sprezzos|debian) SYSTEM_SYSVRCND_PATH=/etc AC_DEFINE(TARGET_DEBIAN, [], [Target is Debian]) M4_DEFINES=-DTARGET_DEBIAN=1 -- nick black http://www.sprezzatech.com -- unix and hpc consulting to make an apple pie from scratch, you need first invent a universe. From 43571179a9effdde3365c5bd72f66f7712b68f5e Mon Sep 17 00:00:00 2001 From: nick black nick.bl...@sprezzatech.com Date: Fri, 28 Dec 2012 23:16:13 -0500 Subject: [PATCH] add sprezzos as an alias for debian in the autoconf script To: systemd-devel@lists.freedesktop.org Cc: debian-derivati...@lists.debian.org --- configure.ac | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index d0003bb..e0e9dca 100644 --- a/configure.ac +++ b/configure.ac @@ -640,7 +640,7 @@ AM_CONDITIONAL(ENABLE_MANPAGES, [test x$have_manpages = xyes]) # -- -AC_ARG_WITH(distro, AS_HELP_STRING([--with-distro=DISTRO],[Specify the distribution to target: One of fedora, suse, debian, arch, gentoo, slackware, altlinux, mandriva, mageia, angstrom or other])) +AC_ARG_WITH(distro, AS_HELP_STRING([--with-distro=DISTRO],[Specify the distribution to target: One of fedora, suse, debian, arch, gentoo, slackware, altlinux, mandriva, mageia, angstrom, sprezzos or other])) if test z$with_distro = z; then if test $cross_compiling = yes; then AC_MSG_WARN([Target distribution cannot be reliably detected when cross-compiling. You should specify it with --with-distro (see $0 --help for recognized distros)]) @@ -660,6 +660,9 @@ SYSTEM_SYSVRCND_PATH=/etc/rc.d M4_DEFINES= +# If you are Debian-derived, and the set of Debian-associated conditionals +# apply to you, make yourself an alias of debian here rather than introducing
