https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #13 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #11)
Hi Xavier,
> I've reduced the needed changes to both 3d5.6b bit 7 and 3d5.6c bit 0.
> Initial registers setting is 3d5.6b = 0x84 and 3d5.6c = 0x01.
> Working re
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #14 from Kevin Brace ---
Created attachment 124393
--> https://bugs.freedesktop.org/attachment.cgi?id=124393&action=edit
EPIA-M (CLE266) Ubuntu 10.04 LTS register dump
The version of OpenChrome is unknown, but it is definitely afte
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #15 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #11)
Hi Xavier,
> I've reduced the needed changes to both 3d5.6b bit 7 and 3d5.6c bit 0.
> Initial registers setting is 3d5.6b = 0x84 and 3d5.6c = 0x01.
> Working re
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #16 from Kevin Brace ---
Just to clarify the TV out, it appears that my EPIA-M TV out is working fine
from a hardware perspective.
In other words, the TV out hardware is not defective.
When I turn the hardware on, TV out displays the
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #17 from Kevin Brace ---
Hi Xavier,
I did recently create a function that initializes IGA1 registers to a certain
state.
It is called viaIGA1Init.
Should I include initialization of 3X5.6B related to IGA1? (i.e., 3X5.6B[7:6]
only and
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #18 from Xavier Bachelot ---
This might indeed be related to TV out. If I disable the call to via_tv_init in
via_outputs.c (with 0.4.169), I get a working display without manually setting
crtc registers 6b and 6c.
In this case, 3d5.6b
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #19 from Xavier Bachelot ---
The bios was set to CRT+TV. Setting to CRT only gave me a working VGA display
with unmodified 0.4.169, so the driver depends on BIOS. I guess the fix would
be to initialize 3x5.6b and 3x5.6c to 0x00 in via
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #20 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #18)
Hi Xavier,
> This might indeed be related to TV out. If I disable the call to via_tv_init
> in via_outputs.c (with 0.4.169), I get a working display without man
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #21 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #19)
Hi Xavier,
> The bios was set to CRT+TV. Setting to CRT only gave me a working VGA
> display with unmodified 0.4.169, so the driver depends on BIOS. I guess the
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #22 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #19)
Hi Xavier,
> The bios was set to CRT+TV. Setting to CRT only gave me a working VGA
> display with unmodified 0.4.169, so the driver depends on BIOS. I guess the
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #23 from Kevin Brace ---
Created attachment 124397
--> https://bugs.freedesktop.org/attachment.cgi?id=124397&action=edit
[PATCH] Initializing CR6A, CR6B, and CR6C when mode setting is done
Not all the register fields of CR6A (3X5.6
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #24 from Kevin Brace ---
Hi Xavier,
I created a patch that can be committed soon.
You can test it, and I hope it works.
I have confirmed that this patch works with a VN896 chipset laptop (FP + VGA).
Please note that I upped the OpenC
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #25 from Kevin Brace ---
Hi Xavier,
I did alter the 3X5.6A value being initialized since messing this register up
leads to a hardware hang.
This is due to the fact that 3X5.6A contains a bit that resets IGA2.
--
You are receiving t
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #26 from Xavier Bachelot ---
So with the patch applied and the bios set to CRT only, it works.
With CRT + TV, 3x5.6b is properly set to 0x04, but 3x5.6c is still set to 0x01
rather than 0x00 and thus no display. Forcing 6c to 0x00 giv
https://bugs.freedesktop.org/show_bug.cgi?id=95499
Kevin Haddock changed:
What|Removed |Added
CC||kevinba...@gmail.com
--- Comment #5 from
https://bugs.freedesktop.org/show_bug.cgi?id=95499
--- Comment #6 from Kevin Haddock ---
Created attachment 124404
--> https://bugs.freedesktop.org/attachment.cgi?id=124404&action=edit
log file for X launch with xorg.conf
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #27 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #26)
Hi Xavier,
> So with the patch applied and the bios set to CRT only, it works.
> With CRT + TV, 3x5.6b is properly set to 0x04, but 3x5.6c is still set to
> 0x0
https://bugs.freedesktop.org/show_bug.cgi?id=96397
Kevin Brace changed:
What|Removed |Added
Attachment #124397|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=95499
--- Comment #7 from Kevin Brace ---
Hi Kevin,
I am kinda lost as to what is going on with your situation.
I know you uploaded xorg.conf and Xorg.0.log, but I personally do not see a
problem from the log file.
It appears that EXA module is loadin
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #29 from Xavier Bachelot ---
Latest patch works fine with bios set to CRT + TV. Tested both with and w/o tv
out (s-video) connected.
Thanks for the fix, this was a tricky one.
--
You are receiving this mail because:
You are the ass
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #30 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #29)
Hi Xavier,
> Latest patch works fine with bios set to CRT + TV. Tested both with and w/o
> tv out (s-video) connected.
>
> Thanks for the fix, this was a trick
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #3 from Xavier Bachelot ---
I still got both the FB mapping error and a segfault with latest git (0.4.176)
and kernel 4.5.6. while everything works with kernel 4.4.9. Fully updated
Fedora 23 with VIA Epia-M (CLE266).
[ 118.791] (II
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #4 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #3)
Hi Xavier,
> I still got both the FB mapping error and a segfault with latest git
> (0.4.176) and kernel 4.5.6. while everything works with kernel 4.4.9. Fully
>
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #5 from Xavier Bachelot ---
> I have not fundamentally changed the code from the older version to the
> newer one.
> As I may have said in another reply for this subject, is this Linux kernel
> or libpciaccess problem?
fwiw, just sw
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #6 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #5)
Hi Xavier,
>
>
> fwiw, just switching from linux 4.4 to linux 4.5 triggers the failure.
> libpciaccess has not been changed, nor openchrome.
>
> This might as
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #7 from Kevin Brace ---
Hi Xavier,
Please try the latest OpenChrome Version 0.4.178.
I will like to see if the crash pattern (i.e., segmentation fault) change.
The code prior to 0.4.178 was calling VIAFreeRec function twice, and that
https://bugs.freedesktop.org/show_bug.cgi?id=96397
--- Comment #31 from Kevin Brace ---
Fixed by commit 97b17c6.
https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=97b17c6823bdf2b0fe07574da2dea464d1ea3730
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freedesktop.org/show_bug.cgi?id=96397
Kevin Brace changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #8 from Kevin Brace ---
Hi Xavier,
Calling VIAFreeRec function was leading to a segmentation fault.
This is not good.
The bug itself it a separate issue.
Error handling code is very hard to reproduce, so I will like to fix that one
b
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #9 from Xavier Bachelot ---
Hi Kevin,
I agree, testing error path is hard. I guess the FB mapping error path was
never exercised, so the segfault was not seen before the other bug with
kernel/libpciaccess/openchrome was triggered.
A
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #10 from Kevin Brace ---
Created attachment 124478
--> https://bugs.freedesktop.org/attachment.cgi?id=124478&action=edit
Proposed fix mapping FB first
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #11 from Kevin Brace ---
Hi Xavier,
I will try to come up with a fix to fix that segmentation fault you are seeing,
but in the meantime, I uploaded a proposed fix (it does not cause problems
either way in my environment).
Now FB is b
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #34 from Kevin Brace ---
Hi Eric and Zong,
Can you guys try out OpenChrome Version 0.4.179?
https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=b57d2f95275f6ef0db098773a48b1cfbb442acac
https://cgit.freedesktop.
https://bugs.freedesktop.org/show_bug.cgi?id=95524
Kevin Brace changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #12 from Tolsti ---
I have tried this, but the driver still crashes. I have also attached a new
logfile.
(In reply to Kevin Brace from comment #10)
> Created attachment 124478 [details] [review]
> Proposed fix mapping FB first
--
Y
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #13 from Tolsti ---
Created attachment 124484
--> https://bugs.freedesktop.org/attachment.cgi?id=124484&action=edit
logfile for patch 124478
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #14 from Xavier Bachelot ---
Latest git + patch, same log here :
[ 1484.833] (--) CHROME(0): Probed amount of VideoRAM = 65536 kB
[ 1484.833] (II) CHROME(0): Entered viaMapFB.
[ 1484.833] (--) CHROME(0): Mapping a frame buffer at
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #15 from Xavier Bachelot ---
latest git + patch, but on kernel 4.4 :
[75.795] (--) CHROME(0): Probed amount of VideoRAM = 65536 kB
[75.795] (II) CHROME(0): Entered viaMapFB.
[75.795] (--) CHROME(0): Mapping a frame buffer
https://bugs.freedesktop.org/show_bug.cgi?id=96500
Bug ID: 96500
Summary: Can't use 1920x1080 on VGA with versions newer than
0.4.176
Product: xorg
Version: git
Hardware: x86 (IA32)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=96500
--- Comment #1 from Max Rus ---
Created attachment 124490
--> https://bugs.freedesktop.org/attachment.cgi?id=124490&action=edit
Xorg.0.log for 0.4.171 driver (without problem)
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #16 from Kevin Brace ---
I think this bug will likely be a blocker for OpenChrome Version 0.5.
If this bug is fixed, OpenChrome Version 0.4.x will be turned into Version
0.4.901 shortly.
Version 0.4.901 will be RC2 (Release Candidate
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #17 from Kevin Brace ---
Actually, is it possible to try out a smaller frame buffer option?
Usually, this can be adjusted in the BIOS setup.
I will like to try that first.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=96500
--- Comment #2 from Kevin Brace ---
Hi Max,
I apologize for the screw up.
Also, thanks for catching my obvious mistake.
I do not own a monitor capable of 1920 X 1080, and this appears to be causing
problems with other people.
The maximum I have
https://bugs.freedesktop.org/show_bug.cgi?id=96500
--- Comment #3 from Kevin Brace ---
Created attachment 124492
--> https://bugs.freedesktop.org/attachment.cgi?id=124492&action=edit
Proposed IGA1 CrtcHTotal limit test mistake fix
There was a bad commit with commit c768c86, and this broke the
https://bugs.freedesktop.org/show_bug.cgi?id=95420
Kevin Brace changed:
What|Removed |Added
Attachment #124478|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #36 from caozong ---
Created attachment 124496
--> https://bugs.freedesktop.org/attachment.cgi?id=124496&action=edit
Xorg.0.log on 0.4.179 on KMS
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #35 from caozong ---
Hi Kevin,
I've tried the OpenChrome Version 0.4.179 on KMS and UMS(I renamed drm.ko
drm_kms_help.ko and via.ko). Cursor shows up on UMS!! And it works well. But it
remain the same on KMS.
Setup: Wyse V90LE ht
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #37 from caozong ---
Created attachment 124497
--> https://bugs.freedesktop.org/attachment.cgi?id=124497&action=edit
Xorg.0.log on 0.4.179 on UMS
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=96500
--- Comment #4 from Max Rus ---
Hi Kevin,
I applyed provided patch (and fixed missing last parenthesis):
+if (mode->CrtcHTotal > (4096 + ((1 << 3) * (5 - 1)))
and now system starts normally with patched 0.4.179:
[14.664] (II) Loading
https://bugs.freedesktop.org/show_bug.cgi?id=96500
--- Comment #5 from Kevin Brace ---
(In reply to Max Rus from comment #4)
Hi Max,
> Hi Kevin,
>
> I applyed provided patch (and fixed missing last parenthesis):
>
> +if (mode->CrtcHTotal > (4096 + ((1 << 3) * (5 - 1)))
>
> and now system
https://bugs.freedesktop.org/show_bug.cgi?id=96500
--- Comment #6 from Max Rus ---
No real disturbance. I'm glad to see this project is alive, and glad that I was
usefull enough to test and help to find mistake. :)
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=96500
--- Comment #7 from Kevin Brace ---
Fixed by Version 0.4.180.
https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=d234cdf68ea6a27718a948918b3075ad257e8a0f
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freedesktop.org/show_bug.cgi?id=96500
Kevin Brace changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #18 from Tolsti ---
Created attachment 124510
--> https://bugs.freedesktop.org/attachment.cgi?id=124510&action=edit
log-file for 16MB VideoRam
Hi,
I lowered the VideoRAM as much as possible, but nothing changed.
--
You are receiv
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #19 from Tolsti ---
Hello,
I also post my output from lspci -vvv for the vga controller:
01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800
Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) (prog-if 00 [V
https://bugs.freedesktop.org/show_bug.cgi?id=94259
--- Comment #38 from Kevin Brace ---
(In reply to caozong from comment #35)
Hi Zong,
> Hi Kevin,
>I've tried the OpenChrome Version 0.4.179 on KMS and UMS(I renamed drm.ko
> drm_kms_help.ko and via.ko). Cursor shows up on UMS!! And it works
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #2 from Kevin Brace ---
Created attachment 124511
--> https://bugs.freedesktop.org/attachment.cgi?id=124511&action=edit
viaProbePinStrapping switch statement warning fix
There was a compilation warning with a switch statement insid
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #3 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #0)
Hi Xavier,
> Several build warnings have appeared in the previous months. Here are the
> relevant extracts of a build log. This is a plain build of the master bra
https://bugs.freedesktop.org/show_bug.cgi?id=95059
--- Comment #16 from Kevin Brace ---
Code to support VT1632A was fixed with Version 0.4.179.
In practice, try Version 0.4.181 or later.
DVI is working with VX855 (Wyse C00X) and I was told, CN700 (Wyse V90LE).
For HP T510's Silicon Image SiI 164,
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #4 from Xavier Bachelot ---
Hi Kevin,
(In reply to Kevin Brace from comment #3)
> (In reply to Xavier Bachelot from comment #0)
>
> Hi Xavier,
>
> > Several build warnings have appeared in the previous months. Here are the
> > rele
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #20 from Kevin Brace ---
Hi Torsten,
Please try Version 0.4.186.
I did make number of improvements to the error handling of the code.
All the commits since Version 0.4.181 were made to fix the bug you have
encountered.
Error code pat
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #21 from Kevin Brace ---
Also, I may need to look at dmesg since it is a memory mapping problem.
Basically pci_device_map_range is telling the caller that the memory map was
already mapped by someone.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #22 from Tolsti ---
Created attachment 124529
--> https://bugs.freedesktop.org/attachment.cgi?id=124529&action=edit
dmesg output as you asked for
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #23 from Tolsti ---
Created attachment 124530
--> https://bugs.freedesktop.org/attachment.cgi?id=124530&action=edit
new error logfile with latest git and kernel 4.6
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #24 from Tolsti ---
Created attachment 124531
--> https://bugs.freedesktop.org/attachment.cgi?id=124531&action=edit
latest working log-file (just in case someone wants to look at it)
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #25 from Tolsti ---
Hello Kevin,
do not worry, I am a linux admin, so I do not mind helping with this problem
(and helping to get my own linux at home running again).
Your hint with the memory begin already mapped was pretty good: vi
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #26 from Kevin Brace ---
(In reply to Tolsti from comment #25)
Hi Torsten,
> Hello Kevin,
>
> do not worry, I am a linux admin, so I do not mind helping with this problem
> (and helping to get my own linux at home running again).
>
https://bugs.freedesktop.org/show_bug.cgi?id=95420
--- Comment #27 from Kevin Brace ---
Hi Torsten,
I just filed a bug report with Linux kernel developers.
https://bugzilla.kernel.org/show_bug.cgi?id=120281
You may have to help them fix the bug as well.
Just to let you know, it often take
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #5 from Kevin Brace ---
Hi Xavier,
For xf86InitFBManagerLinear issue, I feel like it is better to keep it as an
item in the "TODO list" for OpenChrome Version 0.6.
It will take some time to remedy the issue, and at this point, I will
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #6 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #4)
> Hi Kevin,
>
> (In reply to Kevin Brace from comment #3)
> > I hope the patch I uploaded fixes the compilation warning.
> > I hope it fixes the warning.
> >
> Y
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #7 from Kevin Brace ---
The switch statement warning issue was fixed by commit 91b0c7d.
https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=91b0c7d7d5632eb29f0f72f99c675bf1120c5146
--
You are receiving this mai
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #8 from Xavier Bachelot ---
Hi Kevin,
The switch statement warning was just the beginning, I uncovered a bunch of
identical typos in the viaProbePinStrapping function.
I have posted a patch to the mailing list fixing all of them, I a
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #9 from Xavier Bachelot ---
Just noticed the patch won't apply anymore as the switch statement fix was
committed already. I'll rebase the patch and apply it myself once you have
reviewed it.
--
You are receiving this mail because:
Y
https://bugs.freedesktop.org/show_bug.cgi?id=96574
Bug ID: 96574
Summary: cannot compile the driver: xf86InitFBManager undefined
Product: xorg
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: nor
https://bugs.freedesktop.org/show_bug.cgi?id=96574
--- Comment #1 from Benno Schulenberg ---
Created attachment 124585
--> https://bugs.freedesktop.org/attachment.cgi?id=124585&action=edit
the output of ./configure
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=96399
Xavier Bachelot changed:
What|Removed |Added
CC||bensb...@justemail.net
--- Comment #10
https://bugs.freedesktop.org/show_bug.cgi?id=96574
Xavier Bachelot changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #11 from Kevin Brace ---
Created attachment 124595
--> https://bugs.freedesktop.org/attachment.cgi?id=124595&action=edit
Proposed patch to fix xf86InitFBManager implicit declaration warning
Commit e73fa19 removed including xf86fbma
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #12 from Kevin Brace ---
Hi Xavier,
This commit between Version 0.3.3 and 0.4.0 caused the xf86InitFBManager
compilation warning regression.
https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=e73fa19fec23d6ec5b
https://bugs.freedesktop.org/show_bug.cgi?id=85970
Kevin Brace changed:
What|Removed |Added
CC||kevinbr...@gmx.com
--- Comment #12 from Ke
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #13 from Xavier Bachelot ---
Hi Kevin,
The patch in comment 11 fixes the 2 implicit-function-declaration warnings.
Tested on Fedora 23.
I'm currently looking at the other warnings, mostly unused-variable or
unused-but-set-variable w
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #14 from Xavier Bachelot ---
Created attachment 124608
--> https://bugs.freedesktop.org/attachment.cgi?id=124608&action=edit
Fix for 19 unused-variable warnings
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #15 from Xavier Bachelot ---
Created attachment 124609
--> https://bugs.freedesktop.org/attachment.cgi?id=124609&action=edit
Fix unused-variable and unused-but-set-variable warnings in via_display.c
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #16 from Xavier Bachelot ---
Created attachment 124611
--> https://bugs.freedesktop.org/attachment.cgi?id=124611&action=edit
Fix unused-but-set-variable warning in via_driver.c
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #17 from Xavier Bachelot ---
Created attachment 124612
--> https://bugs.freedesktop.org/attachment.cgi?id=124612&action=edit
Fix 3 unused-variable warnings in via_lvds.c
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #18 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #13)
Hi Xavier,
> Hi Kevin,
>
> The patch in comment 11 fixes the 2 implicit-function-declaration warnings.
> Tested on Fedora 23.
>
> I'm currently looking at the
https://bugs.freedesktop.org/show_bug.cgi?id=96399
Xavier Bachelot changed:
What|Removed |Added
Attachment #124608|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #20 from Xavier Bachelot ---
(In reply to Kevin Brace from comment #18)
> Regarding the other compilation warnings, I am not too inclined to fix
> them for the next release (Version 0.5).
> Unused variable warning is not a particu
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #21 from Kevin Brace ---
The xf86InitFBManager implicit declaration warning issue was fixed by commit
ae62ee7.
https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/commit/?id=ae62ee78bf6aa7b8f3ba642fc8d5ff55947b5741
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #22 from Kevin Brace ---
(In reply to Xavier Bachelot from comment #20)
Hi Xavier,
> Agreed, unused variables are not really a problem, but there are so many
> builds warning at the moment that the build logs gets barely readable an
https://bugs.freedesktop.org/show_bug.cgi?id=96399
--- Comment #23 from Kevin Brace ---
Hi Xavier,
One more thing.
You probably should have not added even more compilation warnings to this bug
report since both of the original complaints have been resolved.
You probably should have started a new
https://bugs.freedesktop.org/show_bug.cgi?id=96610
Bug ID: 96610
Summary: Enable treating warnings as errors
Product: xorg
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priori
https://bugs.freedesktop.org/show_bug.cgi?id=96352
--- Comment #4 from Eric ---
Ok so running 0.4.901 when you boot nothing is displayed, The machine seems to
be completely locked at this point. Power button does nothing, Ctrl-Alt-F1 does
nothing.
There was a zero byte Xorg.0.log file
Next I tr
https://bugs.freedesktop.org/show_bug.cgi?id=96352
--- Comment #5 from Eric ---
Created attachment 124655
--> https://bugs.freedesktop.org/attachment.cgi?id=124655&action=edit
0.4.901 corrupted login
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=96352
--- Comment #6 from Eric ---
Created attachment 124656
--> https://bugs.freedesktop.org/attachment.cgi?id=124656&action=edit
Garbage leftover from login dialog
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=96352
--- Comment #7 from Eric ---
Created attachment 124657
--> https://bugs.freedesktop.org/attachment.cgi?id=124657&action=edit
0.4.901 Xorg.0.log from Xn0l with DVI and VGA hooked up
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=96352
--- Comment #8 from Eric ---
Created attachment 124658
--> https://bugs.freedesktop.org/attachment.cgi?id=124658&action=edit
0.4.901 Xorg.0.log from Xn0l boot after disconnecting VGA/DVI cables.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=96632
Bug ID: 96632
Summary: Skewed picture on 720x400 VGA resolution
Product: xorg
Version: git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: mino
https://bugs.freedesktop.org/show_bug.cgi?id=96632
--- Comment #1 from Eric ---
Created attachment 124660
--> https://bugs.freedesktop.org/attachment.cgi?id=124660&action=edit
Xorg.0.log after using ARandR to change to 720x400 on VGA
--
You are receiving this mail because:
You are the assigne
https://bugs.freedesktop.org/show_bug.cgi?id=96633
Bug ID: 96633
Summary: Odd Resolutions on DVI output
Product: xorg
Version: git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: minor
1101 - 1200 of 1764 matches
Mail list logo
