From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: "Luis R. Rodriguez" <mcgrof-IBi9RG/b67k@public.gmane.org>
Cc: linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
Felix Fietkau <nbd-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>,
John Walker <john-40Xsf+s1Dzo@public.gmane.org>,
Krishna Chaitanya
<chaitanya.mgit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Richard Fontana <fontana-7LmRToLsLASJEOdND1YtKA@public.gmane.org>
Subject: Re: Parser stable fix question for CFG80211_INTERNAL_REGDB
Date: Tue, 1 Jul 2014 10:41:49 -0400 [thread overview]
Message-ID: <20140701144149.GB6358@tuxdriver.com> (raw)
In-Reply-To: <CAB=NE6VTN==Ewvf4HhTcadWLzjZnYkF1xSM1Yej6QfotWHKY0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Jun 30, 2014 at 12:19:08PM -0700, Luis R. Rodriguez wrote:
> On Mon, Jun 30, 2014 at 11:55 AM, Luis R. Rodriguez
> <mcgrof-3uybbJdB1yH774rrrx3eTA@public.gmane.org> wrote:
> > For the current kernel we
> > could intake the patch below, and I can port the change to no use
> > dfs_cac, that would enable older kernels to use new and older versions
> > of the ASCII database file.
>
> Personally I actually rather avoid us accept a patch upstream for a
> userspace change. The problem here is that we failed to realize the
> impact of CFG80211_INTERNAL_REGDB at build time with a userspace tool,
> in this case the db.txt file wireless-regdb provides and its format.
>
> If we wanted to avoid a stable patch we could require a match between
> wireless-regdb input file used for a kernel when
> CFG80211_INTERNAL_REGDB is used at build time. That would require
> different ASCII files on wireless-regdb or having the users of
> CFG80211_INTERNAL_REGDB do the conversion themselves. Upstream would
> just follow the wireless-regdb latest format. This then would just
> require upstream a Kconfig update to clarify the requirements.
>
> This seems like a rather lazy option but also one that would be rather
> more fair and honest for upstream, we could deal with a proper fix by
> reconsidering the implementation of CFG80211_INTERNAL_REGDB completely
> for future kernels.
I'm shocked that anyone actually uses CFG80211_INTERNAL_REGDB...
Anyway, I don't see the big deal. We should keep
CFG80211_INTERNAL_REGDB (whether implemented in awk or C) up-to-date
with current kernels. Anyone wanting to use an old kernel with an
updated wireless-regdb file is responsible for ensuring compatibility.
If they can't do that, then they should seek support from a vendor.
How is this any different from any other kernel support issue?
John
--
John W. Linville Someday the world will need a hero, and you
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org might be all we have. Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felix Fietkau <nbd@openwrt.org>, John Walker <john@x109.net>,
Krishna Chaitanya <chaitanya.mgit@gmail.com>,
netfilter-devel@vger.kernel.org,
Richard Fontana <fontana@sharpeleven.org>
Subject: Re: Parser stable fix question for CFG80211_INTERNAL_REGDB
Date: Tue, 1 Jul 2014 10:41:49 -0400 [thread overview]
Message-ID: <20140701144149.GB6358@tuxdriver.com> (raw)
In-Reply-To: <CAB=NE6VTN==Ewvf4HhTcadWLzjZnYkF1xSM1Yej6QfotWHKY0A@mail.gmail.com>
On Mon, Jun 30, 2014 at 12:19:08PM -0700, Luis R. Rodriguez wrote:
> On Mon, Jun 30, 2014 at 11:55 AM, Luis R. Rodriguez
> <mcgrof@do-not-panic.com> wrote:
> > For the current kernel we
> > could intake the patch below, and I can port the change to no use
> > dfs_cac, that would enable older kernels to use new and older versions
> > of the ASCII database file.
>
> Personally I actually rather avoid us accept a patch upstream for a
> userspace change. The problem here is that we failed to realize the
> impact of CFG80211_INTERNAL_REGDB at build time with a userspace tool,
> in this case the db.txt file wireless-regdb provides and its format.
>
> If we wanted to avoid a stable patch we could require a match between
> wireless-regdb input file used for a kernel when
> CFG80211_INTERNAL_REGDB is used at build time. That would require
> different ASCII files on wireless-regdb or having the users of
> CFG80211_INTERNAL_REGDB do the conversion themselves. Upstream would
> just follow the wireless-regdb latest format. This then would just
> require upstream a Kconfig update to clarify the requirements.
>
> This seems like a rather lazy option but also one that would be rather
> more fair and honest for upstream, we could deal with a proper fix by
> reconsidering the implementation of CFG80211_INTERNAL_REGDB completely
> for future kernels.
I'm shocked that anyone actually uses CFG80211_INTERNAL_REGDB...
Anyway, I don't see the big deal. We should keep
CFG80211_INTERNAL_REGDB (whether implemented in awk or C) up-to-date
with current kernels. Anyone wanting to use an old kernel with an
updated wireless-regdb file is responsible for ensuring compatibility.
If they can't do that, then they should seek support from a vendor.
How is this any different from any other kernel support issue?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-07-01 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 18:55 Parser stable fix question for CFG80211_INTERNAL_REGDB Luis R. Rodriguez
2014-06-30 18:55 ` Luis R. Rodriguez
2014-06-30 19:19 ` Luis R. Rodriguez
[not found] ` <CAB=NE6VTN==Ewvf4HhTcadWLzjZnYkF1xSM1Yej6QfotWHKY0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-01 14:41 ` John W. Linville [this message]
2014-07-01 14:41 ` John W. Linville
[not found] ` <20140701144149.GB6358-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-07-01 17:17 ` Luis R. Rodriguez
2014-07-01 17:17 ` Luis R. Rodriguez
2014-07-01 18:54 ` Luis R. Rodriguez
2014-07-01 20:18 ` John W. Linville
2014-07-02 7:33 ` Krishna Chaitanya
2014-07-02 12:04 ` Maxime Bizon
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=20140701144149.GB6358@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=chaitanya.mgit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=fontana-7LmRToLsLASJEOdND1YtKA@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=john-40Xsf+s1Dzo@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mcgrof-IBi9RG/b67k@public.gmane.org \
--cc=nbd-p3rKhJxN3npAfugRpC6u6w@public.gmane.org \
--cc=netfilter-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.