summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorphk <phk@FreeBSD.org>2002-03-24 11:33:52 +0000
committerphk <phk@FreeBSD.org>2002-03-24 11:33:52 +0000
commit93f0d047cf27caa028b88bcc9097bff11b863160 (patch)
tree2556b3d0446fb58f320da992539a8a88719c8f12
parent8842976cdd6c89916f7799133a97e4f32b4ad3c8 (diff)
downloadFreeBSD-src-93f0d047cf27caa028b88bcc9097bff11b863160.zip
FreeBSD-src-93f0d047cf27caa028b88bcc9097bff11b863160.tar.gz
Hide the ACPI counter probing printf behind bootverbose.
The conclusion is that this method really can tell the perfect from the less than perfect ACPI counters. It is in fact probably a bit more discriminative than that, but we will rather condemn some otherwise perfect counters to the slightly slower "-safe" version, than certify a counter as perfect which will let us down later. Many thanks to all the people who sent email reports!
-rw-r--r--sys/dev/acpica/acpi_timer.c7
1 files changed, 4 insertions, 3 deletions
diff --git a/sys/dev/acpica/acpi_timer.c b/sys/dev/acpica/acpi_timer.c
index 6117a6f..1fa9b89 100644
--- a/sys/dev/acpica/acpi_timer.c
+++ b/sys/dev/acpica/acpi_timer.c
@@ -131,9 +131,10 @@ test_counter()
n = 0;
else
n = 1;
- printf("ACPI timer looks %s min = %d, max = %d, width = %d\n",
- n ? "GOOD" : "BAD ",
- min, max, max - min + 1);
+ if (bootverbose)
+ printf("ACPI timer looks %s min = %d, max = %d, width = %d\n",
+ n ? "GOOD" : "BAD ",
+ min, max, max - min + 1);
return (n);
}
OpenPOWER on IntegriCloud