All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] SH4: SCI improvement
Date: Sun, 14 Dec 2008 20:55:45 +0900	[thread overview]
Message-ID: <4944F441.9050408@juno.dti.ne.jp> (raw)
In-Reply-To: <20081206094401.GA2977@game.jcrosoft.org>

Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 13:39 Mon 24 Nov     , Shin-ichiro KAWASAKI wrote:
>> Hi, Jean-san!
>>
>> It seems a good idea to make u-boot run on SH4-QEMU,
>> for brushing up SH4 emulation.
>>
>> Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> 	I've add the flash support at 0xA0000000
>>> 	and have qemu refusing to boot from it
>>> 	qemu: fatal: Trying to execute code outside RAM or ROM at 0xa000000A
>>> 	I've also try to boot u-boot as a kernel and have the output working
>>> 	but not the input. Impossible to type anything
>> I'm afraid that I have no idea about these two points now.
>> I just guess MMU emulation and SCIF emulation might not be enough to run u-boot.
>>
>> To investigate them more closely, I downloaded current u-boot git repository,
>> build if for r2d, and run u-boot.bin with -kernel option.  But u-boot couldn't
>> boot with assertion failures.  Following two parts caused them.
>>
>> - MMUCR initialization with 16 bit word write causes failure.
>>   QEMU only implements 32 bit write for it, following SH7750 document.
>> - BSC's PCR access cause failure.   QEMU does not implement it yet.
>>
>> Have you handled them?
>>
> you need to apply 1 patch on u-boot
> 
> r2dplus fix register access
> I've send to the U-Boot ML
> 
> and 2 patchs to qemu
> 
>>From you
> sh4: pci and mmu support
> and from I
> SH7750/51: add register BCR3, NCR4, PCR, RTCOR, RTCNT, RTCSR, SDMR2, SDMR3 and
> fix BCR2 support

Thanks.

One more simple modification seems necessary to avoid assertion error,
as attached to this mail.  With these patches, I saw that the U-boot
for r2dplus boots cleanly when it is passed with -kernel option to qemu.
Does it help you?
# Please be sure to give two '-serial' options in qemu command line.

I'm interested in the flash support, which will make it more easy
to handle linux kernel boot conditions for qemu-sh users.

Regards,
Shin-ichiro KAWASAKI


diff --git a/hw/sh_serial.c b/hw/sh_serial.c
index da1a2ca..bf1d609 100644
--- a/hw/sh_serial.c
+++ b/hw/sh_serial.c
@@ -242,11 +242,9 @@ static uint32_t sh_serial_ioport_read(void *opaque, uint32_t offs)
                     s->flags &= ~SH_SERIAL_FLAG_RDF;
             }
             break;
-#if 0
         case 0x18:
             ret = s->fcr;
             break;
-#endif
         case 0x1c:
             ret = s->rx_cnt;
             break;

  reply	other threads:[~2008-12-14 11:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 14:41 [Qemu-devel] [PATCH] SH4: SCI improvement Shin-ichiro KAWASAKI
2008-11-23 22:26 ` Jean-Christophe PLAGNIOL-VILLARD
2008-11-24  4:39   ` Shin-ichiro KAWASAKI
2008-12-06  9:44     ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-14 11:55       ` Shin-ichiro KAWASAKI [this message]
2008-12-14 14:53         ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-07 22:46 ` Aurelien Jarno
2008-12-08  3:50 ` Paul Mundt
2008-12-08 15:25   ` Shin-ichiro KAWASAKI

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=4944F441.9050408@juno.dti.ne.jp \
    --to=kawasaki@juno.dti.ne.jp \
    --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.