Subject: Re: ncr53cxxx driver design issues
To: Manuel Bouyer <email@example.com>
From: Jonathan Stone <jonathan@DSG.Stanford.EDU>
Date: 04/20/2000 18:48:24
In message <20000420164422.A1433@antioche.lip6.fr>Manuel Bouyer writes
>On Thu, Apr 20, 2000 at 12:17:03AM -0700, Jonathan Stone wrote:
>> "siop" strikes me as a bad name. It's too generic: lots of other
>> vendors could describe their hardware with the same name. Or even
>> other NCR chips.
>I don't have my doncs handy but I think 'script I/O processor' is a trademark
>or something like that. I'm not sure other vendors could use it.
>Also the symbios docs explicitely name the 53c7xx/53c8xx chips as this,
>so I guess they would chose another name for a different line of products.
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).
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
>> 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
it's a great name... what do Solaris, OSF1/DU/Tru64 use?