Instead of hardcoding the magic '../N900_RescueOS/' path everywhere,
have buildroot pull package config files, patches, etc. from the
directory that holds the main defconfig file, wherever that may be.
The wl1251 driver in upstream linux kernels expects its firmware files
to live at
ti-connectivity/wl1251-fw.bin
ti-connectivity/wl1251-nvs.bin
and the linux-firmware package uses the same names for these files.
However, our current (older) kernel still expects them to be named
wl1251-fw.bin
wl1251-nvs.bin
and so firmware loading would fail.
RescueOS v1.1 included these files under the older filenames, but we'd
like to use the official (upstream) names. Patch our kernel to match.
Also remove the unnecessary (and now erroneous) firmware check from
setup-wpa-wifi.sh.
Configure buildroot to automatically build our kernel (and as a side
effect, get the kernel modules into the rootfs image). While we're at
it, defconfig-ify kernel_config.
For now, we reference the tarball at
<http://n900.quitesimple.org/rescueOS/sourcecode/kernel_source.tar.gz>
which is equivalent to commit
a91ce11c777f31ec3d04e60506bcd224f448382e
from the former MeeGo N900 device adaptation project.
Setup buildroot filesystem overlay and move our custom scripts/configs
into it. Setup a post-build script and have it delete files generated
by buildroot that aren't in RescueOS v1.1.
This gets us closer to a buildroot configuration that will automatically
generate RescueOS images. For now, we're using RescueOS v1.1 as a
reference.
Have buildroot pull busybox config from this repo. Replace
buildrootconfig with a defconfig file produced by buildroot's 'make
savedefconfig' and consumable by 'make defconfig'.
The GCC 4.6.x build system breaks when run on systems with sufficiently
recent versions of texinfo. Tweak buildroot configuration to avoid this
bug.
An equivalent workaround has been commited to buildroot (commit
62322ac). We can drop this once we upgrade buildroot and/or GCC.
GCC bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60961
