* Re: Intial ramdisk and kernel
@ 2003-12-23 23:58 Ashwin Bihari
2003-12-24 2:11 ` Matt Porter
0 siblings, 1 reply; 5+ messages in thread
From: Ashwin Bihari @ 2003-12-23 23:58 UTC (permalink / raw)
To: mporter; +Cc: linuxppc-embedded
>With the stock firmware on a PrPMC800, yes, you have to attach the
>ramdisk to the kernel. You do this by copying the compressed ramdisk
>image to arch/ppc/boot/images/ramdisk.image.gz. Then do a
>'make zImage.initrd'. That will deposit a zImage+initrd image into
>arch/ppc/boot/images/.
Matt,
Ahh OK. Thank you for the details.
>If you have a U-boot port to your board then you can be a lot more
>flexible since it can load a kernel image and ramdisk separately.
>
>-Matt
We are using PPCBug actually. Not sure if you're familiar with it's
capabilities in comparison to U-boot in ramdisk booting ability.
~ Ashwin
_________________________________________________________________
Make your home warm and cozy this winter with tips from MSN House & Home.
http://special.msn.com/home/warmhome.armx
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Intial ramdisk and kernel
2003-12-23 23:58 Intial ramdisk and kernel Ashwin Bihari
@ 2003-12-24 2:11 ` Matt Porter
0 siblings, 0 replies; 5+ messages in thread
From: Matt Porter @ 2003-12-24 2:11 UTC (permalink / raw)
To: Ashwin Bihari; +Cc: mporter, linuxppc-embedded
On Tue, Dec 23, 2003 at 06:58:01PM -0500, Ashwin Bihari wrote:
> >With the stock firmware on a PrPMC800, yes, you have to attach the
> >ramdisk to the kernel. You do this by copying the compressed ramdisk
> >image to arch/ppc/boot/images/ramdisk.image.gz. Then do a
> >'make zImage.initrd'. That will deposit a zImage+initrd image into
> >arch/ppc/boot/images/.
>
> Matt,
>
> Ahh OK. Thank you for the details.
>
> >If you have a U-boot port to your board then you can be a lot more
> >flexible since it can load a kernel image and ramdisk separately.
> >
> >-Matt
>
> We are using PPCBug actually. Not sure if you're familiar with it's
> capabilities in comparison to U-boot in ramdisk booting ability.
Yes, very familiar with PPCBug. That is the "stock firmware" I
mentioned above. The resultant zImage+initrd image is bootable
from PPCBug.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Intial ramdisk and kernel
@ 2003-12-24 5:04 Ashwin Bihari
0 siblings, 0 replies; 5+ messages in thread
From: Ashwin Bihari @ 2003-12-24 5:04 UTC (permalink / raw)
To: mporter; +Cc: linuxppc-embedded
> > We are using PPCBug actually. Not sure if you're familiar with it's
> > capabilities in comparison to U-boot in ramdisk booting ability.
>
>Yes, very familiar with PPCBug. That is the "stock firmware" I
>mentioned above. The resultant zImage+initrd image is bootable from
>PPCBug.
Matt,
Very good to hear! I will give it a shot after Christmas. Thanks once again.
Happy holidays.
~~ Ashwin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Intial ramdisk and kernel
@ 2003-12-23 21:54 Ashwin Bihari
2003-12-23 23:50 ` Matt Porter
0 siblings, 1 reply; 5+ messages in thread
From: Ashwin Bihari @ 2003-12-23 21:54 UTC (permalink / raw)
To: linuxppc-embedded
Greetings,
I'm tring to create an initial ramdisk to use for the purpose of installing
a root file system on an empty hard drive. I've gotten the INITRD made by
using the methods described in the initrd.txt file located in the
Documentation directory under the Linux sources.
>From my reading these lists and other forums, it seems that with the PPC
platform, I have to compile the INITRD into the kernel, how do I go about
doing this???
I'm using a PrPMC800 based installation. Any and all help appreciated.
~Ashwin
_________________________________________________________________
Get reliable dial-up Internet access now with our limited-time introductory
offer. http://join.msn.com/?page=dept/dialup
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Intial ramdisk and kernel
2003-12-23 21:54 Ashwin Bihari
@ 2003-12-23 23:50 ` Matt Porter
0 siblings, 0 replies; 5+ messages in thread
From: Matt Porter @ 2003-12-23 23:50 UTC (permalink / raw)
To: Ashwin Bihari; +Cc: linuxppc-embedded
On Tue, Dec 23, 2003 at 04:54:42PM -0500, Ashwin Bihari wrote:
> >From my reading these lists and other forums, it seems that with the PPC
> platform, I have to compile the INITRD into the kernel, how do I go about
> doing this???
>
> I'm using a PrPMC800 based installation. Any and all help appreciated.
With the stock firmware on a PrPMC800, yes, you have to attach the
ramdisk to the kernel. You do this by copying the compressed ramdisk
image to arch/ppc/boot/images/ramdisk.image.gz. Then do a
'make zImage.initrd'. That will deposit a zImage+initrd image into
arch/ppc/boot/images/.
If you have a U-boot port to your board then you can be a lot more
flexible since it can load a kernel image and ramdisk separately.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-12-24 5:04 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-12-23 23:58 Intial ramdisk and kernel Ashwin Bihari
2003-12-24 2:11 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2003-12-24 5:04 Ashwin Bihari
2003-12-23 21:54 Ashwin Bihari
2003-12-23 23:50 ` Matt Porter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).