Changes between Version 10 and Version 11 of DevDocs/AthDebug
- Timestamp:
- 06/19/07 22:04:12 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevDocs/AthDebug
v10 v11 7 7 The reason why there are two separate programs is that one controls the debugging output from the device (`ath`) specific part and the other one for the generic (`80211`) part. Remember: The 802.11 stack used by MadWifi (net80211) is derived from FreeBSD where it supports more wireless devices than just Atheros based. 8 8 9 Both programs have the same user interface and basically work by setting a bitmap in the driver enabling or disabling debugging output from various subsystems. Both also take an optional parameter `-i device` (e.g. -i wifi1) which can be om mitted if you use wifi0.9 Both programs have the same user interface and basically work by setting a bitmap in the driver enabling or disabling debugging output from various subsystems. Both also take an optional parameter `-i device` (e.g. -i wifi1) which can be omitted if you use wifi0. 10 10 11 11 So we have the basic usage: 146 146 147 147 == Performance Impact == 148 '''Attention:''' Enabling all debugging output on smaller systems can make them very slow and sometimes unresponsive. So it's usually better to only enable the output from the part you are inter rested in.148 '''Attention:''' Enabling all debugging output on smaller systems can make them very slow and sometimes unresponsive. So it's usually better to only enable the output from the part you are interested in. 149 149 150 150 But sometimes you don't know in advance. So it might sometimes be useful to use a script or write all commands in one line to enable debugging output, issue a short command and disable it again. E.g:
