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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 12 Dec 2013 16:33:46 +0530
From:	Panchaxari Prasannamurthy Tumkur 
	<panchaxari.prasannamurthy@...aro.org>
To:	Tomasz Figa <tomasz.figa@...il.com>
Cc:	Kgene Kim <kgene.kim@...sung.com>,
	Patch Tracking <patches@...aro.org>,
	linaro-kernel@...ts.linaro.org,
	Sylwester Nawrocki <s.nawrocki@...sung.com>,
	Heiko Stuebner <heiko@...ech.de>,
	Russell King <linux@....linux.org.uk>,
	Linus Walleij <linus.walleij@...aro.org>,
	linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH CFT] ARM:S5P64X0: Enable ARM_PATCH_PHYS_VIRT and
 AUTO_ZRELADDR by default

Hi Tomasz

> Could you explain the purpose of this change on S5P64x0?
>
> This is actually quite a poor platform choice. As of today, the kernel
> is stuck with supporting just SMDK6440/6450 boards, which are proprietary
> development boards and it doesn't look like any further boards will show
> up in future. Kukjin has actually proposed removing support for this
> platform at all and I consider this reasonable.
>
> Kukjin, should we proceed with removal?

The purpose of this patch is with the greater intent of consolidating
ARM-32 kernel. Which means a generic kernel for ARM-32 processors.

Hence these platform supported configs are introduced as default for
that particular platform.

I hope i answered your question. Else please mail me with further queries.

thanks
Panchaxari
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