staylor has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
stunpix_ has joined #imx6-dev
shogunx has joined #imx6-dev
stunpix_ has quit [Ping timeout: 246 seconds]
vpeter has joined #imx6-dev
shogunx has quit [Ping timeout: 255 seconds]
shogunx has joined #imx6-dev
tasslehoff has joined #imx6-dev
shogunx has quit [Ping timeout: 250 seconds]
shogunx has joined #imx6-dev
stunpix_ has joined #imx6-dev
stunpix_ has quit [Ping timeout: 250 seconds]
shogunx has quit [Ping timeout: 240 seconds]
shogunx has joined #imx6-dev
FelixH has joined #imx6-dev
tasslehoff has left #imx6-dev ["WeeChat 0.4.2"]
stunpix_ has joined #imx6-dev
stunpix_ has quit [Ping timeout: 272 seconds]
perul has joined #imx6-dev
paulk-collins has joined #imx6-dev
shogunx has quit [Ping timeout: 246 seconds]
shogunx has joined #imx6-dev
aholler_ is now known as aholler
aholler has quit [Ping timeout: 250 seconds]
aholler has joined #imx6-dev
stunpix_ has joined #imx6-dev
stunpix_ has quit [Ping timeout: 245 seconds]
diego_r has joined #imx6-dev
jnettlet has quit [Ping timeout: 245 seconds]
jnettlet has joined #imx6-dev
stunpix_ has joined #imx6-dev
stunpix_ has quit [Ping timeout: 272 seconds]
Er0l has quit [Ping timeout: 264 seconds]
Er0l has joined #imx6-dev
staylor has joined #imx6-dev
kroon has joined #imx6-dev
stunpix_ has joined #imx6-dev
stunpix_ has quit [Ping timeout: 245 seconds]
rz2k has joined #imx6-dev
ballock has quit [Ping timeout: 240 seconds]
paulk-collins has quit [*.net *.split]
bfederau has quit [*.net *.split]
hste__ has quit [*.net *.split]
tumdedum has quit [*.net *.split]
tomeu` has quit [*.net *.split]
ballock has joined #imx6-dev
paulk-collins has joined #imx6-dev
tumdedum has joined #imx6-dev
tomeu` has joined #imx6-dev
bfederau has joined #imx6-dev
hste__ has joined #imx6-dev
ragesoss_ has joined #imx6-dev
ragesoss has quit [Quit: No Ping reply in 180 seconds.]
kroon has quit [Quit: Leaving]
Er0l has quit [Ping timeout: 245 seconds]
FelixH has quit [Remote host closed the connection]
perul has quit [Ping timeout: 250 seconds]
stunpix_ has joined #imx6-dev
rz2k has quit []
diego_r has quit [Ping timeout: 250 seconds]
stunpix_ has quit [Ping timeout: 260 seconds]
kroon has joined #imx6-dev
jbd1986 has joined #imx6-dev
<jbd1986>
all, I'm having an interesting issue that I'm hoping someone here can shed some light on
<jbd1986>
I have 6 boards. 5 of them are working fine
<jbd1986>
The one board that isn't working is having an issue where it will only boot all the way to the command prompt (via serial console) if HDMI is not plugged
<jbd1986>
If HDMI is plugged in, the system freezes
<jbd1986>
Now, there is a hardware delta between the board that works and the ones that don't (different SDRAM chips used)
<jbd1986>
sorry boards* that work, and the one* that doesn't.
<aholler>
sounds trivial, the memory timing
<jbd1986>
Plugging the HDMI mid-boot usually causes the boot process to freeze as soon as it's plugged in
<jbd1986>
sometimes it will proceed
<jbd1986>
aholler, that's what I thought, but here's the kicker
<jbd1986>
If I try a different image, the unit that doesn't work will boot fine with or without HDMI plugged in
<jbd1986>
images that work: 3.10.17 sysvinit, androidkk 4.4.2_2.0.0
<kroon>
jbd1986, I've seen this hang, managed to use a JTAG debugger and see that it got stuck in some IRQ-handler for the hdmi I think, due to IRQ-bursts or something
<kroon>
jbd1986, there was a patch in wandboard kernel git that solved it for me IIRC
<jbd1986>
kroon, is there any way you can find that patch? I'm going to look for it, but if you have it that would be VERY helpful
<kroon>
just sayin
<kroon>
jbd1986, let me check
<jbd1986>
kroon, does it make sense that this only happens on one of my 6 boards (with different memory)?
<jbd1986>
my 3.10.17 systemd image is the one having an issue
<jbd1986>
and only on this one board
<kroon>
jbd1986, thats a mystery to me
rabeeh has quit [Read error: Connection reset by peer]
<aholler>
if memory timings are set wrong, everything might appear as a mystery
<jbd1986>
aholler, I suggested that the memory timings could be the problem, but the EE insists that since the device works fine with other images, this would not be the case
<aholler>
that isn't true
<jbd1986>
aholler, how do I articulate that, because that was my initial thought
<kroon>
jbd1986, I either had to add that patch, or revert it, dont remember which
<jbd1986>
at first I was confused, but it appears they moved the function
<jbd1986>
kroon, I will give that a shot
<kroon>
jbd1986, wait, I think that was the wrong patch
paulk-collins has quit [Ping timeout: 255 seconds]
<jbd1986>
kroon, ok I'll hold off
<kroon>
jbd1986, I reverted a commit called "ENGR00288972 HDMI: unmask overflow interrupter when HDMI phy power on"
<kroon>
Sorry, it was some time ago. I'm using latest 3.10.17 kernel from freescale on my Wandboards, and I don't need to have that revert-patch applied anymore
<jbd1986>
kroon, thanks, that certainly looks like it's worth investigating
<kroon>
aholler, where are memory timings set ?
<jbd1986>
kroon, boards.cfg points to a file
ragesoss_ is now known as ragesoss
<jbd1986>
that file would contain DCD settings
<aholler>
kroon: usually in the boot-loader
<kroon>
aha
<aholler>
or similiar. don't know how that happens on i.mx
<jbd1986>
the boards.cfg file is in the root of the uboot tree
<jbd1986>
then look up the board you have configured and it should point to a file
stunpix has quit [Ping timeout: 240 seconds]
<jbd1986>
kroon, aholler, that patch swapped my issue lol
<jbd1986>
well revert I should say
<jbd1986>
Now when I boot with HDMI in it works fine, but with HDMI unplugged I get a kernel panic/freeze
<codinho>
guys, current qtwebkit recipe should have glib thing in PACKAGECONF for html5video, otherwise video just not even starts to feed data. possibly glib integration was not enabled because of some other reason...
hste__ has quit [Ping timeout: 255 seconds]
<codinho>
dv_, was there any progress in last gst release about texture rendering thing including custom rendering things?
<jbd1986>
that seems like a pretty reasonable patch. Here's the interesting part. I looked at the 3.10.31 kernel included with my kk4.4.2_2.0.0 build, and it does not have this patch.
<jbd1986>
Also, the 3.10.17 sysvinit build DID have this issue, but not every time
stunpix_ has joined #imx6-dev
stunpix_ has quit [Ping timeout: 240 seconds]
<kroon>
jbd1986, interesting
bfederau has quit [Remote host closed the connection]
bfederau has joined #imx6-dev
kroon has quit [Quit: Leaving]
stunpix_ has joined #imx6-dev
staylor has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]