Skip to content
Snippets Groups Projects
  • Matthias Schiffer's avatar
    cc174ad1
    x86: copy separate kernel and rootfs images to "other" directory · cc174ad1
    Matthias Schiffer authored
    For regular use, a full disk image is always recommended, as it is
    required to support sysupgrades.
    
    During development or for automated tests, separate images for the
    kernel and rootfs may be useful to pass additional kernel cmdline or use
    nfsroot/virtiofs. The rootfs is only available as a (squashfs)
    filesystem image, not as a TAR archive (the TAR archive in OpenWrt's bin
    directory does not contain DEVICE_PACKAGES, so it is missing most of
    Gluon's packages).
    x86: copy separate kernel and rootfs images to "other" directory
    Matthias Schiffer authored
    For regular use, a full disk image is always recommended, as it is
    required to support sysupgrades.
    
    During development or for automated tests, separate images for the
    kernel and rootfs may be useful to pass additional kernel cmdline or use
    nfsroot/virtiofs. The rootfs is only available as a (squashfs)
    filesystem image, not as a TAR archive (the TAR archive in OpenWrt's bin
    directory does not contain DEVICE_PACKAGES, so it is missing most of
    Gluon's packages).
x86-generic 297 B
include 'x86.inc'

packages {
	'kmod-gpio-nct5104d',
	'kmod-leds-gpio',
	'kmod-pcengines-apuv2',
}

device('x86-generic', 'generic', {
	extra_images = {
		{'-kernel', '-kernel', '.bin'},
		{'-squashfs-rootfs', '-rootfs', '.img.gz'},
	},
	manifest_aliases = {
		'x86-kvm',
		'x86-xen_domu',
	},
})