If I were Genesi, I'd consider this a very important problem to deal with. I wouldn't know how to resolve the issue of the Marvell NDA, but at least Genesi should let it be known that they're a serious hardware vendor and should correct the misleading picture that some important developers may have now. Genesi should work on improving the information flow to and from developers, it should make damn sure email isn't bouncing from any of its offices, and where changes need to be made, they should be.
If there are issues with Peg II hardware or firmware that preclude OpenBSD support, Genesi should proactively outline them, to avoid situations like this. It seems otherwise it will be impossible to win the confidense of outside coders.
Well, it's easy to make suggestions like this in hindsight, but there've been communication and organizational problems with Genesi on various levels since the beginning, so something like this breakdown isn't exactly a huge surprise. The important thing is to make constructive use of it: fix what's broken internally, correct outside impressions that are inaccurate, etc. Just my two cents' worth.
-- gary_c