From: Kalle Valo <kvalo@codeaurora.org>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: ath10k@lists.infradead.org,
Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>,
Julian Calaby <julian.calaby@gmail.com>,
linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
Steve deRosier <derosier@gmail.com>,
Ben Greear <greearb@candelatech.com>
Subject: Re: [v2,1/3] ath9k: Support channels in licensed bands
Date: Thu, 11 May 2017 14:38:58 +0300 [thread overview]
Message-ID: <87efvvvd0t.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1863250.VEhGCjvYY0@prime> (Simon Wunderlich's message of "Tue, 09 May 2017 14:57:32 +0200")
Simon Wunderlich <sw@simonwunderlich.de> writes:
> it seems like there was some discussion here and I wouldn't expect too many
> more opinions ... do you think we can have a decision based on what has been
> discussed here?
Well, there was an excellent reply from Steve and quite a few "in my
opinion this is safe" type of answers. [1] But bluntly said it does not
really matter what we (the engineers) think. What really matters here
are regulatory authorities' opinions and rulings. In that respect here
are few items I want to point out:
o I suspect that from someone's, who is not familiar with software
engineering, point of view there is still quite a diffference from
modifiying source code or just enabling few options from Kconfig with
a custom regdb rule.
o I don't know about other countries, but in Finland applying for any
type of license (even if just to a license to drive a moped) needs
both time and money. So there is significant effort anyway needed to
legally use this band. And how many users there really are is unclear.
o Also this is not about enabling or disabling channel 13, but about a
public _safety_ band which makes me very uneasy.
So the way I see this is that the risks outweigh the benefits and that's
why I do not want to take these. Sorry.
[1] https://patchwork.kernel.org/patch/9641105/
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: Julian Calaby <julian.calaby@gmail.com>,
linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
ath10k@lists.infradead.org, Steve deRosier <derosier@gmail.com>,
Ben Greear <greearb@candelatech.com>,
Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>
Subject: Re: [v2,1/3] ath9k: Support channels in licensed bands
Date: Thu, 11 May 2017 14:38:58 +0300 [thread overview]
Message-ID: <87efvvvd0t.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1863250.VEhGCjvYY0@prime> (Simon Wunderlich's message of "Tue, 09 May 2017 14:57:32 +0200")
Simon Wunderlich <sw@simonwunderlich.de> writes:
> it seems like there was some discussion here and I wouldn't expect too many
> more opinions ... do you think we can have a decision based on what has been
> discussed here?
Well, there was an excellent reply from Steve and quite a few "in my
opinion this is safe" type of answers. [1] But bluntly said it does not
really matter what we (the engineers) think. What really matters here
are regulatory authorities' opinions and rulings. In that respect here
are few items I want to point out:
o I suspect that from someone's, who is not familiar with software
engineering, point of view there is still quite a diffference from
modifiying source code or just enabling few options from Kconfig with
a custom regdb rule.
o I don't know about other countries, but in Finland applying for any
type of license (even if just to a license to drive a moped) needs
both time and money. So there is significant effort anyway needed to
legally use this band. And how many users there really are is unclear.
o Also this is not about enabling or disabling channel 13, but about a
public _safety_ band which makes me very uneasy.
So the way I see this is that the risks outweigh the benefits and that's
why I do not want to take these. Sorry.
[1] https://patchwork.kernel.org/patch/9641105/
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-05-11 11:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 13:30 [PATCH v2 0/3] Channels in licensed bands, noise floor override Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-03-23 13:30 ` [PATCH v2 1/3] ath9k: Support channels in licensed bands Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-04-18 14:36 ` [v2,1/3] " Kalle Valo
2017-04-18 14:36 ` Kalle Valo
[not found] ` <20170418143654.8AC0A60FAA@smtp.codeaurora.org>
2017-04-18 14:50 ` Simon Wunderlich
2017-04-18 14:50 ` Simon Wunderlich
2017-04-18 16:38 ` Steve deRosier
2017-04-18 16:38 ` Steve deRosier
[not found] ` <CALLGbRK2d1wZpfLnXu_UDWxVPA9LvejFyEFpzMub56uLH0+DTw@mail.gmail.com>
2017-04-18 17:09 ` Ben Greear
2017-04-18 17:09 ` Ben Greear
2017-04-21 11:29 ` Simon Wunderlich
2017-04-21 11:29 ` Simon Wunderlich
2017-04-21 12:40 ` Mathias Kretschmer
2017-04-21 12:40 ` Mathias Kretschmer
2017-05-09 12:57 ` Simon Wunderlich
2017-05-09 12:57 ` Simon Wunderlich
2017-05-09 17:50 ` Adrian Chadd
2017-05-09 17:50 ` Adrian Chadd
[not found] ` <CAKR_QV+0cPXbiScO3cS52R97o=wGh4+zgmqaRM7QbotmEJD51Q@mail.gmail.com>
2017-05-10 16:17 ` Ben Greear
2017-05-10 16:17 ` Ben Greear
2017-05-11 11:38 ` Kalle Valo [this message]
2017-05-11 11:38 ` Kalle Valo
2017-05-12 14:12 ` Ben Greear
2017-05-12 14:12 ` Ben Greear
2017-05-12 19:21 ` Steve deRosier
2017-05-12 19:21 ` Steve deRosier
2017-05-12 19:44 ` Ben Greear
2017-05-12 19:44 ` Ben Greear
2017-05-13 12:12 ` Arend Van Spriel
2017-05-13 12:12 ` Arend Van Spriel
2017-03-23 13:30 ` [PATCH v2 2/3] ath10k: add support for " Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-03-23 13:30 ` [PATCH v2 3/3] ath9k: add noise floor override option Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-04-19 14:08 ` [v2,3/3] " Kalle Valo
2017-04-19 14:08 ` 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=87efvvvd0t.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=derosier@gmail.com \
--cc=greearb@candelatech.com \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fit.fraunhofer.de \
--cc=sw@simonwunderlich.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.