Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967184AbdCXTuv (ORCPT ); Fri, 24 Mar 2017 15:50:51 -0400 Received: from mail-it0-f43.google.com ([209.85.214.43]:36409 "EHLO mail-it0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965599AbdCXTum (ORCPT ); Fri, 24 Mar 2017 15:50:42 -0400 MIME-Version: 1.0 In-Reply-To: <20170324122858.GF22771@leverpostej> References: <1490303069-13230-1-git-send-email-thierry.escande@collabora.com> <1490303069-13230-6-git-send-email-thierry.escande@collabora.com> <20170324122858.GF22771@leverpostej> From: Julius Werner Date: Fri, 24 Mar 2017 12:50:40 -0700 X-Google-Sender-Auth: xvWAnrVboLhFikrC7DdtqI07Wog Message-ID: Subject: Re: [PATCH 5/5] firmware: google memconsole: Add ARM/ARM64 support To: Mark Rutland Cc: Thierry Escande , Rob Herring , Greg Kroah-Hartman , Olof Johansson , Stephen Warren , LKML , "devicetree@vger.kernel.org" , Julius Werner , Brian Norris Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 148 Lines: 3 > What exactly is the "memory console"? Is it a log that coreboot writes into? Yes. It contains log messages, like coreboot's equivalent of dmesg.