Linked by Eugenia Loli on Wed 28th Jan 2004 19:24 UTC
Morphos A new product arises from Genesi: The Open Desktop Workstation is based upon the Genesi Pegasos, a CHRP based motherboard. Integrating selected Open Firmware and running multiple (15+) operating systems, the Workstation is an extremely efficient, very expandable hardware solution for personal and business computer requirements. Both IBM and Motorola feature the new product in their pages.
Permalink for comment
To read all comments associated with this story, please click here.
Good Idea!
by bbrv on Wed 28th Jan 2004 22:33 UTC

Hi XBe, this is a good idea (releaseing specs) and something we have been thinking about. In fact, we registered and .org earlier today.

The notion we have is an Open Hardware/Software Architecture Reference or O.P.A. (Open Power Architecture) to provide a flexible and scalable hardware abstraction layer for PowerPC driven devices. The design would cover a wide range of devices, ranging from Smart Phones to SMP server blades. As a comprehensively defined interface between hardware and software, O.P.A. will integrate all facets of a PowerPC implementation. Thus, O.P.A. - compliant base hardware will run all O.P.A. - compliant software and activate all O.P.A. - compliant peripherals. O.P.A. - complaint operating systems would include LINUX, the BSD family, QNX, VxWorks, and others like your favorite, OpenBeOS (time to call Michael Phipps again!).

We would offer the Pegasos as a reference platform, as well as a Firmware and OS reference as well. We might even tie all this into a Foundation and go out with a open license program from there. We like the idea of the Foundation being able to give away complete systems to causes that need them. It could be the only way for us to get the Open Community behind the platform and to get the hardware out there far enough to really make a difference, not to mention an endowment or two to make it happen.

Clearly, hardware vendors no longer would need to develop or license multiple implementation packages to enable multiple systems. Supporting one O.P.A. system means supporting every other O.P.A. system, both at the hardware and software levels. Use of O.P.A. will bring
down system development time and cost while speeding up time to market. OS vendors will be able to multiple support systems at release time by providing just one O.P.A. implementation.

An O.P.A. system would consist of the following elements:


In the definition of O.P.A., firmware is treated as a subclass of hardware element. All pieces used to build the O.P.A. interface are built out from open standards and are certified free of any patents and non-public
licenses. Any intellectual Property created outside of known and freely available standards (like PCI, IEEE1275, etc.) will be secured in the name of and then publicly sub-licensed to the O.P.A. community.

Still ideas at this point, but we are seriously thinking about them.