public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Persvold <sp@scali.no>
To: Pavel Roskin <proski@gnu.org>
Cc: Zilvinas Valinskas <zvalinskas@carolina.rr.com>,
	linux-kernel@vger.kernel.org
Subject: Re: VIA/PDC/Athlon
Date: Fri, 18 May 2001 08:33:22 +0200	[thread overview]
Message-ID: <3B04C232.310A30EA@scali.no> (raw)
In-Reply-To: <Pine.LNX.4.33.0105172131230.5744-100000@portland.hansa.lan>

Pavel Roskin wrote:
> 
> Hello, Zilvinas!
> 
> There are utilities that work with PnP BIOS. They are included with
> pcmcia-cs (which is weird - it should be a separate package) and called
> "lspci" and "setpci". They depend on PnP BIOS support in the kernel
> (CONFIG_PNPBIOS).
> 
> Dumping your PnP BIOS configuration and checking whether it has changed
> after booting to Windows would be more reasonable than checking your PCI
> configuration (IMHO).

Ehm, "lspci" and "setpci" is part of the pci-utils package (at least on RedHat)
and is used to dump/modify PCI configuration space (/proc/bus/pci). If you know
how to use these tools to dump PNP bios, please tell us.

Regards
-- 
  Steffen Persvold               Systems Engineer
  Email : mailto:sp@scali.no     Scali AS (http://www.scali.com)

  reply	other threads:[~2001-05-18  6:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18  3:52 VIA/PDC/Athlon Pavel Roskin
2001-05-18  6:33 ` Steffen Persvold [this message]
2001-05-18 12:15   ` VIA/PDC/Athlon Pavel Roskin
  -- strict thread matches above, loose matches on Subject: below --
2001-05-16 17:25 VIA/PDC/Athlon Jussi Laako
2001-05-16 20:05 ` VIA/PDC/Athlon Vojtech Pavlik
2001-05-17 16:43   ` VIA/PDC/Athlon Jussi Laako
2001-05-17 16:44     ` VIA/PDC/Athlon Alan Cox
2001-05-17 20:28       ` VIA/PDC/Athlon Jussi Laako
2001-05-17 21:25         ` VIA/PDC/Athlon Alan Cox
2001-05-16 23:47 ` VIA/PDC/Athlon Alan Cox
2001-05-17  0:19 ` VIA/PDC/Athlon Zilvinas Valinskas
2001-05-17 16:46   ` VIA/PDC/Athlon Jussi Laako

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=3B04C232.310A30EA@scali.no \
    --to=sp@scali.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=zvalinskas@carolina.rr.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