Attachment 121948 Details for Bug 94210 – attachment-27653-0.html

attachment-27653-0.html

attachment-27653-0.html (text/html), 18.43 KB, created by HuangRan on 2016-02-24 14:22:36 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: HuangRan

Created: 2016-02-24 14:22:36 UTC

Size: 18.43 KB

patch

obsolete

><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>&nbsp;</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>&nbsp;</o:p>Thanks,<o:p></o:p>Frank<o:p></o:p>Â Â Â Â Â Â Â Â  <o:p></o:p><o:p>&nbsp;</o:p><o:p>&nbsp;</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>&nbsp;</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 &lt;kevinbrace@gmx.com&gt;">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>&nbsp;</o:p></pre><pre>Hi Dariusz,<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&gt; Kevin, I will appreciate taking a look at the updated Xorg.log - the<o:p></o:p></pre><pre>&gt; segfault is gone, but the driver still does not recognize the card.<o:p></o:p></pre><pre>&gt; <o:p></o:p></pre><pre>&gt; Regarding your expectations towards 0.3.4 version adoption in Ubuntu:<o:p></o:p></pre><pre>&gt; unfortunately the Stable Release Updates policy<o:p></o:p></pre><pre>&gt; (<a href="https://wiki.ubuntu.com/StableReleaseUpdates">https://wiki.ubuntu.com/StableReleaseUpdates</a>) prevents upgrading packages<o:p></o:p></pre><pre>&gt; during the lifetime of the stable releases. The only available option seems<o:p></o:p></pre><pre>&gt; to be backporting individual changes (in response to reported bugs) to the<o:p></o:p></pre><pre>&gt; version already available in a particular release.<o:p></o:p></pre><pre>&gt; <o:p></o:p></pre><pre>&gt; Sadly, we also missed the opportunity to release it with 16.04 - as it has<o:p></o:p></pre><pre>&gt; entered the feature freeze state.<o:p></o:p></pre><pre>&gt; <o:p></o:p></pre><pre>&gt; I will check if there are any other options.<o:p></o:p></pre><pre><o:p>&nbsp;</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>&nbsp;</o:p></pre><pre>_____________________________________________________________________________<o:p></o:p></pre><pre>. . .<o:p></o:p></pre><pre>Â Â Â  /*** VX900 ***/<o:p></o:p></pre><pre>Â Â Â  {&quot;Simmtronics SIMM-PC VX900i&quot;,Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1019, 0x3126,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre>Â Â Â  {&quot;ECS VX900-I&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1019, 0x7C8E,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre>Â Â Â  {&quot;Foxconn L740&quot;,Â Â Â Â Â Â Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â VIA_VX900,Â Â  0x105B, 0x0CFD,<o:p></o:p></pre><pre>VIA_DEVICE_LCD | VIA_DEVICE_CRT},<o:p></o:p></pre><pre>Â Â Â  {&quot;HP T5550 Thin Client&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1106, 0x7122,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre>Â Â Â  {&quot;Biostar Viotech 3200+&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1565, 0x120A,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre>Â Â Â  {&quot;ASRock PV530&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1849, 0x7122,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre>Â Â Â  {&quot;Fujitsu Futro A300&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0xA0A0, 0x080F,<o:p></o:p></pre><pre>VIA_DEVICE_CRT},<o:p></o:p></pre><pre><o:p>&nbsp;</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>&nbsp;</o:p></pre><pre><o:p>&nbsp;</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>&nbsp;</o:p></pre><pre>___________________________________________________________________________<o:p></o:p></pre><pre>2.1. High-impact bugs<o:p></o:p></pre><pre><o:p>&nbsp;</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>&nbsp;</o:p></pre><pre>. . .<o:p></o:p></pre><pre><o:p>&nbsp;</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>&nbsp;</o:p></pre><pre>. . .<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>2.2. Other safe cases<o:p></o:p></pre><pre><o:p>&nbsp;</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>&nbsp;</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>&nbsp;</o:p></pre><pre>___________________________________________________________________________<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</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>&nbsp;</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>&nbsp;</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>

<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/"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:å®ä½;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:å®ä½;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@å®ä½";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:å®ä½;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:å®ä½;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML é¢è®¾æ ¼å¼ Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:å®ä½;}
span.vcard
	{mso-style-name:vcard;}
span.fn
	{mso-style-name:fn;}
span.HTMLChar
	{mso-style-name:"HTML é¢è®¾æ ¼å¼ Char";
	mso-style-priority:99;
	mso-style-link:"HTML é¢è®¾æ ¼å¼";
	font-family:"Courier New";}
