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: <20080225105110.GA5648@elte.hu>
Date:	Mon, 25 Feb 2008 11:51:10 +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:

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

ok, great! Btw., do you think you could achieve your board to boot fine 
with CONFIG_X86_GENERICARCH=y and CONFIG_M486=y?

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