From: Paul Zimmerman <pauldzim@gmail.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: Any interest in dwc-otg (aka dwc2) device emulation? For Raspi 3 and below.
Date: Mon, 9 Mar 2020 20:15:33 -0700 [thread overview]
Message-ID: <CADBGO7-O7=nZVH1Zm8Fi08KBJK8rhCLQJsNeXzv4va+o+3ViKA@mail.gmail.com> (raw)
In-Reply-To: <a3d88162-abb1-d770-0222-dec576bbdb6a@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]
Hi John,
Thanks for the tips! I found an issue when testing with the usb-storage
device, so I will work on fixing that, and then think about how best to
split up the patches.
Thanks,
Paul
On Mon, Mar 9, 2020 at 7:23 PM John Snow <jsnow@redhat.com> wrote:
>
>
> On 3/6/20 7:34 PM, Paul Zimmerman wrote:
> > Hi Folks,
> >
> > I have been working on an emulation of the dwc-otg USB controller
> > (host mode only for now), as implemented on the Raspberry Pi 3 and
> > below, and on numerous other embedded platforms. I have it to a point
> > where it works pretty well with the dwc2 driver in the mainline Linux
> > kernel, and with the dwc-otg driver in the Raspbian kernel. Mouse and
> > keyboard work fine, and I *think* the usb-net device is working too,
> > although I have been unsuccessful in connecting to the outside world
> > with it.
> >
> > I haven't done anything with gadget-mode yet, but that could certainly
> > be added in the future.
> >
> > Would there be any interest in me submitting this for inclusion in
> > Qemu? I ask because I see there was a previous effort at this at
> > github.com/0xabu/qemu/hw/usb/bcm2835_usb.c, but it seems it never went
> > anywhere.
> >
> > Thanks,
> > Paul
> >
>
> At a minimum, I think you should send your patches to the list for
> posterity even if they don't wind up getting enough review pressure to
> be merged.
>
> If you want advice on how to split up your patches to entice more
> reviewers, please let us know and any one of us can write a thousand
> more :words: that might help make a better case.
>
> (There's a much-too-long wiki entry on the matter, if you are brave.)
>
> The issue, as always, is usually just reviewer time -- and how squeaky
> the wheel is. Making the patches look pretty and well organized is one
> way to trick well meaning people into reviewing your patches.
>
> --js
>
>
[-- Attachment #2: Type: text/html, Size: 2568 bytes --]
next prev parent reply other threads:[~2020-03-10 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 0:34 Any interest in dwc-otg (aka dwc2) device emulation? For Raspi 3 and below Paul Zimmerman
2020-03-10 2:23 ` John Snow
2020-03-10 3:15 ` Paul Zimmerman [this message]
2020-03-10 9:52 ` Stefan Hajnoczi
2020-03-10 9:26 ` Peter Maydell
2020-03-10 19:00 ` Paul Zimmerman
2020-03-10 21:46 ` John Snow
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='CADBGO7-O7=nZVH1Zm8Fi08KBJK8rhCLQJsNeXzv4va+o+3ViKA@mail.gmail.com' \
--to=pauldzim@gmail.com \
--cc=f4bug@amsat.org \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).