Re: sony srx7... sony pi... acpi
well... changing the ACPI driven irq is not so straightforward...
irqs are stored in the acpi tables...
1. you could use a customized version of your DSDT doing
cat /proc/acpi/dsdt > raw_dsdt
after that you have to disassemble the obtained file using a specific AML disassembler, correct the device specific irq, compile the newly obtained file and include that in you kernel.
warning: recompiling your DSDT could result in multiple errors due to buggy bios
2. (perhaps better solution) you could just tweak some acpi-irq code to assing another irq if the device matches (read hardcode pcimcia irq assigment).
I'd suggest to take a look to the acpi-devel mailing list as this issue (DSDT overwrite) has been covered many times (sf.net/projects/acpi)
anyway I wouldn't do that a) because irq sharing shouldn't be a problem, b) because acpi driver is not so stable yet and your null event could be fixed soon (try to post your issue on the acpi-devel ML).
hope this helps,
-- mattia
On Wed, 24 Jul 2002 09:49:16 -0500
Jason Friedlander <jf@northwestern.edu> wrote:
> yep, that fixed it, thanks much. now when i unplug and plug the power in or modprobe sonypi i get a null event in orinoco_interrupt (orinoco_cs has been assigned the same IRQ 9). how would i go about changing the irq's? thanks again for the suggestion below, no more panics for me.
>
> On 24 Jul 2002 07:09:58 -0000
> dongili@supereva.it wrote:
>
> >
> > kernel 2.5.x should already include latest kernel patches.
> >
> > anyway there was an issue with the latest one causing panics on many laptops (including many vaios).
> >
> > using acpi kernel patch 20020709 with 2.4.18 or vanilla 2.5.[25|26|27] you should also add this other patch http://www.brodo.de/english/pub/acpi/20020709/nocorruption.2.acpi.diff to fix the panic.
> >
> > I have a gr7/k with acpi+sonypi+cpufreq(speedstep support) and kernel is very stable.
> >
> > bye,
> > -- mattia
> >
--
To UNSUBSCRIBE, email to debian-laptop-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: