public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James-l7zRWeYnyd2TY6FTCsQk+9Bc4/FLrbF6@public.gmane.org>
To: Andrew de Quincey <adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: Discussion: ACPI selective IRQ blacklist
Date: Thu, 04 Sep 2003 02:47:16 +0100	[thread overview]
Message-ID: <3F5699A4.3090608@superbug.demon.co.uk> (raw)
In-Reply-To: <200309040215.23281.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>

Andrew de Quincey wrote:
> On Wednesday 03 September 2003 23:16, Andrew de Quincey wrote:
> 
>>So:
>>If a motherboard is dodgy and IS in the bad-routing-blacklist, ACPI will
>>not be used for PCI routing.
>>
>>If a motherboard is dodgy and is NOT in the bad-routing-blacklist, the
>>fallback to picmode code should catch it. If the user then wants APIC with
>>ACPI, they report the issue and the board is added to the
>>bad-routing-blacklist.
> 
> 
> On further thought, I realise this isn't future proof. This relies on the 
> existence of legacy BIOS tables (e.g. MPBIOS). My machine for one does not 
> have such a table; instead it relies on ACPI.
> 
> In the meantime, VIA have kindly sent me the docs I need. It turns out the PCI 
> routing entries for the problem BIOSes are wrong. The south bridge chip in 
> question is the VT8235 (device ID 0x1337), which explains the spread of 
> motherboards I've been seeing.
> 
> I have a solution in mind; should have something in the next few days.
> 
Would it be possible to bypass the BIOS completely, and talk to the 
chips on the motherboard direct ?
It should work, unless the BIOS provides information that the chips on 
the motherboard do not have. At a guess, I would say that the chips on 
the motherboard might not have information like a wiring diagram.

Cheers
James




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2003-09-04  1:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-03 22:16 Discussion: ACPI selective IRQ blacklist Andrew de Quincey
     [not found] ` <200309032316.11076.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-04  1:15   ` Andrew de Quincey
     [not found]     ` <200309040215.23281.adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org>
2003-09-04  1:47       ` James Courtier-Dutton [this message]
     [not found]         ` <3F5699A4.3090608-l7zRWeYnyd2TY6FTCsQk+9Bc4/FLrbF6@public.gmane.org>
2003-09-04  1:50           ` Andrew de Quincey
  -- strict thread matches above, loose matches on Subject: below --
2003-09-04  1:19 Nakajima, Jun

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=3F5699A4.3090608@superbug.demon.co.uk \
    --to=james-l7zrweynyd2ty6ftcsqk+9bc4/flrbf6@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=adq_dvb-fmPXVN3awWJAJAzL26g0SA@public.gmane.org \
    --cc=linux-acpi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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