Date: Thu, 14 Aug 2008 12:46:05 -0400 From: Coleman Kane <cokane@FreeBSD.org> To: Robert Noland <rnoland@FreeBSD.org> Cc: freebsd-x11 <freebsd-x11@freebsd.org> Subject: Re: [CFT] drm updates Message-ID: <1218732365.11432.6.camel@localhost> In-Reply-To: <1218731717.6077.27.camel@squirrel.corp.cox.com> References: <1218675844.1899.18.camel@wombat.2hip.net> <1218729645.11432.0.camel@localhost> <1218731717.6077.27.camel@squirrel.corp.cox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-LmViPftR9+uYokulGI0w Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2008-08-14 at 12:35 -0400, Robert Noland wrote: > On Thu, 2008-08-14 at 12:00 -0400, Coleman Kane wrote: > > On Wed, 2008-08-13 at 21:04 -0400, Robert Noland wrote: > > > I have prepared a set of patches for drm kernel modules against -CURR= ENT > > > and -STABLE. I would like to get this into HEAD fairly soon. > > >=20 > > > This update has the latest vblank rework bits in it, so if you have > > > hardware that can disable vblank irq's (radeon, intel) you should see > > > the irq counts drop if there are no vblank consumers running. > > >=20 > > > i915 suspend/resume support is included. > > >=20 > > > For Intel, this should pick up support for the g33 chipsets as well. > > >=20 > > > Lots of other fixes here and there... > > >=20 > > > The patches are located at http://people.freebsd.org/~rnoland > > >=20 > > > robert. > > >=20 > >=20 > > Robert, > >=20 > > Are these patches just snapshots of code currently in git master, or do > > they also include fixes pending commit to git master as well? >=20 > This is a snapshot of git master as of a few days ago... git master is > no longer useable after this point, at least not for intel. I hope to > eventually get gem working, (shameless plea for help) but it may take > some time. Given that we haven't had a real update to drm in a couple > of years, I wanted to get this in the tree. There are a few patches > present in this changeset beyond what was in git master. I've been tracking master, rather than using the drm stuff in sys/ lately. Since I've got an AMD RS690, I just disabled the Intel driver after the gem breakage. I should probably try your patches out instead of the git tree for a bit just to make sure that they don't break anything new. I'm still running into some GPU crashes in the current state of the drm git tree / DRI drivers from git. >=20 > As I stated earlier, the future of drm.git is in question right now, so > I'm not sure what the best way to move forward is yet. I would like to > go ahead and get in the features and fixes that we have now, rather than > stall out and wait until we have the next feature... We will wait > forever on some feature or the other. Argh for the Linuxization of the DRM code.=20 >=20 > What I'm aiming to do with this changeset, is identify any outstanding > bugs/regressions and get us a little more current than we are today. I > have a lot of work that I would like to do outside of trying to keep up > with the new features coming out, but time is limited... >=20 > robert. >=20 --=20 Coleman Kane --=-LmViPftR9+uYokulGI0w Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkikYUsACgkQcMSxQcXat5fOHwCfWFlw4UoDu56sZe9vRgSgIjR4 /ZYAn2r3NlOhCCFN6FUdWMAF56pS4+7N =wKEF -----END PGP SIGNATURE----- --=-LmViPftR9+uYokulGI0w--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1218732365.11432.6.camel>