From: Corey Minyard <minyard@acm.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Hao Wu <wuhaotsh@google.com>,
Patrick Venture <venture@google.com>,
Shengtan Mao <stmao@google.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Chris Rauer <crauer@google.com>
Subject: Re: QEMU question: upstreaming I2C device with unpublished datasheet
Date: Tue, 27 Jul 2021 06:28:16 -0500 [thread overview]
Message-ID: <20210727112816.GU3406@minyard.net> (raw)
In-Reply-To: <CAFEAcA8DqSSg3i5L+Rj6m+9X3BWzr===FdufFJgR49tvq6dq=A@mail.gmail.com>
On Tue, Jul 27, 2021 at 10:23:26AM +0100, Peter Maydell wrote:
> On Wed, 21 Jul 2021 at 22:06, Shengtan Mao <stmao@google.com> wrote:
> >
> > Hi everyone,
> > we are hoping to upstream a MAX I2C device to QEMU. The device's datasheet is not public, and we are contacting the Maxim company to get their permission. If Maxim is okay with upstreaming the device with an unpublished datasheet, will this still be an issue with QEMU?
>
> It's not inherently a blocker, but the difficulty is code review.
> Without knowing how the device should behave, it's hard to tell
> whether the model is doing the right thing. Ideally Maxim should
> just publish their datasheet, so if you/your company has any
> leverage with them you should push them to do that :-)
>
> That said, we do have other device models in the tree which
> don't have public datasheets, and as long as the device is not
> too complicated we should be OK as long as you can also submit
> enough test cases that we could refactor the device in future
> without worrying too much that we're breaking it because we don't
> know how it's supposed to behave.
Thanks Peter.
I will add that you need to be sure you have the legal right to publish
the software. If you have a non-public datasheet, that probably means
you had to sign NDA or something like that to see it. That may limit
what you can do.
-corey
prev parent reply other threads:[~2021-07-27 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 20:45 QEMU question: upstreaming I2C device with unpublished datasheet Shengtan Mao
2021-07-27 9:23 ` Peter Maydell
2021-07-27 11:28 ` Corey Minyard [this message]
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=20210727112816.GU3406@minyard.net \
--to=minyard@acm.org \
--cc=crauer@google.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stmao@google.com \
--cc=venture@google.com \
--cc=wuhaotsh@google.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).