Danct12 has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
Danct12 has quit [Ping timeout: 252 seconds]
Danct12 has joined #linux-amlogic
Danct12 has quit [Ping timeout: 260 seconds]
Danct12 has joined #linux-amlogic
Danct12 has quit [Quit: Leaving]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 246 seconds]
f11f12 has joined #linux-amlogic
f11f12 has quit [Client Quit]
ldevulder_ is now known as ldevulder
dagmcr has quit [Quit: Connection closed for inactivity]
GNUtoo has quit [Ping timeout: 255 seconds]
ldevulder has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
elastic_dog has quit [Read error: Connection reset by peer]
elastic_dog has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
naoki has quit [Quit: naoki]
ldevulder has joined #linux-amlogic
ldevulder has quit [Client Quit]
ldevulder has joined #linux-amlogic
vagrantc has joined #linux-amlogic
elastic_dog has quit [Ping timeout: 246 seconds]
elastic_dog has joined #linux-amlogic
<
narmstrong>
ok so something fixed the u-boot crash introduced in a9bf024b2933bba0e23038892970a18b72dfaeb4
ldevulder has quit [Quit: Leaving]
<
vagrantc>
narmstrong: if that's the commit i think it is, i think it was fixed/workedaround by eff444019545642a844431692dd51829aa52528c
<
vagrantc>
wait, no ... that doesn't seem right
<
vagrantc>
or maybe ... 06d514d77c3700ec6166457f58d37652791038d0
<
vagrantc>
basically, the efi stack needed to make sure it's memory didn't get trampled
<
vagrantc>
or other things get trampled by efi...
<
narmstrong>
ok anyway, happy it's fixed, one thing less to handle !
<
vagrantc>
indeed. :)
tolszak has quit [Ping timeout: 264 seconds]
vagrantc has quit [Quit: leaving]
JohnnyonFlame has joined #linux-amlogic
naoki has joined #linux-amlogic
vagrantc has joined #linux-amlogic