public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	"mobil@wodkahexe.de" <mobil@wodkahexe.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9-rc4 No local APIC present or hardware disabled
Date: Sun, 24 Oct 2004 16:11:17 +0100	[thread overview]
Message-ID: <1098630663.24236.1.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58L.0410241615350.14448@blysk.ds.pg.gda.pl>

On Sul, 2004-10-24 at 16:44, Maciej W. Rozycki wrote:
> > I agree with Alan that accusing the BIOS of being buggy is unwarranted.
> 
>  I disagree.  If the firmware performs any actions on hardware without
> asking the OS for permission, it *must* be prepared for it to be in any
> possible state and handle it correctly, including any transitional states
> (as it does respect spinlocks).  Otherwise it's buggy.

Show me a PC standards document that says this - there are none.

>  Alan, referring to your statement: it's like stating we must only use the
> text mode of the display adapter, because that's the state it's left in by
> the firmware and it may not expect any other state.

If you switch video mode without using the BIOS then the BIOS video
calls are not guaranteed to work. Its the same thing.


> +		if (enable_local_apic <= 0) {
> +			apic_printk(APIC_VERBOSE,
> +				    "Local APIC disabled by BIOS -- "
> +				    "you can enable it with \"lapic\"\n");
> +			return -1;

Looks good to me in this form.


  reply	other threads:[~2004-10-24 16:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 17:54 2.6.9-rc4 No local APIC present or hardware disabled mobil
2004-10-12 16:11 ` Mikael Pettersson
2004-10-12 16:15 ` Prakash K. Cheemplavam
2004-10-13 23:59 ` Maciej W. Rozycki
2004-10-14 10:52   ` Mikael Pettersson
2004-10-14 22:27     ` Maciej W. Rozycki
2004-10-15 12:26       ` Alan Cox
2004-10-15 13:53       ` Mikael Pettersson
2004-10-24 15:44         ` Maciej W. Rozycki
2004-10-24 15:11           ` Alan Cox [this message]
2004-10-25 14:08           ` Mikael Pettersson
2004-10-14 11:59   ` mobil
2004-10-14 21:25     ` Maciej W. Rozycki

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=1098630663.24236.1.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mikpe@csd.uu.se \
    --cc=mobil@wodkahexe.de \
    /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