<div class="gmail_quote">On Sat, Dec 26, 2009 at 1:38 PM, Marcel Holtmann <span dir="ltr"><<a href="mailto:marcel@holtmann.org">marcel@holtmann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Sam,<br>
<div class="im"><br>
> > The other thing are the quality and noise properties. Do you<br>
> still want<br>
> > these? Or can we just go for a signal property showing the<br>
> dBm value<br>
> > like iw scan does. I don't see any extra value in keeping<br>
> deprecated<br>
> > values in the new API.<br>
><br>
><br>
> Please lets get rid of them. One signal strength value that<br>
> could be<br>
> trusted to contain some useful data is much better than three<br>
> with<br>
> semi-random values no one can figure out.. Quality has never<br>
> been<br>
> defined properly and noise is not even a property of a BSS (it<br>
> is per<br>
> channel and should not have been mixed with scan results in<br>
> the first<br>
> place).<br>
><br>
><br>
> I think dropping noise floor is a bad idea unless you add another<br>
> mechanism at the same time to get it (is there a mechanism in the new<br>
> d-bus api?). The quality parameter has never been useful IMO and<br>
> dropping it would make sense.<br>
<br>
</div>isn't the new survey API of nl80211 doing exactly this for you?<br></blockquote><div><br></div><div>Who said anything about linux?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> > Do you think a "Display" or "Name" property showing the SSID<br>
> in<br>
> > converted UTF-8 would be useful. Or should the clients do<br>
> that<br>
> > translation?<br>
><br>
><br>
> I would love to have this, but I do agree that it is next to<br>
> impossible<br>
> to get this right in all cases.<br>
><br>
><br>
> I agree w/ not doing translation in the supplicant. In my world this<br>
> work is part of the UI and unless we push state down into the<br>
> supplicant it cannot do as good a job.<br>
<br>
</div>What state are you talking about? The concern here is to figure out the<br>
locale the AP is potentially using. Even with a country IE available, it<br>
is not guaranteed that it matches the locale of the SSID, but that might<br>
be as close as it gets when guessing.<br><br></blockquote><div>The state needed to do the localization/translation of the string. This is not just a locale it's also all the libraries and related bits.</div><div><br>
</div><div>-Sam</div><div><br></div></div>