public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista•com>
To: Topi Kanerva <tkanerva@ees2•oulu.fi>
Cc: Zhaobin Zhu <zzhu@emc•com>, linuxppc-embedded@lists•linuxppc.org
Subject: Re: <kernel-image-name>
Date: Tue, 24 Oct 2000 14:04:46 -0700	[thread overview]
Message-ID: <39F5F96E.AAE39677@mvista.com> (raw)
In-Reply-To: Pine.GSO.4.21.0010231622560.25586-100000@stekt8


Topi,

I don't know what you're nfs problems are.

initrd is broken.  In the 2.4.0-test kernel (and probably others), some
necessary lines were removed from arch/ppc/boot/head.S.  I believe they have
been added back in the more recent source.  Here is a patch:

--- /opt/hardhat/devkit/lsp/sp8240/linux-2.4.0-test2/arch/ppc/boot/head.S
Sat Nov 27 16:41:59 1999
+++ head.S      Tue Oct 24 13:44:56 2000
@@ -112,6 +112,14 @@
        cmpi    0,r2,0
        bne     00b

+       /* r4,r5 have initrd_start, size */
+       lis     r2,initrd_start@h
+       ori     r2,r2,initrd_start@l
+       lwz     r4,0(r2)
+       lis     r2,initrd_end@h
+       ori     r2,r2,initrd_end@l
+       lwz     r5,0(r2)
+
        /* tell kernel we're prep */
        /*
         * get start address of kernel code which is stored as a coff



Also, the sandpoint_setup_arch() routine in arch/ppc/kernel/sandpoint_setup.c
needs to be fixed.  Change the SCSI_CDROM_MAJOR to RAMDISK_MAJOR.

These hacks should get your ramdisk going...

Mark
--


> Linux/PPC load: root=/dev/ram
>
> Any ideas what I'm doing wrong here? I've been up all day so when you're
> really tired, there's something really stupid I'm forgetting right now...
>
> I don't know why, but I seem to be the only one that cannot even make the
> damn stupid sandpoint to boot at *all*. Maybe I should get a job cleaning
> toilets instead...
>
> -topi

--
Mark A. Greer (mgreer@mvista•com; 480-517-0287)
MontaVista Software, Inc.
2141 E. Broadway Road, Suite 108
Tempe, AZ  85282


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-10-24 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-11 16:05 PCMCIA on the FADS Paolo Scaffardi
2000-10-13 19:47 ` <kernel-image-name> Zhaobin Zhu
2000-10-13 20:07   ` NFS boot hangs Zhaobin Zhu
2000-10-13 20:29   ` <kernel-image-name> Mark A. Greer
2000-10-24 12:55     ` <kernel-image-name> Topi Kanerva
2000-10-24 21:04       ` Mark A. Greer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39F5F96E.AAE39677@mvista.com \
    --to=mgreer@mvista$(echo .)com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=tkanerva@ees2$(echo .)oulu.fi \
    --cc=zzhu@emc$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox