Date: Wed, 21 Dec 2005 18:42:49 -0800 From: Eric Anholt <eta@lclark.edu> To: martinko <martinkov@pobox.sk> Cc: freebsd-current@freebsd.org Subject: Re: DRM update for testing Message-ID: <1135219369.17506.3.camel@leguin> In-Reply-To: <dobvod$iqq$1@sea.gmane.org> References: <1132743283.1197.55.camel@leguin> <dobvod$iqq$1@sea.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-Ub7xGmyyctqsnNck5hsi Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2005-12-21 at 17:26 +0100, martinko wrote: > Eric Anholt wrote: > > I've got a patch at: > > http://people.freebsd.org/~anholt/dri/drm-sys-20051123.diff > > for testing, which merges DRM CVS into FreeBSD. I've done basic tests > > of a recent DRM CVS with WITNESS on AGP/PCI Matrox, AGP/PCI Rage 128, > > AGP Radeon r100/r200/r300, AGP Savage4 (new!), SiS, and 3dfx, and this > > version should be equivalent to what I tested. I'll do another pass of > > testing before I commit, but I'd also like to get some wider testing so > > more panics can show up if they exist. This particular diff has only > > been compile-tested with LINT on amd64 so far. > >=20 > > Known issues: > > - Radeon PCIGART mode hung for me. I've heard this is caused by a > > change in X.Org upstream which itself worked around a different hang, s= o > > those of you not using xorg-server-snap wouldn't hit it hopefully. > > - Savage3d untested iirc > > - Savage4 PCI doesn't work (needs some love in the memory mapping > > department, I think). > >=20 > > However, savage support has experimental and will only be on by default > > with the next release of X.Org, so I feel OK with integrating it into > > -current. > >=20 > > So, for testing: If you get instant reboots while starting/using X, tha= t > > almost always means a kernel panic. This is new behavior in the last > > year or so afaik (where a number of us have issues dumping while in X). > > However, I've hooked up serial consoles and got backtraces fine, which > > hopefully you can do if you hit issues, as well.=20 > >=20 > > Also, note that this brings in a new enough r300 driver for running Mes= a > > CVS's r300 driver, which hasn't been the case for a while. It doesn't > > bring in the via driver, which jakeb ported but which got overcome by > > new linux-specific code (volunteers to work on this in DRM CVS would be > > excellent!) in CVS. Also, the i915 (i830 through i915 integrated > > graphics) driver should be pretty quick for someone with a bit of newbu= s > > knowledge to finish off, or it could be a chance someone who cared to > > learn more about the FreeBSD kernel :) > >=20 >=20 > eric, >=20 > i've got only 64MB video memory, while : >=20 > $ dmesg | g drm > drm0: <ATI Radeon RV300 Mobility 9600 M10> port 0xc800-0xc8ff mem=20 > 0xd0000000-0xd7ffffff,0xff8f0000-0xff8fffff irq 5 at device 0.0 on pci1 > info: [drm] AGP at 0xe0000000 256MB > info: [drm] Initialized radeon 1.19.0 20050911 >=20 > note, that i'm running 6-stable and cvsuped recently just to discover=20 > that radeon driver is finally attaching. Yes, your AGP aperture is a limit on system memory usable by AGP. Totally unrelated to your video card's framebuffer size. --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-Ub7xGmyyctqsnNck5hsi Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDqhKpHUdvYGzw6vcRAtXfAKCMWYjaDl/h6mKRdWF7PaK/ctJJxgCgm2nA KV9O7bdq3QWTLGlmtYU8A3I= =2yHW -----END PGP SIGNATURE----- --=-Ub7xGmyyctqsnNck5hsi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1135219369.17506.3.camel>