From: "Ron Bianco" <ronb@junction.net>
To: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Using SCSI driver sym53c8xx.c - no nvram - no symbios BIOS
Date: Mon, 31 Jul 2000 16:24:52 -0700 [thread overview]
Message-ID: <000001bffb46$8756d300$4d012ac7@warp-speed> (raw)
Is anyone using a sym53c8xx family SCSI chip on their main board? i.e. not on a plugin
PCI card with extra stuff.
I'm using the 53c895.
If there is no NVRAM or SCSI biosROM, then does one have to tune the driver by modifying
some #define's ?
I know there is a few things that the driver will use from the pci setup code, and that
this driver supports kernel command line options, for some stuff. But I'd like to have a
proper default setup.
Right now I'm having trouble with ncr_getclock() which is calling ncrgetfreq(), always
reporting 0kHz. I'm tempted to just force it to 40000khz which is the freq. of the osc
connected to the chip's SCLK input, but I'm not sure if this is the clock referred to in
the code. (NCR SCSI clock freq. )
This problem could also be due to a hardware problem, but the code detects the chip and
reads the config data OK.
Another problem I'm having is: CACHE TEST FAILED: timeout. I'm still tracing this.
I'm pretty sure I set a legal cache line size and latency in the sandpoint_pci.c config
code.
I shall forward this msg to the author of the driver tomorrow if no joy.
regards, Ron
Ron Bianco
Computer Systems Technologist
Level Control Systems
email: ronb@junction.net
phone: 250-549-2558 Ext 8
web: www.lcsaudio.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-31 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-31 23:24 Ron Bianco [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-01 18:48 Using SCSI driver sym53c8xx.c - no nvram - no symbios BIOS Ron Bianco
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='000001bffb46$8756d300$4d012ac7@warp-speed' \
--to=ronb@junction.net \
--cc=linuxppc-embedded@lists.linuxppc.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).