azend|vps has quit [Remote host closed the connection]
azend|vps has joined #linux-rockchip
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 255 seconds]
vstehle has joined #linux-rockchip
<Ke>
fysa: no chromeOS
<Ke>
at least I hope
tl_lim has quit [Ping timeout: 265 seconds]
tl_lim has joined #linux-rockchip
paulk-gagarine has quit [Quit: Leaving]
paulk-gagarine has joined #linux-rockchip
xerpi has joined #linux-rockchip
aalm has quit [Ping timeout: 240 seconds]
Omegamoon has joined #linux-rockchip
aalm has joined #linux-rockchip
yann has quit [Ping timeout: 260 seconds]
tl_lim has quit [Ping timeout: 256 seconds]
tl_lim has joined #linux-rockchip
hanetzer has quit [Ping timeout: 265 seconds]
tl_lim has quit [Ping timeout: 260 seconds]
tl_lim has joined #linux-rockchip
xypron has joined #linux-rockchip
aalm has quit [Quit: xyz 2.0.1]
ayaka has quit [Ping timeout: 245 seconds]
hanetzer has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
ayaka has joined #linux-rockchip
matthias_bgg has quit [Client Quit]
matthias_bgg has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
tl_lim has quit [Ping timeout: 260 seconds]
cnxsoft has joined #linux-rockchip
tl_lim has joined #linux-rockchip
ayaka has quit [Ping timeout: 256 seconds]
kever has joined #linux-rockchip
ayaka has joined #linux-rockchip
yann has joined #linux-rockchip
<eballetbo>
fysa: no is not ChromeOS however it is for coreboot bootloader. I did not test in rock64, I supose the rootfs can be the same but the generated sd-card will probably not work properly.
tl_lim has quit [Read error: Connection reset by peer]
BenG83 has quit [Ping timeout: 240 seconds]
LargePrime has quit [Ping timeout: 256 seconds]
gnufan has quit [Ping timeout: 248 seconds]
LargePrime has joined #linux-rockchip
LargePrime has quit [Ping timeout: 240 seconds]
LargePrime has joined #linux-rockchip
nighty-- has quit [Remote host closed the connection]
<mmind00>
ezequielg: what kernel version were you working on for this? I..e eballetbo did this series allowing the typec to work without extcon support ...also in general did you enable the typec-phy in your config?
<mmind00>
ezequielg: i.e. the dwc3 core failing often indicates that it failed to find its phy or so
afaerber has quit [Quit: Leaving]
xerpi has quit [Quit: Leaving]
afaerber has joined #linux-rockchip
hanetzer1 has joined #linux-rockchip
hanetzer has quit [Ping timeout: 264 seconds]
lurchi_ is now known as lurchi__
mansson has quit [Quit: Leaving]
cnxsoft has quit [Quit: cnxsoft]
LargePrime has quit [Remote host closed the connection]
afaerber has quit [Quit: Leaving]
topi` has quit [Ping timeout: 260 seconds]
afaerber has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-rockchip
adj__ has quit [Remote host closed the connection]
adj__ has joined #linux-rockchip
agusan has joined #linux-rockchip
libv_ is now known as libv
lerc_ has joined #linux-rockchip
lerc has quit [Ping timeout: 256 seconds]
matthias_bgg has quit [Ping timeout: 276 seconds]
tllim has joined #linux-rockchip
yann has quit [Ping timeout: 276 seconds]
Easyfab has joined #linux-rockchip
aalm has joined #linux-rockchip
Easyfab has quit [Quit: Leaving]
afaerber has quit [Quit: Leaving]
anarsoul|2 has joined #linux-rockchip
<ezequielg>
mmind00: I will ask Tom Cubie about opening the schematics.
<ezequielg>
mmind00: and I do not think the type-c phy driver is working properly :)
Omegamoon has left #linux-rockchip [#linux-rockchip]
<mmind00>
ezequielg: yeah, schematics would be helpful
<ezequielg>
mmind00: but otoh, I am having a hard time understanding how the dual role dwc3 driver, the ehci host driver, and the typec driver are related.
<ezequielg>
mmind00: i cannot make any USB to work, and this board seem to have usb 2.0 connectors, which I expected the ehci would support.
<ezequielg>
perhaps I am missing just some silly regulator there.
<mmind00>
ezequielg: ehci has a different phy
<mmind00>
ezequielg: i.e. type-c only handles the two dwc3 ... and so far nobody really looked at how that is supposed to work with the fusb302
<mmind00>
ezequielg: i.e. on gru chrome devices, the cros_ec provides the functionality that fusb302 does on your board
<ezequielg>
mmind00: can we merge this without USB?
<mmind00>
ezequielg: yep
<ezequielg>
like I said, having basic support will be useful, on both uboot and linux.
<ezequielg>
to put it in the lava lab.
<ezequielg>
so, let's fix the regulators and check that all the peripherals we are adding work
<ezequielg>
and we are good
<mmind00>
ezequielg: yep ... regulator-tree is my main qualm right now ... I really like them to model the devices power-tree
<ezequielg>
totally agreed.
<ezequielg>
I needed help reviewing it, and that's why I sent it, tbh.
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-rockchip
BenG83 has joined #linux-rockchip
<ezequielg>
not seeing the drm-misc-next fixes in linux-next. mmind00, is that branch in linux-next?
<ezequielg>
maybe it's worth adding it, if not?
<mmind00>
ezequielg: not sure if that is an individual part of linux-next ... but I think drm-misc people send pull requests to main drm-trm once a week
<ezequielg>
ok, if you say it's expected, i am fine with waiting a few days.