| commit | 28290f37e20cda27574f15be9e9499493e3d0fe8 | |
| author | Alexander Graf <agraf@suse.de> | |
| Fri, 19 Jul 2013 10:56:24 +0000 (19 12:56 +0200) | ||
| committer | Alexander Graf <agraf@suse.de> | |
| Mon, 2 Sep 2013 08:06:40 +0000 (2 10:06 +0200) | ||
| tree | 6677dae209284617bf2feaadd8c0afe1e5d80d73 | treesnapshot (tar.gz zip) |
| parent | 4ff78e0dbcd5c795962567fdc1b31e9e03c55b07 | commitdiff |
PPC: E500: Generate device tree on reset
Today we generate the device tree once on machine initialization and then
store the finalized blob in memory to reload it on reset.
This is bad for 2 reasons. First we potentially waste a bunch of RAM for no
good reason, as we have all information required to regenerate the device
tree available anyways.
The second reason is even more important. On machine init when we generate
the device tree for the first time, we don't have all of the devices fully
initialized yet. But the device tree needs to potentially walk devices to
put information about them into the device tree.
Move the generation into a reset function. That way we just generate it new
every time we reset, solving both of the above issues.
Signed-off-by: Alexander Graf <agraf@suse.de>
Today we generate the device tree once on machine initialization and then
store the finalized blob in memory to reload it on reset.
This is bad for 2 reasons. First we potentially waste a bunch of RAM for no
good reason, as we have all information required to regenerate the device
tree available anyways.
The second reason is even more important. On machine init when we generate
the device tree for the first time, we don't have all of the devices fully
initialized yet. But the device tree needs to potentially walk devices to
put information about them into the device tree.
Move the generation into a reset function. That way we just generate it new
every time we reset, solving both of the above issues.
Signed-off-by: Alexander Graf <agraf@suse.de>
| hw/ppc/e500.c | diffblobblamehistory |