From: Jonathan Morton <chromatix99@gmail.com>
To: dpreed@reed.com
Cc: David Lang <david@lang.hm>,
make-wifi-fast@lists.bufferbloat.net,
Wayne Workman <wayne.workman2012@gmail.com>,
bufferbloat-fcc-discuss
<bufferbloat-fcc-discuss@lists.redbarn.org>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] [bufferbloat-fcc-discuss] arstechnica confirmstp-link router lockdown
Date: Tue, 15 Mar 2016 11:38:42 +0200 [thread overview]
Message-ID: <8F195AF3-ED59-4DAC-8B71-D8214693DD24@gmail.com> (raw)
In-Reply-To: <1458013678.063414576@mobile.rackspace.com>
> On 15 Mar, 2016, at 05:47, dpreed@reed.com wrote:
>
> 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.
As an example of this, AMD’s APUs and GPUs require several different firmware blobs to bring up their 3D capabilities. The on-board BIOS supplies only what is necessary for basic SVGA framebuffer mode, which the operating system can use as a stopgap until the drivers are installed.
In Linux, these firmware blobs are identified by the IP block’s codename. Most APUs and GPUs require a SUMO or SUMO2 blob to bring up the RAMDACs, and a separate GPU-specific blob (VERDE for my 7770) for the graphics engine itself, which takes up a much larger portion of the die.
I’m not sure whether these blobs are signed in AMD’s system, but they could be. Their APUs have a Cortex-A5 based “secure processor” which could in principle be tied into the firmware-loading process, and probably has its own secure ROM. A Cortex-M microcontroller core and ROM to do the job on a GPU would be tiny.
- Jonathan Morton
next prev parent reply other threads:[~2016-03-15 9:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 3:47 dpreed
2016-03-15 9:38 ` Jonathan Morton [this message]
-- 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=8F195AF3-ED59-4DAC-8B71-D8214693DD24@gmail.com \
--to=chromatix99@gmail.com \
--cc=bufferbloat-fcc-discuss@lists.redbarn.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=dpreed@reed.com \
--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