I could split this into two patches, one that just hardcodes the DRHD values, and another that "eases" FSP's job. Should I reuse this change ID for DRHD hardcoding or register writes?

based on the commit subject, the former IMO

+1

The latter is really optional, in the best case a no-op and in the
worst a regression (e.g. if FSP misbehaves) and will probably get
some more bikeshedding about where/when it should be done.

Unrelated, what's with the comment style? I'm generally not op-
posed to //, but seeing it added to a file that consistently uses
the other style makes me freak out a little.

View Change

1 comment:

To view, visit change 35108. To unsubscribe, or for help writing mail filters, visit settings.

Gerrit-Project: coreboot
Gerrit-Branch: master
Gerrit-Change-Id: I7eb20182380b953a1842083e7a3c67919d6971b9
Gerrit-Change-Number: 35108
Gerrit-PatchSet: 2
Gerrit-Owner: Angel Pons <th3fanbus@gmail.com>
Gerrit-Reviewer: Angel Pons <th3fanbus@gmail.com>
Gerrit-Reviewer: Kyösti Mälkki <kyosti.malkki@gmail.com>
Gerrit-Reviewer: Matt DeVillier <matt.devillier@gmail.com>
Gerrit-Reviewer: Maxim Polyakov <max.senia.poliak@gmail.com>
Gerrit-Reviewer: Nico Huber <nico.h@gmx.de>
Gerrit-Reviewer: Patrick Rudolph <siro@das-labor.org>
Gerrit-Reviewer: build bot (Jenkins) <no-reply@coreboot.org>
Gerrit-CC: Paul Menzel <paulepanter@users.sourceforge.net>
Gerrit-Comment-Date: Fri, 30 Aug 2019 09:18:12 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Angel Pons <th3fanbus@gmail.com>
Comment-In-Reply-To: Matt DeVillier <matt.devillier@gmail.com>
Gerrit-MessageType: comment