FAT has to convert between Linux filenames ('iocharset' encoding,
should be UTF-8 today) and native filenames (UTF-16 for long names,
'codepage' encoding for short names). And it has to do case
folding in multiple encodings. Unfortunately Linux doesn't
implement case-folding for UTF-8, resulting in inconsistent name
lookup behaviour as shown in bug #833238.
The 'utf8' option makes FAT assume the Linux filename encoding is
UTF-8, regardless of the 'iocharset' encoding. Enabling this and
setting iocharset=ascii mitigates the problems by enabling case-
folding for the ASCII subset.
Make that the default by enabling FAT_DEFAULT_UTF8 and setting
FAT_DEFAULT_IOCHARSET to "ascii".
Various free and proprietary AV products use this feature and users
apparently want it. But punting access checks to userland seems like
an easy way to deadlock the system, and there will be nothing we can
do about that. So warn and taint the kernel if this feature is
actually used.
DRM_TEGRA_STAGING must currently be enabled in the kernel and libdrm
must be built with --enable-tegra-experimental-api. Our libdrm package
already does the latter (at least on armhf), so enable the former as
well.
The current cross-compiler packages don't set the Multi-Arch field, so
specify that the cross-compiler package must be native, rather than any
architecture.
flex doesn't support multi-arch, and this would require splitting it
(#611230, #761449). Force use of the native package for now.
openssl doesn't support multi-arch but probably easily could (#827028).
Force use of the native package for now.
We need the native libssl-dev while building the kernel itself and the
host libssl-dev while building tools for linux-kbuild.
Document the state of cross-building in README.source.
Enable some options used by the Jetson TX1 board. MAX77620 is used
as system PMIC and PCA9539 as I2C GPIO bus expander.
Set I2C=y since this is required by MFD_MAX77620.
CONFIG_GPIO_MAX77620 and CONFIG_GPIO_MAX77620 are not upstream yet
but will be. I'm adding the options now to make the commit cover
everything needed.
This is patched on a patch submitted upstream by Laxman Dewangan.
BLK_DEV_FD has *never* been enabled on any of these architectures!
The old arm/footbridge configuration did enable it and this suggestion
seems to be have been thoughtlessly copied over to these other
architectures.
Please enable the following options in the armmp kernel configuration,
which enables support for Exynos4, tested on Odroid-U3.
It detects all four CPUs, 2GB of ram, ethernet, and supports USB on
both 4.5.x and 4.6.x. It also supports microSD, and 4.6.x worked fine,
but 4.5.x had some outstanding issues that prevented it from working
correctly. I did not test video or audio output, though modules for
video output did appear to load.
[ Roger Shimizu: modified the comment ]
Most symbols that depend on PM_DEVFREQ - such as the newly enabled
ARM_TEGRA_DEVFREQ - do not select it. Currently it is selected by
SCSI_UFSHCD, but we should not depend on that.
Ben Hutchings
Nicolas LE CAM
Martin Michlmayr
Bastian Blank
Aurelien Jarno
Roger Shimizu
Vagrant Cascadian