| Age | Commit message (Collapse) | Author |
|---|
|
When the link goes down, the DHCP service has been disabled, while
there is no corresponding functionality which enables the service
when the link goes up again. This fix is taken from systemd 217.
|
|
This removes the 3.0.15 based Kernel for Colibri VFxx.
Since some time now we use a more recent Kernel provided from the
linux-toradex-vf_3.18.bb recipe.
|
|
|
|
Use the resize command to set the size of the terminal once upon
login. This is useful for serial console, where the default Unix
signal which takes care of resizing the console (SIGWINCH) is not
available.
|
|
There are no more differences in fstab between machines, hence use
the same common file. The default profile has some differences,
however we can seperate them out and create a file which will be
installed in profile.d.
missing
|
|
Connman gained support for USB gadget. The typical usecase is to use
USB gadget for tethering. In this use case the module would be the
device sharing the connection to the USB host connected to the module.
However, our typical use case in mind for RNDIS is a simple ethernet
connection between a development host and the module, hence no need
for tethering/routing. This however is not easily doable with connman,
since connman tries to have one connection online only. When enabling
USB gadget as a normal ethernet device, this typically leads to classic
ethernet not being configured since the USB RNDIS connection is already
up and running.
By blacklisting USB gadget, connman won't touch the device and we can
use other means of bringing up the network interface.
|
|
eglibc has been superseded by glibc. Update the PREFERRED_PROVIDER
to use set the preferred provider of glibc.
|
|
This enables the resize command in Busybox. The command is useful
when using the serial console and a non-standard terminal sizes.
|
|
|
|
Unifing with imx6 update script pulled in a test that a device-tree
must be deployed. Apalis/Colibri T30 use a not device-tree enabled
Kernel. So remove the check that the device-tree actually exists.
|
|
we don't want busybox syslog as we use the functionality of journalctl
|
|
The migration to BSP V2.4 is somewhat more complex due to ECC level
change. The scripts detect whether we are on a new or old module by
checking the NAND driver type (which probably reflects best which
ECC level has been used). In case the NAND driver has the old name
(fsl_nfc), then the script assumes that migration is required:
The migration script runs in two stages:
- The first part updates U-Boot, erases the root file system and
loads the config block into memory (upgrade_part1).
- After reboot, the second stage runs with the new U-Boot version.
The script update the boot configuration block (BCB), restores the
config block from memory and U-Boot is written again using the
new ECC level. Then, the script erases the UBI partition (which
contains the root filesystem) and recreates it using the new ECC
level too (upgrade_part2).
Since we keep the config block temporarly in RAM, the whole update
process should not be interrupted! In case it did, the new U-Boot
version is able to restore the configuration block from command
line.
In contrast to older update scripts, the standard upgrade procedure
does not erase the whole UBI partition anymore. This makes sure that
wear-leveling information can be preserved.
|
|
Those packages are not required or not absolutely necessary, hence
remove them for the Vybrid image to loose space constraints on
Colibri VF50 somewhat.
|
|
In contrast to the full NTP implementation systemd-timesyncd only
supports the client side of the NTP protocol. In return, the systemd
implementation is ~250kBytes smaller. Since most embedded devices
require client side only, use systemd's timesyncd.
|
|
Make the option -o mandatary, used to default to /media/KERNEL
While at it synchronize the files again.
|
|
Update to latest version (SVN r671) of burnflash.
|
|
Update to latest version (r663) of Vybrid flash scripts.
|
|
|
|
PublicDomain is not known to OE
|
|
PublicDomain is not known to OE
|
|
|
|
Pull out common files of the module specific trees into the common library
directory and symlink the files.
|
|
Drop the burnflash.tar.bz2 tarball and put the individual files under
version control.
Only create minimal set for colibri-t20 for now and move it with the
change to tegra-uboot-flasher.
|
|
|
|
Neiter graphviz_2.32.0.bb graphviz_2.38.0.bb work with dizzy.
Uses python directory from build host.
|
|
The SUMMARY variable gives a short description of the package (<72 chars).
A missing DESCRIPTION is automatically set to the content of SUMMARY.
|
|
${PN} might be extended with some magic prefix, so don't use it in SRC_URI
assignments et. al.
|
|
|
|
There is no difference between iMX6 / Tegra based modules
|
|
|
|
remove consistent_defconfig_dirs.patch as it is no longer needed
starting with 0.5.6
consistent_defconfig_dirs.patch is no longer needed.
change bbappend to contain % instead of the version
|
|
Add the lxde components with meta-lxde packagegroups
and the window and display manager here.
|
|
Don't explicitely add packages already added by the lxde package group.
|
|
Mechanism changed to what the bb file now offers.
|
|
While at it move version to % placeholder and use wildcards in receipe
icu: use wildcard to be independent of version
|
|
The default changed to zImage so explicit set uImage for now.
While at it cleanup the recipe, remove pci from Colibri machine features.
|
|
|
|
|
|
compiling gvfs with samba support in dizzy does not only pull in smbclient
but the full samba package, i.e. 50MB+.
|
|
gnutls recipe now detects pthread in configure task correctly.
|
|
|
|
|
|
|
|
|
|
While at it replace Tegra machines with SOC family
Conflicts:
recipes-qt/qt4/qt4-x11-free_4.8.5.bbappend
|
|
|
|
|
|
|
|
Update to top of -next branch which also includes FEC unbind
fixes.
|
|
- Make sure leases file is not persistent (in /var/run now)
This allows to serve the same IP to the generated (and hence
different IP addresses)
- Start RNDIS service after the network.target
- Tegra: Add extra service for udhcpd. When running dhcpd directly
from udev, the daemon will be killed after a while
|
