linux-kernel - Re: [PATCH v3 1/1] x86: Add Isolated Memory Regions for Quark X1000

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]

Date:	Mon, 26 Jan 2015 18:02:20 +0000
From:	Bryan O'Donoghue <pure.logic@...us-software.ie>
To:	Andy Shevchenko <andy.shevchenko@...il.com>
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 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
--
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/