From: Liming Wang <walimisdev@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2] hw/vexpress.c: Add NOR flash model
Date: Wed, 21 Mar 2012 11:37:16 +0800 [thread overview]
Message-ID: <1332301036-20696-1-git-send-email-walimisdev@gmail.com> (raw)
Vexpress motherboard has two 2x16 NOR flash, but pflash_cfi01
doesn't support interleaving, so here only models two 1x32 flash.
Although it's not exactly modeled, it works fine for running linux.
Signed-off-by: Liming Wang <walimisdev@gmail.com>
---
v2:
- swap NORFLASH0 and NORFLASH0ALIAS and reserve NORFLASH0ALIAS if we
want to boot from flash0 in the future.
hw/vexpress.c | 28 ++++++++++++++++++++++------
1 files changed, 22 insertions(+), 6 deletions(-)
diff --git a/hw/vexpress.c b/hw/vexpress.c
index b9aafec..6a5bf4e 100644
--- a/hw/vexpress.c
+++ b/hw/vexpress.c
@@ -29,9 +29,13 @@
#include "sysemu.h"
#include "boards.h"
#include "exec-memory.h"
+#include "flash.h"
+#include "blockdev.h"
#define VEXPRESS_BOARD_ID 0x8e0
+#define VEXPRESS_FLASH_SIZE 0x04000000
+
static struct arm_boot_info vexpress_binfo;
/* Address maps for peripherals:
@@ -61,8 +65,8 @@ enum {
VE_RTC,
VE_COMPACTFLASH,
VE_CLCD,
- VE_NORFLASH0,
VE_NORFLASH0ALIAS,
+ VE_NORFLASH0,
VE_NORFLASH1,
VE_SRAM,
VE_VIDEORAM,
@@ -92,6 +96,7 @@ static target_phys_addr_t motherboard_legacy_map[] = {
[VE_COMPACTFLASH] = 0x1001a000,
[VE_CLCD] = 0x1001f000,
/* CS0: 0x40000000 .. 0x44000000 */
+ [VE_NORFLASH0ALIAS] = 0x40000000,
[VE_NORFLASH0] = 0x40000000,
/* CS1: 0x44000000 .. 0x48000000 */
[VE_NORFLASH1] = 0x44000000,
@@ -105,8 +110,8 @@ static target_phys_addr_t motherboard_legacy_map[] = {
static target_phys_addr_t motherboard_aseries_map[] = {
/* CS0: 0x00000000 .. 0x0c000000 */
- [VE_NORFLASH0] = 0x00000000,
- [VE_NORFLASH0ALIAS] = 0x08000000,
+ [VE_NORFLASH0ALIAS] = 0x00000000,
+ [VE_NORFLASH0] = 0x08000000,
/* CS4: 0x0c000000 .. 0x10000000 */
[VE_NORFLASH1] = 0x0c000000,
/* CS5: 0x10000000 .. 0x14000000 */
@@ -355,6 +360,9 @@ static void vexpress_common_init(const VEDBoardInfo *daughterboard,
MemoryRegion *vram = g_new(MemoryRegion, 1);
MemoryRegion *sram = g_new(MemoryRegion, 1);
const target_phys_addr_t *map = daughterboard->motherboard_map;
+ DriveInfo *dinfo = NULL;
+ uint32_t sector_len = 256 * 1024;
+ int i = 0;
daughterboard->init(daughterboard, ram_size, cpu_model, pic, &proc_id);
@@ -405,9 +413,17 @@ static void vexpress_common_init(const VEDBoardInfo *daughterboard,
sysbus_create_simple("pl111", map[VE_CLCD], pic[14]);
- /* VE_NORFLASH0: not modelled */
- /* VE_NORFLASH0ALIAS: not modelled */
- /* VE_NORFLASH1: not modelled */
+ for (i = 0; i < 2; i++) {
+ dinfo = drive_get(IF_PFLASH, 0, i);
+ if (dinfo) {
+ pflash_cfi01_register(i ? map[VE_NORFLASH1] : map[VE_NORFLASH0],
+ NULL,
+ i ? "vexpress.flash1" : "vexpress:flash0",
+ VEXPRESS_FLASH_SIZE, dinfo->bdrv, sector_len,
+ VEXPRESS_FLASH_SIZE / sector_len, 4,
+ 0, 0x89, 0x89, 0x19, 0);
+ }
+ }
sram_size = 0x2000000;
memory_region_init_ram(sram, "vexpress.sram", sram_size);
--
1.7.0.4
next reply other threads:[~2012-03-21 3:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 3:37 Liming Wang [this message]
2012-04-05 17:55 ` [Qemu-devel] [PATCH v2] hw/vexpress.c: Add NOR flash model Peter Maydell
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=1332301036-20696-1-git-send-email-walimisdev@gmail.com \
--to=walimisdev@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.