System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
warpme_ has joined #linux-rockchip
warpme_ has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
<qschulz>
Danct12: we've been told that by our FAE yes
<qschulz>
CounterPillow: it does exist but the NDA to sign to get the TRM is absolutely crazy, and the support upstream is not where the RK3399 is today :)
raster has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 252 seconds]
kevery1 is now known as kevery
kevery1 has joined #linux-rockchip
stikonas_ has joined #linux-rockchip
kevery has quit [Ping timeout: 272 seconds]
kevery1 is now known as kevery
naoki has quit [Quit: naoki]
gnuiyl has quit [Remote host closed the connection]
<mmind00>
CounterPillow: should I expect more comments for sre 's 5b+ series - just trying to differentiate between "no time yet" vs. "looks okayish" ;-)
<CounterPillow>
no more comments from my side, the things I noted were the only problems I found
<CounterPillow>
but if you want something more obviously correct to merge, there's always SAI c:
<mmind00>
all on the list for hopefully today ;-)
<mmind00>
Was trying to get both the grf- clocks right first (i.e. moving the rk3528 mmc phase clock to use your grf-stuff)
warpme_ has joined #linux-rockchip
warpme_ has quit [Client Quit]
stikonas_ has quit [Remote host closed the connection]
<diederik>
mmind00: did you receive my comment on patch 5 of sre's 5b+ series? It's not on lore and 'more importantly' it's not marked in my mail client as responded to ... while it is in my Sent folder ...
<diederik>
(thus this is NOT about my confusion wrt squashing)
<CounterPillow>
oh, no I see what this relates to now, your response
<mmind00>
CounterPillow: nope ... that came in reply to my pull request
<mmind00>
a3f: newer socs already have a soc container
<mmind00>
a3f: though I still remember starting with a soc container only to get review comments to drop it 12 years ago ;-)
<a3f>
:D
<mmind00>
a3f: do you have by chance a link for the "which is hopefully put to rest now" ... reading through that thread, the discussion mostly just stopped, but there wasn't any final "resolve"?
<a3f>
mmind00, it wasn't put conclusively to rest, that's all of it
<mmind00>
a3f: hehe ok :-)
<a3f>
Maybe when qschulz's /chosen/bootsource gets accepted, we could give /soc/aliases a try. I think it follows naturally that if we have a property that points at the device used to boot, there should be a mapping table to help the bootloader resolve the bootrom boot source