> -----Original Message----- > From: Pratyush Anand [mailto:panand@xxxxxxxxxx] > Sent: Monday, May 22, 2017 12:09 PM > To: AKASHI Takahiro <takahiro.akashi@xxxxxxxxxx>; Dave Young > <dyoung@xxxxxxxxxx>; Bharat Bhushan <bharat.bhushan@xxxxxxx>; > bhe@xxxxxxxxxx; vgoyal@xxxxxxxxxx; corbet@xxxxxxx; > kexec@xxxxxxxxxxxxxxxxxxx; linux-doc@xxxxxxxxxxxxxxx; linux- > kernel@xxxxxxxxxxxxxxx > Subject: Re: [PATCH] kexec/kdump: Minor Documentation updates for > arm64 and Image > > > > On Friday 19 May 2017 09:15 AM, AKASHI Takahiro wrote: > >>> +to load dump-capture kernel. > >>> + > >>> + kexec -p <dump-capture-kernel-Image> \ > >>> + --initrd=<initrd-for-dump-capture-kernel> \ > >>> + --append="root=<root-dev> <arch-specific-options>" > >> For uncompressed Image, dtb is not necessary? > > Just for clarification, dtb is optional for both vmlinux and Image on > > arm64. (This means you can specify it if you want.) But this is also > > true for initrd and append(command line) to some extent. > > Yes, I agree. Should I mention "-dtb" also for "Image"? Also do we need to mention that it is optional somewhere in this document? I do not see "optional" is mentioned for other parameters and architecture. Does this looks ok: " -dtb=<optional-dtb-for-dump-capture-kernel> \" Thanks -Bharat > > > > More precisely, whether these parameters are optional or not will > > depend on architectures, not formats, I believe. > > May be not architecture, rather a distro environment. > > For example, we should be able to work without --initrd for any arch if kernel > has been compiled by configuring CONFG_INITRAMFS_SOURCE. > > ~Pratyush -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
