>On Thu, 2010-12-09 at 17:20 -0800, Mark Pearson wrote:
>> Magical - thank you very very much. The patch fixes the problem
>>
>> Really appreciate the quick response - and I would never have found that
>in a million years.
>
>No worries.
>
>Looks like someone should send 78e2e68a2b to the stable cr
On Thu, 2010-12-09 at 17:20 -0800, Mark Pearson wrote:
> Magical - thank you very very much. The patch fixes the problem
>
> Really appreciate the quick response - and I would never have found that in a
> million years.
No worries.
Looks like someone should send 78e2e68a2b to the stable crew. F
: Mark Pearson
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Problem with MPC8536 and external IRQs when using a loadable
kernel module
On Thu, 2010-12-09 at 12:45 -0800, Mark Pearson wrote:
> I have a curious problem. This is on a MPC8636 based platform with
> 36-bit address space (that may
On Thu, 2010-12-09 at 12:45 -0800, Mark Pearson wrote:
> I have a curious problem. This is on a MPC8636 based platform with
> 36-bit address space (that may or may not be important).
>
>
>
> I have a very simple driver that registers for one of the external
> IRQs with a trivial interrupt handl
I have a curious problem. This is on a MPC8636 based platform with
36-bit address space (that may or may not be important).
I have a very simple driver that registers for one of the external IRQs
with a trivial interrupt handler. It works great when built in as part
of the kernel.
However,
