From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: [PATCH 1/3] serial: 8250_early: Add earlycon support for AMD Carrizo / Stoneyridge Date: Fri, 6 Apr 2018 14:47:13 +0100 Message-ID: <20180406144713.30d1ca00@alans-desktop> References: <20180314003655.12141-1-djkurtz@chromium.org> <20180314003655.12141-2-djkurtz@chromium.org> <20180326192428.71c23abf@alans-desktop> <20180329143400.6d9256a5@alans-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Aaron Durbin Cc: Andy Shevchenko , Daniel Kurtz , Ricardo Ribalda Delgado , Greg Kroah-Hartman , Jiri Slaby , Marc Gonzalez , Doug Anderson , Matt Redfearn , Jeffy , "open list:SERIAL DRIVERS" , Linux Kernel Mailing List List-Id: linux-serial@vger.kernel.org > But we don't have the full ACPI interpreter up in the early part of > the kernel. All these 'early' devices have their own setup/config > which is the source of the issue. Or maybe I am wrong about the full > interpreter and the early drivers are just not taking advantage of the > ACPI device binding? In very early boot with serial console you just have to pray. No change there. Once ACPI comes up you however have the information to populate everything and configure correctly. So it should work fine except for kernel hackers trying to do early boot debug, which is a small (but important) cornercase ? Alan