Date: Tue, 21 Mar 1995 09:47:54 -0800 From: "Justin T. Gibbs" <gibbs@estienne.CS.Berkeley.EDU> To: Marino.Ladavac@aut.alcatel.at (Marino Ladavac) Cc: terry@cs.weber.edu (Terry Lambert), hackers@freefall.cdrom.com Subject: Re: Adaptec sequencer code (was: SVNET Meeting) Message-ID: <199503211747.JAA01653@estienne.cs.berkeley.edu> In-Reply-To: Your message of "Tue, 21 Mar 1995 16:40:25 %2B0100." <9503211541.AA07308@aut.alcatel.at>
next in thread | previous in thread | raw e-mail | index | archive | help
>Terry Lambert wrote: >> >> For the purposes of binary distribution, it ought to be easier to >> either get the sequencer code un-GPL'ed, rewrite it, or someone sign >> a non-disclosure with Adaptec and write a binary driver distributed >> soley as .o files. >> >> 8-|. >> > > Since the sequencer code is, as far as I could understand, > just a bunch of raw binary data, is it not itself basically > unreadable (bar disassembly) and as such non disclosing? > > I mean, knowing how they did program the sequencer is nice, > but do we really care that much, as long as it works? We care how they programmed the sequecer so we know how to communicate with it. The abstraction I chose in many of the features I implemented may be a far cry from how Adaptec did it. The sequencer and kernel code are very closely tied. You can't change one without affecting the other. > > I don't know about Adaptec's opinion on distributing only the > object format of the sequencer. Is that kosher? It would have to be a full driver from their HIM kit. > >/Alby > -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ==============================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503211747.JAA01653>