lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20180406144713.30d1ca00@alans-desktop> Date: Fri, 6 Apr 2018 14:47:13 +0100 From: Alan Cox <gnomes@...rguk.ukuu.org.uk> To: Aaron Durbin <adurbin@...omium.org> Cc: Andy Shevchenko <andy.shevchenko@...il.com>, Daniel Kurtz <djkurtz@...omium.org>, Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Jiri Slaby <jslaby@...e.com>, Marc Gonzalez <marc_gonzalez@...madesigns.com>, Doug Anderson <dianders@...omium.org>, Matt Redfearn <matt.redfearn@...s.com>, Jeffy <jeffy.chen@...k-chips.com>, "open list:SERIAL DRIVERS" <linux-serial@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 1/3] serial: 8250_early: Add earlycon support for AMD Carrizo / Stoneyridge > 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
Powered by blists - more mailing lists