Subject: Re: ncr53cxxx driver design issues
To: Jonathan Stone <jonathan@DSG.Stanford.EDU>
From: Manuel Bouyer <firstname.lastname@example.org>
Date: 04/21/2000 11:26:40
On Thu, Apr 20, 2000 at 06:48:24PM -0700, Jonathan Stone wrote:
> Where I'm coming from is this: suppose I'm someone who *hasn't*
> perused the NCR spec sheets. I buy a a fancy new NCR or Symbios
> controller. What am I to look for as device name? Is the name "siop"
> mnemonic and meaningful and specific to *that* device? (We don't even
> seem to agree on what "siop" stands for, which isn't a good sign).
My fault, it's a typo.
> Will it be a natural name to people used to other Unices (free or
> For me, personally, the answer is a clear "no". It's a small point,
> but well-chosen names can be helpful; poorly-chosen ones are merely
I think naming drivers from the chip (or chip family) name is something
> >> How about nsp and ensp, as counter-proposals?
> >What does nsp stands for ?
> I was thinking _N_cr _S_CSI _p_rocessor, but I dont pretend
Hum, it's called symbios now :)
> it's a great name... what do Solaris, OSF1/DU/Tru64 use?
Don't know. Anyone with a solaris or DU machine with a NCR53x8xx controller in
Manuel Bouyer, LIP6, Universite Paris VI. Manuel.Bouyer@lip6.fr