[Openchrome-devel] [Bug 95420] Driver 0.4.0 crashes with recent linux kernel version
https://bugs.freedesktop.org/show_bug.cgi?id=95420 Kevin Brace changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 96785] CN700 + VT1632 doesn't detect screen on DVI port
https://bugs.freedesktop.org/show_bug.cgi?id=96785 --- Comment #11 from Kevin Brace --- If I were to add one more thing, OpenChrome DRM appears to have better GPIO based I2C bus control code than OpenChrome DDX. Yesterday, I was able to get OpenChrome DRM to properly readout EDID from a fairly high screen resolution Samsung monitor (it supports 1680x1050). Although the code has not been committed, I did write code for OpenChrome DRM to support VT1632(A). However, the code suffers from strange color issues, so it has not been committed at this point. -- You are receiving this mail because: You are on the CC list for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 96785] CN700 + VT1632 doesn't detect screen on DVI port
https://bugs.freedesktop.org/show_bug.cgi?id=96785 --- Comment #10 from Kevin Brace --- Xavier, I made some improvements in supporting DVI of MSI Fuzzy CN700G mainboard. The reason the code never worked well is because, 1) VT1632A DVI transmitter's I2C bus is connected to GPIO pins 2) GPIO based I2C bus appears to suffer from communication issues 3) There are issues with older X Server's I2C bus handling Try the latest version code (Version 0.6.175) which improves the issues, although there are still some issues with standby resume. -- You are receiving this mail because: You are on the CC list for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 94797] K8M800/K8N800 (unsure which): OpenChrome crashes if viafb is not enabled
https://bugs.freedesktop.org/show_bug.cgi?id=94797 Kevin Brace changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #10 from Kevin Brace --- Feel free to reopen the bug if you get the hardware working again. You will like to clean memory module contacts and / or try a different AC adapter (i.e., third party AC adapter with interchangeable power jacks). Just for the record, OpenChrome DDX runs on K8M800 chipset, but the configuration I tested has only VGA (i.e., no flat panel). -- You are receiving this mail because: You are the assignee for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 91183] Instability of OpenChrome x.org device driver with Lubuntu 12.04 i386
https://bugs.freedesktop.org/show_bug.cgi?id=91183 Kevin Brace changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Kevin Brace --- Closing this bug report since the code has changed dramatically in the past 3 years. -- You are receiving this mail because: You are the assignee for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 106298] Everex NC 1502NC P4M900
https://bugs.freedesktop.org/show_bug.cgi?id=106298 --- Comment #12 from Kevin Brace --- Scott, a lot of my time got taken for various time consuming tasks this week (the week of May 6th, 2018). For example, I had to replace my main development computer's (HP 2133 mini-note) SSD which just died after one year of use. In practice, some other bad things happened as well (non-OpenChrome related), but they are personal, so I will not discuss them here. I will have limited time to work on OpenChrome for the week of May 13th, 2018, but I will still like to make some progress. Let me know what you will like to do with the issues you have raised within this bug report. -- You are receiving this mail because: You are on the CC list for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 100679] Garbled graphics when resuming from standby
https://bugs.freedesktop.org/show_bug.cgi?id=100679 --- Comment #51 from Kevin Brace --- Marty, can I close this bug report? The upcoming OpenChrome DDX Version 0.7 will officially contain the fixes. -- You are receiving this mail because: You are on the CC list for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 106392] blank screen on OpenChrome with VIA VE900
https://bugs.freedesktop.org/show_bug.cgi?id=106392 --- Comment #30 from Kevin Brace --- P Touchman, I did not write most of OpenChrome DDX or DRM code. All I have focused on are display automatic detection and improving standby resume behavior for both DDX and DRM. Although it might seem less than perfect, I am particularly focused on improving the usability and reliability of OpenChrome. That being said, the latest version you used was a developmental version (i.e., Version 0.6.174), so it might contain issues. Typically, I do try to focus on fixes prior to the formal release version (i.e., Version 0.6) so that it is as stable as possible. Despite my best efforts, unfortunately things do break like OpenChrome DDX Version 0.5 breaking HP 2133 mini-note's WLAN (Version 0.6 fixed this bug.). If I were to comment on graphics device driver development, it is pretty hard to attract developers to do this for non-Big 3 x86 platform graphics devices (Intel, AMD, and NVIDIA). Nowadays, I think almost all Linux graphics device driver developers are employed (paid) developers. This is why very little development activities happen outside of Big 3 x86 platform graphics devices. Besides that, it is really difficult to get people to develop code for graphics devices older than 5 years (This is my observation.), in general. I was not too surprised that I got to present at XDC2017, although I was pretty much the only unpaid developer at the conference (some of the Nouveau developers work for RedHat). (In reply to ptouchman from comment #27) > > After reading your presentation I can see that it's a pretty monumental task > to write video drivers. (A very interesting read, BTW) > > https://www.x.org/wiki/Events/XDC2017/brace_openchrome.pdf -- You are receiving this mail because: You are on the CC list for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 106392] blank screen on OpenChrome with VIA VE900
https://bugs.freedesktop.org/show_bug.cgi?id=106392 --- Comment #29 from Kevin Brace --- P Touchman, thus far, I have not touched any of the rendering related code other than remove compilation warnings (mainly of "unused variables" type warnings). In general, the rendering performance of OpenChrome DDX has been going downward since X Server 1.11 (Lubuntu 12.04) even with the same exact OpenChrome DDX code. I know this because I do test the same code by compiling against X Server 1.11 and 1.19, and 1.19 is clearly slower. It is possible this is Linux kernel related since I didn't use identical kernel. I do not plan to work on rendering related code until OpenChrome DRM is mainlined (accepted) into the Linux kernel tree. (In reply to ptouchman from comment #22) > Thanks for your suggestion to try another OS, I booted Knoppix 8.1 live DVD > installed to a flash drive and it worked!!! I couldn't believe it. > Especially as it's supposed to be based on Debian 9.3. So go figure. > > > I also looked very hard for an xorg.conf file in Debian 9.3 and there wasn't > any in /etc/X11 or in /usr/share/X11/. > > > Since the knoppix 8.1 was working I thought I'd see what the performance of > mame was and I only got 30fps on pacman (full speed would be 60fps). -- You are receiving this mail because: You are on the CC list for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 106392] blank screen on OpenChrome with VIA VE900
https://bugs.freedesktop.org/show_bug.cgi?id=106392 --- Comment #28 from Kevin Brace --- P Touchman, a lot of my time got taken for various time consuming tasks this week (the week of May 6th, 2018). For example, I had to replace my main development computer's (HP 2133 mini-note) SSD which just died after one year of use. In practice, some other bad things happened as well (non-OpenChrome related), but they are personal, so I will not discuss them here. I will have limited time to work on OpenChrome for the week of May 13th, 2018, but I will still like to make some progress. If you can, you may want to test the latest OpenChrome DDX with Knoppix. If it is a lot more unstable, it might be because of the new connector detection code not working well sometimes. To test against this, you will like to boot the computer several times to see if the VGA input correctly displays something. If you think the non-detection of the display is sporadic, then I can create a patch disabling this feature. Just for disclosure, I am aware of this connector detection code not working very well with some chipsets. I am considering removing them for the upcoming OpenChrome DDX Version 0.7 if I cannot ensure that it works well with all the chipsets. (In reply to ptouchman from comment #27) > > I'm glad that I got it to finally work! Maybe I'll have mame frameskip a > little, I suppose it doesn't have to render every frame. 30 fps is actually > playable. > > > After reading your presentation I can see that it's a pretty monumental task > to write video drivers. (A very interesting read, BTW) > > https://www.x.org/wiki/Events/XDC2017/brace_openchrome.pdf -- You are receiving this mail because: You are on the CC list for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
[Openchrome-devel] [Bug 106326] openchrome git failed on xubuntu 18.04
https://bugs.freedesktop.org/show_bug.cgi?id=106326 --- Comment #31 from Kevin Brace --- sebastien, a lot of my time got taken for various time consuming tasks this week (the week of May 6th, 2018). For example,I had to replace my main development computer's (HP 2133 mini-note) SSD which just died after one year of use. I will have limited time to work on OpenChrome for the week of May 13th, 2018, but I will still try to make some progress. I upgraded the OpenChrome DDX version to 0.6.175. It contains the initial fix for Samsung NC20 netbook, so you do not need the patch anymore if you pull, compile, and install the latest Since I do not have the actual hardware in front of me, I will need to rely on you to fix issues. Let's start with turming FP or VGA via Display settings of Xubuntu. Can you turn FP on / off reliability via Display settings? Please attach these register dumps. - Before turning off the FP - After turning off the FP - After turning on the FP You will likely need to have VGA running all the time. I will also need to have the associated Xorg.0.log. (In reply to sebastien from comment #30) > yeah its ok for comment 22 -- You are receiving this mail because: You are on the CC list for the bug.___ Openchrome-devel mailing list Openchrome-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
