From: Hamish Moffatt <hamish@cloud.net.au>
To: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] How to configure EISA network card in 715/80
Date: Sat, 12 Jan 2002 10:17:51 +1100 [thread overview]
Message-ID: <20020112101751.A27054@silly.cloud.net.au> (raw)
In-Reply-To: <20020111161705.E26644@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Fri, Jan 11, 2002 at 04:17:05PM +0000
On Fri, Jan 11, 2002 at 04:17:05PM +0000, Matthew Wilcox wrote:
> This is rather strange. I see no EISA adapter. Sure, we have Wax in
> its role as a bus adapter, with its HIL & RS-232 subdevices, but there's
> no EISA device. Anyone know why this might be?
>
> (iirc, it normally shows up as device 6).
FWIW, it's device #11 for me. On a 712/80:
Found devices:
1. Mirage 80 GSC Builtin Graphics (10) at 0xf8000000 [1], versions 0x10, 0x0, 0x85
2. Mirage 80 Core BA (11) at 0xf0100000 [2], versions 0x2b, 0x0, 0x81
3. Mirage 80 Core SCSI (10) at 0xf0106000 [2/0/1], versions 0x2b, 0x0, 0x82
4. Mirage 80 Core LAN (802.3) (10) at 0xf0107000 [2/0/2], versions 0x2b, 0x0, 0x8a
5. Mirage 80 Core RS-232 (10) at 0xf0105000 [2/0/4], versions 0x2b, 0x0, 0x8c
6. Mirage 80 Core Centronics (10) at 0xf0102000 [2/0/6], versions 0x2b, 0x0, 0x74
7. Mirage 80 Audio (10) at 0xf0104000 [2/0/8], versions 0x2b, 0x0, 0x7b
8. Mirage 80 Core PC Floppy (10) at 0xf010a000 [2/0/10], versions 0x2b, 0x0, 0x83
9. Mirage 80 Core PS/2 Port (10) at 0xf0108000 [2/0/11], versions 0x2b, 0x0, 0x84
10. Mirage 80 Core PS/2 Port (10) at 0xf0108100 [2/0/12], versions 0x2b, 0x0, 0x84
11. Mirage 80 Wax EISA BA (11) at 0xfc000000 [4], versions 0x2b, 0x0, 0x90
12. Pace Wax BA (11) at 0xf0200000 [5], versions 0x10, 0x0, 0x8e
13. Pace Core HIL (10) at 0xf0201000 [5/0/1], versions 0x10, 0x0, 0x73
14. Mirage 80 Wax RS-232 (10) at 0xf0202000 [5/0/2], versions 0x10, 0x0, 0x8c
15. Mirage 80 (0) at 0xfffbe000 [8], versions 0x619, 0x0, 0x4
16. Mirage 80 (1) at 0xfffbf000 [9], versions 0x4f, 0x0, 0x9
I don't have anything on the EISA bus that I'm aware of; nothing
that I need to use anyway.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2002-01-11 23:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 15:38 [parisc-linux] How to configure EISA network card in 715/80 Rafael Herrera
2002-01-11 15:43 ` Matthew Wilcox
2002-01-11 16:07 ` Rafael Herrera
2002-01-11 16:17 ` Matthew Wilcox
2002-01-11 16:21 ` Rafael Herrera
2002-01-11 16:27 ` Matthew Wilcox
2002-01-11 17:54 ` Rafael E. Herrera
2002-01-12 1:35 ` Rafael Herrera
2002-01-11 23:17 ` Hamish Moffatt [this message]
2002-01-11 19:38 ` Christian Suder
2002-01-11 20:00 ` Matthew Wilcox
2002-01-11 21:54 ` Matthew Wilcox
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=20020112101751.A27054@silly.cloud.net.au \
--to=hamish@cloud.net.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox