From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: linux-wireless@vger.kernel.org, kvalo@qca.qualcomm.com,
wireless-regdb@lists.infradead.org
Subject: Re: [RFC] wireless: improve dfs-region intersection.
Date: Mon, 23 Jun 2014 19:35:37 -0700 [thread overview]
Message-ID: <53A8E3F9.7000001@candelatech.com> (raw)
In-Reply-To: <20140624004442.GH1390@garbanzo.do-not-panic.com>
>> Maybe just use time-zone or user hints in this case since NICs cannot
>> be fully trusted.
>
> WTF no, the regulatory hint stuff should all be automated and user input
> should really only come from trusted sources, see the cell base station
> hint as a good example use case. The NICs are trusted as that's what
> regulatory bodies like folks to do. Hell even the country IEs are only
> trusted for the alpha2, the actual contents are disregarded. Regular
> user input should only help compliance further, that's it.
NICs just aren't that reliable, seems you can buy NICs with any number
of regulatory domains on the interweb, and then you can hop on a plane
and go other interesting places.
If you ever have a system with NICs with two different regulatory domains,
I assume it is very likely that it was not certified in that configuration.
Maybe the user's input (and AP's beacons and such) are more reliable in this
case.
But, not worth arguing about at this point. As long as the basic regulatory
bugs are fixed (as per the other thread), then my problems should be solveable.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-06-24 2:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 20:08 [RFC] wireless: improve dfs-region intersection greearb
2014-06-23 19:15 ` Luis R. Rodriguez
2014-06-23 20:37 ` Ben Greear
2014-06-23 20:54 ` Luis R. Rodriguez
2014-06-23 21:20 ` Ben Greear
2014-06-24 0:44 ` Luis R. Rodriguez
2014-06-24 2:35 ` Ben Greear [this message]
2014-06-24 2:53 ` Luis R. Rodriguez
2014-06-25 16:48 ` Ben Greear
2014-06-25 17:20 ` Luis R. Rodriguez
2014-06-25 17:34 ` Ben Greear
2014-06-25 17:37 ` Luis R. Rodriguez
2014-06-26 6:50 ` Janusz Dziedzic
2014-06-24 5:47 ` Kalle Valo
2014-06-25 16:52 ` Luis R. Rodriguez
2014-06-25 17:56 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53A8E3F9.7000001@candelatech.com \
--to=greearb@candelatech.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=wireless-regdb@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).