Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Andrew Isaacson <adisaacs@mtu.edu>
To: linux@cthulhu.engr.sgi.com
Subject: Re: Resources in X11 port
Date: Tue, 13 Apr 1999 12:52:54 -0400	[thread overview]
Message-ID: <19990413125254.A20170@mtu.edu> (raw)
In-Reply-To: <371371D7.A8187D38@hol.gr>; from Theodoros Nikitopoulos on Tue, Apr 13, 1999 at 07:33:28PM +0300

On Tue, Apr 13, 1999 at 07:33:28PM +0300, Theodoros Nikitopoulos wrote:
> Hello there,
> 
> I've just setup a web page containing helpfull resources I found in
> the net, in concern of the X11 Linux/SGI port. Maybe you know about
> it but well just in case.. :-)
> 
> Although an X11 port seems at first sight quite difficult--in case
> someone has a valuable ammount of information about--it seems
> to be quiete easy.
> 
> Unfortunately, I cannot personally offer any other help in due of a
> project I have to work during the period April-June at INRIA. But
> in any case drop me an e-mail for any progress !  I would be glad
> to hear about it  :-)
> 
> The page is located at :   http://users.hol.gr/~tnik/X11/

Interesting page.  However, I would suggest that anybody who plans to
tackle porting XFree86 to Linux/SGI should contact xfree86@xfree86.org
and ask to become an XFree86 developer.  There are several resources
which are available only to developers, including mailing list
archives and the 4.0 development tree, which will likely prove
invaluable to anyone attempting a port.

If you (the porters) are willing to wait until June to have publicly
distributable code, you should develop for the 4.0 branch rather than
the 3.3 branch.  There are a lot of useful new features in the new
code base, and the new design is quite a bit easier to code for than
the old.

Also, Theodoros, I'm curious why you recommend starting with a 6.3
tree and patching up to XFree86 3.3.3.  Why not just grab the 3.3.3.1
source tarballs and be done with it?

-andy
-- 
Andy Isaacson adisaacs@mtu.edu adi@acm.org    Fight Spam, join CAUCE:
http://www.csl.mtu.edu/~adisaacs/              http://www.cauce.org/

  reply	other threads:[~1999-04-13 16:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-13  8:57 First Linux/SGI in India Raj Mathur
1999-04-13 10:23 ` Ulf Carlsson
1999-04-13 16:33   ` Resources in X11 port Theodoros Nikitopoulos
1999-04-13 16:52     ` Andrew Isaacson [this message]
1999-04-13 17:22       ` Mike Shaver
1999-04-13 19:10       ` Alan Cox
1999-04-13 13:45         ` Miguel de Icaza
1999-04-13 21:18           ` Andrew Isaacson
1999-04-13 17:20             ` Miguel de Icaza
1999-04-14  0:17               ` Alan Cox
1999-04-14  0:17                 ` Alan Cox
1999-04-14  9:39                 ` Torbjorn Gannholm
1999-04-14 10:35                   ` Alan Cox
1999-04-14 10:35                     ` Alan Cox
1999-04-15  4:36                     ` Raj Mathur
1999-04-15  4:36                       ` Raj Mathur
1999-04-15 12:58                       ` Miguel de Icaza
1999-04-16  0:20                         ` Alan Cox
1999-04-15 18:38                           ` Miguel de Icaza
1999-04-15 18:38                             ` Miguel de Icaza
1999-04-16  0:20                           ` Alan Cox
1999-04-13 19:10         ` Alan Cox
1999-04-13 19:23         ` Ulf Carlsson
1999-04-13 17:21     ` Ulf Carlsson
1999-04-13 20:20       ` Resources in X11 port #2 Theodoros Nikitopoulos

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=19990413125254.A20170@mtu.edu \
    --to=adisaacs@mtu.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    /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