qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <andreas.faerber@web.de>
To: walimis <walimisdev@gmail.com>, kraxel@redhat.com
Cc: Peter Maydell <peter.maydell@linaro.org>,
	peter.crosthwaite@xilinx.com,
	Igor Mitsyanko <i.mitsyanko@samsung.com>,
	qemu-devel@nongnu.org, Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [Qemu-devel] [PATCH RFT 0/5] usb: Clean up and extend SysBus EHCI
Date: Sun, 02 Dec 2012 17:27:16 +0100	[thread overview]
Message-ID: <50BB8164.9040308@web.de> (raw)
In-Reply-To: <20121202103453.GA6029@pek-lwang0-d1>

Am 02.12.2012 11:34, schrieb walimis:
> On Sun, Dec 02, 2012 at 03:57:17AM +0100, Andreas Färber wrote:
>> Appended is Liming's patch to add an EHCI device to Exynos 4 as well as a
>> new patch of mine to prepare a Tegra 2 EHCI device (cf. my tegra branch) to
> 
> BTW, where can I find your tegra branch?

Sorry, it's here, just rebased and hinting at how it's gonna use EHCI:
http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/tegra
git://repo.or.cz/qemu/afaerber.git tegra

Gerd: In order for me to use this with the new-style Tegra2 model we
will need to further move EHCISysBusState and the accompanying macros
that this series adds into the hcd-ehci.h header so that it can be
embedded into the SoC object. So if you're okay with my approach we'd
need a v2.
Also a question: Vincent's patch has a comment "multiple EHCI
controllers support not ready". Is this still a known issue or resolved
by now? Tegra2 would want to instantiate three SysBus EHCI controllers,
with offsets 0x4000 and 0x1000 respectively.

>> Liming Wang (1):
>>  exynos4210: Add EHCI support
> 
> The test is OK for exynos4210 ehci.

Thanks! Can I drop my [AF: ...] change log if this gets resent?

Regards,
Andreas

  reply	other threads:[~2012-12-02 16:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02  2:57 [Qemu-devel] [PATCH RFT 0/5] usb: Clean up and extend SysBus EHCI Andreas Färber
2012-12-02  2:57 ` [Qemu-devel] [PATCH RFT 1/5] usb/ehci: Clean up SysBus and PCI EHCI split Andreas Färber
2012-12-03 18:35   ` Igor Mitsyanko
2012-12-02  2:57 ` [Qemu-devel] [PATCH RFT 2/5] usb/ehci: Move capsbase and opregbase into SysBus EHCI class Andreas Färber
2012-12-03 18:38   ` Igor Mitsyanko
2012-12-02  2:57 ` [Qemu-devel] [PATCH RFT 3/5] usb/ehci: Add SysBus EHCI device for Exynos4210 Andreas Färber
2012-12-03 18:51   ` Igor Mitsyanko
2012-12-04  0:19     ` walimis
2012-12-04  7:14     ` walimis
2012-12-02  2:57 ` [Qemu-devel] [PATCH RFT 4/5] exynos4210: Add EHCI support Andreas Färber
2012-12-03 18:52   ` Igor Mitsyanko
2012-12-02  2:57 ` [Qemu-devel] [PATCH RFT 5/5] usb/ehci: Add Tegra2 SysBus EHCI device Andreas Färber
2012-12-02 10:34 ` [Qemu-devel] [PATCH RFT 0/5] usb: Clean up and extend SysBus EHCI walimis
2012-12-02 16:27   ` Andreas Färber [this message]
2012-12-03  3:24     ` walimis
2012-12-03  6:59     ` Gerd Hoffmann
2012-12-03 11:58       ` walimis
2012-12-03 12:10         ` Peter Maydell
2012-12-03 12:38           ` walimis
2012-12-03 13:37             ` Gerd Hoffmann
2012-12-03 13:39               ` Peter Maydell

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=50BB8164.9040308@web.de \
    --to=andreas.faerber@web.de \
    --cc=i.mitsyanko@samsung.com \
    --cc=kraxel@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vpalatin@chromium.org \
    --cc=walimisdev@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).