On Fri, 02 Nov 2012 06:41:36 +1100, Benjamin Herrenschmidt
wrote:
> On Thu, 2012-11-01 at 15:21 +0100, Grant Likely wrote:
>
> > I think this makes sense. Cyril and I are just talking about what he
> > needs. He wants to set aside per-device reserved regions and would
> > like to have the abilit
On Thu, 2012-11-01 at 15:21 +0100, Grant Likely wrote:
> I think this makes sense. Cyril and I are just talking about what he
> needs. He wants to set aside per-device reserved regions and would
> like to have the ability to reference a particular reserved region
> from a device node, probably wit
On Fri, Sep 21, 2012 at 12:10 AM, Benjamin Herrenschmidt
wrote:
> Hi folks !
>
> The reserve map is, imho, my biggest mistake when coming up with the FDT
> format.
>
> The main problem is that it doesn't survive the transition via a real
> Open Firmware interface. There is no practical way to indi
On Thu, 2012-09-20 at 20:35 -0500, Kumar Gala wrote:
> If you do this, please update the code in dtc/libfdt to construct the
> new nodes. We use this in u-boot to reserve kernel, dtb, initrd, etc
> regions. So would be nice to have drop in replacement code that could
> use same APIs if possible.
On Sep 20, 2012, at 5:10 PM, Benjamin Herrenschmidt wrote:
> Hi folks !
>
> The reserve map is, imho, my biggest mistake when coming up with the FDT
> format.
>
> The main problem is that it doesn't survive the transition via a real
> Open Firmware interface. There is no practical way to indica
Hi folks !
The reserve map is, imho, my biggest mistake when coming up with the FDT
format.
The main problem is that it doesn't survive the transition via a real
Open Firmware interface. There is no practical way to indicate reserved
regions of memory accross in that case, unless you have an OS t
