From owner-freebsd-ppc@FreeBSD.ORG Sun Oct 21 00:34:17 2012 Return-Path: Delivered-To: powerpc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8A41835; Sun, 21 Oct 2012 00:34:16 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 93D3F8FC08; Sun, 21 Oct 2012 00:34:16 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id q9L0YF9J023020; Sat, 20 Oct 2012 20:34:15 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q9L0YFW5023017; Sun, 21 Oct 2012 00:34:15 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 21 Oct 2012 00:34:15 GMT Message-Id: <201210210034.q9L0YFW5023017@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on powerpc/powerpc Precedence: bulk X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2012 00:34:17 -0000 TB --- 2012-10-20 22:47:44 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-10-20 22:47:44 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-10-20 22:47:44 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-10-20 22:47:44 - cleaning the object tree TB --- 2012-10-20 22:51:03 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-10-20 22:51:03 - cd /tinderbox/HEAD/powerpc/powerpc TB --- 2012-10-20 22:51:03 - /usr/local/bin/svn cleanup /src TB --- 2012-10-20 22:53:11 - /usr/local/bin/svn update /src TB --- 2012-10-20 22:53:18 - At svn revision 241790 TB --- 2012-10-20 22:53:19 - building world TB --- 2012-10-20 22:53:19 - CROSS_BUILD_TESTING=YES TB --- 2012-10-20 22:53:19 - MAKEOBJDIRPREFIX=/obj TB --- 2012-10-20 22:53:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-10-20 22:53:19 - SRCCONF=/dev/null TB --- 2012-10-20 22:53:19 - TARGET=powerpc TB --- 2012-10-20 22:53:19 - TARGET_ARCH=powerpc TB --- 2012-10-20 22:53:19 - TZ=UTC TB --- 2012-10-20 22:53:19 - __MAKE_CONF=/dev/null TB --- 2012-10-20 22:53:19 - cd /src TB --- 2012-10-20 22:53:19 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sat Oct 20 22:53:31 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies [...] ===> usr.bin/m4 (depend) yacc -d -o parser.c /src/usr.bin/m4/parser.y lex -t /src/usr.bin/m4/tokenizer.l > tokenizer.c rm -f .depend mkdep -f .depend -a -DEXTENDED -I/src/usr.bin/m4/lib -std=gnu99 /src/usr.bin/m4/eval.c /src/usr.bin/m4/expr.c /src/usr.bin/m4/look.c /src/usr.bin/m4/main.c /src/usr.bin/m4/misc.c /src/usr.bin/m4/gnum4.c /src/usr.bin/m4/trace.c parser.c tokenizer.c /src/usr.bin/m4/lib/ohash_create_entry.c /src/usr.bin/m4/lib/ohash_delete.c /src/usr.bin/m4/lib/ohash_do.c /src/usr.bin/m4/lib/ohash_entries.c /src/usr.bin/m4/lib/ohash_enum.c /src/usr.bin/m4/lib/ohash_init.c /src/usr.bin/m4/lib/ohash_interval.c /src/usr.bin/m4/lib/ohash_lookup_interval.c /src/usr.bin/m4/lib/ohash_lookup_memory.c /src/usr.bin/m4/lib/ohash_qlookup.c /src/usr.bin/m4/lib/ohash_qlookupi.c /src/usr.bin/m4/parser.y:26:18: error: mdef.h: No such file or directory /src/usr.bin/m4/parser.y:27:20: error: extern.h: No such file or directory mkdep: compile failed *** [.depend] Error code 1 Stop in /src/usr.bin/m4. *** [depend] Error code 1 Stop in /src/usr.bin. *** [usr.bin.depend__D] Error code 1 Stop in /src. *** [_depend] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-10-21 00:34:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-10-21 00:34:15 - ERROR: failed to build world TB --- 2012-10-21 00:34:15 - 5056.84 user 591.63 system 6391.12 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-ppc@FreeBSD.ORG Sun Oct 21 04:21:22 2012 Return-Path: Delivered-To: powerpc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 924EA111; Sun, 21 Oct 2012 04:21:22 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 3C2968FC08; Sun, 21 Oct 2012 04:21:21 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id q9L4LLVY019300; Sun, 21 Oct 2012 00:21:21 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q9L4LLYl019294; Sun, 21 Oct 2012 04:21:21 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 21 Oct 2012 04:21:21 GMT Message-Id: <201210210421.q9L4LLYl019294@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on powerpc/powerpc Precedence: bulk X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2012 04:21:22 -0000 TB --- 2012-10-21 02:36:21 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-10-21 02:36:21 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-10-21 02:36:21 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-10-21 02:36:21 - cleaning the object tree TB --- 2012-10-21 02:39:45 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-10-21 02:39:45 - cd /tinderbox/HEAD/powerpc/powerpc TB --- 2012-10-21 02:39:45 - /usr/local/bin/svn cleanup /src TB --- 2012-10-21 02:41:50 - /usr/local/bin/svn update /src TB --- 2012-10-21 02:41:56 - At svn revision 241792 TB --- 2012-10-21 02:41:57 - building world TB --- 2012-10-21 02:41:57 - CROSS_BUILD_TESTING=YES TB --- 2012-10-21 02:41:57 - MAKEOBJDIRPREFIX=/obj TB --- 2012-10-21 02:41:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-10-21 02:41:57 - SRCCONF=/dev/null TB --- 2012-10-21 02:41:57 - TARGET=powerpc TB --- 2012-10-21 02:41:57 - TARGET_ARCH=powerpc TB --- 2012-10-21 02:41:57 - TZ=UTC TB --- 2012-10-21 02:41:57 - __MAKE_CONF=/dev/null TB --- 2012-10-21 02:41:57 - cd /src TB --- 2012-10-21 02:41:57 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Oct 21 02:42:04 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies [...] ===> usr.bin/m4 (depend) yacc -d -o parser.c /src/usr.bin/m4/parser.y lex -t /src/usr.bin/m4/tokenizer.l > tokenizer.c rm -f .depend mkdep -f .depend -a -DEXTENDED -I/src/usr.bin/m4/lib -std=gnu99 /src/usr.bin/m4/eval.c /src/usr.bin/m4/expr.c /src/usr.bin/m4/look.c /src/usr.bin/m4/main.c /src/usr.bin/m4/misc.c /src/usr.bin/m4/gnum4.c /src/usr.bin/m4/trace.c parser.c tokenizer.c /src/usr.bin/m4/lib/ohash_create_entry.c /src/usr.bin/m4/lib/ohash_delete.c /src/usr.bin/m4/lib/ohash_do.c /src/usr.bin/m4/lib/ohash_entries.c /src/usr.bin/m4/lib/ohash_enum.c /src/usr.bin/m4/lib/ohash_init.c /src/usr.bin/m4/lib/ohash_interval.c /src/usr.bin/m4/lib/ohash_lookup_interval.c /src/usr.bin/m4/lib/ohash_lookup_memory.c /src/usr.bin/m4/lib/ohash_qlookup.c /src/usr.bin/m4/lib/ohash_qlookupi.c /src/usr.bin/m4/parser.y:26:18: error: mdef.h: No such file or directory /src/usr.bin/m4/parser.y:27:20: error: extern.h: No such file or directory mkdep: compile failed *** [.depend] Error code 1 Stop in /src/usr.bin/m4. *** [depend] Error code 1 Stop in /src/usr.bin. *** [usr.bin.depend__D] Error code 1 Stop in /src. *** [_depend] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-10-21 04:21:21 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-10-21 04:21:21 - ERROR: failed to build world TB --- 2012-10-21 04:21:21 - 5056.85 user 592.02 system 6299.52 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-ppc@FreeBSD.ORG Sun Oct 21 08:20:42 2012 Return-Path: Delivered-To: powerpc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59D68F69; Sun, 21 Oct 2012 08:20:42 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 0D3ED8FC08; Sun, 21 Oct 2012 08:20:41 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id q9L8KeME016899; Sun, 21 Oct 2012 04:20:40 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q9L8Ke2c016897; Sun, 21 Oct 2012 08:20:40 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 21 Oct 2012 08:20:40 GMT Message-Id: <201210210820.q9L8Ke2c016897@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on powerpc/powerpc Precedence: bulk X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2012 08:20:42 -0000 TB --- 2012-10-21 06:27:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-10-21 06:27:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-10-21 06:27:00 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-10-21 06:27:00 - cleaning the object tree TB --- 2012-10-21 06:30:24 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-10-21 06:30:24 - cd /tinderbox/HEAD/powerpc/powerpc TB --- 2012-10-21 06:30:24 - /usr/local/bin/svn cleanup /src TB --- 2012-10-21 06:32:10 - /usr/local/bin/svn update /src TB --- 2012-10-21 06:32:18 - At svn revision 241794 TB --- 2012-10-21 06:32:19 - building world TB --- 2012-10-21 06:32:19 - CROSS_BUILD_TESTING=YES TB --- 2012-10-21 06:32:19 - MAKEOBJDIRPREFIX=/obj TB --- 2012-10-21 06:32:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-10-21 06:32:19 - SRCCONF=/dev/null TB --- 2012-10-21 06:32:19 - TARGET=powerpc TB --- 2012-10-21 06:32:19 - TARGET_ARCH=powerpc TB --- 2012-10-21 06:32:19 - TZ=UTC TB --- 2012-10-21 06:32:19 - __MAKE_CONF=/dev/null TB --- 2012-10-21 06:32:19 - cd /src TB --- 2012-10-21 06:32:19 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Oct 21 06:32:25 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies [...] ===> usr.bin/m4 (depend) yacc -d -o parser.c /src/usr.bin/m4/parser.y lex -t /src/usr.bin/m4/tokenizer.l > tokenizer.c rm -f .depend mkdep -f .depend -a -DEXTENDED -I/src/usr.bin/m4/lib -std=gnu99 /src/usr.bin/m4/eval.c /src/usr.bin/m4/expr.c /src/usr.bin/m4/look.c /src/usr.bin/m4/main.c /src/usr.bin/m4/misc.c /src/usr.bin/m4/gnum4.c /src/usr.bin/m4/trace.c parser.c tokenizer.c /src/usr.bin/m4/lib/ohash_create_entry.c /src/usr.bin/m4/lib/ohash_delete.c /src/usr.bin/m4/lib/ohash_do.c /src/usr.bin/m4/lib/ohash_entries.c /src/usr.bin/m4/lib/ohash_enum.c /src/usr.bin/m4/lib/ohash_init.c /src/usr.bin/m4/lib/ohash_interval.c /src/usr.bin/m4/lib/ohash_lookup_interval.c /src/usr.bin/m4/lib/ohash_lookup_memory.c /src/usr.bin/m4/lib/ohash_qlookup.c /src/usr.bin/m4/lib/ohash_qlookupi.c /src/usr.bin/m4/parser.y:26:18: error: mdef.h: No such file or directory /src/usr.bin/m4/parser.y:27:20: error: extern.h: No such file or directory mkdep: compile failed *** [.depend] Error code 1 Stop in /src/usr.bin/m4. *** [depend] Error code 1 Stop in /src/usr.bin. *** [usr.bin.depend__D] Error code 1 Stop in /src. *** [_depend] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-10-21 08:20:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-10-21 08:20:40 - ERROR: failed to build world TB --- 2012-10-21 08:20:40 - 5064.55 user 591.36 system 6820.50 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-ppc@FreeBSD.ORG Sun Oct 21 09:58:09 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BADC5AAD for ; Sun, 21 Oct 2012 09:58:09 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6573B8FC0A for ; Sun, 21 Oct 2012 09:58:06 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so936710dad.13 for ; Sun, 21 Oct 2012 02:58:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=lEsHtIQV0zSilskShL6cxnzWHpwsAeIGt90FLcZ/Hgo=; b=0jgHi7PyhaH3U5zavcb59A2dNWIz2WHtkI//lvjRM/DEJ+QG+PMvgc2Lj4sNKRMmo7 MJ0up+pmWJTmXaa/iotWrlfRE20LRc12sbCQhypI4SsnMuHRyQKCu21J9M6BYNoK8GbK LKQaDeVnqCauh9v2N2z3wzFp12ZBLihdaZe9oIYgaSl01p8JAjMgovIh+S9rwKfqnq25 YdrEG/VJCV82KWeyHdgmQNMMaR69ZDwVxJbhuBiji8/r1DrFpfvSKmwo4y8cvVWf7lfL Aw54PI7ZO/clDhnJLV8jvyCD9AgD7rfl/aCSNe5FD2Gz6WzAh+uHDDH6lCeCcjaXzLeU 5Eyg== Received: by 10.68.212.71 with SMTP id ni7mr20647190pbc.81.1350813486041; Sun, 21 Oct 2012 02:58:06 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id nr5sm4123603pbc.20.2012.10.21.02.58.03 (version=SSLv3 cipher=OTHER); Sun, 21 Oct 2012 02:58:05 -0700 (PDT) Message-ID: <5083C719.1040109@gmail.com> Date: Sun, 21 Oct 2012 02:57:45 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: freebsd-ppc@FreeBSD.org, freebsd-xorg@freebsd.org Subject: Does drm/dri currently work on PPC? Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2012 09:58:09 -0000 Do we have working drm/dri for radeon on PowerPC? I saw some old stuff that implied it, and a recent-ish PR. Anyone have this working? Or did it work once? Matt From owner-freebsd-ppc@FreeBSD.ORG Sun Oct 21 10:09:30 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 58644CFB for ; Sun, 21 Oct 2012 10:09:30 +0000 (UTC) (envelope-from michael@kryptos-security.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 02FE08FC0C for ; Sun, 21 Oct 2012 10:09:29 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fw7so2488909vcb.13 for ; Sun, 21 Oct 2012 03:09:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=OsPV4RYWJtKlKpzbzWSCtqNOCJfpJizX18X77Mjim+0=; b=GdtHAohrsLIHUS1io8P4izlmm+3qJxYkZ6laSZQumkpG3aV4dMOarhV547XSD/bdoi mCYp8CmGj+MaCLbHjLVQsJy08e+a7cRgFr6TIhZ8OeXVnwUUg6ueYpCwfb/fazBVd3js 0t+7Ugk3rszRi20QNdNbmMwIk+fhsB/uM5PSPV9dg+oOmndPJ6iDNrhX8nkpykptbY9+ TllvJHYdC5RTnpLpPrxx6L9ZI7rlALd8JCATolRpvoi5SE18YgRa76YvPXcGmgePUeX1 fbxF6vYvxpfdRc61mnkTzVlroCzQPbBXEGoO897CG2kUc3QPuAys9Xmdo1DnWbZdrxwI Fo9w== MIME-Version: 1.0 Received: by 10.52.35.82 with SMTP id f18mr7393365vdj.99.1350814163260; Sun, 21 Oct 2012 03:09:23 -0700 (PDT) Received: by 10.58.234.164 with HTTP; Sun, 21 Oct 2012 03:09:23 -0700 (PDT) X-Originating-IP: [98.231.6.79] In-Reply-To: <5083C719.1040109@gmail.com> References: <5083C719.1040109@gmail.com> Date: Sun, 21 Oct 2012 06:09:23 -0400 Message-ID: Subject: Re: Does drm/dri currently work on PPC? From: Michael Copeland To: matt X-Gm-Message-State: ALoCoQk8K4fpx1c7GkJvQp5ZodPLFb2lOKbuB2J34pOekRx90JriBola/LGvH4WxhuZ8Hov5y6/o Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-xorg@freebsd.org, freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2012 10:09:30 -0000 On Sun, Oct 21, 2012 at 5:57 AM, matt wrote: > Do we have working drm/dri for radeon on PowerPC? > > I saw some old stuff that implied it, and a recent-ish PR. > > Anyone have this working? Or did it work once? > > Matt > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > Seems fine on a mini g4 with radeon 9200. From owner-freebsd-ppc@FreeBSD.ORG Sun Oct 21 13:21:40 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB383D48 for ; Sun, 21 Oct 2012 13:21:40 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 75FFE8FC0C for ; Sun, 21 Oct 2012 13:21:39 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id v11so2573791vbm.13 for ; Sun, 21 Oct 2012 06:21:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=gbfw+Ub4Cg+lznDVO9zeAeNMe4RD62W5jF5IGpPbHl4=; b=i6sl8Sm1/vJX2N5nfY8PH2zChe2yQVjQtXEiAJGCO0Zil8YqPvcsDe6iXCW1yj3rj+ ZNLW3/wCI8t62eET2s6Vasvzy9zm0kh2uuqMC+VQQKIPBw4No7Qs5ql6jsUGdRCUsg66 SADSbxqU3Kaa0Wa9ZZT1ajMDjsfNbd4LPdUQs8B9h5wzNQn4iNDGNUhMiweqRkgs6IGl u7W4J4meUPcdp++IMeDX/B40TX/coAP94PgEdWr3ndIkOMR6wfYO8vYGmJ6d6sx6498f SZ/nN9yY35IAlqpCDuHt/HucfKx6cP7EJovJB9ja3LLzynFlgQ5hHaAJT9QsY/WbNalZ RS5Q== Received: by 10.58.203.161 with SMTP id kr1mr10780669vec.35.1350825699299; Sun, 21 Oct 2012 06:21:39 -0700 (PDT) Received: from narn.knownspace (pool-108-48-127-15.washdc.fios.verizon.net. [108.48.127.15]) by mx.google.com with ESMTPS id f10sm7257656vdk.5.2012.10.21.06.21.38 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 21 Oct 2012 06:21:39 -0700 (PDT) Date: Sun, 21 Oct 2012 09:21:36 -0400 From: Justin Hibbits To: Michael Copeland Subject: Re: Does drm/dri currently work on PPC? Message-ID: <20121021092136.20307802@narn.knownspace> In-Reply-To: References: <5083C719.1040109@gmail.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; powerpc-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-xorg@freebsd.org, freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2012 13:21:40 -0000 On Sun, 21 Oct 2012 06:09:23 -0400 Michael Copeland wrote: > On Sun, Oct 21, 2012 at 5:57 AM, matt wrote: > > > Do we have working drm/dri for radeon on PowerPC? > > > > I saw some old stuff that implied it, and a recent-ish PR. > > > > Anyone have this working? Or did it work once? > > > > Matt > > _______________________________________________ > > freebsd-ppc@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > > To unsubscribe, send any mail to > > "freebsd-ppc-unsubscribe@freebsd.org" > > > Seems fine on a mini g4 with radeon 9200. > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" Haven't had any luck on a G4 tower with radeon9600, but last I tried was over a year ago. Best I can say is try it :) - Justin From owner-freebsd-ppc@FreeBSD.ORG Sun Oct 21 21:05:44 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B210882 for ; Sun, 21 Oct 2012 21:05:44 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C7FD08FC14 for ; Sun, 21 Oct 2012 21:05:43 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so1575711pbb.13 for ; Sun, 21 Oct 2012 14:05:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=y4dlAigiX+HfvRDT4EoWExAbnGURQ0jUfOugCBu8QiI=; b=Id2ecqlM0ktBb3In1KYbogBkq+EXYf+oxJNooCm/cepySXjmxNaI7HvmPankYP/FTT upGIY292I7Pr5muT06cELIGyOmb8vWxIgvmJNaz/vnV/uuZcA7fRccGQRt9GYLcY+iVQ Ss29XvL+p2PWDLTEMWe+vpXUoY7Tb+m3XB54/aM9J4aO9UvBLQHwKdSQ0M3fR2ujL6AJ Bc2NVINc2NB9YqsOs3757mP+rKf+cB2tk/8Kumqcj+5w0PJPkX68ziJBRysRuu0eGp92 ya3gXN7nD+R/u2jFC3ATuOpT3SSsA7kqL9Z0V1PQYl5b5FCWfx0AYXX3S+MhurWar4mc PMXw== Received: by 10.68.125.229 with SMTP id mt5mr24378107pbb.51.1350853543169; Sun, 21 Oct 2012 14:05:43 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id c7sm2436435pay.10.2012.10.21.14.05.40 (version=SSLv3 cipher=OTHER); Sun, 21 Oct 2012 14:05:42 -0700 (PDT) Message-ID: <50846392.70007@gmail.com> Date: Sun, 21 Oct 2012 14:05:22 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Justin Hibbits Subject: Re: Does drm/dri currently work on PPC? References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> In-Reply-To: <20121021092136.20307802@narn.knownspace> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Oct 2012 21:05:44 -0000 On 10/21/12 06:21, Justin Hibbits wrote: > On Sun, 21 Oct 2012 06:09:23 -0400 > Michael Copeland wrote: > >> On Sun, Oct 21, 2012 at 5:57 AM, matt wrote: >> >>> Do we have working drm/dri for radeon on PowerPC? >>> >>> I saw some old stuff that implied it, and a recent-ish PR. >>> >>> Anyone have this working? Or did it work once? >>> >>> Matt >>> _______________________________________________ >>> freebsd-ppc@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>> To unsubscribe, send any mail to >>> "freebsd-ppc-unsubscribe@freebsd.org" >>> >> Seems fine on a mini g4 with radeon 9200. >> _______________________________________________ >> freebsd-ppc@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > Haven't had any luck on a G4 tower with radeon9600, but last I tried > was over a year ago. Best I can say is try it :) > > - Justin > Thanks, I'll give it a try (g4 mdd/radeon 9000). I might be compiling for a bit, but I'll send any results. Matt From owner-freebsd-ppc@FreeBSD.ORG Mon Oct 22 11:06:39 2012 Return-Path: Delivered-To: freebsd-ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5287825C for ; Mon, 22 Oct 2012 11:06:39 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 393838FC19 for ; Mon, 22 Oct 2012 11:06:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q9MB6dLh044515 for ; Mon, 22 Oct 2012 11:06:39 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9MB6ckL044513 for freebsd-ppc@FreeBSD.org; Mon, 22 Oct 2012 11:06:38 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Oct 2012 11:06:38 GMT Message-Id: <201210221106.q9MB6ckL044513@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-ppc@FreeBSD.org Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 11:06:39 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o power/170340 ppc Enabling geom-mirror on 9.1-powerpc64 prevents the sys o power/164225 ppc Boot fails on IBM 7028-6E1 (heap memory claim failed) o power/161947 ppc multimedia/libdvdnav builds broken binaries on big end o power/161045 ppc X doesn't detect ADB mouse up event until another even o power/149009 ppc sysinstall(8) on powerpc fails to install manpages, so o power/140241 ppc [kernel] [patch] Linker set problems on PowerPC EABI o power/135576 ppc gdb cannot debug threaded programs on ppc o power/133503 ppc [sound] Sound stutter after switching ttys o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer 10 problems total. From owner-freebsd-ppc@FreeBSD.ORG Mon Oct 22 17:27:44 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7FD41CC for ; Mon, 22 Oct 2012 17:27:44 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2E0338FC08 for ; Mon, 22 Oct 2012 17:27:43 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id v11so4056329vbm.13 for ; Mon, 22 Oct 2012 10:27:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=P6bVNeDaebTbU+psjL/eiImTKzFUhM2a5yt524OlZ50=; b=FwLdbvdI4UH3eZIHZgFa9xNK4k4HeqPWqQAuNS9cyCKhAFR22rNsBL8ofIVvIfiq/e /2qKNoIXTsrNQtbKMjMVmbP1/k2YGOuuC3KeOeSZje4SBYnis+kar7Yez9aEzf0LS0lZ yJp5Q3skfmnjZpORSuMwsTZH+dCClpMARkavHpMJCgMrYeecQLCZh31YzH+EDQB2IWCH yBYYnSUdwE6inGr6POcXrcZ/+4PWlHyyst25XsQ1UfjjzrDn2vaoc6hqq76u8uxk+DtF CJyrYrMLKNgZrD5ZoRGgCTiVF7LYBqdeWrZsUR8Cw1A1XFPCu/JxB8aR/7IHD+rhCxn6 +R2Q== MIME-Version: 1.0 Received: by 10.52.70.115 with SMTP id l19mr13279801vdu.127.1350926862347; Mon, 22 Oct 2012 10:27:42 -0700 (PDT) Received: by 10.58.213.74 with HTTP; Mon, 22 Oct 2012 10:27:42 -0700 (PDT) In-Reply-To: <50846392.70007@gmail.com> References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> Date: Mon, 22 Oct 2012 13:27:42 -0400 Message-ID: Subject: Re: Does drm/dri currently work on PPC? From: Justin Hibbits To: matt Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Oct 2012 17:27:44 -0000 On Sun, Oct 21, 2012 at 5:05 PM, matt wrote: > On 10/21/12 06:21, Justin Hibbits wrote: > > On Sun, 21 Oct 2012 06:09:23 -0400 > > Michael Copeland wrote: > > > >> On Sun, Oct 21, 2012 at 5:57 AM, matt wrote: > >> > >>> Do we have working drm/dri for radeon on PowerPC? > >>> > >>> I saw some old stuff that implied it, and a recent-ish PR. > >>> > >>> Anyone have this working? Or did it work once? > >>> > >>> Matt > >>> _______________________________________________ > >>> freebsd-ppc@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > >>> To unsubscribe, send any mail to > >>> "freebsd-ppc-unsubscribe@freebsd.org" > >>> > >> Seems fine on a mini g4 with radeon 9200. > >> _______________________________________________ > >> freebsd-ppc@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > > Haven't had any luck on a G4 tower with radeon9600, but last I tried > > was over a year ago. Best I can say is try it :) > > > > - Justin > > > Thanks, I'll give it a try (g4 mdd/radeon 9000). I might be compiling > for a bit, but I'll send any results. > > Matt > Remember, sys/modules/drm is not built by default for PowerPC, so you'll have to manually build those. I don't know what else is needed. - Justin From owner-freebsd-ppc@FreeBSD.ORG Tue Oct 23 00:55:41 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 19CD5471 for ; Tue, 23 Oct 2012 00:55:41 +0000 (UTC) (envelope-from alexandra.rodriguez@vgtelecomreports.com) Received: from smtp.vgtelecomreports.com (smtp.vgtelecomreports.com [108.170.43.130]) by mx1.freebsd.org (Postfix) with ESMTP id E89DA8FC0C for ; Tue, 23 Oct 2012 00:55:40 +0000 (UTC) Received: from smtp.vgtelecomreports.com (smtp.vgtelecomreports.com [184.154.41.218] (may be forged)) by smtp.vgtelecomreports.com (8.13.8/8.13.8) with ESMTP id q9MHtP4l004413 for ; Mon, 22 Oct 2012 21:55:26 +0400 Received: from WIN-BJPLN0C2TAU (WIN-BJPLN0C2TAU [184.154.41.218]) by smtp.vgtelecomreports.com with SMTP; Tue, 23 Oct 2012 01:10:37 +0100 From: Alexandra Rodriguez To: freebsd-ppc@freebsd.org Message-Id: <20121023011037.-328754031@vgtelecomreports.com> Subject: Report: The Wireless Infrastructure Market 2012-2017: Wi-Fi, WiMax, 3G, HSPA+ and LTE Date: Tue, 23 Oct 2012 01:10:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: alexandra.rodriguez@vgtelecomreports.com List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 00:55:41 -0000 Report: The Wireless Infrastructure Market 2012-2017: Wi-Fi, WiMax, 3G, HSPA+ and LTE From owner-freebsd-ppc@FreeBSD.ORG Tue Oct 23 01:40:59 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 63F81765; Tue, 23 Oct 2012 01:40:59 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 202D38FC08; Tue, 23 Oct 2012 01:40:58 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id bi1so2455873pad.13 for ; Mon, 22 Oct 2012 18:40:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=He1SZkWyW46hRWbDBjTf945y30KMPEvHSftbGyRb+FY=; b=IwtarjtKg+60jWKw/eHH/rl/QsmP8SzXXGy52s/94UEEPr7eUlUe0jW5vUpee2Y21B ahizpQ6goAzsgWecTH+SQLIL8MCKh3nolU3Q5PoImPJtrdTw41+jAjGTWmPT3ceNgWBV 40pwjrCCYYRQMVGvXfaOy7i3tOszGSXuIX8gkgVvH0Vw0Bn63ozDTZOLh86/TJpbbdW6 gXXD0p1VRHjVNoybEccOIPzQ19rFpb1rolSXwTNhvi2theFOanyb1l6+ICBNd6OuUe5F xJEdQe0S15UD/yrVLQP7V6lCgOI3yBOoRbam6z+/Z8QNBA/sOdBKwBmfzdsIQLvL2GLY GZPQ== Received: by 10.68.222.231 with SMTP id qp7mr35027079pbc.7.1350956458516; Mon, 22 Oct 2012 18:40:58 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id o1sm6790206pax.21.2012.10.22.18.40.55 (version=SSLv3 cipher=OTHER); Mon, 22 Oct 2012 18:40:57 -0700 (PDT) Message-ID: <5085F595.4050609@gmail.com> Date: Mon, 22 Oct 2012 18:40:37 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Justin Hibbits Subject: Re: Does drm/dri currently work on PPC? References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-x11@freebsd.org, freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 01:40:59 -0000 On 10/22/12 10:27, Justin Hibbits wrote: > On Sun, Oct 21, 2012 at 5:05 PM, matt > wrote: > > On 10/21/12 06:21, Justin Hibbits wrote: > > On Sun, 21 Oct 2012 06:09:23 -0400 > > Michael Copeland > wrote: > > > >> On Sun, Oct 21, 2012 at 5:57 AM, matt > wrote: > >> > >>> Do we have working drm/dri for radeon on PowerPC? > >>> > >>> I saw some old stuff that implied it, and a recent-ish PR. > >>> > >>> Anyone have this working? Or did it work once? > >>> > >>> Matt > >>> _______________________________________________ > >>> freebsd-ppc@freebsd.org > mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > >>> To unsubscribe, send any mail to > >>> "freebsd-ppc-unsubscribe@freebsd.org > " > >>> > >> Seems fine on a mini g4 with radeon 9200. > >> _______________________________________________ > >> freebsd-ppc@freebsd.org > mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > >> To unsubscribe, send any mail to > "freebsd-ppc-unsubscribe@freebsd.org > " > > Haven't had any luck on a G4 tower with radeon9600, but last I tried > > was over a year ago. Best I can say is try it :) > > > > - Justin > > > Thanks, I'll give it a try (g4 mdd/radeon 9000). I might be compiling > for a bit, but I'll send any results. > > Matt > > > Remember, sys/modules/drm is not built by default for PowerPC, so > you'll have to manually build those. I don't know what else is needed. > > - Justin I am running CURRENT based on yesterday evening's CVS. I built the drm modules: cd /usr/src/sys/modules/drm && make && make install This required setting NO_WERROR= and WERROR= in the makefiles for radeon and r128. The errors are "value computed is not used". The second fix required to get it to build was to make sure LINUX_DRM gets undefined, this may result from my build process, but the undef is ifdef'd for amd64. After the module is built "successfully" and installed, kldloading it doesn't do anything, no drm0 created. kldload radeon.ko creates a drm0, but Xorg immediately crashes when loading the radeon driver, bringing down the entire system. I assume there is some endian-unsafe stuff in radeon and drm maybe? My system is an AGP Radeon r200 on an MDD G4. Any ideas or anything I can do to help? Matt From owner-freebsd-ppc@FreeBSD.ORG Tue Oct 23 01:59:55 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1BD978DA; Tue, 23 Oct 2012 01:59:55 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id A51B78FC08; Tue, 23 Oct 2012 01:59:54 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id v11so4646812vbm.13 for ; Mon, 22 Oct 2012 18:59:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=wOWK/7aX1OoKo697RK8MBBWsE+/Fu2RhQO5zpTbBJ5k=; b=z7o63nw+WMjCfbBroHrBPIGRzx3dyDLU0QHSkW9JbvEI+ITgPspgzliHy6WqDi0j3n ynzv7IMSc7hu6FBMaoLtzFSJx9Qn5ZErQToWFCrqsYWMRJRQA58IaqnDEbygeHxotLH8 Dw2GHOUp6662qG9gtnaPMF2MSaWkSTVeCztHcwtRt5wkd2wiXSKHGXf0LAq0TgRf9RmZ MtKlPgLM6hA/WGrFwzXyvmvsQpze8r41rKDO3yhE5S/LhzEsifGxu6Mrt4sotjilyja0 41a6ktFLUjOIA0m0wBj0eZvhO2/Bl96d/q64cWP3jpvqsvCOenTaVdt3FW1v4M6zkDZt DvxQ== Received: by 10.58.203.161 with SMTP id kr1mr20000475vec.35.1350957588157; Mon, 22 Oct 2012 18:59:48 -0700 (PDT) Received: from narn.knownspace (pool-108-48-127-15.washdc.fios.verizon.net. [108.48.127.15]) by mx.google.com with ESMTPS id w17sm11877493vdf.16.2012.10.22.18.59.47 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 22 Oct 2012 18:59:48 -0700 (PDT) Date: Mon, 22 Oct 2012 21:59:45 -0400 From: Justin Hibbits To: matt Subject: Re: Does drm/dri currently work on PPC? Message-ID: <20121022215945.436873dc@narn.knownspace> In-Reply-To: <5085F595.4050609@gmail.com> References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; powerpc-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 01:59:55 -0000 On Mon, 22 Oct 2012 18:40:37 -0700 matt wrote: > On 10/22/12 10:27, Justin Hibbits wrote: > > On Sun, Oct 21, 2012 at 5:05 PM, matt > > wrote: > > > > On 10/21/12 06:21, Justin Hibbits wrote: > > > On Sun, 21 Oct 2012 06:09:23 -0400 > > > Michael Copeland > > wrote: > > > > > >> On Sun, Oct 21, 2012 at 5:57 AM, matt > > wrote: > > >> > > >>> Do we have working drm/dri for radeon on PowerPC? > > >>> > > >>> I saw some old stuff that implied it, and a recent-ish PR. > > >>> > > >>> Anyone have this working? Or did it work once? > > >>> > > >>> Matt > > >>> _______________________________________________ > > >>> freebsd-ppc@freebsd.org > > mailing list > > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > > >>> To unsubscribe, send any mail to > > >>> "freebsd-ppc-unsubscribe@freebsd.org > > " > > >>> > > >> Seems fine on a mini g4 with radeon 9200. > > >> _______________________________________________ > > >> freebsd-ppc@freebsd.org > > mailing list > > >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > > >> To unsubscribe, send any mail to > > "freebsd-ppc-unsubscribe@freebsd.org > > " > > > Haven't had any luck on a G4 tower with radeon9600, but last > > > I tried was over a year ago. Best I can say is try it :) > > > > > > - Justin > > > > > Thanks, I'll give it a try (g4 mdd/radeon 9000). I might be > > compiling for a bit, but I'll send any results. > > > > Matt > > > > > > Remember, sys/modules/drm is not built by default for PowerPC, so > > you'll have to manually build those. I don't know what else is > > needed. > > > > - Justin > > I am running CURRENT based on yesterday evening's CVS. > I built the drm modules: > cd /usr/src/sys/modules/drm && make && make install > This required setting NO_WERROR= and WERROR= in the makefiles for > radeon and r128. The errors are "value computed is not used". > The second fix required to get it to build was to make sure LINUX_DRM > gets undefined, this may result from my build process, but the undef > is ifdef'd for amd64. > > After the module is built "successfully" and installed, kldloading it > doesn't do anything, no drm0 created. > kldload radeon.ko creates a drm0, but Xorg immediately crashes when > loading the radeon driver, bringing down the entire system. > > I assume there is some endian-unsafe stuff in radeon and drm maybe? > My system is an AGP Radeon r200 on an MDD G4. > > Any ideas or anything I can do to help? > > Matt You're exactly where I was when I last tried. I didn't have the patience to look into it. I did read today, though, that NetBSD has working drm on PowerPC, so you can do some diffing with that codebase, or even try NetBSD on a spare partition to confirm. Beyond that, some ddb magic could help track down where the problem lies -- firewire cable and a spare machine come in quite handy for this type of thing, with dcons. Even getting a backtrace would be a good start to tracking down the bugs. DRM is something I want to get working on PowerPC, but it's low on my list (only so many hours in a day unfortunately), so I'm glad somebody is looking :) - Justin From owner-freebsd-ppc@FreeBSD.ORG Tue Oct 23 03:06:14 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F5BB666; Tue, 23 Oct 2012 03:06:14 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2E9768FC08; Tue, 23 Oct 2012 03:06:13 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so99652pbb.13 for ; Mon, 22 Oct 2012 20:06:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=6kN3NGRKqSTCOSYBOTA9pRRbV6m0KHHm0e1+jtD2Iko=; b=Q17bfHDza42TWD7RaHM7dztTmWLTGv8XUJHSsZdCjh8qW1bq4IL3l9Mt4KoQIIuPJq /F5vRHP+wu/Lvnp7yOLMMmUbRuzrx/6wEPTznGVM8cVMZ+jQd9aqiVmpp5q42X9yAwLJ ers+PPwUPJmx0MMO2jgq29+dQbZI/LO5KaeMPru0zcmwufI4IIJrHUsCSOpB1xo+ohpR tOdwVSDWydeyOo0RROepYH3K2i+xU8ZQc9PhGbUVS+Xng7/L05bIHSGbzTiooqW49wNl 3/S4oBtKfQK2CPKDJ4HvrcNfWT+RT/w7Nsrbia3c7ctTa13tp2E6ISuBVS4kmM9jx4b6 NvzQ== Received: by 10.66.90.73 with SMTP id bu9mr31113840pab.71.1350961573809; Mon, 22 Oct 2012 20:06:13 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id oi2sm6903683pbb.62.2012.10.22.20.06.10 (version=SSLv3 cipher=OTHER); Mon, 22 Oct 2012 20:06:12 -0700 (PDT) Message-ID: <50860990.7020204@gmail.com> Date: Mon, 22 Oct 2012 20:05:52 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Justin Hibbits Subject: Re: Does drm/dri currently work on PPC? References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> In-Reply-To: <20121022215945.436873dc@narn.knownspace> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 03:06:14 -0000 On 10/22/12 18:59, Justin Hibbits wrote: > On Mon, 22 Oct 2012 18:40:37 -0700 > matt wrote: > >> On 10/22/12 10:27, Justin Hibbits wrote: >>> On Sun, Oct 21, 2012 at 5:05 PM, matt >> > wrote: >>> >>> On 10/21/12 06:21, Justin Hibbits wrote: >>> > On Sun, 21 Oct 2012 06:09:23 -0400 >>> > Michael Copeland >> > wrote: >>> > >>> >> On Sun, Oct 21, 2012 at 5:57 AM, matt >> > wrote: >>> >> >>> >>> Do we have working drm/dri for radeon on PowerPC? >>> >>> >>> >>> I saw some old stuff that implied it, and a recent-ish PR. >>> >>> >>> >>> Anyone have this working? Or did it work once? >>> >>> >>> >>> Matt >>> >>> _______________________________________________ >>> >>> freebsd-ppc@freebsd.org >>> mailing list >>> >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>> >>> To unsubscribe, send any mail to >>> >>> "freebsd-ppc-unsubscribe@freebsd.org >>> " >>> >>> >>> >> Seems fine on a mini g4 with radeon 9200. >>> >> _______________________________________________ >>> >> freebsd-ppc@freebsd.org >>> mailing list >>> >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>> >> To unsubscribe, send any mail to >>> "freebsd-ppc-unsubscribe@freebsd.org >>> " >>> > Haven't had any luck on a G4 tower with radeon9600, but last >>> > I tried was over a year ago. Best I can say is try it :) >>> > >>> > - Justin >>> > >>> Thanks, I'll give it a try (g4 mdd/radeon 9000). I might be >>> compiling for a bit, but I'll send any results. >>> >>> Matt >>> >>> >>> Remember, sys/modules/drm is not built by default for PowerPC, so >>> you'll have to manually build those. I don't know what else is >>> needed. >>> >>> - Justin >> I am running CURRENT based on yesterday evening's CVS. >> I built the drm modules: >> cd /usr/src/sys/modules/drm && make && make install >> This required setting NO_WERROR= and WERROR= in the makefiles for >> radeon and r128. The errors are "value computed is not used". >> The second fix required to get it to build was to make sure LINUX_DRM >> gets undefined, this may result from my build process, but the undef >> is ifdef'd for amd64. >> >> After the module is built "successfully" and installed, kldloading it >> doesn't do anything, no drm0 created. >> kldload radeon.ko creates a drm0, but Xorg immediately crashes when >> loading the radeon driver, bringing down the entire system. >> >> I assume there is some endian-unsafe stuff in radeon and drm maybe? >> My system is an AGP Radeon r200 on an MDD G4. >> >> Any ideas or anything I can do to help? >> >> Matt > You're exactly where I was when I last tried. I didn't have the > patience to look into it. I did read today, though, that NetBSD has > working drm on PowerPC, so you can do some diffing with that codebase, > or even try NetBSD on a spare partition to confirm. Beyond that, some > ddb magic could help track down where the problem lies -- firewire > cable and a spare machine come in quite handy for this type of thing, > with dcons. Even getting a backtrace would be a good start to tracking > down the bugs. > > DRM is something I want to get working on PowerPC, but it's low on my > list (only so many hours in a day unfortunately), so I'm glad somebody > is looking :) > > - Justin > I tried OpenBSD. They have drm, but no working agp yet. A couple lockups under X thrashed the filesystem and I was over it. The sources for macppc are in transition or something and weren't building for me a week or so ago. NetBSD is probably worth another shot, I started out on MacBSD when it was new. Luckily I have a collection of IDE disks to swap, so it should be painless as far as not having to wipe one for the other. My guess is that we're talking to the card in big endian, because our drivers probably assume the host is little endian like pci. If that's the problem, fixes here will probably apply for sparc and arm (and anything else with non little-endian modes). This is armchair conjecture of course. My amd64 box has firewire, although I've yet to use DDB over firewire. Sounds like fun, so I'll try to work on getting a backtrace. Only so many hours indeed. Matt From owner-freebsd-ppc@FreeBSD.ORG Tue Oct 23 23:32:37 2012 Return-Path: Delivered-To: powerpc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 154D6593; Tue, 23 Oct 2012 23:32:37 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id B47488FC08; Tue, 23 Oct 2012 23:32:36 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id q9NNWZNH091885; Tue, 23 Oct 2012 19:32:35 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q9NNWZwC091884; Tue, 23 Oct 2012 23:32:35 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 23 Oct 2012 23:32:35 GMT Message-Id: <201210232332.q9NNWZwC091884@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on powerpc/powerpc Precedence: bulk X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 23:32:37 -0000 TB --- 2012-10-23 21:01:18 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-10-23 21:01:18 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-10-23 21:01:18 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-10-23 21:01:19 - cleaning the object tree TB --- 2012-10-23 21:01:19 - checking out /src from svn://svn.freebsd.org/base/head TB --- 2012-10-23 21:01:19 - cd /tinderbox/HEAD/powerpc/powerpc TB --- 2012-10-23 21:01:19 - /usr/local/bin/svn cleanup /src TB --- 2012-10-23 21:03:08 - /usr/local/bin/svn update /src TB --- 2012-10-23 21:03:21 - At svn revision 241968 TB --- 2012-10-23 21:03:22 - building world TB --- 2012-10-23 21:03:22 - CROSS_BUILD_TESTING=YES TB --- 2012-10-23 21:03:22 - MAKEOBJDIRPREFIX=/obj TB --- 2012-10-23 21:03:22 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-10-23 21:03:22 - SRCCONF=/dev/null TB --- 2012-10-23 21:03:22 - TARGET=powerpc TB --- 2012-10-23 21:03:22 - TARGET_ARCH=powerpc TB --- 2012-10-23 21:03:22 - TZ=UTC TB --- 2012-10-23 21:03:22 - __MAKE_CONF=/dev/null TB --- 2012-10-23 21:03:22 - cd /src TB --- 2012-10-23 21:03:22 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Tue Oct 23 21:03:29 UTC 2012 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Oct 23 23:22:46 UTC 2012 TB --- 2012-10-23 23:22:46 - generating LINT kernel config TB --- 2012-10-23 23:22:46 - cd /src/sys/powerpc/conf TB --- 2012-10-23 23:22:46 - /usr/bin/make -B LINT TB --- 2012-10-23 23:22:46 - cd /src/sys/powerpc/conf TB --- 2012-10-23 23:22:46 - /usr/sbin/config -m LINT TB --- 2012-10-23 23:22:46 - building LINT kernel TB --- 2012-10-23 23:22:46 - CROSS_BUILD_TESTING=YES TB --- 2012-10-23 23:22:46 - MAKEOBJDIRPREFIX=/obj TB --- 2012-10-23 23:22:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-10-23 23:22:46 - SRCCONF=/dev/null TB --- 2012-10-23 23:22:46 - TARGET=powerpc TB --- 2012-10-23 23:22:46 - TARGET_ARCH=powerpc TB --- 2012-10-23 23:22:46 - TZ=UTC TB --- 2012-10-23 23:22:46 - __MAKE_CONF=/dev/null TB --- 2012-10-23 23:22:46 - cd /src TB --- 2012-10-23 23:22:46 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Oct 23 23:22:46 UTC 2012 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] :> hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/obj/src/make.amd64/make sh /src/sys/conf/newvers.sh LINT cc -c -O -pipe -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror vers.c linking kernel uipc_socket.o: In function `sosend_copyin': uipc_socket.c:(.text+0x2edc): undefined reference to `socow_setup' *** [kernel] Error code 1 Stop in /obj/powerpc.powerpc/src/sys/LINT. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-10-23 23:32:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-10-23 23:32:35 - ERROR: failed to build LINT kernel TB --- 2012-10-23 23:32:35 - 7424.31 user 955.51 system 9076.86 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-ppc@FreeBSD.ORG Fri Oct 26 00:54:23 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 62021596; Fri, 26 Oct 2012 00:54:23 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 24CCC8FC08; Fri, 26 Oct 2012 00:54:22 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so2567453pbb.13 for ; Thu, 25 Oct 2012 17:54:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=P56kCNhaOsjp0fpMys/A7MlAns66XTqRrUHD1IJdy20=; b=Vf8uu68WydzyOdEvg2mx4NYMZHNzLJzbYjTv6vixgos6KjADr75XUGEVDK3tDmseHd j9CWFirhWlaapTWV5WuxI37uAWAUADv7uJpCTuS37Xqm6DOffMiXWzTv8TpJRI7EMIUL 9S0NBwhCjQ6z/QqlTAvRXL+MZZZhgeOxXhjcck+LStq6oAeGiNCtNwDqOkUGk7S38Oi0 7NzmEB9jeKhus1Ie4IKtXORHPrVp8F+z4Z4bq6r1CobY9I/ov1SUJev2cjtgtSOh6Xv9 RFzvQYBnL3l4lgoOEm3EVAEWej+XvoSheS9ujcbi9lQIOAVuxmHApIlLIx0vZsM601Pp k/HQ== Received: by 10.66.79.166 with SMTP id k6mr57720401pax.25.1351212862618; Thu, 25 Oct 2012 17:54:22 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id ho7sm226702pbc.3.2012.10.25.17.54.19 (version=SSLv3 cipher=OTHER); Thu, 25 Oct 2012 17:54:21 -0700 (PDT) Message-ID: <5089DF27.9020803@gmail.com> Date: Thu, 25 Oct 2012 17:53:59 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Albert Vest Subject: Re: Does drm/dri currently work on PPC? References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> In-Reply-To: <5089A6DB.9070904@brakiri.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, Justin Hibbits , freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 00:54:23 -0000 On 10/25/12 13:53, Albert Vest wrote: > > I also use Radeon r200, but on an i386 machine. Same symptom happens to > me if I don't force BusType to PCI in my xorg.conf: > > ... > Option "BusType" "PCI" # Force IGP to PCI > ... > > hope that helps, > Albert. > So far it doesn't look like that helps. It took a bit longer to crash, and the screen flashed a pleasing pinkish-maroon before the system locked up. I'm going to keep trying to fiddle driver section values, but I think there's something architecturally wrong/missing. Here's what I've noticed: In /usr/src/sys/dev/drmP.h, we have htole16 and htole32 wrapped around drm read and write functions, which neither netbsd nor openbsd have (perhaps they wrap it elsewhere). drm_read8 and drm_write8 on freebsd are not wrapped, which seems odd to me? I can understand all or none, but "some" seems like 8-bit reads and writes are either going to be the only ones that work or the only ones that don't. When I try to start X, I am also seeing this mess (X -configure as well) with WITH_NEW_XORG. I have hw.ofwfb.relax_mmap=1. [ 251.670] (WW) xf86EnableIO -1 [ 251.671] (II) xf86EnableIO: ffffffff [ 251.671] (WW) Can't map IO space! [ 251.671] (--) PCI: (0:0:16:0) 1002:4966:1002:4966 rev 1, Mem @ 0x98000000/134217728, 0x90000000/65536, I/O @ 0x00000400/256, BIOS @ 0x????????/65536 [ 251.719] List of video drivers: [ 251.719] ati [ 251.719] radeon [ 251.720] (II) LoadModule: "ati" [ 251.791] (II) Loading /usr/local/lib/xorg/modules/drivers/ati_drv.so [ 251.803] (II) Module ati: vendor="X.Org Foundation" [ 251.803] compiled for 1.10.6, module version = 6.14.6 [ 251.803] Module class: X.Org Video Driver [ 251.803] ABI class: X.Org Video Driver, version 10.0 [ 251.803] (II) LoadModule: "radeon" [ 251.805] (II) Loading /usr/local/lib/xorg/modules/drivers/radeon_drv.so [ 251.895] (II) Module radeon: vendor="X.Org Foundation" [ 251.895] compiled for 1.10.6, module version = 6.14.6 [ 251.895] Module class: X.Org Video Driver [ 251.895] ABI class: X.Org Video Driver, version 10.0 [ 251.895] (WW) xf86EnableIO -1 [ 251.895] (II) xf86EnableIO: ffffffff [ 251.895] (WW) Can't map IO space! [ 251.895] No devices to configure. Configuration failed. From owner-freebsd-ppc@FreeBSD.ORG Fri Oct 26 01:30:22 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A863C87; Fri, 26 Oct 2012 01:30:22 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id B577B8FC17; Fri, 26 Oct 2012 01:30:21 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fw7so3224862vcb.13 for ; Thu, 25 Oct 2012 18:30:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=6c6oemEnj462E9DDwwicN31VIl2qYNgdx3npkQWFE90=; b=JvZVkGz6DUgu1LDy2gjBLOeGM5cdurpXN56cH19U9TGVdf8oFw57gSEoaCss/5IW7g k07L6usZMSuOzGyxaYUUt5w+jkUKUO4wc3Ph3s+aTppmiD2V56DDctThZTJsDZfUVuLm 2FrGmAJrikFf+LFt5kpJLkNd6iBXaIPLry/yaIXiztmeymYxiFhN5EDRZcc9z30Nx0oK e8mM6zwbzd8VlSnuOKLsHMiSK4djzvvELh9lyb89Q7sWP+I9c9Csrgftkh/3GKqRuvo2 pVFmnbzC0zM6C59UpF2esIyZxfPlgO4KQKCRunArRtEXNK9fIgm5uOvfN5YBl+kKJMgk BWxg== Received: by 10.52.65.51 with SMTP id u19mr28679968vds.3.1351215020855; Thu, 25 Oct 2012 18:30:20 -0700 (PDT) Received: from narn.knownspace (pool-108-48-127-15.washdc.fios.verizon.net. [108.48.127.15]) by mx.google.com with ESMTPS id cz16sm90107vdb.15.2012.10.25.18.30.20 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 25 Oct 2012 18:30:20 -0700 (PDT) Date: Thu, 25 Oct 2012 21:30:18 -0400 From: Justin Hibbits To: matt Subject: Re: Does drm/dri currently work on PPC? Message-ID: <20121025213018.2bfa5068@narn.knownspace> In-Reply-To: <5089DF27.9020803@gmail.com> References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; powerpc-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, Albert Vest , freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 01:30:22 -0000 On Thu, 25 Oct 2012 17:53:59 -0700 matt wrote: > On 10/25/12 13:53, Albert Vest wrote: > > > > I also use Radeon r200, but on an i386 machine. Same symptom > > happens to me if I don't force BusType to PCI in my xorg.conf: > > > > ... > > Option "BusType" "PCI" # Force IGP to PCI > > ... > > > > hope that helps, > > Albert. > > > > So far it doesn't look like that helps. It took a bit longer to crash, > and the screen flashed a pleasing pinkish-maroon before the system > locked up. I'm going to keep trying to fiddle driver section values, > but I think there's something architecturally wrong/missing. > > Here's what I've noticed: > > In /usr/src/sys/dev/drmP.h, > we have htole16 and htole32 wrapped around drm read and write > functions, which neither netbsd nor openbsd have (perhaps they wrap > it elsewhere). drm_read8 and drm_write8 on freebsd are not wrapped, > which seems odd to me? I can understand all or none, but "some" seems > like 8-bit reads and writes are either going to be the only ones that > work or the only ones that don't. > > When I try to start X, I am also seeing this mess (X -configure as > well) with WITH_NEW_XORG. I have hw.ofwfb.relax_mmap=1. > > [ 251.670] (WW) xf86EnableIO -1 > [ 251.671] (II) xf86EnableIO: ffffffff > [ 251.671] (WW) Can't map IO space! > [ 251.671] (--) PCI: (0:0:16:0) 1002:4966:1002:4966 rev 1, Mem @ > 0x98000000/134217728, 0x90000000/65536, I/O @ 0x00000400/256, BIOS @ > 0x????????/65536 > [ 251.719] List of video drivers: > [ 251.719] ati > [ 251.719] radeon > [ 251.720] (II) LoadModule: "ati" > [ 251.791] (II) > Loading /usr/local/lib/xorg/modules/drivers/ati_drv.so [ 251.803] > (II) Module ati: vendor="X.Org Foundation" [ 251.803] compiled > for 1.10.6, module version = 6.14.6 [ 251.803] Module class: > X.Org Video Driver [ 251.803] ABI class: X.Org Video Driver, > version 10.0 [ 251.803] (II) LoadModule: "radeon" > [ 251.805] (II) > Loading /usr/local/lib/xorg/modules/drivers/radeon_drv.so > [ 251.895] (II) Module radeon: vendor="X.Org > Foundation" [ 251.895] compiled for 1.10.6, module version = > 6.14.6 [ 251.895] Module class: X.Org Video Driver > [ 251.895] ABI class: X.Org Video Driver, version 10.0 > [ 251.895] (WW) xf86EnableIO -1 [ 251.895] (II) xf86EnableIO: > ffffffff [ 251.895] (WW) Can't map IO space! > [ 251.895] No devices to configure. Configuration failed. > Can't help you with the X error issue you're seeing (does it work if you don't load the radeon module? That'd be the first thing to get working, then worry about drm), but you may be on to something with the DRM endian you found. NetBSD's drmP.h writes bus-order (little endian) only in register space, not in framebuffer space. Although I think this would only mess up the colors, but I may be wrong. Nice find! - Justin From owner-freebsd-ppc@FreeBSD.ORG Fri Oct 26 02:38:39 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BCDD96C5; Fri, 26 Oct 2012 02:38:39 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7B8798FC0C; Fri, 26 Oct 2012 02:38:39 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so2616582pbb.13 for ; Thu, 25 Oct 2012 19:38:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=LDrcJSUfEvZ+oVoV2+wlRbr18Ch1e6Aih9c0SU5OzCE=; b=s+An35Ouk66AYeIyBo0wxoXs/sGk73RlyqyovZl/ipzZXjLPPKjCqTnWObIdBM+g+P RVTqNycx/msRHDCkDNtYveaCLX3KZGgy1VGPyCN2unz8oX+jUo1aoKeN0iiRuiMGRB5J XsAKXibo9OmF+b/P5CnMxKVtxR6H4X909Vf7TEIZv5VxdBJkfhSdm8EY8JRLf+3dhKf8 9xEd3f1X784OkCqeXq7biyeBsgWyUgKcn0LliFm0SRvLBgj3Ex5ObAFEersX9Tn/wf74 39PsJYuT9DWQhir4YfbLoM5MWMNPqK5ouvRpeFNvzC3SH69EDenL3g73b8Ku/Wkl/c+I deBg== Received: by 10.68.137.234 with SMTP id ql10mr4028128pbb.158.1351219118916; Thu, 25 Oct 2012 19:38:38 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id ox7sm365301pbb.14.2012.10.25.19.38.36 (version=SSLv3 cipher=OTHER); Thu, 25 Oct 2012 19:38:37 -0700 (PDT) Message-ID: <5089F799.9030507@gmail.com> Date: Thu, 25 Oct 2012 19:38:17 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Justin Hibbits Subject: Re: Does drm/dri currently work on PPC? References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> In-Reply-To: <20121025213018.2bfa5068@narn.knownspace> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, Albert Vest , freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 02:38:39 -0000 On 10/25/12 18:30, Justin Hibbits wrote: > On Thu, 25 Oct 2012 17:53:59 -0700 > matt wrote: > >> On 10/25/12 13:53, Albert Vest wrote: >>> I also use Radeon r200, but on an i386 machine. Same symptom >>> happens to me if I don't force BusType to PCI in my xorg.conf: >>> >>> ... >>> Option "BusType" "PCI" # Force IGP to PCI >>> ... >>> >>> hope that helps, >>> Albert. >>> >> So far it doesn't look like that helps. It took a bit longer to crash, >> and the screen flashed a pleasing pinkish-maroon before the system >> locked up. I'm going to keep trying to fiddle driver section values, >> but I think there's something architecturally wrong/missing. >> >> Here's what I've noticed: >> >> In /usr/src/sys/dev/drmP.h, >> we have htole16 and htole32 wrapped around drm read and write >> functions, which neither netbsd nor openbsd have (perhaps they wrap >> it elsewhere). drm_read8 and drm_write8 on freebsd are not wrapped, >> which seems odd to me? I can understand all or none, but "some" seems >> like 8-bit reads and writes are either going to be the only ones that >> work or the only ones that don't. >> >> When I try to start X, I am also seeing this mess (X -configure as >> well) with WITH_NEW_XORG. I have hw.ofwfb.relax_mmap=1. >> >> [ 251.670] (WW) xf86EnableIO -1 >> [ 251.671] (II) xf86EnableIO: ffffffff >> [ 251.671] (WW) Can't map IO space! >> [ 251.671] (--) PCI: (0:0:16:0) 1002:4966:1002:4966 rev 1, Mem @ >> 0x98000000/134217728, 0x90000000/65536, I/O @ 0x00000400/256, BIOS @ >> 0x????????/65536 >> [ 251.719] List of video drivers: >> [ 251.719] ati >> [ 251.719] radeon >> [ 251.720] (II) LoadModule: "ati" >> [ 251.791] (II) >> Loading /usr/local/lib/xorg/modules/drivers/ati_drv.so [ 251.803] >> (II) Module ati: vendor="X.Org Foundation" [ 251.803] compiled >> for 1.10.6, module version = 6.14.6 [ 251.803] Module class: >> X.Org Video Driver [ 251.803] ABI class: X.Org Video Driver, >> version 10.0 [ 251.803] (II) LoadModule: "radeon" >> [ 251.805] (II) >> Loading /usr/local/lib/xorg/modules/drivers/radeon_drv.so >> [ 251.895] (II) Module radeon: vendor="X.Org >> Foundation" [ 251.895] compiled for 1.10.6, module version = >> 6.14.6 [ 251.895] Module class: X.Org Video Driver >> [ 251.895] ABI class: X.Org Video Driver, version 10.0 >> [ 251.895] (WW) xf86EnableIO -1 [ 251.895] (II) xf86EnableIO: >> ffffffff [ 251.895] (WW) Can't map IO space! >> [ 251.895] No devices to configure. Configuration failed. >> > Can't help you with the X error issue you're seeing (does it work if > you don't load the radeon module? That'd be the first thing to get > working, then worry about drm), but you may be on to something with the > DRM endian you found. NetBSD's drmP.h writes bus-order (little endian) > only in register space, not in framebuffer space. Although I think this > would only mess up the colors, but I may be wrong. > > Nice find! > > - Justin > It was working without DRM "out-of-the-box". Of course I've made a mess trying different versions of both Xorg and the radeon driver. I'm in the process of getting back to the working config so I can be sure any test changes work/don't work. OpenBSD's mpi@ apparently did a lot recently over there getting DRM to work on the G4 mini. We already had about half of the commits I see at freshbsd, in one way or another...Our rmb/wmb() I think has had PPC barriers since earlier this year? He did #define __BIG_ENDIAN, which apparently was a big deal for the drm code (it's ifdef'd in a couple places), not sure if we are already doing that. If someone has a G4 radeon mini they could test to see if drm works for them or not, to rule out AGP issues (I guess they are PCI?). I'm not sure how the OpenBSD attachment process works vs ours, some of the other commits of note were related to passing the BAR and memory regions from the vgapci to drm. When I kldload drm after compiling it, it doesn't do anything...but if I kldload radeon.ko, it recognizes agp memory and being related to vgapci at the correct pci address...I'm not sure if we "are there" or not. I also didn't have DRM on OpenBSD either. I think if radeon had drm on *any* big-endian platform it should rule out endian issues in drm or radeon. Not sure if this is the case, I guess macppc would be the most likely. Matt From owner-freebsd-ppc@FreeBSD.ORG Fri Oct 26 04:55:59 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 663C7FB8; Fri, 26 Oct 2012 04:55:59 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 24A588FC08; Fri, 26 Oct 2012 04:55:59 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1192442dad.13 for ; Thu, 25 Oct 2012 21:55:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ltWDpcx1U7X/CtXzgvFOKYwG5g1yS6gWyQmE9y2PKG4=; b=LplbwlaMy2S/ZJtZdUlaQD76HSpuOg72vgCv8SxN5lhtM1H5SQjU38zGjJ5RQywaUO 5kVnRpeKJAr53YPTuE6KB9qkEB8e/BVUVBk1QWgpVTy2krGIQwGDUd28M0C/+JE2scHf zuh5XGAaOXFGYdaY87uQ2pznboR2qcQuZ0gscNG8IOF7W9C6tq4iv6fdK8AMd7hDTFqx d4gDHS19GA43UoJgpvxgWNPlJ/56yXqTZhDqBulnd687SbAT/jCxtPNwyWJ3QipqKuPO 3nqruLv6WttxUtZOuMrl6Jx+tdijb/1zDdfhverya8C08PeJOEjzGDzfJBXQg/xo394W guDw== Received: by 10.66.77.168 with SMTP id t8mr58972174paw.28.1351227358700; Thu, 25 Oct 2012 21:55:58 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id tw5sm542450pbc.48.2012.10.25.21.55.56 (version=SSLv3 cipher=OTHER); Thu, 25 Oct 2012 21:55:57 -0700 (PDT) Message-ID: <508A17C9.4030007@gmail.com> Date: Thu, 25 Oct 2012 21:55:37 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Justin Hibbits Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> In-Reply-To: <5089F799.9030507@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, Albert Vest , freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 04:55:59 -0000 > It was working without DRM "out-of-the-box". Of course I've made a mess > trying different versions of both Xorg and the radeon driver. I'm in the > process of getting back to the working config so I can be sure any test > changes work/don't work. > > OpenBSD's mpi@ apparently did a lot recently over there getting DRM to > work on the G4 mini. We already had about half of the commits I see at > freshbsd, in one way or another...Our rmb/wmb() I think has had PPC > barriers since earlier this year? He did #define __BIG_ENDIAN, which > apparently was a big deal for the drm code (it's ifdef'd in a couple > places), not sure if we are already doing that. > If someone has a G4 radeon mini they could test to see if drm works for > them or not, to rule out AGP issues (I guess they are PCI?). > > I'm not sure how the OpenBSD attachment process works vs ours, some of > the other commits of note were related to passing the BAR and memory > regions from the vgapci to drm. When I kldload drm after compiling it, > it doesn't do anything...but if I kldload radeon.ko, it recognizes agp > memory and being related to vgapci at the correct pci address...I'm not > sure if we "are there" or not. I also didn't have DRM on OpenBSD either. > > I think if radeon had drm on *any* big-endian platform it should rule > out endian issues in drm or radeon. Not sure if this is the case, I > guess macppc would be the most likely. > > Matt So I removed WITH_NEW_XORG, deinstalled a ton of ports, and reinstalled Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this matters). I previously put a lot of WERROR= and NO_WERROR= into various drm makefiles to get gcc to shut up about unused return values. X -configure worked, and the xorg log indicates the drm device was successfully opened and I have drm on PPC. mesa-demos is marked broken for PPC, haven't tried glxinfo or glxgears yet. The good news is it works! The bad news: -Cannot switch back to syscons, screen gets corrupted then the system hard locks -WITH_NEW_XORG breaks it somehow Thanks to mpi@openbsd.org, Justin & Nathan! Matt From owner-freebsd-ppc@FreeBSD.ORG Fri Oct 26 12:15:34 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0925740B; Fri, 26 Oct 2012 12:15:34 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 88D468FC16; Fri, 26 Oct 2012 12:15:31 +0000 (UTC) Received: by mail-vc0-f182.google.com with SMTP id fw7so3698749vcb.13 for ; Fri, 26 Oct 2012 05:15:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zPaLivI1s/Rvx8k8DpUHcp+lCjJQOWCmkEbkwQZG2wk=; b=ZhWadCdzoKfo9Oj6zAFyuRgAUey3FriVOtT2opt6XrJsIauRaaklPhxxPo/x6ypPrq ii12cVZ7e4m+UKENBcEY/Q53DvweUhDc9/sm9CY18cq5TQlhTSwzXxjU6ko2jUYUooRg iCzpZlodBicuD8zB75QRcUiZLle2HoDATRl+D03qC0e/GM/7ElcA3czPikVLVkJRzgXE TtJcMBul1Imwk/84Sn1toxQmdxf1p20vNcntFTN5TdvNK0PXfu7ppwtD8oDBiCcZWdma c2ovz3vLLUjOar5jvasBpjJ4BFKfrkv/IXcFABYlry/bj+1VrUxiX+kP9TuYxoTVGGWX e7gQ== MIME-Version: 1.0 Received: by 10.220.210.193 with SMTP id gl1mr18554711vcb.58.1351253731157; Fri, 26 Oct 2012 05:15:31 -0700 (PDT) Received: by 10.58.213.74 with HTTP; Fri, 26 Oct 2012 05:15:31 -0700 (PDT) In-Reply-To: <508A17C9.4030007@gmail.com> References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> Date: Fri, 26 Oct 2012 08:15:31 -0400 Message-ID: Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) From: Justin Hibbits To: matt Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-x11@freebsd.org, Albert Vest , freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 12:15:34 -0000 On Fri, Oct 26, 2012 at 12:55 AM, matt wrote: > > > It was working without DRM "out-of-the-box". Of course I've made a mess > > trying different versions of both Xorg and the radeon driver. I'm in the > > process of getting back to the working config so I can be sure any test > > changes work/don't work. > > > > OpenBSD's mpi@ apparently did a lot recently over there getting DRM to > > work on the G4 mini. We already had about half of the commits I see at > > freshbsd, in one way or another...Our rmb/wmb() I think has had PPC > > barriers since earlier this year? He did #define __BIG_ENDIAN, which > > apparently was a big deal for the drm code (it's ifdef'd in a couple > > places), not sure if we are already doing that. > > If someone has a G4 radeon mini they could test to see if drm works for > > them or not, to rule out AGP issues (I guess they are PCI?). > > > > I'm not sure how the OpenBSD attachment process works vs ours, some of > > the other commits of note were related to passing the BAR and memory > > regions from the vgapci to drm. When I kldload drm after compiling it, > > it doesn't do anything...but if I kldload radeon.ko, it recognizes agp > > memory and being related to vgapci at the correct pci address...I'm not > > sure if we "are there" or not. I also didn't have DRM on OpenBSD either. > > > > I think if radeon had drm on *any* big-endian platform it should rule > > out endian issues in drm or radeon. Not sure if this is the case, I > > guess macppc would be the most likely. > > > > Matt > So I removed WITH_NEW_XORG, deinstalled a ton of ports, and reinstalled > Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this > matters). I previously put a lot of WERROR= and NO_WERROR= into various > drm makefiles to get gcc to shut up about unused return values. X > -configure worked, and the xorg log indicates the drm device was > successfully opened and I have drm on PPC. > mesa-demos is marked broken for PPC, haven't tried glxinfo or glxgears yet. > > The good news is it works! > The bad news: > -Cannot switch back to syscons, screen gets corrupted then the system > hard locks > -WITH_NEW_XORG breaks it somehow > > Thanks to mpi@openbsd.org, Justin & Nathan! > > Matt > That's fantastic! If I'm able to get my current project done (PMU sleep/speed change on PowerBook) I'll definitely give that a shot this weekend. One thing that may help with switching back to syscons is, NetBSD has a radeonfb driver for console framebuffer.Earlier in the week I briefly looked at that, and it may not be too difficult to port it to FreeBSD and integrate with syscons. Only major hurdle for that would be dealing with ofwfb as well. Just some more tinkering :) Excellent news! - Justin From owner-freebsd-ppc@FreeBSD.ORG Fri Oct 26 14:31:28 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CBA69136; Fri, 26 Oct 2012 14:31:28 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id 906EC8FC08; Fri, 26 Oct 2012 14:31:28 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0MCI009028CFT400@smtpauth3.wiscmail.wisc.edu>; Fri, 26 Oct 2012 09:31:28 -0500 (CDT) Received: from comporellon.tachypleus.net (adsl-71-150-249-157.dsl.mdsnwi.sbcglobal.net [71.150.249.157]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0MCI004KD8CD4510@smtpauth3.wiscmail.wisc.edu>; Fri, 26 Oct 2012 09:31:27 -0500 (CDT) Date: Fri, 26 Oct 2012 09:31:25 -0500 From: Nathan Whitehorn Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) In-reply-to: <508A17C9.4030007@gmail.com> To: matt Message-id: <508A9EBD.3080107@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=71.150.249.157 X-Spam-PmxInfo: Server=avs-16, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.10.26.142120, SenderIP=71.150.249.157 References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121019 Thunderbird/16.0.1 Cc: freebsd-x11@freebsd.org, Albert Vest , Justin Hibbits , freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 14:31:28 -0000 On 10/25/12 23:55, matt wrote: >> It was working without DRM "out-of-the-box". Of course I've made a mess >> trying different versions of both Xorg and the radeon driver. I'm in the >> process of getting back to the working config so I can be sure any test >> changes work/don't work. >> >> OpenBSD's mpi@ apparently did a lot recently over there getting DRM to >> work on the G4 mini. We already had about half of the commits I see at >> freshbsd, in one way or another...Our rmb/wmb() I think has had PPC >> barriers since earlier this year? He did #define __BIG_ENDIAN, which >> apparently was a big deal for the drm code (it's ifdef'd in a couple >> places), not sure if we are already doing that. >> If someone has a G4 radeon mini they could test to see if drm works for >> them or not, to rule out AGP issues (I guess they are PCI?). >> >> I'm not sure how the OpenBSD attachment process works vs ours, some of >> the other commits of note were related to passing the BAR and memory >> regions from the vgapci to drm. When I kldload drm after compiling it, >> it doesn't do anything...but if I kldload radeon.ko, it recognizes agp >> memory and being related to vgapci at the correct pci address...I'm not >> sure if we "are there" or not. I also didn't have DRM on OpenBSD either. >> >> I think if radeon had drm on *any* big-endian platform it should rule >> out endian issues in drm or radeon. Not sure if this is the case, I >> guess macppc would be the most likely. >> >> Matt > So I removed WITH_NEW_XORG, deinstalled a ton of ports, and reinstalled > Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this > matters). I previously put a lot of WERROR= and NO_WERROR= into various > drm makefiles to get gcc to shut up about unused return values. X > -configure worked, and the xorg log indicates the drm device was > successfully opened and I have drm on PPC. > mesa-demos is marked broken for PPC, haven't tried glxinfo or glxgears yet. > > The good news is it works! > The bad news: > -Cannot switch back to syscons, screen gets corrupted then the system > hard locks > -WITH_NEW_XORG breaks it somehow > > Thanks to mpi@openbsd.org, Justin & Nathan! > > Matt > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" Great to hear! I checked in some code to define __BIG_ENDIAN if needed in -CURRENT's drm (Linux uses a different number of underscores than we do for perverse reasons). -Nathan From owner-freebsd-ppc@FreeBSD.ORG Fri Oct 26 18:51:56 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3F6F2C4F; Fri, 26 Oct 2012 18:51:56 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id D27918FC0C; Fri, 26 Oct 2012 18:51:55 +0000 (UTC) Received: from deuterium.andreas.nets (dhclient-91-190-14-19.flashcable.ch [91.190.14.19]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id q9QIpcJ2061109; Fri, 26 Oct 2012 20:51:40 +0200 (CEST) (envelope-from andreast-list@fgznet.ch) Message-ID: <508ADBBA.1060201@fgznet.ch> Date: Fri, 26 Oct 2012 20:51:38 +0200 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Nathan Whitehorn , matt Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> <508A9EBD.3080107@freebsd.org> In-Reply-To: <508A9EBD.3080107@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: freebsd-x11@freebsd.org, Albert Vest , Justin Hibbits , freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 18:51:56 -0000 On 26.10.12 16:31, Nathan Whitehorn wrote: > On 10/25/12 23:55, matt wrote: >>> It was working without DRM "out-of-the-box". Of course I've made a mess >>> trying different versions of both Xorg and the radeon driver. I'm in the >>> process of getting back to the working config so I can be sure any test >>> changes work/don't work. >>> >>> OpenBSD's mpi@ apparently did a lot recently over there getting DRM to >>> work on the G4 mini. We already had about half of the commits I see at >>> freshbsd, in one way or another...Our rmb/wmb() I think has had PPC >>> barriers since earlier this year? He did #define __BIG_ENDIAN, which >>> apparently was a big deal for the drm code (it's ifdef'd in a couple >>> places), not sure if we are already doing that. >>> If someone has a G4 radeon mini they could test to see if drm works for >>> them or not, to rule out AGP issues (I guess they are PCI?). >>> >>> I'm not sure how the OpenBSD attachment process works vs ours, some of >>> the other commits of note were related to passing the BAR and memory >>> regions from the vgapci to drm. When I kldload drm after compiling it, >>> it doesn't do anything...but if I kldload radeon.ko, it recognizes agp >>> memory and being related to vgapci at the correct pci address...I'm not >>> sure if we "are there" or not. I also didn't have DRM on OpenBSD either. >>> >>> I think if radeon had drm on *any* big-endian platform it should rule >>> out endian issues in drm or radeon. Not sure if this is the case, I >>> guess macppc would be the most likely. >>> >>> Matt >> So I removed WITH_NEW_XORG, deinstalled a ton of ports, and reinstalled >> Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this >> matters). I previously put a lot of WERROR= and NO_WERROR= into various >> drm makefiles to get gcc to shut up about unused return values. X >> -configure worked, and the xorg log indicates the drm device was >> successfully opened and I have drm on PPC. >> mesa-demos is marked broken for PPC, haven't tried glxinfo or glxgears yet. >> >> The good news is it works! >> The bad news: >> -Cannot switch back to syscons, screen gets corrupted then the system >> hard locks >> -WITH_NEW_XORG breaks it somehow >> >> Thanks to mpi@openbsd.org, Justin & Nathan! >> >> Matt >> _______________________________________________ >> freebsd-ppc@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > > Great to hear! I checked in some code to define __BIG_ENDIAN if needed > in -CURRENT's drm (Linux uses a different number of underscores than we > do for perverse reasons). Thank you very much all! I can confirm it works here too (G5 32-bit): [helium:~] andreast% dmesg |grep drm drm0: on vgapci0 info: [drm] Initialized radeon 1.31.0 20080613 info: [drm] Setting GART location based on new memory map info: [drm] Loading R300 Microcode info: [drm] Num pipes: 1 info: [drm] writeback test succeeded in 1 usecs and glxgears gives around 1250FPS vs. 52FPS w/o dri. Andreas From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 27 01:07:31 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45BABE3B for ; Sat, 27 Oct 2012 01:07:31 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 07C808FC0A for ; Sat, 27 Oct 2012 01:07:30 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id bi1so2416857pad.13 for ; Fri, 26 Oct 2012 18:07:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=gHVpsHvngBaUfhtLO7pZAR1ErJU6D3pMOeZMLZ665s8=; b=n2O7cpcO3WwSf3UTWXhB551TWCAF4Or7UNHTMtAAhYFhZCnBn/6ghDZB2YXG1ZMr8N Ulilkt+9TOIDlK2xdWhZfYRxP8ttlmJ06L620ZgWruVsnbXC5iTjBMHjabmepRVHvOKd zhUel5mfAwYRyss3wjcnxn85MZs84527Eoj/8BeokeKT1Npvm2KHKqDtspi0mI3VTGBX KY2v4fauYMyaoPmSF5T3ojuGgM9us8TVnPFVz+dICOgdSoSFV5E/NwEXbC5spV6BYLJA nhVk4iSdATychOC/r7QUpMvJ8JXWA3lQzSULvnLcr3C2baQ9kMQr1JTApr14lKShjBz9 wuGw== Received: by 10.66.88.197 with SMTP id bi5mr65924188pab.58.1351300050414; Fri, 26 Oct 2012 18:07:30 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id vu7sm1962272pbc.9.2012.10.26.18.07.27 (version=SSLv3 cipher=OTHER); Fri, 26 Oct 2012 18:07:29 -0700 (PDT) Message-ID: <508B33BC.1090107@gmail.com> Date: Fri, 26 Oct 2012 18:07:08 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Justin Hibbits Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 01:07:31 -0000 On 10/26/12 05:15, Justin Hibbits wrote: > On Fri, Oct 26, 2012 at 12:55 AM, matt > wrote: > > > > It was working without DRM "out-of-the-box". Of course I've made > a mess > > trying different versions of both Xorg and the radeon driver. > I'm in the > > process of getting back to the working config so I can be sure > any test > > changes work/don't work. > > > > OpenBSD's mpi@ apparently did a lot recently over there getting > DRM to > > work on the G4 mini. We already had about half of the commits I > see at > > freshbsd, in one way or another...Our rmb/wmb() I think has had PPC > > barriers since earlier this year? He did #define __BIG_ENDIAN, which > > apparently was a big deal for the drm code (it's ifdef'd in a couple > > places), not sure if we are already doing that. > > If someone has a G4 radeon mini they could test to see if drm > works for > > them or not, to rule out AGP issues (I guess they are PCI?). > > > > I'm not sure how the OpenBSD attachment process works vs ours, > some of > > the other commits of note were related to passing the BAR and memory > > regions from the vgapci to drm. When I kldload drm after > compiling it, > > it doesn't do anything...but if I kldload radeon.ko, it > recognizes agp > > memory and being related to vgapci at the correct pci > address...I'm not > > sure if we "are there" or not. I also didn't have DRM on OpenBSD > either. > > > > I think if radeon had drm on *any* big-endian platform it should > rule > > out endian issues in drm or radeon. Not sure if this is the case, I > > guess macppc would be the most likely. > > > > Matt > So I removed WITH_NEW_XORG, deinstalled a ton of ports, and > reinstalled > Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this > matters). I previously put a lot of WERROR= and NO_WERROR= into > various > drm makefiles to get gcc to shut up about unused return values. X > -configure worked, and the xorg log indicates the drm device was > successfully opened and I have drm on PPC. > mesa-demos is marked broken for PPC, haven't tried glxinfo or > glxgears yet. > > The good news is it works! > The bad news: > -Cannot switch back to syscons, screen gets corrupted then the system > hard locks > -WITH_NEW_XORG breaks it somehow > > Thanks to mpi@openbsd.org , Justin & Nathan! > > Matt > > > That's fantastic! If I'm able to get my current project done (PMU > sleep/speed change on PowerBook) I'll definitely give that a shot this > weekend. > > One thing that may help with switching back to syscons is, NetBSD has > a radeonfb driver for console framebuffer.Earlier in the week I > briefly looked at that, and it may not be too difficult to port it to > FreeBSD and integrate with syscons. Only major hurdle for that would > be dealing with ofwfb as well. Just some more tinkering :) > > Excellent news! > > - Justin Be aware that radeonfb has had issues before, I think it's what was making the console unusable on my NetBSD-current attempt. NetBSD's radeonfb maintainer turned it off for the release of 6.0, I think. Might be better now. Switching consoles or killing X (such as reboot or shutdown) definitely crashes the system at least 75% of the time (small dataset). It rebooted once after being told to reboot from X, but it may have just panic'd and rebooted itself. I haven't attached gdb to X yet over ssh while it happens, so I'm not sure if X is crashing or syscons/ofwfb is corrupting memory trying to take over or both. Good luck with those PMUs. Matt From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 27 01:12:13 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC4E6E9A; Sat, 27 Oct 2012 01:12:13 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id A43A48FC0C; Sat, 27 Oct 2012 01:12:13 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so3324285pbb.13 for ; Fri, 26 Oct 2012 18:12:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Ps1FWc925A2yUjEDOW/FKMiCTlnzdarOEIcpK8qk69s=; b=kMuSPgbw1pFb/8LL+1OxTTJzL4fjJZb7O0NTr6Oeg8btYpRLBn9h/0pYNQ9W9GD+Z0 FLUBmyiTbtKMHy2TFQh/XfIK5eRmhx9kgWDePCH7NjJPevbTd3lzQZbvGzgCGV/Jpl5q /PmL70aDKWyUhgf/tYjicXeIVS+Kpb3qSVK3J6eh0RtvWobZ0g45+I7OOO6pRBIagRkh JBa997w/7hU4hIZoUi7DhgHPvtwaZwzvSGcTq++T7aPMsZcuZ/EeFkfWuRBPx4LGDiL3 Taov7z9Hxx8gIGlN2FCnbVxzeUIFsN6pxNwNDdXEPuF+cmsDG8Pxs5lznHhGZtMIWhi9 KnAA== Received: by 10.68.130.201 with SMTP id og9mr74392270pbb.12.1351300332196; Fri, 26 Oct 2012 18:12:12 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id n7sm1823001pav.26.2012.10.26.18.12.09 (version=SSLv3 cipher=OTHER); Fri, 26 Oct 2012 18:12:11 -0700 (PDT) Message-ID: <508B34D6.6000502@gmail.com> Date: Fri, 26 Oct 2012 18:11:50 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Andreas Tobler Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> <508A9EBD.3080107@freebsd.org> <508ADBBA.1060201@fgznet.ch> In-Reply-To: <508ADBBA.1060201@fgznet.ch> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, freebsd-ppc@freebsd.org, Albert Vest , Justin Hibbits X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 01:12:14 -0000 On 10/26/12 11:51, Andreas Tobler wrote: > On 26.10.12 16:31, Nathan Whitehorn wrote: >> On 10/25/12 23:55, matt wrote: >>>> It was working without DRM "out-of-the-box". Of course I've made a >>>> mess >>>> trying different versions of both Xorg and the radeon driver. I'm >>>> in the >>>> process of getting back to the working config so I can be sure any >>>> test >>>> changes work/don't work. >>>> >>>> OpenBSD's mpi@ apparently did a lot recently over there getting DRM to >>>> work on the G4 mini. We already had about half of the commits I see at >>>> freshbsd, in one way or another...Our rmb/wmb() I think has had PPC >>>> barriers since earlier this year? He did #define __BIG_ENDIAN, which >>>> apparently was a big deal for the drm code (it's ifdef'd in a couple >>>> places), not sure if we are already doing that. >>>> If someone has a G4 radeon mini they could test to see if drm works >>>> for >>>> them or not, to rule out AGP issues (I guess they are PCI?). >>>> >>>> I'm not sure how the OpenBSD attachment process works vs ours, some of >>>> the other commits of note were related to passing the BAR and memory >>>> regions from the vgapci to drm. When I kldload drm after compiling it, >>>> it doesn't do anything...but if I kldload radeon.ko, it recognizes agp >>>> memory and being related to vgapci at the correct pci address...I'm >>>> not >>>> sure if we "are there" or not. I also didn't have DRM on OpenBSD >>>> either. >>>> >>>> I think if radeon had drm on *any* big-endian platform it should rule >>>> out endian issues in drm or radeon. Not sure if this is the case, I >>>> guess macppc would be the most likely. >>>> >>>> Matt >>> So I removed WITH_NEW_XORG, deinstalled a ton of ports, and reinstalled >>> Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this >>> matters). I previously put a lot of WERROR= and NO_WERROR= into various >>> drm makefiles to get gcc to shut up about unused return values. X >>> -configure worked, and the xorg log indicates the drm device was >>> successfully opened and I have drm on PPC. >>> mesa-demos is marked broken for PPC, haven't tried glxinfo or >>> glxgears yet. >>> >>> The good news is it works! >>> The bad news: >>> -Cannot switch back to syscons, screen gets corrupted then the system >>> hard locks >>> -WITH_NEW_XORG breaks it somehow >>> >>> Thanks to mpi@openbsd.org, Justin & Nathan! >>> >>> Matt >>> _______________________________________________ >>> freebsd-ppc@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >> >> Great to hear! I checked in some code to define __BIG_ENDIAN if needed >> in -CURRENT's drm (Linux uses a different number of underscores than we >> do for perverse reasons). > > Thank you very much all! > > I can confirm it works here too (G5 32-bit): > > [helium:~] andreast% dmesg |grep drm > drm0: on vgapci0 > info: [drm] Initialized radeon 1.31.0 20080613 > info: [drm] Setting GART location based on new memory map > info: [drm] Loading R300 Microcode > info: [drm] Num pipes: 1 > info: [drm] writeback test succeeded in 1 usecs > > and glxgears gives around 1250FPS vs. 52FPS w/o dri. > > Andreas > > > Can you change consoles or exit X successfully? btw...issue "sync" a couple times first just in case :) Also, is that an AGP or PCIe G5? Thanks, Matt From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 27 01:21:29 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D65E25DC; Sat, 27 Oct 2012 01:21:29 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8D3308FC0C; Sat, 27 Oct 2012 01:21:28 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so3327275pbb.13 for ; Fri, 26 Oct 2012 18:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=cGg/SCTg6ZIcJ0wmVybw3fYQtS/pHf+kGTxq6zoOL/U=; b=KzZL39S1OQasjmP+p5HLJxTpjiMAfsMyvHuV3ARQmoSv4HjFJ/3pNxw2p3/QfpJnWl et/cri/8rVI2B50T7w+VJNifLZTlVKyYdbszHm9vz5dWsoP8T58AWAXPYL28BjYfs/Oi niEmfjlf/dp+LgHxgLrJ4N9TqswnBuQVcgZ7hiufjHjC7xwcRCNmXVWfrw/RN73r3Znb 1gwaa2/wsUy6NRkMKLTgqZMvUMRwN5WohmL6XwsDZnwyzeBLcwisIA3nzM6SroD22WAF R+VeR8fek6n/r20RRz6GHONRr/B9atyyIMTpFMJLyH2m3m5ebYggpYd1JvB1eMpF65E/ lvuQ== Received: by 10.68.190.71 with SMTP id go7mr75091128pbc.66.1351300888041; Fri, 26 Oct 2012 18:21:28 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id kn8sm1979697pbc.24.2012.10.26.18.21.25 (version=SSLv3 cipher=OTHER); Fri, 26 Oct 2012 18:21:27 -0700 (PDT) Message-ID: <508B3702.8060906@gmail.com> Date: Fri, 26 Oct 2012 18:21:06 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Nathan Whitehorn Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> <508A9EBD.3080107@freebsd.org> In-Reply-To: <508A9EBD.3080107@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, Justin Hibbits , freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 01:21:30 -0000 On 10/26/12 07:31, Nathan Whitehorn wrote: > On 10/25/12 23:55, matt wrote: >>> It was working without DRM "out-of-the-box". Of course I've made a mess >>> trying different versions of both Xorg and the radeon driver. I'm in >>> the >>> process of getting back to the working config so I can be sure any test >>> changes work/don't work. >>> >>> OpenBSD's mpi@ apparently did a lot recently over there getting DRM to >>> work on the G4 mini. We already had about half of the commits I see at >>> freshbsd, in one way or another...Our rmb/wmb() I think has had PPC >>> barriers since earlier this year? He did #define __BIG_ENDIAN, which >>> apparently was a big deal for the drm code (it's ifdef'd in a couple >>> places), not sure if we are already doing that. >>> If someone has a G4 radeon mini they could test to see if drm works for >>> them or not, to rule out AGP issues (I guess they are PCI?). >>> >>> I'm not sure how the OpenBSD attachment process works vs ours, some of >>> the other commits of note were related to passing the BAR and memory >>> regions from the vgapci to drm. When I kldload drm after compiling it, >>> it doesn't do anything...but if I kldload radeon.ko, it recognizes agp >>> memory and being related to vgapci at the correct pci address...I'm not >>> sure if we "are there" or not. I also didn't have DRM on OpenBSD >>> either. >>> >>> I think if radeon had drm on *any* big-endian platform it should rule >>> out endian issues in drm or radeon. Not sure if this is the case, I >>> guess macppc would be the most likely. >>> >>> Matt >> So I removed WITH_NEW_XORG, deinstalled a ton of ports, and reinstalled >> Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this >> matters). I previously put a lot of WERROR= and NO_WERROR= into various >> drm makefiles to get gcc to shut up about unused return values. X >> -configure worked, and the xorg log indicates the drm device was >> successfully opened and I have drm on PPC. >> mesa-demos is marked broken for PPC, haven't tried glxinfo or >> glxgears yet. >> >> The good news is it works! >> The bad news: >> -Cannot switch back to syscons, screen gets corrupted then the system >> hard locks >> -WITH_NEW_XORG breaks it somehow >> >> Thanks to mpi@openbsd.org, Justin & Nathan! >> >> Matt >> _______________________________________________ >> freebsd-ppc@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > > Great to hear! I checked in some code to define __BIG_ENDIAN if needed > in -CURRENT's drm (Linux uses a different number of underscores than > we do for perverse reasons). > -Nathan > Thanks, I'm glad we were just a define or so away. Score for byteorder=4321! Matt From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 27 05:09:08 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7D8284B; Sat, 27 Oct 2012 05:09:08 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 624D48FC12; Sat, 27 Oct 2012 05:09:07 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so3396247pbb.13 for ; Fri, 26 Oct 2012 22:09:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=dqQVQNljBOR3lL8a6aoEK7vEVCW912X1u9ANEiZ4PF4=; b=MnbjIFOzLU8FUBbWHr+o33NmxC3vIDaO7A701L0mv8PHDwxXd+V9kmPmdcS8kKtiJA s40nvxnbe1vxtSYpwEbupxpAiV1t0ywyrddzTToJKNVI40gP9/T+taXIvpuMgUsMB2Wj Esxfs5X/kpVEklHMJ5r6kdoSjH9snEjI2DeyeJq5QuwooOHqmf/tzpBNAUz+5g3/vSWr BkzOlUMwPs7TZZUY3cM/o/L+VNatvdRgXwBQy2CfccKQM+A6ng3X4jTG6LbtP8KqcMCm kkzDkYlZw+9bfPlFLkTwo3te/aUtJ0rEvcWQ+GJSWG8lQnH2/zkZRuXOxgQGpBSxIdde UUgA== Received: by 10.68.226.167 with SMTP id rt7mr76218253pbc.94.1351314547441; Fri, 26 Oct 2012 22:09:07 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id m8sm2117909pax.38.2012.10.26.22.09.04 (version=SSLv3 cipher=OTHER); Fri, 26 Oct 2012 22:09:05 -0700 (PDT) Message-ID: <508B6C5D.9010500@gmail.com> Date: Fri, 26 Oct 2012 22:08:45 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Justin Hibbits Subject: Re: Does drm/dri currently work on PPC? References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-x11@freebsd.org, freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 05:09:08 -0000 On 10/26/12 05:15, Justin Hibbits wrote: > On Fri, Oct 26, 2012 at 12:55 AM, matt > wrote: > > > > It was working without DRM "out-of-the-box". Of course I've made > a mess > > trying different versions of both Xorg and the radeon driver. > I'm in the > > process of getting back to the working config so I can be sure > any test > > changes work/don't work. > > > > OpenBSD's mpi@ apparently did a lot recently over there getting > DRM to > > work on the G4 mini. We already had about half of the commits I > see at > > freshbsd, in one way or another...Our rmb/wmb() I think has had PPC > > barriers since earlier this year? He did #define __BIG_ENDIAN, which > > apparently was a big deal for the drm code (it's ifdef'd in a couple > > places), not sure if we are already doing that. > > If someone has a G4 radeon mini they could test to see if drm > works for > > them or not, to rule out AGP issues (I guess they are PCI?). > > > > I'm not sure how the OpenBSD attachment process works vs ours, > some of > > the other commits of note were related to passing the BAR and memory > > regions from the vgapci to drm. When I kldload drm after > compiling it, > > it doesn't do anything...but if I kldload radeon.ko, it > recognizes agp > > memory and being related to vgapci at the correct pci > address...I'm not > > sure if we "are there" or not. I also didn't have DRM on OpenBSD > either. > > > > I think if radeon had drm on *any* big-endian platform it should > rule > > out endian issues in drm or radeon. Not sure if this is the case, I > > guess macppc would be the most likely. > > > > Matt > So I removed WITH_NEW_XORG, deinstalled a ton of ports, and > reinstalled > Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this > matters). I previously put a lot of WERROR= and NO_WERROR= into > various > drm makefiles to get gcc to shut up about unused return values. X > -configure worked, and the xorg log indicates the drm device was > successfully opened and I have drm on PPC. > mesa-demos is marked broken for PPC, haven't tried glxinfo or > glxgears yet. > > The good news is it works! > The bad news: > -Cannot switch back to syscons, screen gets corrupted then the system > hard locks > -WITH_NEW_XORG breaks it somehow > > Thanks to mpi@openbsd.org , Justin & Nathan! > > Matt > > > That's fantastic! If I'm able to get my current project done (PMU > sleep/speed change on PowerBook) I'll definitely give that a shot this > weekend. > > One thing that may help with switching back to syscons is, NetBSD has > a radeonfb driver for console framebuffer.Earlier in the week I > briefly looked at that, and it may not be too difficult to port it to > FreeBSD and integrate with syscons. Only major hurdle for that would > be dealing with ofwfb as well. Just some more tinkering :) > > Excellent news! > > - Justin New development, I get random hangs...I'm going to try disabling EXA for XAA. Backtrace during hang: #0 0x41fd4b28 in ioctl () from /lib/libc.so.7 #1 0x420c0a7c in drmIoctl () from /usr/local/lib/libdrm.so.2 #2 0x420c0bdc in drmCommandNone () from /usr/local/lib/libdrm.so.2 #3 0x421a03e8 in RADEONWaitForIdleCP () from /usr/local/lib/xorg/modules/drivers/radeon_drv.so #4 0x421feef8 in RADEONSyncCP () from /usr/local/lib/xorg/modules/drivers/radeon_drv.so #5 0x42295748 in exaWaitSync () from /usr/local/lib/xorg/modules/libexa.so #6 0x42296d40 in ExaDoPrepareAccess () from /usr/local/lib/xorg/modules/libexa.so #7 0x42297e90 in exaPrepareAccessReg_classic () from /usr/local/lib/xorg/modules/libexa.so #8 0x42296f14 in exaPrepareAccess () from /usr/local/lib/xorg/modules/libexa.so #9 0x422a2c78 in ExaCheckImageGlyphBlt () from /usr/local/lib/xorg/modules/libexa.so #10 0x01976a6c in miImageText8 () #11 0x018f2f0c in DamageSetup () #12 0x018337ec in doImageText () #13 0x01833984 in ImageText () #14 0x0182cb48 in ProcImageText8 () #15 0x0182efe8 in Dispatch () #16 0x01823188 in main () Is this 8bit DRM crashing it because unlike 16 and 32 it's not byteswapped? BTW, mesa-demos compiles if you insert a copy of byteswap.h (I got mine from arnold.se's article about bitcoin, of all things) and you define the powerpc write barrier. Matt From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 27 17:14:07 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A899AA8; Sat, 27 Oct 2012 17:14:07 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id DB9368FC08; Sat, 27 Oct 2012 17:14:05 +0000 (UTC) Received: from deuterium.andreas.nets (dhclient-91-190-14-19.flashcable.ch [91.190.14.19]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id q9RHDsfG052534; Sat, 27 Oct 2012 19:13:55 +0200 (CEST) (envelope-from andreast-list@fgznet.ch) Message-ID: <508C1652.6070909@fgznet.ch> Date: Sat, 27 Oct 2012 19:13:54 +0200 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: matt Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> <508A9EBD.3080107@freebsd.org> <508ADBBA.1060201@fgznet.ch> <508B34D6.6000502@gmail.com> In-Reply-To: <508B34D6.6000502@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: freebsd-x11@freebsd.org, freebsd-ppc@freebsd.org, Albert Vest , Justin Hibbits X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 17:14:07 -0000 On 27.10.12 03:11, matt wrote: > On 10/26/12 11:51, Andreas Tobler wrote: >> On 26.10.12 16:31, Nathan Whitehorn wrote: >>> On 10/25/12 23:55, matt wrote: >>>>> It was working without DRM "out-of-the-box". Of course I've made a >>>>> mess >>>>> trying different versions of both Xorg and the radeon driver. I'm >>>>> in the >>>>> process of getting back to the working config so I can be sure any >>>>> test >>>>> changes work/don't work. >>>>> >>>>> OpenBSD's mpi@ apparently did a lot recently over there getting DRM to >>>>> work on the G4 mini. We already had about half of the commits I see at >>>>> freshbsd, in one way or another...Our rmb/wmb() I think has had PPC >>>>> barriers since earlier this year? He did #define __BIG_ENDIAN, which >>>>> apparently was a big deal for the drm code (it's ifdef'd in a couple >>>>> places), not sure if we are already doing that. >>>>> If someone has a G4 radeon mini they could test to see if drm works >>>>> for >>>>> them or not, to rule out AGP issues (I guess they are PCI?). >>>>> >>>>> I'm not sure how the OpenBSD attachment process works vs ours, some of >>>>> the other commits of note were related to passing the BAR and memory >>>>> regions from the vgapci to drm. When I kldload drm after compiling it, >>>>> it doesn't do anything...but if I kldload radeon.ko, it recognizes agp >>>>> memory and being related to vgapci at the correct pci address...I'm >>>>> not >>>>> sure if we "are there" or not. I also didn't have DRM on OpenBSD >>>>> either. >>>>> >>>>> I think if radeon had drm on *any* big-endian platform it should rule >>>>> out endian issues in drm or radeon. Not sure if this is the case, I >>>>> guess macppc would be the most likely. >>>>> >>>>> Matt >>>> So I removed WITH_NEW_XORG, deinstalled a ton of ports, and reinstalled >>>> Xorg. I rebuild drm with __BIG_ENDIAN defined (not sure if this >>>> matters). I previously put a lot of WERROR= and NO_WERROR= into various >>>> drm makefiles to get gcc to shut up about unused return values. X >>>> -configure worked, and the xorg log indicates the drm device was >>>> successfully opened and I have drm on PPC. >>>> mesa-demos is marked broken for PPC, haven't tried glxinfo or >>>> glxgears yet. >>>> >>>> The good news is it works! >>>> The bad news: >>>> -Cannot switch back to syscons, screen gets corrupted then the system >>>> hard locks >>>> -WITH_NEW_XORG breaks it somehow >>>> >>>> Thanks to mpi@openbsd.org, Justin & Nathan! >>>> >>>> Matt >>>> _______________________________________________ >>>> freebsd-ppc@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >>> >>> Great to hear! I checked in some code to define __BIG_ENDIAN if needed >>> in -CURRENT's drm (Linux uses a different number of underscores than we >>> do for perverse reasons). >> >> Thank you very much all! >> >> I can confirm it works here too (G5 32-bit): >> >> [helium:~] andreast% dmesg |grep drm >> drm0: on vgapci0 >> info: [drm] Initialized radeon 1.31.0 20080613 >> info: [drm] Setting GART location based on new memory map >> info: [drm] Loading R300 Microcode >> info: [drm] Num pipes: 1 >> info: [drm] writeback test succeeded in 1 usecs >> >> and glxgears gives around 1250FPS vs. 52FPS w/o dri. >> >> Andreas >> >> >> > Can you change consoles or exit X successfully? > btw...issue "sync" a couple times first just in case :) > Also, is that an AGP or PCIe G5? I can exit X and restart X successfully. I can also switch (ctrl-alt-F1-F8) between X and console and back (ctrl-alt-F9). Even with glxgears running. No lock-up. It is an AGP card: (--) RADEON(0): Chipset: "ATI Radeon 9600XT AR (AGP)" (ChipID = 0x4152) (--) RADEON(0): Mapped VideoRAM: 131072 kByte (128 bit DDR SDRAM) These are my modules: Section "Module" Load "extmod" Load "record" Load "dbe" Load "glx" Load "dri" Load "dri2" EndSection And nothing special in the driver section. Andreas From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 27 17:28:50 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 286C0F92 for ; Sat, 27 Oct 2012 17:28:50 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id C88C58FC0A for ; Sat, 27 Oct 2012 17:28:49 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 8342F11BEA for ; Sun, 28 Oct 2012 03:28:47 +1000 (EST) Received: (from dommail.onthenet.com.au [173.8.251.193]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with HTTP/1.1 id BHH66510 (AUTH peterg@ptree32.com.au); Sun, 28 Oct 2012 03:28:46 +1000 (EST) From: Peter Grehan Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) To: freebsd-ppc@freebsd.org X-Mailer: Mirapoint Webmail Direct 4.2.4-GA MIME-Version: 1.0 In-Reply-To: <508C1652.6070909@fgznet.ch> References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> <508A9EBD.3080107@freebsd.org> <508ADBBA.1060201@fgznet.ch> <508B34D6.6000502@gmail.com> <508C1652.6070909@fgznet.ch> Message-Id: <201210271728.040348@dommail.onthenet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 28 Oct 2012 03:28:46 +1000 (EST) X-Junkmail-Info: PLING_QUERY,RDNS_NONE X-Junkmail-Status: score=13/51, host=dommail.onthenet.com.au X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 17:28:50 -0000 This sounds interesting, but (very) dumb question: is there anything worth trying that can make use of this, other than glxgears ?? I'd like to try it out but not sure what to do with it. later, Peter. From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 27 19:27:43 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D77A6AD3; Sat, 27 Oct 2012 19:27:43 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 959C18FC0C; Sat, 27 Oct 2012 19:27:43 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so1883486dad.13 for ; Sat, 27 Oct 2012 12:27:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=oPmg8RKEMbe8cpvvt6HDgQuHKz4QGaAr4klDfPuC9uY=; b=o0xCprN3EX46vEejQ4usBgfkfLn/4xY36P5hZ2oPwikn7dB3Ddjqj9mx1kF3Gih3k2 gE7V7myFaVueE1pD3MvKiVKZWpjKk+hwlmODeQeN6Q0u1e3fghq7HZ/pAjxkKAAw8/I2 JjCvxYeC+PxlkxDd+6uIuu/8G7p0WVTnf+EftG+QpnZfBohzP2rxm5kOMkWrmk2/XaMY KBdqYw9HHD6CwO5lzrexU2LMELilERATAotEeu20bUoda57VKr5OFFnXnuOwwigiecXW 7mm3Qq2CKSgEGt6VvmVCj/chOHRzX5wMBfwyyhJaNl6HDuR9CzZ4MWoH5LmvFQoBjVss Pknw== Received: by 10.66.83.9 with SMTP id m9mr71646274pay.22.1351366063155; Sat, 27 Oct 2012 12:27:43 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id ko10sm3202820pbc.1.2012.10.27.12.27.41 (version=SSLv3 cipher=OTHER); Sat, 27 Oct 2012 12:27:42 -0700 (PDT) Message-ID: <508C3599.8020709@gmail.com> Date: Sat, 27 Oct 2012 12:27:21 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Peter Grehan Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> <508A9EBD.3080107@freebsd.org> <508ADBBA.1060201@fgznet.ch> <508B34D6.6000502@gmail.com> <508C1652.6070909@fgznet.ch> <201210271728.040348@dommail.onthenet.com.au> In-Reply-To: <201210271728.040348@dommail.onthenet.com.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 19:27:43 -0000 On 10/27/12 10:28, Peter Grehan wrote: > This sounds interesting, but (very) dumb question: is there anything worth trying that can make use of this, other than glxgears ?? I'd like to try it out but not sure what to do with it. > > later, > > Peter. > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > Try any 3d app, ioquake3 or compiz. Kwin should also benefit. Matt From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 27 21:00:37 2012 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 60C91837; Sat, 27 Oct 2012 21:00:37 +0000 (UTC) (envelope-from sendtomatt@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1EEA58FC08; Sat, 27 Oct 2012 21:00:36 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id bi1so2756334pad.13 for ; Sat, 27 Oct 2012 14:00:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=+GKGO+UJeCPrHhgDqfDcHDZjE4W6jeLDiE0zEQfPkog=; b=wBTu/EfdEOyBPxnVa04saM3Du2RwRNVD6Ze93SgBHSQuDELbv688YgaIy7fBybjv2H QdFpkUGuUguMVRD5MpHrduyMr1Ay6vQfGnXJ5uzWIWCSttzdO9vBXshKe8rysPHzi9wz i0Ouda1TZ8YOykV/L6gTDG2dQVBNENQkijRPX5AcwsoTq3Z60IZwMlMmKw8uxDyJ6pDg Ya5NOn/E9BTB2hqyiH++Xl8+1cq/Wb1vPI2+BVo8CyRwJi6C1wo2qcL/u2f+9Sn0iWDa ttulwPYw5iJZNG8j/TVaHL98qP/XTahrr2ebyCwX8ER9rNRV/dgsWxk/oqKMruPSCyG5 EBEA== Received: by 10.66.84.36 with SMTP id v4mr21413895pay.37.1351371636654; Sat, 27 Oct 2012 14:00:36 -0700 (PDT) Received: from flatline.local (70-36-223-239.dsl.dynamic.sonic.net. [70.36.223.239]) by mx.google.com with ESMTPS id j10sm2224241pax.8.2012.10.27.14.00.33 (version=SSLv3 cipher=OTHER); Sat, 27 Oct 2012 14:00:35 -0700 (PDT) Message-ID: <508C4B5E.2070804@gmail.com> Date: Sat, 27 Oct 2012 14:00:14 -0700 From: matt User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121015 Thunderbird/16.0.1 MIME-Version: 1.0 To: Peter Grehan Subject: Re: Does drm/dri currently work on PPC? (SUCCESS!) References: <5083C719.1040109@gmail.com> <20121021092136.20307802@narn.knownspace> <50846392.70007@gmail.com> <5085F595.4050609@gmail.com> <20121022215945.436873dc@narn.knownspace> <5089A6DB.9070904@brakiri.com> <5089DF27.9020803@gmail.com> <20121025213018.2bfa5068@narn.knownspace> <5089F799.9030507@gmail.com> <508A17C9.4030007@gmail.com> <508A9EBD.3080107@freebsd.org> <508ADBBA.1060201@fgznet.ch> <508B34D6.6000502@gmail.com> <508C1652.6070909@fgznet.ch> <201210271728.040348@dommail.onthenet.com.au> In-Reply-To: <201210271728.040348@dommail.onthenet.com.au> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Oct 2012 21:00:37 -0000 On 10/27/12 10:28, Peter Grehan wrote: > This sounds interesting, but (very) dumb question: is there anything worth trying that can make use of this, other than glxgears ?? I'd like to try it out but not sure what to do with it. > > later, > > Peter. > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > games/ioquake3 is a good test probably. More and more software uses OpenGL, and without DRM it gets emulated slowly in software. Having it should speed up any 3d app, as well as many desktop environments that now expect 3d acceleration (kde, gnome, compiz). Essentially we're talking about modern games and eyecandy. There might be a boost to multimedia apps that use OpenGL to draw video, I think VLC can do this. Matt