From cyril.plisko at mountall.com Mon Jun 8 08:59:53 2009 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Mon, 8 Jun 2009 18:59:53 +0300 Subject: [emerging-platforms-discuss] [osol-announce] First release for ARM platform In-Reply-To: <4A2CC92D.5080204@sun.com> References: <4A2CC92D.5080204@sun.com> Message-ID: On Mon, Jun 8, 2009 at 11:17 AM, Koji Uno wrote: > The first release for ARM platform is now available. That's so cool ! Great work, folks ! > Please visit at http://www.opensolaris.org/os/project/osarm > and enjoy OpenSolaris on ARM platform. The only thing that leaves a bitter taste in the mouth is that this project appeared out of the blue. Oh, well, I guess I am just a perfectionist... -- Regards, Cyril From raysonlogin at gmail.com Wed Jun 10 19:41:26 2009 From: raysonlogin at gmail.com (Rayson Ho) Date: Wed, 10 Jun 2009 21:41:26 -0500 Subject: [emerging-platforms-discuss] OpenSolaris on MIPS Message-ID: <73a01bf20906101941y5be789day849ed21424612e2a@mail.gmail.com> I tried to google for "OpenSolaris on MIPS Project" and found that it's a dead link ( http://opensolaris.org/os/project/mips/ ). Is anyone still working on the project?? Rayson From Jim.Grisanzio at Sun.COM Wed Jun 10 22:34:15 2009 From: Jim.Grisanzio at Sun.COM (Jim Grisanzio) Date: Thu, 11 Jun 2009 14:34:15 +0900 Subject: [emerging-platforms-discuss] OpenSolaris on MIPS In-Reply-To: <73a01bf20906101941y5be789day849ed21424612e2a@mail.gmail.com> References: <73a01bf20906101941y5be789day849ed21424612e2a@mail.gmail.com> Message-ID: <4A309757.6020409@sun.com> On 06/11/09 11:41, Rayson Ho wrote: > I tried to google for "OpenSolaris on MIPS Project" and found that > it's a dead link ( http://opensolaris.org/os/project/mips/ ). Is > anyone still working on the project?? > There was discussion about MIPS and it was approved as a project but it has not opened yet. When it does, however, that's the url that will be used. Jim -- opensolaris.org transition: http://opensolaris.org/os/community/web/ From raysonlogin at gmail.com Wed Jun 10 23:10:36 2009 From: raysonlogin at gmail.com (Rayson Ho) Date: Thu, 11 Jun 2009 01:10:36 -0500 Subject: [emerging-platforms-discuss] OpenSolaris on MIPS In-Reply-To: <4A309757.6020409@sun.com> References: <73a01bf20906101941y5be789day849ed21424612e2a@mail.gmail.com> <4A309757.6020409@sun.com> Message-ID: <73a01bf20906102310g16aa1b27qe2448dc29d70e7be@mail.gmail.com> Thanks for the reply, Jim. So what's blocking the project from starting?? Rayson On Thu, Jun 11, 2009 at 12:34 AM, Jim Grisanzio wrote: > There was discussion about MIPS and it was approved as a project but it has > not opened yet. When it does, however, that's the url that will be used. > > Jim > > -- > opensolaris.org transition: http://opensolaris.org/os/community/web/ > > > From Jim.Grisanzio at Sun.COM Wed Jun 10 23:24:44 2009 From: Jim.Grisanzio at Sun.COM (Jim Grisanzio) Date: Thu, 11 Jun 2009 15:24:44 +0900 Subject: [emerging-platforms-discuss] OpenSolaris on MIPS In-Reply-To: <73a01bf20906102310g16aa1b27qe2448dc29d70e7be@mail.gmail.com> References: <73a01bf20906101941y5be789day849ed21424612e2a@mail.gmail.com> <4A309757.6020409@sun.com> <73a01bf20906102310g16aa1b27qe2448dc29d70e7be@mail.gmail.com> Message-ID: <4A30A32C.5080007@sun.com> Rayson Ho wrote: > Thanks for the reply, Jim. > > So what's blocking the project from starting?? > oh, I'm not sure anything is blocking, per say. It's just common for projects to be discussed and approved and opened at various times later on. As part of the website transition I am checking the status of 40 unopened projects on the site, so that's how I tripped over that one. This is the right list to monitor for it, though. :) Jim -- opensolaris.org transition: http://opensolaris.org/os/community/web/ From storycrafter at gmail.com Thu Jun 11 08:52:40 2009 From: storycrafter at gmail.com (Mark Martin) Date: Thu, 11 Jun 2009 10:52:40 -0500 Subject: [emerging-platforms-discuss] OpenSolaris on MIPS In-Reply-To: <4A30A32C.5080007@sun.com> References: <73a01bf20906101941y5be789day849ed21424612e2a@mail.gmail.com> <4A309757.6020409@sun.com> <73a01bf20906102310g16aa1b27qe2448dc29d70e7be@mail.gmail.com> <4A30A32C.5080007@sun.com> Message-ID: <4A312848.3070308@gmail.com> Jim Grisanzio wrote: > Rayson Ho wrote: >> Thanks for the reply, Jim. >> >> So what's blocking the project from starting?? >> > oh, I'm not sure anything is blocking, per say. It's just common for > projects to be discussed and approved and opened at various times > later on. As part of the website transition I am checking the status > of 40 unopened projects on the site, so that's how I tripped over that > one. This is the right list to monitor for it, though. :) > > Jim Jim, thanks for clarifying the web side of things. Yes, the project is in the _on_ state. The velocity is slow -- most likely because this is an endeavor-of-love for most of us and there are no corporate dollars financing high priority work. Blame me for the lack of anything useful to see on the official project page. On the good side, the recent stealth+outside-of-the-community ARM release opens a lot of doors: - It proves a lot can be done in a little time - It proves for me that QEMU is the right way to get started with a bootstrap - It highlights that the only serious long term impediment to a truly community hosted distribution or port is the eternally closed "libc_i18n.a" - It highlights that the sun cross linker works Needed: QEMU/Mips (preferably with hardware found on the Movidis Revolution x16) GCC cross compile with Sun ld Either a) a libc_i18n.a replacement or b) an inside route to compile a mips version of libc_i18n.a Knowledge of MIPS64 Knowledge of uts Knowledge of newboot Knowledge of Uboot Access to some MIPS hardware (Movidis.com, lemote.com, olph.gdium.com) A way to cover the gap created by lack of drivers on target platforms (Movidis is covered....others????) I've been doing a little bit of work on QEMU and the cross compile toolchain and researching like mad on all of the techologies involved. Where can you help? (BTW, I recently acquired a QNAP for playing with the ARM port -- I'm going to try to get it running on there some weekend soon) From john.dehart at parker.com Fri Jun 12 06:37:31 2009 From: john.dehart at parker.com (John DeHart) Date: Fri, 12 Jun 2009 06:37:31 PDT Subject: [emerging-platforms-discuss] SUNWglrt prerequisite Message-ID: <18727534.321244813881810.JavaMail.Twebapp@sf-app1> Folks, I would like to run CATIA on open solaris. During the installation i receive the error --> SunOS PREREQS: Package SUNWglrt must be installed. So what to do here? I am willing to spend time working the situation out. If we could get this running it would be big boon for the open solaris platform amongst CATIA users. -- This message posted from opensolaris.org From storycrafter at gmail.com Mon Jun 15 08:29:36 2009 From: storycrafter at gmail.com (Mark Martin) Date: Mon, 15 Jun 2009 10:29:36 -0500 Subject: [emerging-platforms-discuss] MIPS Project port sponsorship Message-ID: <4A3668E0.8000802@gmail.com> As a matter of housekeeping, I'd appreciate it if the emerging platforms community could indicate their sponsorship of the MIPS porting project. The initial project charter and request for endorsement were here: http://mail.opensolaris.org/pipermail/emerging-platforms-discuss/2008-October/000001.html Thanks, folks. From raysonlogin at gmail.com Mon Jun 15 10:05:38 2009 From: raysonlogin at gmail.com (Rayson Ho) Date: Mon, 15 Jun 2009 12:05:38 -0500 Subject: [emerging-platforms-discuss] OpenSolaris on MIPS In-Reply-To: <4A312848.3070308@gmail.com> References: <73a01bf20906101941y5be789day849ed21424612e2a@mail.gmail.com> <4A309757.6020409@sun.com> <73a01bf20906102310g16aa1b27qe2448dc29d70e7be@mail.gmail.com> <4A30A32C.5080007@sun.com> <4A312848.3070308@gmail.com> Message-ID: <73a01bf20906151005o331256b9n56ba082acbae3a07@mail.gmail.com> On Thu, Jun 11, 2009 at 10:52 AM, Mark Martin wrote: > Jim, thanks for clarifying the web side of things. Finally, the project page is up!! > On the good side, the recent stealth+outside-of-the-community ARM release > opens a lot of doors: > - It proves a lot can be done in a little time > - It proves for me that QEMU is the right way to get started with a > bootstrap > - It highlights that the only serious long term impediment to a truly > community hosted distribution or port is the eternally closed "libc_i18n.a" > - It highlights that the sun cross linker works Agreed! I believe there are a lot of similarities between the ARM port and the MIPS port, so earlier today I asked for some detail info about the ARM port on the osarm-dev list. > Needed: > QEMU/Mips (preferably with hardware found on the Movidis Revolution x16) > GCC cross compile with Sun ld > Either a) a libc_i18n.a replacement or b) an inside route to compile a mips > version of libc_i18n.a > Knowledge of MIPS64 > Knowledge of uts > Knowledge of newboot > Knowledge of Uboot > Access to some MIPS hardware (Movidis.com, lemote.com, olph.gdium.com) > > A way to cover the gap created by lack of drivers on target platforms > (Movidis is covered....others????) Can we first target the Loongson platform?? I think with the availability of the emulator, and with a number of remote development machines (they are running Linux, but still good for testing some code), it is a better environment than other MIPS hardware. http://groups.google.com/group/archlinux-for-loongson/web/loongson Another advantage (IMO) is that it's the fastest MIPS-based nettop & netbook, and the cost is low (starting from USD 260). > I've been doing a little bit of work on QEMU and the cross compile toolchain > and researching like mad on all of the techologies involved. Where can you > help? I would like to see the whole changeset of the ARM port (minus CZFS) first, then we will get an idea what changes are needed. Rayson > > (BTW, I recently acquired a QNAP for playing with the ARM port -- I'm going > to try to get it running on there some weekend soon) > From William.Kucharski at Sun.COM Mon Jun 15 12:01:45 2009 From: William.Kucharski at Sun.COM (William Kucharski) Date: Mon, 15 Jun 2009 13:01:45 -0600 Subject: [emerging-platforms-discuss] MIPS Project port sponsorship In-Reply-To: <4A3668E0.8000802@gmail.com> References: <4A3668E0.8000802@gmail.com> Message-ID: <4A369A99.1010903@sun.com> Mark Martin wrote: > > As a matter of housekeeping, I'd appreciate it if the emerging platforms > community could indicate their sponsorship of the MIPS porting project. > The initial project charter and request for endorsement were here: > http://mail.opensolaris.org/pipermail/emerging-platforms-discuss/2008-October/000001.html Done! William Kucharski From storycrafter at gmail.com Tue Jun 16 11:54:01 2009 From: storycrafter at gmail.com (Mark Martin) Date: Tue, 16 Jun 2009 13:54:01 -0500 Subject: [emerging-platforms-discuss] Marvell 88F6281 drivers? Message-ID: <4A37EA49.9020504@gmail.com> Now that the cat is out of the bag on the ARM port, it's time to see what hardware platforms we can try running on. Is anyone working on, or interested in working on, drivers for some of the prevalent ARM platforms? I'm noting that 88F6281 fairly commonly found and inexpensive (QNAP, SheevaPlug, etc). QNAP has expressed interest in supporting a porting project, so now would be a good time to think about making sure we have core driver support. It'd be nice if we knew what might be in the pipeline from this Sun/NEC collaboration (hint hint). From cyril.plisko at mountall.com Tue Jun 16 12:08:27 2009 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Tue, 16 Jun 2009 22:08:27 +0300 Subject: [emerging-platforms-discuss] [driver-discuss] Marvell 88F6281 drivers? In-Reply-To: References: <4A37EA49.9020504@gmail.com> Message-ID: On Tue, Jun 16, 2009 at 10:05 PM, Jason King wrote: > On Tue, Jun 16, 2009 at 1:54 PM, Mark Martin wrote: >> Now that the cat is out of the bag on the ARM port, it's time to see what >> hardware platforms we can try running on. ?Is anyone working on, or >> interested in working on, drivers for some of the prevalent ARM platforms? >> ?I'm noting that 88F6281 fairly commonly found and inexpensive (QNAP, >> SheevaPlug, etc). ?QNAP has expressed interest in supporting a porting >> project, so now would be a good time to think about making sure we have core >> driver support. ?It'd be nice if we knew what might be in the pipeline from >> this Sun/NEC collaboration (hint hint). > > The question is, are the companies involved willing to release the > needed specs (or are they already available online)? ?While we could > probably port any equivalent drivers from one of the BSD variants > (where those drivers exist), having the specs would be better. http://www.marvell.com/files/products/embedded_processors/kirkwood/HW_88F6281_OpenSource.pdf 140 pages worth of hardware manual. Not sure whether it is enough or not though. I do not have the actual hardware... > _______________________________________________ > driver-discuss mailing list > driver-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/driver-discuss > -- Regards, Cyril From storycrafter at gmail.com Tue Jun 16 12:12:45 2009 From: storycrafter at gmail.com (Mark Martin) Date: Tue, 16 Jun 2009 14:12:45 -0500 Subject: [emerging-platforms-discuss] [driver-discuss] Marvell 88F6281 drivers? In-Reply-To: References: <4A37EA49.9020504@gmail.com> Message-ID: <4A37EEAD.60506@gmail.com> Cyril Plisko wrote: > On Tue, Jun 16, 2009 at 10:05 PM, Jason King wrote: > >> On Tue, Jun 16, 2009 at 1:54 PM, Mark Martin wrote: >> >>> Now that the cat is out of the bag on the ARM port, it's time to see what >>> hardware platforms we can try running on. Is anyone working on, or >>> interested in working on, drivers for some of the prevalent ARM platforms? >>> I'm noting that 88F6281 fairly commonly found and inexpensive (QNAP, >>> SheevaPlug, etc). QNAP has expressed interest in supporting a porting >>> project, so now would be a good time to think about making sure we have core >>> driver support. It'd be nice if we knew what might be in the pipeline from >>> this Sun/NEC collaboration (hint hint). >>> >> The question is, are the companies involved willing to release the >> needed specs (or are they already available online)? While we could >> probably port any equivalent drivers from one of the BSD variants >> (where those drivers exist), having the specs would be better. >> > > http://www.marvell.com/files/products/embedded_processors/kirkwood/HW_88F6281_OpenSource.pdf > > 140 pages worth of hardware manual. Not sure whether it is enough or > not though. I do not have the actual hardware... > > http://www.globalscaletechnologies.com/p-22-sheevaplug-dev-kit.aspx http://www.qnap.com/pro_detail_hardware.asp?p_id=122 I'm in contact with Marvell and have applied for their "extranet". I'll pass along more details on detailed spec availability for these processors as I come across it. From cyril.plisko at mountall.com Tue Jun 16 13:24:41 2009 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Tue, 16 Jun 2009 23:24:41 +0300 Subject: [emerging-platforms-discuss] [driver-discuss] Marvell 88F6281 drivers? In-Reply-To: <4A37EEAD.60506@gmail.com> References: <4A37EA49.9020504@gmail.com> <4A37EEAD.60506@gmail.com> Message-ID: > > http://www.globalscaletechnologies.com/p-22-sheevaplug-dev-kit.aspx > http://www.qnap.com/pro_detail_hardware.asp?p_id=122 > > I'm in contact with Marvell and have applied for their "extranet". ?I'll > pass along more details on detailed spec availability for these processors > as I come across it. > I have pretty bad previous experience with Marvell. They demonstrated exactly zero willingness to cooperate. Hope your experience will be better. -- Regards, Cyril From storycrafter at gmail.com Tue Jun 16 13:28:09 2009 From: storycrafter at gmail.com (Mark Martin) Date: Tue, 16 Jun 2009 15:28:09 -0500 Subject: [emerging-platforms-discuss] [driver-discuss] Marvell 88F6281 drivers? In-Reply-To: References: <4A37EA49.9020504@gmail.com> <4A37EEAD.60506@gmail.com> Message-ID: <4A380059.4060500@gmail.com> Cyril Plisko wrote: >> http://www.globalscaletechnologies.com/p-22-sheevaplug-dev-kit.aspx >> http://www.qnap.com/pro_detail_hardware.asp?p_id=122 >> >> I'm in contact with Marvell and have applied for their "extranet". I'll >> pass along more details on detailed spec availability for these processors >> as I come across it. >> >> > > I have pretty bad previous experience with Marvell. They demonstrated > exactly zero willingness to cooperate. Hope your experience will be > better. > > > If all else fails, Linux has this platform well covered. Not that it's ideal or anything, but we could always create 2 teams. . . . From cyril.plisko at mountall.com Tue Jun 16 13:29:49 2009 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Tue, 16 Jun 2009 23:29:49 +0300 Subject: [emerging-platforms-discuss] [driver-discuss] Marvell 88F6281 drivers? In-Reply-To: References: <4A37EA49.9020504@gmail.com> Message-ID: On Tue, Jun 16, 2009 at 10:17 PM, Jason King wrote: > On Tue, Jun 16, 2009 at 2:08 PM, Cyril Plisko wrote: >> On Tue, Jun 16, 2009 at 10:05 PM, Jason King wrote: >>> On Tue, Jun 16, 2009 at 1:54 PM, Mark Martin wrote: >>>> Now that the cat is out of the bag on the ARM port, it's time to see what >>>> hardware platforms we can try running on. ?Is anyone working on, or >>>> interested in working on, drivers for some of the prevalent ARM platforms? >>>> ?I'm noting that 88F6281 fairly commonly found and inexpensive (QNAP, >>>> SheevaPlug, etc). ?QNAP has expressed interest in supporting a porting >>>> project, so now would be a good time to think about making sure we have core >>>> driver support. ?It'd be nice if we knew what might be in the pipeline from >>>> this Sun/NEC collaboration (hint hint). >>> >>> The question is, are the companies involved willing to release the >>> needed specs (or are they already available online)? ?While we could >>> probably port any equivalent drivers from one of the BSD variants >>> (where those drivers exist), having the specs would be better. >> >> http://www.marvell.com/files/products/embedded_processors/kirkwood/HW_88F6281_OpenSource.pdf >> >> 140 pages worth of hardware manual. Not sure whether it is enough or >> not though. I do not have the actual hardware... > > It looks like that'd be more useful for someone designing a MB to put > the chip in than those looking to provide OS support. ?It doesn't seem > to have any details on (for example): programming the two gige > interfaces (I'd be looking for things like register descriptions, > descriptor layouts, etc.), the crypto engine, sata controller, etc. > http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf Any better ? -- Regards, Cyril From cyril.plisko at mountall.com Tue Jun 16 13:31:37 2009 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Tue, 16 Jun 2009 23:31:37 +0300 Subject: [emerging-platforms-discuss] [driver-discuss] Marvell 88F6281 drivers? In-Reply-To: <4A380059.4060500@gmail.com> References: <4A37EA49.9020504@gmail.com> <4A37EEAD.60506@gmail.com> <4A380059.4060500@gmail.com> Message-ID: On Tue, Jun 16, 2009 at 11:28 PM, Mark Martin wrote: > Cyril Plisko wrote: >>> >>> http://www.globalscaletechnologies.com/p-22-sheevaplug-dev-kit.aspx >>> http://www.qnap.com/pro_detail_hardware.asp?p_id=122 >>> >>> I'm in contact with Marvell and have applied for their "extranet". ?I'll >>> pass along more details on detailed spec availability for these >>> processors >>> as I come across it. >>> >>> >> >> I have pretty bad previous experience with Marvell. They demonstrated >> exactly zero willingness to cooperate. Hope your experience will be >> better. >> >> >> > > If all else fails, Linux has this platform well covered. ?Not that it's > ideal or anything, but we could always create 2 teams. . . . > Yup. Who wants to be on the read only team ? Hm...., I thought so... :) -- Regards, Cyril From jason at ansipunx.net Tue Jun 16 13:39:43 2009 From: jason at ansipunx.net (Jason King) Date: Tue, 16 Jun 2009 15:39:43 -0500 Subject: [emerging-platforms-discuss] [driver-discuss] Marvell 88F6281 drivers? In-Reply-To: References: <4A37EA49.9020504@gmail.com> Message-ID: On Tue, Jun 16, 2009 at 3:29 PM, Cyril Plisko wrote: > On Tue, Jun 16, 2009 at 10:17 PM, Jason King wrote: >> On Tue, Jun 16, 2009 at 2:08 PM, Cyril Plisko wrote: >>> On Tue, Jun 16, 2009 at 10:05 PM, Jason King wrote: >>>> On Tue, Jun 16, 2009 at 1:54 PM, Mark Martin wrote: >>>>> Now that the cat is out of the bag on the ARM port, it's time to see what >>>>> hardware platforms we can try running on. ?Is anyone working on, or >>>>> interested in working on, drivers for some of the prevalent ARM platforms? >>>>> ?I'm noting that 88F6281 fairly commonly found and inexpensive (QNAP, >>>>> SheevaPlug, etc). ?QNAP has expressed interest in supporting a porting >>>>> project, so now would be a good time to think about making sure we have core >>>>> driver support. ?It'd be nice if we knew what might be in the pipeline from >>>>> this Sun/NEC collaboration (hint hint). >>>> >>>> The question is, are the companies involved willing to release the >>>> needed specs (or are they already available online)? ?While we could >>>> probably port any equivalent drivers from one of the BSD variants >>>> (where those drivers exist), having the specs would be better. >>> >>> http://www.marvell.com/files/products/embedded_processors/kirkwood/HW_88F6281_OpenSource.pdf >>> >>> 140 pages worth of hardware manual. Not sure whether it is enough or >>> not though. I do not have the actual hardware... >> >> It looks like that'd be more useful for someone designing a MB to put >> the chip in than those looking to provide OS support. ?It doesn't seem >> to have any details on (for example): programming the two gige >> interfaces (I'd be looking for things like register descriptions, >> descriptor layouts, etc.), the crypto engine, sata controller, etc. >> > > http://www.marvell.com/files/products/embedded_processors/kirkwood/FS_88F6180_9x_6281_OpenSource.pdf > > Any better ? For at least some of the things, yes (I can't comment on all the components as I haven't messed with every sort of driver). From cyril.plisko at mountall.com Wed Jun 17 04:47:04 2009 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Wed, 17 Jun 2009 14:47:04 +0300 Subject: [emerging-platforms-discuss] [driver-discuss] Marvell 88F6281 drivers? In-Reply-To: <4A38C371.4010409@Sun.COM> References: <4A37EA49.9020504@gmail.com> <4A38C371.4010409@Sun.COM> Message-ID: On Wed, Jun 17, 2009 at 1:20 PM, Darren Kenny wrote: > I can't confirm whether the device you mention is definitely supported or not, > but I tend to prefer the myk driver from : > > ? ? ? ?http://homepage2.nifty.com/mrym3/taiyodo/eng/ > > It can be built with GLD3 support, which works well for me on my MacBook Pro - > usually better than Marvell's own supplied driver - if nothing else it might be > useful as a starting point... > 88F6281 isn't an ethernet controller - it is a complete SoC device, based on ARM core, which happen to have an ethernet controller among other things. -- Regards, Cyril From storycrafter at gmail.com Thu Jun 18 09:23:34 2009 From: storycrafter at gmail.com (Mark Martin) Date: Thu, 18 Jun 2009 11:23:34 -0500 Subject: [emerging-platforms-discuss] [osarm-dev] changeset for the ARM port In-Reply-To: <4A3A0003.2010908@sun.com> References: <73a01bf20906150831x5242343bv427bc13407160273@mail.gmail.com> <4A3998C9.7040402@sun.com> <4A3A0003.2010908@sun.com> Message-ID: <4A3A6A06.9010409@gmail.com> Koji Uno wrote: > Hi, > > The difference is who build binary. > > If Sun builds binary, all stacks of toolchain need to > be sent to Sun. This would be good news if and when we get to that point. It's less than ideal, of course, but good to know it wouldn't be a show stopper. > > If MIPS team builds binary, MIPS team need to sign the > contract. Can we get some rough idea of what this contract is? Is it simply an NDA, or is there more to it than that? I don't think this is a very appealing option, but again, good to know it might help remove a roadblock. As near as I can tell, the only closed bin we're actually talking about is lib_i18n. If that's true, I see the following 3 possibilities: 1) Have a Sun resource build it -- ship them a working toolchain and hope they have the time 2) Have someone commit to an NDA and build it -- possibly making it difficult for them to work in other areas of the project (or even other projects) 3) Wait for http://www.opensolaris.org/os/project/emancipation/tasks/libc_i18n/ to finish. From cyril.plisko at mountall.com Fri Jun 19 13:42:12 2009 From: cyril.plisko at mountall.com (Cyril Plisko) Date: Fri, 19 Jun 2009 23:42:12 +0300 Subject: [emerging-platforms-discuss] Endorsement of ARM port project Message-ID: Hello ! I see that ARM port project is endorsed by Emerging Platform community. Did I miss the discussion on endorsing this project and the vote itself ? -- Regards, Cyril From Jim.Grisanzio at Sun.COM Tue Jun 23 23:21:41 2009 From: Jim.Grisanzio at Sun.COM (Jim Grisanzio) Date: Wed, 24 Jun 2009 15:21:41 +0900 Subject: [emerging-platforms-discuss] [Fwd: Re: [facilitation-discuss] Unendorsed Projects: Need Community <-> Project Mappings] Message-ID: <4A41C5F5.7070201@sun.com> hey, guys. Is busybox an emerging platforms project? If so, can you endorse it? Jim -------- Original Message -------- Subject: Re: [facilitation-discuss] Unendorsed Projects: Need Community <-> Project Mappings Date: Mon, 22 Jun 2009 08:31:31 -0700 From: Garrett D'Amore To: Jim Grisanzio CC: facilitation-discuss at opensolaris.org, Project Set-Up Jim Grisanzio wrote: > hey ... > > Ok, we've got the list of 100+ unendorsed projects down to these 15 in > the last two weeks or so. If there are any Facilitators on this list > whose CG's are responsible for these projects, can you please endorse > them by clicking on "Endorse Projects" in the Community Editor box on > the front page of the endorsing Community and check the right project > in the list? > > Unendorsed Projects: > 3. http://opensolaris.org/os/project/busybox/ This should probably be one for the Emerging Platforms community.