franoosh has quit [Read error: Connection reset by peer]
cbeznea has quit [Remote host closed the connection]
cbeznea_ has joined #linux-rockchip
<qschulz>
shoragan: and the more_opts would be coming from the conf of SnagrecoverDriver as well? the self.soc cannot always be derived, see rk3566 and rk3568 sharing the same productID
<qschulz>
also, I really want the images passed to snagrecover to be configurable so that one can test U-Boot binaries without hacks
alpernebbi has quit [Read error: Connection reset by peer]
catcream has quit [Ping timeout: 248 seconds]
<Dex_2x>
Is the radxa rock 3C relatively new? Because I don't see it listed on armbian
<qschulz>
Dex_2x: it's not because armbian does not support it that it's not well supported
<Dex_2x>
more the rk3566 that is the issue?
<CounterPillow>
no
<CounterPillow>
RK3566 is well supported in mainline
<CounterPillow>
You just don't see an image for this particular device in Armbian, and somehow conclude that everything but Armbian is the problem, when that is not the case.
alpernebbi has joined #linux-rockchip
<Dex_2x>
well radxa only has one image for it as well
<dsimic>
in general, Armbian should be considered for the boards that aren't supported well upstream; otherwise, "plain" Debian is the way to go
<Dex_2x>
I have yet to try plain debian
<Dex_2x>
on a sbc
<dsimic>
the goal high in the sky is that no SBC manufacturer provides some special images, but to have the SBCs "just work" in "vanilla" ARM distros
<CounterPillow>
The DTS is in mainline and SoC support is in mainline as well. The number of poorly copypasted together images made up of vendor stuff is not an indication of how well an SBC is supported
<qschulz>
you may be missing some features as development on RK356x (and possibly Rock 3C) continues, e.g. there's no camera support at the moment if I remember correctly
<qschulz>
so you may need (or even want) to build the mainline kernel yourself
<qschulz>
which is a bit far from "download the image from site Y and flash on my device"
<qschulz>
but we are here if there's any question on the process :)
<dsimic>
Dex_2x: to clarify, regarding Armbian, it's just that people are used a bit too much to having some special images for their SBCs; in the past, Armbian did a great job offering support for the boards that weren't supported well upstream, but as they becomee supported, "vanilla" Debian should be considered instead
<Dex_2x>
dsimic, ah fair enough
<dsimic>
IOW, Armbian could be seen as some kind of staging area
<CounterPillow>
Armbian actually deviates from both mainline and vendor images, doing their own thing, and in the process confusing users
<dsimic>
CounterPillow: true, but for the unsupported boards, there isn't much choice otherwise
<dsimic>
short of hunting down the images provided by the SBC manufacturers, of course
<CounterPillow>
dsimic: there is. Mainline them instead of slapping mud against walls downstream.
<CounterPillow>
Submitting a new board DTS for an already supported SoC is one of the easier ways to contribute towards mainline development
<CounterPillow>
(assuming no excess emotional damage taken from krzk responses)
<Dex_2x>
lol
<dsimic>
CounterPillow: indeed, but there's always a window in which upstream support simply isn't there
<dsimic>
haha, Krzystof does happen to induce some feelings from time to time :)
<dsimic>
though, I wouldn't agree that putting a DT together and submitting it upstream is one of the easiest way to contribute upstream; a lot of knowledge is actually needed, unless one just copies a DT from the downstream blindly
<dsimic>
s/way to/ways to/
<dsimic>
oops, s/Krzystof/Krzysztof/, sorry
naoki has quit [Quit: naoki]
<CounterPillow>
copying downstream DTs is a bad idea because the bindings will be different, the much easier method is to "get inspired" by other SBCs using the same SoC that are already upstream, as they all usually have fairly similar designs, owing to many of them being derived from either EVB designs or made by the same contract design houses.
<dsimic>
true, there are many similarities
raster has joined #linux-rockchip
chewitt has joined #linux-rockchip
Dex_2x has quit [Quit: ZNC 1.9.1+deb2+b3 - https://znc.in]
Dex2x has joined #linux-rockchip
Dex2x has quit [Remote host closed the connection]
<mmind00>
Kwiboo: oh ... nice ... because not having a sane u-boot did keep me very much from even looking at my rk3506 board so far
<CounterPillow>
I, too, have a RK3506 board :D
<Kwiboo>
if I remember correctly the new "cpuclk_v2" threw me off a little bit, so I probably just switched focus to rk3528 instead, should re-send some series for rk3528 before ever looking at linux part for rk3506 ;-)
<mmind00>
yeah, looking through that branch, this one stood out a bit ... (me not trusting that a "v2" is needed yet)
<mmind00>
also I'm definitly undecided on that psci smp method .... probably requiring some binary optee thingy right now
<mmind00>
CounterPillow: that arm64 thing will forever stay a fad ;-)
<mmind00>
arm32 FTW
<CounterPillow>
mmind00: you have now been hired by STM
<Kwiboo>
trying to rework that v2 cpuclk is what I got stuck at, trying to merge it with existing or similar without really understand the existing v1 cpuclk and how it would impact, did not want to dive into another rabbit hole ;-)
<mmind00>
noooooooooooooo
<mmind00>
(^^ CounterPillow)
<CounterPillow>
:D
<mmind00>
Kwiboo: yeah ... I did try to stay out of the rk3506 rabbit hole ... but then you showed me that u-boot branch
<mmind00>
darn you
<mmind00>
there is this Sesamestreet clip on youtiube where Ian McKellen is teaching Cookiemonster about the word "resist" ... need to rewatch
<Kwiboo>
hehe :-), I did a boot test with that rk3506 u-boot branch on a luckfox lyra regular/plus/ultra/zero-w and armsom forge1 the other day, boot from sd-card/emmc, usb otg/host and ethernet should be working, spi nand is not, use of correct rk3506 vs rk3506b ddr init blob seem to be important
stikonas has joined #linux-rockchip
chewitt_ has quit [Quit: Zzz..]
chewitt has joined #linux-rockchip
chewitt has quit [Client Quit]
ldevulder has quit [Ping timeout: 256 seconds]
cbeznea has quit [Ping timeout: 255 seconds]
catcream has joined #linux-rockchip
catcream has quit [Read error: Connection reset by peer]
catcream has joined #linux-rockchip
psydroid2 has joined #linux-rockchip
ldevulder has joined #linux-rockchip
franoosh has joined #linux-rockchip
franoosh has quit [Remote host closed the connection]