<naoki>
dsimic: there is u-boot/arch/arm/dts/rk3328-rock-pi-e-v3.dts, when I added it I thought Linux dts can be shared, but I noticed it was wrong
<dsimic>
hmm, how was it added?
<dsimic>
regarding OpenWrt, please see my last response on linux-rockchip... I'd appreciate if you'd explain what's the actual issue
<dsimic>
however, "catering" to OpenWrt by adding unnecessary new board DTs isn't the right solution, at least because we already have different board variants supported in U-Boot with no separate upstream DTs
<dsimic>
thus, a more general solution is required for whatever the issue is
<naoki>
U-Boot source have no issue without separate upstream DTS
<naoki>
but output binary is not compatible
<naoki>
"A devicetree does describe actual hardware"
<naoki>
actual hardware is different
<naoki>
u-boot binary is different
<naoki>
there must be something in running system to tell actual hardware
<naoki>
if "compatible" strings is not general solution for it, what is general solution?
<dsimic>
I referred to a solution that wouldn't cover just the ROCK Pi E variants, but the similar variants of other boards, such as the Nano Pi M4
<dsimic>
basically, if we accept separate DTs for ROCK Pi E, then we need to introduce separate DTs for all other similar boards
<dsimic>
whose variants with different DRAM are currently handled in U-Boot only
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
<naoki>
we use same dts in linux, then how do we know what is actual hardware? can you automate building u-boot with proper configuration?
<naoki>
for ROCK Pi E case, how can I know which I should use rock-pi-e-rk3328_defconfig or rock-pi-e-v3-rk3328_defconfig?
<dsimic>
those are all good questions
<dsimic>
currently, the end user "just knows" what to use
<dsimic>
which actually isn't a good way
warpme has quit [Ping timeout: 245 seconds]
<dsimic>
let me think a bit more about it, please
<naoki>
I think it will not be good to have dts for all other smiliar boards
<naoki>
but I have no good idea for now
<dsimic>
basically, we'd have maybe even half a dozen new DTs that are all 99.9% the same
<dsimic>
which isn't great, when you think about it, but I see no better solution RN
<dsimic>
I'd like to think more about it, perhaps for the next couple of days
<naoki>
there is rk3xxx-generic.dts ;)
<naoki>
^in u-boot
<dsimic>
that's to be used while bringing up new boards
<dsimic>
as some kind of a starting point
<naoki>
yes
<naoki>
then 99.9% same new dts as a result (I'm not blaming it)
<dsimic>
I hope that you agree about the need for a general solution that covers all such board variants
<dsimic>
IOW, it isn't just about the ROCK Pi E, but about all such boards
<naoki>
I need to write new metadata format for OpenWrt :)
<naoki>
well, it's ok if it's better than my dirty solution
<naoki>
I have no idea
<dsimic>
so far, having separate DTs with unique "compatible" values seems like the best possible option, but it needs to be applied retroactively
<dsimic>
is the way OpenWrt performs board detection and firmware updates documented somewhere?