similar to: H.264 engine differences between fermi and tesla cards

On Thu, Nov 21, 2013 at 5:22 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Thu, Nov 21, 2013 at 5:07 PM, Benjamin Morris <bmorris at nvidia.com> wrote: >> On 11/19/2013 08:16 PM, Ilia Mirkin wrote: >>> Hello, >>> >>> I hope this is an appropriate style of request for this forum. I added >>> code to support video decoding on the tesla

On Thu, Nov 21, 2013 at 5:07 PM, Benjamin Morris <bmorris at nvidia.com> wrote: > On 11/19/2013 08:16 PM, Ilia Mirkin wrote: >> Hello, >> >> I hope this is an appropriate style of request for this forum. I added >> code to support video decoding on the tesla cards that have a >> similar-style video decoding engine to fermi cards (i.e. G98, GT21x, >> the

On Sat, 30 Nov 2013 12:54:45 -0800 Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Thu, Nov 21, 2013 at 5:22 PM, Ilia Mirkin <imirkin at alum.mit.edu> > wrote: > > On Thu, Nov 21, 2013 at 5:07 PM, Benjamin Morris > > <bmorris at nvidia.com> wrote: > >> On 11/19/2013 08:16 PM, Ilia Mirkin wrote: > >>> Hello, > >>> >

Hello, I hope this is an appropriate style of request for this forum. I added code to support video decoding on the tesla cards that have a similar-style video decoding engine to fermi cards (i.e. G98, GT21x, the IGP's -- the falcon-controlled decoding engines, rather than the xtensa-controlled ones), by using pretty much the same logic that we had for the fermi cards. This worked great for

On Fri, Dec 6, 2013 at 7:36 PM, Benjamin Morris <bmorris at nvidia.com> wrote: > I've gathered a few hints regarding H264 video decoding on our hardware. Hopefully some of them will be useful. Very useful! > > First off, regarding naming in general. Our internal names for our video engines differ from the names you've been using. Below is a translation map between the

Hello, We're seeing a very odd issue on many (all?) tesla chips (G8x, G9x, G200, GT21x) related to looping. People will have loops in glsl like for (i = 0; i < 200; i++) { ... if (cond) break; } And it seems like if it breaks out of the loop early, all's well, but eventually it peeters out (I haven't figured out exactly when though). See bug at

Hello I recently retired my old desktop which has a Nvidia Geforce 480 GTX in it. I'm now hoping to use it as a development box for Nouveau. I have no experience with Nouveau development but am hoping to try and work on clocking support for the 480 and am wondering how to start? I have watched a few videos in particular the XDC2014 Project ReClock by Roy Spliet. Where is the current FERMI

Hi Andy, Thanks for checking! I do see an issue on Tesla as well (at least G92, and I believe someone else reported on a GT215 or GT218). However I haven't confirmed that it's the identical issue to what I see on Fermi with quite as much certainty as what I've checked on a GF108. (For the G92, the texture buffer object test fails in the same way it does on Fermi, but there could be

Hello, I've recently run into an unknown bit in Tesla shaders, and was hoping you could shed some light on it. I believe they're related to clamping of some sort. Here are 2 examples (from diff shaders): a0000401 cc054780 cvt rpi f32 $r0 f32 $r2 [unknown: 00000000 00010000] a000060d 8c014780 cvt rni s32 $r3 f32 $r3 [unknown: 00000000 00010000] [This is intel-style syntax, cvt =

Hello poma, The chipset didn't disappear and is still displayed: it is the G98 you get on the "[ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)" line. The "NV98" was the "Nouveau" chipset, but the switch was made to use the same naming as NVIDIA. So rather than displaying both the Nouveau version of the chipset and the NVIDIA one, it make sense to only

Hello Paul I have a GTX 480 (GF100 I believe) at home in an old machine. Is the rest of the Fermi patch set available somewhere for me to test? Thank you Regards Brock On 16 Jan. 2018 9:08 am, "Lyude Paul" <lyude at redhat.com> wrote: It's here! After a lot of investigation, rewrites, and traces, I present the patch series to implement all known )levels of clockgating for

Hi, I would like to donate my "GT630" card (which is actually Fermi/NVC0 family based) to support Nouveau's further development for this hardware generation. It's this model: http://www.inno3d.com/product/gt630_4gb_dual.html Anyone interested? Regards, Moritz Meiser

Hi all PathScale is giving away a limited amount of Nvidia Fermi cards to qualified open source developers and researchers. We are mainly focused on our optimized gpu compiler and the HPC market, but also open to sponsoring creative ideas or projects surrounding the gpu. Here's a short list of some of the areas most interesting to us * Nouveau/kernel drivers * CUDA * OpenCL

Hello, This question is in the context of Tesla / Fermi generations, which have explicit bindings for textures / samplers. It might also apply to Kepler+, not quite as sure due to the bindless nature. I've been trying to understand how the TLD operation works (which is used to implement texelFetch in GLSL). It does not appear to the op takes an explicit sampler id at all (unlike all the

On 02.12.2014 14:52, Ilia Mirkin wrote: > On Tue, Dec 2, 2014 at 8:50 AM, poma <pomidorabelisima at gmail.com> wrote: >> On 02.12.2014 14:40, Ilia Mirkin wrote: >>> On Tue, Dec 2, 2014 at 8:38 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> Is this expected result for Chipset: G98 (NV98)? >>> >>> Yep, 100% expected. [Perhaps you

On Fri, May 16, 2014 at 11:17 PM, Ben Skeggs <skeggsb at gmail.com> wrote: > On 17 May 2014 02:43, "Ilia Mirkin" <imirkin at alum.mit.edu> wrote: >> >> Adds a NvReclock boolean option to allow the user to enable (or disable) >> reclocking. All chipsets default to off, except NVAA/NVAC, which are >> reportedly complete. > Hey Ilia, > > I

Hi Martin, I was asked to clarify a few things: (1) Are all the user reports of loud fans on Fermi-era GPUs? (2) When the VBIOS POSTs the card, it loads initial ucode onto the Falcon processor (PMU), which will do basic fan management on its own. We call this init ucode "IFR" (Init From ROM). nvidia.ko will restore the IFR ucode when unloaded. I assume the loud fan symptom occurs

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- .../drivers/nouveau/codegen/nv50_ir_lowering_nvc0.cpp | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_lowering_nvc0.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_lowering_nvc0.cpp index f010767..4a9e48f 100644 ---

https://bugs.freedesktop.org/show_bug.cgi?id=71994 Priority: medium Bug ID: 71994 Assignee: nouveau at lists.freedesktop.org Summary: Can't set performance level on Fermi card, Linux 3.13 Severity: normal Classification: Unclassified OS: All Reporter: anakin.cs at gmail.com Hardware: Other

4.1.8-200.fc22.x86_64 dmesg: [ 11.809467] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x098200a2 [ 11.809493] nouveau [ DEVICE][0000:02:00.0] Chipset: G98 (NV98) [ 11.809508] nouveau [ DEVICE][0000:02:00.0] Family : NV50 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: [ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2) Where vanished these Chipset & Family super cool lines?