Welcome, Guest. Please login or register.

Author Topic: Open Hardware Architecture  (Read 2232 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Cymric

  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 1031
    • Show all replies
Re: Open Hardware Architecture
« on: February 13, 2004, 03:23:50 PM »
If I understand correctly you want to create a standardised abstraction layer ('OPA') for any PowerPC-based computer platform, the rationale being that such hardware offers a consistent interface to operating systems. The latter can then pick and choose what functions of the interface it will use or build upon. And, since all compliant OSs just see one type of hardware (namely OPA), coding would become more efficient, faster, and so forth. Barring in mind that I have no real experience with CHRP and do not even own a PowerPC-based system... My first gut reaction was 'why??!'

Do you expect such a diversity of PowerPC-based systems that such a standard is necessary?
Do you expect that all OSs you mention will be made OPA-compliant, and if so, in what time frame and by whom?
How do you plan on defining the standard? (I'm thinking W3C here, which according to many vendors is so slow that companies implement their own extensions and more or less get them standardised after the entire world is using them 'illegally'!)
Is there a solid reason why an OS designed for, say, a mobile phone, could or should be run on, say, a fully-equipped PC running Linux, or vice versa? (Think Windows[0-9]+ vs. WindowsCE.)
Is there even sufficient common ground between all types of hardware to warrant such a single interface?

Basically, I'm trying to figure out the answer to the age-old question: if you can do something, should you do it?
Some people say that cats are sneaky, evil and cruel. True, and they have many other fine qualities as well.