LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: linuxppc-dev@lists.ozlabs.org
Subject: Booting with ramdisk in kernel
Date: Tue, 22 Mar 2011 12:04:12 +0100	[thread overview]
Message-ID: <201103221204.12376.dargaud@lpsc.in2p3.fr> (raw)

Hello all,
I already posted this on the buildroot mailing list, so apologies for the dupe, but maybe it's more relevant here.

I'm trying to do something very classic, but it doesn't seem to work and the more I read about it the more I'm confused 
by the amount of antiquated info and nearly-but-not-quite-so relevant info (like doing a temporary ramdisk before the 
'real' OS loads).

So I have a kernel and a buildroot-generated OS, currently on an NFS server. I boot with the following kernel parameters 
and everything goes fine:
console=ttyUL0,115200 rw root=/dev/nfs ip=bootp

Now I want to embed that OS in the kernel (no need for a network anymore as the kernel is on a flash mem and I wrote my 
own bootloader). So I did the following:
- add ROOTFS CPIO to the buildroot options and make a new version
- point CONFIG_INITRAMFS_SOURCE to the resulting rootfs.cpio file
- change the kernel parameters to "console=ttyUL0,115200 root=/dev/ram" (that's in a dts file)
- some documentation talks about CONFIG_BLK_DEV_RAM but I can't find that option in the menuconfig, so maybe that's the 
problem.

When my bootloader jumps to 0x400000, the kernel stops instantly without even a blip on the console. A debugger reveals 
that it stops at 0x401718... I have no idea what's going on at this stage.

What am I doing wrong ?
-- 
Guillaume Dargaud
http://www.gdargaud.net/

                 reply	other threads:[~2011-03-22 11:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201103221204.12376.dargaud@lpsc.in2p3.fr \
    --to=dargaud@lpsc.in2p3.fr \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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