Thank you
i have seen documentation page on wiki,but there is no bpi-r64 specific documentation (only for mt7622 soc). Also i’ve seen no storage scheme. found gpio on getting started page
kernel/uboot-repo is now public (without wifi-driver) 
how do you want to manage mt7615-code cause it is non-GPL? how can we upgrade it to newer codebase (i.e. 4.19)? Can you compile it for me so i can add its binary to my 4.19-tree?
As far as i see in repo you load kernel and devicetree separately via uboot (cause appended dtb not possible).
btw. just booted up my r64 with this image without problems 
thank you Jack
i can now try to bootup newer kernel and a newer debian while waiting for upstream-uboot-support
@jackzeng why do i see eth2 and eth3 instead of eth0&1?
root@bpi-iot-ros-ai:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 16:d2:9d:4c:3a:cc brd ff:ff:ff:ff:ff:ff
3: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ea:6d:4d:82:86:1e brd ff:ff:ff:ff:ff:ff
inet 192.168.0.132/24 brd 192.168.0.255 scope global dynamic eth2
valid_lft 172797sec preferred_lft 172797sec
inet6 fe80::e86d:4dff:fe82:861e/64 scope link
valid_lft forever preferred_lft forever
4: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
link/ipip 0.0.0.0 brd 0.0.0.0
5: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
link/sit 0.0.0.0 brd 0.0.0.0
6: ra0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
7: rai0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 82:bf:e2:f0:64:14 brd ff:ff:ff:ff:ff:ff
eth2 are the lan-ports, wan-port = eth3, lan-ports in dhcp, wan-port manual, /etc/network/interfaces only contain lo-interface
full boot-log: r64-boot.log (185,8 KB)
a question about building: you build Image (uimage or zimage does not work on arm64) here
- why passing “UIMAGE_LOADADDR”? imho it’s no kernel-option (seems not used in kernel-makefile)
- kernel=uImage is defined in uEnv.txt and buildin-environment (buildin) but this is no uImage, right…imho it’s the Image-file (not gzipped and not run through mkimage)
got 4.19 booted so far (using mkimage without dtb and arch arm instead of arm64)…seems like dsa is missing currently. your Page says it is rtl8367S…i have not found a driver for it in menuconfig… i found only rtl8366 driver in drivers/net/dsa, but i think it’s different…hoping realtek bring driver soon…how have you got it working in 4.4? have you realtek-people on your side?
also in linux-next i found no definition of wan/lan-ports in dts…here i need some help
uboot does not support ethernet yet, right?
btw link to HW-NAT is not working on http://wiki.banana-pi.org/Banana_Pi_BPI-R64 (because there are some strange chars at the end of it)
thank you Jack