Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ehab Fares <ehab@aia.rwth-aachen.de>
To: Shrijeet Mukherjee <shm@cthulhu.engr.sgi.com>
Cc: linux-fbdev@vuser.vu.union.edu,
	Linux porting team <linux@cthulhu.engr.sgi.com>
Subject: Re: [linux-fbdev] SGI VW 540, fbdev... and other stuff
Date: Tue, 22 Aug 2000 17:59:43 +0200	[thread overview]
Message-ID: <00082218283000.08755@aia067> (raw)
In-Reply-To: <Pine.SGI.4.21.0008220847450.264415-100000@tantrik.engr.sgi.com>

On Tue, 22 Aug 2000, Shrijeet Mukherjee wrote:
> Well as I have tried to explain in the past the situation is not as cut
> and dry as all that. For most hardware systems, well written driver code
> is a good place to start. (in fact al of the internal port to linux for
> the 320 was done without formal docs, or the engg's to talk to)
> 
> The real problem is that the 320 gfx family uses a SGI style
> high-performance which is different from the AGP style approach that the
> other guys use. Porting this to linux .. or more than knowing how the
> hardware works .. since we need to port a very complicated mechanism, for
> which linux may not have obvious and ready replacements.
> 
> On top of that .. there are potentially Intellectual Property issues with
> the management style. Thus the concerns with just releasing the specs.
> 
> Since this is a recurring question, are there people on this list that are
> personally motivated to try and port this system over ?
> 
We are using a 540 system with the top configuration (4 processors, 2GB Ram and
the flat panel 1600SW). We are certainly motivated to get linux and the
X-Server working  poperly. As already posted in this mailing list the X-server
is not the only problem. I therefore would suggest to start collecting all the
problems that should be solved and look for people interested in working on
the port.  

The problems we have are:
1) new kernels simply wouldn'[t boot the machine. I got the machine working
with  the 2.2.10 patched kernel. All the four processors are working.
2) We have only 960 MB Ram of the installed 2GB working.
3) strange behaviour of the keyboard.
4) the parallel port is not working. (we haven't tested the rest of the ports)
5) very poor X performance with hangs every now and then which is probably
because of the X-Server.

Are there other people having similar or other problems and interested in
solving them? Is there anyone who have the experience or knowledge of that
system (and linux) who can help?

I personally would like to help but need some information and
details as I'm not a kernel hacker. 

Ehab.

      parent reply	other threads:[~2000-08-22 16:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-05 23:13 SGI VW 540, fbdev and pot pourii of faults and evidence..:-) phil
2000-08-09 23:17 ` [linux-fbdev] " James Simmons
2000-08-09 23:28   ` philloc
2000-08-11  7:50     ` Shrijeet Mukherjee
2000-08-11  7:50       ` Shrijeet Mukherjee
2000-08-13 15:10     ` [linux-fbdev] SGI VW 540, fbdev and pot pourii of faults and Alan Cox
2000-08-13 15:10       ` Alan Cox
2000-08-22  3:55   ` [linux-fbdev] SGI VW 540, fbdev and pot pourii of faults and evidence..:-) Andy Isaacson
2000-08-22 15:43     ` James Simmons
2000-08-22 15:53       ` Shrijeet Mukherjee
2000-08-22 15:53         ` Shrijeet Mukherjee
2000-08-22 15:59         ` Ehab Fares [this message]

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=00082218283000.08755@aia067 \
    --to=ehab@aia.rwth-aachen.de \
    --cc=linux-fbdev@vuser.vu.union.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=shm@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