All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kostas Gewrgiou <gewrgiou@imbc.gr>,
	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 17:27:16 -0700	[thread overview]
Message-ID: <20010125172716.F594@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.05.10101251235590.18764-100000@callisto.of.borg>; from geert@linux-m68k.org on Thu, Jan 25, 2001 at 12:38:25PM +0100


On Thu, Jan 25, 2001 at 12:38:25PM +0100, Geert Uytterhoeven wrote:
> On Thu, 25 Jan 2001, Kostas Gewrgiou wrote:
> > On Wed, 24 Jan 2001, Petr Vandrovec wrote:
> > > On 24 Jan 01 at 11:11, Ani Joshi wrote:
> > > > I recently ran into an issue with the matroxfb driver and XFree86 4.0.2's
> > > > matrox driver.  Sometime in the past someone decided to use BE
> > > > register access in matroxfb for BE machines, while this is probably The
> > > > Right Way, it produces problems in X.  I can use BE register access
> > > > macro's in X but it was causing problems with the engine, perhaps some DMA
> > > > issue although the dma BE bits are on.
> > >
> > > Using big-endian on PPC was required by PPC users for compatibility with
> > > existing XF[86][68]_FBDev servers. Are you sure that there are no problems
> > > otherwise, and that it works correctly on all PReP/CHRP/???? architectures?
> >
> > Nope it won't cause any problems, none of the XF[86][68]_FBDev servers where
> > accelerated for matrox, other libs (SDL etc) that have accel for matroxfb
> > don't work correctly for ppc either.
>
> XF68_FBDev is accelerated for matroxfb, at least on the PPC platform.

Er, it is?  I thought only Xpmac was...

> > 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...

Just my thoughts on this, but the matrox+ppc camp is relativly small (Yes, I
know some chrps which now work have 'em) and since I'm guessing (Ani, can you
benchmark some of this? :)) XF4 is faster than Xpmac, putting this in now,
with a toggle bit for people that really don't wanna upgrade to X4, and removing
the toggle in 2.5..  It should be an overall win.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-01-26  0:27 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
2001-01-26  0:27     ` Tom Rini [this message]
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=20010125172716.F594@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --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 \
    /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.