2023-10-27 17:23:47 -04:00
|
|
|
# Implement the run-time component of devmatch by reacting to nomatch events.
|
|
|
|
|
|
2018-02-11 23:45:26 -05:00
|
|
|
#
|
2023-10-27 17:23:47 -04:00
|
|
|
# Ignore those devices that can't possibly match. When there's neither a
|
|
|
|
|
# location, nor a pnpinfo string, we know that there's nothing devmatch can
|
|
|
|
|
# match on. When it's only a location, it'd debateable, but for nomatch
|
|
|
|
|
# events, we can't disambiguate between the two reliably.
|
2018-02-11 23:45:26 -05:00
|
|
|
#
|
2023-10-27 17:23:47 -04:00
|
|
|
nomatch 101 {
|
|
|
|
|
match "_" " +at +on .*";
|
|
|
|
|
};
|
2018-02-11 23:45:26 -05:00
|
|
|
|
|
|
|
|
#
|
2023-10-27 17:23:47 -04:00
|
|
|
# Ignore ACPI devices whose _HID is none. These cannot tell us what to load,
|
|
|
|
|
# since 'none' is not a valid id. There's no need to call devvmatch for these either.
|
|
|
|
|
#
|
|
|
|
|
nomatch 101 {
|
|
|
|
|
match "_HID" "none";
|
|
|
|
|
match "bus" "acpi[0-9]+";
|
|
|
|
|
};
|
|
|
|
|
|
2018-02-11 23:45:26 -05:00
|
|
|
#
|
|
|
|
|
# Generic NOMATCH event
|
2023-10-27 17:23:47 -04:00
|
|
|
#
|
|
|
|
|
# Note: It would be better to have some internal-to-devd action that will do
|
|
|
|
|
# what devmatch does without re-parsing loader.hints for each invocation
|
|
|
|
|
#
|
2018-02-11 23:45:26 -05:00
|
|
|
nomatch 100 {
|
2023-10-27 17:23:47 -04:00
|
|
|
action "service devmatch quietstart $*";
|
2018-02-11 23:45:26 -05:00
|
|
|
};
|
2018-02-12 01:51:20 -05:00
|
|
|
|
2018-02-12 01:52:49 -05:00
|
|
|
# Add the following to devd.conf to prevent this from running:
|
2018-02-12 01:51:20 -05:00
|
|
|
# nomatch 1000 {
|
2018-02-13 03:10:17 -05:00
|
|
|
# action "true";
|
2018-02-12 01:51:20 -05:00
|
|
|
# };
|
|
|
|
|
# it replaces the generic event with one of higher priority that
|
|
|
|
|
# does nothing. You can also set 'devmatch_enable=NO' in /etc/rc.conf
|