LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: ebiederman@uswest.net (Eric W. Biederman)
To: Thomas Hood <jdthood@mail.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Linux should not set the "PnP OS" boot flag
Date: 06 Oct 2001 13:24:08 -0600	[thread overview]
Message-ID: <m1bsjky3l3.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1002339356.814.45.camel@thanatos>
In-Reply-To: <1002339356.814.45.camel@thanatos>

Thomas Hood <jdthood@mail.com> writes:

> My problem was: After running a recent 2.4.x kernel, on a subsequent
> boot of Linux, all configurable devices (internal modem, audio chip,
> parallel, serial and IR ports) were disabled.  This would causes
> oopses in my sound device drivers.
> 
> My workarounds were:
> (1) to reinitialize the BIOS prior to booting, or,
> (2) to run "setpnp on" on all the configurable devices early in
>     the boot sequence.
> 
> I just now figured out what was going on.  When the PnP BIOS is
> going to boot a non-PnP OS, it configures all configurable devices
> itself.  When the PnP BIOS is going to boot a PnP OS (which it
> tells from a "boot flag") it leaves configurable devices, other
> than those needed to boot the OS, unconfigured.  Recent Linux
> kernels have set the "boot flag" indicating that the OS being booted
> is a PnP OS.
> 
> Unfortunately, Linux isn't really a "PnP OS".  The kernel alone
> doesn't configure the devices.  One has to use setpnp to do that.

Hmm.  Linux isn't quite a "PnP OS".  I agree that in the short
term we should not set the boot flag.  But we should also investigate
what needs to added so that setpnp does not need to be called.

In the normal case the pci subsystem gets this correct, and we need
the logic to get this correct to support hot plug devices.

Do you have any insite into what needs to be done so that the kernel
will automatically configure isa pnp devices?

Eric




  reply	other threads:[~2001-10-06 19:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-06  3:35 Thomas Hood
2001-10-06 19:24 ` Eric W. Biederman [this message]
2001-10-06 21:11   ` Alan Cox
2001-10-07  1:08     ` Eric W. Biederman
2001-10-07  2:54 Thomas Hood
2001-10-07 10:02 ` Alan Cox
2001-10-07 13:50   ` Thomas Hood
2001-10-07 14:07     ` Dave Jones
2001-10-07 14:18     ` Alan Cox
2001-10-07 17:10       ` Thomas Hood
2001-10-07 21:59         ` Alan Cox
2001-10-07 17:54       ` Thomas Hood
2001-10-08 12:40 Thomas Hood
2001-10-08 13:25 ` Stelian Pop
2001-10-08 22:12   ` J.D. Hood

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=m1bsjky3l3.fsf@frodo.biederman.org \
    --to=ebiederman@uswest.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jdthood@mail.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Linux should not set the "PnP OS" boot flag' \
    /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

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).