| To: | Guido Guenther <agx@sigxcpu.org> |
|---|---|
| Subject: | Re: emebedded ramdisk vs initrd |
| From: | Pete Popov <ppopov@pacbell.net> |
| Date: | Fri, 23 Nov 2001 11:41:17 -0800 |
| Cc: | linux-mips@oss.sgi.com |
| In-reply-to: | <20011123142210.A32765@galadriel.physik.uni-konstanz.de> |
| References: | <20011123135518.A12210@gandalf.physik.uni-konstanz.de> <20011123142210.A32765@galadriel.physik.uni-konstanz.de> |
| Sender: | owner-linux-mips@oss.sgi.com |
On Fri, 2001-11-23 at 05:22, Guido Guenther wrote: > 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 > ...and therefore makes the compilation fail, I should add. You need a ramdisk.gz in arch/mips/ramdisk. It shouldn't fail then. I think you're right about the CONFIG_EMBEDDED_RAMDISK though. Pete |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [patch] linux: R3k DECstation FPU support, Maciej W. Rozycki |
|---|---|
| Next by Date: | advice on dz.c, William Lee Irwin III |
| Previous by Thread: | Re: emebedded ramdisk vs initrd, Guido Guenther |
| Next by Thread: | Re: emebedded ramdisk vs initrd, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |