Menu
▾
▴
ddccontrol-devel
|
From: Kai-Uwe B. <ku...@gm...> - 2009-12-01 13:28:17
|
I have monitor here, which supports reading and writing of internal LUTs over a small monitor framework[1]. It accesses the montor over i2c device nodes. That would be nice to integrate in my graphic card LUT viewer[2]. Unfortunedly i2c requires root access on my system. And my understanding is that i2c is a security issue to open for normal users. How can my application nevertheless get the curves. As well there is interesst to do more with this monitor communication channel. Can this be achieved over DDC/CI as well? What would be needed to make it non root read and writeable. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org [1] http://sourceforge.net/projects/ookala-mcf/ [2] http://www.oyranos.org/#icc_examin |
|
From: William O. <gun...@on...> - 2009-12-03 20:25:36
|
Hello, Le 01/12/2009 14:28, Kai-Uwe Behrmann a écrit : > I have monitor here, which supports reading and writing of internal LUTs > over a small monitor framework[1]. It accesses the montor over i2c > device nodes. That would be nice to integrate in my graphic card LUT > viewer[2]. > > Unfortunedly i2c requires root access on my system. And my understanding > is that i2c is a security issue to open for normal users. I wasn't aware of that. Where did you get this information from? > How can my > application nevertheless get the curves. As well there is interesst > to do more with this monitor communication channel. > > Can this be achieved over DDC/CI as well? What would be needed to make it > non root read and writeable. > What ddccontrol allows you to do is read and write values that are stored in the monitor's internal chip, so that you can control parameters like Brightness, Contrast, color temp, etc. from you computer, just as you would with the buttons and OSD of your monitor. ddccontrol can use different low-level protocols to do that : for example, I can use i2c, or use my Nvidia graphics card driver's capabilities to communicate with my monitor. DDC/CI is a protocol that works on top of i2c, so as far as I can tell, you will still need to run ddccontrol as root to be able to communicate with your monitor. A while ago, I tried to make ddccontrol work at a user level, but I didn't manage. I'm the current maintainer of the project, but I'm quite busy right now. Maybe we could figure something out together, when we both have time. I hope this answers your question. Regards, William |
|
From: Kai-Uwe B. <ku...@gm...> - 2009-12-04 09:44:15
|
Hello, Am 03.12.09, 12:46 +0100 schrieb William OLLIVIER: > Le 01/12/2009 14:28, Kai-Uwe Behrmann a écrit : >> I have monitor here, which supports reading and writing of internal LUTs >> over a small monitor framework[1]. It accesses the montor over i2c >> device nodes. That would be nice to integrate in my graphic card LUT >> viewer[2]. >> >> Unfortunedly i2c requires root access on my system. And my understanding >> is that i2c is a security issue to open for normal users. > I wasn't aware of that. Where did you get this information from? Seeing that i2c is used for several hardware controls, I guessed that it is cruical to not let ordinary users change clock speed and similiar by default. On my distribution the /dev/i2c-xxx devices are owned by root with chmod 0440. This is controled on startup, and again I guess this is similiar on many Linux distributions. >> How can my >> application nevertheless get the curves. As well there is interesst >> to do more with this monitor communication channel. >> >> Can this be achieved over DDC/CI as well? What would be needed to make it >> non root read and writeable. >> > What ddccontrol allows you to do is read and write values that are > stored in the monitor's internal chip, so that you can control > parameters like Brightness, Contrast, color temp, etc. from you > computer, just as you would with the buttons and OSD of your monitor. > > ddccontrol can use different low-level protocols to do that : for > example, I can use i2c, or use my Nvidia graphics card driver's > capabilities to communicate with my monitor. The nvidia extensions regarding ddc/ci I have noticed. They are probably not a general i2c interface but only ddc/ci. So access through them might be restricted to monitor communication than the i2c device nodes. > DDC/CI is a protocol that works on top of i2c, so as far as I can tell, > you will still need to run ddccontrol as root to be able to communicate > with your monitor. Thanks for your confirmation. > A while ago, I tried to make ddccontrol work at a user level, but I > didn't manage. I'm the current maintainer of the project, but I'm quite > busy right now. Maybe we could figure something out together, when we > both have time. On the Xorg list, I started a thread about that matter. I think ddc/ci would be best integrated therein. Hopefully this opens for a general API that ddccontrol can migrate to as well. Having not to rely on root access is for UI tools essential in order to get generally accepted for desktop use. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org |
|
From: Oleg I. V. <ol...@cs...> - 2009-12-04 11:20:11
|
Hi,
> On the Xorg list, I started a thread about that matter. I think ddc/ci
> would be best integrated therein. Hopefully this opens for a general API
> that ddccontrol can migrate to as well. Having not to rely on root access
> is for UI tools essential in order to get generally accepted for desktop
> use.
ddccontrol is not limited to graphical mode, it's supposed to work in
text mode too, so no X stuff is used at all. Xorg guys has it's own access
to i2c for sure, so they of course could provide a way to ddccontrol to
access this bus or intergate some part of ddccontrol.
Keep in mind that project is now mostly dead for several years now...
Regards,
Oleg.
|
|
From: William O. <gun...@on...> - 2009-12-04 11:22:24
|
Hi Oleg, It's good to see that I'm not the only one to read the ddccontol mailing-lists. Le 04/12/2009 11:39, Oleg I. Vdovikin a écrit : > Keep in mind that project is now mostly dead for several years now... If you're speaking of ddccontrol, I intend to change that statement. I currently don't have much time to work on it, but once I graduate, I should be able to extend the database, and other things. So far, ddccontrol is the ONLY tool running on Linux that I could find to control my button-less, OSD-less monitor. ddccontrol allowed me for the first time in several years to lower the brightness of my monitor. So there is no way I'm letting it die! Cheers William |
|
From: Lars T. B. <li...@sn...> - 2010-01-18 13:28:45
|
Hi, Oleg I. Vdovikin wrote: > Keep in mind that project is now mostly dead for several years now... That's partly true, the SVN repository shows commits nearly each month, but only in the database, not in the program. The program hasn't received a commit for 2 years. Kiran Kotla did write a patch to the program to speed it up by more than double, but it hasn't been accepted upstream. -- Regards, Lars Tobias |
Thanks for helping keep SourceForge clean.
X