PCMCIA support for 860
Hi
Thanx for the answers...
I patched the files mpc8xx.h and init.c as you wrote. Then I recompiled the kernel (2.2.13, including fpu, damm, bossek patches) and restarted it. Then I used the rc.pcmcia to set the modules up. It fails because of...
sh-2.03# ./rc.pcmcia start
Starting PCMCIA services: modules/lib/modules/2.2.13/pcmcia/pcmcia_core.o:
unresolved symbol request_8xxirq /lib/modules/2.2.13/pcmcia/i82365.o: /lib/modules/2.2.13/pcmcia/i82365.o: No such file or directory/lib/modules/2.2.13/pcmcia/ds.o: unresolved symbol proc_pccard /lib/modules/2.2.13/pcmcia/ds.o: unresolved symbol CardServices
cardmgr.
sh-2.03# cardmgr[67]: starting, version is 3.1.10
cardmgr[67]: no pcmcia driver in /proc/devices
cardmgr[67]: exiting
I suppose that I should find the missing request in /proc/ksyms. But there ain't nothing like this:
sh-2.03# cat /proc/ksyms | grep requestc0019478 request_modulec00e8f50 wait_for_requestc00ac2d0 make_requestc0008d6c request_irqc000eb04 request_dmac0016ac0 request_regionc00e5898 io_request_lockc00acd30 end_that_request_firstc00ace3c end_that_request_last
sh-2.03# cat /proc/ksyms | grep 8xx
sh-2.03#
Does someone have a clue on that? Is request_irq and request_8xxirq related??
--
Best regards
Ruedi Hofer
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Ruedi Hofer <[email protected]> writes:
Hi,
Quoted 7 lines
I patched the files
mpc8xx.handinit.cas you wrote. Then I recompiled the kernel (2.2.13, including fpu, damm, bossek patches) and restarted it. Then I used the rc.pcmcia to set the modules up. It fails because of...sh-2.03# ./rc.pcmcia start
Starting PCMCIA services:modules/lib/modules/2.2.13/pcmcia/pcmcia_core.o:
unresolved symbolrequest_8xxirq
[snip]
Quoted 1 line
Does someone have a clue on that? Is
request_irqandrequest_8xxirqrelated??
Just stuff an:
EXPORT_SYMBOL(request_8xxirq);
into arch/ppc/kernel/ppc_ksyms.c and it should work.
//Marcus
--
Signature under construction, please come back later.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Quoted 4 lines · Marcus Sundberg
Quoted 1 line · Ruedi Hofer
Does someone have a clue on that? Is
request_irqandrequest_8xxirqrelated??
Sort of. The MPC8xx has an internal interrupt controller. The Linux community seems to think the world is 8259s and PCI/ISA bus. Mapping request_irq into the 8xx interrupt controller was attempted, but didn't provide the proper results. The request_8xxirq function is used by all integrated device drivers (serial, Ethernet, TDM/audio, USB, SPI, I2C, PCMCIA, general purpose I/O pins, etc.), as they know they are using the internal interrupt controller.
In the case of boards with PCI/ISA bridges, the request_irq is also enabled because there is a downstream 8259 controller. Not defining this when there is no 8259 causes drivers that would attempt to use this to fail. It is nice to know this at build time, rather than wondering why things are crashing or not working once the system is booted.
This also presents a challenge for PCMCIA devices. All of these drivers (or supporting functions) want to install interrupt handlers using request_irq, which doesn't make sense on the 8xx. I have the ATA/IDE patch to install the interrupt handler, but other devices may also need interrupt handler patches.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/