[Lcdproc] CFontz633 or CFontzPacket... + Temp on CF631 and CF635 Re: [Lcdproc]
Cfontz fan temp
David GLAUDE
dglaudemailing@gmx.net
Tue May 9 12:00:03 2006
Hello,
I would like the latest news on:
"Should the owner of a CF633 use CFontz633 or CFontzPacket?"
Also specifically about the CF631 and CF635:
"Are the Fan, Temp and other additional feature supported by your 'fan
temp' version?"
I guess my question to Steward W. Putnam is:
"I think you did work on CFontz633 module, this mean owner of CF631 and
CF635 will not benefit from it."
And my questions to Peter Marschall are:
"Do you have the additional module for the CF631 and CF635 and did you
investigate supporting some of those feature in CFontzPacket?"
"Did you look at Steward modification for fan support?"
David GLAUDE
PS: My recent interest in CF screen is a very strange thing to me too.
PPS: My CF631 does not support external module since it is release
1.0/1.0 ... but I have a CF633 and 4 temp sensor (and maybe a few fan).
Stewart W. Putnam wrote:
> I put up another revison of my fan / temperature / system performance
> project on the CrystalFontz board:
>
> http://www.crystalfontz.com/forum/showthread.php?s=&threadid=3019
>
> I'd like to thank Jannis Achstetter on the list here for an example
> of how to read the hddtemp daemon. ( Aside; I own only one hard drive
> that hddtemp can read, so I my implementation might be broken for
> reading multiple drives. )
>
> Frow the start my interest in in the Crystalfontz's Dallas / MaximIC
> has been off the main focus of LCD ( "oh, the temperature driven fan
> manager has a display screen too? Neat." ) The packet send-receive
> round robin que system in multiple threads in shared memory for
> gauranteeing fan management is quite divergent. And the parts that most
> directly violate the lcdproc plan by spawning a socket screen client
> with access to the Driver * and writing directly to struct widget->text
> are all bracketed by #ifdef <>#endif, for what it's worth ;)
>
> That much said ... anyone from here who finds something broken in it
> please let me know.
>
> Stewart Putnam
> _______________________________________________
> LCDproc mailing list
> LCDproc@lists.omnipotent.net
> http://lists.omnipotent.net/mailman/listinfo/lcdproc
>
>