Age | Commit message (Collapse) | Author |
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
machine/u-boot/kernel files have been added to meta-fsl-arm-extra.
Use them from there now.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Update to latest revision which fixes Colibri iMX6D not powerering off but
creating a stacktrace.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
We have this recipe in meta-fsl-arm-extra.
Convert it to a bbappend and only keep the changes to the bb files.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Change the name form u-boot-it.imx to u-boot.imx-it.
This prepares for the upcomming move of the i.MX 6 based modules BSP
to meta-fsl-arm-extra.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Despite the reordering of when to load the USB Gadget configuration
with commit fadb16f153aa ("libusbg: enable USB Gadgets after Connman
to avoid interference") the network device ended up to be down after
startup. It seems that there is a race condition in systemd-networkd
which triggers especially in combination with USB Gadget, a issue on
the systemd issue tracker has been created:
https://github.com/systemd/systemd/issues/1784
There have been various changes related to link handling between
systemd 219 and the latest version 227. It is possible that the issue
is already solved.
Until this has been resolved, explicitly load the USB Gadget before
starting systemd-networkd seems to get around the issue.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
|
|
|
|
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.
|
|
|
|
meta-openembedded provides a recipe for joe, use that one.
|
|
|
|
The evdev version provided by oe-core is in the meantime newer than
this backport, hence we can safely remove it.
|
|
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
|
|
|
|
|
|
|
|
Non graphical images will never execute graphical.target services.
|
|
With fido e2fsprogs did split out the package e2fsprogs-resize2fs.
RRECOMMEND it so that it gets picked up during rootfs creation.
|
|
Update defconfig and kernel version to latest version from git. This
also configures the USB Gadget ConfigFS as a module. Add the ConfigFS
module to the list of autoloaded modules.
|
|
We noticed that our latest move to using systemd/networkd leaves the
rndis0 interface down. Manually bringing the link up solved the issue.
As a workaround add upping the link to our start-rndis.sh script.
|
|
Follow the rename imx6q-apalis-eval_v1_0.dtb to imx6q-apalis_v1_0-eval.dtb
in the kernel.
The v1_0 denotes the Apalis module version, not the evaluation board version.
|
|
|
|
|
|
This reverts commit bd2d32bf3a8460c87849e75ad01e11450d8cda10.
Remove the backport, is part of fido.
|
|
gpu-viv-bin-mx6q -> imx-gpu-viv
with a bunch of subpackages.
|
|
|
|
|
|
|
|
SCSI lock device disk support is required for USB mass storage to
work. Also enable asynchronous SCSI scanning by default.
|
|
Use a fixed revision of the MCC kernel module which makes sure it
builds with the corresponding Vybrid Linux kernel, which also uses
a fixed git hash.
|
|
|
|
And use 2015.04-toradex branch
|
|
|
|
|
|
|
|
|
|
Angstom Dizzy now uses systemd V218 so there is no need to build
a component seperately anymore.
This reverts commit 16b8b392ad048566729f30d7c3887d1bfdf21bd4.
|
|
Use systemd V2.18 from meta-angstrom.
Issues with firmware loading and the 3.1.10 kernel for the tegra machines
are fixed with a backport from oe-core.
|
|
This changes the minimum required Linux version from 3.7 back to 3.0.
[YOCTO #7409]
Signed-off-by: Jonathan Liu <net147@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
backported from openembedded-core,
commit 31163abc7bedd477c1aad10e6d1f47dbee194513
|
|
This reverts commit 3cf2edb10f5e8ac60db7ca2e71d1e754a177d08c.
Conflicts:
recipes-core/systemd/systemd_%.bbappend
|
|
|