Thread (1 message) 1 message, 1 author, 2003-10-17

RE: eisa_set_level_irq(acpi_fadt.sci_int)

From: Arndt Schoenewald <hidden>
Date: 2003-10-17 10:39:41

On Wed, Oct 15, 2003 at 03:09:59PM -0700, Grover, Andrew wrote:
quoted
From: Brown, Len 
What does eisa_set_level_irq() do for us?

As its presence breaks the !CONFIG_PCI build, I deleted it and found
that ACPI in PIC mode seems to work just fine without it (at 
least on 2
of 2 systems tested so far)
This is how you set a PIC interrupt to PCI semantics (active low, level
triggered.) If your ACPI interrupt is shared, the PCI subsystem will
call this for the irq and so whether ACPI calls it or not is not an
issue, but if ACPI is alone on the irq, it must call it or the irq will
have ISA semantics.
There are a couple of laptops for which the calls to eisa_set_level_irq()
are needed to get some builtin devices to work, i.e. the Gericom 1st
SuperSonic, Supersonic GPRS, Supersonic2; FIC A360, A380; Medion MD 9703.

Apparently the BIOS only initializes the PCI interrupt lines required for
booting and leaves the setup of the rest to the OS. Without these calls
done by the ACPI IRQ routing code, I can't use FireWire, PCMCIA, modem,
and NIC, so please do not remove them. And the call for the ACPI interrupt
is needed, too, or the ACPI events (e.g. power button, lid) won't work.

Best regards,
Arndt

-- 
Arndt Schönewald [off-list ref], Software Developer
Quelltext AG (http://www.quelltext-ag.de), Dortmund, Germany


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help