linux-kernel - Re: [PATCH] Add rdc321x defconfig file

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: <20080225101433.GA30685@elte.hu>
Date:	Mon, 25 Feb 2008 11:14:33 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Florian Fainelli <florian.fainelli@...ecomint.eu>
Cc:	linux-kernel@...r.kernel.org, Adrian Bunk <bunk@...nel.org>,
	Sam Ravnborg <sam@...nborg.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] Add rdc321x defconfig file

* Florian Fainelli <florian.fainelli@...ecomint.eu> wrote:

> This patch adds the default kernel configuration for the RDC R-321x 
> SoC.

hm, i'm not sure. Right now we just have a 32-bit defconfig and a 64-bit 
defconfig - but there are about 8 subarchitectures in arch/x86. Given 
the amount of variety in PC hardware, i doubt it makes sense to start 
collecting defconfigs for hardware variants - we'd end up having 
hundreds or thousands of them. Even ARM has only 75 defconfigs.

what i do is i regularly test whether "make allyesconfig" boots all the 
way up to general user-space in regular whitebox PC hardware. For 
example the attached config is such a config, i successfully booted it 
on 2.6.25-rc3 on a stock PC.

This way we can ensure that the (near-) totality of the config space is 
bootable on regular PCs, and the subarch support is basically just 
bootstrap and quirks differences. Longer term we should get rid of the 
subarchitecture distinction altogether and turn them into regular 
quirks/callbacks/drivers.

In fact for rdc321x that should be rather easy to do right now: wdt.c 
could/should become a regular watchdog driver, and do we really need 
those GPIO specials in include/asm-x86/mach-rdc321x/ ? I believe it 
should be possible to boot CONFIG_X86_GENERICARCH on a rdc321x. Am i 
missing any particular complication?

	Ingo

View attachment "config-all-x86" of type "text/plain" (80598 bytes)