From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3rdSxc043tzDsRr for ; Mon, 27 Jun 2016 22:32:19 +1000 (AEST) Message-ID: <1467027880.20278.74.camel@kernel.crashing.org> Subject: Re: [PATCH v2] powerpc/boot: Add OPAL console to epapr wrappers From: Benjamin Herrenschmidt To: oliver , Stewart Smith Cc: linuxppc-dev@lists.ozlabs.org Date: Mon, 27 Jun 2016 21:44:40 +1000 In-Reply-To: References: <1466754085-8230-1-git-send-email-oohall@gmail.com> <1466772481-11424-1-git-send-email-oohall@gmail.com> <87shvzcklm.fsf@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2016-06-27 at 16:51 +1000, oliver wrote: > None of this is useful to us since we get most of this information > from skiboot, but I'm not sure that's true for other platforms. The > kernel boot log is fairly noisy as-is so we don't gain much from > trimming. At the very least the other messages provide sanity checks > that we've exited firmware and/or the bootloader without issues. I'll > look at changing the returned error messages though, "invalid block > type" is a pretty error useless you already know what you're looking > for. Right also if you crash in the kernel itself and these are your last messages, knowing where the kernel was expanded can be useful. Cheers, Ben.