Re: Changing IRQ`s at DSDT

[Robert Woerle <robert-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org>]

Andrew de Quincey schrieb:

>On Monday 29 September 2003 11:44, Robert Woerle wrote:
>  
>
>>Hi
>>
>>for the history : i am having a issue with ACPI and IRQ`s ( i believe )
>>i have a configuration where sound ( ali5451 ) , eth0( realtek 8139) and
>>usb ( usb-ohci) are using IRQ 5 .
>>Until now what happens is that when i used 2 out of these 3 devices at
>>the same time the unit locked hard .
>>
>>Now i am able to set eth0 to IRQ7 and a first stress test with 600MB
>>dowload and playing songs worked fine .
>>
>>I am using now 2.4.22 + acpi20030916  + the initrd patch to use my own
>>DSDT .
>>
>>I reached that now in sent the LNK1 in my DSDT to IRQ 7 .
>>
>>Unfortunatly the systems still uses IRQ 5 for the other 2 devices
>>although i also did change the LNK8 and LNKU  at the DSDT ( tryed 6  and
>>11 and 7 ) .
>>
>>find attached my data of the unit ..
>>
>>can somebody tell me why it ignores my changes to LNK8 and LNKU in my
>>DSDT and still uses IRQ5 ?
>>i am also curious why certain LNK`s are parsed twice ???
>>    
>>
>
>Aha, that diff doesn't include the other patch I released more recently, which makes ACPI not 
>reallocate an IRQ if the BIOS has already allocated one.. this sounds like the 
>problem you are encontering.
>
>Try this (against 2.4.23-pre3, so you may have to wiggle it into place). Lemme know if it helps.
>
>
>--- linux-2.4.23-pre3.null_crs/drivers/acpi/pci_link.c	2003-09-05 23:57:39.000000000 +0100
>+++ linux-2.4.23-pre3.nochangeirq/drivers/acpi/pci_link.c	2003-09-16 23:59:49.212387016 +0100
>@@ -507,15 +507,15 @@
> 		irq = link->irq.active;
> 	} else {
> 		irq = link->irq.possible[0];
>-	}
> 
>-	/* 
>-	 * Select the best IRQ.  This is done in reverse to promote 
>-	 * the use of IRQs 9, 10, 11, and >15.
>-	 */
>-	for (i=(link->irq.possible_count-1); i>0; i--) {
>-		if (acpi_irq_penalty[irq] > acpi_irq_penalty[link->irq.possible[i]])
>-			irq = link->irq.possible[i];
>+		/* 
>+		 * Select the best IRQ.  This is done in reverse to promote 
>+		 * the use of IRQs 9, 10, 11, and >15.
>+		 */
>+		for (i=(link->irq.possible_count-1); i>0; i--) {
>+			if (acpi_irq_penalty[irq] > acpi_irq_penalty[link->irq.possible[i]])
>+				irq = link->irq.possible[i];
>+		}
> 	}
> 
> 	/* Attempt to enable the link device at this IRQ. */
>  
>
hmm .. this patch doenst change too much ... .it only let run that code 
in the else {} ?? right ?

i used it but didnt found any difference ... all the IRQ`s which are 
active stay active and i cannot change them
with my DSDT ...

is there a way to not mark them as active and then be able to change 
them like i want ???

Cheers Rob

-- 
_____________________________________
*Robert Woerle
Linux & Customer Support*
*PaceBlade Technology Europe SA*
phone: 	+49 89 552 99935
fax: 	+49 89 552 99910
mobile: 	+49 179 474 45 27
email: 	robert-fPtsKRK0pHxl57MIdRCFDg@public.gmane.org <mailto:robert@paceblade.com>
web: 	http://www.paceblade.com
_____________________________________






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