From: dpreed@reed.com
To: "David Lang" <david@lang.hm>
Cc: "Wayne Workman" <wayne.workman2012@gmail.com>,
"bufferbloat-fcc-discuss"
<bufferbloat-fcc-discuss@lists.redbarn.org>,
cerowrt-devel@lists.bufferbloat.net,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] [bufferbloat-fcc-discuss] arstechnica confirmstp-link router lockdown
Date: Mon, 14 Mar 2016 23:47:58 -0400 (EDT) [thread overview]
Message-ID: <1458013678.063414576@mobile.rackspace.com> (raw)
There are many processor architectures that have different instruction memories for different functional units.
SoCs often have multiple functional units on the same die. For radios that allows for a pipeline. You can limit what an EPROM will accept with a crypto signature.
This is common stuff.
-----Original Message-----
From: "David Lang" <david@lang.hm>
Sent: Mon, Mar 14, 2016 at 3:04 pm
To: dpreed@reed.com
Cc: "Wayne Workman" <wayne.workman2012@gmail.com>, "bufferbloat-fcc-discuss" <bufferbloat-fcc-discuss@lists.redbarn.org>, cerowrt-devel@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [bufferbloat-fcc-discuss] [Cerowrt-devel]arstechnica confirmstp-link router lockdown
On Mon, 14 Mar 2016, dpreed@reed.com wrote:
> An external "limit-exceeding signal detector" could also be very inexpensive,
> if it did not need to do ADC from the transmitted signal, but could get access
> to the digital samples and do a simple power measurement.
I agree with this, but have concerns about how you can lock down part of the
firmware and not all of it.
You still have the problem of telling the chip/algorithm which set of rules to
enforce, and updating it when the requirements change.
David Lang
next reply other threads:[~2016-03-15 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 3:47 dpreed [this message]
2016-03-15 9:38 ` Jonathan Morton
-- strict thread matches above, loose matches on Subject: below --
2016-03-14 14:02 [Cerowrt-devel] " dpreed
2016-03-14 14:14 ` [Cerowrt-devel] [Make-wifi-fast] " Jonathan Morton
[not found] ` <CAEfCu-oCfO+FfdLjpZDSwQmZ7-Mc+X4vDvzZMNrnp+p8ut8OKQ@mail.gmail.com>
2016-03-14 17:49 ` [Cerowrt-devel] [bufferbloat-fcc-discuss] [Make-wifi-fast] " dpreed
2016-03-14 19:04 ` [Cerowrt-devel] [Make-wifi-fast] [bufferbloat-fcc-discuss] " David Lang
2016-03-14 19:07 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1458013678.063414576@mobile.rackspace.com \
--to=dpreed@reed.com \
--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