Displaying 20 results from an estimated 1000 matches similar to: "Tesla branch limits?"
2013 Nov 21
2
H.264 engine differences between fermi and tesla cards
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 IGP's -- the falcon-controlled decoding engines, rather than the
> xtensa-controlled ones), by using
2015 Oct 06
2
Chipset & Family
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
2013 Nov 20
0
H.264 engine differences between fermi and tesla cards
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
2013 Nov 21
0
H.264 engine differences between fermi and tesla cards
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
2019 Jan 27
1
[PATCH] update known chipsets list
---
man/nouveau.man | 9 ++++++++-
src/nv_driver.c | 8 ++++++--
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/man/nouveau.man b/man/nouveau.man
index 07d53c8..4878f24 100644
--- a/man/nouveau.man
+++ b/man/nouveau.man
@@ -63,7 +63,14 @@ GF100, GF104, GF106, GF108, GF110, GF114, GF116, GF117, GF119
GK104, GK106, GK107, GK110, GK208
.TP 22
.B GeForce GTX 750
-GM107
+GM107,
2014 Feb 28
2
Tesla shader ISA question
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 =
2014 May 01
13
[Bug 78161] New: [NV96] Artifacts in output of fragment program containing not unrolled loops with conditional break
https://bugs.freedesktop.org/show_bug.cgi?id=78161
Priority: medium
Bug ID: 78161
Assignee: nouveau at lists.freedesktop.org
Summary: [NV96] Artifacts in output of fragment program
containing not unrolled loops with conditional break
Severity: normal
Classification: Unclassified
OS: Linux (All)
2013 Nov 30
2
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
2013 Dec 07
0
H.264 engine differences between fermi and tesla cards
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,
> >>>
>
2014 Apr 23
2
Proper gl_SampleMask output
Hello,
I've been trying to add ARB_sample_shading support to nouveau, and am
being defeated by the gl_SampleMask tests. Everything else works fine.
(And naturally the tests pass with the proprietary driver.) I'm trying
to do this for both GT21x, as well as GF100+.
In the GT21x case, it seems like the low bit of method 0x1928 needs to
be set (as well as the second-to-lowest bit), for
2015 Oct 06
2
Chipset & Family
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?
2014 Apr 30
2
Proper gl_SampleMask output
Hi Ilia. I'll take a look and see what I can find out.
Thanks,
- Andy
On Wed, Apr 23, 2014 at 05:03:17PM -0700, Ilia Mirkin wrote:
> On Wed, Apr 23, 2014 at 6:22 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
> > Hello,
> >
> > I've been trying to add ARB_sample_shading support to nouveau, and am
> > being defeated by the gl_SampleMask tests.
2019 Sep 29
1
nouveau locking machine solid
Hi .
I am having a very annoying problem not sure where the root of it lies
When running FLdigi it runs fine for about 10 mineuts then i start
getting errors leading to a complete lock up that needs a power button
to free it up i get the following
[ 653.080497] nouveau 0000:01:00.0: fifo: DMA_PUSHER - ch 3
[systemd-logind[462]] get 00000d3a24 [ 653.081461] nouveau
0000:01:00.0: gr:
2020 Jul 05
1
Framebuffer double buffering (via FBIOPAN_DISPLAY)
Oops, the FBIOPAN_DISPLAY ioctl error was a stupid mistake on mistake on
my part.? Thanks for the info on where the validation code was.?
Comparing against that made it easy to find the mistake.? It's working
now, well...where I have been able to get over-allocation working!?
Thanks for the help.? If I can't get the over-allocation to work on my
other systems, I'll take it up in
2019 Dec 11
0
[PATCH v3] drm: Generalized NV Block Linear DRM format mod
Builds upon the existing NVIDIA 16Bx2 block linear
format modifiers by adding more "fields" to the
existing parameterized
DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifier
macro that allow fully defining a unique-across-
all-NVIDIA-hardware bit layout using a minimal
set of fields and values. The new modifier macro
DRM_FORMAT_MOD_NVIDIA_BLOCK_LINEAR_2D is
effectively backwards
2009 Nov 12
1
[Bug 25057] New: Incomplete list of supported products
http://bugs.freedesktop.org/show_bug.cgi?id=25057
Summary: Incomplete list of supported products
Product: xorg
Version: 7.4
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
ReportedBy:
2019 Jun 19
0
nouveau: DRM: GPU lockup - switching to software fbcon
On (06/19/19 02:07), Ilia Mirkin wrote:
> On Wed, Jun 19, 2019 at 1:48 AM Sergey Senozhatsky
> <sergey.senozhatsky.work at gmail.com> wrote:
> >
> > On (06/19/19 01:20), Ilia Mirkin wrote:
> > > On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky
> > > <sergey.senozhatsky.work at gmail.com> wrote:
> > > >
> > > > On (06/14/19
2014 Apr 09
0
Tesla shader ISA question
Hi Ilia, sorry for the slow response.
This isn't my area of expertise, but as I understand it:
* You've correctly decoded both instructions:
* The first is a float32-to-float32 conversion, applying ceil()
* The second is a float32-to-signed-int32 conversion, rounding to
the nearest even integer
* For the {float,int}-to-{float,int} operations, bit 48 indicates
whether the
2024 Jan 30
0
GT216M [GeForce GT 240M] (NV50/Tesla) sddm fails to start since commit 0a2f6372a43ff5e948b8b10be34d4473f6c2ef6c
Dear nouveau mailing list,
on my notebook with the GeForce GT 240M graphics card, I am failing to start
sddm since linux kernel 6.5.0.
The screen typically goes black or white, mouse pointer is typically visible
and can be moved.
This happens about 90% of times I try to start the system; in about 10%,
everything works fine.
If the start fails, dmesg shows output such as:
[?? 20.260153] nouveau
2020 Jul 05
2
Framebuffer double buffering (via FBIOPAN_DISPLAY)
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