From roland.mainz at nrubsig.org Thu Oct 16 20:26:49 2008 From: roland.mainz at nrubsig.org (Roland Mainz) Date: Fri, 17 Oct 2008 05:26:49 +0200 Subject: [emerging-platforms-discuss] Screenshots/pictures for the Solaris/SystemZ port ? Message-ID: <48F805F9.3B26D543@nrubsig.org> Hi! ---- Just an old idea (already discussed with Jeff): Can someone with Solaris/SystemZ access (or access to the hardware) make some screenshots and/or pictures for the project page (http://www.opensolaris.org/os/project/systemz/), please ? * Ideas for screenshots would be: - Show system login prompt after boot - Screenshot showing the output of: $ uname -a $ isalist $ psrinfo -v - Screenshot showing the output of $ /usr/bin/ksh93 /usr/demo/ksh/fun/mandelbrotset1 - Screenshot showing the output of $ /usr/bin/ksh93 /usr/demo/ksh/fun/gnaw (note that this is a PacMan clone, you have to start the game to get a nice screenshot similar to http://www.opensolaris.org/os/project/ksh93-integration/screenshots/gnaw_v8_anim_normal.gif * Ideas for pictures would be: - Machine, doors closed, doors open - Machine, mainboard(s) pulled out - Machine, system console - Picture of lab ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 3992797 (;O/ \/ \O;) From storycrafter at gmail.com Sat Oct 18 15:49:44 2008 From: storycrafter at gmail.com (Mark Martin) Date: Sat, 18 Oct 2008 17:49:44 -0500 Subject: [emerging-platforms-discuss] Project Proposal -- Port to MIPS architecture Message-ID: I am seeking approval for a project for porting OpenSolaris to the MIPS architecture. Proposal: Provide code changes, tools, documentation, and other necessary artifacts for a port of OpenSolaris to the MIPS architecture. Movidis, a maker of MIPS based components and systems has expressed interest in support of this port, so it is likely that their products will be the initial supported platforms -- support for other MIPS based platforms may follow suit. The current project goal is to support the MIPS64 architecture, although the MIPS32 ISA may also be a possibility. Among other deliverables, it is expected that this port will include integration of some or all of changes identified in the gccfss project: http://www.opensolaris.org/jive/thread.jspa?threadID=24934, and preserved here: http://cr.opensolaris.org/~devnull/6515400/. There may be additional key core kernel changes similar to those identified in the PowerPC port project. Some of these changes were necessary for support for a gcc based cross compilation tool chain. This cross compiler tool chain is necessary for boot strap of the port, but a self-hosting, native gcc tool chain is also a goal for the project. A discussion list and source repository are also requested. Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From storycrafter at gmail.com Sun Oct 19 06:35:49 2008 From: storycrafter at gmail.com (Mark Martin) Date: Sun, 19 Oct 2008 08:35:49 -0500 Subject: [emerging-platforms-discuss] [osol-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: Message-ID: On Sun, Oct 19, 2008 at 12:54 AM, Cyril Plisko wrote: > > > do you have enough hardware documentation to do this ? At the moment that is a gap. This was also a gap for other platforms considered for the PowerPC platform (Sony PS3, Apple PowerMacs), but I believe our advantage here is that we may have a platform where the vendor is willing to work with us. Movidis has offered to field technical questions, and I have a request in to Cavium Networks for more detailed documentation on the Octeon. I wonder if we will get similar access to documentation if the Qube is also considered as a target. > > Who will be the initial project members ? For the moment, myself, but I'll certainly welcome other volunteers. I do plan to reach out to the Linux, NetBSD, and OpenBSD communities for help from their MIPS porting folks. > > > Anyhow, +1 for this project. > > -- > Regards, > Cyril > -------------- next part -------------- An HTML attachment was scrubbed... URL: From storycrafter at gmail.com Sun Oct 19 06:45:53 2008 From: storycrafter at gmail.com (Mark Martin) Date: Sun, 19 Oct 2008 08:45:53 -0500 Subject: [emerging-platforms-discuss] [osol-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: Message-ID: On Sat, Oct 18, 2008 at 10:04 PM, john g4lt wrote: > +1 > > my qube votes +1 too XD > > In fact, for optimal political success for this, I'd suggest making > the MIPS qubes the primary target, since they were acquired by Sun > with the entire Cobalt company Not a bad idea, but challenging due to the max memory sizes on the Qubes. I also wonder how much information and support we will get for those older platforms. I think if there is any chance of running on running on any platform with less than 512MB (like the Qube or most ARM boards), you'll have to figure out how to change the boot and install requirements. Personally, I think it is a shame to see Linux running on 64MB devices (for specific purposes) and know that it'd be nigh on impossible to see OpenSolaris running there right now. If you're volunteering to help, I'd welcome it and suggest we investigate how much documentation we will get from Sun regarding those systems. I'd personally consider it as a secondary effort without hesitation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyril.plisko at mountall.com Sun Oct 19 07:02:17 2008 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Sun, 19 Oct 2008 16:02:17 +0200 Subject: [emerging-platforms-discuss] [osol-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: Message-ID: On Sun, Oct 19, 2008 at 3:35 PM, Mark Martin wrote: > > > On Sun, Oct 19, 2008 at 12:54 AM, Cyril Plisko > wrote: >> >> >> do you have enough hardware documentation to do this ? > > At the moment that is a gap. This was also a gap for other platforms > considered for the PowerPC platform (Sony PS3, Apple PowerMacs), but I > believe our advantage here is that we may have a platform where the vendor > is willing to work with us. Movidis has offered to field technical > questions, and I have a request in to Cavium Networks for more detailed > documentation on the Octeon. I wonder if we will get similar access to > documentation if the Qube is also considered as a target. > Isn't Qube too old to be considered a viable target for this project ? One of the lessons I've learned from the PPC port is to make sure the hardware is readily available and not going to die soon. Otherwise the software will follow the hardware :-( The platform vendor willingness to cooperate is not always enough - with PPC Genesi was as cooperative as one could possibly dream, however the system logic was not their part and Marvell (their chip was there) just couldn't care less. The platform itself looks quite interesting. Are there any other possible _modern_ platform this project can target ? >> >> Who will be the initial project members ? > > For the moment, myself, but I'll certainly welcome other volunteers. I do > plan to reach out to the Linux, NetBSD, and OpenBSD communities for help > from their MIPS porting folks. Very well. -- Regards, Cyril From storycrafter at gmail.com Sun Oct 19 07:07:30 2008 From: storycrafter at gmail.com (Mark Martin) Date: Sun, 19 Oct 2008 09:07:30 -0500 Subject: [emerging-platforms-discuss] [tools-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: <48FAE564.6090806@netsyncro.com> References: <48FAE564.6090806@netsyncro.com> Message-ID: On Sun, Oct 19, 2008 at 2:44 AM, "C. Bergstr?m" wrote: > Mark Martin wrote: > >> I am seeking approval for a project for porting OpenSolaris to the MIPS >> architecture. >> >> Proposal: Provide code changes, tools, documentation, and other necessary >> artifacts for a port of OpenSolaris to the MIPS architecture. Movidis, a >> maker of MIPS based components and systems has expressed interest in support >> of this port, so it is likely that their products will be the initial >> supported platforms -- support for other MIPS based platforms may follow >> suit. The current project goal is to support the MIPS64 architecture, >> although the MIPS32 ISA may also be a possibility. >> Among other deliverables, it is expected that this port will include >> integration of some or all of changes identified in the gccfss project: >> http://www.opensolaris.org/jive/thread.jspa?threadID=24934, and preserved >> here: http://cr.opensolaris.org/~devnull/6515400/< >> http://cr.opensolaris.org/%7Edevnull/6515400/>. There may be additional >> key core kernel changes similar to those identified in the PowerPC port >> project. Some of these changes were necessary for support for a gcc based >> cross compilation tool chain. This cross compiler tool chain is necessary >> for boot strap of the port, but a self-hosting, native gcc tool chain is >> also a goal for the project. >> >> A discussion list and source repository are also requested. >> > It's too bad sun cc source isn't available yet.. I'm addicted to the > quality of some of the code that SS12 and especially SSX is producing > otherwise I'd be 100% 1+.. I've been working on size optimizations which > code possibly pay off in the not too distant future for an embedded > platform. Hence tools-discuss in the distribution list :) I consider it a necessary evil that GCC is in the bootstrap tool-chain and most likely the native build tool-chain as well. That was going to be the fate for PowerPC had it gotten that far. This is also a gap. I believe it is possible to build at least the OpenSolaris ON consolidation bits with GCC at the moment (although I am not certain of which version). GCC 4 compilation is not possible without at least some of those fixes I referenced, so I believe 3.x is required (at least that was the case with the PowerPC port from nv-56). Also, C++ compilation for other consolidations is going to be a sticky issue as the Sun C++ ABI is the preferred and (almost) required C++ ABI according to current ARC requirements. I believe, for the moment, that closing that gap would have to be a follow-on project. I want to see a port coming up to run levels > 1 before I go working on fixing layered software issues. On that note, this brings up other issues such as distribution and testing down the road. I would like to suggest that the scope for this project be to simply bring up the port for recent versions of the ON, SFW, and X consolidations and I would look to the Emerging Platforms Community to assist in creating follow on projects to close distribution, testing, and developer p & p gaps. As items come up that need to be brought for ARC attention, I can at least lead some of those tasks. > > > Thanks > > ./C > -------------- next part -------------- An HTML attachment was scrubbed... URL: From storycrafter at gmail.com Sun Oct 19 07:35:19 2008 From: storycrafter at gmail.com (Mark Martin) Date: Sun, 19 Oct 2008 09:35:19 -0500 Subject: [emerging-platforms-discuss] [osol-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: Message-ID: On Sun, Oct 19, 2008 at 9:02 AM, Cyril Plisko wrote: > Isn't Qube too old to be considered a viable target for this project ? > One of the lessons I've learned from the PPC port is to make sure the > hardware is readily available and not going to die soon. Otherwise the > software will follow the hardware :-( Agreed. This was, honestly, one of the main reasons I reached out to Movidis. > > > The platform vendor willingness to cooperate is not always enough - > with PPC Genesi was as cooperative as one could possibly dream, > however the system logic was not their part and Marvell (their chip > was there) just couldn't care less. Agreed. Since this isn't corporate sponsored, I consider it a risk to complete success that it will rely on external contributions. Regardless I still have energy and optimism. I know that won't be enough, though. > > > The platform itself looks quite interesting. Are there any other > possible _modern_ platform this project can target ? I'm open to ideas. For me, the Movidis x16 platform is interesting because it does not solely target the dedicated network switch/routing market that I so often see MIPS being used in. I think this may also be interesting http://en.wikipedia.org/wiki/Loongson -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyril.plisko at mountall.com Sun Oct 19 07:48:59 2008 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Sun, 19 Oct 2008 16:48:59 +0200 Subject: [emerging-platforms-discuss] [osol-discuss] [tools-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: <48FAE564.6090806@netsyncro.com> Message-ID: On Sun, Oct 19, 2008 at 4:07 PM, Mark Martin wrote: > >> >> It's too bad sun cc source isn't available yet.. I'm addicted to the >> quality of some of the code that SS12 and especially SSX is producing >> otherwise I'd be 100% 1+.. I've been working on size optimizations which >> code possibly pay off in the not too distant future for an embedded >> platform. > > Hence tools-discuss in the distribution list :) I consider it a necessary > evil that GCC is in the bootstrap tool-chain and most likely the native > build tool-chain as well. That was going to be the fate for PowerPC had it > gotten that far. > > This is also a gap. I believe it is possible to build at least the > OpenSolaris ON consolidation bits with GCC at the moment (although I am not > certain of which version). GCC 4 compilation is not possible without at > least some of those fixes I referenced, so I believe 3.x is required (at > least that was the case with the PowerPC port from nv-56). Also, C++ > compilation for other consolidations is going to be a sticky issue as the > Sun C++ ABI is the preferred and (almost) required C++ ABI according to > current ARC requirements. I believe, for the moment, that closing that gap > would have to be a follow-on project. I want to see a port coming up to run > levels > 1 before I go working on fixing layered software issues. Indeed, I wouldn't worry about C++ and what ARC can say until the system boots up to the shell prompt. I am not sure what is the situation with MIPS/ELF target with GCC3, but I'd stick to gcc-3.4.3 (the one that comes with/builds ON) for the starter. Unless, of course, some really pressing reason will force you to go for GCC4. > On that note, this brings up other issues such as distribution and testing > down the road. I would like to suggest that the scope for this project be > to simply bring up the port for recent versions of the ON, SFW, and X > consolidations and I would look to the Emerging Platforms Community to > assist in creating follow on projects to close distribution, testing, and > developer p & p gaps. As items come up that need to be brought for ARC > attention, I can at least lead some of those tasks. May I suggest pushing SFW and X beyond the original scope ? I think you'll have enough problems to solve even with ON itself. OTOH, when the port become self-hosting many things come almost at no price. -- Regards, Cyril From storycrafter at gmail.com Sun Oct 19 08:40:40 2008 From: storycrafter at gmail.com (Mark Martin) Date: Sun, 19 Oct 2008 10:40:40 -0500 Subject: [emerging-platforms-discuss] [osol-discuss] [tools-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: <48FAE564.6090806@netsyncro.com> Message-ID: On Sun, Oct 19, 2008 at 9:48 AM, Cyril Plisko wrote: > On Sun, Oct 19, 2008 at 4:07 PM, Mark Martin > wrote: > > This is also a gap. I believe it is possible to build at least the > > OpenSolaris ON consolidation bits with GCC at the moment (although I am > not > > certain of which version). GCC 4 compilation is not possible without at > > least some of those fixes I referenced, so I believe 3.x is required (at > > least that was the case with the PowerPC port from nv-56). Also, C++ > > compilation for other consolidations is going to be a sticky issue as the > > Sun C++ ABI is the preferred and (almost) required C++ ABI according to > > current ARC requirements. I believe, for the moment, that closing that > gap > > would have to be a follow-on project. I want to see a port coming up to > run > > levels > 1 before I go working on fixing layered software issues. > > > Indeed, I wouldn't worry about C++ and what ARC can say until the > system boots up to the shell prompt. > I am not sure what is the situation with MIPS/ELF target with GCC3, > but I'd stick to gcc-3.4.3 (the one that comes with/builds ON) for the > starter. Unless, of course, some really pressing reason will force you > to go for GCC4. > Other than significantly reduced build times, none at this moment. > > > On that note, this brings up other issues such as distribution and > testing > > down the road. I would like to suggest that the scope for this project > be > > to simply bring up the port for recent versions of the ON, SFW, and X > > consolidations and I would look to the Emerging Platforms Community to > > assist in creating follow on projects to close distribution, testing, and > > developer p & p gaps. As items come up that need to be brought for ARC > > attention, I can at least lead some of those tasks. > > May I suggest pushing SFW and X beyond the original scope ? I think > you'll have enough problems to solve even with ON itself. > OTOH, when the port become self-hosting many things come almost at no > price. Sounds reasonable. Again, I'll look to the EP Community to create follow-on projects. -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnsonnenschein at gmail.com Sun Oct 19 12:07:29 2008 From: johnsonnenschein at gmail.com (John Sonnenschein) Date: Sun, 19 Oct 2008 12:07:29 -0700 Subject: [emerging-platforms-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: <48FAE564.6090806@netsyncro.com> Message-ID: (cutting down on the number of CC:'s) Mark, were you thinking of a MIPS32 or a MIPS64 ( my personal preference would go towards mips64, but I can see arguments for both sides ) -JohnS On 19-Oct-08, at 8:40 AM, Mark Martin wrote: > > > On Sun, Oct 19, 2008 at 9:48 AM, Cyril Plisko > wrote: > On Sun, Oct 19, 2008 at 4:07 PM, Mark Martin > wrote: > > This is also a gap. I believe it is possible to build at least the > > OpenSolaris ON consolidation bits with GCC at the moment (although > I am not > > certain of which version). GCC 4 compilation is not possible > without at > > least some of those fixes I referenced, so I believe 3.x is > required (at > > least that was the case with the PowerPC port from nv-56). Also, C > ++ > > compilation for other consolidations is going to be a sticky issue > as the > > Sun C++ ABI is the preferred and (almost) required C++ ABI > according to > > current ARC requirements. I believe, for the moment, that closing > that gap > > would have to be a follow-on project. I want to see a port coming > up to run > > levels > 1 before I go working on fixing layered software issues. > > > Indeed, I wouldn't worry about C++ and what ARC can say until the > system boots up to the shell prompt. > I am not sure what is the situation with MIPS/ELF target with GCC3, > but I'd stick to gcc-3.4.3 (the one that comes with/builds ON) for the > starter. Unless, of course, some really pressing reason will force you > to go for GCC4. > > Other than significantly reduced build times, none at this moment. > > > > On that note, this brings up other issues such as distribution and > testing > > down the road. I would like to suggest that the scope for this > project be > > to simply bring up the port for recent versions of the ON, SFW, > and X > > consolidations and I would look to the Emerging Platforms > Community to > > assist in creating follow on projects to close distribution, > testing, and > > developer p & p gaps. As items come up that need to be brought > for ARC > > attention, I can at least lead some of those tasks. > > May I suggest pushing SFW and X beyond the original scope ? I think > you'll have enough problems to solve even with ON itself. > OTOH, when the port become self-hosting many things come almost at > no price. > > Sounds reasonable. Again, I'll look to the EP Community to create > follow-on projects. > > _______________________________________________ > emerging-platforms-discuss mailing list > emerging-platforms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/emerging-platforms- > discuss From storycrafter at gmail.com Sun Oct 19 12:34:45 2008 From: storycrafter at gmail.com (Mark Martin) Date: Sun, 19 Oct 2008 14:34:45 -0500 Subject: [emerging-platforms-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: <48FAE564.6090806@netsyncro.com> Message-ID: On Sun, Oct 19, 2008 at 2:07 PM, John Sonnenschein < johnsonnenschein at gmail.com> wrote: > (cutting down on the number of CC:'s) > > Mark, were you thinking of a MIPS32 or a MIPS64 ( my personal preference > would go towards mips64, but I can see arguments for both sides ) MIPS64 would be my preference as well, but I'm not ruling out MIPS32 in the beginning just to get going. I'm also thinking of where Guy S. left off with regards to the PPC port, and some of the VM issues he came across. I'm fairly certain the Octeon processor supports both. -------------- next part -------------- An HTML attachment was scrubbed... URL: From johnsonnenschein at gmail.com Sun Oct 19 15:34:10 2008 From: johnsonnenschein at gmail.com (John Sonnenschein) Date: Sun, 19 Oct 2008 15:34:10 -0700 Subject: [emerging-platforms-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: <48FAE564.6090806@netsyncro.com> Message-ID: <48FBB5E2.9070002@gmail.com> Mark Martin wrote: > > > On Sun, Oct 19, 2008 at 2:07 PM, John Sonnenschein > > wrote: > > (cutting down on the number of CC:'s) > > Mark, were you thinking of a MIPS32 or a MIPS64 ( my personal > preference would go towards mips64, but I can see arguments for > both sides ) > > > MIPS64 would be my preference as well, but I'm not ruling out MIPS32 > in the beginning just to get going. I'm also thinking of where Guy S. > left off with regards to the PPC port, and some of the VM issues he > came across. I'm fairly certain the Octeon processor supports both. > My suggestion would be to pick a target that one of the better emulators supports. That is, take a look at what qemu and gxemul, and the SGI emulator whose name I forget at the moment support and pick from something in that lis ( for example, I'm relatively certain that the O2 simulator works, and can boot IRIX to some degree. ) From cyril.plisko at mountall.com Mon Oct 20 10:10:02 2008 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Mon, 20 Oct 2008 19:10:02 +0200 Subject: [emerging-platforms-discuss] [powerpc-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: <48fcb7e2.xgLnMiWoBiiDWXcC%Joerg.Schilling@fokus.fraunhofer.de> References: <48FAE564.6090806@netsyncro.com> <48fcb7e2.xgLnMiWoBiiDWXcC%Joerg.Schilling@fokus.fraunhofer.de> Message-ID: On Mon, Oct 20, 2008 at 6:54 PM, Joerg Schilling wrote: > "Mark Martin" wrote: > >> On Sun, Oct 19, 2008 at 2:07 PM, John Sonnenschein < >> johnsonnenschein at gmail.com> wrote: >> >> > (cutting down on the number of CC:'s) >> > >> > Mark, were you thinking of a MIPS32 or a MIPS64 ( my personal preference >> > would go towards mips64, but I can see arguments for both sides ) >> >> >> MIPS64 would be my preference as well, but I'm not ruling out MIPS32 in the >> beginning just to get going. I'm also thinking of where Guy S. left off >> with regards to the PPC port, and some of the VM issues he came across. >> I'm fairly certain the Octeon processor supports both. > > I am sure that the embedded devices and WLAN routers use MIPS32 ;-) Right, but bearing in mind memory constraints I wouldn't count on these devices as a target for OpenSolaris for the near future. -- Regards, Cyril From storycrafter at gmail.com Mon Oct 20 19:39:05 2008 From: storycrafter at gmail.com (Mark Martin) Date: Mon, 20 Oct 2008 21:39:05 -0500 Subject: [emerging-platforms-discuss] [osol-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: References: Message-ID: On Mon, Oct 20, 2008 at 8:46 PM, Ignacio Marambio Cat?n wrote: > what about the chinese Loongson processor? > http://en.wikipedia.org/wiki/Loongson > > a notebook running mandriva using that chip seems to be on the way > http://www.gdium.com/description > > and there is some documentation about it in > http://www.loongsondeveloper.com > We could certainly consider that as a candidate platform for initial development, if it ever shows up. As John S. mentioned earlier, I think the very first two high level tasks are: 1) Identify a standard setup using some chosen software emulator, and target initial bootstrapping on that. 2) Get a MIPS cross toolchain working (primarily work in sgs/ld). I did this once before with a Sparc host/PPC target, but Sun Labs had already blazed the trail for x86 as host. MIPS ELF will be a new adventure. I believe #1 brings the benefit that there is no requirement for purchasing new hardware, and it would be more likely to get more contributions. As this is almost certainly going to be powered by individual contributors (likely all external), I think having a low-cost and lightweight development environment would be crucial to the success of this project. I am certain that not having a cheap, available, and well documented PowerPC platform available had a detrimental effect on the continuation of the PowerPC port. I think the situation is a little better with MIPS, but time will tell. We have to consider the availability of drivers as well. This port to MIPS could very well entail writing new chipset drivers. I think there are issues with the current available lot of software emulators, but we can discuss details of that on the new mailing list if we make it that far. I will have access to a Movidis x16 NAP box soon, and would be happy to provide access to that for contributors as well. Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From storycrafter at gmail.com Fri Oct 24 07:20:01 2008 From: storycrafter at gmail.com (Mark Martin) Date: Fri, 24 Oct 2008 09:20:01 -0500 Subject: [emerging-platforms-discuss] [powerpc-discuss] [osol-discuss] Project Proposal -- Port to MIPS architecture In-Reply-To: <490104E8.1010409@sun.com> References: <490104E8.1010409@sun.com> Message-ID: On Thu, Oct 23, 2008 at 6:12 PM, William Kucharski < William.Kucharski at sun.com> wrote: > So if there is sufficient interest in a MIPS project, I would be happy to > get the ball rolling by formally proposing the creation of such a project > under the Emerging Platforms CG. I thought we had enough votes as it was: Martin B., John S., John G., and Cyril P. all registered +1 votes. Of course, I don't know if those were all from the Emerging Platforms CG, so thank you for picking up formal adoption of this. > > > I'd just need to know the charter and who wants to be the project leads. I had trouble finding a project charter template, so I stole a rare example from John P. (thanks John!). Besides myself, nobody else has stepped forward, so I would certainly welcome volunteers. ===== OpenSolaris on MIPS Project ===== Name OpenSolaris on MIPS Architecture alias: mips-discuss at os.o Synopsis A project to port the OpenSolaris operating system to the MIPS architecture and related platforms. Sponsor Emerging Platforms CG Description Charter: To develop a port of OpenSolaris suitable for running on MIPS based platforms. Primary efforts will be focused on identifying a development environment and target platforms, creating changes to the ON consolidation to support MIPS32 and possibly MIPS64 builds, and creating recommendations for follow on projects to produce a distribution as well as other necessary projects. Related Projects OpenSolaris for PowerPC port. Expected deliverables - Provide a cross linking build environment - Identify candidate hardware and software emulation platform(s) targets. One goal here is to provide a simple development environment that is easy to obtain and maintain. - Build of portions (or all) of the ON consolidation and provide kernel and userland portions to a minimal identified run state - Investigate and port tools used in the OpenSolaris PowerPC port project ("Polaris"). Context ON/Nevada OpenSolaris Development Process http://www.opensolaris.org/os/community/on/os_dev_process/ Preliminary discussions regarding project proposal http://mail.opensolaris.org/pipermail/emerging-platforms-discuss/2008-October/000002.html http://mail.opensolaris.org/pipermail/powerpc-discuss/2008-October/002532.html ===== end ===== -------------- next part -------------- An HTML attachment was scrubbed... URL: