Silently a new 96board starts appearing: Cello
It seems to be produced by LeMaker and is based around the AMD A1100
SoC. That's the same as on the illusive Husky, actually both boards look
very similar with only minor differences in the placement of some
The LeMaker product page has it up for preorder for 299$; with an
estimated shipping time frame of 2016Q2.
This could mean the first "cheap" 64 bit ARM server board becoming
available. Also more power: A57 cores.
Though I'm sure hrw will still disapprove as it has SATA, but is a weird
non-industry-standard form factor.
Oh, and the obligatory question:
Will it be 96boards compliant and are we going to get to see the actual
I also add support(a)linaro.org so we can track and follow up your
questions more formally. Also translate your question into English as
we can ask more English speaker to help for related questions as needed.
So the questions is "how to profiling IPA and enable ftrace event for
- In generally, please don't manually do this thing by yourself.
Workload-automation has prepared all this profiling flow already:
This docuemenation is very important when you want to easily start:
- To enable workload-automation, you need set configuration file at
host PC side so it can connect with board smoothly:
This file usually is in the folder:
~/.workload_automation/config.py; so "wa" command will use this
configuration file to connect target board.
- Then need define the testing configuration file so that can run the
test case automatically, enabling ftrace events, and finally
output profiling log files, you can refer the file:
wa run ~/ipa_tunning.yaml -d ipa_tunning
So finally you will all logs are saved in "ipa_tunning" folder.
- After get the result, it will save trace.dat file into the log
folder, so you can use trappy to analyse the file for temperature
curves. The trappy have a very good example file is:
I have enclosed my ~/.workload_automation/config.py file and
ipa_tunning.yaml for reference. If have any further question, just let
On Mon, Jun 20, 2016 at 05:05:03PM +0800, lu.baoquan(a)zte.com.cn wrote:
> 2.打开Function Tracer，下面这些events是否满足
> trace-cmd record -e cpu_frequency* -e cpu_idle -e thermal -e
> 能否提供一个WA Agenda的模板
> ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
I am playing with Hikey and I am able to get wifi up and running on 3.18
Linaro kernel base/hikey branch. But I am not able to get it work on 4.4
The problem is that st_tty_open is not called that's why it looks like
that problem could be with line discipline setup.
Do you have any kernel/branch with 4.4+ where BT is working?
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs
We now see better support for HiKey in v4.7-rc1 mainline vanilla, and
following features landed in v4.7-rc1: dts, configs, pmic, and drm.
Features supported from mainline kernel include:
- usb otg and host (high-speed mode)
- microSD card
- uart on Low-speed expansion port (LS)
- I2C on LS
- SPI on LS
- WiFi (need update UEFI to latest, see below for link)
Just for your curiosity, in v4.6, we upstreamed: usb & usb phy,
(CONFIG_PHY_HI6220_USB), hi655x regulator, hi6220 mailbox, hisi reset,
and mmc dw k3.
git checkout -b YOUR-WORKING-BRANCH v4.7-rc1
make ARCH=arm64 defconfig;
make ARCH=arm64 Image modules hisilicon/hi6220-hikey.dtb -j20;
1. latest UEFI:
2. Debian rootfs:
Then, replace Image and dtb, you can see v4.7-rc1 running on HiKey.