linux-kernel - Re: [PATCH] Restricted Access Region Register driver for Intel MID devices

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: <6766.1247148820@turing-police.cc.vt.edu>
Date:	Thu, 09 Jul 2009 10:13:40 -0400
From:	Valdis.Kletnieks@...edu
To:	Mark Allyn <mark.a.allyn@...el.com>
Cc:	linux-kernel@...r.kernel.org, alan@...ux.intel.com,
	charles.f.johnson@...el.com
Subject: Re: [PATCH] Restricted Access Region Register driver for Intel MID devices

On Wed, 08 Jul 2009 13:00:12 PDT, Mark Allyn said:
> This is the device driver for the Restricted Access Region registers on the
> Intel MID device.
> 
> Restricted Access Regions are areas of memory that are not accessable to the
> i86 processor.

This text should appear in the Kconfig entry down below.

'i86' - typo, or a new device that just looks like a typo?

> +++ b/drivers/rar_register/Kconfig
> @@ -0,0 +1,17 @@
> +#
> +# Serial device configuration
> +#
> +
> +menu "RAR Register Driver"
> +#
> +# The new 8250/16550 serial drivers
> +config RAR_REGISTER
> +	tristate "Restricted Access Region Register Driver"
> +	depends on MRST

Presumably, a yet-to-appear-in-my-inbox (but possibly in-flight) patch
will define this...

> +	default y
> +	---help---
> +		This driver allows other kernel drivers access to the
> +		contents of the restricted access region control 
> +		registers. 

As noted above, this should mention what chipset(s) these control registers
are found on.

Content of type "application/pgp-signature" skipped