Mitch, > It turns out that there is a GPIO driver - the source is in > char/drivers/cs5535_gpio.c - and it is available as a kernel module: > > modprobe cs5535_gpio > > However, nobody that I asked knows how to use it (it doesn't appear in > /dev/ after you modprobe it, and the correspondence between write() > calls to that driver and specific operations on the GPIO register block > isn't clear). > > And in any case, accessing this behind alsamixer's back is not a good > idea, because then alsamixer will be confused about the state. > > All in all, I think it's better to call alsamixer to do the work, so the > state remains consistent between applications.
Hmm, ok. We sure don't want to give the Squeak VM more permission that it should have, and as you said, bypassing alsamixer wouldn't be good either. For now, we can try it with calls to system(), assuming the other environment variables for the "etoys" command invocation is sane. Thank you! -- Yoshiki _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
