nighty has quit [Quit: Disappears in a puff of smoke]
paulk-collins has quit [Quit: Leaving]
Aussie_matt has joined #linux-rockchip
matthias_bgg_ has joined #linux-rockchip
matthias_bgg_ has quit [Remote host closed the connection]
matthias_bgg has quit [Remote host closed the connection]
matthias_bgg has joined #linux-rockchip
premoboss has quit [Ping timeout: 276 seconds]
npl has joined #linux-rockchip
nighty has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
cnxsoft has quit [Quit: cnxsoft]
<ayaka>
mmind00, could you tell me where you collect those patches next, I would refresh my dwc2 patches with a new version
<ayaka>
I hope I won't waste you time to collect those tags again
cnxsoft has joined #linux-rockchip
<npl>
Speaking about wasting time, have you had time looking into the USB problem, is this reproduceable? (Sent you the two Mails)
<ayaka>
npl, you could ping me here
<ayaka>
npl, I can't, both firefly and firefly plus have a usb hub
<ayaka>
so it is unlikely it doesn't have any device connected at the starting up
<ayaka>
I am going to forward you mail to list as well
tlwoerner has quit [Ping timeout: 265 seconds]
cnxsoft has quit [Quit: cnxsoft]
<ayaka>
and luckily I got a firefly release version yesterday, but I need to start the u-boot first
<npl>
ayaka: I think autosuspend from the USB Hub might be the issue, will try disabling it when I get home
<ayaka>
ok I found somebody have adding the missing phy_reset for me
<ayaka>
npl, it is, but not the best way to solve it
<ayaka>
I need figure what is different between firefly release and firefly plus
<ayaka>
I didn't meet that at firefly plus
<npl>
yeah, probably not the best way, but better than it is now =)
<ayaka>
Anyway I would go through it in the weekend
<npl>
if I can support you in any way (testing) let me know, but I am no big help in USB hacking
<ayaka>
npl, thank you, you could compare the SCH, it would be help
<ayaka>
also check while the reset for usb hub at firefly release is asserted correctly
<ayaka>
I though they may cause the problem
tlwoerner has joined #linux-rockchip
<npl>
ayaka: I did some embedded stuff, but I am totally blank when it comes to USB (reset behaviors, etc) and play with the Rk3288 during the few hours I can afford at home.
<ayaka>
the usb hub reset is just something with GPIO
<ayaka>
feel free to it, anyway I would look into it
<npl>
you mean checking in code with "printf debugging"?
Aussie_matt has quit [Remote host closed the connection]
<npl>
currently I am just trying to narrow it down, I found two patches, neither did help.
<npl>
ill see if i can find anything, but dont count on it =)
<ayaka>
npl, not
npl has quit [Quit: Page closed]
<mmind00>
ayaka: not sure I understand what you mean? I only collect arch-related patches, usb patches go through the trees of Felipe Balbi and Greg Kroah Hartman
<ayaka>
mmind00, I mean those patches with Review-By Ack-By
<ayaka>
I lose the most of those record
paulk-collins has joined #linux-rockchip
ssvb has joined #linux-rockchip
mrjay has joined #linux-rockchip
<mrjay>
mmind00: just to confirm : this patch resolves usb host debounce issues on rk3066; usb is working again
<mrjay>
weird that there is a patch with that name in linux-next dated 2016-09-08
maz has quit [Quit: Leaving]
<mrjay>
question to anybody with rk3066 device: does command "memtester 250M 1" freezes your board too?
<mrjay>
quesstion is to people with mainline kernel running on rk3066
<mrjay>
stdint: my device works ok with that patch
premoboss has joined #linux-rockchip
premoboss has quit [Remote host closed the connection]
afaerber has quit [Quit: Ex-Chat]
mrjay has quit [Quit: Page closed]
JohnDoe_71Rus has joined #linux-rockchip
afaerber has joined #linux-rockchip
ghostD0g has quit [Quit: Leaving]
paulk-collins has quit [Quit: Leaving]
f3z0 has joined #linux-rockchip
<f3z0>
Does recovery mode running partition format command require the debug console to be enabled in device tree, if so why? It’s getting stuck on misc command when I disable it in dt, however if I enable it let it finish partitioning and then update boot image with a kernel having debug console disabled it all works fine (I just can’t have a two step firmware process for logistical reasons)