I agree this may represent something different about how our Linux
kernel is rebooting.
Could you please test with older operating system releases against the
same latest firmware?
Alas, the spurious lid message is not build dependent but FW version
dependent. The issue begins at Q2F12.
On Wed, Aug 29, 2012 at 04:02:38AM -0400, Kevin Gordon wrote:
Alas, the spurious lid message is not build dependent but FW version
dependent. The issue begins at Q2F12. Q2F11 does not display the
message on either 11.3.1 builds 883 or 12.1.0 build 20. With Q2F12
and Q2F13, it does occur,
Hi,
The primary need is for the XOs in the school to have the same time (to
a few seonds, even a minute or so, is probably ok. The primary need is
to have information from the XOs be somewhat consistent. The school
server time should also be accurate to a few minutes, of course.
At the
On Wed, Aug 29, 2012 at 4:21 AM, James Cameron qu...@laptop.org wrote:
On Wed, Aug 29, 2012 at 04:02:38AM -0400, Kevin Gordon wrote:
Alas, the spurious lid message is not build dependent but FW version
dependent. The issue begins at Q2F12. Q2F11 does not display the
message on either
In the end it turns out it does make sense for the sensor (accessible
under /camera-i2c) and the camera (/camera) to be separate.
But Mitch identified the optimal DT layout where the sensor is defined
in the DT at /camera-i2c/image-sensor, which causes i2c-gpio to probe
the ov7670 driver directly.
On Wed, Aug 29, 2012 at 1:59 PM, Daniel Drake d...@laptop.org wrote:
In the end it turns out it does make sense for the sensor (accessible
under /camera-i2c) and the camera (/camera) to be separate.
But Mitch identified the optimal DT layout where the sensor is defined
in the DT at
On Wed, Aug 29, 2012 at 2:22 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
We'll be probably qualifying siv120d for XO-4 production as well. How
do we handle this situation?
So far, OFW didn't need to know which one was installed; the
mmp-camera driver was loading both ov7670 and
Hi,
If you connect an XO to a different school server, you will get an known
host error. The solution is to use the Terminal activity and enter:
cd (cd with no parameters goes to the user's home folder).
rm -rf .ssh/known_hosts
ssh admin@schoolserver
You should get a question whether to
Hi,
Peru has the advantage that it and OLPC know the origins of the
computers. The 100 XO-1.5s at Saint Jacobs are of unknown (to us)
origin. I have tried to find someone who might have the original
manufacturer's spreadsheets, but no one seems to know anything about them.
What I am hearing
