From: Brandon Butterworth <brandon@rd.bbc.co.uk>
To: wayne.workman2012@gmail.com, david@lang.hm
Cc: make-wifi-fast@lists.bufferbloat.net,
bufferbloat-fcc-discuss@lists.redbarn.org,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [bufferbloat-fcc-discuss] arstechnica confirms tp-link router lockdown
Date: Sun, 13 Mar 2016 13:25:47 GMT [thread overview]
Message-ID: <201603131325.NAA15063@sunf10.rd.bbc.co.uk> (raw)
On Sat, 13 Mar 2016, David lang wrote:
> I would do us no good to create a fully open chip if the FCC mandates
> that the firmware must be locked down.
Which firmware must be locked down? I was under the impression that is
just retail end user devices, is the suggestion that chip manufacturers
will not be allowed to sell parts to people who might make a non locked
down device? Does that include if they don't supply firmware and the
user writes their own/reverse engineers others? Sounds like a road to
future regulating all rf hardware sale (stop people selling rp
connectors as it's letting them circumvent the antenna limitations they
were designed to impose?)
Given the interference that caused this is a few incidents a year
compared to the millions of units sold and that those cases were
either bad users or caused by faulty devices it seems that the
lock down would have to be total to prevent future incidents. Quite
impractical.
> Would I like someone to do this, Sure. I'll contribute towards a
> kickstarter, even if it's $100 for a mini-pci card that is the
> equivalent of what we can get today for $30, but it would take
> tens of thousands of people doing that to fund the project, and
> I have serious doubts if you can get that much funding for
> something with such a long lead time.
It think it would be cheaper and quicker to reverse engineer drivers
for others hardware. Even if the cost could be covered to build it'd
lag commercial products by years making it a difficult sell, and likely
subjected to IPR claims from current manufacturers
> If someone does the research and puts together a FPGA version
That could be an interesting project. It may not help but we have
an FPGA MIMO implementation we may be able to release to such a
project (it may be unsuitable though, we've been making radio cameras
https://www.google.co.uk/?gws_rd=ssl#q=bbc+r%26d+mimo
https://www.google.co.uk/?gws_rd=ssl#q=bbc+r%26d+halfrf )
> and is looking for funding to convert it to a ASIC, I think you
> could get funding. But that's not the question in front of us now.
Yes, and if the lock down expands to chips too would have
the same problem
brandon
next reply other threads:[~2016-03-13 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 13:25 Brandon Butterworth [this message]
2016-03-13 23:20 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2016-03-11 18:17 [Make-wifi-fast] " Dave Taht
[not found] ` <CAEfCu-rQN+H7h0OY_3CSrrGcVZ=A4=b0XTAU2h3Pz3_ksh56dw@mail.gmail.com>
2016-03-12 19:14 ` [Make-wifi-fast] [bufferbloat-fcc-discuss] " Henning Rogge
2016-03-12 20:18 ` Adrian Chadd
[not found] ` <CAEfCu-rmR=p1bAGJjPvaMMBAjKRU1wBeZW4ZQCZVm5eVXCCRQQ@mail.gmail.com>
2016-03-12 22:20 ` Dave Taht
2016-03-13 1:04 ` David Lang
[not found] ` <CAEfCu-r-C3C6P2LpKJduvX733YnbwxBF6nOFAPEMbF28qjRXBg@mail.gmail.com>
2016-03-13 8:06 ` David Lang
2016-03-14 0:51 ` Adrian Chadd
2016-03-14 1:25 ` David Lang
2016-03-13 18:19 ` Dave Taht
2016-03-13 1:00 ` David Lang
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201603131325.NAA15063@sunf10.rd.bbc.co.uk \
--to=brandon@rd.bbc.co.uk \
--cc=bufferbloat-fcc-discuss@lists.redbarn.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=wayne.workman2012@gmail.com \
/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