All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Aaron Dominick" <aaron.zakhrov@gmail.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [RFC 00/10] R300 QEMU device V2
Date: Wed, 27 Nov 2019 16:00:01 +0100	[thread overview]
Message-ID: <09273ecd-be76-ab61-304f-7ea0f1f0b107@redhat.com> (raw)
In-Reply-To: <20191126141924.GQ556568@redhat.com>

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.


Aaron: I never received patches 1-4 and 10 of your series, not sure why, 
maybe they are too big.

I recommend to rebase your series, squashing patch 9 over patch 5.

If you don't know about git-rebase, this blog is quite easy to understand:
https://thoughtbot.com/blog/git-interactive-rebase-squash-amend-rewriting-history

Regards,

Phil.



  reply	other threads:[~2019-11-27 15:01 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é [this message]
2019-11-27 15:05     ` Daniel P. Berrangé
2019-11-27 15:13       ` Philippe Mathieu-Daudé
2019-11-27 15:54         ` Daniel P. Berrangé
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=09273ecd-be76-ab61-304f-7ea0f1f0b107@redhat.com \
    --to=philmd@redhat.com \
    --cc=aaron.zakhrov@gmail.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --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 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.