<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Unknown Card-Ids (3371|1019|2125)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92711#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Unknown Card-Ids (3371|1019|2125)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92711">bug 92711</a>
from <span class="vcard"><a class="email" href="mailto:tylderon@yahoo.com.br" title="tylderon@yahoo.com.br">tylderon@yahoo.com.br</a>
</span></b>
<pre>Hello, Kevin.
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.
There are less issues now, thanks to your work (and the other contributors'
too). And maybe kernel integration in the foreseeable future. Pretty cool. :-)
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.
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.
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*).
My best regards to you and the team!
De: "<a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>" <<a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>>
Para: <a href="mailto:tylderon@yahoo.com.br">tylderon@yahoo.com.br</a>
Enviadas: Terça-feira, 16 de Fevereiro de 2016 3:08
Assunto: [<a class="bz_bug_link
bz_status_NEW "
title="NEW - Unknown Card-Ids (3371|1019|2125)"
href="show_bug.cgi?id=92711">Bug 92711</a>] Unknown Card-Ids (3371|1019|2125)
<a href="show_bug.cgi?id=92711#c2">Comment # 2</a> on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Unknown Card-Ids (3371|1019|2125)"
href="show_bug.cgi?id=92711">bug 92711</a> from Kevin Brace 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 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 href="https://lists.freedesktop.org/archives/openchrome-devel/2016-February/001753.html">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 class="bz_bug_link
bz_status_NEW "
title="NEW - Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896"
href="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. You are receiving this mail because:
- You reported the bug.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>