The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] What's with the DZ-11?
Date: Wed, 26 Nov 2014 17:08:02 -0500	[thread overview]
Message-ID: <51548394-0D23-4379-8B7F-4244D7BCB58F@ccc.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1411270742130.30791@aneurin.horsfall.org>

two issues.    first DEC subsetted the modem control lines so running modems - particularly when you wanted hardware flow control like the trailblazers - did not work. 

second as others pointed out there the buffering was mostly lacking and the interrupt load was terrible on the OS



if DEC had used different and better USARTs this would not have been as bad.  When it came out there were other options for the HW guys but IMO it was an example of tunnel vision - plus HW guys not really understanding the SW implications of the choice.  

one of the guys behind the DZ would later become a good friend of mine.  I realized Dave never looked at RS-232 the same way SW people did.   To Dave the DZ was great because it was two boards to do what he thought was the same thing as a DH - ie cheaper / less power / smaller etc. But the saving was a HW one and not what we needed.  


that said DEC sold a lot of them on VMS systems.  it was us UNIX guys that switched to Able's board as soon as we could.  Cheaper and better functionality for the OS.  

ken once told me he always loved us Unix guys because we got it.  he also listened too us and built what we needed when he could.  I tried to get him to put the DH/DM on a AT form factor but he said he could not make money at it.  Eventually the rocket port guys built and ASIC and pretty much did it

Clem 


> On Nov 26, 2014, at 3:48 PM, Dave Horsfall <dave at horsfall.org> wrote:
> 
> I've seen a couple of less than flattering references here; what was the 
> problem with them?
> 
> At UNSW, we couldn't afford the DH-11, so ended up with the crappy DJ-11 
> instead (the driver for the DH-11 had the guts ripped out of it in an 
> all-nighter by Ian Johnston as I recall), and when the DZ-11 came along we 
> thought it was the bees' knees.
> 
> Sure, the original driver was as slow as hell, but the aforesaid IanJ 
> reworked it and made it faster by at least 10x; amongst other things, I 
> think he did away with the character queues and used the buffer pool 
> instead, getting 9600 on all eight channels simultaneously, possibly even 
> full-duplex.
> 
> -- 
> Dave Horsfall DTM (VK2KFU)  "Bliss is a MacBook with a FreeBSD server."
> http://www.horsfall.org/spam.html (and check the home page whilst you're there)
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs



  parent reply	other threads:[~2014-11-26 22:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 20:48 Dave Horsfall
2014-11-26 21:39 ` Ronald Natalie
2014-11-26 22:08 ` Clem Cole [this message]
2014-11-27 19:45 ` Dave Horsfall
2014-11-27 20:55   ` Larry McVoy
2014-11-30  6:03   ` Warren Toomey
2014-11-30  6:43     ` Dave Horsfall
2014-11-30  7:03       ` Warren Toomey
2014-12-01  5:03         ` Dave Horsfall
2014-11-26 21:41 Noel Chiappa
2014-11-27 14:55 Noel Chiappa
2014-11-27 15:47 ` Ronald Natalie
2014-11-27 15:50 ` Ronald Natalie
2014-11-27 19:57 ` Dave Horsfall
2014-11-28 13:04   ` Ronald Natalie
2014-11-27 16:03 Noel Chiappa
2014-12-01 12:32 Noel Chiappa
2014-12-01 15:46 ` Warner Losh
2014-12-01 16:41   ` Clem Cole

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51548394-0D23-4379-8B7F-4244D7BCB58F@ccc.com \
    --to=clemc@ccc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).