From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"dvhart@infradead.org" <dvhart@infradead.org>,
"Ong, Boon Leong" <boon.leong.ong@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 1/1] x86: Add Isolated Memory Regions for Quark X1000
Date: Mon, 26 Jan 2015 18:02:20 +0000 [thread overview]
Message-ID: <54C6812C.9060101@nexus-software.ie> (raw)
In-Reply-To: <CAHp75VcgUuUkfq0+W-Q5ab0Jm_i9syzvD=gC+Qd0_SX9L2LVqA@mail.gmail.com>
On 26/01/15 17:23, Andy Shevchenko wrote:
>>> So, I'm not sure the above is a part of the patch. Would it be a prepend?
>> Hmm - what do you mean by that ?
>
> I mean first to introduce IMR files and then create the board entry in
> the kernel config.
>
> And it may contain the following as well (whatever is mandatory from it)
>
> depends on M586TSC
> select ARCH_REQUIRE_GPIOLIB
> select I2C
>
> I took this snippet from BSP code.
>
Hmm I actually added that to the BSP...
/thinks
Yes 586TSC is in there to make sure the kernel build happens with TSC
enabled - I think it's not an unreasonable constraint to add.
V5 + TSC.
--
BOD
next prev parent reply other threads:[~2015-01-26 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 14:15 [PATCH v3 0/1] x86: Add IMR support to Quark/Galileo Bryan O'Donoghue
2015-01-26 14:15 ` [PATCH v3 1/1] x86: Add Isolated Memory Regions for Quark X1000 Bryan O'Donoghue
2015-01-26 16:37 ` Andy Shevchenko
2015-01-26 16:43 ` Andy Shevchenko
2015-01-26 16:59 ` Bryan O'Donoghue
2015-01-26 17:23 ` Andy Shevchenko
2015-01-26 18:02 ` Bryan O'Donoghue [this message]
2015-01-26 18:04 ` Bryan O'Donoghue
2015-02-23 22:18 ` Pavel Machek
2015-02-24 22:40 ` Bryan O'Donoghue
2015-03-02 12:19 ` Pavel Machek
2015-01-26 14:37 ` [PATCH v3 0/1] x86: Add IMR support to Quark/Galileo Bryan O'Donoghue
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=54C6812C.9060101@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=andy.shevchenko@gmail.com \
--cc=boon.leong.ong@intel.com \
--cc=dvhart@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.