-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Apr 08, 2009 at 01:40:57PM +0100, Peter Robinson wrote:
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
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
On Wed, Apr 08, 2009 at 03:44:05AM -0400, Seth Woodworth wrote:
I'd like to encourage everyone to build on the great work of Arjun
Sarwal and help us extend the sensor interface with our peripheral --
the heart rate monitor.
Looks great! As I intended to do a similar device in the future (it's
Alas, the blocker with Measure (and Turtle Art with Sensors) is that
we haven't come to consensus regarding a packaging strategy for the
binary drivers we include for support of the sensor input; these
differ by architecture, which wasn't a problem when we were building
for just one architecture.
Right now this device works primarily with the XO-1, taking advantage
of the AC/DC conversion going on in the XO's audio-in port. But if
the gain were tweaked a bit more it could work with other audio cards.
The fact that it is XO-1 Hardware specific means that packaging for
different
There's generally no issue with hardware specific packages in distros
(there certainly isn't an issue in Fedora), from the quick read I had
of the ticket it looks more like the turtle activity didn't work on
the non XO hardware. I presume that's because it couldn't load the
specific libraries.
Peter,
In the ticket, I was trying to express my ignorance of how to proceed,
but not suggest that the distros haven't dealt with these sorts of
issues in the past.
There are two separate issues I encountered with TA (and Measure). One
is the need for patches to the alsa audio to accommodate the
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
Alas, the blocker with Measure (and Turtle Art with Sensors) is that
we haven't come to consensus regarding a packaging strategy for the
binary drivers we include for support of the sensor input; these
differ by architecture, which wasn't a problem when we were building
for just one
Hi
In a related note
Kristianpaulhttp://co.sugarlabs.org/wiki/index.php?title=Usuario:Kristianpaulaction=editredlink=1of
Sugarlabs .co is testing measure in Soas (with arjun's help) in an
effort
to adapt it to all kinds of hardware.
http://co.sugarlabs.org/go/Sobre_Measure
Rafael Ortiz
On
Walter Bender wrote:
Peter,
In the ticket, I was trying to express my ignorance of how to proceed,
but not suggest that the distros haven't dealt with these sorts of
issues in the past.
There are two separate issues I encountered with TA (and Measure). One
is the need for patches to the
Alas, the blocker with Measure (and Turtle Art with Sensors) is that
we haven't come to consensus regarding a packaging strategy for the
binary drivers we include for support of the sensor input; these
differ by architecture, which wasn't a problem when we were building
for just one
12 matches
Mail list logo