Age | Commit message (Collapse) | Author |
|
0001-memcpy-don-t-use-optimized-for-VFP-NEON-versions.patch applies
not to oe glibc_2.21
|
|
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Don't write the eMMC twice on Apalis in the not migrate case.
|
|
|
|
|
|
|
|
Add LOCALVERSION and generate a scmversion file to annotate the
Kernel with the Toradex release and a git hash.
|
|
It seems that Connman disables ALL interfaces on startup, even if
they are listed in NetworkInterfaceBlacklist. This leads to the
following situation:
networkd starts...
usb0 gets created...
networkd sets the device up (event triggered)
connman starts... and sets the device down!
networkd does not restart the device in this situation. To avoid
the situation, create the USB Gadget functions after connman. It
seems that if connman is up and running, it does not touch the
device anymore.
|
|
Since we use USB Gadget ConfigFS now use libusbg to load the
USB Gadget configuration automatically.
|
|
The Vybrid devices use a composite gadget device by default which
offers a serial connection over USB on the USB peripheral port.
This enables a serial console on that tty.
|
|
|
|
Change DEFAULTTUNE in machine configurations to Thumb-2.
|
|
To download the sources mirrored on sources.toradex.com add
the Toradex mirror as pre-mirror.
|
|
Up until now, U-Boot for Colibri VF50/VF61 did not had an
environment variable board_name. Use the soc environment
variable to set the board_name.
|
|
To avoid code duplication call fwd_blk from fwd_mmc. This adds
one more indirection, but since flash_mmc.img is a compatibility
script anyway it is not the common case...
|
|
Source the update script only if loading succeeded. This avoids
loops if board_name is not set. Also add a test if board_name is
really set since this variable is/was not available in older
U-Boots.
|
|
Further generalise U-Boot update scripts by using ${board_name} instead
of hard coding module name like apalis_t30, colibri_t20 or colibri_t30.
|
|
Even though our downstream L4T based kernel does not use any
device tree stuff prepare for easy deployment thereof by using the
correct dtb name.
In the Ethernet aka TFTP update case this actually fixes an issue where
it previously tried to TFTP the whole ${board_name} directory which at
least on my setup failed with a permission denied which it retried
forever.
|
|
Deploy and enable CPU hot-plug configuration and startup on our T30
based modules. This significantly reduces power-consumption and
therefore improves thermal characteristics.
|
|
Systemd startup script for NVIDIA T30 CPU hot-plug configuration.
|
|
List all Toradex machines explicitly while still selecting Colibri
T20 by default. Move selection of Qemu targets after our machines.
|
|
|
|
|
|
meta-openembedded provides a recipe for joe, use that one.
|
|
|
|
Introduce/update postinst code to dynamically adjust fw_env.config and
fw_unlock_mmc.sh shell profile extension script to cope with our new
unified eMMC layout:
boot area partition 1 aka primary eMMC boot sector:
with U-Boot boot loader and the U-Boot environment before the
configblock at the end of that boot area partition
|
|
Introduce SRCBRANCH notation for easier switching to our -next branch.
|
|
The evdev version provided by oe-core is in the meantime newer than
this backport, hence we can safely remove it.
|
|
This reverts commit ae568dc9b001306a0723daccf3ea7912d94438ee.
http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-core/systemd/systemd_219.bb?h=fido&id=0cd5a0d5445ff95a8ef4abe24fef705957935e81
fixes the automount issues we have during boot.
So revert the patch which completely disabled the feature.
|
|
|
|
This reverts commit a1040ca051f6c66bc5205502a462d55490653360.
http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-core/systemd/systemd_219.bb?h=fido&id=0cd5a0d5445ff95a8ef4abe24fef705957935e81
fixes the automount issues we have during boot.
So revert the patch which completely disabled the feature.
This (re)introduces the issue that removable media attached during runtime
does get mounted with dbus / udisk in a different fashion.
But the fact that media connected at boot is actually mounted before the
system reaches its running state and that automount works when one disables
the start of the display manager outweights this.
|
|
oe-core moved the mountpoint used to /run/media/<drive>.
In our setup we don't see issues with /media being read only
when udev starts mounting.
In our environment with graphical desktop udisks will later take over
the automount job and udisks currently still uses /media,
so keep this consistent between mounting at boottime and mounting at runtime.
Refer to openembedded-core commits:
acfe3014d41de5e87cdbc58d0396349c6b9c3ffd
62ae16c40252f39ba28e072218d67f47b26b3535
|
|
|
|
Update our U-Boot update scripts to accommodate our new unified eMMC
layout:
boot area partition 1 aka primary eMMC boot sector:
with U-Boot boot loader and the U-Boot environment before the
configblock at the end of that boot area partition
Handle migration of boot loader and configblock on Apalis/Colibri iMX6.
When doing a full update also explicitly flash kernel and FDT from the
update medium in order to allow for easy updating thereof.
|
|
Further clean-up and unify our update scripts:
- Universally mention Ethernet aka TFTP, SD card and USB flash drive as
possible update media.
- Universally mention detailed recovery/update procedures being
available on our developer website.
- Universally split usage and flashing instructions (-f).
- Make sure we don't exceed the 80 characters line length limit.
- Fix various spelling issues.
|
|
Now that both Apalis/Colibri iMX6 as well as Apalis/Colibri T30 will
use the same eMMC layout also concerning boot loader, environment and
configblock locations in the primary eMMC boot area partition update
resp. description.
|
|
The following commit:
f463f754048ebc3325025f0e1506b03cf14203a5
update.sh: use moduletype specific folder for output files
moved the output folder check above the module type selection which now
fails in case of debug aka recovery mode only operation with the
following error:
does not exist, exiting
This patch fixes this by not erring out in the debug aka recovery mode
only operation if no output folder is set.
|
|
|
|
|
|
Non graphical images will never execute graphical.target services.
|
|
|
|
|
|
|
|
|
|
qtdemo-init exists in another recipe for qte. When both recipes are
built we get an error during sysroot deployment.
|
|
With fido e2fsprogs did split out the package e2fsprogs-resize2fs.
RRECOMMEND it so that it gets picked up during rootfs creation.
|
|
With update.sh one creates files on e.g. a SD-card or a tftp server
which enables updating the SW on a module from U-Boot running on
said module.
This commit adds a module type specific directory on that output media
so that update data for multiple module types can be stored on one media.
Generic U-Boot scripts in the media's root directory do select the
matching update data depending on module type.
|
|
|