Eric W. Biederman wrote:
* Vectors 0x20-0x2f are used for ISA interrupts. */ -#define IRQ0_VECTOR FIRST_EXTERNAL_VECTOR +#define IRQ0_VECTOR FIRST_EXTERNAL_VECTOR + 0x10 #define IRQ1_VECTOR IRQ0_VECTOR + 1 #define IRQ2_VECTOR IRQ0_VECTOR + 2 #define IRQ3_VECTOR IRQ0_VECTOR + 3 @@ -82,7 +87,7 @@
I think we have a dependency in i8259.c that irq0 is mapped to vector 0x20. --Mika - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 13/14] x86_64 irq: Safely cleanup an irq after moving it.
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH 13/14] x86_64 irq: Safely cleanup an irq after moving it.
- References:
- Re: What are the real ioapic rte programming constraints?
- From: [email protected] (Eric W. Biederman)
- Re: What are the real ioapic rte programming constraints?
- From: Zwane Mwaikambo <[email protected]>
- Re: What are the real ioapic rte programming constraints?
- From: [email protected] (Eric W. Biederman)
- Re: What are the real ioapic rte programming constraints?
- From: Zwane Mwaikambo <[email protected]>
- Re: What are the real ioapic rte programming constraints?
- From: [email protected] (Eric W. Biederman)
- Conclusions from my investigation about ioapic programming
- From: [email protected] (Eric W. Biederman)
- [PATCH 0/14] x86_64 irq related fixes and cleanups.
- From: [email protected] (Eric W. Biederman)
- [PATCH 01/14] x86_64 irq: Simplfy __assign_irq_vector
- From: [email protected] (Eric W. Biederman)
- [PATCH 02/14] irq: Remove set_native_irq_info
- From: [email protected] (Eric W. Biederman)
- [PATCH 03/14] x86_64 irq: Kill declaration of removed array, interrupt
- From: [email protected] (Eric W. Biederman)
- [PATCH 04/14] x86_64 irq: Remove the unused vector parameter from ioapic_register_intr
- From: [email protected] (Eric W. Biederman)
- [PATCH 05/14] x86_64 irq: Refactor setup_IO_APIC_irq
- From: [email protected] (Eric W. Biederman)
- [PATCH 06/14] x86_64 irq: Simplfiy the set_affinity logic.
- From: [email protected] (Eric W. Biederman)
- [PATCH 07/14] x86_64 irq: In __DO_ACTION perform the FINAL action for every entry.
- From: [email protected] (Eric W. Biederman)
- [PATCH 08/14] x86_64 irq: Use NR_IRQS not NR_IRQ_VECTORS
- From: [email protected] (Eric W. Biederman)
- [PATCH 09/14] x86_64 irq: Begin consolidating per_irq data in structures.
- From: [email protected] (Eric W. Biederman)
- [PATCH 10/14] x86_64 irq: Simplify assign_irq_vector's arguments.
- From: [email protected] (Eric W. Biederman)
- [PATCH 11/14] x86_64 irq: Remove unnecessary irq 0 setup.
- From: [email protected] (Eric W. Biederman)
- [PATCH 12/14] x86_64 irq: Add constants for the reserved IRQ vectors.
- From: [email protected] (Eric W. Biederman)
- [PATCH 13/14] x86_64 irq: Safely cleanup an irq after moving it.
- From: [email protected] (Eric W. Biederman)
- Re: What are the real ioapic rte programming constraints?
- Prev by Date: Re: [PATCH 05/44 take 2] [UBI] internal common header
- Next by Date: Re: [patch 3/3] mm: fix PageUptodate memorder
- Previous by thread: [PATCH 13/14] x86_64 irq: Safely cleanup an irq after moving it.
- Next by thread: Re: [PATCH 13/14] x86_64 irq: Safely cleanup an irq after moving it.
- Index(es):
 |