dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: airlied@gmail.com
Cc: Thomas Hellstrom <thellstrom@vmware.com>,
	dri-devel@lists.freedesktop.org
Subject: [PATCH 01/13] drm/vmwgfx: Assume larger framebuffer max size.
Date: Tue, 27 Apr 2010 19:45:33 +0200	[thread overview]
Message-ID: <1272390345-3655-2-git-send-email-thellstrom@vmware.com> (raw)
In-Reply-To: <1272390345-3655-1-git-send-email-thellstrom@vmware.com>

From: Jakob Bornecrantz <jakob@vmware.com>

Signed-off-by: Jakob Bornecrantz <jakob@vmware.com>
Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
---
 drivers/gpu/drm/vmwgfx/vmwgfx_kms.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
index 31f9afe..146792e 100644
--- a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
+++ b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c
@@ -771,8 +771,9 @@ int vmw_kms_init(struct vmw_private *dev_priv)
 	dev->mode_config.funcs = &vmw_kms_funcs;
 	dev->mode_config.min_width = 1;
 	dev->mode_config.min_height = 1;
-	dev->mode_config.max_width = dev_priv->fb_max_width;
-	dev->mode_config.max_height = dev_priv->fb_max_height;
+	/* assumed largest fb size */
+	dev->mode_config.max_width = 8192;
+	dev->mode_config.max_height = 8192;
 
 	ret = vmw_kms_init_legacy_display_system(dev_priv);
 
-- 
1.6.2.5

  reply	other threads:[~2010-04-27 17:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 17:45 [PATCH 0/13] vmwgfx update Thomas Hellstrom
2010-04-27 17:45 ` Thomas Hellstrom [this message]
2010-04-27 17:45   ` [PATCH 02/13] drm/vmwgfx: Fix single framebuffer detection Thomas Hellstrom
2010-04-27 17:45     ` [PATCH 03/13] drm/vmwgfx: Make sure to unpin old and pin new framebuffer Thomas Hellstrom
2010-04-27 17:45       ` [PATCH 04/13] drm/vmwgfx: Add kernel throttling support. Bump minor Thomas Hellstrom
2010-04-27 17:45         ` [PATCH 05/13] drm/vmwgfx: Get connector status from detection function Thomas Hellstrom
2010-04-27 17:45           ` [PATCH 06/13] drm/vmwgfx: Support older hardware Thomas Hellstrom
2010-04-27 17:45             ` [PATCH 07/13] drm/vmwgfx: Reserve first part of VRAM for framebuffer Thomas Hellstrom
2010-04-27 17:45               ` [PATCH 08/13] drm/vmwgfx: Remove duplicate member from struct vmw_legacy_display_unit Thomas Hellstrom
2010-04-27 17:45                 ` [PATCH 09/13] drm/vmwgfx: Don't use SVGA_REG_ENABLE in modesetting code Thomas Hellstrom
2010-04-27 17:45                   ` [PATCH 10/13] drm/vmwgfx: Some modesetting cleanups and fixes Thomas Hellstrom
2010-04-27 17:45                     ` [PATCH 11/13] drm/vmwgfx: Unpause overlay on update Thomas Hellstrom
2010-04-27 17:45                       ` [PATCH 12/13] drm/vmwgfx: Print warnings in kernel log about bo pinning that fails Thomas Hellstrom
2010-04-27 17:45                         ` [PATCH 13/13] drm/vmwgfx: Remove some leftover debug messages Thomas Hellstrom
2010-04-28  8:49     ` [PATCH 02/13] drm/vmwgfx: Fix single framebuffer detection Paulius Zaleckas
  -- strict thread matches above, loose matches on Subject: below --
2010-05-28  9:21 [PATCH 0/13] vmwgfx update V2 Thomas Hellstrom
2010-05-28  9:21 ` [PATCH 01/13] drm/vmwgfx: Assume larger framebuffer max size Thomas Hellstrom

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=1272390345-3655-2-git-send-email-thellstrom@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=airlied@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