From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Print DT machine model in setup_machine_fdt()
Date: Fri, 28 Apr 2017 17:52:32 +0100 [thread overview]
Message-ID: <20170428165232.GZ13675@arm.com> (raw)
In-Reply-To: <CAMuHMdVHMcY5iy3gsYUOJLhYnMECh4yu-5pZJHXNxJhBp6+TOQ@mail.gmail.com>
On Fri, Apr 28, 2017 at 06:16:46PM +0200, Geert Uytterhoeven wrote:
> On Fri, Apr 28, 2017 at 4:57 PM, Will Deacon <will.deacon@arm.com> wrote:
> > On Thu, Apr 27, 2017 at 02:33:05PM +0200, Geert Uytterhoeven wrote:
> >> On arm32, the machine model specified in the device tree is printed
> >> during boot-up, courtesy of of_flat_dt_match_machine().
> >>
> >> On arm64, of_flat_dt_match_machine() is not called, and the machine
> >> model information is not available from the kernel log.
> >>
> >> Print the machine model to make it easier to derive the machine model
> >> from an arbitrary kernel boot log.
> >>
> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >> ---
> >> I have scripts to save kernel boot logs, and compare logs[*] for
> >> subsequent boots on the same machine. Having a way to extract the
> >> machine model from an arbitrary kernel boot log makes this easier.
>
> > I think your use-case is slightly questionable (e.g. for ACPI, we print
> > something different, and this isn't generally considered to be ABI), but
> > the patch is harmless and if you find it useful then:
>
> Not having access to an ARM ACPI system, what does it print for example?
It's supposed to print out some stuff from DMI, but my Juno just says:
DMI not present or invalid.
Luckily, it's not really an issue because I don't get to a prompt after USB
fails to come up and it times out mounting the rootfs.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Catalin Marinas <catalin.marinas@arm.com>,
Kevin Hilman <khilman@kernel.org>,
Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: Print DT machine model in setup_machine_fdt()
Date: Fri, 28 Apr 2017 17:52:32 +0100 [thread overview]
Message-ID: <20170428165232.GZ13675@arm.com> (raw)
In-Reply-To: <CAMuHMdVHMcY5iy3gsYUOJLhYnMECh4yu-5pZJHXNxJhBp6+TOQ@mail.gmail.com>
On Fri, Apr 28, 2017 at 06:16:46PM +0200, Geert Uytterhoeven wrote:
> On Fri, Apr 28, 2017 at 4:57 PM, Will Deacon <will.deacon@arm.com> wrote:
> > On Thu, Apr 27, 2017 at 02:33:05PM +0200, Geert Uytterhoeven wrote:
> >> On arm32, the machine model specified in the device tree is printed
> >> during boot-up, courtesy of of_flat_dt_match_machine().
> >>
> >> On arm64, of_flat_dt_match_machine() is not called, and the machine
> >> model information is not available from the kernel log.
> >>
> >> Print the machine model to make it easier to derive the machine model
> >> from an arbitrary kernel boot log.
> >>
> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >> ---
> >> I have scripts to save kernel boot logs, and compare logs[*] for
> >> subsequent boots on the same machine. Having a way to extract the
> >> machine model from an arbitrary kernel boot log makes this easier.
>
> > I think your use-case is slightly questionable (e.g. for ACPI, we print
> > something different, and this isn't generally considered to be ABI), but
> > the patch is harmless and if you find it useful then:
>
> Not having access to an ARM ACPI system, what does it print for example?
It's supposed to print out some stuff from DMI, but my Juno just says:
DMI not present or invalid.
Luckily, it's not really an issue because I don't get to a prompt after USB
fails to come up and it times out mounting the rootfs.
Will
next prev parent reply other threads:[~2017-04-28 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 12:33 [PATCH] arm64: Print DT machine model in setup_machine_fdt() Geert Uytterhoeven
2017-04-27 12:33 ` Geert Uytterhoeven
2017-04-28 14:57 ` Will Deacon
2017-04-28 14:57 ` Will Deacon
2017-04-28 16:16 ` Geert Uytterhoeven
2017-04-28 16:16 ` Geert Uytterhoeven
2017-04-28 16:52 ` Will Deacon [this message]
2017-04-28 16:52 ` Will Deacon
2017-04-28 17:30 ` Sudeep Holla
2017-04-28 17:30 ` Sudeep Holla
2017-04-28 16:14 ` Catalin Marinas
2017-04-28 16:14 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170428165232.GZ13675@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.