headers
Chuck Silvers | 19 Jan 2005 17:53
Favicon

which connector for SCSI?

hi,

I borrowed jason's pc532 so that I could work on fixing the cf_unit abuse
in several machine-specific drivers, and now I want to hook up a disk.

I see two sets of pins that look like the right thing physically:
CONN1 (away from everything else, near the edge of the board) and
CONN16 (next to the ISA-looking connectors that reportedly are really SCSI).
the CONN1 one is also labelled "Disk & Tape".

so just to be sure about what I'm doing here, I can plug a normal
internal-SCSI 50-pin cable into one of sets of pins above, right?
does it matter which one?

-Chuck
Permalink | Reply | 17 comments |
headers
Phil Budne | 19 Jan 2005 18:57
Favicon

Re: which connector for SCSI?

The one labeled "disk & tape" goes to the adaptek(?)
chip, which never had a working driver.  You want
the connector near the "ISA" slots (which carry
SCSI signals), which goes to an NCR chip.

phil
Permalink | Reply | 3 comments |
headers
Jason Thorpe | 22 Jan 2005 22:19

Re: which connector for SCSI?


On Jan 19, 2005, at 9:57 AM, Phil Budne wrote:

> The one labeled "disk & tape" goes to the adaptek(?)
> chip, which never had a working driver.

There is a Mach driver for this chip, I believe.  I have the PC532 Mach 
sources laying around.  Maybe Chuq feels like writing a SCSI driver :-)

         -- Jason R. Thorpe <thorpej <at> shagadelic.org>
Permalink | Reply | 1 comment |
headers
Simon Burge | 23 Jan 2005 01:35

Re: which connector for SCSI?

Hi Chuck,

On Wed, Jan 19, 2005 at 08:53:36AM -0800, Chuck Silvers wrote:

> I borrowed jason's pc532 so that I could work on fixing the cf_unit abuse
> in several machine-specific drivers, and now I want to hook up a disk.

For a userland, it's probably easiest to start with the 1.5.3 release.
-current source can build most programs with a couple of provisos:

  - Pthreads don't build.
  - A handful of programs trip over gcc errors.
  - Lint isn't happy in places.  Sprinkle -k or MKLINT=no
  - Only static linking works.

I think the only programs you really need to use a -current kernel are
fsck_ffs and sysctl.  Maybe vmstat too if you want to use that.

Let me know if you have any hassles.

> [ scsi question has already been answered here ]

Cheers,
Simon.
--
Simon Burge                                   <simonb <at> wasabisystems.com>
NetBSD Development, Support and Service:   http://www.wasabisystems.com/
Permalink | Reply | 16 comments |
headers
Chuck Silvers | 23 Jan 2005 01:43
Favicon

Re: which connector for SCSI?

On Wed, Jan 19, 2005 at 12:57:32PM -0500, Phil Budne wrote:
> The one labeled "disk & tape" goes to the adaptek(?)
> chip, which never had a working driver.  You want
> the connector near the "ISA" slots (which carry
> SCSI signals), which goes to an NCR chip.

ok, thanks.  now I just need to figure out which way is up on the cable.  :-)

-Chuck
Permalink | Reply | 0 comments |
headers
Chuck Silvers | 23 Jan 2005 01:45
Favicon

Re: which connector for SCSI?

On Sat, Jan 22, 2005 at 01:19:52PM -0800, Jason Thorpe wrote:
> 
> On Jan 19, 2005, at 9:57 AM, Phil Budne wrote:
> 
> >The one labeled "disk & tape" goes to the adaptek(?)
> >chip, which never had a working driver.
> 
> There is a Mach driver for this chip, I believe.  I have the PC532 Mach 
> sources laying around.  Maybe Chuq feels like writing a SCSI driver :-)

that does sound interesting.  send me the mach stuff and I'll add it to
my ever-growing list of stuff I'd like to do.

-Chuck
Permalink | Reply | 0 comments |
headers
Chuck Silvers | 23 Jan 2005 01:46
Favicon

Re: which connector for SCSI?

On Sun, Jan 23, 2005 at 11:35:07AM +1100, Simon Burge wrote:
> Hi Chuck,
> 
> On Wed, Jan 19, 2005 at 08:53:36AM -0800, Chuck Silvers wrote:
> 
> > I borrowed jason's pc532 so that I could work on fixing the cf_unit abuse
> > in several machine-specific drivers, and now I want to hook up a disk.
> 
> For a userland, it's probably easiest to start with the 1.5.3 release.
> -current source can build most programs with a couple of provisos:
> 
>   - Pthreads don't build.
>   - A handful of programs trip over gcc errors.
>   - Lint isn't happy in places.  Sprinkle -k or MKLINT=no
>   - Only static linking works.
> 
> I think the only programs you really need to use a -current kernel are
> fsck_ffs and sysctl.  Maybe vmstat too if you want to use that.
> 
> Let me know if you have any hassles.

hmm, actually would you mind sending me a disk image?
that'll save me a bunch of messing around.

-Chuck
Permalink | Reply | 0 comments |

Gmane