This also uncouples cbfstool from being overly Chromium specific. However the main objective is to not subprocess flashrom any more and instead use the programmatic API. BUG=b:207808292 TEST=built and ran `elogtool (list|clear|add 0x16 C0FFEE)`. Change-Id: I79df2934b9b0492a554a4fecdd533a0abe1df231 Signed-off-by: Edward O'Callaghan <quasisec@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/59714 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Sam McNally <sammc@google.com>
		
			
				
	
	
		
			18 lines
		
	
	
		
			403 B
		
	
	
	
		
			C
		
	
	
	
	
	
			
		
		
	
	
			18 lines
		
	
	
		
			403 B
		
	
	
	
		
			C
		
	
	
	
	
	
| /* SPDX-License-Identifier: BSD-3-Clause */
 | |
| 
 | |
| #ifndef UFLASHROM_H
 | |
| #define UFLASHROM_H
 | |
| 
 | |
| #define FLASHROM_PROGRAMMER_INTERNAL_AP "internal"
 | |
| 
 | |
| struct firmware_programmer {
 | |
| 	const char *programmer;
 | |
| 	uint32_t size;
 | |
| 	uint8_t *data;
 | |
| };
 | |
| 
 | |
| int flashrom_read(struct firmware_programmer *image, const char *region);
 | |
| int flashrom_write(struct firmware_programmer *image, const char *region);
 | |
| 
 | |
| #endif /* UFLASHROM_H */
 |