ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
anarsoul has quit [Remote host closed the connection]
anarsoul has joined #linux-rockchip
alyssa has left #linux-rockchip [#linux-rockchip]
ganbold has joined #linux-rockchip
LargePrime has quit [Ping timeout: 240 seconds]
LargePrime has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
kaspter has joined #linux-rockchip
LargePrime has quit [Ping timeout: 260 seconds]
JohnDoe_71Rus has joined #linux-rockchip
kaspter has quit [Ping timeout: 264 seconds]
kaspter has joined #linux-rockchip
indy has quit [Read error: Connection reset by peer]
indy has joined #linux-rockchip
ganbold has quit [Remote host closed the connection]
nighty- has quit [Ping timeout: 265 seconds]
nighty- has joined #linux-rockchip
kaspter has quit [Ping timeout: 276 seconds]
kaspter has joined #linux-rockchip
xerpi has joined #linux-rockchip
kaspter has quit [Ping timeout: 268 seconds]
kaspter has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
xerpi has quit [Quit: Leaving]
lurchi__ has joined #linux-rockchip
wzyy2 has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
JohnDoe7 has joined #linux-rockchip
JohnDoe_71Rus has quit [Ping timeout: 256 seconds]
kaspter has quit [Quit: kaspter]
ganbold has joined #linux-rockchip
kaspter has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 264 seconds]
tllim has joined #linux-rockchip
tl_lim has joined #linux-rockchip
tl_lim has quit [Quit: Leaving]
kaspter has quit [Quit: kaspter]
kaspter has joined #linux-rockchip
hanetzer has quit [Ping timeout: 260 seconds]
cnxsoft has quit [Quit: cnxsoft]
hanetzer has joined #linux-rockchip
lurchi__ has joined #linux-rockchip
hanetzer has quit [Ping timeout: 248 seconds]
matthias_bgg has quit [Read error: Connection reset by peer]
matthias_bgg has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 264 seconds]
afaerber has joined #linux-rockchip
lurchi__ has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 268 seconds]
hanetzer has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 248 seconds]
lurchi__ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 256 seconds]
matthias_bgg has quit [Quit: Leaving]
Easyfab has joined #linux-rockchip
vagrantc has joined #linux-rockchip
wzyy2 has quit [Read error: Connection reset by peer]
anarsoul|2 has joined #linux-rockchip
ckeepax has quit [Ping timeout: 240 seconds]
kaspter has quit [Ping timeout: 268 seconds]
hanetzer has quit [Ping timeout: 240 seconds]
afaerber has quit [Quit: Leaving]
<vagrantc> beeble: if i recall correctly, you suggested that it might be possible to use the ATF for the puma-rk3399 on the firefly-rk3399 ... would the only changes for firefly likely need to be in u-boot, or also atf/rk3399m0.bin ?
* vagrantc was guessing the offset load address was about all that would need to be changed ...
<beeble> vagrantc: iirc there are no hardware specific changes in the ATF. so it should work. you may want to have some devicetree changes as these settings get propagated into the atf (rst_gpio out of my head)
<beeble> but the atf is based on a quite old version. so it is missing features, but not sure how relevant they are for non android oses at the moment
<beeble> but the base is the same. so it should work as it is in theory
<vagrantc> is it u-boot SPL that determines what offset to load u-boot.itb from? the puma-rk3399 seemed to use a (much more reasonable) offset
<vagrantc> if i can get it working with the firefly-rk3399, i might upload an atf for and cortex-m0 stuff, as it would at least support two boards.
<beeble> the spl gets the offset from the devicetree
<vagrantc> even if it means some small divergence from upstream u-boot
<beeble> u-boot,spl-payload-offset = <0x40000>;
<vagrantc> aha
<beeble> for rk3399-puma
<beeble> take a look at config and chosen in arch/arm/dts/rk3399-puma.dtsi
<vagrantc> if i get a working atf+cortex-m0+u-boot in debian, I can enable support for those boards out of the box in debian-installer
<beeble> we try to have most things that make sense configurable via the dtb
<vagrantc> i could possibly just enable it for puma-rk3399 ... but it'd be a stronger case to make to support more than one board :)
<beeble> that sounds great
<vagrantc> though, long-term, would rather just see one ATF in Debian
<vagrantc> e.g. upstream
<vagrantc> but someone already uploaded atf-allwinner... so that bridge has been crossed :)
<beeble> having a unified atf repo will take some time, until then you will see vendor forks
<beeble> maybe someday it will be clear what should load what and who initializes what and how all these parts are exchanging informations
hanetzer has joined #linux-rockchip
afaerber has joined #linux-rockchip
<vagrantc> beeble: look forward to that day :)
hanetzer has quit [Remote host closed the connection]
hanetzer has joined #linux-rockchip
JohnDoe7 has quit [Quit: KVIrc 4.9.3 Aria http://www.kvirc.net/]
_whitelogger has joined #linux-rockchip
Easyfab has quit [Quit: Leaving]
xerpi has joined #linux-rockchip
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-rockchip
mrutland has quit [Quit: bye...]
anarsoul|2 has quit [Remote host closed the connection]
anarsoul|2 has joined #linux-rockchip
tllim has quit [Quit: Leaving]
xerpi has quit [Quit: Leaving]
ganbold has quit [Quit: This computer has gone to sleep]
vstehle has quit [Ping timeout: 240 seconds]