All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Ritger <aritger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: offer to help, DCB
Date: Tue, 24 Sep 2013 17:34:22 -0700	[thread overview]
Message-ID: <20130925003422.GE28691@parker.nvidia.com> (raw)
In-Reply-To: <CAPM=9tykSx_p-SgK9+JpUADD8E_M6ciS5kXd68UaE-A9-sgiYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, Sep 24, 2013 at 12:43:46PM -0700, Dave Airlie wrote:
...
> 
> Hey Andy,
> 
> this is great news,
> 
> I suppose the question I have is there any known upfront limits on
> what you can release or is it going to be a per-request type thing?

Hi Dave.

I think we're going to have to deal with things on a case-by-case basis.
I wouldn't take anything off the table, yet.  You all can probably
imagine what areas may have IP/security/whatever entanglements, which
will be more painful for NVIDIA to sort through.  But, for now, just
enumerate what information would be most useful.  The more specific and
targeted the request, the more focused (and hopefully efficient) the
internal vetting process can be.

> My main request if you give Ben whatever he asks for :-P, but I'm
> interested if you guys would be also able to say review things like
> the microcode situation and say explaining what might be missing from
> the nouveau microcode for context switching etc,

For microcode: from NVIDIA's perspective, I think we'd like to move to
a model where NVIDIA releases microcode firmware (as binary-only) with a
defined ABI, versioning, and reasonable licensing to allow redistribution.
We have some release engineering process improvements to make there, since
today the firmware is allowed to evolve along side the NVIDIA proprietary
driver code, and the two are released in lock-step.  But longer-term,
I think we'd like to move things to the firmware that either we're not
comfortable documenting, or things that are Real Hard to get right,
like P-state switching.

Does Nouveau reimplement Falcon microcode due to particular deficiencies
in NVIDIA's microcode, or because you couldn't get permission in the past
to redistribute the firmware extracted from NVIDIA's proprietary driver?
If the latter, I think we can get to the point of solving that with more
amenable licensing.  If the former, I'd like to report the deficiencies
from your point of view back to NVIDIA's firmware team, so that we can
improve the firmware for Nouveau use.

While I know open firmware would be preferred over binary-only firmware
images, hopefully we can find a reasonable compromise there.

> along with VM things like hw with pagefaults etc.

I don't have a great sense for how much internal concern there will be
around pagetable-related documentation.  My guess is that it might be
a little harder than DCB and other BIOS-related docs, but much easier
than clock programming.

Thanks,
- Andy

> Dave.

  parent reply	other threads:[~2013-09-25  0:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24  4:44 offer to help, DCB Andy Ritger
     [not found] ` <20130924044457.GA25785-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2013-09-24  7:12   ` Maarten Lankhorst
     [not found]     ` <52413B42.9050101-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2013-09-24 18:19       ` Andy Ritger
     [not found]         ` <20130924181938.GD27823-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2013-09-24 19:43           ` Dave Airlie
     [not found]             ` <CAPM=9tykSx_p-SgK9+JpUADD8E_M6ciS5kXd68UaE-A9-sgiYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-25  0:34               ` Andy Ritger [this message]
     [not found]                 ` <20130925003422.GE28691-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
2013-09-25  0:59                   ` Dave Airlie
2013-09-25  7:46                   ` Marcin Kościelnicki
     [not found]                     ` <524294C4.20701-mP9o5jsk0RY@public.gmane.org>
2013-09-27 17:52                       ` Andy Ritger
2013-09-24 17:27   ` Ben Skeggs

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=20130925003422.GE28691@parker.nvidia.com \
    --to=aritger-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@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.