linux-kernel - Re: ARM defconfig files

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]

Message-ID: <1275641579.1931.939.camel@pasglop>
Date:	Fri, 04 Jun 2010 18:52:59 +1000
From:	Benjamin Herrenschmidt <benh@....ibm.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Russell King <rmk@....linux.org.uk>,
	Tony Lindgren <tony@...mide.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Kevin Hilman <khilman@...prootsystems.com>,
	Daniel Walker <dwalker@...eaurora.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arm-msm@...r.kernel.org
Subject: Re: ARM defconfig files

On Fri, 2010-06-04 at 08:30 +0200, Geert Uytterhoeven wrote:
> 
> > warrant a different thread. However it's interesting because we do
> that
> > quite well on powerpc :-)
> 
> So you could easily have one big common defconfig... 

Well, there are things we still don't allow in one binary, and I suspect
it would be nasty on ARM too, such as widely different core arch (which
in ARM land would translate into widely different ARM architecture
version).

But yeah, we can pretty much make giant defconfigs. They are not very
useful tho. In the embedded world, size constraints are quite strong and
so you really need to be able to target only the subset of things you
want for some types of devices.

Of course, for things like ARM netbooks, it would be nice to have one
giant defconfig that boots them all, and that's probably an achievable
goal if the variants between bootloaders can be sorted out.

Cheers,
Ben.

--
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/