ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
vicencb has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
vagrantc has quit [Ping timeout: 250 seconds]
stikonas has quit [Read error: Connection reset by peer]
vagrantc has joined #linux-rockchip
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
vagrantc_ has joined #linux-rockchip
vagrantc has quit [Ping timeout: 264 seconds]
vagrantc_ is now known as vagrantc
default__ has quit [Read error: Connection reset by peer]
default__ has joined #linux-rockchip
vstehle has quit [Ping timeout: 255 seconds]
t3st3r has quit [Remote host closed the connection]
ldevulder_ has joined #linux-rockchip
default__ has quit [Ping timeout: 245 seconds]
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
rich0 has quit [Ping timeout: 246 seconds]
vstehle has joined #linux-rockchip
vagrantc has quit [Ping timeout: 250 seconds]
ldevulder_ has quit [Read error: Connection reset by peer]
ldevulder_ has joined #linux-rockchip
jelly has quit [Ping timeout: 245 seconds]
jelly-home has joined #linux-rockchip
field^Zzz1 has joined #linux-rockchip
jelly-home is now known as jelly
gaulishcoin has joined #linux-rockchip
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 250 seconds]
camus is now known as kaspter
maz has quit [Remote host closed the connection]
apritzel has joined #linux-rockchip
BenG83 has quit [Ping timeout: 245 seconds]
nsaenz has joined #linux-rockchip
BenG83 has joined #linux-rockchip
maz has joined #linux-rockchip
vicencb has joined #linux-rockchip
kaspter has quit [Ping timeout: 245 seconds]
kaspter has joined #linux-rockchip
lopsided98 has quit [Quit: No Ping reply in 180 seconds.]
lopsided98 has joined #linux-rockchip
rich0 has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 244 seconds]
ldevulder_ has joined #linux-rockchip
rich0 has quit [Ping timeout: 245 seconds]
rich0 has joined #linux-rockchip
vicencb has quit [Quit: Leaving.]
Kelsar has quit [Quit: No Ping reply in 180 seconds.]
Kelsar has joined #linux-rockchip
vagrantc has joined #linux-rockchip
ldevulder_ is now known as ldevulder
return0e has quit [Remote host closed the connection]
return0e has joined #linux-rockchip
paulk-leonov has quit [Ping timeout: 250 seconds]
paulk-leonov has joined #linux-rockchip
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-rockchip
nsaenz has quit [Ping timeout: 245 seconds]
stikonas has joined #linux-rockchip
aalm has quit [Ping timeout: 250 seconds]
scelestic has quit [Remote host closed the connection]
apritzel has quit [Ping timeout: 255 seconds]
scelestic has joined #linux-rockchip
scelestic has quit [Remote host closed the connection]
aalm has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
vagrantc has quit [Ping timeout: 264 seconds]
vagrantc has joined #linux-rockchip
<vagrantc> so, i've got a rock64 running debian, tried 4.19.x and 4.20.x and 5.0-rc8 kernels ... but USB doesn't work
poulecaca has quit [Ping timeout: 250 seconds]
poulecaca has joined #linux-rockchip
<hanetzer> vagrantc: does it work if you boot with the usb thing plugged in?
<vagrantc> hanetzer: neither cold plug nor hot plug
<hanetzer> worth a thought.
<vagrantc> indeed
<vagrantc> i can try other devices i guess that might have lower power draw
<vagrantc> although then, you'd usually at least get some messages indicating that a device was present but failed or repeated connects and disconnects
<vagrantc> my guess is some soft module dependency like a regulator or something ... the device-tree suggests the status is ok
<vagrantc> $ lsusb --tree
<vagrantc> /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
<vagrantc> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M
<vagrantc> /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M
<vagrantc> so it sees the hubs just fine
lerc has quit [Ping timeout: 246 seconds]
lerc has joined #linux-rockchip
vagrantc_ has joined #linux-rockchip
afaerber has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
<mmind00> vagrantc: for usb3 that is to be expected
<mmind00> vagrantc: but usb2 was working last I checked ... I had my nfsroot running over a usb-ethernet-adapter for quite a while
<vagrantc_> mmind00: hrm. probably missing a module or kernel configuration option, then ...
<vagrantc_> or a regression :/
<mmind00> vagrantc: looks more like some sort of regression ... as you see the usb root ports at least
<mmind00> vagrantc: so if things like usb-phy drivers where missing it _should_ have deferred probing before that
linux-rockchip has quit [Ping timeout: 272 seconds]
linux-rockchip has joined #linux-rockchip
naobsd has quit [Read error: Connection reset by peer]
gaulishcoin has quit [Remote host closed the connection]
naobsd has joined #linux-rockchip
vicencb has joined #linux-rockchip
tlwoerner has quit [Quit: Leaving]
BenG83 has quit [Quit: Leaving]
BenG83 has joined #linux-rockchip
field^Zzz1 has quit [Ping timeout: 245 seconds]