linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mikhail Zaturenskiy <mzaturenskiy.st@gmail.com>
To: "Frank Svendsbøe" <frank.svendsboe@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: RAMDISK on EP88xc
Date: Thu, 2 Jul 2009 08:43:43 -0500	[thread overview]
Message-ID: <97dd5fd20907020643s52cc65aah8ee315c3592d5e1@mail.gmail.com> (raw)
In-Reply-To: <1ba63b520907020010u46a3b495h79672fc4f6d84c14@mail.gmail.com>

On Thu, Jul 2, 2009 at 2:10 AM, Frank
Svendsb=F8e<frank.svendsboe@gmail.com> wrote:
> On Wed, Jul 1, 2009 at 10:14 PM, Mikhail
> Zaturenskiy<mzaturenskiy.st@gmail.com> wrote:
> Hmm... according to "Kernel command line: console=3DttyCPM0,9600n8
> loglevel=3D7" you haven't
> specified where root is. Add root=3D/dev/ram to the kernel command line,
> and specify where the
> init process is located (for instance init=3D/sbin/init).
>
> I haven't tried Denks ramdisk image. You can create one for yourself
> using dd, gzip and U-Boots
> mkimage tool. If the ramdisk image is larger than 4MB, you must either
> change the default
> CONFIG_BLK_DEV_RAM_SIZE=3D4096, or set ramdisk size in the kernel command=
 line.
>
> Btw, I use an older kernel than you use, but I have these defined:
> CONFIG_BLK_DEV=3Dy
> CONFIG_BLK_DEV_LOOP=3Dy
> CONFIG_BLK_DEV_RAM=3Dy
> CONFIG_BLK_DEV_RAM_COUNT=3D16
> CONFIG_BLK_DEV_RAM_SIZE=3D4096
>
> Maybe they're obsolete now, but you can try to add them to your defconfig=
 file.
>
> Good luck ;-)
>

Thanks Frank, this seems to be leading me down the right path. I tried
some of those defines out yesterday and they got the kernel to at
least attempt to load the ramdisk, so I'm getting somewhere. Also
added root=3D/dev/ram (also tried /dev/ram0) and init=3D/sbin/init but for
now things are failing before processing those args.

I haven't tried CONFIG_BLK_DEV or CONFIG_BLK_DEV_LOOP and am still
playing around with the values for CONFIG_BLK_DEV_RAM_COUNT and
CONFIG_BLK_DEV_RAM_SIZE. Strangely, the DEV_RAM defines are completely
missing from my config so I have to put them in manually... (as
opposed to via menuconfig). I'll post back when it's working or when
I've tried all of this and still am getting some error.

Meanwhile a side question - why does BLK_DEV_RAM_COUNT default to 16?

  reply	other threads:[~2009-07-02 13:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 18:04 RAMDISK on EP88xc Mikhail Zaturenskiy
2009-07-01 19:52 ` Frank Svendsbøe
2009-07-01 20:14   ` Mikhail Zaturenskiy
2009-07-02  7:10     ` Frank Svendsbøe
2009-07-02 13:43       ` Mikhail Zaturenskiy [this message]
2009-07-02 13:54         ` Gary Thomas
2009-07-02 16:27           ` Mikhail Zaturenskiy
2009-07-02 18:42             ` Mikhail Zaturenskiy
2009-07-02 19:11               ` Mikhail Zaturenskiy
2009-07-02 20:38               ` Frank Svendsbøe
2009-07-02 21:38                 ` Mikhail Zaturenskiy
2009-07-02 21:49                   ` Scott Wood
2009-07-02 21:57                     ` Mikhail Zaturenskiy
2009-07-06 18:29                     ` Mikhail Zaturenskiy
2009-07-06 18:38                       ` Scott Wood
2009-07-06 18:50                         ` Mikhail Zaturenskiy
2009-07-06 18:57                           ` Scott Wood
2009-07-06 19:01                           ` Scott Wood
2009-07-06 19:28                             ` Mikhail Zaturenskiy
2009-07-06 20:15                               ` Scott Wood
2009-07-06 20:18                                 ` Scott Wood
2009-07-06 20:26                                   ` Mikhail Zaturenskiy

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=97dd5fd20907020643s52cc65aah8ee315c3592d5e1@mail.gmail.com \
    --to=mzaturenskiy.st@gmail.com \
    --cc=frank.svendsboe@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).