From: Matthew Wilcox <matthew@wil.cx>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: Grant Grundler <grundler@puffin.external.hp.com>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] request_region()
Date: Tue, 3 Apr 2001 17:41:56 +0100 [thread overview]
Message-ID: <20010403174156.U11435@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20010403100502.K9198@linuxcare.com>; from rhirst@linuxcare.com on Tue, Apr 03, 2001 at 10:05:02AM +0100
On Tue, Apr 03, 2001 at 10:05:02AM +0100, Richard Hirst wrote:
> Yep, that make sense. Does mean sim700.c will have to make runtime
> decisions whether to use raw_read (for the on-board 53c700) or inb
> (for one on an EISA card), on my 715, but that is no big deal.
i think sim700.c should be using ioremap / readX / writeX instead
of raw_read. Is the EISA scsi really only accessible via port io?
I would have throught that it would be memory mapped, in which case
there's no need to have a macro to access it.
> EISA allocates 0x1000 bytes per slot, with a four (?) byte signature
> at offset 0xc80 (IIRC) to identify the cards. At least, that is
> how my old Compaq works, with first slot at 0x1000. Seems to tie
> up address-wise, at least:
>
> 10. Scorpio Sr. EISA BA (11) at 0xfc000000, versions 0x19, 0x0, 0x76, 0x0, 0x0
> 11. Unknown device (10) at 0xfc001000, versions 0x0, 0x0, 0xfff, 0x0, 0x0
That seems to indicate memory mapped IO...
> Again, IIRC, last time I played with the EISA slot on my 715 I
> found the EISA 53c700 couldn't access main memory, and EISA interrupts
> were not routed to the CPU. The driver could access the chip registers
> though. But that was all a long time ago, so things may be different
> now.
How BugFree(TM) do we think the Wax driver is?
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-04-03 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 23:11 [parisc-linux] request_region() Richard Hirst
2001-04-03 3:06 ` Grant Grundler
2001-04-03 9:05 ` Richard Hirst
2001-04-03 16:41 ` Matthew Wilcox [this message]
2001-04-04 0:25 ` Grant Grundler
2001-04-03 23:57 ` Grant Grundler
2001-04-04 0:10 ` Alan Cox
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=20010403174156.U11435@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=grundler@puffin.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rhirst@linuxcare.com \
/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