[coreboot] how to assign irq to a device
Marc Jones
marcj303 at gmail.com
Wed Oct 10 18:25:36 CEST 2012
On Wed, Oct 10, 2012 at 7:19 AM, WANG Siyuan <wangsiyuanbuaa at gmail.com> wrote:
> hi, ali
> thank you. this is an Ethernet controller plugged in PCI slot. maybe it is
> also called LAN card.
> this card is not plugged in USB slot, it is plugged in PCI slot.
> so I think the irq is not right.
>
> On Wed, Oct 10, 2012 at 7:34 PM, ali hagigat <hagigatali at gmail.com> wrote:
>
>> External PCI network adaptor?
>> If it is plugged in PCI slot so it is internal. Is it a LAN card
>> plugged into USB slot?
>>
>> On Wed, Oct 10, 2012 at 2:41 PM, WANG Siyuan <wangsiyuanbuaa at gmail.com>
>> wrote:
>> > hi,
>> > i am debugging a mainboard with an external pci network adapter.
>> > the adapter share irq with usb. it seems not correct, so i want to assign
>> > an irq for this adapter.
>> > how to do that?
>> > thank you.
>> >
>> > /proc/interrupt
>> > eth1 is an external pci network adapter. i want to assign irq 21 for it.
>> >
>> > CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
>> > CPU6 CPU7
>> > 0: 59 0 0 0 0 0
>> > 0 0 IO-APIC-edge timer
>> > 1: 0 0 1 0 1 1
>> > 0 0 IO-APIC-edge i8042
>> > 7: 1 0 0 0 0 0
>> > 0 0 IO-APIC-edge
>> > 8: 0 0 0 0 0 0
>> > 0 0 IO-APIC-edge rtc0
>> > 9: 0 0 0 0 0 0
>> > 0 0 IO-APIC-fasteoi acpi
>> > 12: 0 0 0 1 1 0
>> > 1 1 IO-APIC-edge i8042
>> > 14: 0 0 0 0 0 0
>> > 0 0 IO-APIC-edge pata_atiixp
>> > 15: 0 0 0 0 0 0
>> > 0 0 IO-APIC-edge pata_atiixp
>> > 16: 93 95 80 91 96 94
>> > 98 97 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4
>> > 17: 1 0 1 0 0 0
>> > 0 0 IO-APIC-fasteoi ehci_hcd:usb1
>> > 18: 4 4 4 4 4 4
>> > 2 4 IO-APIC-fasteoi ohci_hcd:usb5, ohci_hcd:usb6,
>> > ohci_hcd:usb7
>> > 19: 1 1 0 0 0 0
>> > 0 0 IO-APIC-fasteoi ehci_hcd:usb2, eth1
>> > 22: 672 685 691 692 693 683
>> > 687 681 IO-APIC-fasteoi ahci
>> > 296: 119 99 127 87 125 96
>> > 121 105 PCI-MSI-edge eth0-rx-0
>> > 297: 0 0 0 0 0 0
>> > 0 0 PCI-MSI-edge eth0-tx-0
>> > 298: 1 0 0 0 0 0
>> > 0 0 PCI-MSI-edge eth0
>> > 299: 123 125 105 138 93 135
>> > 106 132 PCI-MSI-edge eth2-rx-0
>> > 300: 2 4 4 0 1 2
>> > 1 3 PCI-MSI-edge eth2-tx-0
>> > 301: 0 0 1 0 0 0
>> > 0 2 PCI-MSI-edge eth2
>> > NMI: 0 0 0 0 0 0
>> > 0 0 Non-maskable interrupts
>> > LOC: 4050 1673 3943 2348 2519 2963
>> > 3093 1644 Local timer interrupts
>> > SPU: 0 0 0 0 0 0
>> > 0 0 Spurious interrupts
>> > PMI: 0 0 0 0 0 0
>> > 0 0 Performance monitoring interrupts
>> > IWI: 0 0 0 0 0 0
>> > 0 0 IRQ work interrupts
>> > RTR: 0 0 0 0 0 0
>> > 0 0 APIC ICR read retries
>> > RES: 5454 4177 5477 3690 5121 3822
>> > 5342 3630 Rescheduling interrupts
>> > CAL: 44 58 52 57 46 56
>> > 50 59 Function call interrupts
>> > TLB: 291 391 291 336 274 344
>> > 237 395 TLB shootdowns
>> > TRM: 0 0 0 0 0 0
>> > 0 0 Thermal event interrupts
>> > THR: 0 0 0 0 0 0
>> > 0 0 Threshold APIC interrupts
>> > MCE: 0 0 0 0 0 0
>> > 0 0 Machine check exceptions
>> > MCP: 6 6 6 6 6 6
>> > 6 6 Machine check polls
>> > ERR: 1
>> > MIS: 0
>> >
>> >
>> > --
>> > WANG Siyuan
>> > --
>> > coreboot mailing list: coreboot at coreboot.org
>> > http://www.coreboot.org/mailman/listinfo/coreboot
>>
>
>
>
> --
> WANG Siyuan
> --
> coreboot mailing list: coreboot at coreboot.org
> http://www.coreboot.org/mailman/listinfo/coreboot
It sounds like you have to update the ACPI IRQ routing.
Marc
--
http://se-eng.com
More information about the coreboot
mailing list