From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>, qemu-devel@nongnu.org
Cc: Huacai Chen <zltjiangshi@gmail.com>,
Aleksandar Markovic <amarkovic@wavecomp.com>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 2/4] mips_fulong2e: Fix bios flash size
Date: Tue, 12 Feb 2019 00:59:14 +0100 [thread overview]
Message-ID: <843d579b-9eb3-f96a-bc53-17c16b7cec65@redhat.com> (raw)
In-Reply-To: <4ba510e2c7771808fa5061e14526f313c1ac3817.1549857716.git.balaton@eik.bme.hu>
On 2/11/19 5:01 AM, BALATON Zoltan wrote:
> According to both the specifications on linux-mips.org referenced in a
This link: https://www.linux-mips.org/wiki/Fulong#Front:
> comment at the beginning of the file and the flash chip part number
> the bios size should be 512k not 1M.
>
> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> hw/mips/mips_fulong2e.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/hw/mips/mips_fulong2e.c b/hw/mips/mips_fulong2e.c
> index 02549d5c7e..10e6ed585a 100644
> --- a/hw/mips/mips_fulong2e.c
> +++ b/hw/mips/mips_fulong2e.c
> @@ -21,6 +21,7 @@
> #include "qemu/osdep.h"
> #include "qemu/units.h"
> #include "qapi/error.h"
> +#include "cpu.h"
> #include "hw/hw.h"
> #include "hw/i386/pc.h"
> #include "hw/dma/i8257.h"
> @@ -35,7 +36,6 @@
> #include "audio/audio.h"
> #include "qemu/log.h"
> #include "hw/loader.h"
> -#include "hw/mips/bios.h"
> #include "hw/ide.h"
> #include "elf.h"
> #include "hw/isa/vt82c686.h"
> @@ -51,6 +51,8 @@
> #define ENVP_NB_ENTRIES 16
> #define ENVP_ENTRY_SIZE 256
>
> +/* fulong 2e has a 512k flash: Winbond W39L040AP70Z */
> +#define BIOS_SIZE (512 * KiB)
> #define MAX_IDE_BUS 2
>
> /*
> @@ -307,12 +309,9 @@ static void mips_fulong2e_init(MachineState *machine)
> /* fulong 2e has 256M ram. */
> ram_size = 256 * MiB;
>
> - /* fulong 2e has a 1M flash.Winbond W39L040AP70Z */
> - bios_size = 1 * MiB;
> -
> /* allocate RAM */
> memory_region_allocate_system_memory(ram, NULL, "fulong2e.ram", ram_size);
> - memory_region_init_ram(bios, NULL, "fulong2e.bios", bios_size,
> + memory_region_init_ram(bios, NULL, "fulong2e.bios", BIOS_SIZE,
> &error_fatal);
> memory_region_set_readonly(bios, true);
>
>
next prev parent reply other threads:[~2019-02-11 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 4:01 [Qemu-devel] [PATCH 0/4] Misc MIPS fulong2e improvements BALATON Zoltan
2019-02-11 4:01 ` [Qemu-devel] [PATCH 1/4] hw/pci-host/bonito.c: Add PCI mem region mapped at the correct address BALATON Zoltan
2019-02-12 0:18 ` Philippe Mathieu-Daudé
2019-02-11 4:01 ` [Qemu-devel] [PATCH 3/4] mips_fulong2e: Dynamically generate SPD EEPROM data BALATON Zoltan
2019-02-12 0:00 ` Philippe Mathieu-Daudé
2019-02-14 17:15 ` Aleksandar Markovic
2019-02-14 17:45 ` BALATON Zoltan
2019-02-11 4:01 ` [Qemu-devel] [PATCH 2/4] mips_fulong2e: Fix bios flash size BALATON Zoltan
2019-02-11 23:59 ` Philippe Mathieu-Daudé [this message]
2019-02-11 4:01 ` [Qemu-devel] [PATCH 4/4] mips_fulong2e: Add on-board graphics chip BALATON Zoltan
2019-02-11 23:54 ` Philippe Mathieu-Daudé
2019-02-13 0:01 ` BALATON Zoltan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=843d579b-9eb3-f96a-bc53-17c16b7cec65@redhat.com \
--to=philmd@redhat.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=balaton@eik.bme.hu \
--cc=qemu-devel@nongnu.org \
--cc=zltjiangshi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).