From: Valdis.Kletnieks@vt.edu
To: Mark Allyn <mark.a.allyn@intel.com>
Cc: linux-kernel@vger.kernel.org, alan@linux.intel.com,
charles.f.johnson@intel.com
Subject: Re: [PATCH] Restricted Access Region Register driver for Intel MID devices
Date: Thu, 09 Jul 2009 10:13:40 -0400 [thread overview]
Message-ID: <6766.1247148820@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 08 Jul 2009 13:00:12 PDT." <1247083212-17331-1-git-send-email-mark.a.allyn@intel.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
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.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2009-07-09 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 20:00 Mark Allyn
2009-07-09 8:54 ` Andrey Panin
2009-07-09 14:13 ` Valdis.Kletnieks [this message]
2009-07-09 23:20 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6766.1247148820@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=alan@linux.intel.com \
--cc=charles.f.johnson@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.a.allyn@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®