span.quote
	{mso-style-name:quote;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:694890676;
	mso-list-template-ids:1187257100;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:ï·;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:ï§;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ZH-CN link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Kevin,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Â Â Â Â Â Â Â Â  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></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Â Â Â Â Â Â Â Â  So It seems this ViaCardID table will only bring faults instead of any good things. Why not remove it?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Frank<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'>Â Â Â Â Â Â Â Â  <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></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'><p class=MsoNormal><b><span style='font-size:10.0pt'>åä»¶äºº<span lang=EN-US>:</span></span></b><span lang=EN-US style='font-size:10.0pt'> Openchrome-devel [mailto:openchrome-devel-bounces@lists.freedesktop.org] </span><b><span style='font-size:10.0pt'>ä»£è¡¨ </span></b><span lang=EN-US style='font-size:10.0pt'>bugzilla-daemon@freedesktop.org<br></span><b><span style='font-size:10.0pt'>åéæ¶é´<span lang=EN-US>:</span></span></b><span lang=EN-US style='font-size:10.0pt'> 2016</span><span style='font-size:10.0pt'>å¹´<span lang=EN-US>2</span>æ<span lang=EN-US>24</span>æ¥<span lang=EN-US> 12:15<br></span><b>æ¶ä»¶äºº<span lang=EN-US>:</span></b><span lang=EN-US> openchrome-devel@lists.freedesktop.org<br></span><b>ä¸»é¢<span lang=EN-US>:</span></b><span lang=EN-US> [Openchrome-devel] [Bug 94210] Unknown Card-Ids (7122|1458|D000), Chipset: VX900<o:p></o:p></span></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p>&nbsp;</o:p></span></p><div><p class=MsoNormal><b><span lang=EN-US><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 <span class=vcard><a href="mailto:kevinbrace@gmx.com" title="Kevin Brace &lt;kevinbrace@gmx.com&gt;"><span class=fn>Kevin Brace</span></a> </span></span></b><span lang=EN-US><o:p></o:p></span></p><pre><span lang=EN-US>(In reply to Dariusz Gadomski from <a href="show_bug.cgi?id=94210#c5">comment #5</a>)<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>Hi Dariusz,<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span class=quote><span lang=EN-US>&gt; Kevin, I will appreciate taking a look at the updated Xorg.log - the<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; segfault is gone, but the driver still does not recognize the card.<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; <o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; Regarding your expectations towards 0.3.4 version adoption in Ubuntu:<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; unfortunately the Stable Release Updates policy<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; (<a href="https://wiki.ubuntu.com/StableReleaseUpdates">https://wiki.ubuntu.com/StableReleaseUpdates</a>) prevents upgrading packages<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; during the lifetime of the stable releases. The only available option seems<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; to be backporting individual changes (in response to reported bugs) to the<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; version already available in a particular release.<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; <o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; Sadly, we also missed the opportunity to release it with 16.04 - as it has<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; entered the feature freeze state.<o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; <o:p></o:p></span></span></pre><pre><span class=quote><span lang=EN-US>&gt; I will check if there are any other options.</span></span><span lang=EN-US><o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>Thank you very much for getting back with me.<o:p></o:p></span></pre><pre><span lang=EN-US>Please ignore the unknown device message you see in Xorg.0.log.<o:p></o:p></span></pre><pre><span lang=EN-US>This occurs due to the use of a weird known device table inside OpenChrome.<o:p></o:p></span></pre><pre><span lang=EN-US>I am not a fan of the use of something like this, <o:p></o:p></span></pre><pre><span lang=EN-US>The code is gradually moving towards all automatic detection of display<o:p></o:p></span></pre><pre><span lang=EN-US>devices, but this will take some time to complete.<o:p></o:p></span></pre><pre><span lang=EN-US>I am considering getting rid of this weird known device table in OpenChrome<o:p></o:p></span></pre><pre><span lang=EN-US>Version 0.3.5, but I will likely keep it in there for Version 0.3.4.<o:p></o:p></span></pre><pre><span lang=EN-US>This is what the weird known device table looks like<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>_____________________________________________________________________________<o:p></o:p></span></pre><pre><span lang=EN-US>. . .<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  /*** VX900 ***/<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  {&quot;Simmtronics SIMM-PC VX900i&quot;,Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1019, 0x3126,<o:p></o:p></span></pre><pre><span lang=EN-US>VIA_DEVICE_CRT},<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  {&quot;ECS VX900-I&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1019, 0x7C8E,<o:p></o:p></span></pre><pre><span lang=EN-US>VIA_DEVICE_CRT},<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  {&quot;Foxconn L740&quot;,Â Â Â Â Â Â Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â VIA_VX900,Â Â  0x105B, 0x0CFD,<o:p></o:p></span></pre><pre><span lang=EN-US>VIA_DEVICE_LCD | VIA_DEVICE_CRT},<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  {&quot;HP T5550 Thin Client&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1106, 0x7122,<o:p></o:p></span></pre><pre><span lang=EN-US>VIA_DEVICE_CRT},<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  {&quot;Biostar Viotech 3200+&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1565, 0x120A,<o:p></o:p></span></pre><pre><span lang=EN-US>VIA_DEVICE_CRT},<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  {&quot;ASRock PV530&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0x1849, 0x7122,<o:p></o:p></span></pre><pre><span lang=EN-US>VIA_DEVICE_CRT},<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  {&quot;Fujitsu Futro A300&quot;,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  VIA_VX900,Â Â  0xA0A0, 0x080F,<o:p></o:p></span></pre><pre><span lang=EN-US>VIA_DEVICE_CRT},<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>Â Â Â  /* keep this */<o:p></o:p></span></pre><pre><span lang=EN-US>Â Â Â  {NULL,Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â Â Â Â Â Â Â Â Â Â Â Â VIA_UNKNOWN, 0x0000, 0x0000,<o:p></o:p></span></pre><pre><span lang=EN-US>VIA_DEVICE_NONE}<o:p></o:p></span></pre><pre><span lang=EN-US>_____________________________________________________________________________<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>Looking at the link you provided, I feel like updating OpenChrome Version 0.3.3<o:p></o:p></span></pre><pre><span lang=EN-US>is quite warranted based on the following clauses I saw in the link you<o:p></o:p></span></pre><pre><span lang=EN-US>provided.<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>___________________________________________________________________________<o:p></o:p></span></pre><pre><span lang=EN-US>2.1. High-impact bugs<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>Stable release updates will, in general, only be issued in order to fix<o:p></o:p></span></pre><pre><span lang=EN-US>high-impact bugs. Examples of such bugs include:<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>. . .<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>- Bugs which represent severe regressions from the previous release of Ubuntu.<o:p></o:p></span></pre><pre><span lang=EN-US>This includes packages which are totally unusable, like being uninstallable or<o:p></o:p></span></pre><pre><span lang=EN-US>crashing on startup.<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>. . .<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>2.2. Other safe cases<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>In the following cases a stable release update is also applicable as they have<o:p></o:p></span></pre><pre><span lang=EN-US>a low potential for regressing existing installations but a high potential for<o:p></o:p></span></pre><pre><span lang=EN-US>improving the user experience, particularly for Long Term Support releases:<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>- Bugs which do not fit under above categories, but (1) have an obviously safe<o:p></o:p></span></pre><pre><span lang=EN-US>patch and (2) affect an application rather than critical infrastructure<o:p></o:p></span></pre><pre><span lang=EN-US>packages (like X.org or the kernel).<o:p></o:p></span></pre><pre><span lang=EN-US>- For Long Term Support releases we regularly want to enable new hardware. Such<o:p></o:p></span></pre><pre><span lang=EN-US>changes are appropriate provided that we can ensure not to affect upgrades on<o:p></o:p></span></pre><pre><span lang=EN-US>existing hardware. For example, modaliases of newly introduced drivers must not<o:p></o:p></span></pre><pre><span lang=EN-US>overlap with previously shipped drivers. This also includes updating hardware<o:p></o:p></span></pre><pre><span lang=EN-US>description data such as udev's keymaps, media-player-info, mobile broadband<o:p></o:p></span></pre><pre><span lang=EN-US>vendors, or PCI vendor/product list updates.<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>___________________________________________________________________________<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>Anyway, since the bug is a fatal one, and a severe regression from Version<o:p></o:p></span></pre><pre><span lang=EN-US>0.2.904, is there a way the newer version can be treated as a security fix<o:p></o:p></span></pre><pre><span lang=EN-US>update so that Canonical can replace OpenChrome Version 0.3.3?<o:p></o:p></span></pre><pre><span lang=EN-US>Also, can OpenChrome Version 0.3.4 go into Ubuntu 16.04.1 LTS if not Ubuntu<o:p></o:p></span></pre><pre><span lang=EN-US>16.04 LTS?<o:p></o:p></span></pre><pre><span lang=EN-US>At this point, I will likely not release OpenChrome Version 0.3.4 since I have<o:p></o:p></span></pre><pre><span lang=EN-US>not been able to fix the DVI related problems completely at this point,<o:p></o:p></span></pre><pre><span lang=EN-US>although there was some progress on this front today.<o:p></o:p></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US><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></span></pre><pre><span lang=EN-US><o:p>&nbsp;</o:p></span></pre><pre><span lang=EN-US>If necessary, I can release OpenChrome Version 0.3.4 immediately, and fix DVI<o:p></o:p></span></pre><pre><span lang=EN-US>related bugs in Version 0.3.5.<o:p></o:p></span></pre></div><div class=MsoNormal align=center style='text-align:center'><span lang=EN-US><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><span lang=EN-US>You are receiving this mail because: <o:p></o:p></span></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span lang=EN-US>You are the assignee for the bug.<o:p></o:p></span></li></ul></div></div></body></html>

Actions: View

Attachments on bug 94210: 121841 | 121928 | 121948

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.