From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53315) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y31qM-0000F6-9Y for qemu-devel@nongnu.org; Mon, 22 Dec 2014 07:12:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y31qG-00028K-6H for qemu-devel@nongnu.org; Mon, 22 Dec 2014 07:12:10 -0500 Received: from mx1.redhat.com ([209.132.183.28]:47963) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y31qF-00028G-Vf for qemu-devel@nongnu.org; Mon, 22 Dec 2014 07:12:04 -0500 From: Paolo Bonzini Date: Mon, 22 Dec 2014 13:11:37 +0100 Message-Id: <1419250305-31062-4-git-send-email-pbonzini@redhat.com> In-Reply-To: <1419250305-31062-1-git-send-email-pbonzini@redhat.com> References: <1419250305-31062-1-git-send-email-pbonzini@redhat.com> Subject: [Qemu-devel] [PATCH v6 03/11] fw_cfg_mem: max access size and region size are the same for data register List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: peter.maydell@linaro.org, qemu-devel@nongnu.org, rjones@redhat.com, drjones@redhat.com, lersek@redhat.com, agraf@suse.de From: Laszlo Ersek Make it clear that the maximum access size to the MMIO data register determines the full size of the memory region. Currently the max access size is 1. This patch doesn't change behavior. Signed-off-by: Laszlo Ersek Signed-off-by: Paolo Bonzini --- hw/nvram/fw_cfg.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hw/nvram/fw_cfg.c b/hw/nvram/fw_cfg.c index c48bc6e..8deb860 100644 --- a/hw/nvram/fw_cfg.c +++ b/hw/nvram/fw_cfg.c @@ -31,7 +31,6 @@ #include "qemu/config-file.h" #define FW_CFG_SIZE 2 -#define FW_CFG_DATA_SIZE 1 #define FW_CFG_NAME "fw_cfg" #define FW_CFG_PATH "/machine/" FW_CFG_NAME @@ -694,7 +693,8 @@ static void fw_cfg_mem_realize(DeviceState *dev, Error **errp) sysbus_init_mmio(sbd, &s->ctl_iomem); memory_region_init_io(&s->data_iomem, OBJECT(s), &fw_cfg_data_mem_ops, - FW_CFG(s), "fwcfg.data", FW_CFG_DATA_SIZE); + FW_CFG(s), "fwcfg.data", + fw_cfg_data_mem_ops.valid.max_access_size); sysbus_init_mmio(sbd, &s->data_iomem); } -- 2.1.0