* emebedded ramdisk vs initrd
@ 2001-11-23 12:55 Guido Guenther
2001-11-23 13:22 ` Guido Guenther
2001-11-25 1:43 ` Ralf Baechle
0 siblings, 2 replies; 4+ messages in thread
From: Guido Guenther @ 2001-11-23 12:55 UTC (permalink / raw)
To: linux-mips; +Cc: ralf
[-- Attachment #1: Type: text/plain, Size: 275 bytes --]
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
[-- Attachment #2: ramdisk.diff --]
[-- Type: text/plain, Size: 346 bytes --]
--- arch/mips/Makefile.orig Fri Nov 23 13:43:52 2001
+++ arch/mips/Makefile Fri Nov 23 13:46:37 2001
@@ -111,7 +111,7 @@
# You need a compressed ramdisk image, named ramdisk.gz in
# arch/mips/ramdisk
#
-ifdef CONFIG_BLK_DEV_INITRD
+ifdef CONFIG_EMBEDDED_RAMDISK
CORE_FILES += arch/mips/ramdisk/ramdisk.o
SUBDIRS += arch/mips/ramdisk
endif
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emebedded ramdisk vs initrd
2001-11-23 12:55 emebedded ramdisk vs initrd Guido Guenther
@ 2001-11-23 13:22 ` Guido Guenther
2001-11-23 19:41 ` Pete Popov
2001-11-25 1:43 ` Ralf Baechle
1 sibling, 1 reply; 4+ messages in thread
From: Guido Guenther @ 2001-11-23 13:22 UTC (permalink / raw)
To: linux-mips
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.
-- Guido
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emebedded ramdisk vs initrd
2001-11-23 13:22 ` Guido Guenther
@ 2001-11-23 19:41 ` Pete Popov
0 siblings, 0 replies; 4+ messages in thread
From: Pete Popov @ 2001-11-23 19:41 UTC (permalink / raw)
To: Guido Guenther; +Cc: linux-mips
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: emebedded ramdisk vs initrd
2001-11-23 12:55 emebedded ramdisk vs initrd Guido Guenther
2001-11-23 13:22 ` Guido Guenther
@ 2001-11-25 1:43 ` Ralf Baechle
1 sibling, 0 replies; 4+ messages in thread
From: Ralf Baechle @ 2001-11-25 1:43 UTC (permalink / raw)
To: linux-mips
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-11-25 2:43 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-11-23 12:55 emebedded ramdisk vs initrd Guido Guenther
2001-11-23 13:22 ` Guido Guenther
2001-11-23 19:41 ` Pete Popov
2001-11-25 1:43 ` Ralf Baechle
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox