Attachment 121786 Details for Bug 92711 – attachment-8793-0.html

attachment-8793-0.html

attachment-8793-0.html (text/html), 6.45 KB, created by tylderon on 2016-02-16 16:07:38 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: tylderon

Created: 2016-02-16 16:07:38 UTC

Size: 6.45 KB

patch

obsolete

><html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_1_1455638327542_2765"><span>Hello, Kevin.</span></div><div id="yui_3_16_0_1_1455638327542_2676"><span><br></span></div><div id="yui_3_16_0_1_1455638327542_2760"><span id="yui_3_16_0_1_1455638327542_2759">Don't worry at all. You're doing it for free, and I've been keeping track of the truckload of changes you've been comitting to OpenChrome. I have to say I'm pretty glad you got the time, interest *and* technical skills to help so thoroughly with this project. Thank you for all you (and everyone else) have been doing for this hardware. Believe it or not, this video card is quite widespread around (because it's so cheap) and it's sad to see Linux having so many issues with it.</span></div><div id="yui_3_16_0_1_1455638327542_2761"><span><br></span></div><div id="yui_3_16_0_1_1455638327542_2762"><span id="yui_3_16_0_1_1455638327542_2796">There are less issues now, thanks to your work (and the other contributors' too). And maybe kernel integration in the foreseeable future. Pretty cool. :-)</span></div><div id="yui_3_16_0_1_1455638327542_2762"><span><br></span></div><div id="yui_3_16_0_1_1455638327542_2762">The bad news is that I don't have the hardware with me anymore, so I really can't test the changes. It's not with anyone I'm in touch with either (it's been donated), so I can't contact anyone to test it.</div><div id="yui_3_16_0_1_1455638327542_2762"><br></div><div id="yui_3_16_0_1_1455638327542_2762">The good news is that, as soon as I "committed" my changes (attached to this bug) and rebuilt the driver, it worked flawlessly and automagically. No quirky Xorg settings, nothing. So it seems that it was *really* just a matter of adding it to the device table. My hardware id is strictly the same as the one in the new bug you mentioned. I know testing it would be the perfect solution, but there's little theoretical difference between our cases - the solution for the new bug should "solve" my problem as well.</div><div id="yui_3_16_0_1_1455638327542_2762"><br></div><div id="yui_3_16_0_1_1455638327542_2762" dir="ltr">I'm glad you're trying to make the driver less table-dependent. I can't really understand why it would *need* to match a device table in order to work, once it has already been detected as OpenChrome by the whole subsystem (I can understand its usefulness, but not it's absolute *necessity*).</div><div id="yui_3_16_0_1_1455638327542_2762" dir="ltr"><br></div><div id="yui_3_16_0_1_1455638327542_2762" dir="ltr">My best regards to you and the team!</div><div class="qtdSeparateBR" id="yui_3_16_0_1_1455638327542_2634"><br></div><div class="yahoo_quoted" id="yui_3_16_0_1_1455638327542_2639" style="display: block;">  <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13px;" id="yui_3_16_0_1_1455638327542_2638"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_1_1455638327542_2637"> <div dir="ltr" id="yui_3_16_0_1_1455638327542_2636"> <font size="2" face="Arial" id="yui_3_16_0_1_1455638327542_2635"> <hr size="1"> <b><span style="font-weight:bold;">De:</span></b> "bugzilla-daemon@freedesktop.org" &lt;bugzilla-daemon@freedesktop.org&gt;<br> <b><span style="font-weight: bold;">Para:</span></b> tylderon@yahoo.com.br <br> <b><span style="font-weight: bold;">Enviadas:</span></b> TerÃ§a-feira, 16 de Fevereiro de 2016 3:08<br> <b><span style="font-weight: bold;">Assunto:</span></b> [Bug 92711] Unknown Card-Ids (3371|1019|2125)<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_1_1455638327542_2640"><br><div id="yiv2757932415">
>    
>      <base>
>    
>    <div id="yui_3_16_0_1_1455638327542_2645">
>      <div>
>        </div><div id="yui_3_16_0_1_1455638327542_2644">
>            <b id="yui_3_16_0_1_1455638327542_2943"><a rel="nofollow" class="yiv2757932415bz_bug_link           yiv2757932415bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125)" target="_blank" href="https://bugs.freedesktop.org/show_bug.cgi?id=92711#c2">Comment # 2</a>
>              on <a rel="nofollow" class="yiv2757932415bz_bug_link           yiv2757932415bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125)" target="_blank" href="https://bugs.freedesktop.org/show_bug.cgi?id=92711" id="yui_3_16_0_1_1455638327542_2942">bug 92711</a>
>              from <span class="yiv2757932415vcard"><a rel="nofollow" class="yiv2757932415email" ymailto="mailto:kevinbrace@gmx.com" target="_blank" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> <span class="yiv2757932415fn">Kevin Brace</span></a>
></span></b>
>        <pre id="yui_3_16_0_1_1455638327542_2646">Just to let you know, OpenChrome project has been without a maintainer for many
>months.
>This is why you did not get a response.
>I recently obtained a commit privilege, and have already made several commits.
>
><a rel="nofollow" target="_blank" href="https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/">https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/</a>
>
>I also wrote a detailed instructions on how to compile the device driver.
>
><a rel="nofollow" target="_blank" href="https://lists.freedesktop.org/archives/openchrome-devel/2016-February/001753.html" id="yui_3_16_0_1_1455638327542_2675">https://lists.freedesktop.org/archives/openchrome-devel/2016-February/001753.html</a>
>
>It may not be necessary since you already know how to compile the device
>driver, but just included the location of it for your reference.
>I can say that your bug appears similar to a newer bug that got reported
>recently.
>
><a rel="nofollow" class="yiv2757932415bz_bug_link           yiv2757932415bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896" target="_blank" href="https://bugs.freedesktop.org/show_bug.cgi?id=94130">https://bugs.freedesktop.org/show_bug.cgi?id=94130</a>
>
>It will be nice if you can try the latest OpenChrome master branch code without
>your LCD related workaround, in order to see what happens.
>In general, I am inclined to reduce the usage of the predefined device table
>moving forward.</pre>
>        </div>
>      
>      <hr>
>      <span>You are receiving this mail because:</span>
>      
>      <ul>
>          <li>You reported the bug.</li>
>      </ul>
>    </div>
></div><br><br></div> </div> </div>  </div></div></body></html>

<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_1_1455638327542_2765"><span>Hello, Kevin.</span></div><div id="yui_3_16_0_1_1455638327542_2676"><span><br></span></div><div id="yui_3_16_0_1_1455638327542_2760"><span id="yui_3_16_0_1_1455638327542_2759">Don't worry at all. You're doing it for free, and I've been keeping track of the truckload of changes you've been comitting to OpenChrome. I have to say I'm pretty glad you got the time, interest *and* technical skills to help so thoroughly with this project. Thank you for all you (and everyone else) have been doing for this hardware. Believe it or not, this video card is quite widespread around (because it's so cheap) and it's sad to see Linux having so many issues with it.</span></div><div id="yui_3_16_0_1_1455638327542_2761"><span><br></span></div><div id="yui_3_16_0_1_1455638327542_2762"><span id="yui_3_16_0_1_1455638327542_2796">There are less issues now, thanks to your work (and the other contributors' too). And maybe kernel integration in the foreseeable future. Pretty cool. :-)</span></div><div id="yui_3_16_0_1_1455638327542_2762"><span><br></span></div><div id="yui_3_16_0_1_1455638327542_2762">The bad news is that I don't have the hardware with me anymore, so I really can't test the changes. It's not with anyone I'm in touch with either (it's been donated), so I can't contact anyone to test it.</div><div id="yui_3_16_0_1_1455638327542_2762"><br></div><div id="yui_3_16_0_1_1455638327542_2762">The good news is that, as soon as I "committed" my changes (attached to this bug) and rebuilt the driver, it worked flawlessly and automagically. No quirky Xorg settings, nothing. So it seems that it was *really* just a matter of adding it to the device table. My hardware id is strictly the same as the one in the new bug you mentioned. I know testing it would be the perfect solution, but there's little theoretical difference between our cases - the solution for the new bug should "solve" my problem as well.</div><div id="yui_3_16_0_1_1455638327542_2762"><br></div><div id="yui_3_16_0_1_1455638327542_2762" dir="ltr">I'm glad you're trying to make the driver less table-dependent. I can't really understand why it would *need* to match a device table in order to work, once it has already been detected as OpenChrome by the whole subsystem (I can understand its usefulness, but not it's absolute *necessity*).</div><div id="yui_3_16_0_1_1455638327542_2762" dir="ltr"><br></div><div id="yui_3_16_0_1_1455638327542_2762" dir="ltr">My best regards to you and the team!</div><div class="qtdSeparateBR" id="yui_3_16_0_1_1455638327542_2634"><br></div><div class="yahoo_quoted" id="yui_3_16_0_1_1455638327542_2639" style="display: block;">  <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13px;" id="yui_3_16_0_1_1455638327542_2638"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_1_1455638327542_2637"> <div dir="ltr" id="yui_3_16_0_1_1455638327542_2636"> <font size="2" face="Arial" id="yui_3_16_0_1_1455638327542_2635"> <hr size="1"> <b><span style="font-weight:bold;">De:</span></b> "bugzilla-daemon@freedesktop.org" &lt;bugzilla-daemon@freedesktop.org&gt;<br> <b><span style="font-weight: bold;">Para:</span></b> tylderon@yahoo.com.br <br> <b><span style="font-weight: bold;">Enviadas:</span></b> TerÃ§a-feira, 16 de Fevereiro de 2016 3:08<br> <b><span style="font-weight: bold;">Assunto:</span></b> [Bug 92711] Unknown Card-Ids (3371|1019|2125)<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_1_1455638327542_2640"><br><div id="yiv2757932415">
    
      <base>
    
    <div id="yui_3_16_0_1_1455638327542_2645">
      <div>
        </div><div id="yui_3_16_0_1_1455638327542_2644">
            <b id="yui_3_16_0_1_1455638327542_2943"><a rel="nofollow" class="yiv2757932415bz_bug_link           yiv2757932415bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125)" target="_blank" href="https://bugs.freedesktop.org/show_bug.cgi?id=92711#c2">Comment # 2</a>
              on <a rel="nofollow" class="yiv2757932415bz_bug_link           yiv2757932415bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125)" target="_blank" href="https://bugs.freedesktop.org/show_bug.cgi?id=92711" id="yui_3_16_0_1_1455638327542_2942">bug 92711</a>
              from <span class="yiv2757932415vcard"><a rel="nofollow" class="yiv2757932415email" ymailto="mailto:kevinbrace@gmx.com" target="_blank" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> <span class="yiv2757932415fn">Kevin Brace</span></a>
</span></b>
        <pre id="yui_3_16_0_1_1455638327542_2646">Just to let you know, OpenChrome project has been without a maintainer for many
months.
This is why you did not get a response.
I recently obtained a commit privilege, and have already made several commits.

<a rel="nofollow" target="_blank" href="https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/">https://cgit.freedesktop.org/openchrome/xf86-video-openchrome/</a>

I also wrote a detailed instructions on how to compile the device driver.

<a rel="nofollow" target="_blank" href="https://lists.freedesktop.org/archives/openchrome-devel/2016-February/001753.html" id="yui_3_16_0_1_1455638327542_2675">https://lists.freedesktop.org/archives/openchrome-devel/2016-February/001753.html</a>

It may not be necessary since you already know how to compile the device
driver, but just included the location of it for your reference.
I can say that your bug appears similar to a newer bug that got reported
recently.

<a rel="nofollow" class="yiv2757932415bz_bug_link           yiv2757932415bz_status_NEW " title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896" target="_blank" href="https://bugs.freedesktop.org/show_bug.cgi?id=94130">https://bugs.freedesktop.org/show_bug.cgi?id=94130</a>

It will be nice if you can try the latest OpenChrome master branch code without
your LCD related workaround, in order to see what happens.
In general, I am inclined to reduce the usage of the predefined device table
moving forward.</pre>
        </div>
      
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You reported the bug.</li>
      </ul>
    </div>
</div><br><br></div> </div> </div>  </div></div></body></html>

Actions: View

Attachments on bug 92711: 119259 | 121786

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.