From: "Gérard Roudier" <groudier@free.fr>
To: Justin Guyett <justin@soze.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Are we going too fast?
Date: Mon, 13 Aug 2001 18:54:26 +0200 (CEST) [thread overview]
Message-ID: <20010813175724.T666-100000@gerard> (raw)
In-Reply-To: <Pine.LNX.4.33.0108130327460.27721-100000@kobayashi.soze.net>
On Mon, 13 Aug 2001, Justin Guyett wrote:
> On Mon, 13 Aug 2001, Gérard Roudier wrote:
>
> > You may want to elaborate on the ncr53c8xx problems (I maintain this
> > driver). More generally, you must not ignore the thousands of bugs in the
> > hardware you are using, but software developpers haven't access to all
> > errata descriptions since hardware vendors donnot like to make this
> > information freely available.
>
> I've got a quick unrelated question.
>
> Why not change the name (or at least the description) of sym53c8xx to
> include the 53c1010 chips, which this driver seems to work on (and on a
> SMP box, no less)?
I have an SMP box and a C1010 chip. I like the 'way' this hardware
combination 'seems' to work for me. :-)
About the driver name, I have changed it to just 'sym' for the port to
FreeBSD. Software modules are usually named using a short name under this
O/S. At the time I did the port, LSI had bought SYMBIOS, but they seemed
to want to keep with SYMBIOS name for the 53C8XX PCI-SCSI family.
Then they (LSI) invented the 53C1010, called it LSI53C1010 and designed it
in a way that made possible to use a single driver for the SYM53C8xx
series (NCR+SYMBIOS) and this one.
The current LSI53C10xx family consists in 2 different architectures that
require 2 different software drivers:
- [PCI host interface + SCSI Ultra-160 interface + SCSI scripts
processor] that are supported by the sym53c8xx driver, the
derivated 'sym' under FreeBSD and the latest SYM-2 (derived from sym)
that wants to be portable.
- [PCI/X host interface + SCSI Ultra-320 interface + ARM based IO
processor] that requires a new driver. I heared that LSILOGIC want to
provide a driver for Linux. Note that the LSI FC controllers and those
ones should possibly share the same software drivers.
Then, what better name for the sym53c8xx driver?
- sym has been obsoleted by lsi.
- sym53c8,10xx is confusing, given the 10xx family weirdness (see above).
- lsi is too vague a name, given the numerous chips supplied by LSI.
- siop (SCSI IO PROCESSOR) is already used and looks to me more vague
than all other names that have ever been used for an HBA driver.:)
In my taste, sym53c8xx is still quite good name for the following reasons:
1) It is the SYMBIOS company that made the greatest development for the
53C8XX family, in my opinion.
2) The 53C10xx chips that can be driven by the sym* drivers use a 53C1010
core, even if then may be named 53C1000, etc..., for marketing reasons.
3) All future 53C10xx HBAs will probably be based on PCI/X + U320 + ARM
and so will not be supported by sym* (same for SIOP, btw).
Now, we could change everything that wants to describe this driver.
Here is my current one (from sym-2 that also supports NCR53C8xx chips):
* Device driver for the SYMBIOS/LSILOGIC 53C8XX and 53C1010 family
* of PCI-SCSI IO processors.
Just my 0.02 euro. :)
Gérard.
next prev parent reply other threads:[~2001-08-13 16:57 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 7:43 Are we going too fast? PinkFreud
2001-08-13 8:52 ` Brian
2001-08-13 8:55 ` Francois Romieu
2001-08-14 4:21 ` Pete Toscano
2001-08-14 12:48 ` Alan Cox
2001-08-14 13:03 ` usb-uhci + SMP -> bad Andre Pang
2001-08-14 16:01 ` Russell Cattelan
2001-08-14 22:30 ` Are we going too fast? Paul G. Allen
2001-08-13 10:03 ` Gérard Roudier
2001-08-13 10:29 ` Justin Guyett
2001-08-13 12:56 ` Andrzej Krzysztofowicz
2001-08-13 16:54 ` Gérard Roudier [this message]
2001-08-13 10:09 ` Chris Wilson
2001-08-13 11:09 ` szonyi calin
2001-08-13 13:11 ` Alan Cox
2001-08-14 18:51 ` Anders Larsen
2001-08-14 20:29 ` Anders Larsen
2001-08-13 13:46 ` hugang
2001-08-13 13:55 ` Anton Altaparmakov
2001-08-13 17:16 ` Stephen Satchell
2001-08-13 21:01 ` A warning (was: Re: Are we going too fast?) Nico Schottelius
2001-08-13 17:53 Are we going too fast? PinkFreud
2001-08-13 20:27 ` Gérard Roudier
2001-08-13 18:46 Per Jessen
2001-08-14 13:58 ` Andrew Scott
2001-08-14 19:54 ` David Ford
2001-08-13 18:53 Petr Vandrovec
[not found] <fa.l9dq0tv.7gqnhh@ifi.uio.no>
[not found] ` <fa.g70as7v.1722ipv@ifi.uio.no>
2001-08-13 19:14 ` John Weber
[not found] <no.id>
2001-08-13 20:24 ` Alan Cox
2001-08-13 21:06 ` Anthony Barbachan
2001-08-14 20:47 ` Alan Cox
2001-08-15 0:07 ` PinkFreud
2001-08-13 21:07 PinkFreud
2001-08-13 21:20 ` Alan Cox
2001-08-13 21:41 ` Rog�rio Brito
2001-08-14 0:56 ` Ben Ford
2001-08-14 7:34 ` Peter Wächtler
2001-08-14 2:24 ` David Ford
2001-08-14 4:19 ` Nicholas Knight
2001-08-14 12:49 ` Alan Cox
2001-08-14 22:27 ` Paul G. Allen
2001-08-13 21:36 PinkFreud
2001-08-14 7:57 ` Helge Hafting
2001-08-13 21:44 PinkFreud
2001-08-14 0:04 ` PinkFreud
2001-08-14 7:24 ` Francois Romieu
2001-08-15 23:24 ` Dr. Kelsey Hudson
2001-08-14 16:25 PinkFreud
2001-08-14 16:32 PinkFreud
2001-08-14 19:47 Per Jessen
2001-08-14 20:07 Per Jessen
2001-08-14 20:20 Per Jessen
2001-08-15 20:13 Roy Murphy
2001-08-16 21:42 PinkFreud
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=20010813175724.T666-100000@gerard \
--to=groudier@free.fr \
--cc=justin@soze.net \
--cc=linux-kernel@vger.kernel.org \
/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).