From: Martin Peres <martin.peres-GANU6spQydw@public.gmane.org>
To: Andy Ritger <aritger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: NVIDIA Falcon Microprocessor Security
Date: Sat, 27 Sep 2014 01:15:46 +0200 [thread overview]
Message-ID: <5425F3A2.3050703@free.fr> (raw)
In-Reply-To: <20140926171939.GE6384-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
Hi Andy,
On 26/09/2014 19:19, Andy Ritger wrote:
> Hi, all.
>
> Below is a link to a brief document describing some changes in NVIDIA
> Falcon processors ("fuc", in Nouveau-speak, IIUC)
We actually renamed most of our docs to falcon :)
> that happened in
> Maxwell: certain aspects of the chip will only be available to Falcon
> firmware images signed by NVIDIA. So far, the set of restricted things
> is pretty small, but I expect this list will slowly grow over future
> hardware generations.
>
> ftp://download.nvidia.com/open-gpu-doc/Falcon-Security/1/Falcon-Security.html
>
> I suspect this will not be the most popular decision, but it is the
> direction the hardware is taking.
Thank you for the heads-up! We actually wondered yesterday about
what kind of operations were forbidden without a signed falcon.
> On a slightly different note, we'd like to work out the best way to
> make NVIDIA firmware images separately (from the rest of the driver)
> available and officially redistributable for use by Nouveau. At this
> point, it is mostly just a release engineering question, but I don't think
> we'll have a lot of influence over the content: the engineers working on
> Falcon microcode assume it changes in lock-step with NVIDIA's nvidia.ko,
> so there are no backwards compatibility guarantees. How painful has
> the lack of backwards compatibility been for Nouveau thus far?
>
> If NVIDIA just released firmware binaries along side each NVIDIA GPU driver
> release, would it be reasonable for Nouveau to pick and choose which
> firmware you'd like promoted to, e.g.,
>
> http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/
>
> ?
>
> Anyway, this might be a good topic to discuss at XDC. It looks I'll
> see a lot of you then; I'm looking forward to it!
Yeah, this really seems like a very good discussion to have at XDC. I'll
find a room for us to sit and discuss the problem.
Thanks again and see you soon!
Martin
next prev parent reply other threads:[~2014-09-26 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 17:19 NVIDIA Falcon Microprocessor Security Andy Ritger
[not found] ` <20140926171939.GE6384-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2014-09-26 23:15 ` Martin Peres [this message]
2014-09-27 0:13 ` Ben Skeggs
[not found] ` <CACAvsv7WgxpE5qK=9tnebhj-JEt+epOfHzqoK+wx+_yGXV-jFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-27 1:02 ` Andy Ritger
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=5425F3A2.3050703@free.fr \
--to=martin.peres-ganu6spqydw@public.gmane.org \
--cc=aritger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.