From: Maarten Lankhorst <maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Andy Ritger <aritger-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: offer to help, DCB
Date: Tue, 24 Sep 2013 09:12:02 +0200 [thread overview]
Message-ID: <52413B42.9050101@canonical.com> (raw)
In-Reply-To: <20130924044457.GA25785-4K9zQNqW3/fFT5IIyIEb6QC/G2K4zDHf@public.gmane.org>
Hey,
Op 24-09-13 06:44, Andy Ritger schreef:
> Hi Nouveau developers,
>
> NVIDIA is releasing public documentation on certain aspects of our GPUs,
> with the intent to address areas that impact the out-of-the-box usability
> of NVIDIA GPUs with Nouveau. We intend to provide more documentation
> over time, and guidance in additional areas as we are able.
>
> As a first step towards that, we've posted a document here:
>
> ftp://download.nvidia.com/open-gpu-doc/DCB/1/DCB-4.0-Specification.html
>
> that documents the Device Control Block ("DCB") layout in the VBIOS.
> The DCB describes board topology and the board's display connectors.
>
> I suspect much of the information in that document is not news for
> the Nouveau community, but hopefully it will be helpful to confirm your
> understanding or flesh out the implementation of a few unhandled cases.
>
> A few of us who work on NVIDIA's proprietary Linux GPU driver will pay
> attention to nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org and try to chime in when
> we can.
>
> If there are specific areas of documentation that would most help you, that
> feedback would help NVIDIA prioritize our documentation efforts.
>
> If you have specific questions for NVIDIA, you can ask here, or direct
> them to: open-gpu-doc-DDmLM1+adcqXj1p+fO2waQ@public.gmane.org I can't promise we'll be able to answer
> everything, but we'll provide best-effort in areas where we are able.
You rock! :D
Our biggest struggle at the moment is the video clocking and power management, which is highly device specific
and depends on configuration too. A complete video bios documentation would be nice too, I understand that will
take a bit longer than just the dcb. :)
~Maarten
next prev parent reply other threads:[~2013-09-24 7:12 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 [this message]
[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
[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=52413B42.9050101@canonical.com \
--to=maarten.lankhorst-z7wlfzj8ewms+fvcfc7uqw@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.