[lkml]   [2001]   [Oct]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux should not set the "PnP OS" boot flag
 --- Stelian Pop <> wrote: 
> Anyway, the PnP OS setting in the BIOS doesn't change anything
> regarding to the Linux PnP initialisation oops (same printouts,
> same calltrace, etc).

Too bad. :(

Although it apparently won't help Stelian, I still think it's
good practice (1) to set the boot flags to what's safe, and
then (2) to give the user the ability to change the default if
s/he wants to try speeding things up.

(Parenthesis re: time savings
Alan: You say that setting the PnP-OS flag can save up to
thirty seconds at boot time. My suspicion is that it may
actually be the diagnostics that take up all these seconds
(e.g., testing each of 128 million memory locations), not
the configuration process. Are you sure that it isn't
clearing the DIAG flag that's important for time savings,
not setting the PNPOS flag?)

It's useful to be able to select a different default at build
time (CONFIG_SBF_PNPOS). But in addition I would like to provide
/proc access to the bootflags. That way, if I suspect a hardware
problem I can "echo 1 > /proc/sys/bootflags/diag" and reboot; or
if I am going to boot DOS I can "echo 0 > /proc/sys/bootflags/pnpos"
and reboot. Question: Where should I put these entries under
/proc. Are my examples okay?


Do You Yahoo!?
Get your free address at
or your free address at
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:05    [W:0.041 / U:5.700 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site