linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Michel D	nzer <daenzerm@student.ethz.ch>,
	Iain Sandoe <iain@sandoe.co.uk>,
	takashi oe <toe@unlserve.unl.edu>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: LinuxPPC X Server
Date: Wed, 02 Aug 2000 12:40:49 +0200	[thread overview]
Message-ID: <3987FAB1.14086A30@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.10.10007311758340.20511-100000@opal.biophys.uni-duesseldorf.de


Michael Schmitz wrote:
>
> > > >>And yes, there have been reports of people trying it (one yesterday - said
> > > >>it was quicker in some places & slower in others...)
> >
> > He didn't provide any numbers though. For all chipsets which have an
> > accelerated driver in X 4, it's almost certainly faster than anything else -
> > and also for the others it should be faster than X 3.3.x .
>
> Talking about x11perf on Mach64? It's faster for scrolls and rectcopys but
> as fast as the fbdev driver or slightly slower for other stuff. I can send
> logs (at 32 bpp) to anyone that cares to analyze them. Switching back to
> 3.3.x is something I always wanted to do but never found time for, but
> even the fbdev driver on 4.01 feels a lot faster than the 3.3.x one.

I installed Franz's XFree-4.0.1-0.36a RPMs, and with these I can run
either the new XFree68 server or the XF68_FBDev server from 3.3.6 or
Xpmac. In fact, I have all three of them running right now at the same
time on different VCs (well, Xpmac isn't really usable, because I don't
know how to talk it into using the new mouse stuff, but that's a
different story).

So I don't see any need to switch back to 3.3.x for anything except
possibly the server binary itself. All the rest, font server, libraries,
seem to be compatible.

And although I am only using the fbdev driver, it is definitely faster:
For x11perf -scroll500, I get (8 bit video on valkyriefb):

  36.5/sec for XFree-4.0.1
  13.0/sec for XF68_FBDev-3.3.6 (similarly for Xpmac, from memory)

So scrolling is nearly 3 times faster!

Two or three small annoying problems remain:

1) Clicking on a scroll arrow (in netscape, for example) for more than 1
or 2 seconds, sometimes even less, makes the window scroll all the way
to the end.

2) There are color palette problems on the 8 bit display. Probably the
defaults have changed for colors that cannot be allocated? Sometimes
this gives me black text on black background, for instance in "make
menuconfig" or in pinfo. These are unusable when some color hungry
program such as netscape is already running.

While these 2 problems only occur with the new XFree86 server and not
with XF68_FBDev, the following seems to come from the new libraries. To
verify this suspicion, I would have to revert to the XFree-3.3.6 RPMs.
It could also come from a number of other packages I upgraded recently.
Difficult to find out.

3) Mozilla-M16 (and M17_BRANCH) doesn't work any more. It starts
loading, and when called with an URL, gets to the first browser window.
Any further action gives "segmentation fault" or "illegal instruction"
or just silent death. When called without URL, it dies silently before
the first window comes up.

--
Martin

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

  reply	other threads:[~2000-08-02 10:40 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-30 20:00 LinuxPPC X Server Iain Sandoe
2000-07-30 18:14 ` Michel D nzer
2000-07-30 22:33   ` Steffen Haeuser
2000-07-31  3:12   ` Daniel Jacobowitz
2000-07-31  7:40     ` Michel Dänzer
2000-08-01 21:03       ` Daniel Jacobowitz
2000-07-31 16:05   ` Michael Schmitz
2000-08-02 10:40     ` Martin Costabel [this message]
2000-07-30 22:46 ` Steffen Haeuser
  -- strict thread matches above, loose matches on Subject: below --
2000-08-02 16:07 Jack Howarth
2000-08-03 13:27 ` Kostas Gewrgiou
2000-08-02  0:25 Iain Sandoe
2000-07-31 14:07 Benjamin Herrenschmidt
2000-08-01 19:05 ` Michel Dänzer
     [not found]   ` <20000801191739.26835@mailhost.mipsys.com>
2000-08-01 19:37     ` Michel Dänzer
     [not found]       ` <20000801204113.29901@mailhost.mipsys.com>
2000-08-01 21:31         ` Michel Dänzer
2000-08-02 12:45           ` Geert Uytterhoeven
2000-08-02 23:27             ` Michel Dänzer
2000-07-30 21:24 Iain Sandoe
2000-07-31 12:53 ` Josh Huber
2000-07-31 16:28   ` Michael Schmitz
2000-07-30 20:33 Iain Sandoe
2000-07-31  7:50 ` Michel Dänzer
2000-07-31  9:25   ` Steffen Haeuser
2000-07-31  8:47     ` Michel Dänzer
2000-07-31 10:05       ` Steffen Haeuser
2000-07-31  9:03         ` Michel Dänzer
2000-07-31 10:21           ` Steffen Haeuser
2000-08-01 12:54       ` Kostas Gewrgiou
2000-08-01 16:25         ` Steffen Haeuser
2000-08-01 21:06         ` Daniel Jacobowitz
2000-08-02  9:20           ` Michel Dänzer
2000-08-02 18:17           ` Kostas Gewrgiou
2000-07-30 16:56 Iain Sandoe
2000-07-30 19:29 ` Steffen Haeuser
2000-07-30 21:13 ` Timothy A. Seufert
2000-07-29 13:31 Steffen Haeuser
2000-07-29 22:55 ` Takashi Oe
2000-07-30 11:27   ` Steffen Haeuser
2000-07-30 11:54     ` Takashi Oe
2000-07-30 14:40       ` Steffen Haeuser
2000-07-30 14:41         ` Takashi Oe
2000-07-30 16:13           ` Steffen Haeuser

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=3987FAB1.14086A30@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=daenzerm@student.ethz.ch \
    --cc=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    --cc=toe@unlserve.unl.edu \
    /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).