qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: yoshii.takashi@gmail.com
Cc: qemu-devel@nongnu.org, takasi-y@ops.dti.ne.jp,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Subject: [Qemu-devel] Re: Qemu SH4 status #2
Date: Wed, 12 Nov 2008 11:56:08 +0100	[thread overview]
Message-ID: <20081112115608.af656fee.kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <20081112133313.967c82e2.yoshii.takashi@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1787 bytes --]

On Wed, 12 Nov 2008 13:33:13 +0900
yoshii.takashi@gmail.com wrote:

> Hi,
> 
> > I'm still getting segmentation fault at exact same
> > location. Have you made additional patches?
> Please find attached file "qemu081111.diff".
> Basically, this is an aggregate of patches found on qemu-devel ML,
>  with some conflicts against current svn source being resolved,
>  and some small fix are added, which are scheduled to be posted after
>  I finished with my pending patches.
> 
> I post this to share information between qemu and linux/sh people,
>  and hopefully accelerate debugging with linux people's help.
> 

I will give it a try later today. Big thx!

> Another file "linuxconfig_r2d_qemu.diff" is diff for linux kernel
>  configuretion. It changes following parameters from r2d+'s defconfig.
> - Cache -> off (qemu has no cache)
> - commandline change (for debugging)
> - 8139too -> 8139cp (qemu's default is c+, still thinking how to switch)
> - SH SPI -> off (sci emulation is not mature enough to handle it)
> 
> Build procedure is as follows,
> Configure kernel:
>  make ARCH=sh rts7751r2dplus_defconfig
>  patch .config < linuxconfig_r2d_qemu.diff
>  (and build)
> 
> Configure Qemu:
>  ./configure --disable-system --target-list=sh4-softmmu \
>   --disable-linux-user --disable-kqemu
> 
> Execute:
>  sh4-softmmu/qemu-system-sh4 -M r2d --serial vc --serial /dev/tty \
>   --kernel zImage --append "console=tty0 root=/dev/sda" \
>   -usb --usbdevice keyboard --usbdevice mouse disk.img
> 
> I've tested it on qemu svn head this morning.
> You will see penguin logo, and fbcon input/output working.
> For debugging purpose, console=ttySC0,115200 might help.
> /yoshii
> 


-- 
Kristoffer Ericson <kristoffer.ericson@gmail.com>

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081110233926.3d8c7fd1.kristoffer.ericson@gmail.com>
     [not found] ` <20081111141335.3c869c26.yoshii.takashi@gmail.com>
2008-11-11 11:27   ` [Qemu-devel] Re: Qemu SH4 status #2 Kristoffer Ericson
2008-11-12  4:33     ` yoshii.takashi
2008-11-12  4:58       ` Paul Mundt
2008-11-12 10:56       ` Kristoffer Ericson [this message]
2008-11-12 16:52       ` Kristoffer Ericson
2008-11-24  7:10       ` Shin-ichiro KAWASAKI
2008-11-25 16:37         ` 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=20081112115608.af656fee.kristoffer.ericson@gmail.com \
    --to=kristoffer.ericson@gmail.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=takasi-y@ops.dti.ne.jp \
    --cc=yoshii.takashi@gmail.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).