From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
<linux-wireless@vger.kernel.org>,
<wireless-regdb@lists.infradead.org>
Subject: Re: [RFC] wireless: improve dfs-region intersection.
Date: Tue, 24 Jun 2014 08:47:46 +0300 [thread overview]
Message-ID: <87pphy7ta5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <53A89011.1010806@candelatech.com> (Ben Greear's message of "Mon, 23 Jun 2014 13:37:37 -0700")
Ben Greear <greearb@candelatech.com> writes:
> As for being confusing, the current code is nasty and it is very hard
> to have any idea why things do or do not work, especially if you do not
> have ability to add printk all over the place to figure out what the
> code is actually doing.
Heh, this is exatly what I do when I debug regulatory issues :)
> I think some more effort should go into printing out a lot more
> information about the regulator domain decisions, through printk
> or related call if nothing better is found...
IMHO the regulatory code is the most fragile part of Linux wireless
stack and needs a rewrite. It needs to be simple and easy to understand.
--
Kalle Valo
next prev parent reply other threads:[~2014-06-24 5:47 UTC|newest]
Thread overview: 24+ 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 19:15 ` [wireless-regdb] " Luis R. Rodriguez
2014-06-23 20:37 ` Ben Greear
2014-06-23 20:54 ` Luis R. Rodriguez
2014-06-23 20:54 ` [wireless-regdb] " Luis R. Rodriguez
2014-06-23 21:20 ` Ben Greear
2014-06-24 0:44 ` Luis R. Rodriguez
2014-06-24 0:44 ` [wireless-regdb] " Luis R. Rodriguez
2014-06-24 2:35 ` Ben Greear
2014-06-24 2:53 ` Luis R. Rodriguez
2014-06-24 2:53 ` [wireless-regdb] " Luis R. Rodriguez
2014-06-25 16:48 ` Ben Greear
2014-06-25 17:20 ` Luis R. Rodriguez
2014-06-25 17:20 ` [wireless-regdb] " Luis R. Rodriguez
2014-06-25 17:34 ` Ben Greear
2014-06-25 17:37 ` Luis R. Rodriguez
2014-06-25 17:37 ` [wireless-regdb] " Luis R. Rodriguez
2014-06-26 6:50 ` Janusz Dziedzic
2014-06-26 6:50 ` [wireless-regdb] " Janusz Dziedzic
2014-06-24 5:47 ` Kalle Valo [this message]
2014-06-25 16:52 ` Luis R. Rodriguez
2014-06-25 16:52 ` [wireless-regdb] " 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=87pphy7ta5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=greearb@candelatech.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 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.