All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: vandrove@vc.cvut.cz, lkml <linux-kernel@vger.kernel.org>
Subject: RE: Using ACPI to get PCI routing info?
Date: Fri, 13 Jul 2001 16:53:58 -0700	[thread overview]
Message-ID: <3B4F8A16.83EF0CA1@osdlab.org> (raw)

Petr-

Where does someone find/get BIOS version F5a for the 6VXD7?
The latest that I see on the Gigabyte web pages is F5.

Thanks,
~Randy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hi,
  Gigabyte (and/or AMI and/or VIA) decided that it is not worth 
of effort to create full mptable and since version F5a for 6VXD7 
they do not report PCI interrupts as 16-19, but only as traditional 
0-15 (and they do not report them as conforms/conforms, but as 
active-lo/level).

  For now I hardwired correct routing table into my kernel, as
I have other uses for IRQ < 16, but after some investigation I 
found that ACPI _SB_.PCI0._PRT element returns correct routing 
table (using IRQ 16-19). So my question is, are there any plans 
to use ACPI tables to get IRQ routing tables, or should I complain 
to Gigabyte that I'm not satisfied (I'll complain anyway, but...)?

                                        Thanks,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz

P.S.: No, there is no MPS1.1/MPS1.4 switch in BIOS (anymore) :-(
And no, there is no way to disable ACPI in that BIOS :-((

/* Old working BIOS... 6VXD7 - F2 */
...
/* 'Broken' 6VXD7 - F5a */
...

             reply	other threads:[~2001-07-13 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-13 23:53 Randy.Dunlap [this message]
2001-07-14 19:35 ` Using ACPI to get PCI routing info? Petr Vandrovec
  -- strict thread matches above, loose matches on Subject: below --
2001-02-22 21:38 Grover, Andrew
2001-02-22 20:30 Petr Vandrovec

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=3B4F8A16.83EF0CA1@osdlab.org \
    --to=rddunlap@osdlab.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.