public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: ASUS K8N-DL Beta BIOS
Date: Sat, 02 Jul 2005 22:37:11 -0600	[thread overview]
Message-ID: <42C76B77.9020709@shaw.ca> (raw)
In-Reply-To: <4lzQi-2fw-21@gated-at.bofh.it>

Sean Bruno wrote:
> Also, the ACPI PCI Interrupt Routing Table (PRT) contains references to
> entries that don't exist elsewhere in the ACPI tables:
> 
> ACPI: Subsystem revision 20050309
>     ACPI-0352: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace,
> AE_NOT_FOUND
> search_node ffff81013ffca240 start_node ffff81013ffca240 return_node
> 0000000000000000
>     ACPI-0352: *** Error: Looking up [\_SB_.PCI0.APC0] in namespace,
> AE_NOT_FOUND
> search_node ffff81013ffca140 start_node ffff81013ffca140 return_node
> 0000000000000000
> 
> Linux unfortunately appears to give up on parsing the PRT when this
> happens, unlike Windows, which will parse the table despite these
> errors. Without parsing the PRT, Linux cannot know how to route
> interrupts for various PCI devices, which results in the later errors:

Is there a reason Linux couldn't behave similarly to Windows in this 
situation? That might provide some better compatibility with such buggy 
BIOSes..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2005-07-03  4:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4lznf-1XY-7@gated-at.bofh.it>
     [not found] ` <4lzQi-2fw-21@gated-at.bofh.it>
2005-07-03  4:37   ` Robert Hancock [this message]
2005-07-05  4:00 ASUS K8N-DL Beta BIOS Hodle, Brian
  -- strict thread matches above, loose matches on Subject: below --
2005-07-01 19:19 Hodle, Brian
2005-07-01 19:42 ` Sean Bruno
2005-07-02 17:43   ` Alistair John Strachan
2005-07-02 19:44     ` Andi Kleen
2005-07-03  4:32       ` Sean Bruno
2005-07-03  7:37         ` Alexander Nyberg
2005-07-04 20:06           ` Sean Bruno
2005-07-04 21:02             ` Sean Bruno
2005-07-04 21:26               ` Andi Kleen
2005-07-04 21:39                 ` Sean Bruno
2005-07-04 21:37             ` Andi Kleen
2005-07-05 15:54   ` Alan Cox
2005-07-05 16:43     ` Lee Revell
2005-07-03  5:05 ` Karim Yaghmour
2005-06-28 22:05 Sean Bruno
2005-06-29  1:46 ` Karim Yaghmour

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=42C76B77.9020709@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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