From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: mzyngier@freesurf.fr
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] Permedia2 fb on PPC
Date: 08 Dec 2001 23:51:36 +0100 [thread overview]
Message-ID: <1007851896.9146.12.camel@pismo> (raw)
In-Reply-To: <wrpr8q5baho.fsf@hina.wild-wind.fr.eu.org>
On Sat, 2001-12-08 at 23:41, Marc ZYNGIER wrote:
> >>>>> "Michel" == Michel Dänzer <michdaen@iiic.ethz.ch> writes:
>
> Michel> And does it work with the XFree86 glint driver with Option
> Michel> "UseFBDev"?
> >>
> >> Don't know yet. _Now_ that I have a console (thanks to this patch),
> >> I'll have a look at the X11 thingy.
>
> Michel> Well at least when I last worked on the glint driver, it
> Michel> relied on the register aperture being big endian.
>
> Indeed, glint driver doesn't work with UseFBDev.
>
> Could this be a chipset issue (3DLabs vs TI) ? Mine is a Texas
> Instrument (aka ti_pm2) :
No, IIRC that's exactly the one it assumes you have if you're running
pm2fb.
As I said, the driver assumes the register aperture is big endian with
Option "UseFBDev". And without, it will also try to use the big endian
aperture.
If there's really no way to use the big endian aperture on some boards,
the only solution I see is to change both pm2fb and the glint driver to
always use the little endian one.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-08 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 10:29 [PATCH] Permedia2 fb on PPC Marc ZYNGIER
2001-12-05 17:19 ` Michel Dänzer
2001-12-05 22:52 ` Marc ZYNGIER
2001-12-08 21:47 ` Michel Dänzer
2001-12-08 22:41 ` Marc ZYNGIER
2001-12-08 22:51 ` Michel Dänzer [this message]
2001-12-08 23:08 ` Marc ZYNGIER
2001-12-08 23:43 ` Michel Dänzer
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=1007851896.9146.12.camel@pismo \
--to=michdaen@iiic.ethz.ch \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mzyngier@freesurf.fr \
/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).