While the firmware may be open source, the hardware is not. It's not enough to be able to see the schematic in a PDF; it's important to have proper, machine-readable, design files.
Nobody would consider a print-out of the Linux kernel's source code to be an acceptable means of distributing it.
Wow, that's crazy! I've always wondered if something like that would be feasible... had no idea it had actually been done on a grand-scale before. Thanks for that.
To respond to a deleted comment about why it's important:
The claim is that it's open-source, not open-rendering. There's no thing you can insert a PDF into to be able to manipulate the design in a meaningful way.
Even as a visual reference, it's not very useful. Googling the the two main chips gives no useful search results. If you did manually recreate the schematic, you would still have no way of building anything with it.
The schematic, even in image form, is the source as far as my experience goes. No, it isn't turnkey, but the schematic (in CAD file format or not) is the design. Everything after that is primarily implementation- more analogous to modern day compilers and linkers, IMO.
Even if they gave you layout files, they would likely be both a pain, and not very useful. Like getting someone else's *.o files. You probably won't be using the same tools, and you probably won't have the same boardhouse, the same parts... I didn't really come to grips with how incredibly nonstandard (or maybe just incredibly varied) parts footprints are until I made my first >100 part count SMD board. It quickly became clear why companies develop their own parts libraries, and why they cling ferociously to existing vendors, supply lines, and specific parts.
Suppose I gave you an article/paper in a proprietary file format you can't convert, with a font you don't have, painstakingly arranged for a paper size you've never heard of, in color gradients your printer can't resolve, that uses features only a couple printers can print. Would that be helpful? Me, I'd rather just get the raw .txt file and .jpg's...
Doubt it, they require a special DP to HDMI converter IC, and you basically have to build a custom PCB in order to route the high-frequency DisplayPort and HDMI signals properly. May as well stick the microcontroller on the board too because that's easy to lay out compared to everything else.
I disagree. Standalone gerbers aren't terribly useful for hobbyists, and you'd have no luck opening an Allegro project even if they released that (which they wouldn't due to in-house component libraries containing supply leads etc.)
This remains an excellent reference design to build upon. The world of PCB design is more labor intensive, but this would be perfectly simple to reimplement using hobby-level PCB software.
There are no universal Schematic/PCB Design files. It is actually very common to provide only a PDF as reference. Anyone who is going through the trouble of trying to make these should have the basic skills necessary to do a decent layout. It is a very simple board.
Nobody would consider a print-out of the Linux kernel's source code to be an acceptable means of distributing it.