Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 05 Jun 2008 14:01:56 -0400
From:      Coleman Kane <cokane@FreeBSD.org>
To:        "Marat N.Afanasyev" <amarat@ksu.ru>
Cc:        x11@FreeBSD.org
Subject:   Re: updating drm
Message-ID:  <1212688916.1904.19.camel@localhost>
In-Reply-To: <484702B1.6080402@ksu.ru>
References:  <48456950.8060507@ksu.ru> <1212511997.15220.25.camel@localhost> <484702B1.6080402@ksu.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-8rzPL3rQe3AhWcuYpPDq
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, 2008-06-05 at 01:01 +0400, Marat N.Afanasyev wrote:
> Coleman Kane =D0=BF=D0=B8=D1=88=D0=B5=D1=82:
> > On Tue, 2008-06-03 at 19:54 +0400, Marat N.Afanasyev wrote:
> >> Hello!
> >>
> >> I wonder is there any plans to update drm in either CURRENT or STABLE=20
> >> from MESA tree?
> >>
> >=20
> > I believe so, but only after the stuff in the MESA tree is stable. From
> > what I can tell, there is still work going into developing it more
> > (integrating VBLANK and other changes). There will probably be a merge
> > once the BSD part of the tree is stable again.
> >=20
> > I've also got at least one outstanding bug report open that needs eithe=
r
> > fixing in drm/bsd-core or in xf86-video-ati.
> >=20
>=20
> I think that without importing drm onto, at least, CURRENT, there will=20
> be a few chances to receive bug-reports to be worked with ;)
>=20

The bug report above is one that I've submitted, and we're currently
working on resolving it.

At least two combined changes happened at the same time to the BSD drm
code (vblank-rework as well as r5xx/r6xx support). I've been trying to
get the latter one working, but in the process I think I might have
gotten bit by the former. The drm code has almost always been
continually developed in the mesa/drm git tree at freedesktop.org, with
snapshots being merged into the FreeBSD tree as new features and changes
settle.

I am confident that when more of these outstanding issues are resolved,
the resulting code will get merged. A likely result of just merging
everything now might be a sudden breakage of DRI for numerous R1xx,
R2xx, R3xx, and R4xx users who already have good, working DRI support.
It would be better if the deluge of PR's was limited to the users of
R5xx and above cards, who right now don't have DRI support. I am also
confident that this will happen real-soon-now.

That said, anybody can see/get the current development trees by
visiting:
      * http://gitweb.freedesktop.org/?p=3Dmesa/drm.git;a=3Dsummary



--=20
Coleman Kane

--=-8rzPL3rQe3AhWcuYpPDq
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)

iEYEABECAAYFAkhIKhIACgkQcMSxQcXat5fJrgCZAXRN9wlHPYL0JETGyA7kHgz1
VfEAn1CYq6UNUmMNKTGSJzQgfK8jyK4N
=oIZ3
-----END PGP SIGNATURE-----

--=-8rzPL3rQe3AhWcuYpPDq--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1212688916.1904.19.camel>