search for: g80

I've been talking about it for some time, but now it actually does something, so comitted it. I always said i wouldn't use the randr-1.2 clone stuff and i didn't, so you can use this as an example how it could also be done. What doesn't work (for sure): lvds with no ddc support no fbcon yet output/connector properties Notes: the bare minimum of bios code was imported (eventually

I have some things to add to renouveau.xml (NV50_MEMORY_TO_MEMORY_FORMAT high address words, and NV50COMPUTE object 0x50c0), see the attached patch Greetings, Wladimir -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.freedesktop.org/archives/nouveau/attachments/20071119/f65ec979/attachment.htm -------------- next part -------------- A non-text

Hi there, I'd like to help on finding out more details about the G8x hardware from NVidia, especially given these cards have more functionality than your average GPU: with CUDA ( http://developer.nvidia.com/object/cuda.html ) it is possible to use them as compute devices. This makes me very interested in their low level capabilities, like microcode/shader specifications, and maybe even how

...s that did not get a sensor calibration in the factory. Signed-off-by: Martin Peres <martin.peres at free.fr> --- configure.ac | 1 + drm/Kbuild | 4 ++ drm/core/include/subdev/fuse.h | 1 + drm/core/subdev/fuse/base.c | 1 + drm/core/subdev/fuse/g80.c | 1 + drm/core/subdev/fuse/gf100.c | 1 + drm/core/subdev/fuse/gm107.c | 1 + drm/core/subdev/fuse/priv.h | 1 + nvkm/engine/device/gm100.c | 2 + nvkm/engine/device/nv50.c | 15 ++++++++ nvkm/engine/device/nvc0.c | 10 +++++ nvkm/engine/device/nve0.c | 8 ++++...

...he factory. > > Signed-off-by: Martin Peres <martin.peres at free.fr> > --- > configure.ac | 1 + > drm/Kbuild | 4 ++ > drm/core/include/subdev/fuse.h | 1 + > drm/core/subdev/fuse/base.c | 1 + > drm/core/subdev/fuse/g80.c | 1 + > drm/core/subdev/fuse/gf100.c | 1 + > drm/core/subdev/fuse/gm107.c | 1 + > drm/core/subdev/fuse/priv.h | 1 + > nvkm/engine/device/gm100.c | 2 + > nvkm/engine/device/nv50.c | 15 ++++++++ > nvkm/engine/device/nvc0.c | 10 +++++ >...

This is primarily targeted at Koala_BR, but if someone happens to have a a fully working nouveay g80 setup, then go ahead. Maarten. (this is attempt 2, as 100 KiB seems to be the maximum allowed size) -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-NV50-Merge-crtc-creation.patch Type: text/x-patch Size: 2751 bytes Desc: not available Url : http://lists.fr...

...in the factory. > > Signed-off-by: Martin Peres <martin.peres at free.fr> > --- > configure.ac | 1 + > drm/Kbuild | 4 ++ > drm/core/include/subdev/fuse.h | 1 + > drm/core/subdev/fuse/base.c | 1 + > drm/core/subdev/fuse/g80.c | 1 + > drm/core/subdev/fuse/gf100.c | 1 + > drm/core/subdev/fuse/gm107.c | 1 + > drm/core/subdev/fuse/priv.h | 1 + > nvkm/engine/device/gm100.c | 2 + > nvkm/engine/device/nv50.c | 15 ++++++++ > nvkm/engine/device/nvc0.c | 10 +++++ > nvkm/...

Ilia Mirkin wrote: > I suspect the fb0 issue is because you disabled > CONFIG_DRM_FBDEV_EMULATION? Does the freeze also happen with 4.3? Any > chance you could bisect? I saw this config option, but I didn't realize that. The issue also occurs with 4.3. I even tried 4.3-rc1 with the same results. Would the DRM_FBDEV_EMULATION effect 3D? > On Mon, Jan 11, 2016 at 7:23 PM, Wakko

For now pixmaps will only be tiled if driver pixmaps are being used and we're told to with the NOUVEAU_CREATE_PIXMAP_TILED usage hint. Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- src/nouveau_exa.c | 31 ++++++++++++++++++++----------- src/nv50_exa.c | 6 +++--- src/nv50_xv.c | 2 +- src/nv_proto.h | 2 +- src/nv_type.h | 1 + 5 files

...lay/nv3_pramdac.xml index 13b6a7b..e236921 100644 --- a/rnndb/display/nv3_pramdac.xml +++ b/rnndb/display/nv3_pramdac.xml @@ -79,12 +79,79 @@ <bitfield pos="28" name="VCLK_DB2"/> <bitfield pos="29" name="VCLK2_DB2" variants="NV11:NV20 NV25:G80"/> </reg32> + <reg32 offset="0x510" name="PLL_SETUP_CONTROL"/> <reg32 offset="0x520" name="VPLL2" variants="NV11:NV20 NV25:NV30 NV31:G80" type="nv3_pll"/> <reg32 offset="0x520" name="VPLL2&...

Hello, We recently tracked down a bug on Tesla GPUs (i.e. G80-GT218) whereby it appears that instructions like 00000028: b5000409 08000780 add rn f32 $r2 $r2 neg c0[$a1] 00000040: b500060d 08004780 add rn f32 $r3 $r3 neg c0[$a1+0x4] or with nvdisasm: .headerflags @"EF_CUDA_SM12 EF_CUDA_PTX_SM(EF_CUDA_SM12)" /*0000*/...

...pcicfg shadow region in the GPU's PCI BAR0 window at offset > 0x88000. (This was actually originally implemented for NV4x, so you'll > probably want to do that there as well.) Hm, I recently discovered this while looking for the errata myself, but it seems you guys only do it on G80/G84/G86, and use 0x88068 at some point after that, before Fermi (G96/GT200, for example). > It seems that this was done to > avoid a hardware bug that may cause the EOI write to be dropped, blocking > all further interrupts from being serviced. That was our theory also. Thanks for c...

