qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nobuhiro Iwamatsu <iwamatsu.nobuhiro@renesas.com>
To: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
Cc: Takashi Yoshii <yoshii.takashi@renesas.com>,
	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: Thu, 15 Jan 2009 10:46:24 +0900	[thread overview]
Message-ID: <496E9570.2050306@renesas.com> (raw)
In-Reply-To: <496C98EB.5040309@juno.dti.ne.jp>

Shin-ichiro KAWASAKI wrote:
> 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 ....

Flash model is 29lv160t.
> 
> I should have explained it.  To avoid messy many board support,
> board should be selected carefully.
> 
> I wanted a board which can test SCI (not SCIF) console emulation.
> I'm sure that SE7750 supports both SCI and SCIF, and it is suitable
> to check SCI work.  For this purpose, any other board is OK if it
> uses SCI for console.
> 
> # The reason I stick to SCI is r2d+ board's RTC.  The r2d+ board uses
> # SCI not for console but for SPI connection with RTC chip.  Before
> # thinking about RTC emulation, SCI emulation should be done.

OK.

> 
> Another reason for SE7750 is support for TOPPERS. TOPPERS is an open
> source realtime OS. I think QEMU will be a strong tool for TOPPERS
> developers.  They already utilizes SkyEye, the ARM dedicated CPU
> simulator for board-less development. Of course SkyEye cannot be
> used for the work for SuperH.
> 
> Here's the list of the CPUs and boards which can run TOPPERS.
>  http://www.toppers.jp/en/jsp-kernel-e.html
> SE7750 is the only one board which has SuperH, can run TOPPERS, and
> has Linux kernel's default config.
> 
> We should focus on completing SH-Linux emulation before thinking about
> other OSes.  But if I have to add new board emulation, I think SE7750
> is a good choice.

I understood.
But this board can not get now and CPU is too old.
And you don't have this. How do you develop this board and IP?

# Does the development of SH of Toppers still continue?

> 
> 
>> 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.
>>
>> How about you?
> Good idea.  I agree that virtual board is useful.
> I wonder how linux kernel config will be.
> Or on what kind of policy, its specs should be decided?
I think that the Qemu-sh developer talk about it.
# Though the talk might be not settled....
Or get from other architectures (ex. MIPS).
Or I thought create of configurable mechanism to be good.

Best regards,
  Nobuhiro

  reply	other threads:[~2009-01-15  1:46 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
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 [this message]
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=496E9570.2050306@renesas.com \
    --to=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).