From: Alex deVries <adevries@thepuffingroup.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] PCI bus walking!
Date: Sun, 03 Oct 1999 02:54:47 -0400 [thread overview]
Message-ID: <37F6FDB7.54FEEE9F@thepuffingroup.com> (raw)
The kernel tree in CVS now has PCI code sort of working, so it can scan
the PCI bus on a Dino and find devices. It's still broken in several
ways: it
doesn't support multiple dino's, it can't handle interrupts yet, and is
basically doing things in the wrong order, but does work.
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next reply other threads:[~1999-10-03 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-03 6:54 Alex deVries [this message]
1999-10-03 21:57 ` [parisc-linux] PCI bus walking! 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=37F6FDB7.54FEEE9F@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox