[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2LZKfZpdTQ-R4o9mJ6dk52VRF+Bxj=PJEx-1MA4yH8+w@mail.gmail.com>
Date: Thu, 18 Aug 2022 14:06:40 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Joel Stanley <joel@....id.au>
Cc: Quan Nguyen <quan@...amperecomputing.com>,
Arnd Bergmann <arnd@...db.de>, openbmc@...ts.ozlabs.org,
Olof Johansson <olof@...om.net>, soc@...nel.org,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Andrew Jeffery <andrew@...id.au>,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-aspeed@...ts.ozlabs.org,
Open Source Submission <patches@...erecomputing.com>,
Phong Vo <phong@...amperecomputing.com>,
thang@...amperecomputing.com
Subject: Re: [PATCH v3 2/2] ARM: dts: aspeed: Add device tree for Ampere's Mt.
Mitchell BMC
On Thu, Aug 18, 2022 at 9:33 AM Joel Stanley <joel@....id.au> wrote:
> > +
> > +/ {
> > + model = "Ampere Mt.Mitchell BMC";
> > + compatible = "ampere,mtmitchell-bmc", "aspeed,ast2600";
> > +
> > + chosen {
> > + stdout-path = &uart5;
>
> I know you've been told by Arnd and others to remove the default
> command line here, but without it your device tree fails to produce
> any output in my tests:
>
> qemu-system-arm -M ast2600-evb -nographic -dtb
> arch/arm/boot/dts/aspeed-bmc-ampere-mtmitchell.dtb -kernel
> arch/arm/boot/zImage
>
> Without a working test, I can't tell the difference between a broken
> device tree and one that omits the serial device on the command line.
> Can you work with Arnd to come to a solution here?
If you use qemu as the boot loader, I think the expected way to do
this is to use the "-append" command line argument along with "-kernel".
Is there any reason for this machine to be special here?
Arnd
Powered by blists - more mailing lists