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.
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
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.
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.
Let's start a dialog here. Thanks!
John Hawkes
|