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