RFC: Obsoleting or32
markku.puro at insta.fi
Mon Apr 25 08:58:50 UTC 2005
OpenRISC1000/1200 is quite active.
There is also "OpenRISC 1000 RTEMS"
BTW: They have weekly builds for GNU Toolchain and OS ports???
"The OpenRISC automated testing system (ATS) is, at present,
a single machine which weekly builds OpenRISC GNU Toolchain and
OS ports and reports building problems to the developers."
> -----Original Message-----
> From: Ray [mailto:xr at trasin.net]
> Sent: 25. huhtikuuta 2005 7:16
> To: joel.sherrill at OARcorp.com; Ralf Corsepius
> Cc: Karel Gardas; RTEMS Users
> Subject: Re: Re: RFC: Obsoleting or32
> Joel Sherrill:
> http://www.opencores.org/ is Still OK. See the following:
> opencores.org yesterday lost one hard disk, so this was the
> main reason why services were down. The services are now
> mainly up, but problems may occur because the system was
> restored from backup from Sunday, 17th April.
> >Ralf Corsepius wrote:
> >> On Mon, 2005-04-18 at 15:56 +0200, Karel Gardas wrote:
> >>>On Mon, 18 Apr 2005, Joel Sherrill <joel at OARcorp.com> wrote:
> >>>>>Therefore, unless somebody objects by Sat, Apr. 23, 06:00 CEST
> >>>>>(04:00 GMT - ca. one week from now), I will go ahead and
> remove the
> >>>>>or32 from RTEMS source-tree.
> >>>>www.opencores.org is definitely down. I don't know how
> long it has
> >>>>been down.
> >>>FYI: I've seen this running around January this year.
> >> What are you referring to their site or the RTEMS or32 port?
> >> There site currently comes up with a page talking about "technical
> >> problems, hope to be back soon".
> >> Wrt. the or32 port: IMO, the minimum requirement for a
> port to stay
> >> in RTEMS official source tree is to have a functional toolchain,
> >> otherwise it is impossible to maintain these sources.
> >Agreed. And since the OR32 is an open source processor, if
> the source
> >code is unavailable or unsupported, it is the equivalent of the
> >manufacturer killing the CPU.
More information about the users