Re: [PATCH] Add rdc321x defconfig file

[Florian Fainelli <florian.fainelli@telecomint.eu>]

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]

Hi Ingo,

Le lundi 25 février 2008, Ingo Molnar a écrit :
> 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.

I was answering to Adrian Bunk's email about missing defconfigs for the x86 
subarchitecture boards.

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

Apart from selecting the 486 instruction subset, everything else should be 
allright though I had the habit to have a stripped down kernel for testing.

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

The GPIO calls will be moving later when I have finished the gpiolib 
integration for RDC just like what is currently done for ARM. You are right 
for the watchdog driver, I will move it right now.

>
> 	Ingo



-- 
Cordialement, Florian Fainelli
------------------------------

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]