> There are two separate issues I encountered with TA (and Measure). One > is the need for patches to the alsa audio to accommodate the special > OLPC hardware modifications.
That would need to be accepted upstream by the alsa project, and then distros will automatically get the changes when they are part of a release. > The other is a means within the Sugar > bundling system to include binaries for multiple architectures. I > actually had written a work-around for the former, but I remain > ignorant about the details of how to best handle the latter. (At one > point, Sascha had helped me include a script that would build the > appropriate binaries at install time, but that solution depends upon a > build environment be installed, which is not the default for most OLPC > systems. Oops.) That would be just a packaging procedure. In the case of Fedora it would be just the arch dependant rpms as opposed to using a activity .xo file which I believe are arch independent. Unless I've missed something here. > Regarding available sensors, Arjun describes some on the Measure page > in the OLPC wiki Thanks! > http://wiki.laptop.org/go/Measure > > There are also many people working on USB sensor input devices that > would be great to support in general. In fedora at least from a driver perspective it would land in Fedora as soon as the upstream kernel has the drivers. I'm not sure whether there is a defined api for accessing those sort sensors on linux. If there was I would presume as the hardware is added that TA/measure would automatically get support for the hardware as its added, if there's not I presume there would need to be individual support added for each device. Peter _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) [email protected] http://lists.sugarlabs.org/listinfo/iaep
