Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

On Mon, 2018-09-24 at 19:46 -0500, Chris Pollock wrote: > On Thu, 2018-09-06 at 10:10 -0500, Chris wrote: > > On Thu, 2018-09-06 at 16:00 +0200, Michel Dänzer wrote: > > > On 2018-09-06 1:53 p.m., Chris wrote: > > > > On Thu, 2018-09-06 at 12:21 +0200, Michel Dänzer wrote: > > > > > On 2018-09-05

[PATCH v2] Fix checking for valid argument of --dpi

Function strtod() sets strtod_error to the pointer of the first invalid character and therefore it does not have to be first character from input. When input is valid then it points to nul byte. Conversion error is indicated by setted errno. Zero-length argument, non-positive DPI or DPI with

[PATCH xf86-video-mga] Write 8 bits instead of 32 to MGAREG_CACHEFLUSH

From: Henry Zhao Fixes misaligned address crash when EXA is enabled on Solaris SPARC (Oracle Bug id 22993744) Signed-off-by: Alan Coopersmith --- src/mga_exa.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/mga_exa.c b/src/mga_exa.c index 86ec09e..03c5229 100644 ---

Re: [PATCH xf86-video-mga] Use fabs() to compute absolute value of floating point number.

On 11/26/18 12:12 PM, Matthieu Herrb wrote: Fixes a warning from clang and looks like it was a real bug. Signed-off-by: Matthieu Herrb --- src/mga_dacG.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/mga_dacG.c b/src/mga_dacG.c index 3b0d93e..5c08f8a 100644 ---

Re: Will like to release xf86-video-mga Version 1.7 soon

On Mon, Nov 26, 2018 at 08:30:52PM +0100, Kevin Brace wrote: > Hi, > > I am not personally invested in maintaining xf86-video-mga DDX code at this > point, but the other day, I built an AMD Athlon 64 based computer with Matrox > G400 MAX AGP graphics card, and noticed that the last few commit

Re: Will like to release xf86-video-mga Version 1.7 soon

On 11/26/18 11:30 AM, Kevin Brace wrote: Anyway, I decided to fix a few annoying compilation warnings, and I just posted the patches to this mailing list. As long as you're cleaning up, should README_HALLIB and the corresponding entries in src/binding.h be deleted now? Seemes like they were

[PATCH xf86-video-mga] Use fabs() to compute absolute value of floating point number.

Fixes a warning from clang and looks like it was a real bug. Signed-off-by: Matthieu Herrb --- src/mga_dacG.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/mga_dacG.c b/src/mga_dacG.c index 3b0d93e..5c08f8a 100644 --- a/src/mga_dacG.c +++ b/src/mga_dacG.c @@ -986,8

Will like to release xf86-video-mga Version 1.7 soon

Hi, I am not personally invested in maintaining xf86-video-mga DDX code at this point, but the other day, I built an AMD Athlon 64 based computer with Matrox G400 MAX AGP graphics card, and noticed that the last few commit ago commit broke the screen. Fortunately, the person who committed the

[PATCH xf86-video-mga 3/4] Convert most HAVE_XAA_H conditional compilation labels to USE_XAA

Signed-off-by: Kevin Brace --- src/mga.h| 2 +- src/mga_dga.c| 8 src/mga_driver.c | 4 ++-- src/mga_storm.c | 28 ++-- src/mga_video.c | 4 ++-- 5 files changed, 23 insertions(+), 23 deletions(-) diff --git a/src/mga.h b/src/mga.h index

[PATCH xf86-video-mga 4/4] Suppression of a compilation error when XAA is not in use

Signed-off-by: Kevin Brace --- src/mga.h | 3 ++- src/mga_arc.c | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/src/mga.h b/src/mga.h index f47b0af..1a7cb47 100644 --- a/src/mga.h +++ b/src/mga.h @@ -737,8 +737,9 @@ Bool mgaExaInit(ScreenPtr pScreen); Bool

[PATCH xf86-video-mga 2/4] Eliminate set but unused variables

Signed-off-by: Kevin Brace --- src/mga_dacG.c | 21 - src/mga_driver.c | 10 -- src/mga_video.c | 18 -- 3 files changed, 12 insertions(+), 37 deletions(-) diff --git a/src/mga_dacG.c b/src/mga_dacG.c index b86ad39..d5a7689 100644 ---

[PATCH xf86-video-mga 1/4] Eliminate unused variables

Care had to be taken to properly handle XAA usage situation Signed-off-by: Kevin Brace --- src/mga_bios.c | 1 - src/mga_dacG.c | 6 +- src/mga_dri.c| 5 +++-- src/mga_driver.c | 3 +-- src/mga_storm.c | 11 ++- src/mga_video.c | 11 ++- 6 files changed, 25

Re: what does "+"(preferred) means in xrandr?

"preferred" generally means that the Extended Display Information Data (EDID) from the monitor indicates that that mode most closely matches the native timings of the display. All modes listed by RandR for a given monitor should work with that monitor, but the preferred mode should work best (for

Re: what does "+"(preferred) means in xrandr?

"preferred" generally means that the Extended Display Information Data (EDID) from the monitor indicates that that mode most closely matches the native timings of the display. All modes listed by RandR for a given monitor should work with that monitor, but the preferred mode should work best (for

what does "+"(preferred) means in xrandr?

hello everyone！ What the “preferred" means in xrandr? Is it setted by display hardware? Can we set it manual? If we call “XOpenDisplay” to open default screen and then poll the returned x11_fd, will we interrupted for “preferred" changed? Is there others docs about it? Looking forward to