From: "Stephen J. Bevan" <stephen@dino.dnsalias.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] PCI vs. VPC
Date: Tue, 7 May 2002 12:05:09 +0000 [thread overview]
Message-ID: <m3bsbtc12s.fsf@dino.dnsalias.com> (raw)
In-Reply-To: <0fa9a1a48b551903e12d530998e96205@plan9.bell-labs.com>
jmk@plan9.bell-labs.com writes:
> My first suspect would be that the PCI configuration ports are not
> being emulated. Windows and Linux use the BIOS to retrieve PCI configuration
> space information, Plan 9 does it raw.
Linux can do it raw or via the BIOS. The default is to do it raw even
if there is a BIOS. However, if a raw probe for configuration types 1
or 2 fails, it falls back to using the BIOS. This fallback can be
disabled by booting Linux with "nobios".
next prev parent reply other threads:[~2002-05-07 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 13:12 jmk
2002-05-07 12:05 ` Stephen J. Bevan [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 15:25 jmk
2002-05-04 14:31 jmk
2002-05-07 11:59 ` Don
2002-05-04 6:04 Jake
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=m3bsbtc12s.fsf@dino.dnsalias.com \
--to=stephen@dino.dnsalias.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).