[U-Boot] [PATCH 07/14] dm: dts: omap: Select correct console for beaglebone

Tom Rini trini at ti.com
Wed Oct 22 17:59:21 CEST 2014


On Mon, Sep 22, 2014 at 09:48:47AM -0600, Simon Glass wrote:

> Select serial0 as the console.
> 
> Signed-off-by: Simon Glass <sjg at chromium.org>
> ---
> 
>  arch/arm/dts/am335x-bone-common.dtsi | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/arch/arm/dts/am335x-bone-common.dtsi b/arch/arm/dts/am335x-bone-common.dtsi
> index 2f66ded..e70b4d1 100644
> --- a/arch/arm/dts/am335x-bone-common.dtsi
> +++ b/arch/arm/dts/am335x-bone-common.dtsi
> @@ -10,6 +10,10 @@
>  	model = "TI AM335x BeagleBone";
>  	compatible = "ti,am335x-bone", "ti,am33xx";
>  
> +	chosen {
> +		stdout-path = &uart0;
> +	};
> +
>  	cpus {
>  		cpu at 0 {
>  			cpu0-supply = <&dcdc2_reg>;

So here's where I worry.  The reason we have a Kconfig for CONS_INDEX is
that there are boards it's NOT uart0.  Setting aside the people with a
"uart cape" (or otherwise breadboarding out another uart to a real
connector), the industrial EVM is uart2 I want to say and we had been
happily supporting this board with just a different build target (then
defconfig).  What can we do here?  And yes, I see this is the bone DT
not the EVM dt, but I'd rather not have to, if we don't have to at
least, default to just not supporting the board (which is at least on
the table, there's no DT for it in the kernel either).

As it stands however, it's right for what it's modifying so:

Acked-by: Tom Rini <trini at ti.com>

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20141022/ed6eb92c/attachment.pgp>


More information about the U-Boot mailing list