Re: pSeries boot failure due to wrong interrupt controller

2015-06-26 Thread Jeremy Linton
Ping? Anyone? I'm adding ppc-dev to see if anyone there is interested in picking up the patch.. Thanks, Jeremy Ok so I messed up the formatting a little and was lazy and didn't checkpatch it cause I mean, it was 1 line! If someone wants it resent I will do so. On 6/23/2015 8:42

Re: pSeries boot failure due to wrong interrupt controller

2015-06-26 Thread Jeremy Linton
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/26/2015 4:54 PM, Benjamin Herrenschmidt wrote: Ah I missed that completely. From your discussion, it looks correct, I'll see if I can find a machine to test, however I think we dropped support for POWER3 so it might be non-trivial to do so.

Re: pSeries boot failure due to wrong interrupt controller

2015-06-26 Thread Benjamin Herrenschmidt
On Fri, 2015-06-26 at 12:54 -0500, Jeremy Linton wrote: Ping? Anyone? I'm adding ppc-dev to see if anyone there is interested in picking up the patch.. Ah I missed that completely. From your discussion, it looks correct, I'll see if I can find a machine to test, however I think we dropped

Re: pSeries boot failure due to wrong interrupt controller

2015-06-23 Thread Rob Herring
+Grant On Mon, Jun 22, 2015 at 2:44 PM, Jeremy Linton lintonrjer...@gmail.com wrote: The OF IRQ logic was refactored a while back, and it appears that it broke the case where a device doesn't have an interrupt-map (legacy/ISA platform peripherals). In particular on the older pSeries platforms

pSeries boot failure due to wrong interrupt controller

2015-06-22 Thread Jeremy Linton
The OF IRQ logic was refactored a while back, and it appears that it broke the case where a device doesn't have an interrupt-map (legacy/ISA platform peripherals). In particular on the older pSeries platforms the console serial port (keyboard/etc) is attached via a Winbond super I/O controller.