| To: | linux-mips@oss.sgi.com |
|---|---|
| Subject: | Re: emebedded ramdisk vs initrd |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Sun, 25 Nov 2001 12:43:16 +1100 |
| In-reply-to: | <20011123135518.A12210@gandalf.physik.uni-konstanz.de>; from agx@sigxcpu.org on Fri, Nov 23, 2001 at 01:55:18PM +0100 |
| References: | <20011123135518.A12210@gandalf.physik.uni-konstanz.de> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Fri, Nov 23, 2001 at 01:55:18PM +0100, Guido Guenther wrote: > Trying to link in arch/mips/ramdisk/ramdisk.o whenever > CONFIG_BLK_DEV_INITRD is defined is a bad idea, since there are other > ways to use a ramdisk (bootloader, addinitrd). I suggest to use > CONFIG_EMBEDDED_RAMDISK instead , since it's already used by sibyte/swarm. Good idea, Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: FPU test on RedHat7.1, H . J . Lu |
|---|---|
| Next by Date: | FPU interrupt handler, William Lee Irwin III |
| Previous by Thread: | Re: emebedded ramdisk vs initrd, Pete Popov |
| Next by Thread: | [patch] linux: R3k DECstation FPU support, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |