From: Philipp Rumpf <prumpf@suse.de>
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: PCI-like busses
Date: Fri, 3 Sep 1999 20:46:34 +0200 [thread overview]
Message-ID: <19990903204634.N10698@suse.de> (raw)
In-Reply-To: <199909031827.LAA08791@milano.cup.hp.com>; from Grant Grundler on Fri, Sep 03, 1999 at 11:27:10AM -0700
> > So: Are there parisc boxen with more than one type of interface to PCI-like
> > busses?
>
> B/C/D class boxen haben PCI u. EISA (u. GSC) "slots".
> Since learning EISA/ISA busses are "PCI-like", the answer is "yes".
Of course, strictly speaking we could separate between pci busses (where we
have configuration space accesses) and isa-like busses (where we don't). I
don't see any advantage. For port accesses, we don't have to separate.
> And if this answer is right, then I'll put back the "multi-bus type"
> support in pci.h. I don't get how EISA would use these services
> (perhaps just the IRQ stuff?) but I'll trust you on that.
Remember I still want to remove the IRQ handling out of struct pci_bus_ops.
> Yes - but I'm only aware of K/T class "form factor" (shape/size).
> These won't normally fit in the A/B/C/D class boxes which also have
The Dino-on-a-card I have in the A180C is quite long, yes.
> (Next week I'll see if I can wedge the K-class one into a workstation
> anyway)
Don't destroy any hardware ;)
Philipp Rumpf
prev parent reply other threads:[~1999-09-03 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199909012302.RAA04026@puffin.external.hp.com>
1999-09-02 9:12 ` [parisc-linux-cvs] grundler Philipp Rumpf
1999-09-02 17:20 ` Grant Grundler
1999-09-03 11:15 ` Philipp Rumpf
1999-09-03 16:22 ` Alex deVries
1999-09-03 22:47 ` [parisc-linux] Card-mode Dino Grant Grundler
1999-09-04 2:19 ` LaMont Jones
1999-09-04 20:18 ` Grant Grundler
1999-09-03 18:27 ` [parisc-linux] PCI-like busses Grant Grundler
1999-09-03 18:46 ` Philipp Rumpf [this message]
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=19990903204634.N10698@suse.de \
--to=prumpf@suse.de \
--cc=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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