They're listed in AUTHORS and often incorrect anyway, for example: - What's a "Copyright $year-present"? - Which incarnation of Google (Inc, LLC, ...) is the current copyright holder? - People sometimes have their editor auto-add themselves to files even though they only deleted stuff - Or they let the editor automatically update the copyright year, because why not? - Who is the copyright holder "The coreboot project Authors"? - Or "Generated Code"? Sidestep all these issues by simply not putting these notices in individual files, let's list all copyright holders in AUTHORS instead and use the git history to deal with the rest. Change-Id: I89b10076e0f4a4b3acd59160fb7abe349b228321 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/39611 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-by: Angel Pons <th3fanbus@gmail.com> Reviewed-by: David Hendricks <david.hendricks@gmail.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
77 lines
2.3 KiB
C
77 lines
2.3 KiB
C
/*
|
|
* This file is part of the coreboot project.
|
|
*
|
|
*
|
|
* This program is free software; you can redistribute it and/or modify
|
|
* it under the terms of the GNU General Public License as published by
|
|
* the Free Software Foundation; version 2 of the License.
|
|
*
|
|
* This program is distributed in the hope that it will be useful,
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
* GNU General Public License for more details.
|
|
*/
|
|
|
|
#ifndef _BOOT_DEVICE_H_
|
|
#define _BOOT_DEVICE_H_
|
|
|
|
#include <commonlib/region.h>
|
|
|
|
/*
|
|
* Boot device region can be protected by 2 sources, media and controller.
|
|
* The following modes are identified. It depends on the flash chip and the
|
|
* controller if mode is actually supported.
|
|
*
|
|
* MEDIA_WP : Flash/Boot device enforces write protect
|
|
* CTRLR_WP : Controller device enforces write protect
|
|
* CTRLR_RP : Controller device enforces read protect
|
|
* CTRLR_RWP : Controller device enforces read-write protect
|
|
*/
|
|
enum bootdev_prot_type {
|
|
CTRLR_WP = 1,
|
|
CTRLR_RP = 2,
|
|
CTRLR_RWP = 3,
|
|
MEDIA_WP = 4,
|
|
};
|
|
/*
|
|
* Please note that the read-only boot device may not be coherent with
|
|
* the read-write boot device. Thus, mixing mmap() and writeat() is
|
|
* most likely not to work so don't rely on such semantics.
|
|
*/
|
|
|
|
/* Return the region_device for the read-only boot device. */
|
|
const struct region_device *boot_device_ro(void);
|
|
|
|
/* Return the region_device for the read-write boot device. */
|
|
const struct region_device *boot_device_rw(void);
|
|
|
|
/*
|
|
* Create a sub-region of the read-only boot device.
|
|
* Returns 0 on success, < 0 on error.
|
|
*/
|
|
int boot_device_ro_subregion(const struct region *sub,
|
|
struct region_device *subrd);
|
|
|
|
/*
|
|
* Create a sub-region of the read-write boot device.
|
|
* Returns 0 on success, < 0 on error.
|
|
*/
|
|
int boot_device_rw_subregion(const struct region *sub,
|
|
struct region_device *subrd);
|
|
|
|
/*
|
|
* Write protect a sub-region of the boot device represented
|
|
* by the region device.
|
|
* Returns 0 on success, < 0 on error.
|
|
*/
|
|
int boot_device_wp_region(const struct region_device *rd,
|
|
const enum bootdev_prot_type type);
|
|
|
|
/*
|
|
* Initialize the boot device. This may be called multiple times within
|
|
* a stage so boot device implementations should account for this behavior.
|
|
**/
|
|
void boot_device_init(void);
|
|
|
|
#endif /* _BOOT_DEVICE_H_ */
|