From: Shin-ichiro KAWASAKI <kawasaki@juno.dti.ne.jp>
To: qemu-devel@nongnu.org
Subject: pmac kernel & disk image wanted (was Re: [Qemu-devel] [PATCH] sh4: mmio based CF support on r2d board.)
Date: Thu, 09 Oct 2008 00:20:08 +0900 [thread overview]
Message-ID: <48ECCFA8.6020901@juno.dti.ne.jp> (raw)
In-Reply-To: <20080923085519.GA7603@linux-sh.org>
Paul Mundt wrote:
> On Tue, Sep 23, 2008 at 01:31:36AM +0900, yoshii.takashi@gmail.com wrote:
>> This patch adds emulation for a CompactFlash on sh4/r2d board.
>> I can mount/umount and some read/writes with r2d-1 kernel (no irq mode).
>> No heavy/formal test has not be done, though.
>>
>> The device is CF, but wired to be worked as True-IDE mode, and connected
>> directly to SH bus. So, this code is to supports generally mmio based IDEs
>> which are supported by "pata_platform" driver in linux kernel.
>>
>> I wonder where to put function prototype for mmio_ide_init().
>> Currently, it is in r2d.c, but I believe it can be in more common place.
>>
>> Any suggestions?
>>
> ide.c is likely the best place for it. It looks like there is a bit of
> overlap with pmac_ide though. ARM and others that use pata_platform will
> want to use this as well.
I confirmed that the mmio_ide patch works fine for SH4 system emulation.
I hope it to be merged into trunk.
By the way, I guess pmac_ide functions can be re-implemented with
mmio_ide functions. Before trying this work, I want working kernel
and disk image for PowerMAC(g3bw) system emulation to check if new
implementation works fine or not.
The kernel and disk image for PREP are found at the following URL,
http://www.oszoo.org/wiki/index.php/Debian_Etch_ppc_(PowerPC)_-_Qemu_Ready
But PREP's ide feature does not use pmac_ide but uses isa_ide, so it
does not suit for my purpose.
Any indications or comments will be appreciated.
Regards,
Shin-ichiro KAWASAKI
next prev parent reply other threads:[~2008-10-08 15:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 16:31 [Qemu-devel] [PATCH] sh4: mmio based CF support on r2d board yoshii.takashi
2008-09-22 19:00 ` takasi-y
2008-09-23 8:55 ` Paul Mundt
2008-10-08 15:20 ` Shin-ichiro KAWASAKI [this message]
2008-10-26 15:35 ` pmac kernel & disk image wanted (was Re: [Qemu-devel] [PATCH] sh4: mmio based CF support on r2d board.) Andreas Färber
2008-10-26 15:17 ` [Qemu-devel] [PATCH 1/3] sh4: mmio based CF support on r2d board takasi-y
2008-10-26 15:54 ` Blue Swirl
2008-10-27 1:29 ` andrzej zaborowski
2008-10-27 17:10 ` Blue Swirl
2008-10-29 14:22 ` andrzej zaborowski
2008-10-29 18:37 ` Blue Swirl
2008-10-27 18:57 ` takasi-y
2008-10-27 19:12 ` Blue Swirl
2008-10-28 20:58 ` [Qemu-devel] [PATCH 1/3] take3 " takasi-y
2008-10-26 15:17 ` [Qemu-devel] [PATCH 0/3] take 2. " takasi-y
2008-10-26 15:17 ` [Qemu-devel] [PATCH 2/3] sh4: Add IRL(4bit encoded interrupt input) support takasi-y
2008-10-26 16:09 ` Blue Swirl
2008-10-28 20:58 ` [Qemu-devel] [PATCH 2/3] take3 " takasi-y
2008-10-29 18:09 ` [Qemu-devel] " Blue Swirl
2008-10-30 17:28 ` takasi-y
2008-10-26 15:17 ` [Qemu-devel] [PATCH 3/3] sh4: Add r2d onboard FPGA IRQ controller takasi-y
2008-10-28 20:58 ` [Qemu-devel] [PATCH 3/3] take3 " takasi-y
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=48ECCFA8.6020901@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 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).