From: Keith Smith (keith_at_ksmith.com)
Date: 2002-06-14 05:41:34 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jean Tourrilhes wrote:
| Jouni Malinen wrote :
|
|>On Sat, Jun 08, 2002 at 04:46:02PM -0700, Keith Smith wrote:
|>
|>>Is there anyay to maybe make it a % value (which would make more
|>>sense MAYBE) so txpower 100% means all the way up, etc. This would
|>>seem to be a function of 'wireless tools' also. . .
|>
|>Current iwconfig supports dBm and mW values for txpower option and
|>the driver uses only dBm. Of course these could mapped in many ways
|>to something, but I don't think it is quite trivial to get it to be
|>both understandable and accurate..
|
|
| If you want me to add relative values (percent or whatever)
| for txpower in the Wireless Tools, please just ask, and I'll
| oblige. It's a trivial change.
| But, I believe that the effort of presenting the user with dBm
| or mW is well worth it.
| Have fun...
|
| Jean
|
Not to beat a dead horse or anything... The only thing I can think of is an external table for wireless tools to look up the card somehow. That way you could map +-63 to something meaningful on a per-card basis. Most of the cards I see claim between 10-16 as the max power they will put out. This might add too much needless crap though.
"You are in a maze of twisty standards all different".
While we are on the subject. It appears that the power level "floats" if it is not explicitly set, is this correct? Is there a way to return to "floating" once you set the power? If this is in some docs somewhere just flame, and I'll look again. :)
iD8DBQE9CYILz2CugoiX+Q0RAiLeAJ9OVbKJHwPgwP+rX67FQ5Cadt6G/wCgqCgW
0ZfsM85aE7zRpPthXMQ1ipU=
=Ml0L
-----END PGP SIGNATURE-----