From: "Iain Sandoe" <iain@sandoe.co.uk>
To: SteffenH@hyperion-software.de, takashi oe <toe@unlserve.unl.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: LinuxPPC X Server
Date: Sun, 30 Jul 2000 21:00:13 +0100 [thread overview]
Message-ID: <200007301959.UAA25203@hyperion.valhalla.net> (raw)
n Sun, Jul 30, 2000, Steffen Haeuser wrote:
> Am 30-Jul-00 schrieb Iain Sandoe:
>>On the up side I built it yesterday (with Ani's rsync stuff in place of the
>>xfree86 directory). It build without problem - now all I need is time to
>>test ;-)
>
>>At present I'm not able to host the binaries (and not enough experienced
>>with X to be sure of building the right collection :-)
>
>>On the down side it took **all** day to build on my 300M G3.
>
>>And yes, there have been reports of people trying it (one yesterday - said
>>it was quicker in some places & slower in others...)
>
> Did these sources you have compiled include the DRI Drivers ?
Don't know - I did a make "World" so I guess that should have built
everything?
This will be the first time I've tried XF directly (although my X86 box has
it) - so I'm very new to it.
> Do you know if the bug concerning VidModeExtension 640x480 Fullscreen is gone
> ? (I could send you a small test executable...).
I will mail you off list when I have had time to do a test.
> You told it took 1 day to do... so
> there were big problems/source code changes to do ? Or what caused this ?
No problems, no changes, it's just *BIG* :-)
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-30 20:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-30 20:00 Iain Sandoe [this message]
2000-07-30 18:14 ` LinuxPPC X Server 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
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=200007301959.UAA25203@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=SteffenH@hyperion-software.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--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 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.