Go back to have our own do_configure. The kernel.bbclass would
execute "oldnoconfig" where we simply executed "oldconfig". Keep
on using our old way (for the legacy of it). E.g. with the question
how we ended up having SMP enabled in the BSC build this might
be the answer.
OE-Core seems to unpack the kernel sources into another
directory now (e.g. to share the sources with builds for
modules). Use the kernel.bbclass kernel_do_configure and
copy the .config to the build directory.
The kernel is now built in a dedicated build directory.
We actually only use the PMIC (TPS65910) RTC in the hardware,
and not the AM335x RTC. Having a driver for a hardware that doesn't
receive actual backup voltage doesn't make sense.
The odu-gpiotool is a small script created by roh to selectively reset
individual peripherals of the system by the administrator. It originates
from ticket https://projects.sysmocom.de/ortelius/issues/655
We use the new sysfs file to obtain the board version number and
configure the port swapping accordingly. If the board_version sysfs
attribute is not present, we default to v2.
We also integrate resetting the hub chip from within this tool right
befeore writing the new register values via I2C.
[hfreyther: We assume that the user might install OpenVPN with
a different priority but that it will always be available in the
runlevel two (e.g. even if the user changed the default runlevel)]
Related: SYS#517
Similiae to the layer code we simplify the machine include to work
for all versions of a 1.5 release. Poky 1.5.4 has been released and
we don't want to continue to play this game.
I have no idea who creates the /run/openvpn directory on Debian.
The path is not in a tmpfiles.d and I don't see the generator
creating it or the service file indicating that it needs to be
created. Place the file with openvpn.NAME.status into the /run
directory which appears to work on the device.
We want to use systemd for managing the lifetime of OpenVPN. Take
the debian generator (which should work with busybox ash) and the
openvpn.service (to inhibit the sysvinit script) and the target
file and install it.
On systems that have ran "update-rc.d openvpn defaults" one need
to manually execute a systemctl enable openvpn.service. This is
not done through a post-inst script and I am not sure if we should
do it. This means there is a danger of ending with a unit that
doesn't start OpenVPN automatically after upgrade!
The scripts/packages have not been tested on a device yet.
We should use a more recent version of the OpenVPN client. Import
it from the meta-networking layer like we did before. The sysvinit
script has just minor whitespace differences and wasn't imported.
We need to test opkg upgrades of OpenVPN through the VPN. We don't
want to kill the tunnel on such upgrade.
One might need to erase the environment but with a default
environment barebox will now send a LLDP during boot up. This
way we can see if a device is on a local link or not.
Fixes: SYS#488
* split out rtl-nic firmware from the big
linux-firmware package
[hfreyther: For whatever reasons the NIC works without
additional firmware as well. I couldn't see in the driver
source when that is the case and which features are missing]