From: Alex deVries <adevries@thepuffingroup.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Dino developments...
Date: Sun, 03 Oct 1999 19:29:19 -0400 [thread overview]
Message-ID: <37F7E6CF.F781614F@thepuffingroup.com> (raw)
I've fixed up a couple of things in the kernel:
- PCI bus walking happens in the *right place*, pci_init().
- I've fixed the inventory code to handle hversion_rev and sversion_rev
- Multiple Dinos are detected properly now
- Card Mode Dino now seems to work for bus walking, the MMIO is a whole
different story.
As a test, I packed in:
- a Symbios SCSI controller PCI card
- a GSC gigabit ethernet card (which uses a dino)
- another GSC gigabit ethernet card (which uses a dino)
(and if you're curious as to how I can pack three cards in an A class,
you'll have to visit Ottawa to see)
The output I get is:
Dino version 3.1 (bridge mode) found at
0xfff80000
Dino version 3.0/3.1 (card mode) found at
0xfff84000
Found a PCI device, and the vendor is 0x107e, device
0x3
Dino version 3.0/3.1 (card mode) found at
0xfff88000
Found a PCI device, and the vendor is 0x12ae, device
0x1
PCI: Probing PCI
hardware
Found a PCI device, and the vendor is 0x104b, device
0x8130
Found a PCI device, and the vendor is 0x1011, device
0x19
So the first PCI device found is an "Interphase" gigE thing that's not
in the PCI database, the second is an Alteon Acenic gigE, the third is
the Symbios SCSI card, and the last is the onboard DEC tulip.
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next reply other threads:[~1999-10-03 23:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-03 23:29 Alex deVries [this message]
1999-10-04 4:45 ` [parisc-linux] Dino developments Grant Grundler
1999-10-04 16:05 ` Alex deVries
1999-10-04 5:30 ` Grant Grundler
1999-10-04 19:57 ` Alex deVries
-- strict thread matches above, loose matches on Subject: below --
1999-10-07 21:00 Grant Grundler
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=37F7E6CF.F781614F@thepuffingroup.com \
--to=adevries@thepuffingroup.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 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.