| Age | Commit message (Collapse) | Author |
|---|
|
The LM006 USB WiFi adapter uses a Realtek RTL8188CUS chipset,
which requires the compatible firmware RTL8192CU.
Signed-off-by: Bhuvanchandra DV <bhuvanchandra.dv@toradex.com>
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
With the cfgblock command in U-Boot we now have a better solution.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Don't write the eMMC twice on Apalis in the not migrate case.
|
|
|
|
Since we use USB Gadget ConfigFS now use libusbg to load the
USB Gadget configuration automatically.
|
|
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.
|
|
|
|
meta-openembedded provides a recipe for joe, use that one.
|
|
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.
|
|
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.
|
|
|
|
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.
|
|
|
|
To flash a large rootfs over tftp the rootfs must be split into chunks
of 64MB on the tftp server.
Add the option '-c' to the update.sh script which does this automatically.
Use 64MB chunks on all module types.
|
|
While at it:
- remove the default directory for the -o parameter
- cleanup text and sort variables
|
|
Switch to using the temperature Chamber validated 800 MHz BCT
Apalis_T30_2GB_800Mhz.bct.
Please note that for now this is a fixed 800 MHz BCT which does not
allow for memory DVFS (e.g. 400/800 MHz switching like currently only
possible on Colibri T30).
|
|
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.
|
|
Conflicts:
recipes/images/angstrom-qt-x11-image.bb
|
|
While we were checking whether the mkfs.ubifs tool has the magic
--space-fixup option available we never actually enabled that option
to be used when generating our UBIFS root file system images.
Thanks Bhuvan for spotting this having actually been in our update
scripts for almost two years now!
|
|
Prepare the rootfs for a future kernel which allows to use modesetting.
|
|
|
|
Newer kernels use a user space deamon to control wifi regulatory domains.
Deploy the user space deamon in all images independent on what kernel
version is used.
|
|
Without this the colibri-vf u-boot is not built.
|
|
gpu-viv-bin-mx6q -> imx-gpu-viv
with a bunch of subpackages.
|
|
|
|
kernel-module-mcc is now provided as virtual/kernel-module-mcc.
Pull it in via depends of libmcc and automatically choose the
correct one.
|
|
Now that we exit on failure the test for a user accessible parted must not
return an error code.
|
|
On recent Ubuntu distributions gawk no longer supports awk -V which makes
the test fail.
Simulate our awk use case and test the result instead.
Additionally set 'set -e' to exit immediately on errors. Fix places where
a command returns not zero in 'normal' situations.
E.g. A full disk leads otherwise to funny effects.
Allow relative OUT_DIR.
|
|
The eMMC layout comments are confusing and in some regards outdated.
Clean it up.
While at it move the calculation of the rootfs file system size to
the rootfs creation to not confuse the rootfs file system size with
the size of the rootfs partition.
|
|
U-Boot now has the command cfgblock which can be used to create a valid
configblock.
Alternatively one can be created with create_configblock.sh.
|
|
Cleanup: Use the append operator to add soc-arch/machine specific
packages to IMAGE_INSTALL.
No change in the image is intended.
|
|
add the missing _append
|
|
remove connman-gnome applet and libwnck which make no sense in a qt image.
|
|
gpioconfig depends on gtk+
|
|
The resize command confuses Eclipse's launcher.
On a ssh console resize isn't needed anyway so only start it if
the console device starts with /dev/tty to work around the issue.
|
|
The mmc unlock function causes troubles when using Poky reference
distribution since Poky uses the busybox shell:
/etc/rc5.d/S09xserver-nodm: /etc/profile.d/fw_unlock_mmc.sh: line 2: syntax error: unexpected "("
This avoids X getting at all.
This patch does not solve the underlying problem, but works around it
by moving the script to the u-boot-toradex-fw-utils recipe, which is
not installed by the Poky images by default.
|
|
Remove udev-extra-rules since the main functionality, automatic
mounting using udev/mount.sh, does not work anymore. Systemd
starts the udev daemon using mount namespaces, which leads to
mounts not being visible outside of the udev processes scope.
Hence the file system get mounted, but other then the udev process
nobody can actually use them.
To make mounting using udev/mount.sh work again, one needs to
remove the MountFlags option in the systemd-udevd.service file
(/lib/systemd/system/systemd-udevd.service).
Another possible solution which might fit the needs of automouting
is to use a systemd mount unit.
|
|
Currently udisks and udev-extra-rules (which provides a udev based
automount approach) are installed. Since the UI is prefering the
D-Bus based udisks approach, remove udev-extra-rules in favor of
udisks.
|
|
We now use mkimage during do_imagedeploy to build the u-boot scripts.
For machines which build a zImage this tool has not yet been built and
we get an error because the tool is missing.
|
|
GPIOConfig CPU detection was broken on Colibri VF50. Update to latest
revision 674 which fixes CPU detection on newer kernel for Colibri
VF50 too.
|
