From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B75FDC43381 for ; Thu, 28 Mar 2019 14:13:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 825D0217D7 for ; Thu, 28 Mar 2019 14:13:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="AEBl682V" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726344AbfC1OND (ORCPT ); Thu, 28 Mar 2019 10:13:03 -0400 Received: from mail.skyhub.de ([5.9.137.197]:36962 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725994AbfC1ONC (ORCPT ); Thu, 28 Mar 2019 10:13:02 -0400 Received: from zn.tnic (p200300EC2F098000329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2f09:8000:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id E08D11EC02C1; Thu, 28 Mar 2019 15:13:00 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1553782381; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=SFCWdSOlaJfNRzFp/ijRTQRtbU5jqY6S3izHaLCyZFk=; b=AEBl682VpTrYlsUWLhQC7YF6usdv8rK4Xs4PW20DGHlfDORWoCrM50uqFaPZyR5Vo5ivqM w3r75hrnSvW4dHEl/E0xSXtKOTEa0NYx8mRFZ1zq7yyBxrxRekBmrljGSteh1rOfD7JvmB gLZV1/14bZFf8lNwn8AlUbgCL2dSLkg= Date: Thu, 28 Mar 2019 15:13:07 +0100 From: Borislav Petkov To: Andy Shevchenko Cc: "H. Peter Anvin" , x86@kernel.org, Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 7/7] x86/boot: Support nocfg parameter for earlyprintk Message-ID: <20190328141307.GM22720@zn.tnic> References: <20190319184325.72807-1-andriy.shevchenko@linux.intel.com> <20190319184325.72807-8-andriy.shevchenko@linux.intel.com> <20190328130317.GG22720@zn.tnic> <20190328132153.GZ9224@smile.fi.intel.com> <20190328134213.GJ22720@zn.tnic> <20190328140039.GC9224@smile.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190328140039.GC9224@smile.fi.intel.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 28, 2019 at 04:00:39PM +0200, Andy Shevchenko wrote: > If it's _non-standard_ serial interface (by meaning of I/O accessors and port > addresses), user may consider to use this options in case the interface to > communicate with kernel is serial one and its configuration is done by other > means (firmware / bootloader / EFI / etc). And is this non-standard interface out there in the wild or only at Intel's labs? Are there boxes like that out there? If I go to the store and buy a box, how do I know whether that box would need "nocfg"? Do I look in the BIOS or how do I find out I need to supply "nocfg"? > If by BIOS or by other means the serial port is configured How do I find out that the serial port is configured? And don't give me that "example" about the typing on keyboard or on touch screen again. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.