search for: rendernodes

Could WineHQ be used to run Windows software as rendernodes? Hi, I'm doing 3D computer graphics and I was asking myself if it's possible to do network windows rendering with software like Luxology Modo, Autodesk 3ds Max, Newtek Lightwave, etc... To do this rendering Windows software has to be able to connect via LAN.

...t will contain about 8 nodes but it should be build at growth. now the setup i had in mind is as following: All the data is already stored on a StorNext SAN filesystem (quantum ) this should be mounted on a centos server trough fiber optics , which in its turn shares the FS over NFS to all the rendernodes (also centos). Now we've estimated that the average file send to each node will be about 90MB , so that's what i like the average connection to be, i know that gigabit ethernet should be able to that (testing with iperf confirms that) but testing the speed to already existing nfs shares...

...s being handed an intel > device. This does not work well. Fixing this will require tracing > through the va winsys code which to figure out how it invokes the > loader. > > > https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 > > For the DRM/rendernodes "platform", it will just take whatever fd it > is given. vainfo appears to give it a fixed device: > > > https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 > > However it looks like you can pass in --device /dev/dri/renderD129 or > whatever t...

On Tue, Nov 06, 2018 at 06:41:22PM +0200, Ville Syrjälä wrote: > On Tue, Nov 06, 2018 at 05:24:15PM +0100, Thierry Reding wrote: > > From: Thierry Reding <treding at nvidia.com> > > > > Irrespective of whether or not the device has any usable outputs, the > > modesetting helpers will try to register all the resources such as CRTCs > > and planes.

> > It does indicate a config problem, but why do you want to use the > nvidia GPU for video accel? I'd rely on intel to provide acceleration > as this also reduces power consumption of the entire system. Also I > think vaapi on the secondary GPU is pretty much untested. Well you've got a point there. It's just that the dang nvidia is pretty much sitting there on its

Make it a Bool consistently, as declared in header. Reported-by: Ilia Mirkin <imirkin at alum.mit.edu> Signed-off-by: Mario Kleiner <mario.kleiner.de at gmail.com> --- src/nouveau_present.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/nouveau_present.c b/src/nouveau_present.c index 4de1e6e..699a58d 100644 --- a/src/nouveau_present.c +++

https://bugs.freedesktop.org/show_bug.cgi?id=82152 Priority: medium Bug ID: 82152 Assignee: nouveau at lists.freedesktop.org Summary: any OpenGL application crashes X, locks up machine with nouveau and PRIME Severity: normal Classification: Unclassified OS: Linux (All) Reporter: celticmadman at

...could be > instantiating the IP in an SoC and include a display engine, in which > case we'd need the DRIVER_MODESET feature again, but I'm not aware of > anyone doing that, so it may not be worth planning for that at this > point. I thought DRIVER_MODESET was required even for rendernodes. Is that no longer the case? Note that e.g. GF117 GPUs also don't have a display engine hooked up in nouveau (or in hardware). -ilia

...u want it to, and the nouveau driver is being handed an intel device. This does not work well. Fixing this will require tracing through the va winsys code which to figure out how it invokes the loader. https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 For the DRM/rendernodes "platform", it will just take whatever fd it is given. vainfo appears to give it a fixed device: https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 However it looks like you can pass in --device /dev/dri/renderD129 or whatever the right one is, which should pas...

...device. This does not work well. Fixing this will require tracing >> through the va winsys code which to figure out how it invokes the >> loader. >> >> >> https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/frontends/va/context.c#n111 >> >> For the DRM/rendernodes "platform", it will just take whatever fd it >> is given. vainfo appears to give it a fixed device: >> >> >> https://github.com/intel/libva-utils/blob/master/common/va_display_drm.c#L39 >> >> However it looks like you can pass in --device /dev/dri/rende...

On 04.11.2015 11:57, Martin Peres wrote: > On 02/11/15 08:28, poma wrote: >> An interesting results. >> >> DRI2: >> >> $ vblank_mode=0 glxgears >> ATTENTION: default value of option vblank_mode overridden by environment. >> 6321 frames in 5.0 seconds = 1264.103 FPS >> 6380 frames in 5.0 seconds = 1275.943 FPS >> 6369 frames in 5.0 seconds =