Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1523935
| From | Guenter Roeck <linux@roeck-us.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' |
| Date | 2016-11-16 23:50 +0100 |
| Message-ID | <sEhbI-xX-3@gated-at.bofh.it> (permalink) |
| References | <sEcvn-609-13@gated-at.bofh.it> <sEdrs-6BG-25@gated-at.bofh.it> <sEgIG-nF-9@gated-at.bofh.it> <sEgSm-rg-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Nov 16, 2016 at 08:27:09PM -0200, Fabio Estevam wrote:
> Hi Guenter,
>
> On Wed, Nov 16, 2016 at 8:10 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> >
> > Anyway, I guess the problem is that the "official" dtb files no longer provide
> > the skeleton /chosen and /memory nodes (and maybe others), and qemu seems to
> > expect that they are provided. Is that correct ?
>
> imx6qdl-sabrelite.dtsi provides chosen and memory nodes.
Yes, but not the 'device_type' property, which the kernel seems to expect.
The qemu patch below fixes the problem for sabrelite, I just don't know
if that is really the way to go. You tell me; I'll be happy to submit
the necessary patch(es) into qemu.
The same is true for 'chosen'. Right now qemu expects this node to exist.
It does exist for sabrelite, but apparently not for imx25-pdk.
Guenter
---
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index 1b913a4..080d1e5 100644
--- a/hw/arm/boot.c
+++ b/hw/arm/boot.c
@@ -486,6 +486,12 @@ static int load_dtb(hwaddr addr, const struct arm_boot_info *binfo,
g_free(nodename);
}
} else {
+ Error *err = NULL;
+
+ if (!qemu_fdt_getprop(fdt, "/memory", "device_type", NULL, &err)) {
+ qemu_fdt_setprop_string(fdt, "/memory", "device_type", "memory");
+ }
+
rc = qemu_fdt_setprop_sized_cells(fdt, "/memory", "reg",
acells, binfo->loader_start,
scells, binfo->ram_size);
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Guenter Roeck <linux@roeck-us.net> - 2016-11-16 18:50 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Fabio Estevam <festevam@gmail.com> - 2016-11-16 19:50 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Mark Rutland <mark.rutland@arm.com> - 2016-11-16 19:50 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Guenter Roeck <linux@roeck-us.net> - 2016-11-16 23:20 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Fabio Estevam <festevam@gmail.com> - 2016-11-16 23:30 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Guenter Roeck <linux@roeck-us.net> - 2016-11-16 23:50 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Fabio Estevam <festevam@gmail.com> - 2016-11-17 00:00 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Mark Rutland <mark.rutland@arm.com> - 2016-11-17 12:00 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Mark Rutland <mark.rutland@arm.com> - 2016-11-17 18:10 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Guenter Roeck <linux@roeck-us.net> - 2016-11-17 18:30 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Guenter Roeck <linux@roeck-us.net> - 2016-11-17 18:20 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Mark Rutland <mark.rutland@arm.com> - 2016-11-17 18:40 +0100
Re: Boot failures in -next due to 'ARM: dts: imx: Remove skeleton.dtsi' Guenter Roeck <linux@roeck-us.net> - 2016-11-17 19:10 +0100
csiph-web