[Openchrome-users] New openchrome driver -version appeared in Debian-testing

[Andreas Glaeser]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 2 Apr 2016 05:14:17 +0200
"Kevin Brace" <kevinbrace at gmx.com> wrote:

> This is Kevin Brace.
> I am the current OpenChrome project maintainer.
> I just released Version 0.4.0, and I hope this improves the situation you experienced.
> I communicated with Timo Aaltonen of Debian X Strike Force, and he told me that he will
> upload the new version soon. There is a reason why the flat panel did not work with
> your laptop. This is because the older OpenChrome was relying very heavily on what I
> call "known device table," and basically this was misdetecting the display devices
> attached to your computer. Here is part of the Xorg.0.log you posted.
> 
> > [    24.500] (WW) CHROME(0): Manufacturer plainly copied main PCI IDs to
> > subsystem/card IDs. [    24.500] (--) CHROME(0): Detected VIA VT3344 (VM800) - EPIA
> > EN. Card-Ids (1106|3344) [    24.500] (II) CHROME(0): Detected MemClk 3  
> 
> Until very recently, OpenChrome needed a positive match for PCI subvendor ID and
> subdevice ID to even think about initializing a flat panel. In addition to this, an LCD
> panel option had to be specified manually in this "known device table" in order for it
> to work. This "known device table" used to be located somewhere in the source code, so
> it is not something most end users can deal with it. In your case, it was detecting a
> VIA EPIA-EN mini-ITX mainboard, and I will somewhat doubt that this supports a flat
> panel. This is so problematic and going against the industry trend of automatic
> detection, so I finally got rid of it. I just took over the project 2 months or so ago,
> and I have different views than the previous developers on how to improve OpenChrome.
> Besides that, previous developers went AWOL, so I was able to take over the project
> without much resistance. It is my goal to improve the stability and reliability of
> OpenChrome, and while it might take several years for it, I am willing to work on it
> for years to come.


Hello, there,

thanks a lot for explaining the problem very verbosely in human readable text, I am not

much of a C-programmer, currently I feel looking at the source-code directly would only

be a waste of time, because I am still missing some of the basics of C and clearly lack

practice in actually writing code.

The situation with the moobile thin-client seems to be similar with the other thin-clients

I have tested out, so I am lookign forward already to closing some of those Debian-bugs.


Greetings

Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlb/iu8ACgkQ5+rBHyUt5wvw+gCfYt7Ek2ijJGYxn8T6tlgGGH0S
P8YAn2K2Mmky0fAovtUluV5Ba2cAxnC7
=3szI
-----END PGP SIGNATURE-----