summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* hwdb: ieee1394-unit-function: add entries for Point Grey camerasTakashi Sakamoto2021-05-053-3/+28
| | | | | | | | | | | Point Grey Research, inc. shipped cameras to support IIDC, however some of them are necessarily compliant to IIDC specification in terms of the value of software version field in unit directory of configuration ROM. This commit adds entries for them. Reviewed-by: Damien Douxchamps <damien@douxchamps.net> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
* hwdb: ieee1394-unit-function: add IIDC generic entriesTakashi Sakamoto2021-05-053-3/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instrumentation & Industrial Digital Camera (IIDC) specifications are defined by 1394 Trading Association for camera device in IEEE 1394 bus. IIDC2 specifications are defined by joint working group between Japan Industrial Imaging Association (JIIA) and 1394 Trade Association as bus-independent specification. This commit adds entries for the specifications to remove existent udev rules. Supported specifications are listed below: * 1394-based Digital Camera Specification Version 1.04 (Aug. 9, 1996, 1394 Trading Association) * 1394-based Digital Camera Specification Version 1.20 (Jul. 23, 1998, 1394 Trading Association) * IIDC Digital Camera Control Specification Ver.1.30 (Jul. 25, 2000, 1394 Trading Association) * IIDC Digital Camera Control Specification Ver.1.31 (Feb. 2, 2004, 1394 Trading Association, TA Document 2003017) * IIDC Digital Camera Control Specification Ver.1.32 (Jul. 24, 2008, 1394 Trading Association, Document number 2007009) * IIDC2 Digital Camera Control Specification Ver.1.0.0 (Jan 26th, 2012, 1394 Trading Association, TS2011001) * IIDC2 Digital Camera Control Specification Ver.1.1.0 (May 19th, 2015, 1394 Trading Association, TS2015001) Reviewed-by: Damien Douxchamps <damien@douxchamps.net> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
* hwdb: ieee1394-unit-function: add entries for Digital Everywhere FloppyDTV ↵Takashi Sakamoto2021-05-051-0/+40
| | | | | | | | | | | and FireDTV Linux kernel has firedtv kernel module as driver for Digital Everywhere FloppyDTV and FireDTV. Although this driver works without any help of userspace application, it's better to add entries to hardware database for developer's convenience. Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
* hwdb: ieee1394-unit-function: fix indentationTakashi Sakamoto2021-05-051-544/+544
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Zbigniew Jędrzejewski-Szmek points that current entries are against the convention of indentation. It should be indented by one space instead of two. This commit fixes current entries according to it. Reported-by: Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> Fixes: 1b6d9a05b14a ("hwdb: add database entries for models with ASICs in BeBoB solution") Fixes: 0db0564e957f ("hwdb: add database entries for models with Fireworks board module") Fixes: 38338b302cb0 ("hwdb: add database entries for models with OXFW970/971 ASICs") Fixes: c0d8b61f9385 ("hwdb: add database entries for models based on DICE ASICs with TCAT specification") Fixes: a774b5099bce ("hwdb: add database entries for models based on DICE ASICs specialized to M-Audio") Fixes: ff1cb7b9393a ("hwdb: add database entries for models based on DICE ASICs specialized to Weiss Engineering") Fixes: 6f44dddbe20a ("hwdb: add database entries for models based on DICE ASICs specialized by Loud Technologies") Fixes: 49ed0aad525b ("hwdb: add database entries for models based on DICE ASICs specialized by Harman Music Group") Fixes: effbb4024b8b ("hwdb: add database entries for models based on DICE ASICs specialized by Solid State Logic") Fixes: 4aaa093b5fb6 ("hwdb: add database entries for models of Digidesign Digi 00x family") Fixes: c489e7f9d3c4 ("hwdb: add database entries for Tascam FireWire series") Fixes: 650b8967a57b ("hwdb: add database entries for MOTU FireWire series") Fixes: 51e9242b9b91 ("hwdb: add database entries for RME Fireface series") Fixes: a90a6a9ae9f8 ("hwdb: add database entries for Yamaha mLAN 2nd generation") Fixes: 41f2d0d393a4 ("hwdb: add database entries for Yamaha mLAN 3rd generation") Fixes: 1d2ee962922f ("hwdb: add database entries for Focusrite Liquid Mix series") Fixes: 0c20543835d6 ("hwdb: add database entries for TC Electronic PowerCore FireWire series") Fixes: 8b4b76dc5021 ("hwdb: add database entry for node with single unit with video function") Fixes: 12dd2404bee8 ("hwdb: add database entries for node with multiple units") Fixes: dece0357e1c8 ("hwdb: add database entries for node with single unit for multiple functions") Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
* hwdb: fix parser to execute test for ieee1394-unit-function with no argumentTakashi Sakamoto2021-05-051-1/+1
| | | | | | | | | | | When given no arguments, hwdb parser script seeks test target files by glob pattern. Although I added a new file for IEEE 1394 unit functions, the file is excluded as test target due to the pattern. This commit fixes it. Fixes: 7713f3fc6a2 ("hwdb: add parser grammar for IEEE 1394 unit function list") Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
* Merge pull request #19454 from keszybz/assorted-cleanupsZbigniew Jędrzejewski-Szmek2021-05-057-62/+56
|\ | | | | Assorted cleanups
| * core/automount: drop unecessary castZbigniew Jędrzejewski-Szmek2021-05-041-1/+1
| |
| * core/cgroup: remove some unnecessary variablesZbigniew Jędrzejewski-Szmek2021-05-041-10/+5
| |
| * basic/log: directly initialize iovec arraysZbigniew Jędrzejewski-Szmek2021-05-041-19/+21
| | | | | | | | | | It doesn't change much, but removes a bunch of explicit size and index handling and unnecessary initializations.
| * basic/io-util: move iterator variable declarations into loop headersZbigniew Jędrzejewski-Szmek2021-05-041-2/+2
| |
| * resolved: directly initialize iovec arrayZbigniew Jędrzejewski-Szmek2021-05-041-7/+6
| |
| * basic/io-util: invert return value from IOVEC_INCREMENT()Zbigniew Jędrzejewski-Szmek2021-05-042-9/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | We would try to return a value that could be nonzero only if the kernel reported writing more bytes than we gave to it, hopefully a rare occurence. Instead, assert that this doesn't happen. Instead, return true if we got to the end of the iovec array. The caller can use this information to know that the whole iovec array was written. This allows one loop to be dropped in write_to_syslog(). Also drop _unlikely_: this function is called with very short arrays, and it *is* likely that we trigger this condition. Let's just let the compiler generate normal code without giving it a potentially false hint.
| * core: remove spurious % in dump stringZbigniew Jędrzejewski-Szmek2021-05-041-1/+1
| |
| * core/cgroup: use assert_se() moreZbigniew Jędrzejewski-Szmek2021-05-041-9/+4
| |
| * core: minor simplificationZbigniew Jędrzejewski-Szmek2021-05-041-3/+1
| |
| * meson: make one check shorterZbigniew Jędrzejewski-Szmek2021-05-041-1/+1
| |
* | tests: use "H" as the hostnameZbigniew Jędrzejewski-Szmek2021-05-052-6/+6
| | | | | | | | | | | | "systemd-testsuite" gets in the way when grepping for "testsuite-*.sh". Also, the name doesn't matter for anything, so let's just use something very short to save space.
* | hostnamectl: fix hyperlink in "Operating System" fieldYu Watanabe2021-05-041-9/+2
| | | | | | | | | | | | | | | | | | This fixes a bug introduced by 822be62fb23ed0ec1062ffd18057e53f6c2f8c01. Before this, if terminal width is not enough, the all subsequent lines are included in the hyperlink. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1955475.
* | tree-wide: fix typoYu Watanabe2021-05-042-2/+2
|/
* Add correct rotation support for Mediacom Winpad 7.0 W700imayoda2021-05-031-0/+7
| | | | this patch enables correct bios detection and matrix for the aforementioned tiny tablet (touchscreen support commit pending now in kernel) thnx
* hostnamectl: deprecate set-* methods and expose getters by only using nouns ↵Jakub Warczarek2021-05-034-89/+96
| | | | in commands
* core: apply LogLevelMax to messages about unitsRyan Hendrickson2021-05-039-138/+178
| | | | | | | | | | This commit applies the filtering imposed by LogLevelMax on a unit's processes to messages logged by PID1 about the unit as well. The target use case for this feature is a service that runs on a timer many times an hour, where the system administrator decides that writing a generic success message to the journal every few minutes or seconds adds no diagnostic value and isn't worth the clutter or disk I/O.
* Merge pull request #19403 from nmeyerhans/dmi-entriesLennart Poettering2021-05-036-12/+81
|\ | | | | virt: differentiate Amazon EC2 bare-metal from VM instances using SMBIOS data
| * Use BIOS characteristics to distinguish EC2 bare-metal from VMsNoah Meyerhans2021-04-301-4/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | DMI vendor information fields do not provide enough information for us to distinguish between Amazon EC2 virtual machines and bare-metal instances. SMBIOS provides a BIOS Information table (https://www.dmtf.org/sites/default/files/standards/documents/DSP0134_3.4.0.pdf Ch. 7) that provides a field to indicate that the current machine is a virtual machine. On EC2 virtual machine instances, this field is set, while bare-metal instances leave this unset, so we inspect the field via the kernel's /sys/firemware/dmi/entries interface. Fixes #18929
| * machine-id-setup: generate machine-id from DMI product ID on Amazon EC2Bertrand Jacquin2021-04-301-4/+5
| | | | | | | | | | | | Amazon EC2 Nitro hypervisor is technically based on KVM[1]. [1] https://aws.amazon.com/ec2/faqs/
| * virt: detect Amazon EC2 Nitro instanceBertrand Jacquin2021-04-305-4/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Amazon EC2 Nitro hypervisor is technically based on KVM[1], which systemd-detect-virt identify propely from CPUID. However the lack of CPUID on aarch64 (A1, T4 instance type) prevents a correct identification, impacting hostnamectl and systemd-random-seed. Instead it's possible to identify virtualization from DMI vendor ID. Prior to this commit: # hostnamectl Static hostname: n/a Transient hostname: ip-10-97-8-12 Icon name: computer Machine ID: 8e3772fbcfa3dd6f330a12ff5df5a63b Boot ID: b7b7e2fe0079448db664839df59f9817 Operating System: Gentoo/Linux Kernel: Linux 5.4.69-longterm Architecture: arm64 After this commit: # hostnamectl Static hostname: n/a Transient hostname: ip-10-97-8-12 Icon name: computer-vm Chassis: vm Machine ID: 8e3772fbcfa3dd6f330a12ff5df5a63b Boot ID: bd04da57084e41078f20541101867113 Virtualization: amazon Operating System: Gentoo/Linux Kernel: Linux 5.4.69-longterm Architecture: arm64 [1] https://aws.amazon.com/ec2/faqs/
* | Document the need to do journalctl --flush for persistent logging (#19481)Luca Adrian L2021-05-032-0/+10
| | | | | | | | | | Document the need to do journalctl --flush for persistent logging. (fixes #19480) Co-authored-by: Luca Lindhorst <l.lindhorst@wut.de>
* | Revert "sysusers/firstboot: temporarily disable LoadCredential"Luca Boccassi2021-05-032-14/+10
| | | | | | | | | | | | | | | | This reverts commit 7c20dd4b6ef6e69862576722ac69b895d7a92dc9. Debian has now been updated to patch the issue, so SemaphoreCI should no longer fail. The fix has also been backported to the affected stable branches.
* | Merge pull request #19487 from mrc0mmand/test-all-services-in-TEST-01Yu Watanabe2021-05-032-6/+13
|\ \ | | | | | | test: don't mask "supporting" services in TEST-01-BASIC
| * | test: explicitly pull resolved/networkd in TEST-01-BASICFrantisek Sumsal2021-04-301-0/+1
| | | | | | | | | | | | to give them at least a basic coverage.
| * | test: don't mask "supporting" services in TEST-01-BASICFrantisek Sumsal2021-04-301-6/+12
| | | | | | | | | | | | This got lost during one of the code de-duplication attempts.
* | | test: fix a yet another pipefail + pipe raceFrantisek Sumsal2021-05-011-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Basically the same scenario as in a33e2692e162671f0d97856ad2f49a2620a1ec10, where `awk` exits as soon as it finds a match, thus sending SIGPIPE to `ldd` if it's not fast enough. That, in combination with `set -o pipefail` causes random & unexpected fails, like: ``` No journal files were found. -rw-r----- 1 root root 16777216 Apr 30 10:31 /var/tmp/TEST-01-BASIC_sanitizers-nspawn/system.journal TEST-01-BASIC RUN: Basic systemd setup [OK] systemd is not linked against the ASan DSO gcc does this by default, for clang compile with -shared-libasan make: *** [Makefile:2: clean-again] Error 1 make: Leaving directory '/build/test/TEST-01-BASIC' ```
* | | Merge pull request #19476 from yuwata/network-canYu Watanabe2021-05-013-73/+66
|\ \ \ | | | | | | | | network: several CAN device related updates
| * | | network: do not bring up CAN interface on configureYu Watanabe2021-04-301-0/+4
| | | |
| * | | network: make CAN device follow activation policyYu Watanabe2021-04-301-10/+9
| | | |
| * | | network: introduce link_activate()Yu Watanabe2021-04-302-7/+17
| | | |
| * | | network: do not try to configure address or etc on can deviceYu Watanabe2021-04-303-0/+25
| | | |
| * | | network: can: shorten code a bitYu Watanabe2021-04-301-13/+5
| | | |
| * | | network: can: do not warn if link does not exist anymoreYu Watanabe2021-04-301-1/+5
| | | |
| * | | network: drop duplicated link_up_can()Yu Watanabe2021-04-303-45/+4
| |/ /
* | | Merge pull request #18904 from yuwata/udev-watchYu Watanabe2021-05-0119-277/+450
|\ \ \ | |_|/ |/| | udev: several inotify watch fixups
| * | test: add a simple test for udev watchYu Watanabe2021-04-302-1/+76
| | |
| * | test: generate debugging logs for udev testsYu Watanabe2021-04-304-1/+8
| | |
| * | test: run udev tests after currently queued events are finishedYu Watanabe2021-04-301-0/+2
| | |
| * | udev,sd_device: also save map from device ID to watch handle in /run/udev/watchYu Watanabe2021-04-307-109/+183
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, watch handle is saved in the udev databse. But in most cases, the handle saved in the database is not updated. Especially, when udevd is restarted, the inotify watch is restarted, but the database is not updated. Moreover, it is not necessary to save watch handle in the database, as the handle is only take a effect during udevd is running, and the value is meaningless when udevd is restarted. So, this makes the opposite map from device ID to watch handle is saved in /run/udev/watch as a symbolic link, and the handle not saved in the database anymore. Fixes #18525.
| * | udev: make udev_watch_end() noop when device does not have devnameYu Watanabe2021-04-302-8/+6
| | |
| * | sd-device: cleanup sd_device_get_subsystem()Yu Watanabe2021-04-302-40/+44
| | |
| * | sd-device: drop sysname_set flagYu Watanabe2021-04-302-9/+5
| | | | | | | | | | | | When device_set_sysname() succeeds, sysname is always set.
| * | sd-device: minor optimization for sd_device_new_from_device_id()Yu Watanabe2021-04-301-6/+5
| | |
| * | sd-device: check the validity of device idYu Watanabe2021-04-301-0/+3
| | | | | | | | | | | | | | | The device id is used as filename under /run/udev/data or /run/udev/watch.
View Lorry Controller Status