On Sun, Dec 15, 2013 at 08:05:40PM -0500, Nathan C. Riddle wrote:
> On Sun, Dec 15, 2013 at 4:20 PM, Adam Holt wrote:
> > James wrote:
> > > [... that clock battery bricking no longer occurs with latest
> > > firmware, which is also compatible with older operating syst
rom this original 1000+ group (I don't know the stats of what was
> originally received.) Like a G1G1 XO in the US that was booted, used a bit and
> then stored, the Cambodia XOs from this group will brick if stored long enough
> for the clock battery to completely discharge. In Ca
On Mon, Dec 09, 2013 at 10:04:28PM -0500, Richard A. Smith wrote:
> On 12/09/2013 08:07 PM, James Cameron wrote:
> > The symptom is that pressing the power button gives about a one
> > second pulse on the power indicator, then it goes blank. There is
> > no serial cable output from the processor.
On 12/09/2013 08:07 PM, James Cameron wrote:
The symptom is that pressing the power button gives about a one second
pulse on the power indicator, then it goes blank. There is no serial
cable output from the processor.
Take a look at the EC output. It won't be as verbose as later
generation
> discharge rate, and the discharge rate is not under the control of
> > the firmware or the software.
I take that back. There is no _easy_ way.
Thanks to Paul Fox for the idea.
Looking at the datasheet for the CS5536 chip (AMDG_CS5536.pdf), page
475 shows the RTC_CRA register has a div
Hi,
I ran Clock-12.5 on 11.3.1, 12.1.0 and 13.2.0 build 11, all on the
same XO-1, to see if we have any difference in startup time. This is a
GTK2 activity.
Launching 10 times from hot caches and averaging, my measurements are:
11.3.1: 12.52 seconds
12.1.0: 11.53 seconds
13.2.0: 11.74 seconds
It seems okay to me on first reading.
On 6/13/2013 7:53 AM, Daniel Drake wrote:
> Hi Mitch,
>
> As mentioned, upstream now has APBC/APMU clock drivers, and I think there
> are a couple of things in way that clock-dt.c interacts with the common
> clock framework that upstream woul
stream kernels, once
we get to that point. The DT is missing regulator information so the
MMC controller doesn't get powered up. This is the "old firmware, new
kernel" problem.
The DT clock changes described here would also mean that new firmwares
become incompatible with released
daniel wrote:
> Hi Mitch,
>
> As mentioned, upstream now has APBC/APMU clock drivers, and I think there
> are a couple of things in way that clock-dt.c interacts with the common
> clock framework that upstream wouldn't approve of.
>
> Here is my first attempt at
Hi Mitch,
As mentioned, upstream now has APBC/APMU clock drivers, and I think there
are a couple of things in way that clock-dt.c interacts with the common
clock framework that upstream wouldn't approve of.
Here is my first attempt at a new approach, using the new upstream clock
drivers
On Tue, Feb 5, 2013 at 12:47 AM, James Cameron wrote:
> On Mon, Feb 04, 2013 at 03:22:29PM +0200, Christoph Derndorfer wrote:
> > FWIW: Still no luck even though they have been charging for an hour
> > now and automatic power saving is turned off... :-/
> >
> > However seeing that I have to leave
On Mon, Feb 04, 2013 at 03:22:29PM +0200, Christoph Derndorfer wrote:
> FWIW: Still no luck even though they have been charging for an hour
> now and automatic power saving is turned off... :-/
>
> However seeing that I have to leave the office in 2~3 hours to catch
> my plane back home and the la
ch was
>> released in 2007, there's almost no chance of anybody remembering
>> anything useful. It has been more than five years!
>>
>> To verify that the Page Fault is happening because of the known
>> problem (ticket #5391, svn 752), please use the Open Fi
output?
>
> There might be, but if you have a version before Q2D05 which was
> released in 2007, there's almost no chance of anybody remembering
> anything useful. It has been more than five years!
>
> To verify that the Page Fault is happening because of the known
> p
s happening because of the known
problem (ticket #5391, svn 752), please use the Open Firmware ok
prompt to display the values in the real-time clock, using the .clock
command:
ok .clock
If the month is invalid, then the Page Fault is most likely to be the
one expected.
Another method
Hey everyone,
(1) on Friday while looking at one of the XO-1s which didn't show anything
on the display (even with a display which was known to work) with the
serial adapter I saw the attached output.
Looking at the wiki now and given the number of "invalid system date"
issues we saw on other mac
,
> pushed for next build). Since its an odd issue and likely to bite
> again at some point, here are the details:
>
> viafb recently started tweaking the state of the primary (IGA1) and
> secondary (IGA2) clocks and PLLs (e.g. in commit b692a63af8b6).
> It is the tweaking
tweaking the state of the primary (IGA1) and
secondary (IGA2) clocks and PLLs (e.g. in commit b692a63af8b6).
It is the tweaking of the clock state that causes instability. The
clocks in question are configured by IO Port 3C5.1B ("Power Management
Control 1"), bits 5:4 (IGA1) and 7:6 (IG
Signed-off-by: Saadia Baloch
---
arch/arm/configs/xo_175_defconfig |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/configs/xo_175_defconfig
b/arch/arm/configs/xo_175_defconfig
index 875d980..7f41378 100644
--- a/arch/arm/configs/xo_175_defconfig
+++ b/arch/arm
2007. Although we used several right away and
> they worked without any problems...we stored 6 of them away and
> recently discovered that none of the screens turn on when powering up.
> It appears to be the "fix clock" problem and since I live in
> Kyrgyzstan it is too
appears to be the "fix clock" problem and since I live in
Kyrgyzstan it is too expensive to ship back to the US to get them
repaired. I would like to try to fix this myself but it would be great
if I can get more specific instructions for the following (from
http://wiki.laptop.org/go/Fi
daniel wrote:
> Having seen a handful of RTC battery problems in Nicaragua I found
> myself revisiting the process, and struggling to explain the wiki page
> to the team.
>
> So I restructured it a bit, mainly to take the focus away from the
> problems caused by ancient firmware versions and
Having seen a handful of RTC battery problems in Nicaragua I found
myself revisiting the process, and struggling to explain the wiki page
to the team.
So I restructured it a bit, mainly to take the focus away from the
problems caused by ancient firmware versions and badly shaped holders,
and inste
n that socket.
>> Both sig01 and sig02 formats are accepted in the server response. One
>> important point is that the expiry date of any sig02 keys used in the
>> chain are *not* checked at all -- this is because we're assuming the
>> XO clock might not be accurate.
ft_deterrence_protocol#Theft-deterrent_server_response
> Both sig01 and sig02 formats are accepted in the server response. One
> important point is that the expiry date of any sig02 keys used in the
> chain are *not* checked at all -- this is because we're assuming the
> XO clock might not be acc
nction badly) is trusting _less_
clocks in terms of numbers. Each clock with a wider impact if it does
go astray.
>> But the day it happens (that an XS clock is really off) things do go
>> pear-shaped.
>
> Even if they aren't using key delegation?
As you say, if the clients s
any kind of attack, or perhaps I misunderstand
your response.
My point was that there are reasonable setups where the time in the
lease is known to be correct, but that the time on the server that
dishes the leases out over port 191 (the XS) might have a bad clock.
>> Specifically I
we've just only just released a parallel system (multiple keys in
> firmware) which is already being used by multiple countries and can
> realistically be used as an alternative to the delegation system.
Multi-keys and delegation are orthogonal.
> Right now there is no assumption
>2009/8/27 Martin Langhoff :
>>> 4. sig02 leases are still unsupported in the latest OpenFirmware, but
>>> it looks like we have renewed interest in getting this finished off,
>>> so no initramfs changes will be needed in this area.
>>
>> Here Daniel skips the fact that there is a homely but IMO va
pdating the time over port 191, is it OK to ignore the expiry
>> of the sig02 lease? This seems to indicate that anyone who has got
>> hold of the appropriate key material to sign sig02 leases at some
>> point in time is now able to set the clock of any lease-expired XO who
>
s of whether the lease is valid or not.
Yes, the time is asked _after_ we get a response for the lease, but it
has to be set _before_ we validate the lease.
Otherwise, the lease validation would fail with a corrupt clock.
There is a (desired) side-effect to this as well: XOs with marginal
RTC ba
1 can update the hardware clock on the XO. If it received any data
at all in response to the original "" message, the initramfs will
now send a 2nd message to the oats server with the string "time01:
" where the nonce is randomly-generated by the client at
that moment.
The s
1. Project name : Clock - What Time Is It?
2. Existing website, if any : http://wiki.laptop.org/go/Clock_activity
3. One-line description : A clock activity to learn how to tell time.
4. Longer description : The Clock activity aims at two simple goals:
* As a teaching tool
At Mon, 01 Sep 2008 16:38:19 -0400,
Chris Ball wrote:
>
> Hi Bastien,
>
>> is there a Sugar activity displaying a simple clock?
>
> Yes; search for Clock on http://wiki.laptop.org/go/Activities.
>
>> What activities can be used to teach things about t
Hello Bastien
On Mon, Sep 1, 2008 at 3:34 PM, Bastien <[EMAIL PROTECTED]>wrote:
> Dear Chocolate Frosted Sugar Geeks,
>
> is there a Sugar activity displaying a simple clock?
>
> What activities can be used to teach things about time? (seconds,
> minutes, hours, da
Hi Bastien,
> is there a Sugar activity displaying a simple clock?
Yes; search for Clock on http://wiki.laptop.org/go/Activities.
> What activities can be used to teach things about time? (seconds,
> minutes, hours, days, weeks, months, years, decades, centuries...)
I do
Dear Chocolate Frosted Sugar Geeks,
is there a Sugar activity displaying a simple clock?
What activities can be used to teach things about time? (seconds,
minutes, hours, days, weeks, months, years, decades, centuries...)
Is there a simple calendar activity? Can we manipulate the earth
and
C. Scott Ananian wrote:
> On Dec 23, 2007 4:55 PM, Bernardo Innocenti <[EMAIL PROTECTED]> wrote:
>> Jerry Van Baren wrote:
>>
>>> Hmmm, odd. After setting the hwclock with --utc, my /etc/adjtime has
>>> "UTC" but, when I cycled power, my syst
On Dec 23, 2007 4:55 PM, Bernardo Innocenti <[EMAIL PROTECTED]> wrote:
> Jerry Van Baren wrote:
>
> > Hmmm, odd. After setting the hwclock with --utc, my /etc/adjtime has
> > "UTC" but, when I cycled power, my system clock was off by my timezone.
> > Ahh,
Jerry Van Baren wrote:
> Hmmm, odd. After setting the hwclock with --utc, my /etc/adjtime has
> "UTC" but, when I cycled power, my system clock was off by my timezone.
> Ahh, my /etc/adjtime has "0" instead of "UTC" on the second line.
This is probabl
On Dec 22, 2007 10:06 PM, Hal Murray <[EMAIL PROTECTED]> wrote:
> It looks in /etc/sysconfig/clock for the UTC flag. It defaults to local.
>
> My XO doesn't have an /etc/sysconfig/clock
>
> All the Linux boxes I've ever worked with have run with the hardware clock
> OK, setting my hwclock to utc shows /etc/adjtime has "UTC", but after
> rebooting it gets reset to "0" (localtime), causing the incorrect time
> offset.
/etc/init.d/halt calls hwclock to write the current time out to the hardware.
It looks in /etc/sysconfi
Bernardo Innocenti wrote:
> Jerry Van Baren wrote:
>
>> FWIIW, the hardware clock configuration is set to use localtime by
>> default. This can be reconfigured to use UTC (see /etc/rc.sysinit which
>> includes the config file /etc/sysconfig/clock if it exists), but it
Jerry Van Baren wrote:
> FWIIW, the hardware clock configuration is set to use localtime by
> default. This can be reconfigured to use UTC (see /etc/rc.sysinit which
> includes the config file /etc/sysconfig/clock if it exists), but it
> probably isn't worth the effort.
&g
FWIIW, the hardware clock configuration is set to use localtime by
default. This can be reconfigured to use UTC (see /etc/rc.sysinit which
includes the config file /etc/sysconfig/clock if it exists), but it
probably isn't worth the effort.
WRT my previous advice on using hwclock, do *not
;> Is it reasonable to assume that the XO's clock is set correctly?
>>> Specifically I'd like to use python's time.time() to determine which
>>> participant of an activity has been using it the longest.
>>
>> A NetworkManager callout could set it, but
Bernardo Innocenti wrote:
> Joshua Minor wrote:
>> Is it reasonable to assume that the XO's clock is set correctly?
>> Specifically I'd like to use python's time.time() to determine which
>> participant of an activity has been using it the longest.
>
On Dec 22, 2007 3:07 AM, Bernardo Innocenti <[EMAIL PROTECTED]> wrote:
> Joshua Minor wrote:
> > Is it reasonable to assume that the XO's clock is set correctly?
> > Specifically I'd like to use python's time.time() to determine which
> > participant of
Joshua Minor wrote:
> Is it reasonable to assume that the XO's clock is set correctly?
> Specifically I'd like to use python's time.time() to determine which
> participant of an activity has been using it the longest.
A NetworkManager callout could set it, but it seem
> > http://dev.laptop.org/~yoshiki/etoys/Clock.004.pr
> >
> > One way or another, please load it onto Etoys (on a non-XO
> > environment, drag-and-drop from Finder or Explorer. On XO, access the
> > URL with browse, copy it to a USB memory and resume it from Jou
On Nov 16, 2007, at 19:54 , Yoshiki Ohshima wrote:
>>> http://dev.laptop.org/~yoshiki/etoys/Clock.004.pr
>>>
>>> One way or another, please load it onto Etoys (on a non-XO
>>> environment, drag-and-drop from Finder or Explorer. On XO,
>>> acc
On Nov 16, 2007, at 6:15 , Yoshiki Ohshima wrote:
> http://dev.laptop.org/~yoshiki/etoys/Clock.004.pr
>
> One way or another, please load it onto Etoys (on a non-XO
> environment, drag-and-drop from Finder or Explorer. On XO, access the
> URL with browse, copy it to a USB me
Hello,
After having a conversation with one of my colleague (Ian), I
couldn't resist, and I happened to have some spare time while helping
a TA as an unofficial TA. So I made a Clock project in Etoys.
The file is available at:
http://dev.laptop.org/~yoshiki/etoys/Clock.004.pr
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
1. Project name : Clock
2. Existing website, if any : None
3. One-line description : It's a clock.
4. Longer description : It shows 24-hour digital time, 12-hour analog
time, and auto-localized date. Digital time and a
54 matches
Mail list logo
