VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- Springboard Modules (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=10)
-- Springboard for Springboards (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=5014)

Does the specs for the springboard allows
some springboard to hold other springboards?
I can imagine there will be some useful
springboards that can be produced very small
and so it would be a waste to eat up the
whole slot. Also, how robust is the connector
when hving a few useful springboards and I always have to change them around and around.

The connector is the same one used by PCMCIA devices. I haven't heard of any problems with those.

Springboards basically get a view of the CPU bus, and two pins that remind them the bus is talking to THEM (chip select 0 and one).

Reading the dev info it looks like CS0 is expected to be memory (a ROM, or FLASH), and in fact the first hundrad bytes or so have to have a special header. It is expected that CS0 have the programs that drive the hardware, or just hold code/data on "ROM only" springboards. It is expected, but not required that CS1 have the hardware interface.

You could make a springboard that used CS0 and passed CS1 onto the next springboard as CS0. You could even fit both your program and your hardware in CS0. Unfortunitly you would only be able to support another Springboard that only uses CS0, not both CS0 and CS1. However I'm not sure who would want something compatable with "most memory springboards, and a few other random things".

Doing anything else would be a rather large kludge, for example send everything on to the "next" springboard *unless* you see 15 reads in a row for the first byte on CS0, then switch to showing your springboard until....

If there were anything intresting you could do without talking to the Palm device (say just suplying power) doing a pass through would be easy, but I'm not sure you could make any intresting devices that way.