You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(1) |
Feb
(4) |
Mar
(4) |
Apr
|
May
|
Jun
(4) |
Jul
(3) |
Aug
(5) |
Sep
(18) |
Oct
(1) |
Nov
(5) |
Dec
(2) |
2006 |
Jan
|
Feb
(7) |
Mar
(11) |
Apr
(2) |
May
(4) |
Jun
(12) |
Jul
(7) |
Aug
(6) |
Sep
(5) |
Oct
(5) |
Nov
|
Dec
(1) |
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
(1) |
Dec
|
2008 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(5) |
2010 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
(2) |
2013 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Nicolas B. <ni...@bo...> - 2006-10-14 07:25:01
|
Hello, I just released a new version of the database, see the changelog below. Thanks Roberto for your message, it gave me the motivation to release it sooner that what I'm used to do .-) So I hope this new version will get in the next Debian release. Best regards, Nicolas Changelog: - Add support for new monitors: + Add support for Samsung SyncMaster 971P (Thanks to Oleg Artamonov) + Improve support for Samsung SyncMaster 244T (Thanks to Oleg Artamonov) + Add support for Philips 170B (Thanks to Jamil Djadala) + Add support for AOC LM928 (Thanks to Michael G. Hansen) + Add support for DELL 1905FP (Thanks to David R. Piegdon) + Add support for NEC LCD175VXM (Thanks to Raymond Tau) + Add support for Samsung Syncmaster 215TW DVI (Thanks to Jason Ellefson) + Add support for Dell 2007FP (Thanks to Oleg Artamonov) + Add support for Dell 1907FP (Thanks to rkoumis). + Add support for Samsung SyncMaster 940BF (Thanks to Daniel) + Add support for Samsung SyncMaster 244T (Thanks to Mega MoiX) + Add support for Philips 200W6 (Thanks to Norbert Kamenicky) + Add support for Samsung SyncMaster 204B (Thanks to Arno Lepisk and Evan Innis) + Add support for Compaq P1100 (Thanks to Janne Himanka) + Improve LG LCD entry (Thanks to Evgeny Stambulchik). + Add support for Samsung SyncMaster 753V (thanks to Luis Augusto Perles) + Add support for LG Flatron L1952HM (thanks to Evgeny Stambulchik) - Update Polish translation, thanks to Jakub Bogusz. |
From: Roberto C. S. <ro...@co...> - 2006-10-12 23:38:24
|
Nicolas et. al., I was wondering when the next release might be made. There was a recent flurry of activity in CVS adding many new monitors. I ask because Debian Etch will go into freeze before the end of the month. Once that happens, it will be difficult to get updated packages in. I would like to see Etch release with the latest possible version of ddccontrol and ddccontrol-db. Regards, -Roberto --=20 Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com |
From: Roberto C. S. <ro...@co...> - 2006-09-29 14:02:48
|
On Fri, Sep 29, 2006 at 08:34:55PM +0800, Nicolas Boichat wrote: >=20 > So, I would recommend that you restrict the package to x86 and amd64,=20 > which have been fully tested. >=20 OK. I will prepare a new upload soon. Regards, -Roberto --=20 Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com |
From: Nicolas B. <ni...@bo...> - 2006-09-29 12:35:34
|
Hi Roberto, alpha and ia64 archs have never been tested, so I cannot give any warranty whether it will work, or not... ddcpci (the part that causes some problems to build on some archs) use at least one x86-specific function (ioperm), so I don't think this part of the code will work on alpha and ia64. So, I would recommend that you restrict the package to x86 and amd64, which have been fully tested. Best regards, Nicolas |
From: Roberto C. S. <ro...@co...> - 2006-09-25 13:37:15
|
Nicolas et al, I wanted to make sure that I get this right before I prepare a new upload of the ddccontrol package for Debian. Based on the Debian buildd reports [0] [1], it appears that the package has successfully build for alpha, amd64, i386 and ia64. It is still waiting to be built on arm, but I am not sure if that will succeed. The builds on hppa, m68k, mips, mipsel, powerpc and s390 all failed for lack of a sys/io.h file. If you are comfortable that ddccontrol will work on alpha, amd64, i386 and ia64, I will prepare the new upload which restricts the package to those arches. Please let me know your thoughts on this. Regards, -Roberto [0] http://buildd.debian.org/build.php?&pkg=3Dddccontrol [1] http://people.debian.org/~igloo/status.php?email=3Droberto%40familiasanchez= =2Enet --=20 Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com |
From: Nicolas B. <ni...@bo...> - 2006-09-15 03:37:48
|
Hi Roberto, Roberto C. Sanchez wrote: > package ddccontrol > tags 386235 upstream > forwarded 386235 ddc...@li... > forwarded 385812 ddc...@li... > thanks > > > Two bugs have been reported against the recently uploaded Debian > packages: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385812 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386235 > > The first bug is a FTBFS bug. Apparently the IBM s390 architecture does > not have a sys/io.h file. I talked with some Debian developers on IRC > about it and it was recommended that I figure out which architectures > ddccontrol should work with and restrict the Debian package to those. I > am guessing that at a minimum, i386, amd64, ia64, powerpc, and powerpc64 > should be supported. If there are others, please let me know. > The only archs that have been tested are amd64 and x86. I'm quite sure ia64, ppc and ppc64 will not compile as is, and, anyway, all these architectures are only of little use to the end-user, which is the target of ddccontrol : ia64 is only meant for servers, ppc and ppc64 are almost dead for end-users, as Apple switched to Intel (if someone with an "old" mac wants to do the job to try to compile it, I'd of course accept a patch). > The second bug appears to be the result of trying to load a non-existent > file. The file, /usr/share/ddccontrol-db/monitor/SNY03A0.xml, does not > exist in the ddccontrol-db sources. Is this an oversight? > This is not a bug, the monitor does not support DDC/CI. I'll answer directly on debian bugs. Thanks for forwarding bugs. Best regards, Nicolas |
From: Roberto C. S. <ro...@co...> - 2006-09-15 02:33:27
|
package ddccontrol tags 386235 upstream forwarded 386235 ddc...@li... forwarded 385812 ddc...@li... thanks Two bugs have been reported against the recently uploaded Debian packages: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D385812 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D386235 The first bug is a FTBFS bug. Apparently the IBM s390 architecture does not have a sys/io.h file. I talked with some Debian developers on IRC about it and it was recommended that I figure out which architectures ddccontrol should work with and restrict the Debian package to those. I am guessing that at a minimum, i386, amd64, ia64, powerpc, and powerpc64 should be supported. If there are others, please let me know. The second bug appears to be the result of trying to load a non-existent file. The file, /usr/share/ddccontrol-db/monitor/SNY03A0.xml, does not exist in the ddccontrol-db sources. Is this an oversight? Regards, -Roberto --=20 Roberto C. Sanchez http://familiasanchez.net/~roberto |
From: Nicolas B. <ni...@bo...> - 2006-08-29 11:07:31
|
Hello, Jakub Bogusz wrote: > Hello, > > I updated Polish translations for ddccontrol 0.4.2 and ddccontrol-db > 20060730. As I can see CVS contains the same code, so these versions are > still up to date. > Updated pl.po files can be get from: > > http://qboosh.cs.net.pl/pl.po/ddccontrol-0.4.2.pl.po > http://qboosh.cs.net.pl/pl.po/ddccontrol-db-20060730.pl.po > > Could you commit them to CVS? > Done, thanks a lot. May I recontact you before I release the next version (probably not before June 2007...), so you can update the files ? (I can give you a CVS access if you prefer). > BTW: translation guide for ddccontrol[1] contains link to bacula-devel list > - isn't it some copy-pasto? > > [1] http://ddccontrol.sourceforge.net/doc/latest/ape.html#translator No no, I wanted you to send the files to bacula-devel .-) But my personnal address is fine too ! Best regards, Nicolas |
From: Nicolas B. <ni...@bo...> - 2006-08-29 10:44:51
|
Hello, Have you tried to run ddccontrol, and then have a look at the code ? You may also be interested in the tool parseedid. Best regards, Nicolas Martin Owens wrote: > Hey all, > > I want to learn more about monitor detection via DDC. I've had a look > around and you guys seem like the best people to ask. > > I'm developing a hardware tool and I'd like it to be able to detect or > get information relating to any monitors pluged in. > > Best Regards, Martin Owens > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > ------------------------------------------------------------------------ > > _______________________________________________ > ddccontrol-devel mailing list > ddc...@li... > https://lists.sourceforge.net/lists/listinfo/ddccontrol-devel > |
From: Martin O. <doc...@gm...> - 2006-08-17 15:59:09
|
Hey all, I want to learn more about monitor detection via DDC. I've had a look around and you guys seem like the best people to ask. I'm developing a hardware tool and I'd like it to be able to detect or get information relating to any monitors pluged in. Best Regards, Martin Owens |
From: Nicolas B. <ni...@bo...> - 2006-08-15 02:53:28
|
Hi, Roberto C. Sanchez wrote: > Hello, > > The Debian packages I have prepared have been uploaded and are now > awaiting processing by the ftp maspters as they are new packages: > > http://ftp-master.debian.org/new.html > Great, thanks for your work. Please keep me informed of the progress, and tell me if you need any support (for example if people start a flame war about that-should-be-in-the-kernel, that-should-be-in-Xorg, etc..., as I have seen in one of the thread about ddccontrol on debian lists). Thanks, Nicolas |
From: Roberto C. S. <ro...@fa...> - 2006-08-11 23:12:24
|
Hello, The Debian packages I have prepared have been uploaded and are now awaiting processing by the ftp maspters as they are new packages: http://ftp-master.debian.org/new.html It looks like the general freeze for Etch will be near the end of October. Once that occurs, whatever version is in Debian at that time will be the version which ships with the next release. Regards, -Roberto --=20 Roberto C. Sanchez http://familiasanchez.net/~roberto |
From: Nicolas B. <ni...@bo...> - 2006-08-05 11:48:32
|
Third try to send this message... Maybe it got marked as spam by SF filters... Nicolas Boichat wrote: > Looks like this message has not been sent correctly... (Or SF lists have > serious problems...) > >> Hi all, >> >> I just released DDCcontrol version 0.4.2, and ddccontrol-db version >> 20060730 (changes below). Thanks to all the people who helped (quite a >> lot!), particularly Roberto Sanchez: I hope a Debian package will give a >> new start to the projet, bringing more developers (I feel alone >> sometimes .-)), and translators (that's something we really need). >> >> This will probably be the last release of ddccontrol (the application >> package) until about 1 year, as I am now in university exchange >> in Singapore (NUS) until June 2007: I won't be able to develop new >> features, as I won't have a monitor to control (I recently bought a >> laptop, and didn't travel with my monitors .-)). However, I'll still >> create new monitor profiles, and do 2 or 3 database releases if there >> are enough new reports (and if I have enough time). >> >> Of course, if somebody implements interesting new features, I'll try to >> release a new version of ddccontrol, in this case I'll need the user >> base (i.e. you .-)) to test the new features, report and fix bugs, as I >> won't be able to do it myself. >> >> Thanks, >> >> Best regards, >> >> Nicolas >> >> Version 0.4.2 - 2006-07-30 >> - Allow binary data in CAPS. >> - Add more I2C busses to Intel 810-like chips. >> - Fix gcc 4.0 and 4.1 compilation warnings. >> - Added manual pages. >> >> Version 20060730: >> - Add support for new monitors: >> + SGI GDM-5011P and GDM-5411 (Thanks to Florin Andrei) >> + Samsung SyncMaster 173P+ (DVI) (Thanks to KRZYzaK) >> + Samsung SyncMaster 797mb (Thanks to Evgeniy) >> + Samsung SyncMaster 720T (Thanks to Piotr) >> + Dell 2005FPW (Thanks to Christian Abegg) >> + Philips 170C6 (Thanks to Dmitry Artamonow) >> + Samsung SyncMaster 173s (Thanks to Artur Flinta) >> + Samsung SyncMaster 940B (Thanks to Jörg Evers) >> + Philips 200P6 (Thanks to podolany). >> + Samsung SyncMaster 215TW (thanks to David R Mulligan). >> + Sony SDM-S205K, and generic profile for Sony LCD monitors (thanks >> to lardhan) >> + Samsung Syncmaster 760BF VGA (thanks to John Kent). >> >> >> >> |
From: Nicolas B. <ni...@bo...> - 2006-07-30 17:13:37
|
Roberto C. Sanchez wrote: > Nicolas and company, > > I apologize for the delay, No problem .-) > but all the changes I need are now committed. > Thanks for your patience and understanding. > Thanks, I'll release the next version later today. Best regards, Nicolas |
From: Nicolas B. <ni...@bo...> - 2006-07-30 17:10:35
|
Hi Will, William Hollingworth wrote: > Hi Nicolas > > Thanks for testing this. I should have followed up and told you that > I also eventually tried this and it works OK. So that is good news. > Yes that's really good news .-) > I can ask my contacts in ATI engineering about supporting the > "/dev/i2c-" interface in their drivers. Is it the same as Nvidia in > that their proprietary drivers don't support it at all? Do they have > any kind of interface for controlling all of the extra goodies on > their boards with their drivers? I've never looked at their > proprietary drivers. > That would be really great if you could ask ATI to add /dev/i2c-* support (maybe they have other kind of interface, I don't know either, but I'm sure they do not support standard /dev/i2c-* devices). If ATI does so, I could imagine disabling ddcpci by default, which would probably speed up ddccontrol load time. Best regards, Nicolas |
From: Roberto C. S. <ro...@fa...> - 2006-07-27 13:38:35
|
Since there is already html documentation available within ddccontrol, I am going to keep the manual page simple and just place one that refers the user to the location of the html documentation. I will commit it later this afternoon (US Eastern time). -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto |
From: Roberto C. S. <ro...@fa...> - 2006-07-26 22:09:43
|
Nicolas and company, I apologize for the delay, but all the changes I need are now committed. Thanks for your patience and understanding. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto |
From: William H. <wi...@ai...> - 2006-07-25 15:20:39
|
Hi Nicolas Thanks for testing this. I should have followed up and told you that I also eventually tried this and it works OK. So that is good news. I can ask my contacts in ATI engineering about supporting the "/dev/i2c-" interface in their drivers. Is it the same as Nvidia in that their proprietary drivers don't support it at all? Do they have any kind of interface for controlling all of the extra goodies on their boards with their drivers? I've never looked at their proprietary drivers. Thanks Will At 11:11 AM 7/22/2006, Nicolas Boichat wrote: >Hi Will, > >William Hollingworth wrote: > > Hi Nicolas > > > > I was just forwarded this link to some updated documentation from Nvidia. > > > > > http://download.nvidia.com/XFree86/Linux-x86_64/1.0-8762/README/appendix-z.html > > > > From what I understand from this, it seems to mean they are now > > supporting the "/dev" interface method for DDC/CI. What do you think? > > > > If this is true, then it would no longer be necessary to use the PCI > > interface method if you didn't want to - right? > > > > Has anyone actually tried their latest drivers to see if if this > > works? I haven't had chance yet. > > >I finally found the time to try this, and it works fine. I'll update the >documentation. > >I wish every binary drivers supported this interface (for example, ATI >doesn't), so we could drop direct pci interface method (which is a nice >workaround, but has nothing to do in a userspace program). > >Best regards, > >Nicolas > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys -- and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >_______________________________________________ >ddccontrol-devel mailing list >ddc...@li... >https://lists.sourceforge.net/lists/listinfo/ddccontrol-devel |
From: Nicolas B. <ni...@bo...> - 2006-07-22 16:41:20
|
Thunderbird crashed just after I sent the message, so I think it was not delivered successfully... Here is my previous message: Nicolas Boichat wrote: > Hi Will, > > William Hollingworth wrote: > >> Hi Nicolas >> >> I was just forwarded this link to some updated documentation from Nvidia. >> >> http://download.nvidia.com/XFree86/Linux-x86_64/1.0-8762/README/appendix-z.html >> >> From what I understand from this, it seems to mean they are now >> supporting the "/dev" interface method for DDC/CI. What do you think? >> >> If this is true, then it would no longer be necessary to use the PCI >> interface method if you didn't want to - right? >> >> Has anyone actually tried their latest drivers to see if if this >> works? I haven't had chance yet. >> >> > I finally found the time to try this, and it works fine. I'll update the > documentation. > > I wish every binary drivers supported this interface (for example, ATI > doesn't), so we could drop direct pci interface method (which is a nice > workaround, but has nothing to do in a userspace program). > > Best regards, > > Nicolas > > |
From: Nicolas B. <ni...@bo...> - 2006-07-22 16:11:55
|
Hi Will, William Hollingworth wrote: > Hi Nicolas > > I was just forwarded this link to some updated documentation from Nvidia. > > http://download.nvidia.com/XFree86/Linux-x86_64/1.0-8762/README/appendix-z.html > > From what I understand from this, it seems to mean they are now > supporting the "/dev" interface method for DDC/CI. What do you think? > > If this is true, then it would no longer be necessary to use the PCI > interface method if you didn't want to - right? > > Has anyone actually tried their latest drivers to see if if this > works? I haven't had chance yet. > I finally found the time to try this, and it works fine. I'll update the documentation. I wish every binary drivers supported this interface (for example, ATI doesn't), so we could drop direct pci interface method (which is a nice workaround, but has nothing to do in a userspace program). Best regards, Nicolas |
From: Nicolas B. <ni...@bo...> - 2006-06-25 19:58:20
|
Roberto C. Sanchez wrote: > Quoting Nicolas Boichat <ni...@bo...>: > > >> Hello, >> >> Roberto Sanchez wrote: >> >>> Nicolas Boichat wrote: >>> >>>> ddccontrol builds fine, without warning, with gcc-4.1.1 (gentoo). >>>> >>>> >>> OK. Just so that I am clear, are you referring to the CVS version? >>> If I recall correctly, the most recent release only builds clean with >>> gcc 3.4. >>> >> Yes you're right. The last release builds with 4.0, but with a lot of >> warnings. I'll try to release ddccontrol 0.5 as soon as I can. >> >> > > OK. Is there a way I can have a week or two to write the man pages? > That way they can be included in the next release? > No problem. I plan to release the next version around July 25. Best regards, Nicolas |
From: William H. <wi...@ai...> - 2006-06-21 23:50:28
|
Hi Nicolas I was just forwarded this link to some updated documentation from Nvidia. http://download.nvidia.com/XFree86/Linux-x86_64/1.0-8762/README/appendix-z.html From what I understand from this, it seems to mean they are now supporting the "/dev" interface method for DDC/CI. What do you think? If this is true, then it would no longer be necessary to use the PCI interface method if you didn't want to - right? Has anyone actually tried their latest drivers to see if if this works? I haven't had chance yet. Thanks Will |
From: Roberto C. S. <ro...@fa...> - 2006-06-21 21:49:18
|
Quoting Nicolas Boichat <ni...@bo...>: > Hello, > > Roberto Sanchez wrote: >> Nicolas Boichat wrote: >>> >>> ddccontrol builds fine, without warning, with gcc-4.1.1 (gentoo). >>> >> >> OK. Just so that I am clear, are you referring to the CVS version? >> If I recall correctly, the most recent release only builds clean with >> gcc 3.4. > Yes you're right. The last release builds with 4.0, but with a lot of > warnings. I'll try to release ddccontrol 0.5 as soon as I can. > OK. Is there a way I can have a week or two to write the man pages? That way they can be included in the next release? -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto |
From: Nicolas B. <ni...@bo...> - 2006-06-21 06:33:03
|
Hi David, Please don't forget to cc the devel list .-) David R Mulligan wrote: > Nicolas, > > Seems the mistake came from Philips. When looking at your recent cvs > changes I just assumed the missing < and ) characters were were human > error on your part rather than manufacturer. Forgive me if this is > absurd for you due to attention to detail or testing :) > I just forgot to run "make check-db" before committing the files (this does some integrity check)... Anyway, running this command is in my checklist before releasing a new version of the database, so I couldn't release the db with this mistake. > Another absurd question... Has anyone contacted Samsung and the others > about the DDC/CI capabilities of all of their monitors? I doubt it but > they might be happy to provide specs and command lists. > I contacted many manufacturers, and I have (very) good contacts at NEC-Mitsubishi and Fujitsu-Siemens. I've been unable to contact the right person at Samsung. > I should look at the ddccontrol code. I want to work on something > outside of work and maybe even try to remember c/c++. Its embarrassing > but I've been writing in java for so long that I cannot remember a lot. > It took me a while to remember what the -> operator did!! :( That's something I fully understand, I constantly switch between these 3 languages, sometimes I write printf in Java .-) > As I > mentioned in the past I would love to get ddccontrol and synergy talking > to each other. > Whatever you can do will always be greatly appreciated .-) Thanks, Best regards, Nicolas > On Tue, 2006-20-06 at 22:44 +0200, Nicolas Boichat wrote: > >> Hi, >> >> David R Mulligan wrote: >> >>> I was wondering if these files could be auto-generated, tweaked and then >>> submitted. It seems that the output of the ddccontrol util is taken at >>> face value for the first version so why can't it be used to generate a >>> test xml file? Perhaps it could be done with some interaction from the >>> user? >>> >> That's something I thought about, but unfortunately I think it is too >> complicated to do. xml files are not very complicated to create, but it >> needs some intelligence and experience about how DDC/CI works (or >> doesn't work), which a computer program cannot provide. For example, >> these are things I've done to create the database: >> - Google, ask if the monitor is a LCD or a CRT (so I don't define absurd >> controls like "pincushion" for LCDs) >> - see that there is a missing parenthesis in monitor caps (Philips) >> - see that a monitor reports strange values for some controls, so ask >> the user if the controls really works (like the Samsung 215tw) >> - create CAPS manually for an old monitor only supporting DDC/CI >> partially (Samsung 173s) >> - see that some controls are useful, but not in CAPS (very common for >> Samsung) >> - ask NEC-Mitsubishi / Fujistu-Siemens about the missing controls (I >> have contact with these two manufacturer) >> - etc... >> >> xml-file creation has also been really simplified with the introduction >> of generic profiles, it is also less important to have full support for >> monitor as the user, without having a specific file for his monitor, >> already has basic support (like brightness, which is probably the most >> wanted control .-)). >> >> >>> Part of why I am asking is the because of the mistakes made in some of >>> the recent xml files >>> >> What mistakes ? Please tell me and I would be happy to fix these. >> >> >>> as well as the fact that I am sure Nicolas would >>> like some of his time back to do more interesting things than to parse >>> the monitor capability output text to generate xml definition files :) >>> >> Of course I would like to do something else, but unfortunately, nothing >> is simple with the monitors: controls are far from standard, and even >> for a specific manufacturer, the same control sometimes behaves >> differently (look at SAMlcd.xml for example), and a lot of monitors are >> buggy. >> >> If I had time, I would like to do some work on gddccontrol (add more >> full screen patterns for example), add support for read-only controls in >> the database (to support rotation for example), allow better integration >> with scripts, etc... I will post a topic about the future of the project >> in a few weeks, as I probably won't work on it until June 2007. The only >> thing I will do during the next 12 months is the creation of XML files. >> >> Of course, if you want to create a tool to generate xml files, feel free >> .-), as long as it doesn't require more work to fix mistakes introduced >> by an automatic program that it would with manual xml file creation. >> (but I think that if you have time there are more interesting work to do >> on ddccontrol .-)) >> >> Best regards, >> >> Nicolas >> >> > > |
From: Nicolas B. <ni...@bo...> - 2006-06-21 06:23:58
|
Hello, Roberto Sanchez wrote: > Nicolas Boichat wrote: >> >> ddccontrol builds fine, without warning, with gcc-4.1.1 (gentoo). >> > > OK. Just so that I am clear, are you referring to the CVS version? > If I recall correctly, the most recent release only builds clean with > gcc 3.4. Yes you're right. The last release builds with 4.0, but with a lot of warnings. I'll try to release ddccontrol 0.5 as soon as I can. Best regards, Nicolas |