From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Ani Joshi <ajoshi@shell.unixbox.com>
Cc: 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: Wed, 24 Jan 2001 20:44:49 MET-1 [thread overview]
Message-ID: <1383CA701391@vcnet.vc.cvut.cz> (raw)
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?
And I think that matroxfb should return current driver's endianess to
userspace... Do we have some spare bits in fb_fix_info?
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-24 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 20:44 Petr Vandrovec [this message]
2001-01-25 10:29 ` [linux-fbdev] Matrox and XFree86 4.0.2 update 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
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=1383CA701391@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=ajoshi@shell.unixbox.com \
--cc=debian-powerpc@lists.debian.org \
--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.