From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linville@tuxdriver.com>, <wireless-regdb@lists.infradead.org>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wireless-regdb: add regulatory rule for ETSI members on 60gHz band
Date: Mon, 10 Dec 2012 13:09:27 +0200 [thread overview]
Message-ID: <1424987.QUc2GD1qWX@lx-vladimir> (raw)
In-Reply-To: <1355134918.9857.9.camel@jlt4.sipsolutions.net>
On Monday, December 10, 2012 11:21:58 AM Johannes Berg wrote:
> On Mon, 2012-12-10 at 11:45 +0200, Vladimir Kondratiev wrote:
>
> > For the 60gHz band, regulation defined in the "Etsi En 302 567"
> > http://docsfiles.com/pdf_final_draft_etsi_en_302_567.html
>
> > +country AD:
> > + # 60 gHz band channels 1-4, ref: Etsi En 302 567
> > + (57240 - 65880 @ 2160), (N/A, 40), NO-OUTDOOR
> > + (57240 - 65880 @ 2160), (N/A, 25)
>
> There doesn't seem to be a bandwidth limitation in the rules, should we
> really put one into the database?
Yes, there is no limit and I'd want to remove bandwidth, but I don't see
how to do so. If I simply omit '@ 2160', I am getting error from db2bin.py:
$ ./db2bin.py regulatory.bin db.txt vkondrat.key.priv.pem
Traceback (most recent call last):
File "./db2bin.py", line 52, in <module>
countries = p.parse(file(sys.argv[2]))
File "/local/mnt/vkondrat/60ghz/wireless-regdb/dbparse.py", line 361, in parse
self._parse_country_item(line)
File "/local/mnt/vkondrat/60ghz/wireless-regdb/dbparse.py", line 268, in _parse_country_item
self._syntax_error("Badly parenthesised band definition")
File "/local/mnt/vkondrat/60ghz/wireless-regdb/dbparse.py", line 139, in _syntax_error
raise SyntaxError("Syntax error in line %d%s" % (self._lineno, txt))
dbparse.SyntaxError: Syntax error in line 17 (Badly parenthesised band definition)
next prev parent reply other threads:[~2012-12-10 11:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 14:16 [PATCH] wireless-regdb: add regulatory rule for US on 60gHz band Vladimir Kondratiev
2012-12-10 9:45 ` [PATCH] wireless-regdb: add regulatory rule for ETSI members " Vladimir Kondratiev
2012-12-10 10:21 ` Johannes Berg
2012-12-10 11:09 ` Vladimir Kondratiev [this message]
2012-12-10 11:31 ` Johannes Berg
2012-12-10 12:15 ` Vladimir Kondratiev
2012-12-10 12:33 ` Johannes Berg
2012-12-10 15:48 ` [PATCH v2] " Vladimir Kondratiev
2013-02-06 18:39 ` John W. Linville
2013-02-07 9:27 ` Vladimir Kondratiev
2012-12-23 9:36 ` [PATCH] wireless-regdb: add regulatory rule for US " Vladimir Kondratiev
-- strict thread matches above, loose matches on Subject: below --
2014-10-14 12:28 [PATCH] wireless-regdb: add regulatory rule for ETSI members on 60GHz band Xose Vazquez Perez
2014-10-19 6:49 ` Vladimir Kondratiev
2014-10-27 17:26 ` John W. Linville
2014-10-28 8:19 ` Vladimir Kondratiev
2014-10-28 11:06 ` Xose Vazquez Perez
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=1424987.QUc2GD1qWX@lx-vladimir \
--to=qca_vkondrat@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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