information board Firefly-RK3288 Specifications Wiki
good performance parameters:
ARM Cortex A15/A17 SoCs Comparison – Nvidia Tegra K1 vs Samsung Exynos 5422 vs Rockchip RK3288 vs AllWinner A80

board already ordered, will soon be made assemblage of images Slackware-current

Information about installing the GPU drivers

Interesting. I am waiting to buy once the strengths of these devices become a bit clearer.

I briefly owned a Pipo P1 with the RK3288. It had a TF 3G sim, which required reboots to register any settings although it's accessible from the outside. It also failed to pick up 3G if you turned on wifi and then turned it off, which was a pain. Reboot required.

The Pipo P1 arrived with an antutu score of 40k+. Antutu updated itself (as things do) and the score came down to 34,400:-(.

As for the Nvidia K1, they claim 2.2 Ghz. One report commented "2.2 Ghz? Forget it - the test model did 1557Mhz and no faster. Antutu score 28000." Perhaps heat was the issue?

Watch out for RockChip kernel modules in the firmware which are not part of the kernel. They seem to write one kernel module per SoC (perhaps all of them do). It can make alternative software difficult.

It sounds like a familiar line:

"Brief bursts of extreme speed followed by inevitable disaster." They're welcome to over clock it, and try to deal with the extra heat until something fizzles. I'm not fitting a heatsink & fan to a tablet. What struck me is that the Android version that came with the Pipo I had is pure crap. I have a falling-apart RK3188 and have become increasingly skeptical about Rockchip's 3288 offering. Interesting link, however.

first release

1. resize partition firstboot device
2. wifi firmware moved to /lib/firmware
3. wifi enable /etc/rc.d/rc.wifi start|stop (in rc.local)

login: root
password: password

http://fail.pp.ua/RK3288UbootLoader_V2.19.01.bin
http://fail.pp.ua/parameters.txt
http://fail.pp.ua/resource.img
http://fail.pp.ua/boot.img
http://fail.pp.ua/slack-current-miniroot_09Mar15.img
http://fail.pp.ua/flash.sh

2 members found this post helpful.

the support http://fail.pp.ua/board/2

files are located here:
http://dl.fail.pp.ua/slackware/firef...r_V2.19.01.bin
http://dl.fail.pp.ua/slackware/firefly-rk3288/boot.img
http://dl.fail.pp.ua/slackware/firefly-rk3288/flash.sh
http://dl.fail.pp.ua/slackware/firef...parameters.txt
http://dl.fail.pp.ua/slackware/firef...8/resource.img
http://dl.fail.pp.ua/slackware/firef...09Mar15.img.7z

@sndwvs: Congratulations and thank you for providing Slackware for Firefly-RK3288.
I got mine just a couple of days ago and I'm still experimenting with it.
Is the Slackware release you made a soft or hard-float one?
I am interested in video playback and so obviously a hard-float release will suit me fine!

@rouvas: Is the Slackware release you made a soft or hard-float one?

collected from Slackware-current which is soft
prepares a with xfce environment, installed and configured the video drivers

new assembly system

info
http://fail.pp.ua/public/board/2

changelog:
added image with the desktop xfce
installed video driver mali fbdev t76x_r5p0-06rel0
support 32 bit color in X
added unprivileged user
load faster dhcpcd
resize partition firstboot device
wifi firmware moved to /lib/firmware
wifi enable /etc/rc.d/rc.wifi start|stop (in rc.local)

• small hotfix
• added support in the kernel nfs, xfs, btrfs, jfs

info
http://fail.pp.ua/public/board/2

Two things I wanna ask you:
1. Can you give me a solution to flash it using windows? I got no linux machine at the moment
2. Does it have video acceleration?

1. flash windows guide http://radxa.com/Rock/flash_the_image
2. OpenGL ES Linux support on Firefly-RK3288 Development Board. Firefly-RK3288 development board is equipped with the powerful Mali T764 GPU. Lately, ARM has released the binary user-space fbdev driver.

No succes at all. It says "loading firmware failed" when using rkbatchtool. Any idea why?

this official wiki: http://enwiki.t-firefly.com/index.ph...Flash_image/en

Still no luck. It says again "Loading firmware failed" in AndroidTool. I tried also Rkbatchtool and the same message is present, plus few extra infos, like in the screenshot attached. Interesting that the support chip is reported as RK31, not RK32.

Attached Thumbnails