Wolfgang Grandegger wrote:
> Jan Kiszka wrote:
>> Benjamin Zores wrote:
>>> On Mon, 27 Nov 2006 13:11:23 +0100
>>> Wolfgang Grandegger <[EMAIL PROTECTED]> wrote:
>>>> Benjamin Zores wrote:
>>>>> On Mon, 27 Nov 2006 12:21:25 +0100
>>>>> Wolfgang Grandegger <[EMAIL PROTECTED]> wrote:
>>>>>>> Well, I hack a bit my patch to make it compile and the kernel
>>>>>>> already booted.
>>>>>>> Though it hangs when loading the SATA driver.
>>>>>>> I have no idea why atm.
>>>>>> Problems with IRQs?
>>>>> Probably, as when unplugging the SATA drive, the boot goes further
>>>>> but then hang at USB detection (both are handlign IRQs a lot i guess).
>>>>> Would be interesting if someone could test on other board than just
>>>>> mine.
>>>> As I pointed out in my previous mail, the IRQ handling is not yet
>>>> correct for powerpc. Try to correct his first.
>>> The 2.6.19 having been released out, and working much better on my card
>>> than the vanilla 2.6.18 used to be, I'm now more kind to adapt my
>>> patch to
>>> this latest kernel.
>>> However the IRQ handling API seem to have changed a lot
>>> and i was wondering if some work on porting Adeos
>>> (x86/ppc, not yet powerpc of course) patches already have been started
>>> by someone here ?
>> I don't see that PPC is converted to genirq, that new API. And I'm not
>> sure (while not being a PPC expert) if it ever will be, specifically as
>> PowerPC is already on genirq and should obsolete PPC one day, right?
> No, or at least partially wrong. I have to check what the new, fully
> implemented genirq does. But I realized, that the common IRQ structure
> is used now (resulting in some name changes, w.g. ->handler ->chip).
> Likely, PPC and PowerPC already use the new genirq.

It is likely used under PPC as far it has to be: renamed structures,
moved information. But the core issue is if the flow handling (edge,
level, simple etc.) also moved to kernel/irq/chip.c, and that looks to
me like only being the case for PowerPC.


Attachment: signature.asc
Description: OpenPGP digital signature

Xenomai-core mailing list

Reply via email to