Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!necntc!dandelion!ulowell!dino!miner
From: miner@dino.cpe.ulowell.edu (Rich Miner)
Newsgroups: comp.sys.amiga
Subject: Re: Autoconfig for expansions
Message-ID: <1936@dino.cpe.ulowell.edu>
Date: 24 Feb 88 00:46:20 GMT
References: <1408@sugar.UUCP> <507@xicom.UUCP> <2507@tekig4.TEK.COM>
Reply-To: miner@dino.cpe.ulowell.edu (Rich Miner)
Organization: University of Lowell
Lines: 20
Keywords: autoconfig hobby

In article <2507@tekig4.TEK.COM> brianr@tekig4.UUCP (Brian Rhodefer) writes:
>Here's a half-baked notion for dealing with the complexity of
>adding autoconfigurability to otherwise-simple peripheral cards:
       <Description of half-baked idea deleted>

The problem with your idea is that the Amiga auto-config is clean, 
elegant and easy to implement.   Anyone who is technically capable of
designing the hard disk controller you give as an example could add the
auto-config logic with no problem.   CBM provides very clean examples
for the auto-config circuit with their docs.   The EE students in
our lab have designed the auto-configuration glue into several 
boards; and it all worked the first time.   I think encouraging
non auto-configuring hardware is as punishable an offense as 
encouraging non multi-tasking software!





-- 
Rich miner@ulowell.edu  617/452-5000x2693  ULowell CPE Imaging Research Lab