search for: pixremap_supported

Displaying 5 results from an estimated 5 matches for "pixremap_supported".

2014 Nov 25
3
Second copy engine on GF116
...3 for 0x104650 and 4 for 0x105650. We're using the engine at >> 0x104000 for copy on the GF108... > > Yes, 0x104650 and 0x105650 are the right addresses, from what I can tell. > > FWIW, the other capability bits are: > bit 0: "DMACOPY_SUPPORTED" > bit 1: "PIXREMAP_SUPPORTED" > > (I think PIXREMAP_SUPPORTED is in reference to the component remapping > controlled by methods 0x00000700, 0x00000704, and 0x00000708 in the > copy engine class). Neat. We went around and grabbed that 0x650 register on a bunch of GPUs, see the CE* columns at: http://envytool...
2014 Nov 21
3
Second copy engine on GF116
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 an engine for performing LZO decompression as > part of performing the copy. It has a variety of limitations (e.g., > cannot handle blocklinear format), and was only in a few Fermi
2014 Nov 25
0
Second copy engine on GF116
...08 right now, which > returns 3 for 0x104650 and 4 for 0x105650. We're using the engine at > 0x104000 for copy on the GF108... Yes, 0x104650 and 0x105650 are the right addresses, from what I can tell. FWIW, the other capability bits are: bit 0: "DMACOPY_SUPPORTED" bit 1: "PIXREMAP_SUPPORTED" (I think PIXREMAP_SUPPORTED is in reference to the component remapping controlled by methods 0x00000700, 0x00000704, and 0x00000708 in the copy engine class). > From my admittedly limited understanding, both 0x104000 and 0x105000 > appear to be falcon engines, where the fuc is presuma...
2014 Nov 25
0
Second copy engine on GF116
...We're using the engine at > >> 0x104000 for copy on the GF108... > > > > Yes, 0x104650 and 0x105650 are the right addresses, from what I can tell. > > > > FWIW, the other capability bits are: > > bit 0: "DMACOPY_SUPPORTED" > > bit 1: "PIXREMAP_SUPPORTED" > > > > (I think PIXREMAP_SUPPORTED is in reference to the component remapping > > controlled by methods 0x00000700, 0x00000704, and 0x00000708 in the > > copy engine class). > > Neat. We went around and grabbed that 0x650 register on a bunch of > GPUs, see t...
2014 Nov 26
1
Second copy engine on GF116
...engine at >>>> 0x104000 for copy on the GF108... >>> >>> Yes, 0x104650 and 0x105650 are the right addresses, from what I can tell. >>> >>> FWIW, the other capability bits are: >>> bit 0: "DMACOPY_SUPPORTED" >>> bit 1: "PIXREMAP_SUPPORTED" >>> >>> (I think PIXREMAP_SUPPORTED is in reference to the component remapping >>> controlled by methods 0x00000700, 0x00000704, and 0x00000708 in the >>> copy engine class). >> >> Neat. We went around and grabbed that 0x650 register on a bunch...