According to John Hawkes ...
>
> Simon has asked me to try to get my hands around the
> Linux-MIPS64-on-O2000 (or is it O200?) project to understand its status.
> The premise is that early Linux experience with the SN architecture
> translates to a faster bringup of Linux-IA64-SN1 and the hope of a real
> headstart on exploiting the architectural capabilities of SN1 and SN2.
I have been trying to push this view point along when we started the
linux port to o200 in Fall 98. I am glad that the view points are
converging here.
>
> It is my understanding that each of you has been involved in various
> aspects of Linux-MIPS64-O2000. I understand that up to now, the project
> has been viewed by Engineering as a low-priority, almost off-the-books
> effort, but I believe that view is changing, at least from the view of
> higher management.
>
> I would appreciate greatly if each of you would give me a brief summary
> of what you've been doing, personally and as a project, and where the
> current roadblocks are. Simon is especially interested in having a
Ported 2.1.100 to o200 to single user. The major roadblock was the tool
set which was gcc frontend hosted on irix and the mongoose backend. This
would not work for asm code with .section attributes in between and one
of the mongoose releases fixed only this. There were other problems with
front end and back end.
> visible list of bugworks PV bugs. And yes, I do understand that some of
> the roadblocks are in the compilers. We need to clarify exactly what
> the problems are before we can motivate that part of the Engineering
> organization to fix them.
>
We talked to the compilers group at that time (Jan 99) to make this
a proper product release. At that time, (Bean Anderson) and others
wanted a full ABI story for them to produce the mips 64 bit tools for
linux apps. The wanted to know the o32/n32/64 details. So, at that
time we decided that we would not build 64 bit apps and just use
the existing mips o32 apps.
One of the important things that needs to be done to help sn1ia64 is
for Simon's group to get a multinode multi io SN1 mips box and test
the current release on that. If this can be done asap, the IO part
of sn1ia64 can try out the devfs/hwgraph, PCI infrastructure and
distributed IO discovery and other portions of code on final hardware.
Our current medusa simulator may not be sufficient.
For VM/NUMA only an o2000 port which can come up to multi user should
be sufficient.
> As far as which bugworks project to use, it seems to me that it's
> easiest to use sgi.bugs.linux-mips64, rather than create a new project
> like sgi.bugs.o2000-linux or sgi.bugs.origin-linux. What do you think?
> Yes, some of the bugs (or feature enhancements, or PV "issues") are
> platform-specific and some are MIPS64-specific, but I think it
> complicates matters to have multiple bugworks projects.
I dont know if we are at the bug filing stage yet. We need to get the
base code in place first. Or if we want to treat the work as bugs I
would like to file the first one :-)
Need 2.3.47 to work multi user on SN1 and SN0-o2000
Thanks
srinivasa
>
> Let's start a dialog here. Thanks!
>
> John Hawkes
>
>
|