I'm currently implementing mipmaps but I have a set of troubles guessing the block height and block depth of them. According to https://envytools.readthedocs.io/en/latest/hw/memory/g80-surface.html#textures-mipmapping-and-arrays the texture unit auto resizes mipmaps' blocks but how do I know how many blocks each one uses? I'm currently using this algorithm: u32 height = MipHeight(mip_level); u32 gobs_in_y = (height + 7) / 8; u32 bh = block_height;...

...ious interfaces no longer exist. For compatibility with the 0.0.13 kernel in drm.git the interface exposed is identical, however, the MM_ENABLED getparam will *always* return 1. Calling the older ioctls will return an error. - Kernel modesetting for all supported chipsets. - The code for G80 onwards should be fairly OK, it's mostly the same as what's in Fedora 11, which appears to work well. There are some changes from F11 though, see below. - For earlier chipsets, fbcon comes up fine, and X will start on all the cards I have available, but it hasn't been ove...

...t; On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater > <alastair.bridgewater at gmail.com> wrote: > > + /* HDMI 3D support */ > > + if ((disp->disp.oclass >= NV50_DISP) > > You probably meant G82_DISP. Although I don't know if there were any > G80's with DP or HDMI. Either way, all that logic is in hdmig84.c (and > newer), so ... :) > Having taken a closer look at the lower level code, I agree. It should be G82_DISP. Will correct in the v4 patch series (if there ends up being a v4 patch series). Good catch, and thank you! -- Ala...

Hello Bergström/Eric, Thanks for the reply. The G80(sm_10) architecture was ported on FPGA by a group of researchers (http://www.ecs.umass.edu/ece/tessier/andryc-fpt13.pdf). Our group have some further research interest on this work. I was working on modifying the Clang-LLVM for a couple of months and achieved the required changes. But Clang-LLVM is...

...; argument validation of the FBIOPAN_DISPLAY ioctl. > > CONFIG_FB_NVIDIA is a dedicated fbdev driver, not compatible with > nouveau (it takes over the relevant PCI device). It also won't support > your Pascal GPU, I believe -- I think it MIGHT support the Tesla > generation (i.e. G80..GT21x) but definitely not anything newer. Most > likely it supports pre-G80 GPUs, and again, not compatible with > nouveau. > > DRM-based drivers use the DRM <-> FBDEV emulation layer to provide an > fbdev interface for legacy applications. The fbdev emulation acts as > sor...

http://bugs.freedesktop.org/show_bug.cgi?id=12833 Summary: Geforce 8400M GS (id 0x427): stick to 800x600 Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

Well...it's been a bit of a mixed bag.? Setting drm_kms_helper.drm_fbdev_overalloc=200 set the vinfo.yres_virtual to 2160 as opposed to 1080 (My monitor vertical resolution)? This fixed the mmap() problem.? However, it only worked on my main workstation.? My laptop running Intel graphics wasn't affected by the change in kernel cmdline.? My workstation is a custom build from a few

...il I press Ctrl+C and quit the program. The output is: 9/80 test_draw_buffer No Stereo context. Skipping stereo tests No double buffering. Skipping double buffer tests No GL_EXT_vertex_weighting extension. No GL_NV_texgen_emboss extension. GL_NV_vertex_program3 crashes up until driver 100.14.19 on G80 - skipping. 79/80 test_arb_vertex_buffer_object_indexed The output of lspci is attached. Please let me know if I can get you any further logs or anything else that would assist you. Regards, Aaron -- FSF Associate Member: 5632 http://www.fsf.org -------------- next part -------------- An embed...