Lines Matching refs:and

9  The design of the debugging message interface was guided and
11  to understand the history and evolution in order to understand current
12  practice and relate it to older driver source code.
16  level ranged from 0 to 7, and monotonically increased in verbosity.
24     3  Interface starts and stops, including normal status messages
25     4  Tx and Rx frame error messages, and abnormal driver operation
27     6  Status on each completed Tx packet and received Rx packets
28     7  Initial contents of Tx and Rx packets
31  e.g. "lance_debug", so that a kernel symbolic debugger could locate and
33  were consistently renamed to "debug" and allowed to be set as a module
38  reasonable and easily implemented enhancements
44  complexity and code size increase.
51     variable is a bit map rather than a level, and is initialized as