From: takasi-y@ops.dti.ne.jp
To: linux-sh@vger.kernel.org
Subject: Re: Concerning Qemu SH4
Date: Sat, 08 Nov 2008 15:28:35 +0000 [thread overview]
Message-ID: <200811081528.mA8FSZaC010580@smtp12.dti.ne.jp> (raw)
In-Reply-To: <20081108020202.0c9a4b59.kristoffer.ericson@gmail.com>
Hi,
> Oki, gotten it to work now. Whats left is putting some sort
> of harddrive file there. I've created an loop file but
> can't seem to get it going.
Have you applied all patches on ML?
Otherwise it doesn't support hard disk.
QEMU repository is being maintained very slowly.
There always many patches left on ML waiting for being merged.
Now, following patches are pending.
http://lists.gnu.org/archive/html/qemu-devel/2008-10/msg00970.html
This must be applied. Otherwise it will be crashed frequently.
http://lists.gnu.org/archive/html/qemu-devel/2008-10/msg01246.html
http://lists.gnu.org/archive/html/qemu-devel/2008-10/msg01247.html
http://lists.gnu.org/archive/html/qemu-devel/2008-10/msg01248.html
These three are needed use to use HDD.
http://lists.gnu.org/archive/html/qemu-devel/2008-11/msg00118.html
http://lists.gnu.org/archive/html/qemu-devel/2008-11/msg00119.html
These two are needed to use network.
Some of them can't be applied cleanly, because other patch has been
applied after I posted them. Please edit them manually.
> I'm also missing something with the initrd as it
> constantly claims that the initrd expands beyond
> the memory boundry.
Current code doesn't support --initrd nor --append.
Only --kernel works. Use initramfs and initial command line.
/yoshii
next prev parent reply other threads:[~2008-11-08 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 0:01 Concerning Qemu SH4 Kristoffer Ericson
2008-11-08 15:28 ` takasi-y [this message]
2008-11-08 19:37 ` Kristoffer Ericson
2008-11-08 19:42 ` Kristoffer Ericson
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=200811081528.mA8FSZaC010580@smtp12.dti.ne.jp \
--to=takasi-y@ops.dti.ne.jp \
--cc=linux-sh@vger.kernel.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