Quote:
If you need help with the schematics
I can't give you the Efika schematics :D
Quote:
A way to find out which of the power supply lines is used for the IRDA port is with a multimeter...
It's a PC standard IrDA connector. The Specification page links to the connector format. It's like that. The pin marked N/A is actually a GPIO wakeup pin or UART CTS depending on port config. That's the only difference (but it's not relevant to IrDA, this is a throwback to the original MPC5200 chip which had a more dedicated IrDA controller)
Quote:
shutdown my web server (yes, it's true! :-) ) and disassemble the box to reach the connectors.
You would have to do that to use them anyway. Shorting connectors while the board is on could fry the MPC5200B.
Absolutely 100% of the information required to use the exposed ports on the board is in the manual. Some clever guesswork and conservative software management can expose some more.
Quote:
By the way, do you know whether the "hard switch off" (by pressing the "Power On" button for 5s) is implemented in HW or SW? I mean if it is done by some resource on the board or by the OFW? It's a critical piece of info for the ACPI emulation in the post that originated this thread.
It's part of the ATX power supply standard, if you hold the switch long enough the PSU will turn itself off. If there is any software control it is handled by the onboard PIC/nvram controller which you *must not even consider touching under any circumstance*.
Do not emulate ACPI. ACPI is plug and play and power management scripting, and device abstraction. Open Firmware does this for you. There is no need for AML or interrupt emulation. Support Open Firmware instead, and the MPC5200B specification. There are plenty of hooks in drivers for power management and configuration via the device tree.
To shut down the Efika using software, simply write a driver which uses the PSC6 pins and reconfigures them for GPIO. You have a voltage, ground and 3 GPIO on that connector, two of which can cause a hardware interrupt.
This is how Sylvain Munaut's "deep sleep" driver works, however in reverse (GPIO wakeup handles it automatically, any wakeup interrupt source will restore the MPC5200B to "normal" mode). Simply capture that interrupt in a Linux driver. You will get a real hardware power switch (connected to PWR pins) and a software controlled switch which can be configured how you like. There are even enough pins left over for I2C control so you can connect a PIC on a piece of breadboard if you need fancier control or other operations.