From: Timur Tabi <timur@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] powerpc: make the padding for the device tree a configurable option
Date: Wed, 19 May 2010 19:03:17 -0500 [thread overview]
Message-ID: <AANLkTilefxXcMnWqKSultu88r4D9W98adHLHxvUwi113@mail.gmail.com> (raw)
In-Reply-To: <1274309050.1931.21.camel@pasglop>
On Wed, May 19, 2010 at 5:44 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> It's still not kernel business to have to deal with u-boot memory
> allocation constraints.
I agree, but it still makes sense to me to allow the padding to be configurable.
> The padding in the kernel built is intended to
> make space for DT changes done by the zImage wrapper.
Well, okay. I think it would be nice if we expanded that to handle
general usage.
> Maybe we could add to libfdt a way to provide a realloc() callback to it
> when it hits the max size, and uboot can then move things around (or
> fail).
The problem is that the code which allocates a block for the fdt is
completely distinct from the code that manipulates the fdt. We'd need
to put in either some kind of funky callback mechanism, or insist that
every fdt exist in a block of memory allocated by some specific method
(e.g. lmb).
I'm stuck between a rock and a hard place, it seems. No one is
willing to compromise on any of my ideas. It's hard to convince our
BSP developers that they should be pushing more code upstream when I
get so much resistance for a such a mundane change.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-05-20 0:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 19:53 [PATCH] powerpc: make the padding for the device tree a configurable option Timur Tabi
2010-05-19 21:20 ` Benjamin Herrenschmidt
2010-05-19 21:33 ` Timur Tabi
2010-05-19 22:44 ` Benjamin Herrenschmidt
2010-05-20 0:03 ` Timur Tabi [this message]
2010-05-20 0:23 ` Benjamin Herrenschmidt
2010-05-20 0:36 ` M. Warner Losh
2010-05-20 1:18 ` David Gibson
2010-05-20 1:46 ` Timur Tabi
2010-05-20 6:17 ` David Gibson
2010-05-20 11:40 ` Timur Tabi
2010-05-20 16:04 ` Scott Wood
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=AANLkTilefxXcMnWqKSultu88r4D9W98adHLHxvUwi113@mail.gmail.com \
--to=timur@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@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).