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:	Sun, 1 Nov 2015 20:37:37 +0000
From:	Noam Camus <noamc@...hip.com>
To:	Alexey Brodkin <Alexey.Brodkin@...opsys.com>,
	"linux-snps-arc@...ts.infradead.org" 
	<linux-snps-arc@...ts.infradead.org>
CC:	Vineet Gupta <Vineet.Gupta1@...opsys.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arc: dts - remove default value if
 CONFIG_ARC_BUILTIN_DTB_NAME is blank

> From: linux-snps-arc <linux-snps-arc-bounces@...ts.infradead.org> on behalf of Alexey Brodkin <Alexey.Brodkin@...opsys.com>
> Sent: Sunday, November 1, 2015 1:21 AM
> To: linux-snps-arc@...ts.infradead.org
> Cc: Vineet Gupta; Alexey Brodkin; linux-kernel@...r.kernel.org
> Subject: [PATCH] arc: dts - remove default value if CONFIG_ARC_BUILTIN_DTB_NAME is blank

> As of today default .dtb will be built (and subsequently will be built-in
> kernel binary) even if CONFIG_ARC_BUILTIN_DTB_NAME is not set.

> But it is possible we're going to use external .dtb and so we don't want to
have .dtb built-in kernel binary.

> For example that could be the case with:
> a) U-Boot which loads .dtb in DDR and passes its address to the kernel
> b) OpenWRT which embeds .dtb in existing kernel binary

> This change excludes .dtb building if CONFIG_ARC_BUILTIN_DTB_NAME is
blank.

You can add my Ack (worked on my platform)
Noam
--
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