From owner-freebsd-x11@FreeBSD.ORG Fri Oct 26 01:30:22 2012 Return-Path: Delivered-To: freebsd-x11@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, freebsd-ppc@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: 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