Known issues for unified OSELAS.BSP-Phytec-phyCORE releases

OSELAS.BSP-Phytec-phyCORE-12-1

	Issue: Building the GPS daemon package may fail.
		Description: The package gpsd fails to build on the ARM11 based platforms (i.MX31/i.MX35) due to missing search paths in the used binutils. This is an OSELAS.Toolchain issue.
		Solution: Use the most recent OSELAS.Toolchain available here.

	Issue: Building the directfb-examples package may fail.
		Description: The package directfb-examples fails to build if there is no quilt tool available on the host.
		Solution: Install quilt on your host.

	Refer BSP's protocols/known-issues.txt.

OSELAS.BSP-Phytec-phyCORE-12

	Issue: Building the directfb-examples package may fail.
		Description: The package directfb-examples fails to build if there is no quilt tool available on the host.
		Solution: Install quilt on your host.

	Issue: The package libiconv fails if there is a libiconv installed on the host.
		Description: libiconv's buildsystem links against the host libiconv library instead of its own built one.
		Solution: No patch from our side yet. Try to remove the libiconv library from your host. Its features are part of the regular glibc and is typically not needed on a GNU libc based system.

	Issue: The phyCORE-i.MX35 platform is broken by accident.
		Description: This release comes with an old platform release due to a wrong pointer in our revision control system.
		Solution: Download the OSELAS.BSP-Phytec-phyCORE-12-1 release.

	Refer BSP's protocols/known-issues.txt.

OSELAS.BSP-Phytec-phyCORE-11

	Issue: Display colours are inverted on the phyCORE-i.MX31 when the Sharp LQ035Q7 display is in use.
		Description: Due to a failure in the display config data the driver sets up the display hardware in a wrong manner.
		Solution: Download this patch and apply it to the BSP as described in its header.

	Issue: mt9v022 cameras can show wrong colours.
		Description: Due to a typo in the gstreamer scripts this type of cameras are using a wrong colour converter.
		Solution: Download this patch and apply it to the BSP as described in its header.

	Issue: Building the directfb-examples package may fail.
		Description: The package directfb-examples fails to build if there is no quilt tool available on the host.
		Solution: Install quilt on your host.

	Issue: Building the BSP can fail due to special environment variables.
		Description: The package fbtest fails if the environment variable TARGET is set by accident.
		Solution: Unset this variable prior starting the build.

	Issue: Audio works with bad quality on the phyCORE-i.MX27 platform.
		Description: When playing audio (with madplay or aplay) one can hear some cracking noise or audio stops suddenly. This happens on systems which uses an older U-Boot-v2 (rc3 for example) due to some strange things happen in conjunction with clock settings and the CPU frequency scaler: The scaler switches down to the lowest possible CPU frequency and audio cannot work anymore.
		Solution: Switching to the performance governor keeps the frequency scaler away from switching down CPU's frequency. Run this command to switch the system to the performance governor: $ echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

	Issue: The package fontconfig is broken.
		Description: Building the package fontconfig fails if it locates a different freetype revision on the host than used in this BSP. This happens because freetype isn't full cross-build aware.
		Solution: Download this patch and apply it to the BSP as described in its header.

	Issue: Building any of the graphic based platforms fails on systems lacking the development libraries of the zlib.
		Description: Due to a failure in one of the build rule files a host zlib is expected to be present on the host.
		Solution: Install the zlib development package on your host (for example on Debian zlib1g-dev or maybe zlib-devel on other distributions

	Issue: The quickstart for the phyCORE-i.MX27 platform describes the audio feature in an outdated way.
		Description: The count of ALSA controls and also their names changed, so the quickstart does not help to use the audio feature.
		Solution: None yet.

	Issue: The quickstart for the phyCORE-MPC5200B-IO platform describes the FPGA usage in an outdated way.
		Description: The FPGA usage part of the quickstart needs an update. The "how to use the demo firmware" does not work in the described way any more.
		Solution: None yet.

	Issue: The U-Boot-v2 coming with this BSP revision cannot work with the NAND flash memory.
		Description: An option set by accident at compiletime will inhibit any write operation on the NAND device. But disabling this option destroys the image in a currently unknown manner.
		Solution: None yet.

	Refer BSP's protocols/known-issues.txt.

OSELAS.BSP-Phytec-phyCORE-10

	Issue: Building the toolchain in the way the quickstarts mentions ends up into the follwoing message: error: The config file 'selected_platformconfig' is missing the symbol: 'PTXCONF_PLATFORMCONFIG_VERSION', which means it is broken.
		Description: One of the configuration files miss a tag variable ptxdist-1.99.12 is expecting.
		Solution: Do the ptxdist go step with the additional --force parameter. $ ptxdist --force go

	Issue: The quickstarts coming with the archive are in some ways broken or incomplete.
		Description: Bear with us...
		Solution: Use the fixed quickstarts from the download location instead.

	Refer BSP's protocols/known-issues.txt.

OSELAS.BSP-Phytec-phyCORE-9

	Issue: Running ptxdist test flash fails with a Flashing Kernel...........................Time out
		Description: This happens when the running U-Boot at target side uses an incomplete environment.
		Solution: Ensure running a ptxdist test setenv prior the ptxdist test flash.

	Refer BSP's protocols/known-issues.txt.

OSELAS.BSP-Phytec-phyCORE-8

	Issue: mtdparts kernel command line parameter uses the wrong name for the NOR flash memory in the quickstart. It uses phymapped_flash.0 instead of the correct physmap-flash.0 name.
		Description: The name of these references change sometimes with a new kernel version or a new driver. The names used in the quickstarts where used in earlier kernel versions.
		Solution: Ignore the wrong names used in the quickstart. The correct ones are used in the BSP.

	Issue: The quickstart for the phyCORE-i.MX27 platform uses the NAND 64MiB 3,3V 8-bit to define partitions for the NAND flash memory which is wrong. It must be mxc_nand instead.
		Description: The name of this reference was changed from Kernel 2.6.27 to 2.6.28. As the phyCORE-i.MX27 platform is still at kernel 2.6.27 it also must continue using the mxc_nand name.
		Solution: Ignore the wrong name used in the quickstart. The correct one is used in the BSP for the phyCORE-i.MX27 platform.

	Refer BSP's protocols/known-issues.txt.

Read also ptxdist's FAQ