9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 53c895 failed to INIT
Date: Fri, 28 Jul 2000 11:32:27 +0100	[thread overview]
Message-ID: <E13I7NM-000EMb-0Y@anchor-post-34.mail.demon.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 605 bytes --]

There is a problem with taking this approach, as I have already noted.

Time for some more detail. 

The 895 is capable of Ultra2 transfers. To do this it has a 4x clock multiplier,
not a 2x clock multiplier. Your settings pretend the 895 only has a 2x multiplier.

If you use these settings, then when sending data
to the disk, it will be sent 2x faster the disk expects. This may be OK, because
disks are often over specified, but it is risky for a fileserver.

If you wait a short time, I will post a modified version of scsincr53c8xx.c which
is better for you. Not perfect, but better.


[-- Attachment #2: Type: message/rfc822, Size: 2619 bytes --]

From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 53c895 failed to INIT
Date: Fri, 28 Jul 2000 06:08:07 -0400 (EDT)
Message-ID: <200007281008.GAA12337@cse.psu.edu>

Hello,

We can find the line:
#define SYM_895_DID	0x000c
in scsincr53c8xx.c. However it seems this is not used
anywhere.

We can also find following lines bellow the line.

{ SYM_875_DID,   0x01, "SYM53C875r1",	Burst128, 16, Prefetch|LocalRAM|BigFifo|Differential|Wide|Ultra },
{ SYM_875_DID,   0xff, "SYM53C875",	Burst128, 16, Prefetch|LocalRAM|BigFifo|Differential|Wide|Ultra|ClockDouble },
{ SYM_885_DID,   0xff, "SYM53C885",	Burst128, 16, Prefetch|LocalRAM|BigFifo|Wide|Ultra|ClockDouble },
{ SYM_896_DID,   0xff, "SYM53C896",	Burst128, 16, Prefetch|LocalRAM|BigFifo|Wide|Ultra|ClockDouble },

SYS53C895 does not apear here.
Therefore init fails.

Does it mean SYS53C895 is not supported?

I added entry:
{ SYM_895_DID,   0xff, "SYM53C895",	Burst128, 16, Prefetch|LocalRAM|BigFifo|Wide|Ultra|ClockDouble },
and ran 9pcfs (based on emelie), then I reached "config:" message without
error message.

now I am formatting....
I will report the result.

Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp

             reply	other threads:[~2000-07-28 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-28 10:32 nigel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-28 10:08 arisawa
2000-07-28  8:36 nigel
2000-07-28  5:21 arisawa
2000-07-27  6:24 nigel
2000-07-27  6:01 arisawa

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=E13I7NM-000EMb-0Y@anchor-post-34.mail.demon.net \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /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).