On Wed, Aug 21, 2013 at 11:43:21AM -0400, Kyle McMartin wrote:
> I've suspected there might be a config issue, as omap2_defconfig
> works alright, as does booting a uImage with an appended
> omap4-panda.dtb, but there's no love with a zImage + initrd + dtb
> (or even just zImage without initrd + dtb.)
>
after some further investigation, something odd is going on... turns
out things have been working (at least until initrd time, but that's
another story) fine but none of the bootargs have made it into the
kernel, so console= was unset and no messages came out.
not sure if this is appropriate, but explicitly putting the "default"
serial consoles into the dtb, at least helps me get along debugging
issues...
---
From: Kyle McMartin <kyle@xxxxxxxxxx>
Specify default bootargs consoles for the Beaglebone and Pandaboards
in their respective device tree files.
Signed-off-by: Kyle McMartin <kyle@xxxxxxxxxx>
--- a/arch/arm/boot/dts/am335x-bone.dts
+++ b/arch/arm/boot/dts/am335x-bone.dts
@@ -19,6 +19,10 @@
};
};
+ chosen {
+ bootargs = "console=ttyO0,115200n8";
+ };
+
memory {
device_type = "memory";
reg = <0x80000000 0x10000000>; /* 256 MB */
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi b/arch/arm/boot/dts/omap4-panda-common.dtsi
index faa95b5..b424d00 100644
--- a/arch/arm/boot/dts/omap4-panda-common.dtsi
+++ b/arch/arm/boot/dts/omap4-panda-common.dtsi
@@ -16,6 +16,10 @@
reg = <0x80000000 0x40000000>; /* 1 GB */
};
+ chosen {
+ bootargs = "console=ttyO2,115200";
+ };
+
leds: leds {
compatible = "gpio-leds";
pinctrl-names = "default";
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
