[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcgUuUkfq0+W-Q5ab0Jm_i9syzvD=gC+Qd0_SX9L2LVqA@mail.gmail.com>
Date: Mon, 26 Jan 2015 19:23:40 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: "Bryan O'Donoghue" <pure.logic@...us-software.ie>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
"x86@...nel.org" <x86@...nel.org>,
"dvhart@...radead.org" <dvhart@...radead.org>,
"Ong, Boon Leong" <boon.leong.ong@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/1] x86: Add Isolated Memory Regions for Quark X1000
On Mon, Jan 26, 2015 at 6:59 PM, Bryan O'Donoghue
<pure.logic@...us-software.ie> wrote:
> On 26/01/15 16:37, Andy Shevchenko wrote:
>> So, I mean if user enables this in the kernel config and runs rebuilt
>> kernel on the Quark it will work, will it?
>
>
> Yes. Do you mean to add a stronger comment indicating IMR is mandatory ?
> No issue with that.
No, it's just for my information.
>> If so, IMR is mandatory stuff or not? What else is mandatory?
> IMR is the only mandatory addition.
>> 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.
--
With Best Regards,
Andy Shevchenko
--
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