| Message ID | 20251113151802.366-1-jon.mason@arm.com |
|---|---|
| State | New |
| Headers | show |
| Series | [v4,1/2] runqemu: avoid setting "mem=" when using a DTB | expand |
diff --git a/scripts/runqemu b/scripts/runqemu index 2be7a0f2869f..370b45578137 100755 --- a/scripts/runqemu +++ b/scripts/runqemu @@ -884,7 +884,7 @@ to your build configuration. self.set('QB_MEM', qb_mem) mach = self.get('MACHINE') - if not mach.startswith(('qemumips', 'qemux86', 'qemuloongarch64')): + if not mach.startswith(('qemumips', 'qemux86', 'qemuloongarch64')) and self.get('QB_DTB') == "": self.kernel_cmdline_script += ' mem=%s' % self.get('QB_MEM').replace('-m','').strip() + 'M' self.qemu_opt_script += ' %s' % self.get('QB_MEM')
Some emulated machines, such as the Raspberry Pi models, fail to boot if a fixed "mem=" value is passed on the kernel command line. When a DTB is used (QB_DTB is set), the memory size is already defined there, so specifying it again is unnecessary and can cause issues. Skip adding "mem=" to the kernel command line when QB_DTB is present. Signed-off-by: Jon Mason <jon.mason@arm.com> --- scripts/runqemu | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)