| commit | cfaadf0e89e7c2a47462d5f96390c9a9b4de037c | |
| author | Laszlo Ersek <lersek@redhat.com> | |
| Mon, 22 Dec 2014 12:11:40 +0000 (22 13:11 +0100) | ||
| committer | Peter Maydell <peter.maydell@linaro.org> | |
| Mon, 22 Dec 2014 23:39:18 +0000 (22 23:39 +0000) | ||
| tree | 7ba58b6d1544b93a9a6be7e3d73d2286f3163d29 | treesnapshot (tar.gz zip) |
| parent | ff6cff7554be06e95f8d712f66cd16bd6681c746 | commitdiff |
fw_cfg_mem: introduce the "data_width" property
The "data_width" property is capable of changing the maximum valid access
size to the MMIO data register, and resizes the memory region similarly,
at device realization time.
The default value of "data_memwidth" is set so that we don't yet diverge
from "fw_cfg_data_mem_ops".
Most of the fw_cfg_mem users will stick with the default, and for them we
should continue using the statically allocated "fw_cfg_data_mem_ops". This
is beneficial for debugging because gdb can resolve pointers referencing
static objects to the names of those objects.
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-id: 1419250305-31062-7-git-send-email-pbonzini@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
The "data_width" property is capable of changing the maximum valid access
size to the MMIO data register, and resizes the memory region similarly,
at device realization time.
The default value of "data_memwidth" is set so that we don't yet diverge
from "fw_cfg_data_mem_ops".
Most of the fw_cfg_mem users will stick with the default, and for them we
should continue using the statically allocated "fw_cfg_data_mem_ops". This
is beneficial for debugging because gdb can resolve pointers referencing
static objects to the names of those objects.
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-id: 1419250305-31062-7-git-send-email-pbonzini@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
| hw/nvram/fw_cfg.c | diffblobblamehistory |