aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLuis R. Rodriguez <mcgrof@do-not-panic.com>2013-05-25 12:09:16 -0700
committerLuis R. Rodriguez <mcgrof@do-not-panic.com>2013-05-25 12:09:16 -0700
commit965c2a1e81c3bbaa04ba79c92aa8e9fd44f7916a (patch)
treee256a2600d5d86bdaed4bea5a565c9099f4c2dfa
parentc5505f6e9e887f80cc5ecbe6059a18b18d82620b (diff)
downloadcrda-965c2a1e81c3bbaa04ba79c92aa8e9fd44f7916a.tar.gz
crda: annotate intersection worst case scenerio
In the worst case scenerio of regulatory domain intersections between a different set of regulatory rules you will end up without being able to initiate radiation on any frequency range. Provide a hint as to what needs to be done next in order to actually build a useful regulatory domain. Currently we do this manually but building the mathematics would be even more useful as we grow usage of the spectrum. Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
-rw-r--r--intersect.c9
1 files changed, 8 insertions, 1 deletions
diff --git a/intersect.c b/intersect.c
index dea9145..169fe1a 100644
--- a/intersect.c
+++ b/intersect.c
@@ -83,7 +83,14 @@ int main(int argc, char **argv)
printf("%d regulatory domains intersected\n", intersected);
else {
world = prev_world;
- printf("Only one intersection completed\n");
+ printf("No intersections completed\n");
+ if (idx > 1) {
+ printf("Since more than one regulatory domain is "
+ "present and no intersections were possible "
+ "no globally allowed spectrum is possible so "
+ "consider enabling passive scan flags\n");
+ return r;
+ }
}
/* Tada! */