linux-kernel - Re: [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying DEBUG

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]

Message-ID: <20150617194058.GZ7557@n2100.arm.linux.org.uk>
Date:	Wed, 17 Jun 2015 20:40:58 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Cc:	Boris Brezillon <boris.brezillon@...e-electrons.com>,
	Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] ARM: fix DEBUG_UART_PHYS/VIRT issue when modifying
 DEBUG_LL output

On Wed, Jun 17, 2015 at 02:46:56PM +0200, Thomas Petazzoni wrote:
> What is the status of this patch? It would actually be quite useful
> when switching back and forth between different DEBUG_LL configurations.
> 
> Russell, what do you think of the proposed approach?

I'd rather we killed all the defaults, rather than keep trying to fix
these subtle issues.  That was always my goal of converting to this
model anyway.

However, I think it's important not to loose this information (how many
of us with lots of different platforms want to keep on digging through
PDFs to try and find this documentation?)  I'd like to see a per-SoC
file somewhere in Documentation/arm/ giving these details so at least
they're relatively easy to find.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/