qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Markus Armbruster" <armbru@redhat.com>,
	qemu-devel@nongnu.org, kraxel@redhat.com,
	"Aaron Dominick" <aaron.zakhrov@gmail.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [RFC 00/10] R300 QEMU device V2
Date: Wed, 27 Nov 2019 15:54:23 +0000	[thread overview]
Message-ID: <20191127155423.GH2131806@redhat.com> (raw)
In-Reply-To: <19e8e458-04dc-874d-d372-04a0e2d5246b@redhat.com>

On Wed, Nov 27, 2019 at 04:13:18PM +0100, Philippe Mathieu-Daudé wrote:
> Cc'ing more.
> 
> On 11/27/19 4:05 PM, Daniel P. Berrangé wrote:
> > On Wed, Nov 27, 2019 at 04:00:01PM +0100, Philippe Mathieu-Daudé wrote:
> > > Hi Daniel, Aaron.
> > > 
> > > On 11/26/19 3:19 PM, Daniel P. Berrangé wrote:
> > > > On Tue, Nov 26, 2019 at 06:14:27PM +0530, aaron.zakhrov@gmail.com wrote:
> > > > > From: Aaron Dominick <aaron.zakhrov@gmail.com>
> > > > > 
> > > > > I have removed the botched patches and have got the code working upto the GART initialization.
> > > > > I am not sure how to implement the GART. I am guessing it should be an IOMMU device but I think that is a bit much for an emulated card.
> > > > > The earlier problem of display probing seems to be resolved by using an R300 bios I got from TechPowerUP's GPU database:
> > > > > 
> > > > > 	https://www.techpowerup.com/vgabios/14509/14509
> > > > > I am NOT sure if we can distribute it in the QEMU source tree. If it
> > > > > does cause problems I can send a patch to remove it.
> > > > 
> > > > That site seems to be a repository of BIOS uploaded by arbitrary users,
> > > > with no information on what license terms might apply to the uploads.
> > > > 
> > > > We have to therefore assume the worst and treat the BIOS images on that
> > > > site as proprietary and not re-distributable, despite the fact that the
> > > > site itself is acting as a 3rd party distributor.
> > > 
> > > We can not redistribute this BIOS.
> > > 
> > > > IOW, we can't have this in QEMU git I'm afraid, unless someone can find
> > > > a trustworthy vendor source for the original image with accompanying
> > > > license information.
> > > 
> > > Daniel, I think there is no problem if Aaron contributes a model of the R300
> > > device to QEMU, right? This doesn't involve redistributing any BIOS.
> > 
> > Having just the device impl doesn't cause any legal problems.
> > 
> > It does become a slight usability issue, as any users need to go and find
> > the suitable BIOS in order to use the device. No downstream OS vendors are
> > going to be able to distribute this BIOS either
> > 
> > I don't know if we have hit this problem before & if we have any
> > general policies about it ?
> 
> This appears to me the same case as a user downloading a proprietary
> driver/firmware at some vendor website, accepting the EULA, then using the
> driver within a QEMU VM.
> 
> No close source blob are redistributed, but users can still run them, and
> both party (the QEMU project, and the users) are legally correct, right? But
> IANAL.

Well in this case the user wouldn't be reading or accepting any EULA,
because this 3rd party site doesn't provide any such things with the
firmware it is re-distributing.

IOW, the only way the user can use this device is to download the
firmware from this 3rd site & ignore the lack of legal information
they provide about license/distribution rules.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2019-11-27 15:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 12:44 [RFC 00/10] R300 QEMU device V2 aaron.zakhrov
2019-11-26 12:44 ` [RFC 05/10] Add Radeon kernel headers. Will clean up later aaron.zakhrov
2019-11-26 12:44 ` [RFC 06/10] Fix MC STATUS resgister aaron.zakhrov
2019-11-26 12:44 ` [RFC 07/10] R300 fixes aaron.zakhrov
2019-11-26 12:44 ` [RFC 08/10] Got GPU init working. Stops at probing display aaron.zakhrov
2019-11-26 12:44 ` [RFC 09/10] Clean up Radeon Header files aaron.zakhrov
2019-11-27  9:55   ` Aleksandar Markovic
2019-11-27 14:42     ` BALATON Zoltan
2019-11-26 14:19 ` [RFC 00/10] R300 QEMU device V2 Daniel P. Berrangé
2019-11-27 15:00   ` Philippe Mathieu-Daudé
2019-11-27 15:05     ` Daniel P. Berrangé
2019-11-27 15:13       ` Philippe Mathieu-Daudé
2019-11-27 15:54         ` Daniel P. Berrangé [this message]
2019-11-27 16:12       ` Gerd Hoffmann
2019-11-27 16:32         ` Daniel P. Berrangé
2019-11-28  6:51           ` Aaron Zakhrov
2019-11-29 18:03             ` BALATON Zoltan
2019-11-27 16:17       ` BALATON Zoltan

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=20191127155423.GH2131806@redhat.com \
    --to=berrange@redhat.com \
    --cc=aaron.zakhrov@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.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).