The main difference between the non-EFI and EFI images generated by OpenWrt is that the former uses an MS-DOS partition table, while the latter uses GPT. The EFI images still have a BIOS-compatible MBR, so they work fine on non-EFI systems. Closes #2403
		
			
				
	
	
		
			52 lines
		
	
	
		
			993 B
		
	
	
	
		
			PHP
		
	
	
	
	
	
			
		
		
	
	
			52 lines
		
	
	
		
			993 B
		
	
	
	
		
			PHP
		
	
	
	
	
	
| config('VDI_IMAGES', true)
 | |
| config('VMDK_IMAGES', true)
 | |
| 
 | |
| packages {
 | |
| 	'kmod-3c59x',
 | |
| 	'kmod-8139cp',
 | |
| 	'kmod-8139too',
 | |
| 	'kmod-e100',
 | |
| 	'kmod-e1000',
 | |
| 	'kmod-e1000e',
 | |
| 	'kmod-forcedeth',
 | |
| 	'kmod-igb',
 | |
| 	'kmod-natsemi',
 | |
| 	'kmod-ne2k-pci',
 | |
| 	'kmod-pcnet32',
 | |
| 	'kmod-r8169',
 | |
| 	'kmod-sis900',
 | |
| 	'kmod-sky2',
 | |
| 	'kmod-tg3',
 | |
| 	'kmod-tulip',
 | |
| 	'kmod-via-rhine',
 | |
| 	'kmod-via-velocity',
 | |
| 	'kmod-ath9k',
 | |
| 	'kmod-gpio-button-hotplug',
 | |
| 	'kmod-hwmon-core',
 | |
| 	'kmod-sp5100-tco',
 | |
| 	'kmod-usb-core',
 | |
| 	'kmod-usb-ohci',
 | |
| 	'kmod-usb2',
 | |
| 	'kmod-usb3',
 | |
| 	'kmod-usb-serial',
 | |
| 	'kmod-ath10k',
 | |
| 	'ath10k-firmware-qca9887',
 | |
| 	'ath10k-firmware-qca9888',
 | |
| 	'ath10k-firmware-qca988x',
 | |
| 	'ath10k-firmware-qca9984',
 | |
| 	'kmod-mt76x0e',
 | |
| 	'kmod-mt76x2',
 | |
| 	'kmod-mt7603',
 | |
| 	'kmod-mt7615e',
 | |
| }
 | |
| 
 | |
| -- We do not use the ext4 images, so we do not want to build them.
 | |
| config('TARGET_ROOTFS_EXT4FS', false)
 | |
| 
 | |
| defaults {
 | |
| 	factory = '-squashfs-combined-efi',
 | |
| 	factory_ext = {'.img.gz', '.vmdk', '.vdi'},
 | |
| 	sysupgrade = '-squashfs-combined-efi',
 | |
| 	sysupgrade_ext = '.img.gz',
 | |
| }
 |