Hello Bill, Am 26.04.2017 um 18:32 schrieb Bill Merriam:

Has anyone had a chance to try this board? With 4GB of RAM on it and a couple of SSDs, it might make a pretty good server/build server/desktop/media center or something.

http://wiki.t-firefly.com/index.php/Firefly-RK3399/en

I notice Andreas has some firmware for this processor. Can I put that together with our AARCH64 root file system and make a bootable system?

Would it help things along if I gifted one of these boards to Andreas?

Your trust is of course flattering. ;) But in this particular case it won't be necessary... Let's just say there were above-average customs problems getting that board into Germany end of last month. I've been in touch with T-Firefly and hope to have one arrive next week now. (Customs couldn't say retroactively, but my hypothesis is that they held it and then returned it to China due to the included power supply not being CE certified for the European Union - so beware for other EU member countries as well. Workaround is asking T-Firefly to remove the power supply - now it passed and just needs to be delivered after weekend and Labour Day.) I usually create HCL Wiki pages only once I have the hardware in hands, so here's some quick notes: * We still need a proper U-Boot package for the Firefly-RK3399, which could be achieved by throwing one or two patches onto our 2017.05 queue. Currently there's only a u-boot-evb-rk3399 package, which may or may not work partially. * I need to find a suitable devel project for my ARM Trusted Firmware packages, which you seem to have seen. Any suggestions? * According to Yousaf, creating a JeOS image won't work currently, because Kiwi's first partition would overlap with the bootloaders. * Ideally we should just make JeOS-efi work (adding dtb-rockchip) on SD/USB/SATA and document how to get an up-to-date U-Boot onto eMMC. That would also allow to use the installation DVD instead of JeOS-efi. Hopefully we will know more in time for oSC17. Regards, Andreas P.S. For the record there is one other new board with 4 GB on an exchangeable DIMM (for $110 more), although the bootloader situation for its SoC seems much more work-in-progress still, at least compared to another board with RK3399 (not having tested the Firefly-RK3399 yet). -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org

On 14/05/17 18:03, Andreas Färber wrote:

Am 26.04.2017 um 18:32 schrieb Bill Merriam:

...

Has anyone had a chance to try this board? With 4GB of RAM on it and a couple of SSDs, it might make a pretty good server/build server/desktop/media center or something.

http://wiki.t-firefly.com/index.php/Firefly-RK3399/en

I notice Andreas has some firmware for this processor. Can I put that together with our AARCH64 root file system and make a bootable system?

I've finally managed to get a mainline based U-Boot onto the board, but eMMC appears to be the only working boot device at the moment.

One work branch also has network support (but a random MAC address). So it's still rather early for this board...

https://en.opensuse.org/HCL:Firefly-RK3399

There is a hacked-up branch which enables booting via usb. If there is someone who wants to try: https://github.com/mmind/u-boot-rockchip/tree/tmp/rk3399-firefly Regards, Matthias -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org