From: Gerd Hoffmann <kraxel@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: airlied@linux.ie, puck.chen@hisilicon.com,
z.liuxinliang@hisilicon.com, hdegoede@redhat.com,
kong.kongxinwei@hisilicon.com, dri-devel@lists.freedesktop.org,
zourongrong@gmail.com, sam@ravnborg.org
Subject: Re: [PATCH 2/4] drm/bochs: Implement struct drm_mode_config_funcs.mode_valid
Date: Mon, 3 Feb 2020 07:47:57 +0100 [thread overview]
Message-ID: <20200203064757.2v4hqad2trw7jcwk@sirius.home.kraxel.org> (raw)
In-Reply-To: <20200201122744.27165-3-tzimmermann@suse.de>
On Sat, Feb 01, 2020 at 01:27:42PM +0100, Thomas Zimmermann wrote:
> The implementation of struct drm_mode_config_funcs.mode_valid verifies
> that enough video memory is available for a given display mode.
There is bochs_connector_mode_valid() doing the same check,
you can drop it when hooking up drm_vram_helper_mode_valid.
cheers,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-02-03 6:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 12:27 [PATCH 0/4] drm/vram: Check display modes against available VRAM Thomas Zimmermann
2020-02-01 12:27 ` [PATCH 1/4] drm/vram: Add helpers to validate a display mode's memory requirements Thomas Zimmermann
2020-02-03 9:49 ` Daniel Vetter
2020-02-03 9:53 ` Daniel Vetter
2020-02-03 10:25 ` Thomas Zimmermann
2020-02-01 12:27 ` [PATCH 2/4] drm/bochs: Implement struct drm_mode_config_funcs.mode_valid Thomas Zimmermann
2020-02-03 6:47 ` Gerd Hoffmann [this message]
2020-02-03 8:35 ` Thomas Zimmermann
2020-02-03 10:25 ` Gerd Hoffmann
2020-02-01 12:27 ` [PATCH 3/4] drm/hibmc: " Thomas Zimmermann
2020-02-03 9:50 ` Daniel Vetter
2020-02-01 12:27 ` [PATCH 4/4] drm/vboxvideo: " Thomas Zimmermann
2020-02-03 9:53 ` Daniel Vetter
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=20200203064757.2v4hqad2trw7jcwk@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=kong.kongxinwei@hisilicon.com \
--cc=puck.chen@hisilicon.com \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.de \
--cc=z.liuxinliang@hisilicon.com \
--cc=zourongrong@gmail.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.