|
From: c3kkos <c3...@ho...> - 2009-04-07 07:21:29
|
I know i'm filling up your mailboxes but this is now n open challenge for me.
Here i have cat'ed my /proc/interrupts:
CPU0
0: 11869 XT-PIC-XT timer
1: 377 XT-PIC-XT i8042
2: 0 XT-PIC-XT cascade
3: 2 XT-PIC-XT
4: 2 XT-PIC-XT
5: 0 XT-PIC-XT ES1938, mach64@pci:0000:01:00.0
6: 5 XT-PIC-XT floppy
7: 2 XT-PIC-XT
8: 2 XT-PIC-XT rtc0
9: 0 XT-PIC-XT acpi
10: 5 XT-PIC-XT
11: 743 XT-PIC-XT uhci_hcd:usb1, yenta, yenta
12: 4472 XT-PIC-XT i8042
14: 2659 XT-PIC-XT ide0
15: 1473 XT-PIC-XT ide1
NMI: 0 Non-maskable interrupts
LOC: 0 Local timer interrupts
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
TRM: 0 Thermal event interrupts
SPU: 0 Spurious interrupts
ERR: 0
MIS: 0
----------------------------------------------------------
it's now clear that i'm facing a irq problem. indeed the drm module does not
like sharing the bus with
the audio data trunks. I think trying to have a different pci latency
timings setup is a waste of time. The bios does not have any option to
manipulate the plug-n-play system..
IRQ 5 is bound to the SOLO-1 at boot time and is bound again to the
drm/mach64 when xorg load up his modules.
I've to find out how i can modify the solo-1 irq assignment via software..
cause the other way is the old "jumpers way" but since i'm using a
notebook.. i can hardly think there're some upon my hardware..
any suggestions? i've looked for a script set called rtirq that maybe can be
useful but it can be used, as the name already tells, with the real-time
kernels..
Ahuuuuuu!!!!!!!!
--
View this message in context: http://www.nabble.com/mach64-kernel-modules-for-2.6.26-kernel-tp22668419p22922682.html
Sent from the mesa3d-users mailing list archive at Nabble.com.
|