All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Grant Grundler <grundler@puffin.external.hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] request_region()
Date: Tue, 3 Apr 2001 10:05:02 +0100	[thread overview]
Message-ID: <20010403100502.K9198@linuxcare.com> (raw)
In-Reply-To: <200104030306.VAA10572@puffin.external.hp.com>; from grundler@puffin.external.hp.com on Mon, Apr 02, 2001 at 09:06:10PM -0600

On Mon, Apr 02, 2001 at 09:06:10PM -0600, Grant Grundler wrote:
> The plan was EISA devices under ASP should use request_region()
> and inb/outb. I have no clue how EISA "bus walk" works or how EISA
> drivers will find/claim their devices.
> 
> The EISA HBA needs to register it's "pci_ops".
> See arch/parisc/kernel/pci.c:PCI_PORT_OUT macro.

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.
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

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.

Richard

  reply	other threads:[~2001-04-03  9:05 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 [this message]
2001-04-03 16:41     ` Matthew Wilcox
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=20010403100502.K9198@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=grundler@puffin.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.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 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.