qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 1/3] sh: SE7750 board definition


From: Nobuhiro Iwamatsu
Subject: Re: [Qemu-devel] [PATCH 1/3] sh: SE7750 board definition
Date: Thu, 15 Jan 2009 10:25:41 +0900
User-agent: Thunderbird 1.5.0.14 (Windows/20071210)

Jean-Christophe PLAGNIOL-VILLARD wrote:
On 11:32 Tue 13 Jan     , Nobuhiro Iwamatsu wrote:
Paul Mundt wrote:
On Mon, Jan 12, 2009 at 12:48:02PM +0900, Shin-ichiro KAWASAKI wrote:
+    cpu_physical_memory_write(SH7750_BCR1_A7, (uint8_t *)&bcr1, 4);
+    cpu_physical_memory_write(SH7750_BCR2_A7, (uint8_t *)&bcr2, 2);
+
+    /* Start from P2 area */
+    env->pc = SDRAM_BASE | 0xa0000000;
+
+    /* pass kernel cmdline */
+    if (kernel_cmdline) {
+ pstrcpy((char *)phys_load_addr + ENTRY_OFFSET + COMMAND_LINE_OFFSET,
+                strlen(kernel_cmdline) + 1, kernel_cmdline);
+        env->pc += 0x80000;
+        phys_load_addr += 0x80000;
+    }
do you known the flash model present on the real board?
No, I don't.
The patches for SE7750 are all implemented using informations in linux source code. I visited Solution Engine site (in Japanese) but could not find useful specs.
http://www.hitachi-ul.co.jp/system/SH-SE/shiyou.html

I haven't seen one of these boards in at least 7 years, so I can't help
you with specifications. Yoshii-san or Iwamatsu-san might know, though?
SE7751 should have the same flash model and layout IIRC.

This board can not get from Hitachi-ULSI now and this is too old.
I can send it later by examining the flash memory of this board.
# I do not understand the meaning that supports this board ....

BTW, I have question about Qemu-sh board support.
Does the developer of Qemu-SH try to support all boards?
I think that it is good to make it the base of Qemu-SH by
thinking about one board as virtual as MIPS.

Because first of all, I am not so interested in the support of the board.
I am interested in emulation of CPU and the userland.
In the current situation, the number of supported real boards increases
when the support of CPU increases. The code of the board enters whenever
CPU is supported.
I think that you should decide a virtual board of SH and switch CPU.
A virtual board is good to test CPU and different IPs, but you can not compare
the comportment of qemu against the real hard. IMHO, this is the more
important part for supporting new boards.

I understood your comment.

Then, I do not support in each board and I think support it by the unit of IP.
Because we can be tested IP with a real machine.

BTW, because I think that qemu is CPU or userland emulator,
I don't think that complete emulation of the board is so important.

Best regards,
 Nobuhiro
Best regards,
 Nobuhiro




reply via email to

[Prev in Thread] Current Thread [Next in Thread]