Sanford Rockowitz
2017-05-01 15:26:04 UTC
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "ddcutil"
* Package name : ddcutil
Version : 0.8.0-6
Upstream Author : Sanford Rockowitz <***@minsoft.com>
* URL : https://github.com/rockowitz/ddcutil
* License : GPL-2.0
Section : utils
It builds those binary packages:
ddcutil - Control monitor settings - Standalone command line version
libddcutil-dev - ddcutil - C development files
libddcutil0 - ddcutil - Shared libraries
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/ddcutil
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/d/ddcutil/ddcutil_0.8.0-6.dsc
More information about ddcutil can be obtained from
https://www.ddcutil.com
Changes since the last upload:
ddcutil (0.8.0-6) unstable; urgency=low
* Bump Debian release for debian-mentors
ddcutil is a utility for querying and changing monitor settings, such as
brightness and color levels.
ddcutil primarily uses DDC/CI (Display Data Channel Command Interface) to
communicate with monitors implementing MCCS (Monitor Control Command Set)
over I2C. Alternatively, there is support for monitors (such as Eizo
ColorEdge
displays) that implement MCCS using a USB connection.
Use cases for ddcutil include:
- To record and reset color related settings as part of color profile
management
- Switching monitor input
- Controlling brightness
The most closely comparable program is ddccontrol, which has not been
maintained
for several years. The design of ddcutil differs from ddccontrol in two
fundamental
ways that should make it more robust in the face of hardware changes and
monitor
variation:
1) It uses the userspace i2c-dev interface instead of providing its own
I2C drivers,
so is less sensitive to video driver implementation.
2) Instead of relying on a database of features by monitor model, which can
never hope to be up to date, ddcutil bases its feature interpretation on
a detailed understanding of the MCCS specification. The downside is that
can only give generic interpretation for MCCS Virtual Control Panel features
in the range reserved for manufacturer specific features.
Regards,
Sanford Rockowitz
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "ddcutil"
* Package name : ddcutil
Version : 0.8.0-6
Upstream Author : Sanford Rockowitz <***@minsoft.com>
* URL : https://github.com/rockowitz/ddcutil
* License : GPL-2.0
Section : utils
It builds those binary packages:
ddcutil - Control monitor settings - Standalone command line version
libddcutil-dev - ddcutil - C development files
libddcutil0 - ddcutil - Shared libraries
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/ddcutil
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/d/ddcutil/ddcutil_0.8.0-6.dsc
More information about ddcutil can be obtained from
https://www.ddcutil.com
Changes since the last upload:
ddcutil (0.8.0-6) unstable; urgency=low
* Bump Debian release for debian-mentors
ddcutil is a utility for querying and changing monitor settings, such as
brightness and color levels.
ddcutil primarily uses DDC/CI (Display Data Channel Command Interface) to
communicate with monitors implementing MCCS (Monitor Control Command Set)
over I2C. Alternatively, there is support for monitors (such as Eizo
ColorEdge
displays) that implement MCCS using a USB connection.
Use cases for ddcutil include:
- To record and reset color related settings as part of color profile
management
- Switching monitor input
- Controlling brightness
The most closely comparable program is ddccontrol, which has not been
maintained
for several years. The design of ddcutil differs from ddccontrol in two
fundamental
ways that should make it more robust in the face of hardware changes and
monitor
variation:
1) It uses the userspace i2c-dev interface instead of providing its own
I2C drivers,
so is less sensitive to video driver implementation.
2) Instead of relying on a database of features by monitor model, which can
never hope to be up to date, ddcutil bases its feature interpretation on
a detailed understanding of the MCCS specification. The downside is that
can only give generic interpretation for MCCS Virtual Control Panel features
in the range reserved for manufacturer specific features.
Regards,
Sanford Rockowitz