From: Tormod Volden <lists.tormod@gmail.com>
To: dri-devel@lists.freedesktop.org
Subject: Re: multiple framebuffer drm maps
Date: Tue, 3 May 2011 23:54:49 +0200 [thread overview]
Message-ID: <1304459689-7687-1-git-send-email-lists.tormod@gmail.com> (raw)
In-Reply-To: <1304457607-3783-1-git-send-email-lists.tormod@gmail.com>
From: Tormod Volden <debian.tormod@gmail.com>
Subject: [PATCH] drm/savage: Do not add framebuffer and aperture maps
Since multiple framebuffer maps are not supported any longer (commit
41c2e75e60200a860a74b7c84a6375c105e7437f) these maps would be broken,
and they are not used by the drm anyway.
Leave it to userspace to create one working map instead.
Signed-off-by: Tormod Volden <debian.tormod@gmail.com>
---
And if we are absolutely sure that we do not want to support multiple
framebuffers maps, I would instead suggest this change to the savage
driver, which at least allows userspace to work around it.
Tormod
drivers/gpu/drm/savage/savage_bci.c | 13 +------------
drivers/gpu/drm/savage/savage_drv.h | 2 --
2 files changed, 1 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/savage/savage_bci.c b/drivers/gpu/drm/savage/savage_bci.c
index bf5f83e..91fe7b4 100644
--- a/drivers/gpu/drm/savage/savage_bci.c
+++ b/drivers/gpu/drm/savage/savage_bci.c
@@ -639,18 +639,7 @@ int savage_driver_firstopen(struct drm_device *dev)
if (ret)
return ret;
- ret = drm_addmap(dev, fb_base, fb_size, _DRM_FRAME_BUFFER,
- _DRM_WRITE_COMBINING, &dev_priv->fb);
- if (ret)
- return ret;
-
- ret = drm_addmap(dev, aperture_base, SAVAGE_APERTURE_SIZE,
- _DRM_FRAME_BUFFER, _DRM_WRITE_COMBINING,
- &dev_priv->aperture);
- if (ret)
- return ret;
-
- return ret;
+ return 0;
}
/*
diff --git a/drivers/gpu/drm/savage/savage_drv.h b/drivers/gpu/drm/savage/savage_drv.h
index df2aac6..2b49b3e 100644
--- a/drivers/gpu/drm/savage/savage_drv.h
+++ b/drivers/gpu/drm/savage/savage_drv.h
@@ -153,8 +153,6 @@ typedef struct drm_savage_private {
/* memory regions in physical memory */
drm_local_map_t *sarea;
drm_local_map_t *mmio;
- drm_local_map_t *fb;
- drm_local_map_t *aperture;
drm_local_map_t *status;
drm_local_map_t *agp_textures;
drm_local_map_t *cmd_dma;
--
1.7.0.4
next prev parent reply other threads:[~2011-05-03 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 21:54 multiple framebuffer drm maps Tormod Volden
2011-05-03 21:20 ` Tormod Volden
2011-05-03 21:54 ` Tormod Volden [this message]
2011-05-22 19:27 ` [PATCH] drm/savage: Do not add framebuffer and aperture maps Tormod Volden
2011-05-27 18:19 ` [PATCH resend] " Tormod Volden
2011-05-27 20:48 ` Dave Airlie
2011-05-27 23:44 ` Tormod Volden
2011-05-29 23:12 ` [PATCH] drm: Compare only lower 32 bits of framebuffer map offsets Tormod Volden
2011-05-29 23:29 ` Dave Airlie
2011-05-30 19:45 ` [PATCH v2] " Tormod Volden
2011-05-31 22:04 ` Tormod Volden
2011-06-10 22:59 ` Tormod Volden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1304459689-7687-1-git-send-email-lists.tormod@gmail.com \
--to=lists.tormod@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).