<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><base href="https://bugs.freedesktop.org/"><style></style></head><body lang=ZH-CN link=blue vlink=purple><div class=WordSection1>Hi Kevin,<o:p></o:p><o:p> </o:p> Recent two days, I am looking into the UMS xf86-video-openchrome code and also be shocked by ViaCardID[] struct in Via_id.c file. Why does the UMS driver use this table to identify the board? I am also buying some old boards including VX700/VX855/VX900 and I found some boards(i.e., Wyse Thin Clients) are not in this list. So I can guess same error will be reported.<o:p></o:p> So It seems this ViaCardID table will only bring faults instead of any good things. Why not remove it?<o:p></o:p><o:p> </o:p>Thanks,<o:p></o:p>Frank<o:p></o:p> <o:p></o:p><o:p> </o:p><o:p> </o:p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>发件人: Openchrome-devel [mailto:openchrome-devel-bounces@lists.freedesktop.org] 代表 bugzilla-daemon@freedesktop.org 发送时间: 2016年2月24日 12:15 收件人: openchrome-devel@lists.freedesktop.org 主题: [Openchrome-devel] [Bug 94210] Unknown Card-Ids (7122|1458|D000), Chipset: VX900<o:p></o:p></div></div><o:p> </o:p><div><a href="https://bugs.freedesktop.org/show_bug.cgi?id=94210#c6" title="NEW - Unknown Card-Ids (7122|1458|D000), Chipset: VX900">Comment # 6</a> on <a href="https://bugs.freedesktop.org/show_bug.cgi?id=94210" title="NEW - Unknown Card-Ids (7122|1458|D000), Chipset: VX900">bug 94210</a> from <a href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>">Kevin Brace</a> <o:p></o:p><pre>(In reply to Dariusz Gadomski from <a href="show_bug.cgi?id=94210#c5">comment #5</a>)<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Hi Dariusz,<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>> Kevin, I will appreciate taking a look at the updated Xorg.log - the<o:p></o:p></pre><pre>> segfault is gone, but the driver still does not recognize the card.<o:p></o:p></pre><pre>> <o:p></o:p></pre><pre>> Regarding your expectations towards 0.3.4 version adoption in Ubuntu:<o:p></o:p></pre><pre>> unfortunately the Stable Release Updates policy<o:p></o:p></pre><pre>> (<a href="https://wiki.ubuntu.com/StableReleaseUpdates">https://wiki.ubuntu.com/StableReleaseUpdates</a>) prevents upgrading packages<o:p></o:p></pre><pre>> during the lifetime of the stable releases. The only available option seems<o:p></o:p></pre><pre>> to be backporting individual changes (in response to reported bugs) to the<o:p></o:p></pre><pre>> version already available in a particular release.<o:p></o:p></pre><pre>> <o:p></o:p></pre><pre>> Sadly, we also missed the opportunity to release it with 16.04 - as it has<o:p></o:p></pre><pre>> entered the feature freeze state.<o:p></o:p></pre><pre>> <o:p></o:p></pre><pre>> I will check if there are any other options.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Thank you very much for getting back with me.<o:p></o:p></pre><pre>Please ignore the unknown device message you see in Xorg.0.log.<o:p></o:p></pre><pre>This occurs due to the use of a weird known device table inside OpenChrome.<o:p></o:p></pre><pre>I am not a fan of the use of something like this, <o:p></o:p></pre><pre>The code is gradually moving towards all automatic detection of display<o:p></o:p></pre><pre>devices, but this will take some time to complete.<o:p></o:p></pre><pre>I am considering getting rid of this weird known device table in OpenChrome<o:p></o:p></pre><pre>Version 0.3.5, but I will likely keep it in there for Version 0.3.4.<o:p></o:p></pre><pre>This is what the weird known device table looks like<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>_____________________________________________________________________________<o:p></o:p></pre><pre>. . .<o:p></o:p></pre><pre> /*** VX900 ***/<o:p></o:p></pre><pre> {"Simmtronics SIMM-PC VX900i", VIA_VX900, 0x1019, 0x3126,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre> {"ECS VX900-I", VIA_VX900, 0x1019, 0x7C8E,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre> {"Foxconn L740", VIA_VX900, 0x105B, 0x0CFD,<o:p></o:p></pre><pre>VIA_DEVICE_LCD | VIA_DEVICE_CRT},<o:p></o:p></pre><pre> {"HP T5550 Thin Client", VIA_VX900, 0x1106, 0x7122,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre> {"Biostar Viotech 3200+", VIA_VX900, 0x1565, 0x120A,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre> {"ASRock PV530", VIA_VX900, 0x1849, 0x7122,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre> {"Fujitsu Futro A300", VIA_VX900, 0xA0A0, 0x080F,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> /* keep this */<o:p></o:p></pre><pre> {NULL, VIA_UNKNOWN, 0x0000, 0x0000,<o:p></o:p></pre><pre>VIA_DEVICE_NONE}<o:p></o:p></pre><pre>_____________________________________________________________________________<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Looking at the link you provided, I feel like updating OpenChrome Version 0.3.3<o:p></o:p></pre><pre>is quite warranted based on the following clauses I saw in the link you<o:p></o:p></pre><pre>provided.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>___________________________________________________________________________<o:p></o:p></pre><pre>2.1. High-impact bugs<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Stable release updates will, in general, only be issued in order to fix<o:p></o:p></pre><pre>high-impact bugs. Examples of such bugs include:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>. . .<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>- Bugs which represent severe regressions from the previous release of Ubuntu.<o:p></o:p></pre><pre>This includes packages which are totally unusable, like being uninstallable or<o:p></o:p></pre><pre>crashing on startup.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>. . .<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>2.2. Other safe cases<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>In the following cases a stable release update is also applicable as they have<o:p></o:p></pre><pre>a low potential for regressing existing installations but a high potential for<o:p></o:p></pre><pre>improving the user experience, particularly for Long Term Support releases:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>- Bugs which do not fit under above categories, but (1) have an obviously safe<o:p></o:p></pre><pre>patch and (2) affect an application rather than critical infrastructure<o:p></o:p></pre><pre>packages (like X.org or the kernel).<o:p></o:p></pre><pre>- For Long Term Support releases we regularly want to enable new hardware. Such<o:p></o:p></pre><pre>changes are appropriate provided that we can ensure not to affect upgrades on<o:p></o:p></pre><pre>existing hardware. For example, modaliases of newly introduced drivers must not<o:p></o:p></pre><pre>overlap with previously shipped drivers. This also includes updating hardware<o:p></o:p></pre><pre>description data such as udev's keymaps, media-player-info, mobile broadband<o:p></o:p></pre><pre>vendors, or PCI vendor/product list updates.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>___________________________________________________________________________<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>Anyway, since the bug is a fatal one, and a severe regression from Version<o:p></o:p></pre><pre>0.2.904, is there a way the newer version can be treated as a security fix<o:p></o:p></pre><pre>update so that Canonical can replace OpenChrome Version 0.3.3?<o:p></o:p></pre><pre>Also, can OpenChrome Version 0.3.4 go into Ubuntu 16.04.1 LTS if not Ubuntu<o:p></o:p></pre><pre>16.04 LTS?<o:p></o:p></pre><pre>At this point, I will likely not release OpenChrome Version 0.3.4 since I have<o:p></o:p></pre><pre>not been able to fix the DVI related problems completely at this point,<o:p></o:p></pre><pre>although there was some progress on this front today.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><a href="show_bug.cgi?id=91966#c211" title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics">https://bugs.freedesktop.org/show_bug.cgi?id=91966#c211</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>If necessary, I can release OpenChrome Version 0.3.4 immediately, and fix DVI<o:p></o:p></pre><pre>related bugs in Version 0.3.5.<o:p></o:p></pre></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div>You are receiving this mail because: <o:p></o:p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>You are the assignee for the bug.<o:p></o:p></li></ul></div></div></body></html>