[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems with xfree86 4.0.1d - Compac Armada 1500c(CT69000+DSTN)



4.0.1e (and 4.0.1-2 by Branden) does work on my IBM ThinkPad235
with C&T 65555. Thanks!

In <[🔎] 20001109065734A.kgh12351@kgh12351.nifty.ne.jp>,
 on "Thu, 09 Nov 2000 06:57:34 +0900",
  Taketoshi Sano <sano@debian.org> wrote:

> 4.0.1e has some updates on C&T driver, it does not use cfb now but uses fb.
> 
> But I'm not sure if this new version can solve this problem, the change 
> from 4.0.1d to 4.0.1e may be just irrelevant.

The modification to use the new fb code was introduced on chips driver
at 4.0.1d partly, and that was very possibly the cause of the problem.
But 4.0.1e completely moves to use the new fb code and most of the old
cfb code is now removed from chips driver code.

I have checked the xStone and it shows great improvement, at least
in depth 16 where I tested both of 4.0.1c and 4.0.1d (4.0.1d was
broken and it does not work with/without "UseFB" option, so I can't
check the performance of it).

xStone.depth16.tp235_ct65555:4.0.1c(832,603)

TOTAL    131747 lineStones
TOTAL     12181 fillStones
TOTAL     10447 blitStones
TOTAL   3314532 arcStones
TOTAL    374687 textStones
TOTAL     26601 complexStones
TOTAL     26198 xStones

xStone.depth16.tp235_ct65555:4.0.1e(832,603)

TOTAL    197247 lineStones
TOTAL     94088 fillStones
TOTAL     45069 blitStones
TOTAL  15165544 arcStones
TOTAL   1219626 textStones
TOTAL    126339 complexStones
TOTAL    126138 xStones

 You can find 'xbench' which is the tool for this xStone bench-marking
 from <ftp://ftp.xfree86.org/pub/xbench/xbench.tar.gz>.

 'xbench' and 'Xmark' is the two popular bench marking for X server,
  or at least I was told so.  The usage of xbench is described in README
  file of that tar ball, and the usage of Xmark is described in Xmark
  itself (which is a bourne shell script to summarize the result from
  x11perf command).

> I will do it, but it will take some more days.

I'm happy that I don't need to spend more days to find the solution :)

Thanks.
-- 
  Taketoshi Sano: <sano@debian.org>,<sano@debian.or.jp>,<kgh12351@nifty.ne.jp>



Reply to: