From: Sébastien Côté <scote1@matrox.com>
To: mgreer@mvista.com
Cc: LinuxPPC-embedded list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: initrd problems
Date: Fri, 19 Jan 2001 09:53:18 -0500 [thread overview]
Message-ID: <3A6854DD.A370D56B@matrox.com> (raw)
In-Reply-To: 3A6794B1.D0B70C1C@mvista.com
"Mark A. Greer" wrote:
>
> Where did you get this version of that kernel? From the MontaVista CDK or from
> the website? If from the website, when did you get it?
I'm pretty sure it came from the web.. I think it was downloaded at the
end of November but I can't be sure... I could probably answer this
next week.
> Try this (if its not already done). Go into arch/ppc/boot/head.S and add the
> following lines after the set up of r6 to hold the cmd_line.
>
> /* 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)
>
> Go into arch/ppc/kernel/sandpoint_setup.c. Find sandpoint_setup_arch() and add
> something like (again, if its not already there).
>
> #ifdef CONFIG_BLK_DEV_INITRD
> if (initrd_start)
> ROOT_DEV = MKDEV(RAMDISK_MAJOR, 0);
>
> #endif
>
I tried that patch that I found in the list archives but it didn't make
any difference.
Sébastien Côté
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-19 14:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 15:53 initrd problems Sébastien Côté
2001-01-18 22:27 ` Sébastien Côté
2001-01-18 20:01 ` Matt Porter
2001-01-19 17:22 ` Sébastien Côté
2001-01-20 14:35 ` Matt Porter
2001-01-22 18:56 ` Sébastien Côté
2001-01-22 19:24 ` Kyle Harris
2001-01-22 20:45 ` Sébastien Côté
2001-01-19 1:13 ` Mark A. Greer
2001-01-19 14:53 ` Sébastien Côté [this message]
2001-01-23 21:03 ` Michael Pruznick
-- strict thread matches above, loose matches on Subject: below --
2002-10-30 16:28 Anders Blomdell
2002-10-30 16:47 ` Wolfgang Denk
2003-04-24 5:32 Sriram Narasimhan
2003-04-24 7:35 ` Wolfgang Denk
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=3A6854DD.A370D56B@matrox.com \
--to=scote1@matrox.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgreer@mvista.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).