linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Mirek23 <miroslaw.dach@psi.ch>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: U-boot and linux command line parameters
Date: Mon, 25 May 2009 10:06:18 +1000	[thread overview]
Message-ID: <20090525000618.GD8059@yookeroo.seuss> (raw)
In-Reply-To: <23698384.post@talk.nabble.com>

On Sun, May 24, 2009 at 02:38:52PM -0700, Mirek23 wrote:
> 
> Dear All,
> 
> I use linux kernel 2.6.23 and u-boot 1.2.0 (on ppc405 virtex-4 ) for
> some time. All works fine when the kernel together with initramfs is
> smaller than 8MB. If it is bigger than the kernel does not boot
> properly.
> 
> First of all I would like to know how the address for the linux
> command line parameters is "transferred" from u-boot to linux for
> ppc405 (virtex4 chip)?  (via some registers or is it a fixed address
> in the memory ie. 8MB?)  Does somebody know what should be changed,
> in the kernel, in order to move this limitation from 8MB to let say
> 12MB? I would be grateful for any hint.

IIRC, U-boot 1.2.0 is a version of u-boot before it became device tree
aware.  Which means if I'm reading the cuboot.c code correctly, the
command line address is passed to the kernel at entry in r6, with the
length in r7.  With later, device-tree aware u-boot versions, the
command line is instead passed as a device tree property.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  parent reply	other threads:[~2009-05-25  0:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 21:38 U-boot and linux command line parameters Mirek23
2009-05-24 21:41 ` Hunter Cobbs
2009-05-25  0:06 ` David Gibson [this message]
2009-05-25  8:41   ` Mirek23
2009-05-25 17:54     ` Wolfgang Denk
2009-05-25 20:40     ` Mirek23

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=20090525000618.GD8059@yookeroo.seuss \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=miroslaw.dach@psi.ch \
    /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).