From: Matt Porter <porter@cox.net>
To: Laurent Mohin <laurent.mohin@acterna.com>
Cc: Stefan Roese <stefan.roese@esd-electronics.com>,
Michael Meriin <Michael@KSWaves.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: How to change endian attribute for a memory region
Date: Tue, 15 Oct 2002 07:15:46 -0700 [thread overview]
Message-ID: <20021015071546.A14041@home.com> (raw)
In-Reply-To: <OFC1D42D18.CCDFA3B3-ONC1256C53.003C90BA@eni.wago.de>; from laurent.mohin@acterna.com on Tue, Oct 15, 2002 at 01:07:19PM +0200
On Tue, Oct 15, 2002 at 01:07:19PM +0200, Laurent Mohin wrote:
>
> Stefan,
>
> I'm the initiator of the question.
> I use the Epson chip in big endian mode. The problem is that in 16 bpp
> mode, the RGB mapping into video memory is fixed by the chip and described
> in little endian format.
>
> By the way, I really studied the chip and if I want to be able to manage
> both 8 bpp and 16 bpp mode, I need to be able to change the endianness
> attribute of the memory region.
Why wouldn't you access video memory via a sthbrx instruction (writew)?
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-15 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 11:07 How to change endian attribute for a memory region Laurent Mohin
2002-10-15 14:15 ` Matt Porter [this message]
2002-10-15 14:35 ` Allen Curtis
-- strict thread matches above, loose matches on Subject: below --
2002-10-15 16:40 Ralph Blach
2002-10-15 15:00 Laurent Mohin
2002-10-15 15:45 ` Dan Malek
2002-10-15 14:57 Laurent Mohin
2002-10-15 14:34 Ralph Blach
2002-10-15 9:08 Laurent Mohin
2002-10-15 9:55 ` Stefan Roese
2002-10-14 10:18 ` Michael Meriin
2002-10-15 8:42 Laurent Mohin
2002-10-14 8:57 ` Michael Meriin
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=20021015071546.A14041@home.com \
--to=porter@cox.net \
--cc=Michael@KSWaves.com \
--cc=laurent.mohin@acterna.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stefan.roese@esd-electronics.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.