Searched hist:"8 daebefe59e51bbf562d0e9726a5183d5d265d26" (Results 1 – 4 of 4) sorted by relevance
| /rk3399_ARM-atf/tools/memory/src/memory/ |
| H A D | printer.py | 8daebefe59e51bbf562d0e9726a5183d5d265d26 Tue Apr 15 13:00:50 UTC 2025 Chris Kay <chris.kay@arm.com> refactor(memmap)!: change behavioural flags to commands
This change factors out the following memory map tool flags into
independent commands:
- `--footprint` (becomes `memory footprint`)
- `--tree` (becomes `memory tree`)
- `--symbol` (becomes `memory symbol`)
So, for example, where previously you would generate the memory
footprint of a build with:
memory --tree
You would now instead use:
memory footprint
Any flags specific to a command (e.g. `--depth` for `tree`) must be
specified after the command, e.g.
memory tree --depth 1
... instead of:
memory --depth 1 tree
BREAKING-CHANGE: The image memory map visualization tool now uses
commands, rather than arguments, to determine the behaviour of the
script. See the commit message for further details.
Change-Id: I11d54d1f6276b8447bdfb8496544ab80399459ac
Signed-off-by: Chris Kay <chris.kay@arm.com>
|
| H A D | memmap.py | 8daebefe59e51bbf562d0e9726a5183d5d265d26 Tue Apr 15 13:00:50 UTC 2025 Chris Kay <chris.kay@arm.com> refactor(memmap)!: change behavioural flags to commands
This change factors out the following memory map tool flags into
independent commands:
- `--footprint` (becomes `memory footprint`)
- `--tree` (becomes `memory tree`)
- `--symbol` (becomes `memory symbol`)
So, for example, where previously you would generate the memory
footprint of a build with:
memory --tree
You would now instead use:
memory footprint
Any flags specific to a command (e.g. `--depth` for `tree`) must be
specified after the command, e.g.
memory tree --depth 1
... instead of:
memory --depth 1 tree
BREAKING-CHANGE: The image memory map visualization tool now uses
commands, rather than arguments, to determine the behaviour of the
script. See the commit message for further details.
Change-Id: I11d54d1f6276b8447bdfb8496544ab80399459ac
Signed-off-by: Chris Kay <chris.kay@arm.com>
|
| /rk3399_ARM-atf/docs/tools/ |
| H A D | memory-layout-tool.rst | 8daebefe59e51bbf562d0e9726a5183d5d265d26 Tue Apr 15 13:00:50 UTC 2025 Chris Kay <chris.kay@arm.com> refactor(memmap)!: change behavioural flags to commands
This change factors out the following memory map tool flags into
independent commands:
- `--footprint` (becomes `memory footprint`)
- `--tree` (becomes `memory tree`)
- `--symbol` (becomes `memory symbol`)
So, for example, where previously you would generate the memory
footprint of a build with:
memory --tree
You would now instead use:
memory footprint
Any flags specific to a command (e.g. `--depth` for `tree`) must be
specified after the command, e.g.
memory tree --depth 1
... instead of:
memory --depth 1 tree
BREAKING-CHANGE: The image memory map visualization tool now uses
commands, rather than arguments, to determine the behaviour of the
script. See the commit message for further details.
Change-Id: I11d54d1f6276b8447bdfb8496544ab80399459ac
Signed-off-by: Chris Kay <chris.kay@arm.com>
|
| /rk3399_ARM-atf/ |
| H A D | Makefile | 8daebefe59e51bbf562d0e9726a5183d5d265d26 Tue Apr 15 13:00:50 UTC 2025 Chris Kay <chris.kay@arm.com> refactor(memmap)!: change behavioural flags to commands
This change factors out the following memory map tool flags into
independent commands:
- `--footprint` (becomes `memory footprint`)
- `--tree` (becomes `memory tree`)
- `--symbol` (becomes `memory symbol`)
So, for example, where previously you would generate the memory
footprint of a build with:
memory --tree
You would now instead use:
memory footprint
Any flags specific to a command (e.g. `--depth` for `tree`) must be
specified after the command, e.g.
memory tree --depth 1
... instead of:
memory --depth 1 tree
BREAKING-CHANGE: The image memory map visualization tool now uses
commands, rather than arguments, to determine the behaviour of the
script. See the commit message for further details.
Change-Id: I11d54d1f6276b8447bdfb8496544ab80399459ac
Signed-off-by: Chris Kay <chris.kay@arm.com>
|