From: Michel Dänzer <daenzerm@student.ethz.ch>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Michel Lanners <mlan@cpu.lu>,
dmj+@andrew.cmu.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: Control fb problem on 8500
Date: Mon, 21 Aug 2000 15:19:11 +0200 [thread overview]
Message-ID: <39A12C4F.1AEFBA48@student.ethz.ch> (raw)
In-Reply-To: Pine.LNX.4.10.10008211320490.11699-100000@opal.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
>
> > > That's what I was thinking about. However, I'm not sure that XFree
> > > supports a display with discontiguous lines in video memory. I think I
> > > read that somewhere in some mailing list or X doc... Can any of the
> > > XFree specialists confirm?
> >
> > I can speak for XFree86 3.x only, not for 4.x.
> >
> > The only way to work with this is to make xres_virtual = xres+0x20. But
> > then XFree86 will draw into the cursor region, too.
>
> I think it used to work without such a hack - some old m68k Macs had the
> video scan lines start every 1024 bytes but the actual xres was smaller.
> I'll have to look at the macfb code to see what xres_virtual was set to.
> I'm sure the X server didn't draw to the offscreen region as that would
> have caused a bus error (at least the earlier 3.3.x versions didn't.
> Later X versions drawing beyond xres would in fact explain bus errors
> some people saw ...).
X 4.0 distincts 3 values:
'xres' - physical horizontal resolution of the current mode.
virtualX - horizontal resolution of the virtual screen. Never changes during a
screen's life.
displayWidth - the length in pixels of each scanline in memory.
Unfortunately, the fbdev driver still assumes that displayWidth == virtualX,
and most other drivers have adapted that assumption (for most of them it's
right though :) .
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-21 13:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 17:45 Control fb problem on 8500 Kevin M. Myer
2000-08-15 18:26 ` Michel D nzer
2000-08-15 19:41 ` Michel Lanners
2000-08-18 21:02 ` Michel Lanners
2000-08-19 6:47 ` Daniel Jacobowitz
2000-08-19 7:18 ` Michel Lanners
2000-08-19 11:59 ` Benjamin Herrenschmidt
2000-08-19 14:15 ` XF4 hangs on 2.4 kernel (was: Re: Control fb problem on 8500) Michel Lanners
2000-08-19 15:16 ` Martin Costabel
2000-08-23 12:18 ` Kostas Gewrgiou
2000-08-19 12:12 ` Control fb problem on 8500 Geert Uytterhoeven
2000-08-21 11:25 ` Michael Schmitz
2000-08-21 13:19 ` Michel Dänzer [this message]
2000-08-21 16:44 ` Geert Uytterhoeven
2000-08-21 17:11 ` Michael Schmitz
2000-08-19 13:20 ` Michel Dänzer
2000-08-21 8:57 ` Michel Dänzer
2000-08-21 10:46 ` Geert Uytterhoeven
2000-08-21 13:14 ` Michel Dänzer
2000-08-21 16:45 ` Geert Uytterhoeven
2000-08-22 8:33 ` Michel Dänzer
2000-08-22 9:42 ` Geert Uytterhoeven
2000-08-22 10:14 ` Michel Dänzer
2000-08-22 21:15 ` Michel Lanners
2000-08-22 21:55 ` Michel Dänzer
2000-08-23 11:51 ` Geert Uytterhoeven
2000-08-22 21:10 ` Michel Lanners
2000-08-22 22:39 ` Michel Dänzer
2000-08-23 8:11 ` Michael Schmitz
2000-08-23 8:21 ` Michel Dänzer
2000-08-21 11:33 ` Michael Schmitz
2000-08-19 14:40 ` David Riley
[not found] <200008160459.XAA20764@lists.linuxppc.org>
2000-08-22 10:51 ` William H. Schultz
2000-08-22 11:56 ` Benjamin Herrenschmidt
2000-08-22 16:52 ` Geert Uytterhoeven
2000-08-23 14:03 ` William H. Schultz
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=39A12C4F.1AEFBA48@student.ethz.ch \
--to=daenzerm@student.ethz.ch \
--cc=dmj+@andrew.cmu.edu \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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).