From owner-freebsd-x11@FreeBSD.ORG Mon Mar 11 04:19:15 2013 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AFDC5FF5; Mon, 11 Mar 2013 04:19:15 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id 7A5D12FF; Mon, 11 Mar 2013 04:19:15 +0000 (UTC) Received: from pool-141-154-241-44.bos.east.verizon.net ([141.154.241.44] helo=homobox.opal.com) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1UEuCa-000D0T-Nv; Mon, 11 Mar 2013 04:19:08 +0000 Received: from shibato (pool-173-52-168-49.nycmny.east.verizon.net [173.52.168.49]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id r2B4J4Tt041121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 11 Mar 2013 00:19:05 -0400 (EDT) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 141.154.241.44 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+BXxSMFoUebkKOMe5Qr2fH Date: Mon, 11 Mar 2013 00:18:58 -0400 From: "J.R. Oldroyd" To: Adam K Kirchhoff Subject: Re: New AMD drm code Message-ID: <20130311001858.61224bf6@shibato> In-Reply-To: References: X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (homobox.opal.com [141.154.241.44]); Mon, 11 Mar 2013 00:19:06 -0400 (EDT) X-Spam-Status: No, score=3.1 required=5.0 tests=AWL,BAYES_00, FH_HOST_EQ_VERIZON_P,FSL_HELO_NON_FQDN_1,RCVD_IN_PBL,RDNS_DYNAMIC shortcircuit=no autolearn=no version=3.3.2 X-Spam-Level: *** X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on homobox.opal.com Cc: "freebsd-x11@freebsd org" , =?UTF-8?B?SmVh?= =?UTF-8?B?bi1Tw6liYXN0aWVuIFDDqWRyb24=?= X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 04:19:15 -0000 On Sun, 10 Mar 2013 20:39:46 -0400 Adam K Kirchhoff wrote: > >=20 > I'm wondering if there is some secret to getting the new radeon drm code = up and running. I realize it's currently very experimental, but I have a n= umber of machines and cards I can test with.=20 >=20 > I've tried using both a standard -CURRENT kernel and one built from here:= =20 >=20 > https://github.com/dumbbell/freebsd >=20 > However, in both cases, the radeon kernel module does not attach to my HD= 6950 when I load it. In fact, a quick look at ways/dev/drm2/drm_pciids.h d= oesn't seem to show any newer Radeon HD gpus. >=20 > I have the feeling I'm missing something obvious.. >=20 > Thanks. >=20 > Adam Jean-S=C3=A9bastien has the code working on -current, and I just about have it working on 9.1-release. For both, you'll need the sys/dev/drm2 code from his git (at the URL you gave above), not the code in head. For 9.x, you'll also need a handful of changes to sys/vm and sys/dev/iicbus and probably another bugfix or two that we haven't worked out yet. I can send this as a diff to anyone who's interested. Your Cayman PRO is there in the drm_pciids.h file (line 491), so it is supported in the original Linux code. There's a lot of code specific to the cayman cards, however not all of it may have been ported yet. If you see lots of "#ifdef DUMBBELL_WIP"s in the cayman code, that means work is still to be done. You could post your dmesg to show what's happening when you load the module. Note that if the module loads ok, syscons goes blank because there is no support in it for KMS yet. You'll need to ssh in to start an X server or run a script to both load the module and start X. You will also need to patch the port graphics/libdrm to make it enable KMS. This isn't just a question of enabling the KMS compilation option. You'll need to edit xf86drmMode.c to have it return true for the FreeBSD case. Also note that this will then cause your old UMS driver to fail if you go back to it. You'll need to revert libdrm to the non KMS version to go back to the old UMS setup. -jr