> > As for what to display for "possible", I don't think that > > this is meaningful here. I would rather see the default > > output just be "LINK", "PROPERTY", "VALUE" and "DEFAULT". > > unfortunately we already follow the above convention (printing > POSSIBLE) for wifi links.. so unless we want to break the trend, we > are stuck with reporting possible. I personally also feel ther eis some > use in printing possible, as this gives a hint of input range.
Since none of the *-linkprop has shipped in a marketing release, it's quite easy to make changes to it. In other words, please don't feel like we're "stuck with it" :-) The "POSSIBLE" concept changed a few times during WiFi development, and it's a bit underspecified at the moment. In particular, right now there can be values listed in "POSSIBLE" that may in fact be impossible (because of other environment conditions -- e.g., if `powermode' is "off", the only possible value for `radio' is "off", but we still also show "on" as a possible value). If we had a GUI, these would be the sort of things that we'd gray out -- but old-school ASCII makes it hard to represent such a concept. If we want to sort this out, we'd probably need another field. -- meem _______________________________________________ driver-discuss mailing list driver-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/driver-discuss
