All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulius Zaleckas <paulius.zaleckas@gmail.com>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 02/13] drm/vmwgfx: Fix single framebuffer detection.
Date: Wed, 28 Apr 2010 11:49:46 +0300	[thread overview]
Message-ID: <4BD7F6AA.5090506@gmail.com> (raw)
In-Reply-To: <1272390345-3655-3-git-send-email-thellstrom@vmware.com>

On 04/27/2010 08:45 PM, Thomas Hellstrom wrote:
> 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_ldu.c |    3 +++
>   1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
> index 9089159..be88fc6 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
> @@ -130,6 +130,7 @@ static int vmw_ldu_del_active(struct vmw_private *vmw_priv,
>   	if (list_empty(&ldu->active))
>   		return 0;
>
> +	/* must init otherwise list_empty(&ldu->active) well not work */

Spelling well->will

>   	list_del_init(&ldu->active);
>   	if (--(ld->num_active) == 0) {
>   		BUG_ON(!ld->fb);
> @@ -208,6 +209,8 @@ static int vmw_ldu_crtc_set_config(struct drm_mode_set *set)
>
>   	/* ldu only supports one fb active at the time */
>   	if (dev_priv->ldu_priv->fb&&  vfb&&
> +	    !(dev_priv->ldu_priv->num_active == 1&&
> +	      !list_empty(&ldu->active))&&
>   	dev_priv->ldu_priv->fb != vfb) {
>   		DRM_ERROR("Multiple framebuffers not supported\n");
>   		return -EINVAL;

  parent reply	other threads:[~2010-04-28  8:56 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 ` [PATCH 01/13] drm/vmwgfx: Assume larger framebuffer max size Thomas Hellstrom
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     ` Paulius Zaleckas [this message]
  -- 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
2010-05-28  9:21   ` [PATCH 02/13] drm/vmwgfx: Fix single framebuffer detection 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=4BD7F6AA.5090506@gmail.com \
    --to=paulius.zaleckas@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=thellstrom@vmware.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.