Oliver Smith d4f4ea8488 pmb: add -f (force) parameter to bootimg_analyze ... We are analyzing the `boot.img` with `file` before we send it to `unpackbootimg`. File does not recognize all kinds of `boot.img` files, which `unpackbootimg` can extract, so we need a way to skip this check. Details: * Add `-f` parameter, continues extraction with a warning if the file seems to be invalid * Tell the user that `-f` can be used if the `boot.img` is invalid and it's not specified * Consistent spelling of `boot.img` instead of `bootimg` in messages Fixes #1608		2018-07-06 21:57:18 +02:00
..
aportgen	devicepkg-dev kernel prepare function	2018-07-02 00:12:49 +00:00
build	Remove github.com references	2018-06-30 09:00:48 +02:00
chroot	menuconfig: add gconfig/xconfig support (#1509)	2018-06-09 06:52:24 +00:00
config	Remove github.com references	2018-06-30 09:00:48 +02:00
export	Add install flag to generate separate boot and system images (#1442)	2018-05-01 00:18:40 +00:00
flasher	pmb/flasher: Fix regression with exporting odin images (#1529)	2018-06-01 18:19:12 +00:00
helpers	CI failure check successful, now fix it	2018-06-30 09:08:02 +02:00
install	Remove github.com references	2018-06-30 09:00:48 +02:00
parse	pmb: add -f (force) parameter to bootimg_analyze	2018-07-06 21:57:18 +02:00
qemu	Use Alpine's QEMU rather than host system QEMU (v2)	2018-07-06 19:50:59 +00:00
__init__.py	Only print 'pmbootstrap log' msg to stdout (#1453)	2018-05-01 00:22:16 +00:00