From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] lib/igt_draw: Only skip when width/x is not a multiple of 2.
Date: Fri, 16 Nov 2018 11:16:13 +0100 [thread overview]
Message-ID: <e29a29c7-5c02-79cf-a1b8-15f171d08864@linux.intel.com> (raw)
In-Reply-To: <20181030133447.GV9144@intel.com>
Op 30-10-18 om 14:34 schreef Ville Syrjälä:
> On Tue, Oct 30, 2018 at 12:26:46PM +0100, Maarten Lankhorst wrote:
>> Y and height have no such restrictions, since pixel size has no
>> relation to height.
>>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> ---
>> lib/igt_draw.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/lib/igt_draw.c b/lib/igt_draw.c
>> index 05821480bc80..84dd212c1daf 100644
>> --- a/lib/igt_draw.c
>> +++ b/lib/igt_draw.c
>> @@ -581,9 +581,7 @@ static void draw_rect_render(int fd, struct cmd_data *cmd_data,
>> * smaller bpps you won't succeeed if you need to copy "half" of a 32bpp
>> * pixel or something similar. */
>> igt_skip_on(rect->x % (32 / buf->bpp) != 0 ||
>> - rect->y % (32 / buf->bpp) != 0 ||
>> - rect->w % (32 / buf->bpp) != 0 ||
>> - rect->h % (32 / buf->bpp) != 0);
>> + rect->w % (32 / buf->bpp) != 0);
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Adding 16bpp support to rendercopy shouldn't be too hard...
Thanks, pushed. Will take a look at how to add it to rendercopy.
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2018-11-16 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 11:26 [igt-dev] [PATCH i-g-t] lib/igt_draw: Only skip when width/x is not a multiple of 2 Maarten Lankhorst
2018-10-30 13:27 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2018-10-30 13:34 ` [igt-dev] [PATCH i-g-t] " Ville Syrjälä
2018-11-16 10:16 ` Maarten Lankhorst [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=e29a29c7-5c02-79cf-a1b8-15f171d08864@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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