cmuller__ has joined #linux-exynos
cmuller__ has quit [Ping timeout: 240 seconds]
cmuller__ has joined #linux-exynos
afaerber has joined #linux-exynos
cmuller__ has quit [Remote host closed the connection]
<ssvb> Wizzup: nice, another picture of a swollen chromebook battery there :) so I was not the only one to have this problem
<Wizzup> yeah
<ssvb> still I don't quite understand what was their problem with odroids
<ssvb> they mention sd card issues and presume that the problems are heat related
<ssvb> but if they are using sd cards for the rootfs, then they are likely just reaching the erase cycle limits by nonstop reading/writing too much
<swabbles> Wizzup: new day, new insights.
<Wizzup> swabbles: Ah?
<swabbles> I think the kernel is just fine, except that we can't set the rootfs yet (for which we want nv u-boot or abuse the environment of the default u-boot).
<Wizzup> ssvb: I also blamed sd cards for my cubie2 failing, but I'm thinking that may not be the case -- I find that the IO mostly just halts/stops, but i'm not ready to blame the sd card because it is new and works in other devices
<Wizzup> but I think this may be the memory clock etc. being too high on cubie2
<Wizzup> I'll try that later
<swabbles> But I suspect the nv u-boot binaries on the website are simplefb ones for some reason.
<Wizzup> anyway </offtopic>
<Wizzup> swabbles: :-)
<swabbles> Which may explain why it isn't working.
<swabbles> But the thing I don't understand is why do they create an entire flash map image.
<swabbles> To later just extract the U-Boot part (which is either u-boot.bin or u-boot.bin + fdt).
<swabbles> Because wrapping up u-boot.bin and signing the image doesn't seem to work :/.
rz2k has joined #linux-exynos
<WarheadsSE> ssvb: this is why we use USB3 -> SATA to SSDs for our farm full of XUs
<WarheadsSE> we've gone through 4 models to find an adapter** that wouldn't overheat
<ssvb> WarheadsSE: that's interesting, which adapter ended up being the best?
<ssvb> WarheadsSE: currently I use a buffalo ministation usb3 hard drive with my chromebook, did not have any problems with it yet
<ssvb> WarheadsSE: but it is not stressed 24/7, so this does not really mean anything :)
robclark has quit [Ping timeout: 260 seconds]
robclark has joined #linux-exynos
libv has quit [Ping timeout: 260 seconds]
libv has joined #linux-exynos
libv has quit [Ping timeout: 260 seconds]
libv has joined #linux-exynos
<WarheadsSE> ssvb: let me check on the adapter
libv_ has joined #linux-exynos
<WarheadsSE> looks like we end up with Anker's
<WarheadsSE> Dropped you a pic
libv has quit [Ping timeout: 260 seconds]
libv_ is now known as libv
rz2k has quit []
<swabbles> Going to try emerging the bootimage stuff using a chromium dev environment.
<swabbles> I'm wondering if I can reproduce a working nv u-boot.
afaerber has quit [Quit: Verlassend]
meridion has quit []
kspaans has quit [*.net *.split]
kspaans has joined #linux-exynos
WarheadsSE has quit [*.net *.split]
WarheadsSE has joined #linux-exynos
<RSpliet> robclark: how close is the stiH41x to the av8100 on the old STEricsson U8500 SoC?
<RSpliet> oh wait
<RSpliet> not your driver :p
<robclark> RSpliet, no idea.. probably ask benjiG ;-)
<robclark> heheh
<RSpliet> I might just do that one day ;-)
<RSpliet> ugh, so many fun projects
<RSpliet> so little time :)