This currently requires the meta-ti layer but we will make sure
that nothing from it will be required in the end. The kernel is
based on linux-3.2 as this is the "default" TI kernel that supports
the SGX (not that we care)
This is the latest stable kernel. I had hoped some crashes to
go away with it but it turns out to be a compiler issue that
we backported a patch for separately.
* The Linux 3.2.X kernel has some funny issues with GCC 4.8 in the
fs/namei.c look up code. It is easier to move to 3.10 than to fully
debug the issue.
* disable the mISDN loop patch for v3.10
* use the hack to make v3.2 compilable for edison and v3.10 for dora
Provide custom systemd config files to enable the watchdog handling. For
systemd we depend on the image containing and using systemd as init script.
In case we build images without systemd we will need to install the
old watchdog. Maybe it is time to create a MACHINE_FEATURE for watchdog.
The build differs in that it doesn't use a getty on ttyS0. In the fuutre,
a modified kernel serial driver as well as a 2050-specific utility
for managing the supervisor processor will follow.
The rootfs in the UBI is configured to grow to the full size of the
UBI, currently these are 999 LEBs (when there is no kernel volume)
but we had limited the LEBs the filesystem can hold to 400. After
this change the filesystem will grow from the 42MB to more than 120
MB.
I'm not sure if we really want to have a rootfs of that size but we
can at least experiment with it and see if the failure rate is changing
or not.
The modules depend on kernel-base (renamed kernel-3.2.35) package,
the tasks depend on some modules and nothing needed the kernel package.
In OE Core/Poky the machines depend on kernel-modules which will pull
the kernel package into the rootfs. We do it by hand using the essential
depends and bumping the PR for the task-core-boot.
I have verified that on a kernel ugrade task-core-boot will be updated
and the kernel package is installed.
The idea is that the basic extension resides inside the the normal
recipe directories. Depending on the version of poky the bbappends
need to be included. Appends applying to all versions will be put
into the shared folder, specific ones into the specific directory.
Once a bbappend can not be shared anymore it needs to be copied.
RevB and RevC feature different kind of nand flash. RevB is still
pre-production hardware so for the few units allow to set the right
flash parameters in the local.conf.