[Openchrome-devel] [Bug 94130] Unknown Card-Ids (3371|1019|2125), Chipset: P4M900/VN896/CN896

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=94130

--- Comment #16 from HuangRan <huangran at iscas.ac.cn> ---
Hi Kevin,

   Do you mean that 0.3.4 and 0.4.0 will not support VT1632A support with DVI
port? And as I reported in 91966 bug, right now my V90LE still not work with
VGA and DVI ports both with latest git repository code. So for which commit id
of UMS driver, I can use for V90LE?
   Please let me know it and verify it before you make 0.3.4 release.

Thanks,
Frank

(In reply to Kevin Brace from comment #14)
> Hi everyone,
> 
> I can go with the idea of releasing OpenChrome Version 0.3.4, but I will say
> that I will need to reverse last several commits I have made.
> This is what it will mean.
> 
> - The large known device table will stay (only for Version 0.3.4)
> - VBE mode setting will stay (only for Version 0.3.4)
> - "Legacy" mode setting will stay (only for Version 0.3.4)
> - Benno's patch (Bug 94660) will get incorporated
> - Drop support for VT1632A external TMDS transmitter for now 
>   (it does not work)
> 
> If this sounds okay, I can release OpenChrome Version 0.3.4 within two weeks.
> Of course, this assumes that I do not run into Git related tool usage issue.
>     After that, I will return to "regularly scheduled program already in
> progress," and remove the following items from the master branch source code.
> 
> - The large known device table
> - VBE mode setting option
> - "Legacy" mode setting option
> 
> That version will be called OpenChrome Version 0.4.0, and all future
> development work will revolve around this version.
> I do not plan to make any more fixes to Version 0.3.4 branch code since it
> is broken in many ways.
> I hope to get VT1632A support back for something like Version 0.4.1 or 0.4.2.
> I will also like to support Silicon Image SiI 164 for that future version.
>     Regarding VT1632A support, all I will do for now is OpenChrome will not
> initialize it.
> The code will stay, but via_dvi_init will not be called, making it
> effectively inactive.
> Let me know how all of you think.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/openchrome-devel/attachments/20160325/7304c099/attachment-0001.html>