From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Unified u-boot feature set for simpler distro support
Date: Mon, 5 Aug 2013 16:14:36 -0400 [thread overview]
Message-ID: <20130805201436.GU5164@bill-the-cat> (raw)
In-Reply-To: <20130805145059.14c35ebf@adria.ausil.us>
On Mon, Aug 05, 2013 at 02:50:59PM -0500, Dennis Gilmore wrote:
> On Mon, 05 Aug 2013 12:39:03 -0600
> Stephen Warren <swarren@wwwdotorg.org> wrote:
>
> > On 08/03/2013 01:11 AM, Dennis Gilmore wrote:
[snip]
> > > when it comes to memory addressing a distro and user shouldn't need
> > > to know anything. Ideally u-boot will auto allocate addresses based
> > > on the size of loaded objects. starting with a base address
> > > internal to u-boot you load a kernel, when loading an initramfs
> > > u-boot automatically calculates an address that ensures it does not
> > > overlap with the kernel. same for a fdt if loaded. I say auto
> > > calculated because what we think today will be enough room may not
> > > be tomorrow, dynamically calculating gives the flexibility for
> > > whatever may come.
> >
> > The way I've approached this for Tegra is to have the default
> > environment define certain standard environment variables that U-Boot
> > scripts can use, without a care. For example, the kernel should be
> > loaded at ${kernel_addr_r}, initrd at ${ramdisk_addr_r}, DTB at
> > ${fdt_addr_r}, etc.
> I really don't want to need to deal with variable names either. I
> really want to just say load a kernel initramfs and here is some
> arguments and have the rest just work.
Note that the pxe menu parsing code in turn relies on ${kernel_addr_r}
and ${ramdisk_addr_r} (and ${bootargs}) to know where to place what's
requested.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130805/78d5d651/attachment.pgp>
next prev parent reply other threads:[~2013-08-05 20:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 7:11 [U-Boot] Unified u-boot feature set for simpler distro support Dennis Gilmore
2013-08-03 10:08 ` Peter Maydell
2013-08-05 16:25 ` Tom Rini
2013-08-04 19:48 ` Wolfgang Denk
2013-08-04 23:02 ` Dennis Gilmore
2013-08-05 18:39 ` Stephen Warren
2013-08-05 18:48 ` Stephen Warren
2013-08-05 20:26 ` Dennis Gilmore
2013-08-05 20:54 ` Stephen Warren
2013-08-05 19:50 ` Dennis Gilmore
2013-08-05 20:14 ` Tom Rini [this message]
2013-08-05 20:21 ` Stephen Warren
2013-08-05 20:43 ` Wolfgang Denk
2013-08-05 20:49 ` Stephen Warren
2013-08-05 21:00 ` Tom Rini
2013-08-05 21:09 ` Stephen Warren
2013-08-05 21:20 ` Tom Rini
2013-08-05 21:08 ` Dennis Gilmore
2013-08-05 22:06 ` Stephen Warren
2013-08-06 11:34 ` Wolfgang Denk
2013-08-05 19:01 ` Tom Rini
2013-08-05 20:11 ` Dennis Gilmore
2013-08-05 20:25 ` Tom Rini
2013-08-05 20:54 ` Dennis Gilmore
2013-08-05 21:02 ` Tom Rini
2013-08-05 20:45 ` Stephen Warren
2013-08-08 18:48 ` Dirk Müller
2013-08-08 20:01 ` Stephen Warren
2013-08-08 20:37 ` Tom Rini
2013-08-13 12:23 ` Dirk Müller
2013-08-10 21:02 ` Dennis Gilmore
2013-08-09 22:20 ` Stephen Warren
2013-08-09 22:49 ` Wolfgang Denk
2013-08-09 23:00 ` Stephen Warren
2013-08-10 4:35 ` Stephen Warren
2013-08-10 21:07 ` Dennis Gilmore
2013-08-12 13:56 ` Tom Rini
2013-08-10 10:11 ` Wolfgang Denk
2013-08-10 14:29 ` Adam Conrad
2013-08-10 21:05 ` Dennis Gilmore
2013-08-13 13:42 ` Tom Rini
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=20130805201436.GU5164@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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