diff options
Diffstat (limited to 'meta-n450/ReleaseNotes')
-rw-r--r-- | meta-n450/ReleaseNotes | 148 |
1 files changed, 0 insertions, 148 deletions
diff --git a/meta-n450/ReleaseNotes b/meta-n450/ReleaseNotes deleted file mode 100644 index 67e3ff20..00000000 --- a/meta-n450/ReleaseNotes +++ /dev/null | |||
@@ -1,148 +0,0 @@ | |||
1 | Poky Laverne Release 4.0 | ||
2 | |||
3 | - Dependencies | ||
4 | - Features and Updates | ||
5 | - Known Issues | ||
6 | |||
7 | DEPENDENCIES | ||
8 | ============ | ||
9 | |||
10 | This layer depends on: | ||
11 | |||
12 | URI: git://git.openembedded.org/bitbake | ||
13 | branch: master | ||
14 | |||
15 | URI: git://git.openembedded.org/openembedded-core | ||
16 | layers: meta | ||
17 | branch: master | ||
18 | |||
19 | URI: git://git.yoctoproject.org/meta-intel | ||
20 | layers: intel | ||
21 | branch: master | ||
22 | |||
23 | URI: git://git.yoctoproject.org/poky | ||
24 | layers: meta-yocto | ||
25 | branch: master | ||
26 | |||
27 | NOTE: n450 currently depends on meta-yocto due to atom-pc | ||
28 | dependencies. The plan is to move atom-pc to meta-intel as soon as | ||
29 | the layer tooling comes online and meta-yocto becomes its own | ||
30 | repository. At that point, meta-yocto will no longer be required. | ||
31 | |||
32 | Note also that the layering with respect to the poky repository is in | ||
33 | transition; it currently contains both meta from openembedded-core and | ||
34 | bitbake along with some other files and directories which will | ||
35 | eventually be contained in standalone repositories once the ongoing | ||
36 | layering work has been completed. As such, the master branch of the | ||
37 | poky repository can at the present time be used to satisfy all | ||
38 | meta-intel dependencies. | ||
39 | |||
40 | |||
41 | PATCHES | ||
42 | ======= | ||
43 | |||
44 | Please submit any patches against this BSP to the Yocto mailing list | ||
45 | (yocto@yoctoproject.org) and cc: the maintainer: | ||
46 | |||
47 | Maintainer: Darren Hart <dvhart@linux.intel.com> | ||
48 | |||
49 | Please see the meta-intel/MAINTAINERS file for more details. | ||
50 | |||
51 | |||
52 | FEATURES AND UPDATES | ||
53 | ==================== | ||
54 | |||
55 | - Poky Build System Updates | ||
56 | * Saved State / Checksumming | ||
57 | * Working prebuilt packages | ||
58 | * If a cache of prebuilt packages is present, these should be | ||
59 | used to accelerate the build | ||
60 | * Task based prebuilts | ||
61 | * Meta Directory Update | ||
62 | * Debug symbols into sysroot | ||
63 | * Builds outside Poky TMPDIR | ||
64 | * Can install to a readonly directory | ||
65 | * Ability to Build GPL v2 only target images | ||
66 | * Swapper integrated to detect host contamination | ||
67 | - Prelink Tool Integration | ||
68 | * Integration of cross prelink tools into Poky | ||
69 | - Toolchain Update | ||
70 | * GCC 4.5.0 now default compiler | ||
71 | * EGLIBC is default libc provider | ||
72 | - New and Updated Recipes | ||
73 | * Major update of core recipes | ||
74 | * Add additional packages to get initial lsb support | ||
75 | * Add QT4 Libraries and demo code | ||
76 | - Packaging | ||
77 | * rootfs creating done with RPM | ||
78 | * Use pseudo for setting ownership and permissions | ||
79 | * Software package Management now use RPM5 and Zypper | ||
80 | - Standalone Yocto Linux SDK Generator | ||
81 | * Enable other SW development | ||
82 | * Output from Poky | ||
83 | * Cof a sysroot representing a target system | ||
84 | * Includes a standalone cross compiler and cross build tools to isolate the two systems | ||
85 | - Yocto Linux SDK Generator IDE Plug-ins | ||
86 | * Work within IDE using Yocto sysroot environment and cross platform toolchains | ||
87 | * Remote user spacke tool suite interaction | ||
88 | * Eclipse | ||
89 | * Anjuta | ||
90 | - Yocto Linux SDK Generator remote agent | ||
91 | * Runs on a "device" | ||
92 | * Manage tasks e.g. deployment, launching remote tools, setup cross debugging session | ||
93 | - Yocto Linux SDK Generator remote tasks support | ||
94 | * Remote deploy support | ||
95 | * Remote debug suppport | ||
96 | * Remote tools interaction | ||
97 | - Qemu basic system simulation/emulation | ||
98 | * Enhanced with GL passthrough | ||
99 | * Support user mode NFS | ||
100 | - User space tool suite for target device tuning, analyzing and optimizing | ||
101 | * OProfile | ||
102 | * Powertop | ||
103 | * Latencytop | ||
104 | * Perf | ||
105 | * ftrace/lttng user space | ||
106 | - Host side clients for tools on target devices and IDE interaction | ||
107 | * ProfileUI | ||
108 | * Lttv-viewer | ||
109 | - Updated Documentation | ||
110 | * Core Reference Manunal Updated | ||
111 | * BSP standard document | ||
112 | * Quick Start Guide | ||
113 | * FAQs | ||
114 | |||
115 | |||
116 | KNOWN ISSUES | ||
117 | ============ | ||
118 | |||
119 | See bugzilla.yoctoproject.org | ||
120 | |||
121 | 382 - oprofile-server on PPC is built big-endian while oprofile-viewer | ||
122 | on host system may built with little-endian, but oprofile-server | ||
123 | and oprofile-viewer are not implemented to correctly handle | ||
124 | conversion between host byte order and network byte order, so | ||
125 | oprofile-server and oprofile-viewer may run into connection issue. | ||
126 | |||
127 | 439 - No audio from the Blacksand board Front Channel auido jack. | ||
128 | Workaround: run the following cmd: 'amixer sset "Front" 30 on' | ||
129 | |||
130 | 467 - Issues building with Fedora 14, this distribution provided a version | ||
131 | of make that is not compatible with the Poky build system, the | ||
132 | workaround it to build a native version of make via the build system. | ||
133 | Users of Fedora 14 will need to do a 'bitbake make-native' before | ||
134 | running any other targets. | ||
135 | |||
136 | 429 - Building poky from scratch with /opt/poky in your path cause host | ||
137 | contamination issues, be sure that /opt/poky is not in your path | ||
138 | if building from scratch | ||
139 | |||
140 | 160 - The Emenlow Hardware gets stuck in the HW Reboot sequence and needs | ||
141 | to be power cycled. | ||
142 | |||
143 | Zypper / RPM Issues | ||
144 | 489/490/491 - Due to some archetectual difference between Zypper and RPM5.0, | ||
145 | there are some compatibility issues that prevent zypper from | ||
146 | working correctly. | ||
147 | Packages can still be managed with the rpm commands. | ||
148 | |||