From: Igor Mitsyanko <i.mitsyanko@samsung.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
vpalatin@chromium.org, qemu-devel@nongnu.org,
"Peter A. G. Crosthwaite" <peter.crosthwaite@petalogix.com>,
paul@codesourcery.com, duyl@xilinx.com, linnj@xilinx.com,
edgar.iglesias@gmail.com, john.williams@petalogix.com,
Dmitry Solodkiy <d.solodkiy@samsung.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/2] SDHCI: inital version
Date: Mon, 02 Apr 2012 12:38:43 +0400 [thread overview]
Message-ID: <4F796593.1080306@samsung.com> (raw)
In-Reply-To: <4F795CB7.9060404@suse.de>
On 04/02/2012 12:00 PM, Andreas Färber wrote:
> Am 02.04.2012 09:20, schrieb Peter Maydell:
>> On 2 April 2012 07:24, Peter A. G. Crosthwaite
>> <peter.crosthwaite@petalogix.com> wrote:
>>> device more for standard SD host controller interface (SDHCI).
>>>
>>> Signed-off-by: Peter A. G. Crosthwaite<peter.crosthwaite@petalogix.com>
>>
>> So how does this compare with Vincent Palatin's version?
>> (http://patchwork.ozlabs.org/patch/106767/) I'm guessing from
>> the copyright string that it's a modified version -- it would
>> be nice to say what the differences are.
>
> ...and what the differences to Samsung's version are.
>
> We should probably also cc Kevin on the topic.
>
> Andreas
It looks like this sdhc implements version 1 of standard SDHC
specification, while ours implements second version. Second version
should be backwards compatible with first, I didn't want to submit it
yet to see if vmstate issue will be resolved or not. And also the whole
QEMU SD emulation scheme needs some refactoring which I've been busy
with for a while now. The biggest issues are that currently we cannot
hot-insert SD card into virtual board interface and we do not take any
advantage of QOM (which is hard until Paolo's and Andrea's patches land
in master).
The one advantage of our SDHCI implementation is that it provides
interface to implement SoC-specific successors of standart SDHCI. I'll
send these patches today (even though I wanted to do a lot more
refactoring with them), Peter, could you please test them to find out if
you can use them instead of your SDHCI implementation?
--
Mitsyanko Igor
ASWG, Moscow R&D center, Samsung Electronics
email: i.mitsyanko@samsung.com
next prev parent reply other threads:[~2012-04-02 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 6:24 [Qemu-devel] [PATCH v1 0/2] SDHCI for Xilinx Zynq Peter A. G. Crosthwaite
2012-04-02 6:24 ` [Qemu-devel] [PATCH v1 1/2] SDHCI: inital version Peter A. G. Crosthwaite
2012-04-02 7:20 ` Peter Maydell
2012-04-02 8:00 ` Andreas Färber
2012-04-02 8:38 ` Igor Mitsyanko [this message]
2012-04-02 11:05 ` Peter Crosthwaite
2012-04-02 13:31 ` Igor Mitsyanko
2012-04-02 13:47 ` Peter Crosthwaite
2012-04-02 14:16 ` Igor Mitsyanko
2012-04-02 13:46 ` Peter Maydell
2012-04-02 13:56 ` Igor Mitsyanko
2012-04-02 10:40 ` Peter Crosthwaite
2012-04-02 6:24 ` [Qemu-devel] [PATCH v1 2/2] xilinx_zynq: added sdhci controller Peter A. G. Crosthwaite
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=4F796593.1080306@samsung.com \
--to=i.mitsyanko@samsung.com \
--cc=afaerber@suse.de \
--cc=d.solodkiy@samsung.com \
--cc=duyl@xilinx.com \
--cc=edgar.iglesias@gmail.com \
--cc=john.williams@petalogix.com \
--cc=kwolf@redhat.com \
--cc=linnj@xilinx.com \
--cc=paul@codesourcery.com \
--cc=peter.crosthwaite@petalogix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vpalatin@chromium.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.