Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 3 Nov 2007 18:00:58 -0400
From:      Randy Pratt <bsd-unix@embarqmail.com>
To:        Stanislav Sedov <stas@freebsd.org>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: mga patch
Message-ID:  <20071103180058.1c1bd333.bsd-unix@embarqmail.com>
In-Reply-To: <20071103202731.GD50040@dracon.ht-systems.ru>
References:  <20071103181037.GC50040@dracon.ht-systems.ru> <20071103130827.W9534@wonkity.com> <20071103202731.GD50040@dracon.ht-systems.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 3 Nov 2007 23:27:31 +0300
Stanislav Sedov <stas@freebsd.org> wrote:

> On Sat, Nov 03, 2007 at 01:12:41PM -0600 Warren Block mentioned:
> > On Sat, 3 Nov 2007, Stanislav Sedov wrote:
> > 
> >> It's looks like that mga driver was updated to the wrong snapshot
> >> (from the incorrect branch).
> > 
> > Which version?
> 
> I have compared both the 1.9.100 and 1.4.7 versions to git HEAD,
> and 1.4.7 is much closer.
> 
> 1.9.100 doesn't work for a lot of people, take a look at
> http://www.freebsd.org/cgi/query-pr.cgi?pr=117726
> for example.
> 
> > 
> >> It caused a lot of problems for people with Matrox cards, if fact i 
> >> haven't heard about any 'success story' with it:-)
> > 
> > Not sure what you mean.  Several of us are using xf86-video-mga 1.9.100 
> > like this:
> > 
> > http://www.wonkity.com/~wblock/mgapatch/xorg-patch.txt
> 
> Can you check if it will work with the patch?
> 
> > 
> >> The patch attached reverts the port back to 1.4.7 version (which is
> >> looks like the latest version available) and also adds some patches
> >> from git for known problems.
> > 
> > No patch attached.
> > 
> 
> Ok, probably I forgot it, it's in place now.

I just did the patch (mga.diff):

	xf86-video-mga-1.4.7,1 X.Org mga display driver

Built and installed with no problems and everything seems to be
as it should be.

I do have to say that I did learn more about Xorg in trying to
use the newer driver.  I probably wouldn't have if the new driver
had just worked out of the box.

This definitely needs to get committed before the upcoming release(s).

Thanks for fixing this!

Randy


-- 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071103180058.1c1bd333.bsd-unix>