From: "Keith Packard" <keithp@keithp.com>
To: Eric Engestrom <eric.engestrom@imgtec.com>
Cc: mesa-dev@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/7] vulkan: Add KHR_display extension to anv and radv using DRM
Date: Mon, 12 Feb 2018 14:16:11 -0800 [thread overview]
Message-ID: <871shpc0r8.fsf@keithp.com> (raw)
In-Reply-To: <20180212152704.cchww2vlowyjnd4i@imgtec.com>
[-- Attachment #1.1: Type: text/plain, Size: 1940 bytes --]
Eric Engestrom <eric.engestrom@imgtec.com> writes:
> copy/paste error: s/drm/display/
That's actually intentional -- any system which supports 'drm' can
support the display backend as it's based on that. Maybe it should use a
different test? (note that I haven't been using the autotools backend
recently, so it may not be great at this point. At least my current tree
builds?)
>> +if with_platform_display
>> + radv_flags += [
>> + '-DVK_USE_PLATFORM_DISPLAY_KHR',
>> + ]
>
> Nit: this can be a simple
> radv_flags += '-DVK_USE_PLATFORM_DISPLAY_KHR'
>
>> +if with_platform_display
>> + vulkan_wsi_args += [
>> + '-DVK_USE_PLATFORM_DISPLAY_KHR',
>> + ]
>
> Ditto:
> vulkan_wsi_args += '-DVK_USE_PLATFORM_DISPLAY_KHR'
Oh, good point -- I'd split out the RANDR and DISPLAY bits but didn't
simplify the meson stuff.
> Nit: src/amd/vulkan/ uses tabs for indent, you used spaces.
Thanks; I'll reconfigure my environment so that it uses tabs in that
directory, and re-indent the changes.
>> +#define MM_PER_PIXEL (1.0/96.0 * 25.4)
>
> unused
Good catch; those got left in both anv and radv directories after some
refactoring.
>> +#if 0
>
> `#if DEBUG` maybe?
Could do; I could also just strip out the printf debugging, but when
you're doing timing-sensitive stuff at that level, printf debugging is
pretty useful.
>> +#define wsi_display_debug(...) fprintf(stderr, __VA_ARGS__)
>> +#define wsi_display_debug_code(...) __VA_ARGS__
>
> that 2nd one is unused
It gets used in a later patch.
>> + if (wsi) {
>
> if (!wsi) return;
> and carry on without the extra indent
Yeah, would probably look cleaner.
> I don't know enough for this to be an actual review though, but the rest
> of this file looks reasonable to me :)
Thanks for reviewing the basic formatting and structure though; I
totally missed the tabs/spaces issue.
--
-keith
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-02-12 22:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 4:45 [PATCH 0/7] vulkan: Add direct display extensions Keith Packard
2018-02-10 4:45 ` [PATCH 1/7] vulkan: Add KHR_display extension to anv and radv using DRM Keith Packard
2018-02-12 15:27 ` Eric Engestrom
2018-02-12 22:16 ` Keith Packard [this message]
2018-02-12 16:18 ` [Mesa-dev] " Emil Velikov
2018-02-12 23:12 ` Keith Packard
2018-02-14 1:10 ` Jason Ekstrand
2018-02-15 17:46 ` Keith Packard
2018-02-23 23:00 ` Jason Ekstrand
2018-02-23 23:43 ` Keith Packard
2018-02-24 0:51 ` Jason Ekstrand
2018-03-12 23:02 ` Keith Packard
2018-03-29 6:59 ` Mao, David
2018-03-29 15:05 ` Keith Packard
2018-02-10 4:45 ` [PATCH 2/7] vulkan: Add EXT_direct_mode_display Keith Packard
2018-02-10 4:45 ` [PATCH 3/7] vulkan: Add EXT_acquire_xlib_display Keith Packard
2018-02-13 0:16 ` Dylan Baker
2018-02-10 4:45 ` [PATCH 4/7] vulkan: Add VK_EXT_display_surface_counter [v4] Keith Packard
2018-02-10 4:45 ` [PATCH 5/7] vulkan: add VK_EXT_display_control [v4] Keith Packard
2018-02-10 4:45 ` [PATCH 6/7] vulkan: Add new VK_MESA_query_timestamp extension Keith Packard
2018-02-13 0:20 ` Dylan Baker
2018-02-13 10:49 ` [Mesa-dev] " Lionel Landwerlin
2018-02-13 21:11 ` Keith Packard
2018-02-10 4:45 ` [PATCH 7/7] vulkan: Add VK_GOOGLE_display_timing extension (x11 and display backends) Keith Packard
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=871shpc0r8.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@imgtec.com \
--cc=mesa-dev@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