linux-kernel - Re: [RFC 0/5] console/acpi: add DBG2 and SPCR console configuration

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 12 Jan 2016 10:14:09 -0500
From:	Christopher Covington <cov@...eaurora.org>
To:	Leif Lindholm <leif.lindholm@...aro.org>,
	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
	linux-serial@...r.kernel.org, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org, graeme.gregory@...aro.org
CC:	mark.rutland@....com, al.stone@...aro.org,
	linaro-acpi@...ts.linaro.org, jcm@...hat.com, torez@...hat.com,
	lv.zheng@...el.com, Timur Tabi <timur@...cinc.com>,
	"linux-arm-msm@...r.kernel.org" <linux-arm-msm@...r.kernel.org>
Subject: Re: [RFC 0/5] console/acpi: add DBG2 and SPCR console configuration

Hi,

On 09/08/2015 08:43 AM, Leif Lindholm wrote:
> Support for configuring bootconsole and console via the ACPI tables
> DBG2 (Debug Port Table 2) [1] and SPCR (Serial Port Console Redirection
> Table) [2], defined by Microsoft, has been discussed on and off over the
> years.
> 
> [1] https://msdn.microsoft.com/en-us/library/windows/hardware/dn639131(v=vs.85).aspx
> [2] https://msdn.microsoft.com/en-us/library/windows/hardware/dn639132(v=vs.85).aspx
> 
> Licensing concerns have prevented this happening in the past, but as of
> 10 August 2015, these tables have both been released also under OWF 1.0
> (http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0)
> which is think is noncontroversially GPL-compatible?
> 
> This set is a first attempt at implementing this.
> 
> Submitting as an RFC since the SPCR handling currently depends on the
> console driver being initialized after subsystem initcalls. Workaround
> to enable testing surrounding infrastructure in 5/5, _really_ not
> intended to be merged.
> (Suggestions for acceptable ways of working around this appreciated.)

What's required for this to graduate from RFC status? Is anyone working
on it?

Thanks,
Christopher Covington

-- 
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project