Here are some basic Tegra test results for Linux v4.5-rc5.
Logs and other details at:
https://nvtb.github.io//linux/test_v4.5-rc5/20160220140102/
Test summary
------------
Build: zImage:
Pass: ( 2/ 2): multi_v7_defconfig, tegra_defconfig
Build: Image:
Pass: ( 1/ 1): defconfig
Boot to userspace: defconfig:
Pass: ( 3/ 3): qemu-vexpress64, tegra132-norrin,
tegra210-p2371-0000
Boot to userspace: multi_v7_defconfig:
Pass: ( 4/ 4): tegra114-dalmore-a04, tegra124-jetson-tk1,
tegra20-trimslice, tegra30-beaver
Boot to userspace: tegra_defconfig:
Pass: ( 4/ 4): tegra114-dalmore-a04, tegra124-jetson-tk1,
tegra20-trimslice, tegra30-beaver
PM: System suspend: multi_v7_defconfig:
FAIL: ( 1/ 4): tegra114-dalmore-a04
Pass: ( 3/ 4): tegra124-jetson-tk1, tegra20-trimslice,
tegra30-beaver
PM: System suspend: tegra_defconfig:
FAIL: ( 1/ 4): tegra114-dalmore-a04
Pass: ( 3/ 4): tegra124-jetson-tk1, tegra20-trimslice,
tegra30-beaver
vmlinux object size
(delta in bytes from test_v4.5-rc4 (18558cae0272f8fd9647e69d3fec1565a7949865)):
text data bss total kernel
+60 +512 +128 +700 defconfig
+1596 +224 0 +1820 multi_v7_defconfig
+1320 +232 0 +1552 tegra_defconfig
Boot-time memory difference
(delta in bytes from test_v4.5-rc4 (18558cae0272f8fd9647e69d3fec1565a7949865))
avail rsrvd high freed board kconfig dtb
. . . . qemu-vexpress64 defconfig __internal
-8k 8k . 4k tegra114-dalmore-a04 multi_v7_defconfig tegra114-dalmore
. . . . tegra114-dalmore-a04 tegra_defconfig tegra114-dalmore
-8k 8k . 4k tegra124-jetson-tk1 multi_v7_defconfig tegra124-jetson-tk1
. . . . tegra124-jetson-tk1 tegra_defconfig tegra124-jetson-tk1
. . . . tegra132-norrin defconfig tegra132-norrin
-8k 8k . 4k tegra20-trimslice multi_v7_defconfig tegra20-trimslice
. . . . tegra20-trimslice tegra_defconfig tegra20-trimslice
. . . . tegra210-p2371-0000 defconfig tegra210-p2371-0000
-8k 8k . 4k tegra30-beaver multi_v7_defconfig tegra30-beaver
. . . . tegra30-beaver tegra_defconfig tegra30-beaver
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
