dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mathieu Larouche <mathieu.larouche@matrox.com>
Cc: Egbert Eich <eich@suse.de>, Dave Airlie <airlied@redhat.com>,
	dri-devel@lists.freedesktop.org,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 00/14] mgag200 fixes
Date: Tue, 01 Aug 2017 23:18:31 +0200	[thread overview]
Message-ID: <s5hini756mw.wl-tiwai@suse.de> (raw)
In-Reply-To: <5980D597.3080703@matrox.com>

On Tue, 01 Aug 2017 21:25:11 +0200,
Mathieu Larouche wrote:
> 
> On 18/07/2017 10:43 AM, Takashi Iwai wrote:
> > Hi,
> >
> > this is a summer cleanup sale, a patchset containing various fixes for
> > mgag200 driver taken from openSUSE / SUSE kernels.  They have been in
> > our kernels for ages, so at least they are supposed to be stable.
> >
> > Most of patches came from Egbert, and one PM patch from me that is a
> > resubmission of the once-post-and-lost patch.
> >
> >
> > thanks,
> >
> > Takashi
> >
> > ===
> >
> > Egbert Eich (13):
> >    drm/mgag200: Add doublescan and interlace support
> >    drm/mgag200: Add additional limits for certain G200 variants
> >    drm/mgag200: Fix memleak in error path in mgag200_bo_create()
> >    drm/mgag200: Free container instead of member in
> >      mga_user_framebuffer_destroy()
> >    drm/mgag200: Initialize data needed to map fbdev memory
> >    drm/mgag200: Simplify function mgag200_ttm_placement()
> >    drm/mgag200: Add support for MATROX PCI device IDs 0x520 and 0x521
> >    drm/mgag200: Cleanup cursor BOs properly
> >    drm/mgag200: Add missing drm_connector_unregister()
> >    drm/mgag200: Don't use crtc_* parameters for validation
> >    drm/mgag200: Consolidate depth/bpp handling
> >    drm/mgag200: Add command line option to specify preferred depth
> >    drm/mgag200: Add mode validation debugging code
> >
> > Takashi Iwai (1):
> >    drm/mgag200: Implement basic PM support
> >
> >   drivers/gpu/drm/mgag200/mgag200_drv.c  |  54 +++++++++++
> >   drivers/gpu/drm/mgag200/mgag200_drv.h  |  22 +++--
> >   drivers/gpu/drm/mgag200/mgag200_fb.c   |  14 +--
> >   drivers/gpu/drm/mgag200/mgag200_main.c | 146 +++++++++++++++++++++++++++--
> >   drivers/gpu/drm/mgag200/mgag200_mode.c | 166 ++++++++++++++++++++++++++-------
> >   drivers/gpu/drm/mgag200/mgag200_ttm.c  |  11 ++-
> >   6 files changed, 357 insertions(+), 56 deletions(-)
> >
> 
> Patches were tested against G200eW3, G200e4 & G200eH3 and it's working
> fine and we haven't seen any issues.

Thanks for testing!

> There's one thing though, the patch "[PATCH 01/14] drm/mgag200: Add
> doublescan and interlace support" may cause problems as doublescan and
> interlace aren't tested and aren't officially supported on the G200
> server line products. So, I'm wondering if it shouldn't be kept
> disabled for them.

OK, that's good to know.  My understanding is that the patch was
brought only for adapting the UMS X driver quality, but not for
actually fixing the real bugs.  Let's drop that patch, then.


Takashi
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2017-08-01 21:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 14:43 [PATCH 00/14] mgag200 fixes Takashi Iwai
2017-07-18 14:43 ` [PATCH 01/14] drm/mgag200: Add doublescan and interlace support Takashi Iwai
2017-07-18 14:43 ` [PATCH 02/14] drm/mgag200: Add additional limits for certain G200 variants Takashi Iwai
2017-07-18 14:43 ` [PATCH 03/14] drm/mgag200: Fix memleak in error path in mgag200_bo_create() Takashi Iwai
2017-07-18 14:43 ` [PATCH 04/14] drm/mgag200: Free container instead of member in mga_user_framebuffer_destroy() Takashi Iwai
2017-07-18 14:43 ` [PATCH 05/14] drm/mgag200: Initialize data needed to map fbdev memory Takashi Iwai
2017-07-18 14:43 ` [PATCH 06/14] drm/mgag200: Simplify function mgag200_ttm_placement() Takashi Iwai
2017-07-18 14:43 ` [PATCH 07/14] drm/mgag200: Add support for MATROX PCI device IDs 0x520 and 0x521 Takashi Iwai
2017-07-20  4:17   ` Dave Airlie
2017-07-20  9:47     ` Takashi Iwai
2017-07-20 15:05       ` Egbert Eich
2017-07-18 14:43 ` [PATCH 08/14] drm/mgag200: Cleanup cursor BOs properly Takashi Iwai
2017-07-18 14:43 ` [PATCH 09/14] drm/mgag200: Add missing drm_connector_unregister() Takashi Iwai
2017-07-19  8:44   ` Takashi Iwai
2017-07-20  8:15     ` Daniel Vetter
2017-07-18 14:43 ` [PATCH 10/14] drm/mgag200: Don't use crtc_* parameters for validation Takashi Iwai
2017-07-19  6:38   ` Daniel Vetter
2017-07-18 14:43 ` [PATCH 11/14] drm/mgag200: Consolidate depth/bpp handling Takashi Iwai
2017-07-20 11:58   ` Paul Menzel
2017-07-20 12:08     ` Takashi Iwai
2017-07-18 14:43 ` [PATCH 12/14] drm/mgag200: Add command line option to specify preferred depth Takashi Iwai
2017-07-18 14:43 ` [PATCH 13/14] drm/mgag200: Add mode validation debugging code Takashi Iwai
2017-07-18 14:43 ` [PATCH 14/14] drm/mgag200: Implement basic PM support Takashi Iwai
2017-08-01 19:25 ` [PATCH 00/14] mgag200 fixes Mathieu Larouche
2017-08-01 21:18   ` Takashi Iwai [this message]

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=s5hini756mw.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eich@suse.de \
    --cc=mathieu.larouche@matrox.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 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).