Using request_8xxirq

Using request_8xxirq

[Kwansuk Kim]

I have redhat's embbed linux kernel 2.2.13.

I ported it on my custom board (which has MPC860 CPU), and for studying the device driver I recompiled the kernel with loadable module.

There were some error, because some unused modules symbols are exported ( e.g., PCI driving symbols). I think I can omit them.

But among the unused symbols there was request_irq.

I searched the request_irq, and I found there was request_8xxirq instead of request_irq. In DRIVERS\CHAR\SERIAL.C file I found this define state.

"#define request_irq request_8xxirq"

and in ARCH\PPC\KERNEL\IRQ.C,

#ifndef CONFIG_8xx
int request_irq(unsigned int irq, void (*handler)(int, void *, struct pt_regs *),
#else
int request_8xxirq(unsigned int irq, void (*handler)(int, void *, struct pt_regs *),
#endif

I wonder whether request_8xxirq can work same as request_irq, and all modules work with request_8xxirq.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: Using request_8xxirq

[Dan Malek]

Kwansuk Kim wrote:

> "#define request_irq request_8xxirq"

Bad, bad, bad.....

> I wonder whether request_8xxirq can work same as request_irq, and all modules work with request_8xxirq.

It does not work the same, which is why there is a different function
with a different name.  The drivers that use the request_irq function
assume PC 8259 type interrupt numbers, which is completely inappropriate
for the internal 8xx interrupt controller.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/