From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fdt: add fdtcmd env var to allow post processing of device tree before boot
Date: Tue, 05 Aug 2008 00:53:42 +0200 [thread overview]
Message-ID: <20080804225342.4657C24848@gemini.denx.de> (raw)
In-Reply-To: Your message of "Mon, 04 Aug 2008 17:18:36 CDT." <8A440031-0ADE-4AC5-84C3-C0D58583493A@kernel.crashing.org>
In message <8A440031-0ADE-4AC5-84C3-C0D58583493A@kernel.crashing.org> you wrote:
>
> > Why not? Wouldn't it be just another environment variable, like the
> > load address for the kernel?
>
> Right now the fdt is placed at the first 4k page after the kernel is
> decompressed. I don't now where that address is.
Who places it there?
We were talking about the bootm arguments, which are different
things, I think?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
That Microsoft, the Trabant of the operating system world, may be
glancing over the Berlin Wall at the Audis and BMWs and Mercedes. In
their own universe Trabants and Ladas were mainstream too...
-- Evan Leibovitch
next prev parent reply other threads:[~2008-08-04 22:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 18:46 [U-Boot-Users] [PATCH] fdt: add fdtcmd env var to allow post processing of device tree before boot Kumar Gala
2008-08-04 18:56 ` Wolfgang Denk
2008-08-04 19:49 ` Kumar Gala
2008-08-04 20:19 ` Jerry Van Baren
2008-08-04 20:24 ` Kumar Gala
2008-08-04 20:44 ` Jerry Van Baren
2008-08-04 20:52 ` Kumar Gala
2008-08-04 21:04 ` Wolfgang Denk
2008-08-04 20:27 ` Wolfgang Denk
2008-08-04 20:50 ` Kumar Gala
2008-08-04 20:55 ` Scott Wood
2008-08-04 22:18 ` Kumar Gala
2008-08-04 22:21 ` Scott Wood
2008-08-04 22:53 ` Wolfgang Denk [this message]
2008-08-04 21:07 ` Wolfgang Denk
2008-08-04 22:23 ` Kumar Gala
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=20080804225342.4657C24848@gemini.denx.de \
--to=wd@denx.de \
--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