similar to: DCB 4.1 spec update

On Wed, Dec 10, 2014 at 7:36 AM, Ben Skeggs <skeggsb at gmail.com> wrote: > On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: >> Hi, > Hey Andy, > >> >> The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. >> I've posted an updated DCB spec here: >> >>

On Sat, Dec 13, 2014 at 6:42 PM, Andy Ritger <aritger at nvidia.com> wrote: > On Wed, Dec 10, 2014 at 07:46:16AM +1000, Ben Skeggs wrote: >> On Wed, Dec 10, 2014 at 7:36 AM, Ben Skeggs <skeggsb at gmail.com> wrote: >> > On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: >> >> Hi, >> > Hey Andy, >> > >>

On Wed, Dec 10, 2014 at 07:46:16AM +1000, Ben Skeggs wrote: > On Wed, Dec 10, 2014 at 7:36 AM, Ben Skeggs <skeggsb at gmail.com> wrote: > > On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: > >> Hi, > > Hey Andy, > > > >> > >> The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. > >>

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:

On Wed, Dec 10, 2014 at 4:26 AM, Andy Ritger <aritger at nvidia.com> wrote: > Hi, Hey Andy, > > The VBIOS on GM20x GPUs uses a slightly updated version of the DCB. > I've posted an updated DCB spec here: > > ftp://download.nvidia.com/open-gpu-doc/DCB/2/DCB-4.x-Specification.html > > You can diff it against the previous version: > >

Greetings, box: bog standard [tc]rusty old Nvidia equipped Q6600 Medion (Aldi) deskside kernel: master.today (v4.12-11690-gccd5d1b91f22) lspci -nn -d 10de: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) abreviated dmesg: ... [ 3.720990] fb: switching to nouveaufb from VESA VGA [ 3.744489] Console: switching to colour dummy device

https://bugs.freedesktop.org/show_bug.cgi?id=101887 Bug ID: 101887 Summary: gtx 970 black screen Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

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,

This is the beginnings of HDMI 2.0 support. All of the "extra" features are left out, such as 12/16bpc, YUV420, etc. I've verified that with this code, a GP108 (GT1030) can switch between 4k at 60 and 1920x1080 at 60 on a LG 4K TV. Further, I've verified via i2c tools, that the SCDC writes really do happen. I suspect that the patch for keeping track of the high-speed TMDS

I have the signed firmware (I think) and I'm running a fresh 4.6 kernel. I got an image to show up briefly, rendering the Fedora sign-in screen at something like one frame per ten seconds. But then I got all kinds of garbage, and I see: [ 719.300820] nouveau 0000:09:00.0: disp: outp 04:0006:0f44: link training failed dmesg |grep nouveau says: [ 10.053162] fb: switching to nouveaufb

small update to my last version I sent out. Patches 3-6 are optional and should only improve detecting the max clocks for HDMI and DP, but they didn't underwent big testing and I am a bit concerned, that it might break detecting the DP limits on some boards. Karol Herbst (6): kms/nv50: move nv50_mstm out of the dp union in nouveau_encoder kms/nv50: reject interlaced modes if the hardware

Hi Ben, still _assuming_ it's an issue of the card I thought about why it works with the NVIDIA binary driver. And I can image they're just trying to do an identity-mapping first and if that doesn't work (e.g. the particular SOR is already in use by another macro link) they just pick the next suitable one. So the case would be that the NVIDIA binary driver always assignes the only

On Mon, Nov 24, 2014 at 8:33 PM, Andy Ritger <aritger at nvidia.com> wrote: > On Fri, Nov 21, 2014 at 01:39:55AM -0500, Ilia Mirkin wrote: >> On Fri, Nov 21, 2014 at 1:16 AM, Andy Ritger <aritger at nvidia.com> wrote: >> > Hi Ilia, >> > >> > Actually 0x90b8 is different than copy engine. I'm not very familiar >> > with it, but 0x90b8 is

On Tue, Sep 24, 2013 at 12:12:02AM -0700, Maarten Lankhorst wrote: > 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

Taken from NVIDIA binary driver (Linux 64-bit, revision 390.25) from README.txt. Signed-off-by: Danilo Krummrich <danilokrummrich at dk-develop.de> --- drivers/gpu/drm/nouveau/nvkm/engine/device/pci.c | 41 ++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/device/pci.c b/drivers/gpu/drm/nouveau/nvkm/engine/device/pci.c index

My new GTX 960 (GM206, I think) says: [ 10.329351] nouveau ![ DEVICE][0000:09:00.0] unknown Maxwell chipset [ 10.329355] nouveau E[ DEVICE][0000:09:00.0] unknown chipset, 0x126010a1 [ 10.329356] nouveau E[ DRM] failed to create 0x00000080, -22 [ 10.330129] nouveau: probe of 0000:09:00.0 failed with error -22 Hacking up nouveau so that it treats it like a GM204 doesn't work. Are

From: Hauke Mehrtens <hauke at hauke-m.de> Without this patch a pixel clock rate above 165 MHz on a TMDS link is assumed to be dual link. This is true for DVI, but not for HDMI. HDMI supports no dual link, but it supports pixel clock rates above 165 MHz. Only activate Dual Link mode when it is actual possible. Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de> Signed-off-by: Ilia

Taken from NVIDIA binary driver (Linux 64-bit, revision 390.25) from README.txt. Signed-off-by: Danilo Krummrich <danilokrummrich at dk-develop.de> --- drivers/gpu/drm/nouveau/nvkm/engine/device/pci.c | 41 ++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/device/pci.c b/drivers/gpu/drm/nouveau/nvkm/engine/device/pci.c index

Hi again, I got a new dmesg log with the debug parameters, but I guess I could not isolate VESA. I blacklisted it at /etc/modprobe.d/blacklist.conf but comparing those logs I see no difference... Is it possible to isolate VESA somehow without removing it? The new logs are here, I'm posting full content because I'm not sure what information is more relevant...

On Tue, Mar 17, 2015 at 2:57 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Tue, Mar 17, 2015 at 5:52 PM, Andy Lutomirski <luto at amacapital.net> wrote: >> On Fri, Feb 13, 2015 at 9:52 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>> On Fri, Feb 13, 2015 at 8:59 PM, Andy Lutomirski <luto at amacapital.net> wrote: >>>> My new GTX 960