Hey there.
On 6 Dec 2001, Cory Bell wrote:
> On Thu, 2001-12-06 at 17:03, Randy.Dunlap wrote:
> > Hi-
> >
> > Did your search for "$PIR" or "RIP$" ?
> > It is suppsed to be the latter (little-endian).
>
> Tried both. The flash BIOS update might be reading system specific stuff
> and then appending it to the new update, though. Maybe they have
> separate "code" and data areas, and the the data part never gets
> overwritten.
>
> Would you happen to have any thoughts or advice WRT the problem we have
> and the proper method of addressing it? Absent a BIOS fix, of course,
> which I imagine would be the ultimate solution.
How new is this system?
If it's new (3-6 months) PCI IRQ information is probably encoded in ACPI
AML methods. OEMs are gradually changing from the old way (PIRQ and MP
tables, APM) to new Grand Unified Way(tm) (ACPI).
For a while now, BIOSes have shipped with both old tables and ACPI tables,
and in a lot of cases, one or the other lies. So, you're almost lucky in a
sense. Unfortunately, it doesn't solve your problem.
For some reason, the people that wrote the spec encoded PCI IRQ
information in AML (ACPI Machine Language), instead of putting them in a
flat table. Which means you need the interpretor up and running and you
need to execute those methods (don't ask, just nod and smile).
The Intel ACPI guys kinda have this working. They are able to extract and
execute the methods. But, they still have yet to make devices request and
use that information. Maybe Andy Grover can comment on this..
BTW, The latest ACPI patch is at: http://sourceforge.net/projects/acpi/.
-pat
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Dec 07 2001 - 21:00:39 EST