ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion
kevery has quit [Read error: Connection reset by peer]
kevery 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]
macc24 has joined #linux-rockchip
macc24 has quit [Changing host]
macc24 has joined #linux-rockchip
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 268 seconds]
vagrantc has quit [Quit: leaving]
System_Error has quit [Ping timeout: 276 seconds]
chewitt has joined #linux-rockchip
chewitt has quit [Quit: Zzz..]
System_Error has joined #linux-rockchip
System_Error is now known as HardFault
HardFault is now known as System_Error
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
kevery has quit [Ping timeout: 256 seconds]
kevery has joined #linux-rockchip
stikonas has joined #linux-rockchip
System_Error has quit [Remote host closed the connection]
kevery has quit [Quit: kevery]
matthias_bgg has joined #linux-rockchip
vagrantc has joined #linux-rockchip
nashpa has quit [Quit: Going away]
dliviu has joined #linux-rockchip
dlezcano has joined #linux-rockchip
Rathann has quit [Quit: Leaving]
vagrantc has quit [Remote host closed the connection]
vagrantc has joined #linux-rockchip
<samueldr>
just in case, quickly refreshing my question: anyone can confirm whether eMMC boot partitions (mmcblk×boot[01]) on RK3399 (or other rockchip SoCs) can or cannot be used to store e.g. U-Boot?
<samueldr>
I'm asking since "common knowledge" for other vendors' SoCs turned out to be wrong, so eh, let's see if one of you has had access to more in-depth docs detailing the startup sequence
<robmur01>
on a board with a pluggable eMMC module, I guess you could slap a logic analyser on the pins and see what commands it actually sends?
<dlezcano>
It seems like the RK3588 will be released soon, is there any plan to have upstream support ?
<CounterPillow>
no
<dlezcano>
CounterPillow, "no" for samueldr's question or mine ? :)
<CounterPillow>
yours
<CounterPillow>
volunteer contributors cannot upstream support for something that does not yet exist
<daniels>
it is gradually starting to exist
mrjay has joined #linux-rockchip
<mrjay>
what could be the reason nand controller outputing random data and not for example nand id when asked for nand id?
<mrjay>
it works fine when bootrom boot from nand
<mrjay>
it doesn't work when booting from "rkflashtool L"
<mrjay>
my first guess was clock issue ... but everything look good in the clock driver
<mrjay>
any ideas?
<mrjay>
nevermind ... not only controller needed reset ... nand chip too