From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 08EC8C432C3 for ; Wed, 27 Nov 2019 15:06:29 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8866A20674 for ; Wed, 27 Nov 2019 15:06:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="YVM6PEgz" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8866A20674 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:39358 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZytf-0001Fi-Ed for qemu-devel@archiver.kernel.org; Wed, 27 Nov 2019 10:06:27 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:48186) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iZysr-0000qu-Bi for qemu-devel@nongnu.org; Wed, 27 Nov 2019 10:05:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iZyso-00035x-UP for qemu-devel@nongnu.org; Wed, 27 Nov 2019 10:05:36 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:46189 helo=us-smtp-1.mimecast.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iZyso-00035I-Q3 for qemu-devel@nongnu.org; Wed, 27 Nov 2019 10:05:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1574867133; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=/zLDZOOz77BMhJgRVA+XdOUsUC3GLqnxf8Zvw7MPvwU=; b=YVM6PEgzKbWGGrG1p7SXmDP9DTtzAmt/Tw9hloyDCZXxPoS04ZmCnO266A+d6xFMz4tfc4 8j+OTpwbA4fYkEaUu4Wb4UzAeCD29PGDDP6DtAAiXruNT6bSAmQVXqO6dIPeaW5aNPG1lp tFJLD4lbxfnKT84rVpT6JDvMOpGGC6s= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-52-b_opsM6lMsm3-4-ff1a2aQ-1; Wed, 27 Nov 2019 10:05:30 -0500 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D7FC4107ACE3; Wed, 27 Nov 2019 15:05:28 +0000 (UTC) Received: from redhat.com (unknown [10.42.16.105]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7E864600C8; Wed, 27 Nov 2019 15:05:22 +0000 (UTC) Date: Wed, 27 Nov 2019 15:05:20 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= Subject: Re: [RFC 00/10] R300 QEMU device V2 Message-ID: <20191127150520.GG2131806@redhat.com> References: <20191126124433.860-1-aaron.zakhrov@gmail.com> <20191126141924.GQ556568@redhat.com> <09273ecd-be76-ab61-304f-7ea0f1f0b107@redhat.com> MIME-Version: 1.0 In-Reply-To: <09273ecd-be76-ab61-304f-7ea0f1f0b107@redhat.com> User-Agent: Mutt/1.12.1 (2019-06-15) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-MC-Unique: b_opsM6lMsm3-4-ff1a2aQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 205.139.110.120 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Cc: qemu-devel@nongnu.org, Aaron Dominick , kraxel@redhat.com Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Wed, Nov 27, 2019 at 04:00:01PM +0100, Philippe Mathieu-Daud=C3=A9 wrote= : > Hi Daniel, Aaron. >=20 > On 11/26/19 3:19 PM, Daniel P. Berrang=C3=A9 wrote: > > On Tue, Nov 26, 2019 at 06:14:27PM +0530, aaron.zakhrov@gmail.com wrote= : > > > From: Aaron Dominick > > >=20 > > > 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 a= n 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: > > >=20 > > > =09https://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. > >=20 > > 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. > >=20 > > 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. >=20 > We can not redistribute this BIOS. >=20 > > 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. >=20 > Daniel, I think there is no problem if Aaron contributes a model of the R= 300 > 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 ? Regards, Daniel --=20 |: 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= :|