From: Dmitry <dbaryshkov@gmail.com>
To: andrzej zaborowski <balrogg@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tc6393xb: non-accelerated FB support
Date: Tue, 4 Nov 2008 06:14:01 +0300 [thread overview]
Message-ID: <bc64b4640811031914h2c6b0861kf71e377c3e3904fe@mail.gmail.com> (raw)
In-Reply-To: <fb249edb0811031546r754bcd45o4f888737042c0a5b@mail.gmail.com>
2008/11/4 andrzej zaborowski <balrogg@gmail.com>:
> 2008/11/2 Dmitry Baryshkov <dbaryshkov@gmail.com>:
> [...]
>> As a second thought I've implemented blanking, implemented your
>> suggestions. Please take a look at the following patch.
>
> Thanks, this looks better.
Good!
>
>>
>> From 57cd66fefc31ac18f1f896a8ca53441b01f0d345 Mon Sep 17 00:00:00 2001
>> From: Dmitry Baryshkov <dbaryshkov@gmail.com>
>> Date: Thu, 11 Sep 2008 04:39:15 +0400
>> Subject: [PATCH] tc6393xb: non-accelerated FB support
>>
>> Signed-off-by: Dmitry Baryshkov <dbaryshkov@gmail.com>
>> ---
>> hw/devices.h | 4 +-
>> hw/tc6393xb.c | 120 +++++++++++++++++++++++++++++++++++++++++++++++-
>> hw/tc6393xb_template.h | 72 +++++++++++++++++++++++++++++
>> hw/tosa.c | 17 +++++--
>> 4 files changed, 205 insertions(+), 8 deletions(-)
>> create mode 100644 hw/tc6393xb_template.h
>> +
>> +#if BITS == 8
>> +# define SET_PIXEL(addr, color) *(uint8_t*)addr = color;
>> +#elif BITS == 15 || BITS == 16
>> +# define SET_PIXEL(addr, color) *(uint16_t*)addr = color;
>> +#elif BITS == 24
>> +# define SET_PIXEL(addr, color) \
>> + addr[0] = color; addr[1] = (color) >> 8; addr[2] = (color) >> 16;
>> +#elif BITS == 32
>> +# define SET_PIXEL(addr, color) *(uint32_t*)addr = color;
>> +#else
>> +# error unknown bit depth
>> +#endif
>
> Hmm.. now when I look at this it triggers an alert because
> *(uint16_t *) addr = color;
> and
> addr[0] = coor; addr[1] = (color) >> 8;
> do different things on a bigendian host. But I can't tell offhand
> which one we want here...
>
> pxa2xx_template.h and pl110_template.h might have the same problem.
>From a quick glance most other video emulators will suffer from this problem.
IMO we can merge this as is and later fix this if the problem really exists
on BE hosts.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2008-11-04 3:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 13:16 [Qemu-devel] [PATCH] scoop: GPRR reports the state of GPIO lines Dmitry Baryshkov
2008-11-02 13:16 ` [Qemu-devel] [PATCH] tc6393xb: initial support for nand Dmitry Baryshkov
2008-11-02 13:16 ` [Qemu-devel] [PATCH] tosa: support leds Dmitry Baryshkov
2008-11-02 13:16 ` [Qemu-devel] [PATCH] tosa: basic lcd support Dmitry Baryshkov
2008-11-02 13:16 ` [Qemu-devel] [PATCH] tosa: provide correct IRQ to tc6393xb init Dmitry Baryshkov
2008-11-02 13:16 ` [Qemu-devel] [PATCH] tosa: disable pxafb as it's not used on tosa Dmitry Baryshkov
2008-11-02 13:16 ` [Qemu-devel] [PATCH] tc6393xb: non-accelerated FB support Dmitry Baryshkov
2008-11-02 16:31 ` andrzej zaborowski
2008-11-02 17:36 ` Dmitry Baryshkov
2008-11-02 19:40 ` Dmitry Baryshkov
2008-11-03 23:46 ` andrzej zaborowski
2008-11-04 3:14 ` Dmitry [this message]
2008-11-02 16:09 ` [Qemu-devel] [PATCH] tosa: basic lcd support andrzej zaborowski
2008-11-02 17:19 ` Dmitry Baryshkov
2008-11-04 9:14 ` andrzej zaborowski
2008-11-02 14:45 ` [Qemu-devel] Re: [PATCH] scoop: GPRR reports the state of GPIO lines Dmitry Baryshkov
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=bc64b4640811031914h2c6b0861kf71e377c3e3904fe@mail.gmail.com \
--to=dbaryshkov@gmail.com \
--cc=balrogg@gmail.com \
--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).