From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
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: Thu, 20 May 2010 10:23:53 +1000 [thread overview]
Message-ID: <1274315033.1931.25.camel@pasglop> (raw)
In-Reply-To: <AANLkTilefxXcMnWqKSultu88r4D9W98adHLHxvUwi113@mail.gmail.com>
On Wed, 2010-05-19 at 19:03 -0500, Timur Tabi wrote:
> 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.
I don't see why we couldn't add a callback to libfdt for allocation /
reallocation.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Timur Tabi <timur-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: linuxppc-dev-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] powerpc: make the padding for the device tree a configurable option
Date: Thu, 20 May 2010 10:23:53 +1000 [thread overview]
Message-ID: <1274315033.1931.25.camel@pasglop> (raw)
In-Reply-To: <AANLkTilefxXcMnWqKSultu88r4D9W98adHLHxvUwi113-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, 2010-05-19 at 19:03 -0500, Timur Tabi wrote:
> 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.
I don't see why we couldn't add a callback to libfdt for allocation /
reallocation.
Cheers,
Ben.
next prev parent reply other threads:[~2010-05-20 0:24 UTC|newest]
Thread overview: 24+ 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 19:53 ` Timur Tabi
2010-05-19 21:20 ` Benjamin Herrenschmidt
2010-05-19 21:20 ` Benjamin Herrenschmidt
2010-05-19 21:33 ` Timur Tabi
2010-05-19 21:33 ` Timur Tabi
2010-05-19 22:44 ` Benjamin Herrenschmidt
2010-05-19 22:44 ` Benjamin Herrenschmidt
2010-05-20 0:03 ` Timur Tabi
2010-05-20 0:03 ` Timur Tabi
2010-05-20 0:23 ` Benjamin Herrenschmidt [this message]
2010-05-20 0:23 ` Benjamin Herrenschmidt
2010-05-20 0:36 ` M. Warner Losh
2010-05-20 0:36 ` M. Warner Losh
2010-05-20 1:18 ` David Gibson
2010-05-20 1:18 ` David Gibson
2010-05-20 1:46 ` Timur Tabi
2010-05-20 1:46 ` Timur Tabi
2010-05-20 6:17 ` David Gibson
2010-05-20 6:17 ` David Gibson
2010-05-20 11:40 ` Timur Tabi
2010-05-20 11:40 ` Timur Tabi
2010-05-20 16:04 ` Scott Wood
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=1274315033.1931.25.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.