[Openchrome-devel] [Bug 94473] DRM / KMS bootup error on VX900 platform

[bugzilla-daemon at freedesktop.org]

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

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

  I have not gotten time to go through this discussion. But in my opinion, I
fully support your point to remove legacy code(VBE, device table...) because
those modules are also not used anymore in modern Intel/AMD open source driver.
Also, using I2C to detect EDID information is the trend which replaces the
fixed table method. 
  Making some code in regression in this process is normal. We just need record
which commit id is working and let users(like me) to know that or as Benno
said, we can use a branch to do that before committing to master. By this way,
the users can still get correct working driver which will make them happy to go
with the new driver.

Thanks,
Frank

(In reply to Kevin Brace from comment #59)

> I was taking a break from my OpenChrome hard work today, but during my
> slacking off period, I found this public UniChrome / OpenChrome feud thread
> from 2005.
> 
> http://markmail.org/message/vutzfc65va4h554r#query:+page:1+mid:
> x4bp6vxkd7kmf3sh+state:results
> 
> That thread explains the schism the two project had more than 10 years ago,
> and it served no one's interest, in my opinion.
> Apparently, Luc Verhaegen (who is still active in the FOSS graphics scene)
> and Thomas Hellström (who now works for VMware) had issues.
> Read the posts from Luc and Thomas.
> It is very interesting.
> With the hindsight of 20/20, I think Luc was right that VBE mode setting
> should have never been in the code, or should have been removed by 2010.
> This is why I removed VBE mode setting support a few days ago (10 years
> later).
> I removed it because VBE and "known device table" were causing display
> detection coding nightmare.
> I fix one problem (DVI to VGA adapter problem), and then flat panel of my
> netbook (non-I2C flat panel) goes wrong.
> If I fix that non-I2C flat panel, then DVI to VGA adapter no longer works
> (you and Eric reported this for Wyse thin client recently).
> This is why I wanted to remove the legacy code that causes so many issues,
> but now I have to put it back for the one last time.
> After that VBE mode setting will be gone.
> In some ways, Luc is finally vindicated, but 10 years too late.
> So Frank, that's the much less than flattering history of OpenChrome.
> This schism from 10 years ago still has an impact (on me and others who have
> seen their screen disappear) even today.

-- 
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/20160326/fe6dccdb/attachment.html>