<LiquidAcid>
pokazef, your problem sounds similar, you can double-check by attaching the cable after the device "hangs", if you then find yourself on the u-boot prompt it would a pretty strong indicator that you'r seeing the same issue
<pokazef>
LiquidAcid: I'll check that symptom when I resume working on it, thanks for the tip.
<pokazef>
LiquidAcid: But as I recall, I wasn't getting any response whatsoever when attaching the serial adapter on the fly.
<LiquidAcid>
pokazef, not even an echo?
<LiquidAcid>
pokazef, that you won't get any direct output is obvious (if we assume that you're on the uboot prompt)
<pokazef>
LiquidAcid: Oops, my bad. It seems I'm on the u-boot prompt.
<pokazef>
LiquidAcid: I'll try applying your patch to u-boot and see how that goes.
<pokazef>
LiquidAcid: But not today, though. I need to clear my head first.
<pokazef>
How can this kind of problem happen with one power supply and not happen with another?
krzk has quit [Quit: Ex-Chat]
<pokazef>
It reminds me a little of my Raspberry Pi days, when every USB bug was blamed on a faulty power supply :)
<LiquidAcid>
pokazef, iirc the issue occured randomly -- since it disappears as soon as ethernet or hdmi is connected i would assume that it's a grounding issue with the pmic
prahal has quit [Ping timeout: 244 seconds]
prahal has joined #linux-exynos
masta has quit [Ping timeout: 250 seconds]
<pokazef>
LiquidAcid: Low-level power bugs are scary...
<pokazef>
And by the way, is it possible to do any permanent damage when misconfiguring power management / voltage regulation stuff?
<LiquidAcid>
pokazef, i'm not sure if this is really a power issue in the sense of the hdmi-current-feedback one
<LiquidAcid>
pokazef, of course, so always check for any additional zeros when setting regulator voltages ;)
<pokazef>
LiquidAcid: I'm not used to that kind of responsability when compiling a kernel...
<pokazef>
I wish this kind of stuff stayed in hardware
<LiquidAcid>
pokazef, just double-check everything if you're working in that area
<LiquidAcid>
pokazef, what do you want to do anyway? add these 2ghz frequencies?
<pokazef>
LiquidAcid: I see no reason why I should be, but thanks for the head-up anyway
prahal has quit [Quit: prahal]
<pokazef>
LiquidAcid: Nope, I have no reason to touch any of it. It's just something I had been wondering.
prahal has joined #linux-exynos
<LiquidAcid>
pokazef, then i wouldn't worry too much
<pokazef>
LiquidAcid: OK, thanks
wwilly has joined #linux-exynos
amitk has quit [Quit: leaving]
prahal has quit [Ping timeout: 276 seconds]
<pokazef>
LiquidAcid: I just applied your patch to u-boot v2016.03 and I still get the same behavior.
<pokazef>
Luckily, I can just use the other power supply, so it's not a big problem for now
<LiquidAcid>
pokazef, hmm strange, no idea then
<pokazef>
It's ok, thanks for the help
<pokazef>
LiquidAcid: is there some backlog in the u-boot console that I could check, BTW?
<LiquidAcid>
pokazef, you mean like some scrollback buffer?
<pokazef>
yep
<LiquidAcid>
hmm, not that i know of
<pokazef>
Oh well
prahal has joined #linux-exynos
LiquidAcid has quit [Quit: Leaving]
paulk-collins has joined #linux-exynos
prahal has quit [Ping timeout: 260 seconds]
prahal has joined #linux-exynos
wwilly has quit [Quit: Leaving]
prahal has quit [Ping timeout: 250 seconds]
prahal has joined #linux-exynos
prahal has quit [Remote host closed the connection]