From: BALATON Zoltan <balaton@eik.bme.hu>
To: Sebastian Bauer <mail@sebastianbauer.info>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 2/5] sm501: Perform a full update after palette change
Date: Fri, 22 Jun 2018 23:38:25 +0200 (CEST) [thread overview]
Message-ID: <alpine.BSF.2.21.1806222337350.86811@zero.eik.bme.hu> (raw)
In-Reply-To: <592d7d6d3bc7587bc1898c3f9647c6ea@sebastianbauer.info>
On Fri, 22 Jun 2018, Sebastian Bauer wrote:
> Am 2018-06-22 03:34, schrieb Philippe Mathieu-Daudé:
>> On 06/21/2018 05:08 AM, BALATON Zoltan wrote:
>>> From: Sebastian Bauer <mail@sebastianbauer.info>
>>>
>>> Changing the palette of a color index has as an immediate effect on
>>> all pixels with the corresponding index on real hardware. Performing a
>>> full update after a palette change is a simple way to emulate this
>>> effect.
>>>
>>> Signed-off-by: Sebastian Bauer <mail@sebastianbauer.info>
>>> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
>>> ---
>>>
>>> Notes:
>>> v4: Updated commit message
>>>
>>> hw/display/sm501.c | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>>>
>>> diff --git a/hw/display/sm501.c b/hw/display/sm501.c
>>> index 0625cf5..a2ee6e3 100644
>>> --- a/hw/display/sm501.c
>>> +++ b/hw/display/sm501.c
>>> @@ -479,6 +479,7 @@ typedef struct SM501State {
>>> MemoryRegion twoD_engine_region;
>>> uint32_t last_width;
>>> uint32_t last_height;
>>> + uint32_t do_full_update; /* perform a full update next time */
>>
>> Can this be a bool?
>
> Yes, this can be a bool. Let me know if you think that this is required.
I can take care of this in next submission, no need to resend the patch, I
can change it to bool.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2018-06-22 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 8:08 [Qemu-devel] [PATCH 0/5] Misc sm501 improvements BALATON Zoltan
2018-06-21 8:08 ` [Qemu-devel] [PATCH 1/5] sm501: Implement i2c part for reading monitor EDID BALATON Zoltan
2018-06-22 4:00 ` Philippe Mathieu-Daudé
2018-06-23 23:05 ` BALATON Zoltan
2018-06-21 8:08 ` [Qemu-devel] [PATCH 3/5] sm501: Use values from the pitch register for 2d operations BALATON Zoltan
2018-06-21 8:08 ` [Qemu-devel] [PATCH 4/5] sm501: Set updated region dirty after 2D operation BALATON Zoltan
2018-06-21 8:08 ` [Qemu-devel] [PATCH 5/5] sm501: Fix support for non-zero frame buffer start address BALATON Zoltan
2018-06-22 9:46 ` BALATON Zoltan
2018-06-21 8:08 ` [Qemu-devel] [PATCH 2/5] sm501: Perform a full update after palette change BALATON Zoltan
2018-06-22 1:34 ` Philippe Mathieu-Daudé
2018-06-22 19:21 ` Sebastian Bauer
2018-06-22 21:38 ` BALATON Zoltan [this message]
2018-06-22 0:51 ` [Qemu-devel] [PATCH 0/5] Misc sm501 improvements David Gibson
2018-06-22 1:37 ` Philippe Mathieu-Daudé
2018-06-22 9:24 ` Gerd Hoffmann
2018-06-22 1:32 ` Philippe Mathieu-Daudé
2018-06-22 8:55 ` BALATON Zoltan
2018-06-22 11:55 ` Philippe Mathieu-Daudé
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=alpine.BSF.2.21.1806222337350.86811@zero.eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=aurelien@aurel32.net \
--cc=david@gibson.dropbear.id.au \
--cc=f4bug@amsat.org \
--cc=magnus.damm@gmail.com \
--cc=mail@sebastianbauer.info \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).