From: James Bottomley <James.Bottomley@steeleye.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Using ncr53c8xx.c for a 53c770 chip (Was: State of NCR53c7xx based drivers)
Date: 13 Jan 2004 11:33:03 -0500 [thread overview]
Message-ID: <1074011584.2173.126.camel@mulgrave> (raw)
In-Reply-To: <20040113145553.A1738@sygehus.dk>
On Tue, 2004-01-13 at 08:55, Rask Ingemann Lambertsen wrote:
> That's only for the 2.6.x kernels, isn't it?
it's only been cut apart to work nicely like this in 2.6 kernels, yes.
There is a residue in 2.4 for driving the parisc zalon (53c720) card
> I need some help filling in the ncr_chip structure. Where do I find the
> device_id, revision_id, burst_max, nr_divisor and features settings? I can
> figure some of it out:
> .offset_max = 15 (the maximum allowed by the AmigaOS driver).
> .features = FE_ULTRA | FE_WIDE | FE_RAM (but maybe more flags are needed?)
I'd get it working in 53c720 mode first (i.e. drop the FE_ULTRA) and
then go back and add the ultra capability.
> I also need some help filling in the ncr_slot structure. The registers are
> memory mapped at bus address 0xf40000 and the script RAM is memory mapped at
> bus address 0xf41000. So I guess base is for the registers, base2 is for
> the script RAM and that *_v is for the virtual memory addresses of the above.
> That still leaves me with io_port, base_c, base2_c and base_io.
That should be correct...although I've not tested it, it might be wise
to begin without the FE_RAM as well. I can check this with the
NCR_Q720, though if you get problems. Although it doesn't have on-chip
ram for scripts, the board itself has 2Mb of ram behind the MCA window
> Where do I tell the driver about the SCSI clock (50 MHz)?
The driver will work it out...it has its own timing routine.
This is another reason for trying without FE_ULTRA. Normally, a 770 in
Ultra mode requires an 80MHz clock. For a 50MHz clock, you need to use
the 770s clock doubler mode, so when you're ready to try it, you'll need
FE_DBLR (and I don't think this has ever been tested on a 770 either...)
James
next prev parent reply other threads:[~2004-01-13 16:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 11:38 State of NCR53c7xx based drivers Christoph Hellwig
2003-11-23 9:08 ` Richard Hirst
2003-11-23 10:24 ` Geert Uytterhoeven
2003-11-23 16:50 ` Rask Ingemann Lambertsen
2003-11-23 16:59 ` James Bottomley
2004-01-13 13:55 ` Using ncr53c8xx.c for a 53c770 chip (Was: State of NCR53c7xx based drivers) Rask Ingemann Lambertsen
2004-01-13 14:15 ` Using ncr53c8xx.c for a 53c770 chip Rask Ingemann Lambertsen
2004-01-13 16:45 ` James Bottomley
2004-01-13 16:33 ` James Bottomley [this message]
2004-01-13 18:57 ` Rask Ingemann Lambertsen
2003-11-23 17:07 ` State of NCR53c7xx based drivers Geert Uytterhoeven
2003-11-23 22:21 ` Rask Ingemann Lambertsen
2003-11-24 5:12 ` Ken Tyler
2003-11-24 14:26 ` Rask Ingemann Lambertsen
2003-11-24 19:13 ` Ken Tyler
2003-11-24 20:49 ` Geert Uytterhoeven
2003-11-25 11:32 ` Ken Tyler
2003-11-25 16:01 ` Rask Ingemann Lambertsen
2003-11-25 20:17 ` Ken Tyler
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=1074011584.2173.126.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rask@sygehus.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.