HP L2245wg

[anarcat]

probably very similar to the HP LP2475w described in #31, but I figured i would keep that split out since the model numbers are different. i suspect it will end up being the same configuration because it's looking for the same file, namely /usr/share/ddccontrol-db/monitor/HWP26FB.xml, but i'll let you call the shots on that. :)

root@curie:/home/anarcat# LANG= LC_ALL= ddccontrol -p -c -d
ddccontrol version 0.4.2
Copyright 2004-2005 Oleg I. Vdovikin (oleg@cs.msu.su)
Copyright 2004-2006 Nicolas Boichat (nicolas@boichat.ch)
This program comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of this program under the terms of the GNU General Public License.

Probing for available monitorsI/O warning : failed to load external entity "/usr/share/ddccontrol-db/monitor/HWP26FB.xml"
Document not parsed successfully.
.....
Detected monitors :
 - Device: dev:/dev/i2c-4
   DDC/CI supported: Yes
   Monitor Name: VESA standard monitor
   Input type: Analog
  (Automatically selected)
Reading EDID and initializing DDC/CI at bus dev:/dev/i2c-4...
I/O warning : failed to load external entity "/usr/share/ddccontrol-db/monitor/HWP26FB.xml"
Document not parsed successfully.

EDID readings:
    Plug and Play ID: HWP26FB [VESA standard monitor]
    Input type: Analog
=============================== WARNING ===============================
There is no support for your monitor in the database, but ddccontrol is
using a basic generic profile. Many controls will not be supported, and
some controls may not work as expected.
Please update ddccontrol-db, or, if you are already using the latest
version, please send the output of the following command to
ddccontrol-users@lists.sourceforge.net:

LANG= LC_ALL= ddccontrol -p -c -d

Thank you.
=============================== WARNING ===============================

Capabilities:
Raw output: (prot(monitor)type(LCD)model(L2245W)cmds(01 02 03 07 0C E3 F3)vcp(02 04 05 06 08 0B 0C 0E 10 12 14(01 05 08 0B) 16 18 1A 1E 1F 20 30 3E 52 60(01 03)  6C 6E 70 AC AE B2 B6 C6 C8 C9 CA C0 CC(01 02  03 04 05 06 08  0A 13) D6(01 04 05) DF FA(00 01 02) FB FC FD FE(00 01 02 04))mswhql(1)asset_eep(40)mccs_ver(2.1))
Parsed output: 
    VCP: 02 04 05 06 08 0b 0c 0e 10 12 14 16 18 1a 1e 1f 20 30 3e 52 60 6c 6e 70 ac ae b2 b6 c0 c6 c8 c9 ca cc d6 df fa fb fc fd fe 
    Type: Unknown

Controls (valid/current/max) [Description - Value name]:
Control 0x02: +/2/2 C [???]
Control 0x04: +/0/1 C [Restore Factory Defaults]
Control 0x05: +/0/1 C [Restore Brightness and Contrast]
Control 0x06: +/0/1 C [Restore Factory Default Geometry]
Control 0x08: +/0/1 C [Restore Factory Default Color]
Control 0x0b: +/3000/65535 C [???]
Control 0x0c: +/1/2 C [???]
Control 0x0e: +/60/120 C [Image Lock Coarse (Clock)]
Control 0x10: +/90/100 C [Brightness]
Control 0x12: +/80/100 C [Contrast]
Control 0x14: +/5/11 C [???]
Control 0x16: +/255/255 C [Red maximum level]
Control 0x18: +/255/255 C [Green maximum level]
Control 0x1a: +/255/255 C [Blue maximum level]
Control 0x1e: +/0/255 C [Automatically adjust]
Control 0x1f: +/0/255 C [???]
Control 0x20: +/50/100 C [Horizontal Position]
Control 0x30: +/50/100 C [Vertical Position]
Control 0x3e: +/46/60 C [Image Lock Fine (Clock Phase)]
Control 0x52: +/81/65535 C [???]
Control 0x60: +/1/3 C [Input Source Select - Analog]
Control 0x6c: +/2/100 C [Red minimum level]
Control 0x6e: +/2/100 C [Green minimum level]
Control 0x70: +/2/100 C [Blue minimum level]
Control 0xac: +/64/1 C [???]
Control 0xae: +/6030/65535 C [???]
Control 0xb2: +/1/8 C [???]
Control 0xb6: +/3/0 C [???]
Control 0xc0: +/7237/65535 C [???]
Control 0xc6: +/90/65535 C [???]
Control 0xc8: +/9/9509 C [???]
Control 0xc9: +/256/0 C [???]
Control 0xca: +/2/2 C [???]
Control 0xcc: +/2/21 C [???]
Control 0xd6: +/1/5 C [DPMS Control - On]
Non-fatal error: Invalid response, magic is 0x6e
Invalid response, length is 110, should be 8 at most
Control 0xdf: +/513/0 C [???]
Control 0xfa: +/0/255 C [???]
Control 0xfb: +/0/60 C [???]
Control 0xfc: +/0/65535 C [???]
Control 0xfd: +/0/65535 C [???]
Control 0xfe: +/0/255 C [???]

i was able to control the brightness, but didn't test the other parameters.

[kravemir]

If you could make a monitor descriptor, it would be great. You don't have to test everything, but it's good to document what have you done, so somebody else could catch up the work. For example, see following PR: https://github.com/ddccontrol/ddccontrol-db/pull/49/files. You can use some markdown editor like Typora, and process ddccontrol output with sed to make initial Markdown table.

[anarcat]

hmm... that seems like a rather involved process... why doesn't ddccontrol output this format directly?

[kravemir]

This was a long dead project. There are many areas, which need improvement, and currently there's limited capacity of developers. Right now, only I'm working on a project, and I'm focusing on creation of D-Bus daemon: https://github.com/ddccontrol/ddccontrol/issues/25

[anarcat]

okay well... i don't have much time for this either unfortunately... i'm glad to see you take up the project, but i unfortunately can't contribute to the same level. i hope someone can pick up this issue (and others) and make something with them!

i'm also a bit confused as to why there is both a markdown and XML specification... don't those overlap somehow?

[kravemir]

okay well... i don't have much time for this either unfortunately... i'm glad to see you take up the project, but i unfortunately can't contribute to the same level. i hope someone can pick up this issue (and others) and make something with them!

Currently, help with sponsoring Debian packages would be great! :-)

i'm also a bit confused as to why there is both a markdown and XML specification... don't those overlap somehow?

XML doesn't contain testing documentation. Someone could just copy other monitor descriptor. Documentation about what had been tested adds some order/system to it. But, if somebody is making a descriptor, there's some testing involved, and usually it's also somehow noted. So, in the end, most time is spent by testing, not by creating documentation.

I've got an idea how to make creation of monitor XML easier - using a wizard. I have already made initial GUI skeleton using Python and GTK. But, now I'm focusing on usage - daemon. I will probably be "spamming" all the monitor issues to let people know, once it is implemented.

[anarcat]

makes sense. i'll wait for this and help you with debian instead, shortly.