| To: | linux-mips@oss.sgi.com |
|---|---|
| Subject: | emebedded ramdisk vs initrd |
| From: | Guido Guenther <agx@sigxcpu.org> |
| Date: | Fri, 23 Nov 2001 13:55:18 +0100 |
| Cc: | ralf@gnu.org |
| Mail-followup-to: | linux-mips@oss.sgi.com, ralf@gnu.org |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
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. -- Guido
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: TrueColor on an Indy, Guido Guenther |
|---|---|
| Next by Date: | Re: emebedded ramdisk vs initrd, Guido Guenther |
| Previous by Thread: | Failure to remote debug MIPS kernel modules..., Steven J. Hill |
| Next by Thread: | Re: emebedded ramdisk vs initrd, Guido Guenther |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
