We use the default compiler provided by (cross-)build-essential for
userland, so the compiler build-dependencies are not needed when
the pkg.linux.nokernel profile is used.
The hppa64 packages were listed twice with profile restrictions of
<!stage1 !cross> and <!stage1 cross>, which is equivalent to listing
them once with <!stage1>.
- Various config symbols were removed, renamed or split
- HOTPLUG_PCI_SHPC is now boolean, so set it to built-in
- The stack protector config symbols were changed to two booleans
with different names
- Various ancient SCSI drivers were removed
- BT_HCIBTUART and INFINIBAND_CXGB3_DEBUG were removed
- OMAP_DM_TIMER is now an automatic symbol
- Marvell NAND driver was rewritten, so we enable MTD_NAND_MARVELL
instead of MTD_NAND_PXA3xx
- Various netfilter symbols are now boolean instead of tristate
- Drop patches already in 4.16
- Overwrite changes on master to debian/installer, which were also
applied on sid and then changed
- [x86] Fix up dell_smbios configuration; now it's a single driver
selected by DELL_SMBIOS, with DELL_SMBIOS_{SMM,WMI} being boolean
options
- Clean up configuration with kconfigeditor2
FRAMEBUFFER_CONSOLE is enabled in almost all configurations. So make
this the top level default, and disable it in the few exceptional
configurations (armel/marvell, mips*/octeon, s390x).
- [alpha] fbdev: Re-enable FRAMEBUFFER_CONSOLE as built-in
- [armel] fbdev: Explicitly disable FRAMEBUFFER_CONSOLE, as it can no longer
be a module
- [arm64] Re-enable MMC_QCOM_DML
- Change RC_CORE back to being a module
- power/supply: Enable BATTERY_BQ27XXX and BATTERY_BQ27XXX_HDQ as modules,
replacing W1_SLAVE_BQ27000
Clean up with kconfigeditor2 and delete obsolete symbols.
The config option LOCKUP_DETECTOR was split upstream in
05a4a9527931 ("kernel/watchdog: split up config options")
The old setting LOCKUP_DETECTOR=y is equivalent to enabling the soft and
hard detector now.
Currently we don't explicitly set CONFIG_FB for arm64, and the only
reason it's enabled as a module is that the DRM drivers (which are
built as modules) select it. We *do* explicitly set CONFIG_FB=y on
almost all other architectures and flavours.
Simplify this by setting CONFIG_FB=y at the top level and overriding
where needed (not arm64).
- Various ancient SCSI drivers were removed; delete config for them
- r8723au was replaced by rtl8xxxu; enable the latter instead and for
all architectures
- netfilter config symbols were renamed; enable the new ones
- Various other config symbols are obsolete; delete them
- Various other config symbols moved to different Kconfig files
-----BEGIN PGP SIGNATURE-----
iQIcBAABCgAGBQJX4HvgAAoJEOe/yOyVhhEJq9cP/j1XO1dNpOXxq0JZod66K1sl
JIC4LPZ3i+kiAD0amMZiAexAuCpqCDjinjVr/pAhEoAa79983tFoY9yWjDCAW+9H
0j7Torb5wQ76BlyXCjSoaztcQmzQ1YiCvjIzk4hCJCcvqdTuA1MMr7+AbXAgi3xE
Es/G7ai+7SK5suEYgsbliM2ndFFMtIDqgpvDVDFNBDt61m2RXKxw7SQwyItIx+Hn
n7Aq/P+LP7BjMSP6nW6EafF/RidbAwq4x+FKqzGyZhVQV7c3YFbh0EA7lVcTDhC7
A1ZbdeUjiFhUKchRPa56qf+eAI8sBEeU3Ga1mhpkxL8RkFKwvWmmB2J0tBE7KHgw
WCy+8nPxnLAq3eVIkOcB3MuvNdM9DvvtQ7X5NjXnBIfq06OX4y+C+udMpafmegTG
5YB3FVppFQNGZcOxeF9hCQspHGvBsTGRYoK3hxzx4AY94E1cakl08oZte4dHYALz
GvP/tjbLH5i/g9djVNGtfZCHKMZbDq2QhD60GNwFoN/ssX4Q/L3q4N+eyJD9KoQM
Bu44v1ZY7M13F4t5JUomjU2e5mze3opxEB2C7vIoyJfaUvtAWX/mn8SysDGdT0OJ
zd8ow6IntzcL+mqxrarOPMenSt2yqoQ6WdkYkpF5aCTj2GJyAkU7dUWfWdKWtLM7
yjuIvqRAcVzMU9XuU8uf
=s0s4
-----END PGP SIGNATURE-----
Merge tag 'debian/4.7.4-2'
- Drop ABI references and ABI maintenance patches
- Fix Kconfig symbols for omapdss sub-drivers, which were renamed for 4.8
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 it by default
- Disable it for armel/marvell since signature verification is not enabled.
- Disable it for mips and mipsel so linux-signed can be uploaded without
waiting for them to build
- Disable it for all architectures not in the main archive, as linux-signed
won't support them (at least, not initially).
We don't need a variable to control signing of the image, because
we should do that for all flavours that have CONFIG_EFI_STUB=y.
Use kconfigeditor2/process.py to put all definitions in Kconfig order
with proper headings.
Delete all definitions of unknown config symbols, which I verified
have been removed (or made automatic) upstream and not renamed.
svn path=/dists/sid/linux/; revision=22701