From: Michel Dänzer <daenzer@relog.ch>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
Ani Joshi <ajoshi@shell.unixbox.com>,
debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org,
linux-fbdev@vuser.vu.union.edu
Subject: Re: [linux-fbdev] Matrox and XFree86 4.0.2 update
Date: Thu, 25 Jan 2001 14:02:30 +0100 [thread overview]
Message-ID: <3A7023E6.516580F@relog.ch> (raw)
In-Reply-To: Pine.LNX.4.30.0101251245400.17598-100000@idd-01.imbc.gr
Kostas Gewrgiou wrote:
>
> On Thu, 25 Jan 2001, Geert Uytterhoeven wrote:
>
> > On Thu, 25 Jan 2001, Kostas Gewrgiou wrote:
>
> > > Changing the endian to little is the *right* thing, big-endian mode
> > > doesn't offer us anything beyond problems in matroxfb 8/16 bit accesses
> > > become a nightmare there...
> >
> > 8/16 bit accesses? I assume you're talking about the frame buffer, not
> > about the register accesses?
>
> No i am talking about register accesses, for example
> the mga driver in xfree86 uses
> #define MGAISBUSY() (INREG8(MGAREG_Status + 2) & 0x01)
> SDL uses
> #define mga_wait(space) { \
> while ( mga_in8(MGAREG_FIFOSTATUS) < space ); \
> }
>
> Both will fail under big-endian mode in PPC, the addressing is changed
> so you have to use something like *(addr + (3-addr%4) to get the right
> byte (i hope i got it right, its still early here)
What about adapting the macros then?
Michel
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-25 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 20:44 [linux-fbdev] Matrox and XFree86 4.0.2 update Petr Vandrovec
2001-01-25 10:29 ` Kostas Gewrgiou
2001-01-25 11:38 ` Geert Uytterhoeven
2001-01-25 11:08 ` Kostas Gewrgiou
2001-01-25 13:02 ` Michel Dänzer [this message]
2001-01-26 0:27 ` Tom Rini
2001-01-26 8:21 ` Geert Uytterhoeven
2001-01-26 15:09 ` Tom Rini
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=3A7023E6.516580F@relog.ch \
--to=daenzer@relog.ch \
--cc=VANDROVE@vc.cvut.cz \
--cc=ajoshi@shell.unixbox.com \
--cc=debian-powerpc@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=gewrgiou@imbc.gr \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michdaen@iiic.ethz.ch \
/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).