search for: vidmem

...> no checks in hardware for the aperture, so we get away with setting VRAM > as the aperture for buffers that are actually in system memory. Can GK20A take comptags with aperture set to system memory? For some reason I can recall, I was under the impression PTEs needed to be pointed at "vidmem" (despite them actually accessing system memory anyway) on Tegra parts for compression to work? I could be mistaken though. Ben. > > Signed-off-by: Thierry Reding <treding at nvidia.com> > --- > drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.h | 1 - > drivers/gpu/d...

...ined3d/directx.c b/dlls/wined3d/directx.c index 9536b71..1386a76 100644 --- a/dlls/wined3d/directx.c +++ b/dlls/wined3d/directx.c @@ -1022,6 +1022,11 @@ BOOL IWineD3DImpl_FillGLCaps(WineD3D_GL_Info *gl_info) { gl_info->gl_card = CARD_NVIDIA_GEFORCE_7400; vidmem = 256; /* The 7400 uses 256-512MB */ } + /* Geforce7 lowend */ + else if(strstr(gl_info->gl_renderer, "7300")) { + gl_info->gl_card = CARD_NVIDIA_GEFORCE_7300; + vidmem = 256; /* Mac Pros with this...

...rdware for the aperture, so we get away with setting VRAM > > as the aperture for buffers that are actually in system memory. > Can GK20A take comptags with aperture set to system memory? For some > reason I can recall, I was under the impression PTEs needed to be > pointed at "vidmem" (despite them actually accessing system memory > anyway) on Tegra parts for compression to work? I could be mistaken > though. I don't think GK20A supports comptags at all. I think this wasn't introduced until GM20B. nvgpu has some "gk20a" code to flush comptags, but...

I'm running an Nvidia geforce 8400 GS 512 Mb card, but when i go into the oblivion options, under the Graphics adapter tab it shows me Geforce 8300 Gs whcih is a motherboard which I assume has some sort of GPU onboard. This would explain the subpar framerates im getting.

On 25/11/14 22:05, Andy Ritger wrote: > On Tue, Nov 25, 2014 at 10:57:44AM -0500, Ilia Mirkin wrote: >> On Mon, Nov 24, 2014 at 8:33 PM, Andy Ritger <aritger at nvidia.com> wrote: >>> On Fri, Nov 21, 2014 at 01:39:55AM -0500, Ilia Mirkin wrote: >>>> On Fri, Nov 21, 2014 at 1:16 AM, Andy Ritger <aritger at nvidia.com> wrote: >>>>> Hi Ilia,

All- With suggestions from Ian and previous posts on this list, I''ve been investigating why Xen causes a Transmeta-based system to reboot immediately.. I''ve added instrumentation to xen/arch/x86/boot/x86_32.S (a collection of ''.asciz "foo"'' statements) hoping to locate a point of failure.. and it dies sometime before this code is run.. At what point

...e don't have to simulate non-existent VRAM memory. In that respect it seems to be the right thing to do, and all things taken is not very intrusive. Tested on GK20A with Wayland and several EGL clients running, and working fine. Changes since v1: - When using GART as the VRAM domain, move all vidmem bindings to sysmem and set vidmem_bindings to 0. Alexandre Courbot (3): nouveau: support for custom VRAM domains nvc0: use NV_VRAM_DOMAIN() macro gk20a: use NOUVEAU_BO_GART as VRAM domain src/gallium/drivers/nouveau/nouveau_buffer.c | 6 ++--- src/gallium/drivers/nouveau/nouveau_s...

From: Thierry Reding <treding at nvidia.com> Hi Ben, these are a couple of patches that are in preparation for adding GV11B support. The fundamental issue that these are trying to solve is that the GV11B is the first Tegra incarnation of the GPU where the aperture really matters. All prior generations would accept any of them. For dGPUs we usually allocate memory in VRAM, so the default

Hi Andi, This is a set of updates for the firstfloor patch queue. Quick rundown: revert-mm-x86_64-mm-account-for-module-percpu-space-separately-from-kernel-percpu.patch separate-module-percpu-space.patch Update the module percpu accounting patch fix-ff-allow-percpu-variables-to-be-page-aligned.patch Make sure the percpu memory allocation is page-aligned

Hi Andi, This is a set of updates for the firstfloor patch queue. Quick rundown: revert-mm-x86_64-mm-account-for-module-percpu-space-separately-from-kernel-percpu.patch separate-module-percpu-space.patch Update the module percpu accounting patch fix-ff-allow-percpu-variables-to-be-page-aligned.patch Make sure the percpu memory allocation is page-aligned

https://bugs.freedesktop.org/show_bug.cgi?id=105319 Bug ID: 105319 Summary: DRM: EVO timeout with kernel 4.15.x Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau