We still add a master header for compatibility purposes, and the default layouts don't cover anything non-coreboot (eg. IFD regions) yet. The default layouts can be overridden by specifying an fmd file, from which the fmap is generated. Future work: - map IFD regions to fmap regions - non-x86: build minimalistic trampolines that jump into the first cbfs file, so the bootblock can be part of CBFS instead of reserving a whole 64K for it. - teach coreboot's cbfs code to work without the master header - teach coreboot's cbfs code to work on different fmap regions Change-Id: Id1085dcd5107cf0e02e8dc1e77dc0dd9497a819c Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-on: https://review.coreboot.org/11692 Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: build bot (Jenkins)
		
			
				
	
	
		
			16 lines
		
	
	
		
			452 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			16 lines
		
	
	
		
			452 B
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| # layout for firmware residing at top of 4GB address space
 | |
| # +-------------+ <-- 4GB - ROM_SIZE / start of flash
 | |
| # | unspecified |
 | |
| # +-------------+ <-- 4GB - BIOS_SIZE
 | |
| # | FMAP        |
 | |
| # +-------------+ <-- 4GB - BIOS_SIZE + FMAP_SIZE
 | |
| # | CBFS        |
 | |
| # +-------------+ <-- 4GB / end of flash
 | |
| 
 | |
| FLASH@##ROM_BASE## ##ROM_SIZE## {
 | |
| 	BIOS@##BIOS_BASE## ##BIOS_SIZE## {
 | |
| 		FMAP@##FMAP_BASE## ##FMAP_SIZE##
 | |
| 		COREBOOT(CBFS)@##CBFS_BASE## ##CBFS_SIZE##
 | |
| 	}
 | |
| }
 |