From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
Cc: Takashi Yoshii <yoshii.takashi@renesas.com>,
Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>,
qemu-devel@nongnu.org,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH 1/3] sh: SE7750 board definition
Date: Tue, 13 Jan 2009 07:28:27 +0100 [thread overview]
Message-ID: <20090113062827.GF26923@game.jcrosoft.org> (raw)
In-Reply-To: <496BFD30.30306@renesas.com>
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.
Best Regards,
J.
next prev parent reply other threads:[~2009-01-13 6:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 9:10 [Qemu-devel] [PATCH 1/3] sh: SE7750 board definition Shin-ichiro KAWASAKI
2009-01-11 12:57 ` Edgar E. Iglesias
2009-01-11 13:04 ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-12 3:48 ` Shin-ichiro KAWASAKI
2009-01-12 12:49 ` Paul Mundt
2009-01-13 2:32 ` Nobuhiro Iwamatsu
2009-01-13 6:28 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-01-15 1:25 ` Nobuhiro Iwamatsu
2009-01-13 7:46 ` Laurent Desnogues
2009-01-24 17:59 ` Shin-ichiro KAWASAKI
2009-01-13 13:36 ` Shin-ichiro KAWASAKI
2009-01-15 1:46 ` Nobuhiro Iwamatsu
2009-01-17 10:45 ` Shin-ichiro KAWASAKI
2009-01-17 11:16 ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-21 9:04 ` Paul Mundt
2009-01-21 16:51 ` Shin-ichiro KAWASAKI
2009-01-21 17:06 ` Paul Brook
2009-01-24 5:46 ` sh: Virtual Board or Real board? (was Re: [Qemu-devel] [PATCH 1/3] sh: SE7750 board definition) Shin-ichiro KAWASAKI
2009-01-27 0:43 ` Paul Mundt
2009-02-01 13:50 ` Shin-ichiro KAWASAKI
2009-01-21 19:01 ` [Qemu-devel] [PATCH 1/3] sh: SE7750 board definition Jean-Christophe PLAGNIOL-VILLARD
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=20090113062827.GF26923@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=iwamatsu.nobuhiro@renesas.com \
--cc=kawasaki@juno.dti.ne.jp \
--cc=linux-sh@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=yoshii.takashi@renesas.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).