Re: [U-Boot] [PATCH 10/15] x86: quark: Assign a unique I/O APIC ID

2016-05-23 Thread Bin Meng
On Mon, May 23, 2016 at 8:19 AM, Simon Glass wrote: > On 22 May 2016 at 02:45, Bin Meng wrote: >> After power-on, both LAPIC and I/O APIC appear with the same APIC ID >> zero, which creates an ID conflict. When generating MP table, U-Boot >> reports zero as the LAPIC ID in the processor entry, an

Re: [U-Boot] [PATCH 10/15] x86: quark: Assign a unique I/O APIC ID

2016-05-22 Thread Simon Glass
On 22 May 2016 at 02:45, Bin Meng wrote: > After power-on, both LAPIC and I/O APIC appear with the same APIC ID > zero, which creates an ID conflict. When generating MP table, U-Boot > reports zero as the LAPIC ID in the processor entry, and zero as the > I/O APIC ID in the I/O APIC as well as the

[U-Boot] [PATCH 10/15] x86: quark: Assign a unique I/O APIC ID

2016-05-22 Thread Bin Meng
After power-on, both LAPIC and I/O APIC appear with the same APIC ID zero, which creates an ID conflict. When generating MP table, U-Boot reports zero as the LAPIC ID in the processor entry, and zero as the I/O APIC ID in the I/O APIC as well as the I/O interrupt assignment entries. Such MP table c