On 05/12/2017 12:21 PM, Steve deRosier wrote:
Hi Ben,
On Fri, May 12, 2017 at 7:12 AM, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote:
On 05/11/2017 04:38 AM, Kalle Valo wrote:
Simon Wunderlich <sw@xxxxxxxxxxxxxxxxxx> 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.
If someone with real authority ever complains, then the code could be
backed out again. Your opinion seems not much more informed than the
rest of us discussing this.
With all due respect, _I_ am quite well informed about this issue.
From my conversations with him, I'd also judge Kalle to be quite
informed likewise.
Anyway, if upstream is blocked, then maybe we could work on getting this
into LEDE?
Honestly, I don't see how this solves any problems. You're just moving
the chair. A chair that someone will stand on and fall off and get
hurt. LEDE, OpenWRT or even Buildroot is essentially just a big patch
and build system. For a closed-ecosystem manufacturer, which by
definition a public-safety band licensed equipment manufacturer must
be, can just as easily maintain their own internal fork of the kernel
with these patches sitting there.
That's not something I'd normally advocate, but it does seem
appropriate in this specific application.
Maintaining outside patches means work for everyone..but if there
is a single set of outside patches, then at least it is easier.
That is what LEDE might be able to offer.
As for keeping lame users from causing trouble, maybe we can merge
much of the code that often conflicts with upstream code but leave out a few key patches
to actually enable the feature. Then no one can just re-build
with a different kernel option (after hacking their regdb) and
get it to work.
All that said, I doubt this will matter at all to FCC because
if LEDE can boot on a device, it can already be put out of spec
without much trouble. Making it take 2 days of effort vs 1 hour
surely doesn't make a difference?
Thanks,
Ben
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
