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: <20091116165716.GD3568@n2100.arm.linux.org.uk>
Date:	Mon, 16 Nov 2009 16:57:16 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Brian Swetland <swetland@...gle.com>
Cc:	Pavel Machek <pavel@....cz>, Arve Hj?nnev?g <arve@...roid.com>,
	kernel list <linux-kernel@...r.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/3] msm: add minimal board file for HTC Dream device

On Mon, Nov 16, 2009 at 08:43:20AM -0800, Brian Swetland wrote:
> What's the best way to handle a situation where there is no valid
> debug uart?  Could the arch/platform require DEBUG_LL be unset via
> Kconfig directives if it is configured in a way where there is no
> valid debug uart?

You're the first to have that issue.  Everyone else has a UART they
can always direct stuff at.

However, I believe you're making the issue far larger than it really is.

1. If you define the DEBUG_LL macros to be empty, printascii() etc will
   not touch any mapping.

2. If no mapping is going to be touched by printascii(), does it matter
   whether a UART is mapped via this early mapping stuff?

The answer to (2) is no.

So, you can still arrange for these fields to be populated with a valid
value even if you don't intend to use the resulting mapping.  And so
there's no need to force DEBUG_LL to be unset.

If you really have no values you can use, make sure you set io_pg_offst
to 0x3ffc - the last offset in the L1 page table.  This will cause the
code to write a single dummy entry at the very top of the page table,
which will then be overwritten by the generic ARM arch code for its own
use.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