Changeset 4677 for lm-sensors/branches/lm-sensors-3.0.0/lib/sensors.conf.5

Timestamp:

08/16/07 12:06:35 (6 years ago)

Author:

khali

Message:

Chip types can no longer contain dashes. This makes it possible to
rewrite sensors_parse_chip_name() with a simpler algorithm. The new
code is smaller by about one third, and twice as fast on average
(5 times as fast in the most frequent case "foo-*".)

This closes ticket #2221.

Files:

• lm-sensors/branches/lm-sensors-3.0.0/lib/sensors.conf.5 (modified) (3 diffs)

lm-sensors/branches/lm-sensors-3.0.0/lib/sensors.conf.5

@@ -187 +187 @@
 
 A chip description is built from a couple of elements, separated by
-dashes. To complicate matters, sometimes an element can also contain
-dashes. This complicates the parsing algorithm, but is not too confusing
-for humans (we hope!).
+dashes.
 
 The first element is the name of the chip type. Sometimes a single driver
@@ -217 +215 @@
 for this element. 
 
-There are some folding rules for wildcards to make things easier for humans
-to read. Also, you can't specify the address if you wildcard the complete
-second element. The following are all valid chip type specification based
-on 
+Note that it wouldn't make any sense to specify the address without the
+bus type. For this reason, the address part is plain omitted when the bus
+type isn't specified.
+The following are all valid chip type specification based on
 .I lm78\-i2c\-1\-2d
 or
@@ -251 +249 @@
 .sp 0
 *\-isa\-*
-.sp 0
-*\-*
-.sp 0
-*
 .RE