search for: videomem

We do not have a generic blitter on nv3x cards, so we must use the sifm object for color resolving. This commit divides the sources and dest surfaces in to tiles which match the constraints of the sifm object, so that color resolving will work properly on nv3x cards. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- Changes in v2: -Use 1024x1024 blocks -Use the sifm on both nv3x

...CALLOC_STRUCT(nv30_screen); > + if (!screen) > + return NULL; > + > + pscreen = &screen->base.base; > + pscreen->destroy = nv30_screen_destroy; > + > /* > * Some modern apps try to use msaa without keeping in mind the > * restrictions on videomem of older cards. Resulting in dmesg saying: > @@ -479,8 +482,6 @@ nv30_screen_create(struct nouveau_device *dev) > if (screen->max_sample_count > 4) > screen->max_sample_count = 4; > > - pscreen = &screen->base.base; > - pscreen->destroy = nv30_scr...

...return NULL; >>> + >>> + pscreen = &screen->base.base; >>> + pscreen->destroy = nv30_screen_destroy; >>> + >>> /* >>> * Some modern apps try to use msaa without keeping in mind the >>> * restrictions on videomem of older cards. Resulting in dmesg saying: >>> @@ -479,8 +482,6 @@ nv30_screen_create(struct nouveau_device *dev) >>> if (screen->max_sample_count > 4) >>> screen->max_sample_count = 4; >>> >>> - pscreen = &screen->base.base;...

...n); return NULL; } + screen = CALLOC_STRUCT(nv30_screen); + if (!screen) + return NULL; + + pscreen = &screen->base.base; + pscreen->destroy = nv30_screen_destroy; + /* * Some modern apps try to use msaa without keeping in mind the * restrictions on videomem of older cards. Resulting in dmesg saying: @@ -479,8 +482,6 @@ nv30_screen_create(struct nouveau_device *dev) if (screen->max_sample_count > 4) screen->max_sample_count = 4; - pscreen = &screen->base.base; - pscreen->destroy = nv30_screen_destroy; pscreen-&gt...

...+ if (!screen) >> + return NULL; >> + >> + pscreen = &screen->base.base; >> + pscreen->destroy = nv30_screen_destroy; >> + >> /* >> * Some modern apps try to use msaa without keeping in mind the >> * restrictions on videomem of older cards. Resulting in dmesg saying: >> @@ -479,8 +482,6 @@ nv30_screen_create(struct nouveau_device *dev) >> if (screen->max_sample_count > 4) >> screen->max_sample_count = 4; >> >> - pscreen = &screen->base.base; >> - pscree...

From: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 4016871..c02ee61 100644 --- a/configure.ac +++ b/configure.ac @@ -73,7 +73,7 @@ LIBDRM_RADEON_REQUIRED=2.4.56 LIBDRM_AMDGPU_REQUIRED=2.4.63 LIBDRM_INTEL_REQUIRED=2.4.61

From: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 4016871..c02ee61 100644 --- a/configure.ac +++ b/configure.ac @@ -73,7 +73,7 @@ LIBDRM_RADEON_REQUIRED=2.4.56 LIBDRM_AMDGPU_REQUIRED=2.4.63 LIBDRM_INTEL_REQUIRED=2.4.61

From: Ben Skeggs <bskeggs at redhat.com> v2. forgot bump for non-gallium driver Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- configure.ac | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index b6680d0..965c6f7 100644 --- a/configure.ac +++ b/configure.ac @@ -72,8 +72,8 @@ LIBDRM_REQUIRED=2.4.60

Hi, I have a set of 32bit HVM images running fine under Xen 3.2.1 and Xen 3.4.1. Due to performance issues with the fully virtualized setup, I would like to migrate one of those images to a paravirtualized image to compare the network performance. As I do not have a Xen-aware kernel for that VM, I thought the best would be to provide one from outside. Sounds like an easy task, doesn''t