From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1424745AbdD1Ra6 (ORCPT ); Fri, 28 Apr 2017 13:30:58 -0400 Received: from foss.arm.com ([217.140.101.70]:51806 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1422832AbdD1Rat (ORCPT ); Fri, 28 Apr 2017 13:30:49 -0400 Subject: Re: [PATCH] arm64: Print DT machine model in setup_machine_fdt() To: Will Deacon , Geert Uytterhoeven References: <1493296385-14140-1-git-send-email-geert+renesas@glider.be> <20170428145730.GS13675@arm.com> <20170428165232.GZ13675@arm.com> Cc: Sudeep Holla , Geert Uytterhoeven , Arnd Bergmann , Kevin Hilman , Catalin Marinas , "linux-kernel@vger.kernel.org" , Mark Brown , "linux-arm-kernel@lists.infradead.org" From: Sudeep Holla Organization: ARM Message-ID: <7b593509-a0de-8493-051d-8b7e3118f551@arm.com> Date: Fri, 28 Apr 2017 18:30:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170428165232.GZ13675@arm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 28/04/17 17:52, Will Deacon wrote: > On Fri, Apr 28, 2017 at 06:16:46PM +0200, Geert Uytterhoeven wrote: >> On Fri, Apr 28, 2017 at 4:57 PM, Will Deacon 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 >>>> --- >>>> 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. > With latest firmware, I get something like: DMI: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform, BIOS EDK II ... -- Regards, Sudeep