<tuxbrain>
thanks xianfu, I will test procedures once the build I runing right now (wich I guess is a mixture of both :P) finish :), I need a full toolchain with qt, if the mixture brings it to me I will be fine :)
<tuxbrain>
damn it, I have not remove the /CONFIG_ALL=y option ... I'm building the whole repo , the good thing is that if successful builds I will ha a damn complete toolchain with all libs aviable on openwrt :P
<tuxbrain>
is building since 7:00AM now is 16:00
<jow_laptop>
tuxbrain: you can just abort, disable config_all and continue
<tuxbrain>
yeah I can but... I love to see my machine working :P, and I'm courious how much space the FULL toolchain will arrive.
<tuxbrain>
after if finish I will do a "just image build" and compare
<tuxbrain>
yes I need new glasses, xMff I can be a real PITA isn't it? any advance on avr tools ported to openwrt you experience any problem?
<viric>
lars_: 2.6.36 is the only vanilla kernel that runs on the nanonote? Do .37 and .38 work as is?
<lars_>
.37 does
<lars_>
.38 does not
<viric>
ok
<viric>
lars_: can you point me to some document that talks about 'the hardware has a problem that makes suspend-to-ram fail after some time suspended'
<lars_>
not really, afaic it was only discussed here
<viric>
mh
<viric>
and what does it require to become 'sure' it is a hardware problem?
<lars_>
a hw fix
<viric>
:)
<viric>
How have been the attempts to fix it, to decide 'it's a hardware problem'?
<lars_>
i don't think so.
<lars_>
we can work around it in sw, by wakeing it up with the rtc clock from time to time
<viric>
I was told here you (and some other people here) think it is a hardware problem
<viric>
What happens with that rtc clock?
<lars_>
i assume, that it is a hardware problem, because it doesn't occur on other jz4740 based devices.
<lars_>
the rtc clock would wake up the device
<viric>
isn't the rtc clock in the jz4740?
<lars_>
hm?
<viric>
hm
<lars_>
yes
<lars_>
but you'd wake up the device before the problem occurs
<viric>
you mean a problem of the jz4740 in the nanonote, or a problem out of the jz4740?
<lars_>
after two hours
<lars_>
i guess it's a problem of the nanonote circuit
<viric>
but noone found out what problem still
<wpwrak>
do we know if the work-around eliminates the problem reliably ? or are there unintended side-effects ?
<lars_>
i'm not sure if anybody tested it yet extensivly
<viric>
What I tested was to suspend
<viric>
wait some hours, and try to wake it up
<viric>
and it was *off*
<viric>
I had to power it up as if it was off.
<viric>
Is this the behaviour you saw?
<viric>
it did not look hanged. I expected to find it hanged
<lars_>
why?
<viric>
I've no idea. I imagined that :)
<viric>
here people simply said 'it does not work'
<kristianpaul>
old gps-receivers (1990) we're prety valuable for hacking