From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>, qemu-devel@nongnu.org
Cc: "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH 1/3] sh: SE7750 board definition
Date: Mon, 12 Jan 2009 12:48:02 +0900 [thread overview]
Message-ID: <496ABD72.20400@juno.dti.ne.jp> (raw)
In-Reply-To: <20090111130445.GA12080@game.jcrosoft.org>
Thank you for the review!
# This mail CCed to linux-sh ML expecting some comments on SE7750 flash.
Jean-Christophe PLAGNIOL-VILLARD wrote:
>> +#define SDRAM_BASE 0x0c000000 /* Physical location of SDRAM: Area 3 */
>> +#define SDRAM_SIZE 0x02000000
>
>> +#define ENTRY_OFFSET 0x00001000
>> +#define COMMAND_LINE_OFFSET 0x0000100
> IIRC it's the case for all SH4 maybe we could define it in a header and all
> board to overwrite it
I agree. I think it will be another patch.
>> +
>> +static void se7750_init(ram_addr_t ram_size, int vga_ram_size,
>> + const char *boot_device, DisplayState * ds,
>> + const char *kernel_filename, const char *kernel_cmdline,
>> + const char *initrd_filename, const char *cpu_model)
>> +{
>> + CPUState *env;
>> + struct SH7750State *s;
>> + ram_addr_t sdram_addr;
>> + int kernel_size;
>> + uint8 * phys_load_addr = phys_ram_base;
>> +
>> + /* initialize CPU */
>> + if (!cpu_model)
>> + cpu_model = "SH7750";
>> +
>> + env = cpu_init(cpu_model);
>> + if (!env) {
>> + fprintf(stderr, "Unable to find CPU definition\n");
>> + exit(1);
>> + }
>> +
>> + /* Allocate memory space */
>> + sdram_addr = qemu_ram_alloc(SDRAM_SIZE);
>> + cpu_register_physical_memory(SDRAM_BASE, SDRAM_SIZE, sdram_addr);
>> +
>> + /* Register peripherals */
>> + s = sh7750_init(env);
>> +
>> + /* initialization which should be done by firmware */
>> + uint32_t bcr1 = 1 << 3; /* cs3 SDRAM */
>> + uint16_t bcr2 = 3 << (3 * 2); /* cs3 32-bit */
> please move tihs too the beginning of the function
Sure. I'll do so.
>> + 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
Regards,
Shin-ichiro KAWASAKI
next prev parent reply other threads:[~2009-01-12 3:48 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 [this message]
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
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=496ABD72.20400@juno.dti.ne.jp \
--to=kawasaki@juno.dti.ne.jp \
--cc=linux-sh@vger.kernel.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 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).