03-24-2016, 01:16 PM
(03-23-2016, 12:51 PM)janjwerner Wrote:(03-19-2016, 03:32 PM)longsleep Wrote: I pushed another Kernel build to support the smallest 512MB Pine64 model (with another device tree). Some other minor build changes have landed as well, see the first post for details.
Get 3.10.65-3-pine64-longsleep-2 from https://www.stdin.xyz/downloads/people/l...ges/linux/
Update like this (as root) on any of my images:
Code:bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_uboot.sh)
bash <(curl -s https://raw.githubusercontent.com/longsleep/build-pine64-image/master/simpleimage/platform-scripts/pine64_update_kernel.sh)
If you update U-Boot as well you will get automatic Pine64 model detection, making the image also work with networking on the non-plus Pine64 automatically when you remove the fixed dtb filename from the existing /boot/uEnv.txt.
Image works like a charm on 512mb model.
As for the ethernet functioning:
Iperf3 between Pine+ (server) and Pine (client)
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-30.00 sec 337 MBytes 94.2 Mbits/sec 20 sender
[ 4] 0.00-30.00 sec 337 MBytes 94.2 Mbits/sec receiver
two boards connected to same gigabit switch.
That's great that it's working! Just for comparison, also using iperf3, using a windows desktop with GigE and pine64+ I get:
664 Mbit/s with pine64+ as server
371 Mbit/s with pine64+ as client
Thought it was interesting that there was asymmetry. Perhaps CPU bound?