Return to BSD News archive
Xref: sserve comp.sys.ibm.pc.hardware:33466 comp.unix.bsd:6554
Newsgroups: comp.sys.ibm.pc.hardware,comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!sol.ctr.columbia.edu!hamblin.math.byu.edu!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Question on Diamond Clock Synthesizer
Message-ID: <1992Oct14.033731.28397@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Reply-To: terry@icarus.weber.edu
Organization: University of Utah Computer Center
References: <1992Oct11.045446.1020@fcom.cc.utah.edu> <Bvy0H3.Lwq@mudos.ann-arbor.mi.us> <1992Oct13.050754.4113@sinkhole.unf.edu> <1992Oct13.175214.19534@fcom.cc.utah.edu> <1bfp2oINNn4a@maverick.ksu.ksu.edu>
Date: Wed, 14 Oct 92 03:37:31 GMT
Lines: 40
In article <1bfp2oINNn4a@maverick.ksu.ksu.edu>, brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:
|> In <1992Oct13.175214.19534@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
|>
|> >Wrong reason. The reason was legal. There would be no more danger in a
|> >piece of code dealing with the video card than any other code dealing with
|> >a video card. The warnings you remember were from another post for some
|> >alpha VGA code (not the "Batman" code). Unfortunately, no one who has
|> >used the "Batman" code can sy whether or not there was a problem, since
|> >doing so could be admitting a violation of the trade secrets act if Diamond
|> >wanted to prosecute.
|>
|> That's rediculous. You can't be held liable for leaking a trade secret
|> if you never signed a non-disclosure agreement. If I want to use that
|> code, or tell other people about that code, that is fine. The original
|> author of the code could be held liable, but no one else. I never signed
|> anything, so there isn't anything legal that they can do to me about it.
Ever here the term "accessory after the fact"? Besides, I was referring to
the danger to the original poster or to someone including it in a "product"
(like XFree86).
All this is now totally beside the point: I now have it on good authority
that the original code posting was either accidently or maliciously "doctored"
to set the clock at the highest possible value -- and "If someone compiles
that code thinking that it will set up the clocks for him, his monitor will
likely go 'pop'". Unless you modify the code and the constant timing
parameters, I suggest you not use the code under any circumstances.
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------