>> I don't think it'd make sense to have such a board specialized for MorphOS, whatever
>> that should mean in a technical sense (maybe using only components that MorphOS
>> has already drivers for?).

> A new board should be able to use the components that MorphOS has already drivers
> for... This is a case, yes.

I was more referring to the on-board components, not components the board could use via expansion slots (and which I don't consider being part of the actual board).

> some more modern hardware should be added to this driver list.

A new board for MorphOS (and other niche operating systems) would most likely use some highly integrated SoC, so these new MorphOS drivers would have to include drivers for the SoC's on-chip controllers.

> it could done and could be done cheap. I know that lots of work and money are needed
> for MorphOS to jump on this train

I don't understand. Aren't "cheap" and "lots of money" mutually exclusive?

> No one said no to more operating systems that would expand a user base

In my opinion, a "board specialized for MorphOS" (you didn't answer yet what that means technically) wouldn't have any advantage over a board specialized for no particular OS. What's important is that the on-board components and the controllers integrated therein are publicly documented so driver development for any OS wouldn't have to resort to reverse engineering or similar measures.

> MorphOS should be a priority, lime it was on Pegasos.

bplan didn't prioritize MorphOS for the Pegasos. Linux had the same priority and was on the Pegasos even before MorphOS:

http://www.bplan-gmbh.de/first-pegasos-hardware.html
http://www.bplan-gmbh.de/pegasos-meets-morphos.html