9 comments:
File Documentation/getting_started/mainboard_template.md:
* 'EVT early prototype' (Unit is for 'Engineering validation test')
* 'DVT prototype' (Unit is for 'Design verification test')
This is generally confidential information, and is generally only a few months apart.
Patch Set #4, Line 30: * What's the expected release date?
This is also confidential information
File Documentation/getting_started/new_mainboard_ports.md:
Patch Set #4, Line 7: It provides
"It generally provides"? For example the AMD Picasso code won't be getting SPDs since memory is already up.
Try to find out as much as possible about the current hardware.
Dump information with existing tools:
* lspci
* lsusb
* superiotool
* inteltool
* ectool
* dmidecode
* acpidump
This is only valid for a port from an IBV BIOS.
Patch Set #4, Line 53: scheme instead.
When it makes sense.
Patch Set #4, Line 56: Provide good documentation, see point 4
This was discussed in the coreboot leadership meeting, and while desirable, documentation is NOT a requirement to submit a board, and should not be presented as such.
Patch Set #4, Line 63: What you should **not** document:
Why?
Patch Set #4, Line 68: Recommended a flashing method as described in [Flashing tutorial]
Doesn't this directly contradict point 5?
File Documentation/getting_started/writing_documentation.md:
Patch Set #4, Line 52: New mainboard ports should also add documentation
"It's requested, although not required that new mainboards add documentation."
To view, visit change 34632. To unsubscribe, or for help writing mail filters, visit settings.