All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilkinson <kinsham@verizon.net>
To: buildroot@busybox.net
Subject: [Buildroot] Creating initrd
Date: Thu, 11 Oct 2012 11:16:09 -0400	[thread overview]
Message-ID: <1349968569.14474.10.camel@Homeserver> (raw)
In-Reply-To: <20121011164826.753f8312@skate>

The .config is here

http://pastebin.com/84LqnBXS

This shows what I'm trying to achieve.

http://d-i.alioth.debian.org/manual/en.armel/ch05s01.html#boot-firmware. 

The output on the serial console goes like this on power up.

>>
No network interfaces found

EM-7210 ver.T04 2005-12-12 (For ver.AA)
== Executing boot script in 1.000 seconds - enter ^C to abort

At this point, hit Control-C to interrupt the boot loader[4]. This will
give you the RedBoot prompt. Enter the following commands:

> load -v -r -b 0x01800000 -m ymodem ramdisk.gz
> load -v -r -b 0x01008000 -m ymodem zImage
> exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M at 0xa0000000" -r
0x01800000

Chris
On Thu, 2012-10-11 at 16:48 +0200, Thomas Petazzoni wrote:
> Dear Chris Wilkinson,
> 
> On Thu, 11 Oct 2012 10:05:03 -0400, Chris Wilkinson wrote:
> > I haven't been able to figure out how to get BR to create an initial
> > ramdisk.
> > 
> > I selected initramfs in Filesystem images. What I end up with is
> > 
> > -rw-r--r-- 1 chrisw chrisw 38356992 Oct 11 09:00 rootfs.cpio
> > -rw-r--r-- 1 chrisw chrisw 13666196 Oct 11 09:00 rootfs.cpio.gz
> > -rw-r--r-- 1 chrisw chrisw 48346112 Oct 11 09:00 rootfs.ext2
> > -rw-r--r-- 1 chrisw chrisw 13990321 Oct 11 09:00 rootfs.ext2.gz
> > -rwxr-xr-x 1 chrisw chrisw  1422576 Oct 11 09:01 zImage
> > 
> > There is no initrd and the rootfs is way too big for flash.
> 
> Forget about initrd, nobody uses that anymore.
> 
> Can you post your entire .config?
> 
> Thanks,
> 
> Thomas

  reply	other threads:[~2012-10-11 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11 14:05 [Buildroot] Creating initrd Chris Wilkinson
2012-10-11 14:48 ` Thomas Petazzoni
2012-10-11 15:16   ` Chris Wilkinson [this message]
2012-10-11 15:23     ` Thomas Petazzoni
2012-10-11 17:28       ` Chris Wilkinson
2012-10-11 18:53         ` Thomas Petazzoni
     [not found]           ` <1349988968.14474.34.camel@Homeserver>
     [not found]             ` <20121012091408.6184bb9f@skate>
     [not found]               ` <1350049738.14474.52.camel@Homeserver>
2012-10-12 14:12                 ` Thomas Petazzoni
2012-10-12 15:19                   ` Chris Wilkinson
2012-10-12 14:23                 ` Thomas Petazzoni
2012-10-11 21:45       ` Chris Wilkinson
2012-10-12  7:10         ` Thomas Petazzoni

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=1349968569.14474.10.camel@Homeserver \
    --to=kinsham@verizon.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.