search for: gf8

...bogus restriction on placement is, but it breaks decoding 1080p >> VDPAU at boot speed. With this patch applied I only need to bump the vdec clock to >> get real-time 1080p decoding. It prevents a lot of VRAM <-> VRAM buffer moves. > It's not bogus, and is required for pre-GF8 boards with VRAM > BAR size. > > What configuration does the buffer that's getting moved here have > exactly? The placement restriction isn't necessary on GF8, the rest > of the restrictions may currently be required still however. > >= vdpau on NVC0 with tiling. I upl...

...acement is, but it breaks decoding 1080p >>>> VDPAU at boot speed. With this patch applied I only need to bump the vdec clock to >>>> get real-time 1080p decoding. It prevents a lot of VRAM <-> VRAM buffer moves. >>> It's not bogus, and is required for pre-GF8 boards with VRAM > BAR size. >>> >>> What configuration does the buffer that's getting moved here have >>> exactly? The placement restriction isn't necessary on GF8, the rest >>> of the restrictions may currently be required still however. >>&gt...

...iction on placement is, but it breaks decoding 1080p >>> VDPAU at boot speed. With this patch applied I only need to bump the vdec clock to >>> get real-time 1080p decoding. It prevents a lot of VRAM <-> VRAM buffer moves. >> It's not bogus, and is required for pre-GF8 boards with VRAM > BAR size. >> >> What configuration does the buffer that's getting moved here have >> exactly? The placement restriction isn't necessary on GF8, the rest >> of the restrictions may currently be required still however. >> >>= vdpau on...

I have no idea what this bogus restriction on placement is, but it breaks decoding 1080p VDPAU at boot speed. With this patch applied I only need to bump the vdec clock to get real-time 1080p decoding. It prevents a lot of VRAM <-> VRAM buffer moves. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c

Hi all! I read that the older Nvidia hardware (maybe < GF8) is in a different driver and no longer maintained. Is that the case? I have a GeForce 4000 MX that I'm trying to get to work on debian/sparc64, which I admit is a bit of longshot, but I was wondering how much effort it would take to even get the driver to build, and then to function. I'm v...

...dea what this bogus restriction on placement is, but it breaks decoding 1080p > VDPAU at boot speed. With this patch applied I only need to bump the vdec clock to > get real-time 1080p decoding. It prevents a lot of VRAM <-> VRAM buffer moves. It's not bogus, and is required for pre-GF8 boards with VRAM > BAR size. What configuration does the buffer that's getting moved here have exactly? The placement restriction isn't necessary on GF8, the rest of the restrictions may currently be required still however. Ben. > > Signed-off-by: Maarten Lankhorst <maarten...

...I thought some discussion would be a good idea rather than just ripping it out :) The non-KMS paths are messy, and lets face it, rotting badly. IMO the KMS code is stable enough now that we can continue without the UMS crutch, and indeed, the KMS code supports a lot more chipsets (particularly on GF8 and up) than the UMS code ever will. I've left the Xv overlay code intact, but ifdef'd out. I want to bring support back with KMS enabled (thinking of older chipsets where the blitter sucks), so it made sense to leave the old code there for now. So, who has some Signed-off-by's :) B...

Hi! Today i received Battlefield 2 and i installed it without any problem, but when laucnhing it it crashes, i use a no-cd crack but i have the same problem. Here's my output: http://pastebin.be/15146 Can someone help me? I really want to play this game! Thanks, kind regards... -------------- next part -------------- An HTML attachment was scrubbed... URL: