GitHub-Mirror/build
2
0
Fork 0
mirror of https://github.com/Fishwaldo/build.git synced 2025-03-17 04:11:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
build/config/kernel/linux-mvebu-current.config

7238 lines
170 KiB
Text
Raw Permalink Normal View History

More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Automatically generated file; DO NOT EDIT.
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
# Linux/arm 5.10.12 Kernel Configuration
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
Adding upstream patches and update kernel configs for several kernels
2020-12-06 17:17:49 +01:00
CONFIG_CC_VERSION_TEXT="arm-linux-gnueabihf-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0"
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CC_IS_GCC=y
Adding upstream patches and update kernel configs for several kernels
2020-12-06 17:17:49 +01:00
CONFIG_GCC_VERSION=80300
CONFIG_LD_VERSION=232000000
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CLANG_VERSION=0
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_LLD_VERSION=0
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CC_CAN_LINK=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_CC_CAN_LINK_STATIC=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CC_HAS_ASM_GOTO=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CC_HAS_ASM_INLINE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_IRQ_WORK=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_BUILDTIME_TABLE_SORT=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LOCALVERSION_AUTO is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_BUILD_SALT=""
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
CONFIG_KERNEL_GZIP=y
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_DEFAULT_INIT=""
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_WATCH_QUEUE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_USELIB=y
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_AUDIT=y
Switch several kernels to Thumb2 mode
2016-11-20 21:22:45 +03:00
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_AUDITSYSCALL=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_GENERIC_IRQ_SHOW_LEVEL=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK=y
[ general ] update kernel configs due to upstream changes
2019-04-17 11:41:23 +02:00
CONFIG_GENERIC_IRQ_MIGRATION=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_CHIP=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_GENERIC_IRQ_IPI=y
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HANDLE_DOMAIN_IRQ=y
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_GENERIC_IRQ_DEBUGFS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of IRQ subsystem
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_GENERIC_IRQ_MULTI_HANDLER=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_HAS_TICK_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_HZ_PERIODIC=y
# CONFIG_NO_HZ_IDLE is not set
# CONFIG_NO_HZ_FULL is not set
Consolidate timer frequency settings accross all kernels ...skipping default 3.x kernels
2018-07-16 16:41:45 +02:00
CONFIG_NO_HZ=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HIGH_RES_TIMERS=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Timers subsystem
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_IRQ_TIME_ACCOUNTING is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
CONFIG_SCHED_THERMAL_PRESSURE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_BSD_PROCESS_ACCT is not set
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_PSI is not set
# end of CPU/Task time and stats accounting
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CPU_ISOLATION=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_RCU_EXPERT=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SRCU=y
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_TREE_SRCU=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_TASKS_RCU_GENERIC=y
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_TASKS_RCU=y
CONFIG_TASKS_RUDE_RCU=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_TASKS_TRACE_RCU=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_RCU_STALL_COMMON=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_RCU_NEED_SEGCBLIST=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_RCU_FANOUT=32
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_NOCB_CPU is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_TASKS_TRACE_RCU_READ_MB is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of RCU Subsystem
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BUILD_BIN2C=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_IKHEADERS=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_LOG_BUF_SHIFT=16
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_GENERIC_SCHED_CLOCK=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Scheduler features
#
# CONFIG_UCLAMP_TASK is not set
# end of Scheduler features
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MEMCG_KMEM=y
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_BLK_CGROUP=y
CONFIG_CGROUP_WRITEBACK=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_RT_GROUP_SCHED is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_CGROUP_PIDS=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_CGROUP_RDMA=y
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_CGROUP_FREEZER=y
CONFIG_CPUSETS=y
Update mvebu-next config
2017-06-12 13:02:33 +03:00
# CONFIG_PROC_PID_CPUSET is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_CGROUP_PERF=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_CGROUP_BPF is not set
Enable minimal kernel debug info - Enable KGDB support - Enable earlycon and earlyprintk support
2017-12-30 16:50:10 +08:00
# CONFIG_CGROUP_DEBUG is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_SOCK_CGROUP_DATA=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
CONFIG_USER_NS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_PID_NS=y
CONFIG_NET_NS=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_CHECKPOINT_RESTORE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_RELAY=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_RD_GZIP=y
CONFIG_RD_BZIP2=y
CONFIG_RD_LZMA=y
CONFIG_RD_XZ=y
CONFIG_RD_LZO=y
CONFIG_RD_LZ4=y
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
CONFIG_RD_ZSTD=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BOOT_CONFIG is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_LD_ORPHAN_WARN=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SYSCTL=y
CONFIG_HAVE_UID16=y
CONFIG_BPF=y
Update mvebu-next config
2017-06-12 13:02:33 +03:00
# CONFIG_EXPERT is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_UID16=y
CONFIG_MULTIUSER=y
CONFIG_SYSFS_SYSCALL=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_FHANDLE=y
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_POSIX_TIMERS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_PRINTK=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_PRINTK_NMI=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_FUTEX_PI=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_AIO=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_IO_URING=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ADVISE_SYSCALLS=y
CONFIG_MEMBARRIER=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BPF_SYSCALL=y
# CONFIG_BPF_JIT_ALWAYS_ON is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_BPF_PRELOAD is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_USERFAULTFD is not set
CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y
CONFIG_RSEQ=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y
#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
Enable minimal kernel debug info - Enable KGDB support - Enable earlycon and earlyprintk support
2017-12-30 16:50:10 +08:00
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Kernel Performance Events And Counters
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_VM_EVENT_COUNTERS=y
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_SLAB_MERGE_DEFAULT=y
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_SLAB_FREELIST_RANDOM=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_SLAB_FREELIST_HARDENED=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_SHUFFLE_PAGE_ALLOCATOR is not set
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_SLUB_CPU_PARTIAL=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SYSTEM_DATA_VERIFICATION=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_PROFILING is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of General setup
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARM=y
CONFIG_ARM_HAS_SG_CHAIN=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_HAVE_PROC_CPU=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_ARM_PATCH_PHYS_VIRT=y
CONFIG_GENERIC_BUG=y
CONFIG_PGTABLE_LEVELS=2
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# System Type
#
CONFIG_MMU=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARCH_MMAP_RND_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_BITS_MAX=16
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ARCH_MULTIPLATFORM=y
# CONFIG_ARCH_EBSA110 is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_FOOTBRIDGE is not set
# CONFIG_ARCH_IOP32X is not set
# CONFIG_ARCH_IXP4XX is not set
# CONFIG_ARCH_DOVE is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_RPC is not set
# CONFIG_ARCH_SA1100 is not set
# CONFIG_ARCH_S3C24XX is not set
# CONFIG_ARCH_OMAP1 is not set
#
# Multiple platform selection
#
#
# CPU Core family selection
#
# CONFIG_ARCH_MULTI_V6 is not set
CONFIG_ARCH_MULTI_V7=y
CONFIG_ARCH_MULTI_V6_V7=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Multiple platform selection
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_VIRT is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_ARCH_ACTIONS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_ALPINE is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_ARCH_ARTPEC is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ARCH_ASPEED is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_AT91 is not set
# CONFIG_ARCH_BCM is not set
# CONFIG_ARCH_BERLIN is not set
# CONFIG_ARCH_DIGICOLOR is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ARCH_EXYNOS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_HIGHBANK is not set
# CONFIG_ARCH_HISI is not set
# CONFIG_ARCH_MXC is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ARCH_KEYSTONE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_MEDIATEK is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ARCH_MESON is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ARCH_MILBEAUT is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ARCH_MMP is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_ARCH_MSTARV7 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARCH_MVEBU=y
CONFIG_MACH_MVEBU_ANY=y
CONFIG_MACH_MVEBU_V7=y
CONFIG_MACH_ARMADA_370=y
CONFIG_MACH_ARMADA_375=y
CONFIG_MACH_ARMADA_38X=y
CONFIG_MACH_ARMADA_39X=y
CONFIG_MACH_ARMADA_XP=y
CONFIG_MACH_DOVE=y
# CONFIG_ARCH_NPCM is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# TI OMAP/AM/DM/DRA Family
#
# CONFIG_ARCH_OMAP3 is not set
# CONFIG_ARCH_OMAP4 is not set
# CONFIG_SOC_OMAP5 is not set
# CONFIG_SOC_AM33XX is not set
# CONFIG_SOC_AM43XX is not set
# CONFIG_SOC_DRA7XX is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of TI OMAP/AM/DM/DRA Family
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ARCH_SIRF is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_QCOM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ARCH_RDA is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ARCH_REALTEK is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_ARCH_REALVIEW is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_ROCKCHIP is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ARCH_S5PV210 is not set
# CONFIG_ARCH_RENESAS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_SOCFPGA is not set
# CONFIG_PLAT_SPEAR is not set
# CONFIG_ARCH_STI is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ARCH_STM32 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_SUNXI is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_ARCH_TANGO is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCH_TEGRA is not set
# CONFIG_ARCH_UNIPHIER is not set
# CONFIG_ARCH_U8500 is not set
# CONFIG_ARCH_VEXPRESS is not set
# CONFIG_ARCH_WM8850 is not set
# CONFIG_ARCH_ZX is not set
# CONFIG_ARCH_ZYNQ is not set
CONFIG_PLAT_ORION=y
#
# Processor Type
#
CONFIG_CPU_PJ4=y
CONFIG_CPU_PJ4B=y
CONFIG_CPU_V7=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_CPU_THUMB_CAPABLE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CPU_32v6K=y
CONFIG_CPU_32v7=y
CONFIG_CPU_ABRT_EV7=y
CONFIG_CPU_PABRT_V7=y
CONFIG_CPU_CACHE_V7=y
CONFIG_CPU_CACHE_VIPT=y
CONFIG_CPU_COPY_V6=y
CONFIG_CPU_TLB_V7=y
CONFIG_CPU_HAS_ASID=y
CONFIG_CPU_CP15=y
CONFIG_CPU_CP15_MMU=y
#
# Processor Features
#
# CONFIG_ARM_LPAE is not set
CONFIG_ARM_THUMB=y
CONFIG_ARM_THUMBEE=y
CONFIG_ARM_VIRT_EXT=y
CONFIG_SWP_EMULATE=y
# CONFIG_CPU_BIG_ENDIAN is not set
# CONFIG_CPU_ICACHE_DISABLE is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_CPU_ICACHE_MISMATCH_WORKAROUND is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CPU_BPREDICT_DISABLE is not set
[ general ] adjust a few kernel configs
2019-01-22 08:50:41 +01:00
CONFIG_CPU_SPECTRE=y
CONFIG_HARDEN_BRANCH_PREDICTOR=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_KUSER_HELPERS=y
# CONFIG_VDSO is not set
CONFIG_OUTER_CACHE=y
CONFIG_OUTER_CACHE_SYNC=y
CONFIG_CACHE_FEROCEON_L2=y
# CONFIG_CACHE_FEROCEON_L2_WRITETHROUGH is not set
CONFIG_MIGHT_HAVE_CACHE_L2X0=y
CONFIG_CACHE_L2X0=y
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_CACHE_L2X0_PMU is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_PL310_ERRATA_588369 is not set
# CONFIG_PL310_ERRATA_727915 is not set
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_PL310_ERRATA_753970=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_PL310_ERRATA_769419 is not set
CONFIG_CACHE_TAUROS2=y
CONFIG_ARM_L1_CACHE_SHIFT_6=y
CONFIG_ARM_L1_CACHE_SHIFT=6
CONFIG_ARM_DMA_MEM_BUFFERABLE=y
CONFIG_ARM_HEAVY_MB=y
CONFIG_ARCH_SUPPORTS_BIG_ENDIAN=y
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_DEBUG_ALIGN_RODATA=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_IWMMXT=y
CONFIG_PJ4B_ERRATA_4742=y
# CONFIG_ARM_ERRATA_430973 is not set
CONFIG_ARM_ERRATA_643719=y
CONFIG_ARM_ERRATA_720789=y
# CONFIG_ARM_ERRATA_754322 is not set
# CONFIG_ARM_ERRATA_754327 is not set
# CONFIG_ARM_ERRATA_764369 is not set
# CONFIG_ARM_ERRATA_775420 is not set
# CONFIG_ARM_ERRATA_798181 is not set
# CONFIG_ARM_ERRATA_773022 is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
# CONFIG_ARM_ERRATA_818325_852422 is not set
# CONFIG_ARM_ERRATA_821420 is not set
# CONFIG_ARM_ERRATA_825619 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ARM_ERRATA_857271 is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
# CONFIG_ARM_ERRATA_852421 is not set
# CONFIG_ARM_ERRATA_852423 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ARM_ERRATA_857272 is not set
# end of System Type
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Bus support
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ARM_ERRATA_814220 is not set
# end of Bus support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Kernel Features
#
CONFIG_HAVE_SMP=y
CONFIG_SMP=y
CONFIG_SMP_ON_UP=y
CONFIG_ARM_CPU_TOPOLOGY=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_SCHED_MC=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SCHED_SMT is not set
CONFIG_HAVE_ARM_SCU=y
# CONFIG_HAVE_ARM_ARCH_TIMER is not set
CONFIG_HAVE_ARM_TWD=y
# CONFIG_MCPM is not set
# CONFIG_BIG_LITTLE is not set
CONFIG_VMSPLIT_3G=y
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_VMSPLIT_3G_OPT is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_1G is not set
CONFIG_PAGE_OFFSET=0xC0000000
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NR_CPUS=8
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HOTPLUG_CPU=y
# CONFIG_ARM_PSCI is not set
CONFIG_ARCH_NR_GPIO=0
CONFIG_HZ_FIXED=0
Consolidate timer frequency settings accross all kernels ...skipping default 3.x kernels
2018-07-16 16:41:45 +02:00
# CONFIG_HZ_100 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HZ_200 is not set
Use CONFIG_HZ=250 where applicable Closes #1142
2018-10-27 10:38:35 +02:00
CONFIG_HZ_250=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HZ_300 is not set
# CONFIG_HZ_500 is not set
Use CONFIG_HZ=250 where applicable Closes #1142
2018-10-27 10:38:35 +02:00
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SCHED_HRTICK=y
Switch several kernels to Thumb2 mode
2016-11-20 21:22:45 +03:00
CONFIG_THUMB2_KERNEL=y
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_ARM_PATCH_IDIV=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_AEABI=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HAVE_ARCH_PFN_VALID=y
CONFIG_HIGHMEM=y
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_HIGHPTE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CPU_SW_DOMAIN_PAN=y
CONFIG_HW_PERF_EVENTS=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
Hopefully fix module relocation issues in several kernels
2017-10-16 13:33:10 +03:00
CONFIG_ARM_MODULE_PLTS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_FORCE_MAX_ZONEORDER=11
CONFIG_ALIGNMENT_TRAP=y
# CONFIG_UACCESS_WITH_MEMCPY is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_PARAVIRT is not set
# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_XEN is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Kernel Features
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Boot options
#
CONFIG_USE_OF=y
CONFIG_ATAGS=y
# CONFIG_DEPRECATED_PARAM_STRUCT is not set
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
Update mvebu-next config
2017-06-12 13:02:33 +03:00
# CONFIG_ARM_APPENDED_DTB is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CMDLINE=""
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_AUTO_ZRELADDR=y
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_EFI is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Boot options
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# CPU Power Management
#
#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_CPU_FREQ_GOV_ATTR_SET=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CPU_FREQ_GOV_COMMON=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CPU_FREQ_STAT=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
# CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CPU_FREQ_GOV_POWERSAVE=y
CONFIG_CPU_FREQ_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_ONDEMAND=y
CONFIG_CPU_FREQ_GOV_CONSERVATIVE=y
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_CPU_FREQ_GOV_SCHEDUTIL=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# CPU frequency scaling drivers
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CPUFREQ_DT=m
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_CPUFREQ_DT_PLATDEV=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARM_ARMADA_37XX_CPUFREQ=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_ARM_ARMADA_8K_CPUFREQ=m
# end of CPU Frequency scaling
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# CPU Idle
#
CONFIG_CPU_IDLE=y
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_CPU_IDLE_MULTIPLE_DRIVERS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CPU_IDLE_GOV_LADDER=y
CONFIG_CPU_IDLE_GOV_MENU=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_CPU_IDLE_GOV_TEO is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_DT_IDLE_STATES=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# ARM CPU Idle Drivers
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ARM_CPUIDLE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ARM_MVEBU_V7_CPUIDLE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of ARM CPU Idle Drivers
# end of CPU Idle
# end of CPU Power Management
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Floating point emulation
#
#
# At least one emulation must be selected
#
CONFIG_VFP=y
CONFIG_VFPv3=y
CONFIG_NEON=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_KERNEL_MODE_NEON=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Floating point emulation
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Power management options
#
CONFIG_SUSPEND=y
CONFIG_SUSPEND_FREEZER=y
# CONFIG_HIBERNATION is not set
CONFIG_PM_SLEEP=y
CONFIG_PM_SLEEP_SMP=y
# CONFIG_PM_AUTOSLEEP is not set
# CONFIG_PM_WAKELOCKS is not set
CONFIG_PM=y
# CONFIG_PM_DEBUG is not set
# CONFIG_APM_EMULATION is not set
CONFIG_PM_CLK=y
CONFIG_PM_GENERIC_DOMAINS=y
# CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set
CONFIG_PM_GENERIC_DOMAINS_SLEEP=y
CONFIG_PM_GENERIC_DOMAINS_OF=y
CONFIG_CPU_PM=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ENERGY_MODEL is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARM_CPU_SUSPEND=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Power management options
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Firmware Drivers
#
# CONFIG_FW_CFG_SYSFS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_TRUSTED_FOUNDATIONS is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_GOOGLE_FIRMWARE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_HAVE_ARM_SMCCC=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Tegra firmware driver
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Tegra firmware driver
# end of Firmware Drivers
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARM_CRYPTO=y
CONFIG_CRYPTO_SHA1_ARM=m
CONFIG_CRYPTO_SHA1_ARM_NEON=m
CONFIG_CRYPTO_SHA1_ARM_CE=m
CONFIG_CRYPTO_SHA2_ARM_CE=m
CONFIG_CRYPTO_SHA256_ARM=m
CONFIG_CRYPTO_SHA512_ARM=m
CONFIG_CRYPTO_AES_ARM=m
CONFIG_CRYPTO_AES_ARM_BS=m
CONFIG_CRYPTO_AES_ARM_CE=m
CONFIG_CRYPTO_GHASH_ARM_CE=m
CONFIG_CRYPTO_CRCT10DIF_ARM_CE=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_CRC32_ARM_CE=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CRYPTO_CHACHA20_NEON=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_CRYPTO_POLY1305_ARM=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_NHPOLY1305_NEON=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_CRYPTO_CURVE25519_NEON=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
CONFIG_AS_VFP_VMRS_FPINST=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# General architecture-dependent options
#
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_SET_FS=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y
CONFIG_ARCH_USE_BUILTIN_BSWAP=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_NMI=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_HAVE_DMA_CONTIGUOUS=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_GENERIC_IDLE_POLL_SETUP=y
CONFIG_ARCH_HAS_FORTIFY_SOURCE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_ARCH_HAS_KEEPINITRD=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARCH_HAS_SET_MEMORY=y
CONFIG_HAVE_ARCH_THREAD_STRUCT_WHITELIST=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_ARCH_32BIT_OFF_T=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_HAVE_RSEQ=y
CONFIG_HAVE_HW_BREAKPOINT=y
CONFIG_HAVE_PERF_REGS=y
CONFIG_HAVE_PERF_USER_STACK_DUMP=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y
CONFIG_ARCH_WANT_IPC_PARSE_VERSION=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_HAVE_ARCH_SECCOMP=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_HAVE_ARCH_SECCOMP_FILTER=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_SECCOMP=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SECCOMP_FILTER=y
CONFIG_HAVE_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR=y
CONFIG_STACKPROTECTOR_STRONG=y
CONFIG_HAVE_CONTEXT_TRACKING=y
CONFIG_HAVE_VIRT_CPU_ACCOUNTING_GEN=y
CONFIG_HAVE_IRQ_TIME_ACCOUNTING=y
CONFIG_HAVE_MOD_ARCH_SPECIFIC=y
CONFIG_MODULES_USE_ELF_REL=y
CONFIG_ARCH_HAS_ELF_RANDOMIZE=y
CONFIG_HAVE_ARCH_MMAP_RND_BITS=y
CONFIG_HAVE_EXIT_THREAD=y
CONFIG_ARCH_MMAP_RND_BITS=8
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CLONE_BACKWARDS=y
CONFIG_OLD_SIGSUSPEND3=y
CONFIG_OLD_SIGACTION=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_COMPAT_32BIT_TIME=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARCH_OPTIONAL_KERNEL_RWX=y
CONFIG_ARCH_OPTIONAL_KERNEL_RWX_DEFAULT=y
CONFIG_ARCH_HAS_STRICT_KERNEL_RWX=y
CONFIG_STRICT_KERNEL_RWX=y
CONFIG_ARCH_HAS_STRICT_MODULE_RWX=y
CONFIG_STRICT_MODULE_RWX=y
CONFIG_ARCH_HAS_PHYS_TO_DMA=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_LOCK_EVENT_COUNTS is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_ARCH_WANT_LD_ORPHAN_WARN=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# GCOV-based kernel profiling
#
# CONFIG_GCOV_KERNEL is not set
CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of GCOV-based kernel profiling
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_HAVE_GCC_PLUGINS=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of General architecture-dependent options
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_RT_MUTEXES=y
CONFIG_BASE_SMALL=0
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MODULE_SIG_FORMAT=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set
CONFIG_MODULE_SIG_ALL=y
CONFIG_MODULE_SIG_SHA1=y
# CONFIG_MODULE_SIG_SHA224 is not set
# CONFIG_MODULE_SIG_SHA256 is not set
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not set
CONFIG_MODULE_SIG_HASH="sha1"
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_MODULE_COMPRESS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MODULE_ALLOW_MISSING_NAMESPACE_IMPORTS is not set
# CONFIG_UNUSED_SYMBOLS is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_TRIM_UNUSED_KSYMS is not set
CONFIG_MODULES_TREE_LOOKUP=y
CONFIG_BLOCK=y
CONFIG_BLK_SCSI_REQUEST=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_BLK_CGROUP_RWSTAT=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_BLK_DEV_BSG=y
CONFIG_BLK_DEV_BSGLIB=y
CONFIG_BLK_DEV_INTEGRITY=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_BLK_DEV_INTEGRITY_T10=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_BLK_DEV_ZONED=y
CONFIG_BLK_DEV_THROTTLING=y
# CONFIG_BLK_DEV_THROTTLING_LOW is not set
# CONFIG_BLK_CMDLINE_PARSER is not set
CONFIG_BLK_WBT=y
# CONFIG_BLK_CGROUP_IOLATENCY is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_BLK_CGROUP_IOCOST is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_BLK_WBT_MQ=y
# CONFIG_BLK_DEBUG_FS is not set
# CONFIG_BLK_SED_OPAL is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BLK_INLINE_ENCRYPTION is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_EFI_PARTITION=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Partition Types
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_BLK_MQ_PCI=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BLK_MQ_VIRTIO=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_BLK_PM=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# IO Schedulers
#
CONFIG_MQ_IOSCHED_DEADLINE=y
CONFIG_MQ_IOSCHED_KYBER=y
CONFIG_IOSCHED_BFQ=y
CONFIG_BFQ_GROUP_IOSCHED=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_BFQ_CGROUP_DEBUG is not set
# end of IO Schedulers
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_PADATA=y
CONFIG_ASN1=y
CONFIG_INLINE_SPIN_UNLOCK_IRQ=y
CONFIG_INLINE_READ_UNLOCK=y
CONFIG_INLINE_READ_UNLOCK_IRQ=y
CONFIG_INLINE_WRITE_UNLOCK=y
CONFIG_INLINE_WRITE_UNLOCK_IRQ=y
CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y
CONFIG_MUTEX_SPIN_ON_OWNER=y
CONFIG_RWSEM_SPIN_ON_OWNER=y
CONFIG_LOCK_SPIN_ON_OWNER=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_ARCH_HAS_NON_OVERLAPPING_ADDRESS_SPACE=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_FREEZER=y
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_ELF_FDPIC is not set
CONFIG_ELFCORE=y
CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS=y
CONFIG_BINFMT_SCRIPT=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_ARCH_HAS_BINFMT_FLAT=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_BINFMT_FLAT=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_BINFMT_FLAT_ARGVP_ENVP_ON_STACK=y
# CONFIG_BINFMT_FLAT_OLD is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_BINFMT_ZFLAT=y
CONFIG_BINFMT_SHARED_FLAT=y
CONFIG_BINFMT_MISC=m
CONFIG_COREDUMP=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Executable file formats
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Memory Management options
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_ARCH_KEEP_MEMBLOCK=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MEMORY_ISOLATION=y
CONFIG_SPLIT_PTLOCK_CPUS=4
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MEMORY_BALLOON=y
CONFIG_BALLOON_COMPACTION=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_COMPACTION=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_PAGE_REPORTING=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MIGRATION=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CONTIG_ALLOC=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_BOUNCE=y
CONFIG_KSM=y
CONFIG_DEFAULT_MMAP_MIN_ADDR=4096
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CLEANCACHE=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_FRONTSWAP=y
CONFIG_CMA=y
# CONFIG_CMA_DEBUG is not set
# CONFIG_CMA_DEBUGFS is not set
CONFIG_CMA_AREAS=7
CONFIG_ZSWAP=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_DEFLATE is not set
Enable zswap with zstd/z3fold where applicable
2020-12-29 16:29:49 +01:00
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZO is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_842 is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4 is not set
# CONFIG_ZSWAP_COMPRESSOR_DEFAULT_LZ4HC is not set
Enable zswap with zstd/z3fold where applicable
2020-12-29 16:29:49 +01:00
CONFIG_ZSWAP_COMPRESSOR_DEFAULT_ZSTD=y
CONFIG_ZSWAP_COMPRESSOR_DEFAULT="zstd"
# CONFIG_ZSWAP_ZPOOL_DEFAULT_ZBUD is not set
CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ZSWAP_ZPOOL_DEFAULT_ZSMALLOC is not set
Enable zswap with zstd/z3fold where applicable
2020-12-29 16:29:49 +01:00
CONFIG_ZSWAP_ZPOOL_DEFAULT="z3fold"
CONFIG_ZSWAP_DEFAULT_ON=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ZPOOL=y
CONFIG_ZBUD=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_Z3FOLD=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ZSMALLOC=m
# CONFIG_ZSMALLOC_STAT is not set
CONFIG_GENERIC_EARLY_IOREMAP=y
CONFIG_IDLE_PAGE_TRACKING=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_FRAME_VECTOR=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_PERCPU_STATS is not set
# CONFIG_GUP_BENCHMARK is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Memory Management options
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NET=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_INGRESS=y
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_NET_EGRESS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_REDIRECT=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_SKB_EXTENSIONS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Networking options
#
CONFIG_PACKET=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_PACKET_DIAG=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_UNIX=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_UNIX_SCM=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_UNIX_DIAG=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_TLS=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_TLS_DEVICE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_TLS_TOE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_XFRM=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_XFRM_OFFLOAD=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_XFRM_ALGO=y
CONFIG_XFRM_USER=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_XFRM_INTERFACE=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_XFRM_SUB_POLICY=y
CONFIG_XFRM_MIGRATE=y
CONFIG_XFRM_STATISTICS=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_XFRM_AH=m
CONFIG_XFRM_ESP=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_XFRM_IPCOMP=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_KEY=m
CONFIG_NET_KEY_MIGRATE=y
CONFIG_XDP_SOCKETS=y
CONFIG_XDP_SOCKETS_DIAG=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_INET=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_IP_FIB_TRIE_STATS=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
CONFIG_IP_ROUTE_CLASSID=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_PNP_RARP=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_IPIP=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_IPGRE_DEMUX=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_IP_TUNNEL=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_IP_MROUTE_COMMON=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_MROUTE=y
CONFIG_IP_MROUTE_MULTIPLE_TABLES=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_SYN_COOKIES=y
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_NET_IPVTI=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_NET_UDP_TUNNEL=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_NET_FOU=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_NET_FOU_IP_TUNNELS is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_INET_ESP_OFFLOAD=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_INET_ESPINTCP is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_INET_TUNNEL=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_INET_UDP_DIAG=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_INET_RAW_DIAG=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_INET_DIAG_DESTROY=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_TCP_CONG_ADVANCED=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_TCP_CONG_BIC=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_TCP_CONG_CUBIC=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_TCP_CONG_HSTCP=m
CONFIG_TCP_CONG_HYBLA=m
CONFIG_TCP_CONG_VEGAS=m
CONFIG_TCP_CONG_NV=m
CONFIG_TCP_CONG_SCALABLE=m
CONFIG_TCP_CONG_LP=m
CONFIG_TCP_CONG_VENO=m
CONFIG_TCP_CONG_YEAH=m
CONFIG_TCP_CONG_ILLINOIS=m
CONFIG_TCP_CONG_DCTCP=m
CONFIG_TCP_CONG_CDG=m
CONFIG_TCP_CONG_BBR=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_DEFAULT_CUBIC=y
# CONFIG_DEFAULT_RENO is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_DEFAULT_TCP_CONG="cubic"
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_TCP_MD5SIG=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_IPV6=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IPV6_ROUTER_PREF=y
CONFIG_IPV6_ROUTE_INFO=y
CONFIG_IPV6_OPTIMISTIC_DAD=y
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_INET6_ESP_OFFLOAD=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_INET6_ESPINTCP is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_INET6_IPCOMP=m
CONFIG_IPV6_MIP6=m
CONFIG_IPV6_ILA=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_IPV6_VTI=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IPV6_SIT=m
CONFIG_IPV6_SIT_6RD=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_IPV6_NDISC_NODETYPE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IPV6_TUNNEL=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_IPV6_GRE=m
CONFIG_IPV6_FOU=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IPV6_MULTIPLE_TABLES=y
CONFIG_IPV6_SUBTREES=y
CONFIG_IPV6_MROUTE=y
CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
CONFIG_IPV6_PIMSM_V2=y
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_IPV6_SEG6_LWTUNNEL=y
CONFIG_IPV6_SEG6_HMAC=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_IPV6_SEG6_BPF=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_IPV6_RPL_LWTUNNEL is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NETLABEL=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MPTCP is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NETWORK_SECMARK=y
CONFIG_NET_PTP_CLASSIFY=y
CONFIG_NETWORK_PHY_TIMESTAMPING=y
CONFIG_NETFILTER=y
CONFIG_NETFILTER_ADVANCED=y
CONFIG_BRIDGE_NETFILTER=m
#
# Core Netfilter Configuration
#
CONFIG_NETFILTER_INGRESS=y
CONFIG_NETFILTER_NETLINK=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NETFILTER_FAMILY_BRIDGE=y
CONFIG_NETFILTER_FAMILY_ARP=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NETFILTER_NETLINK_ACCT=m
CONFIG_NETFILTER_NETLINK_QUEUE=m
CONFIG_NETFILTER_NETLINK_LOG=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NETFILTER_NETLINK_OSF=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NF_CONNTRACK=m
CONFIG_NF_LOG_COMMON=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_NF_LOG_NETDEV=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NETFILTER_CONNCOUNT=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NF_CONNTRACK_MARK=y
CONFIG_NF_CONNTRACK_SECMARK=y
CONFIG_NF_CONNTRACK_ZONES=y
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_EVENTS=y
CONFIG_NF_CONNTRACK_TIMEOUT=y
CONFIG_NF_CONNTRACK_TIMESTAMP=y
CONFIG_NF_CONNTRACK_LABELS=y
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_NF_CT_PROTO_DCCP=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NF_CT_PROTO_GRE=y
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_NF_CT_PROTO_SCTP=y
CONFIG_NF_CT_PROTO_UDPLITE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NF_CONNTRACK_AMANDA=m
CONFIG_NF_CONNTRACK_FTP=m
CONFIG_NF_CONNTRACK_H323=m
CONFIG_NF_CONNTRACK_IRC=m
CONFIG_NF_CONNTRACK_BROADCAST=m
CONFIG_NF_CONNTRACK_NETBIOS_NS=m
CONFIG_NF_CONNTRACK_SNMP=m
CONFIG_NF_CONNTRACK_PPTP=m
CONFIG_NF_CONNTRACK_SANE=m
CONFIG_NF_CONNTRACK_SIP=m
CONFIG_NF_CONNTRACK_TFTP=m
CONFIG_NF_CT_NETLINK=m
CONFIG_NF_CT_NETLINK_TIMEOUT=m
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_NF_CT_NETLINK_HELPER=m
CONFIG_NETFILTER_NETLINK_GLUE_CT=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NF_NAT=m
CONFIG_NF_NAT_AMANDA=m
CONFIG_NF_NAT_FTP=m
CONFIG_NF_NAT_IRC=m
CONFIG_NF_NAT_SIP=m
CONFIG_NF_NAT_TFTP=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NF_NAT_REDIRECT=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NF_NAT_MASQUERADE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NETFILTER_SYNPROXY=m
CONFIG_NF_TABLES=m
mvebu: config: Update linux-mvebu-current.config Debian Buster use nftables backend for iptables command. Added support for nftable Added PCIe support Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2020-01-02 18:17:06 +07:00
CONFIG_NF_TABLES_INET=y
CONFIG_NF_TABLES_NETDEV=y
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_NFT_NUMGEN=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFT_CT=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NFT_FLOW_OFFLOAD=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFT_COUNTER=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NFT_CONNLIMIT=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFT_LOG=m
CONFIG_NFT_LIMIT=m
CONFIG_NFT_MASQ=m
CONFIG_NFT_REDIR=m
CONFIG_NFT_NAT=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NFT_TUNNEL=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_NFT_OBJREF=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFT_QUEUE=m
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_NFT_QUOTA=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFT_REJECT=m
mvebu: config: Update linux-mvebu-current.config Debian Buster use nftables backend for iptables command. Added support for nftable Added PCIe support Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2020-01-02 18:17:06 +07:00
CONFIG_NFT_REJECT_INET=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFT_COMPAT=m
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_NFT_HASH=m
mvebu: config: Update linux-mvebu-current.config Debian Buster use nftables backend for iptables command. Added support for nftable Added PCIe support Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2020-01-02 18:17:06 +07:00
CONFIG_NFT_FIB=m
CONFIG_NFT_FIB_INET=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NFT_XFRM=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NFT_SOCKET=m
CONFIG_NFT_OSF=m
CONFIG_NFT_TPROXY=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NFT_SYNPROXY=m
mvebu: config: Update linux-mvebu-current.config Debian Buster use nftables backend for iptables command. Added support for nftable Added PCIe support Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2020-01-02 18:17:06 +07:00
CONFIG_NF_DUP_NETDEV=m
CONFIG_NFT_DUP_NETDEV=m
CONFIG_NFT_FWD_NETDEV=m
CONFIG_NFT_FIB_NETDEV=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NF_FLOW_TABLE_INET=m
CONFIG_NF_FLOW_TABLE=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NETFILTER_XTABLES=m
#
# Xtables combined modules
#
CONFIG_NETFILTER_XT_MARK=m
CONFIG_NETFILTER_XT_CONNMARK=m
CONFIG_NETFILTER_XT_SET=m
#
# Xtables targets
#
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_NETFILTER_XT_TARGET_AUDIT=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NETFILTER_XT_TARGET_CHECKSUM=m
CONFIG_NETFILTER_XT_TARGET_CLASSIFY=m
CONFIG_NETFILTER_XT_TARGET_CONNMARK=m
CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=m
CONFIG_NETFILTER_XT_TARGET_CT=m
CONFIG_NETFILTER_XT_TARGET_DSCP=m
CONFIG_NETFILTER_XT_TARGET_HL=m
CONFIG_NETFILTER_XT_TARGET_HMARK=m
CONFIG_NETFILTER_XT_TARGET_IDLETIMER=m
CONFIG_NETFILTER_XT_TARGET_LED=m
CONFIG_NETFILTER_XT_TARGET_LOG=m
CONFIG_NETFILTER_XT_TARGET_MARK=m
CONFIG_NETFILTER_XT_NAT=m
CONFIG_NETFILTER_XT_TARGET_NETMAP=m
CONFIG_NETFILTER_XT_TARGET_NFLOG=m
CONFIG_NETFILTER_XT_TARGET_NFQUEUE=m
CONFIG_NETFILTER_XT_TARGET_NOTRACK=m
CONFIG_NETFILTER_XT_TARGET_RATEEST=m
CONFIG_NETFILTER_XT_TARGET_REDIRECT=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NETFILTER_XT_TARGET_MASQUERADE=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NETFILTER_XT_TARGET_TEE=m
CONFIG_NETFILTER_XT_TARGET_TPROXY=m
CONFIG_NETFILTER_XT_TARGET_TRACE=m
CONFIG_NETFILTER_XT_TARGET_SECMARK=m
CONFIG_NETFILTER_XT_TARGET_TCPMSS=m
CONFIG_NETFILTER_XT_TARGET_TCPOPTSTRIP=m
#
# Xtables matches
#
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE=m
CONFIG_NETFILTER_XT_MATCH_BPF=m
CONFIG_NETFILTER_XT_MATCH_CGROUP=m
CONFIG_NETFILTER_XT_MATCH_CLUSTER=m
CONFIG_NETFILTER_XT_MATCH_COMMENT=m
CONFIG_NETFILTER_XT_MATCH_CONNBYTES=m
CONFIG_NETFILTER_XT_MATCH_CONNLABEL=m
CONFIG_NETFILTER_XT_MATCH_CONNLIMIT=m
CONFIG_NETFILTER_XT_MATCH_CONNMARK=m
CONFIG_NETFILTER_XT_MATCH_CONNTRACK=m
CONFIG_NETFILTER_XT_MATCH_CPU=m
CONFIG_NETFILTER_XT_MATCH_DCCP=m
CONFIG_NETFILTER_XT_MATCH_DEVGROUP=m
CONFIG_NETFILTER_XT_MATCH_DSCP=m
CONFIG_NETFILTER_XT_MATCH_ECN=m
CONFIG_NETFILTER_XT_MATCH_ESP=m
CONFIG_NETFILTER_XT_MATCH_HASHLIMIT=m
CONFIG_NETFILTER_XT_MATCH_HELPER=m
CONFIG_NETFILTER_XT_MATCH_HL=m
CONFIG_NETFILTER_XT_MATCH_IPCOMP=m
CONFIG_NETFILTER_XT_MATCH_IPRANGE=m
CONFIG_NETFILTER_XT_MATCH_IPVS=m
CONFIG_NETFILTER_XT_MATCH_L2TP=m
CONFIG_NETFILTER_XT_MATCH_LENGTH=m
CONFIG_NETFILTER_XT_MATCH_LIMIT=m
CONFIG_NETFILTER_XT_MATCH_MAC=m
CONFIG_NETFILTER_XT_MATCH_MARK=m
CONFIG_NETFILTER_XT_MATCH_MULTIPORT=m
CONFIG_NETFILTER_XT_MATCH_NFACCT=m
CONFIG_NETFILTER_XT_MATCH_OSF=m
CONFIG_NETFILTER_XT_MATCH_OWNER=m
CONFIG_NETFILTER_XT_MATCH_POLICY=m
CONFIG_NETFILTER_XT_MATCH_PHYSDEV=m
CONFIG_NETFILTER_XT_MATCH_PKTTYPE=m
CONFIG_NETFILTER_XT_MATCH_QUOTA=m
CONFIG_NETFILTER_XT_MATCH_RATEEST=m
CONFIG_NETFILTER_XT_MATCH_REALM=m
CONFIG_NETFILTER_XT_MATCH_RECENT=m
CONFIG_NETFILTER_XT_MATCH_SCTP=m
CONFIG_NETFILTER_XT_MATCH_SOCKET=m
CONFIG_NETFILTER_XT_MATCH_STATE=m
CONFIG_NETFILTER_XT_MATCH_STATISTIC=m
CONFIG_NETFILTER_XT_MATCH_STRING=m
CONFIG_NETFILTER_XT_MATCH_TCPMSS=m
CONFIG_NETFILTER_XT_MATCH_TIME=m
CONFIG_NETFILTER_XT_MATCH_U32=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Core Netfilter Configuration
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_SET=m
CONFIG_IP_SET_MAX=256
CONFIG_IP_SET_BITMAP_IP=m
CONFIG_IP_SET_BITMAP_IPMAC=m
CONFIG_IP_SET_BITMAP_PORT=m
CONFIG_IP_SET_HASH_IP=m
CONFIG_IP_SET_HASH_IPMARK=m
CONFIG_IP_SET_HASH_IPPORT=m
CONFIG_IP_SET_HASH_IPPORTIP=m
CONFIG_IP_SET_HASH_IPPORTNET=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_IP_SET_HASH_IPMAC=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_SET_HASH_MAC=m
CONFIG_IP_SET_HASH_NETPORTNET=m
CONFIG_IP_SET_HASH_NET=m
CONFIG_IP_SET_HASH_NETNET=m
CONFIG_IP_SET_HASH_NETPORT=m
CONFIG_IP_SET_HASH_NETIFACE=m
CONFIG_IP_SET_LIST_SET=m
CONFIG_IP_VS=m
CONFIG_IP_VS_IPV6=y
# CONFIG_IP_VS_DEBUG is not set
CONFIG_IP_VS_TAB_BITS=12
#
# IPVS transport protocol load balancing support
#
CONFIG_IP_VS_PROTO_TCP=y
CONFIG_IP_VS_PROTO_UDP=y
CONFIG_IP_VS_PROTO_AH_ESP=y
CONFIG_IP_VS_PROTO_ESP=y
CONFIG_IP_VS_PROTO_AH=y
CONFIG_IP_VS_PROTO_SCTP=y
#
# IPVS scheduler
#
CONFIG_IP_VS_RR=m
CONFIG_IP_VS_WRR=m
CONFIG_IP_VS_LC=m
CONFIG_IP_VS_WLC=m
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_IP_VS_FO=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_VS_OVF=m
CONFIG_IP_VS_LBLC=m
CONFIG_IP_VS_LBLCR=m
CONFIG_IP_VS_DH=m
CONFIG_IP_VS_SH=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_IP_VS_MH=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_VS_SED=m
CONFIG_IP_VS_NQ=m
#
# IPVS SH scheduler
#
CONFIG_IP_VS_SH_TAB_BITS=8
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# IPVS MH scheduler
#
CONFIG_IP_VS_MH_TAB_INDEX=12
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
#
# IPVS application helper
#
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_IP_VS_FTP=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_VS_NFCT=y
CONFIG_IP_VS_PE_SIP=m
#
# IP: Netfilter Configuration
#
CONFIG_NF_DEFRAG_IPV4=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NF_SOCKET_IPV4=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NF_TPROXY_IPV4=m
mvebu: config: Update linux-mvebu-current.config Debian Buster use nftables backend for iptables command. Added support for nftable Added PCIe support Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2020-01-02 18:17:06 +07:00
CONFIG_NF_TABLES_IPV4=y
CONFIG_NFT_REJECT_IPV4=m
CONFIG_NFT_DUP_IPV4=m
CONFIG_NFT_FIB_IPV4=m
CONFIG_NF_TABLES_ARP=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NF_FLOW_TABLE_IPV4=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NF_DUP_IPV4=m
CONFIG_NF_LOG_ARP=m
CONFIG_NF_LOG_IPV4=m
CONFIG_NF_REJECT_IPV4=m
CONFIG_NF_NAT_SNMP_BASIC=m
CONFIG_NF_NAT_PPTP=m
CONFIG_NF_NAT_H323=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_AH=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_RPFILTER=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_SYNPROXY=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_CLUSTERIP=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_TTL=m
CONFIG_IP_NF_RAW=m
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_IP_NF_SECURITY=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of IP: Netfilter Configuration
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
#
# IPv6: Netfilter Configuration
#
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_NF_SOCKET_IPV6=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NF_TPROXY_IPV6=m
mvebu: config: Update linux-mvebu-current.config Debian Buster use nftables backend for iptables command. Added support for nftable Added PCIe support Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2020-01-02 18:17:06 +07:00
CONFIG_NF_TABLES_IPV6=y
CONFIG_NFT_REJECT_IPV6=m
CONFIG_NFT_DUP_IPV6=m
CONFIG_NFT_FIB_IPV6=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NF_FLOW_TABLE_IPV6=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NF_DUP_IPV6=m
CONFIG_NF_REJECT_IPV6=m
CONFIG_NF_LOG_IPV6=m
CONFIG_IP6_NF_IPTABLES=m
CONFIG_IP6_NF_MATCH_AH=m
CONFIG_IP6_NF_MATCH_EUI64=m
CONFIG_IP6_NF_MATCH_FRAG=m
CONFIG_IP6_NF_MATCH_OPTS=m
CONFIG_IP6_NF_MATCH_HL=m
CONFIG_IP6_NF_MATCH_IPV6HEADER=m
CONFIG_IP6_NF_MATCH_MH=m
CONFIG_IP6_NF_MATCH_RPFILTER=m
CONFIG_IP6_NF_MATCH_RT=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_IP6_NF_MATCH_SRH=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP6_NF_TARGET_HL=m
CONFIG_IP6_NF_FILTER=m
CONFIG_IP6_NF_TARGET_REJECT=m
CONFIG_IP6_NF_TARGET_SYNPROXY=m
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_IP6_NF_SECURITY=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP6_NF_NAT=m
CONFIG_IP6_NF_TARGET_MASQUERADE=m
CONFIG_IP6_NF_TARGET_NPT=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of IPv6: Netfilter Configuration
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NF_DEFRAG_IPV6=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NF_TABLES_BRIDGE=m
CONFIG_NFT_BRIDGE_META=m
mvebu: config: Update linux-mvebu-current.config Debian Buster use nftables backend for iptables command. Added support for nftable Added PCIe support Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2020-01-02 18:17:06 +07:00
CONFIG_NFT_BRIDGE_REJECT=m
CONFIG_NF_LOG_BRIDGE=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NF_CONNTRACK_BRIDGE=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BRIDGE_NF_EBTABLES=m
CONFIG_BRIDGE_EBT_BROUTE=m
CONFIG_BRIDGE_EBT_T_FILTER=m
CONFIG_BRIDGE_EBT_T_NAT=m
CONFIG_BRIDGE_EBT_802_3=m
CONFIG_BRIDGE_EBT_AMONG=m
CONFIG_BRIDGE_EBT_ARP=m
CONFIG_BRIDGE_EBT_IP=m
CONFIG_BRIDGE_EBT_IP6=m
CONFIG_BRIDGE_EBT_LIMIT=m
CONFIG_BRIDGE_EBT_MARK=m
CONFIG_BRIDGE_EBT_PKTTYPE=m
CONFIG_BRIDGE_EBT_STP=m
CONFIG_BRIDGE_EBT_VLAN=m
CONFIG_BRIDGE_EBT_ARPREPLY=m
CONFIG_BRIDGE_EBT_DNAT=m
CONFIG_BRIDGE_EBT_MARK_T=m
CONFIG_BRIDGE_EBT_REDIRECT=m
CONFIG_BRIDGE_EBT_SNAT=m
CONFIG_BRIDGE_EBT_LOG=m
CONFIG_BRIDGE_EBT_NFLOG=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_BPFILTER is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_DCCP=m
CONFIG_INET_DCCP_DIAG=m
#
# DCCP CCIDs Configuration
#
# CONFIG_IP_DCCP_CCID2_DEBUG is not set
CONFIG_IP_DCCP_CCID3=y
# CONFIG_IP_DCCP_CCID3_DEBUG is not set
CONFIG_IP_DCCP_TFRC_LIB=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of DCCP CCIDs Configuration
Enable minimal kernel debug info - Enable KGDB support - Enable earlycon and earlyprintk support
2017-12-30 16:50:10 +08:00
#
# DCCP Kernel Hacking
#
# CONFIG_IP_DCCP_DEBUG is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of DCCP Kernel Hacking
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IP_SCTP=m
# CONFIG_SCTP_DBG_OBJCNT is not set
CONFIG_SCTP_DEFAULT_COOKIE_HMAC_MD5=y
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_SHA1 is not set
# CONFIG_SCTP_DEFAULT_COOKIE_HMAC_NONE is not set
CONFIG_SCTP_COOKIE_HMAC_MD5=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SCTP_COOKIE_HMAC_SHA1=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_INET_SCTP_DIAG=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_RDS=m
CONFIG_RDS_TCP=m
# CONFIG_RDS_DEBUG is not set
CONFIG_TIPC=m
CONFIG_TIPC_MEDIA_UDP=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_TIPC_CRYPTO=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_TIPC_DIAG=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
CONFIG_ATM_CLIP_NO_ICMP=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_ATM_LANE=m
# CONFIG_ATM_MPOA is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ATM_BR2684=m
CONFIG_ATM_BR2684_IPFILTER=y
CONFIG_L2TP=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_L2TP_DEBUGFS=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_L2TP_V3=y
CONFIG_L2TP_IP=m
CONFIG_L2TP_ETH=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_STP=m
CONFIG_GARP=m
CONFIG_MRP=m
CONFIG_BRIDGE=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BRIDGE_IGMP_SNOOPING=y
CONFIG_BRIDGE_VLAN_FILTERING=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BRIDGE_MRP is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HAVE_NET_DSA=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_DSA=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_DSA_TAG_8021Q=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_NET_DSA_TAG_AR9331 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_DSA_TAG_BRCM_COMMON=m
CONFIG_NET_DSA_TAG_BRCM=m
CONFIG_NET_DSA_TAG_BRCM_PREPEND=m
CONFIG_NET_DSA_TAG_GSWIP=m
CONFIG_NET_DSA_TAG_DSA=m
CONFIG_NET_DSA_TAG_EDSA=m
CONFIG_NET_DSA_TAG_MTK=m
CONFIG_NET_DSA_TAG_KSZ=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
CONFIG_NET_DSA_TAG_RTL4_A=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_NET_DSA_TAG_OCELOT=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_DSA_TAG_QCA=m
CONFIG_NET_DSA_TAG_LAN9303=m
CONFIG_NET_DSA_TAG_SJA1105=m
CONFIG_NET_DSA_TAG_TRAILER=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VLAN_8021Q=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_VLAN_8021Q_GVRP=y
CONFIG_VLAN_8021Q_MVRP=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_DECNET is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_LLC=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_LLC2 is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ATALK=m
CONFIG_DEV_APPLETALK=m
CONFIG_IPDDP=m
CONFIG_IPDDP_ENCAP=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_PHONET is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_6LOWPAN=m
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_6LOWPAN_DEBUGFS is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_6LOWPAN_NHC=m
CONFIG_6LOWPAN_NHC_DEST=m
CONFIG_6LOWPAN_NHC_FRAGMENT=m
CONFIG_6LOWPAN_NHC_HOP=m
CONFIG_6LOWPAN_NHC_IPV6=m
CONFIG_6LOWPAN_NHC_MOBILITY=m
CONFIG_6LOWPAN_NHC_ROUTING=m
CONFIG_6LOWPAN_NHC_UDP=m
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_6LOWPAN_GHC_EXT_HDR_HOP=m
CONFIG_6LOWPAN_GHC_UDP=m
CONFIG_6LOWPAN_GHC_ICMPV6=m
CONFIG_6LOWPAN_GHC_EXT_HDR_DEST=m
CONFIG_6LOWPAN_GHC_EXT_HDR_FRAG=m
CONFIG_6LOWPAN_GHC_EXT_HDR_ROUTE=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_IEEE802154=m
# CONFIG_IEEE802154_NL802154_EXPERIMENTAL is not set
CONFIG_IEEE802154_SOCKET=m
CONFIG_IEEE802154_6LOWPAN=m
CONFIG_MAC802154=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_SCHED=y
#
# Queueing/Scheduling
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_SCH_HFSC=m
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_NET_SCH_ATM=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_MULTIQ=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFB=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_SCH_CBS=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_SCH_ETF=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_SCH_TAPRIO=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_SCH_DRR=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_SCH_MQPRIO=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_SCH_SKBPRIO=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_SCH_CHOKE=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_SCH_QFQ=m
CONFIG_NET_SCH_CODEL=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_SCH_FQ_CODEL=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_SCH_CAKE=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_SCH_FQ=m
CONFIG_NET_SCH_HHF=m
CONFIG_NET_SCH_PIE=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_NET_SCH_FQ_PIE is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_SCH_INGRESS=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_SCH_PLUG=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_NET_SCH_ETS is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_NET_SCH_DEFAULT=y
# CONFIG_DEFAULT_FQ is not set
# CONFIG_DEFAULT_CODEL is not set
# CONFIG_DEFAULT_FQ_CODEL is not set
# CONFIG_DEFAULT_SFQ is not set
CONFIG_DEFAULT_PFIFO_FAST=y
CONFIG_DEFAULT_NET_SCH="pfifo_fast"
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
#
# Classification
#
CONFIG_NET_CLS=y
CONFIG_NET_CLS_BASIC=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_CLS_TCINDEX=m
CONFIG_NET_CLS_ROUTE4=m
CONFIG_NET_CLS_FW=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_CLS_U32=m
CONFIG_CLS_U32_PERF=y
CONFIG_CLS_U32_MARK=y
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_CLS_RSVP=m
CONFIG_NET_CLS_RSVP6=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_CLS_FLOW=m
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
CONFIG_NET_CLS_CGROUP=y
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_CLS_BPF=m
CONFIG_NET_CLS_FLOWER=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_CLS_MATCHALL=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_EMATCH=y
CONFIG_NET_EMATCH_STACK=32
CONFIG_NET_EMATCH_CMP=m
CONFIG_NET_EMATCH_NBYTE=m
CONFIG_NET_EMATCH_U32=m
CONFIG_NET_EMATCH_META=m
CONFIG_NET_EMATCH_TEXT=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_EMATCH_CANID=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_EMATCH_IPSET=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_EMATCH_IPT=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_CLS_ACT=y
CONFIG_NET_ACT_POLICE=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_ACT_GACT=m
CONFIG_GACT_PROB=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_ACT_MIRRED=m
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_NET_ACT_SAMPLE=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_ACT_IPT=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_ACT_NAT=m
CONFIG_NET_ACT_PEDIT=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_ACT_SIMP=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_ACT_SKBEDIT=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_ACT_CSUM=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_ACT_MPLS=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_ACT_VLAN=m
CONFIG_NET_ACT_BPF=m
CONFIG_NET_ACT_CONNMARK=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_ACT_CTINFO=m
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_NET_ACT_SKBMOD=m
Update networking options for mainline kernels Closes #609
2017-01-27 17:30:18 +03:00
CONFIG_NET_ACT_IFE=m
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_NET_ACT_TUNNEL_KEY=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_ACT_CT=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_NET_ACT_GATE is not set
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_NET_IFE_SKBMARK=m
CONFIG_NET_IFE_SKBPRIO=m
CONFIG_NET_IFE_SKBTCINDEX=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_NET_TC_SKB_EXT is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_SCH_FIFO=y
CONFIG_DCB=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DNS_RESOLVER=m
CONFIG_BATMAN_ADV=m
CONFIG_BATMAN_ADV_BATMAN_V=y
CONFIG_BATMAN_ADV_BLA=y
CONFIG_BATMAN_ADV_DAT=y
CONFIG_BATMAN_ADV_NC=y
CONFIG_BATMAN_ADV_MCAST=y
# CONFIG_BATMAN_ADV_DEBUGFS is not set
# CONFIG_BATMAN_ADV_DEBUG is not set
CONFIG_BATMAN_ADV_SYSFS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_OPENVSWITCH=m
CONFIG_OPENVSWITCH_GRE=m
CONFIG_OPENVSWITCH_VXLAN=m
CONFIG_OPENVSWITCH_GENEVE=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VSOCKETS=m
CONFIG_VSOCKETS_DIAG=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_VSOCKETS_LOOPBACK=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIRTIO_VSOCKETS=m
CONFIG_VIRTIO_VSOCKETS_COMMON=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NETLINK_DIAG=m
CONFIG_MPLS=y
CONFIG_NET_MPLS_GSO=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MPLS_ROUTING=m
CONFIG_MPLS_IPTUNNEL=m
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_NET_NSH=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_HSR=m
CONFIG_NET_SWITCHDEV=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_L3_MASTER_DEV=y
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_QRTR=m
CONFIG_QRTR_TUN=m
CONFIG_QRTR_MHI=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_NCSI=y
CONFIG_NCSI_OEM_CMD_GET_MAC=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_RPS=y
CONFIG_RFS_ACCEL=y
CONFIG_XPS=y
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_HWBM=y
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
CONFIG_CGROUP_NET_PRIO=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CGROUP_NET_CLASSID=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NET_RX_BUSY_POLL=y
CONFIG_BQL=y
Update mvebu-next config
2017-06-12 13:02:33 +03:00
CONFIG_BPF_JIT=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NET_FLOW_LIMIT=y
#
# Network testing
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_PKTGEN=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Network testing
# end of Networking options
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HAMRADIO=y
#
# Packet Radio protocols
#
CONFIG_AX25=m
CONFIG_AX25_DAMA_SLAVE=y
CONFIG_NETROM=m
CONFIG_ROSE=m
#
# AX.25 network device drivers
#
CONFIG_MKISS=m
CONFIG_6PACK=m
CONFIG_BPQETHER=m
CONFIG_BAYCOM_SER_FDX=m
CONFIG_BAYCOM_SER_HDX=m
# CONFIG_BAYCOM_PAR is not set
Bugfix: adjust mvebu-current kernel config It boots up properly now @boards-marvell Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
2020-04-29 12:27:29 +02:00
CONFIG_BAYCOM_EPP=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_YAM=m
# end of AX.25 network device drivers
CONFIG_CAN=m
CONFIG_CAN_RAW=m
CONFIG_CAN_BCM=m
CONFIG_CAN_GW=m
CONFIG_CAN_J1939=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_CAN_ISOTP=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
#
# CAN Device Drivers
#
CONFIG_CAN_VCAN=m
CONFIG_CAN_VXCAN=m
CONFIG_CAN_SLCAN=m
CONFIG_CAN_DEV=m
CONFIG_CAN_CALC_BITTIMING=y
CONFIG_CAN_FLEXCAN=m
CONFIG_CAN_GRCAN=m
CONFIG_CAN_KVASER_PCIEFD=m
CONFIG_CAN_TI_HECC=m
CONFIG_CAN_C_CAN=m
CONFIG_CAN_C_CAN_PLATFORM=m
CONFIG_CAN_C_CAN_PCI=m
CONFIG_CAN_CC770=m
CONFIG_CAN_CC770_ISA=m
CONFIG_CAN_CC770_PLATFORM=m
# CONFIG_CAN_IFI_CANFD is not set
CONFIG_CAN_M_CAN=m
CONFIG_CAN_M_CAN_PLATFORM=m
CONFIG_CAN_M_CAN_TCAN4X5X=m
CONFIG_CAN_PEAK_PCIEFD=m
CONFIG_CAN_RCAR=m
CONFIG_CAN_RCAR_CANFD=m
CONFIG_CAN_SJA1000=m
CONFIG_CAN_EMS_PCI=m
CONFIG_CAN_F81601=m
CONFIG_CAN_KVASER_PCI=m
CONFIG_CAN_PEAK_PCI=m
CONFIG_CAN_PEAK_PCIEC=y
CONFIG_CAN_PLX_PCI=m
CONFIG_CAN_SJA1000_ISA=m
CONFIG_CAN_SJA1000_PLATFORM=m
CONFIG_CAN_SOFTING=m
#
# CAN SPI interfaces
#
CONFIG_CAN_HI311X=m
CONFIG_CAN_MCP251X=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_CAN_MCP251XFD=m
# CONFIG_CAN_MCP251XFD_SANITY is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# end of CAN SPI interfaces
#
# CAN USB interfaces
#
CONFIG_CAN_8DEV_USB=m
CONFIG_CAN_EMS_USB=m
CONFIG_CAN_ESD_USB2=m
CONFIG_CAN_GS_USB=m
CONFIG_CAN_KVASER_USB=m
CONFIG_CAN_MCBA_USB=m
CONFIG_CAN_PEAK_USB=m
CONFIG_CAN_UCAN=m
# end of CAN USB interfaces
# CONFIG_CAN_DEBUG_DEVICES is not set
# end of CAN Device Drivers
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BT=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_BT_BREDR=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BT_RFCOMM=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BT_RFCOMM_TTY=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BT_BNEP=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BT_HIDP=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_BT_HS=y
CONFIG_BT_LE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BT_6LOWPAN=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BT_LEDS=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BT_MSFTEXT is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_BT_DEBUGFS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BT_SELFTEST is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Bluetooth device drivers
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BT_INTEL=m
CONFIG_BT_BCM=m
CONFIG_BT_RTL=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BT_QCA=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BT_HCIBTUSB=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BT_HCIBTUSB_AUTOSUSPEND=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BT_HCIBTUSB_BCM=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_BT_HCIBTUSB_MTK is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BT_HCIBTUSB_RTL=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BT_HCIBTSDIO=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BT_HCIUART=m
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_BT_HCIUART_SERDEV=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BT_HCIUART_H4=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BT_HCIUART_NOKIA=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_ATH3K=y
CONFIG_BT_HCIUART_LL=y
CONFIG_BT_HCIUART_3WIRE=y
CONFIG_BT_HCIUART_INTEL=y
CONFIG_BT_HCIUART_BCM=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BT_HCIUART_RTL is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BT_HCIUART_QCA=y
CONFIG_BT_HCIUART_AG6XX=y
CONFIG_BT_HCIUART_MRVL=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BT_MRVL=m
CONFIG_BT_MRVL_SDIO=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BT_ATH3K=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_BT_MTKSDIO=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BT_MTKUART=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Bluetooth device drivers
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AF_RXRPC=m
# CONFIG_AF_RXRPC_IPV6 is not set
# CONFIG_AF_RXRPC_INJECT_LOSS is not set
# CONFIG_AF_RXRPC_DEBUG is not set
# CONFIG_RXKAD is not set
CONFIG_AF_KCM=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_STREAM_PARSER=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_FIB_RULES=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_WIRELESS=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_WIRELESS_EXT=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_WEXT_SPY=y
CONFIG_WEXT_PRIV=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CFG80211=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_NL80211_TESTMODE is not set
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y
CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CFG80211_DEFAULT_PS=y
CONFIG_CFG80211_DEBUGFS=y
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
CONFIG_CFG80211_CRDA_SUPPORT=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CFG80211_WEXT=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_CFG80211_WEXT_EXPORT=y
CONFIG_LIB80211=m
CONFIG_LIB80211_CRYPT_WEP=m
CONFIG_LIB80211_CRYPT_CCMP=m
CONFIG_LIB80211_CRYPT_TKIP=m
# CONFIG_LIB80211_DEBUG is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_MAC80211=m
CONFIG_MAC80211_HAS_RC=y
CONFIG_MAC80211_RC_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT_MINSTREL=y
CONFIG_MAC80211_RC_DEFAULT="minstrel_ht"
Merge safe changes from development to master, part 2
2018-04-29 16:02:11 +03:00
CONFIG_MAC80211_MESH=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_MAC80211_LEDS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MAC80211_DEBUGFS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_MAC80211_MESSAGE_TRACING is not set
# CONFIG_MAC80211_DEBUG_MENU is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MAC80211_STA_HASH_MAX_SIZE=0
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_WIMAX=m
CONFIG_WIMAX_DEBUG_LEVEL=8
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_RFKILL=m
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
CONFIG_RFKILL_GPIO=m
Update mvebu kernel configs
2017-05-28 19:22:20 +03:00
CONFIG_NET_9P=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_9P_VIRTIO=m
Update mvebu kernel configs
2017-05-28 19:22:20 +03:00
# CONFIG_NET_9P_DEBUG is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CAIF is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CEPH_LIB=m
# CONFIG_CEPH_LIB_PRETTYDEBUG is not set
# CONFIG_CEPH_LIB_USE_DNS_RESOLVER is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NFC=m
CONFIG_NFC_DIGITAL=m
CONFIG_NFC_NCI=m
CONFIG_NFC_NCI_SPI=m
CONFIG_NFC_NCI_UART=m
CONFIG_NFC_HCI=m
CONFIG_NFC_SHDLC=y
#
# Near Field Communication (NFC) devices
#
CONFIG_NFC_TRF7970A=m
CONFIG_NFC_SIM=m
CONFIG_NFC_PORT100=m
CONFIG_NFC_FDP=m
CONFIG_NFC_FDP_I2C=m
CONFIG_NFC_PN544=m
CONFIG_NFC_PN544_I2C=m
CONFIG_NFC_PN533=m
CONFIG_NFC_PN533_USB=m
CONFIG_NFC_PN533_I2C=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_NFC_PN532_UART is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NFC_MICROREAD=m
CONFIG_NFC_MICROREAD_I2C=m
CONFIG_NFC_MRVL=m
CONFIG_NFC_MRVL_USB=m
CONFIG_NFC_MRVL_UART=m
CONFIG_NFC_MRVL_I2C=m
CONFIG_NFC_MRVL_SPI=m
CONFIG_NFC_ST21NFCA=m
CONFIG_NFC_ST21NFCA_I2C=m
CONFIG_NFC_ST_NCI=m
CONFIG_NFC_ST_NCI_I2C=m
CONFIG_NFC_ST_NCI_SPI=m
CONFIG_NFC_NXP_NCI=m
CONFIG_NFC_NXP_NCI_I2C=m
CONFIG_NFC_S3FWRN5=m
CONFIG_NFC_S3FWRN5_I2C=m
CONFIG_NFC_ST95HF=m
# end of Near Field Communication (NFC) devices
CONFIG_PSAMPLE=m
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_NET_IFE=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_LWTUNNEL=y
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_LWTUNNEL_BPF=y
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_DST_CACHE=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_GRO_CELLS=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_SOCK_MSG=y
CONFIG_NET_DEVLINK=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_PAGE_POOL=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_FAILOVER=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_ETHTOOL_NETLINK=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_HAVE_EBPF_JIT=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Device Drivers
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_HAVE_PCI=y
CONFIG_PCI=y
CONFIG_PCI_DOMAINS=y
CONFIG_PCI_DOMAINS_GENERIC=y
CONFIG_PCI_SYSCALL=y
# CONFIG_PCIEPORTBUS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_PCIEASPM=y
CONFIG_PCIEASPM_DEFAULT=y
# CONFIG_PCIEASPM_POWERSAVE is not set
# CONFIG_PCIEASPM_POWER_SUPERSAVE is not set
# CONFIG_PCIEASPM_PERFORMANCE is not set
# CONFIG_PCIE_PTM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_PCI_MSI=y
CONFIG_PCI_MSI_IRQ_DOMAIN=y
CONFIG_PCI_QUIRKS=y
CONFIG_PCI_DEBUG=y
# CONFIG_PCI_STUB is not set
CONFIG_PCI_BRIDGE_EMUL=y
# CONFIG_PCI_IOV is not set
# CONFIG_PCI_PRI is not set
# CONFIG_PCI_PASID is not set
# CONFIG_HOTPLUG_PCI is not set
#
# PCI controller drivers
#
CONFIG_PCI_MVEBU=y
# CONFIG_PCI_FTPCI100 is not set
# CONFIG_PCI_HOST_GENERIC is not set
# CONFIG_PCIE_XILINX is not set
# CONFIG_PCI_V3_SEMI is not set
# CONFIG_PCIE_ALTERA is not set
#
# DesignWare PCI Core Support
#
# CONFIG_PCIE_DW_PLAT_HOST is not set
# CONFIG_PCI_LAYERSCAPE is not set
# CONFIG_PCIE_ARMADA_8K is not set
# CONFIG_PCI_MESON is not set
# end of DesignWare PCI Core Support
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
#
# Mobiveil PCIe Core Support
#
# end of Mobiveil PCIe Core Support
#
# Cadence PCIe controllers support
#
# CONFIG_PCIE_CADENCE_PLAT_HOST is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_PCI_J721E_HOST is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# end of Cadence PCIe controllers support
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of PCI controller drivers
#
# PCI Endpoint
#
# CONFIG_PCI_ENDPOINT is not set
# end of PCI Endpoint
#
# PCI switch controller drivers
#
# CONFIG_PCI_SW_SWITCHTEC is not set
# end of PCI switch controller drivers
# CONFIG_PCCARD is not set
CONFIG_RAPIDIO=m
CONFIG_RAPIDIO_DISC_TIMEOUT=30
# CONFIG_RAPIDIO_ENABLE_RX_TX_PORTS is not set
# CONFIG_RAPIDIO_DMA_ENGINE is not set
# CONFIG_RAPIDIO_DEBUG is not set
# CONFIG_RAPIDIO_ENUM_BASIC is not set
# CONFIG_RAPIDIO_CHMAN is not set
# CONFIG_RAPIDIO_MPORT_CDEV is not set
#
# RapidIO Switch drivers
#
# CONFIG_RAPIDIO_TSI57X is not set
# CONFIG_RAPIDIO_CPS_XX is not set
# CONFIG_RAPIDIO_TSI568 is not set
# CONFIG_RAPIDIO_CPS_GEN2 is not set
# CONFIG_RAPIDIO_RXS_GEN3 is not set
# end of RapidIO Switch drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Generic Driver Options
#
CONFIG_UEVENT_HELPER=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_UEVENT_HELPER_PATH=""
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Firmware loader
#
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_FW_LOADER=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_FW_LOADER_PAGED_BUF=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_EXTRA_FIRMWARE=""
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_FW_LOADER_USER_HELPER=y
CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_FW_LOADER_COMPRESS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_FW_CACHE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Firmware loader
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_WANT_DEV_COREDUMP=y
CONFIG_ALLOW_DEV_COREDUMP=y
CONFIG_DEV_COREDUMP=y
Enable minimal kernel debug info - Enable KGDB support - Enable earlycon and earlyprintk support
2017-12-30 16:50:10 +08:00
# CONFIG_DEBUG_DRIVER is not set
# CONFIG_DEBUG_DEVRES is not set
# CONFIG_DEBUG_TEST_DRIVER_REMOVE is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_TEST_ASYNC_DRIVER_PROBE is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_GENERIC_CPU_AUTOPROBE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SOC_BUS=y
CONFIG_REGMAP=y
CONFIG_REGMAP_I2C=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_REGMAP_SPI=m
CONFIG_REGMAP_W1=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_REGMAP_MMIO=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_REGMAP_IRQ=y
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_REGMAP_SPI_AVMM=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_DMA_SHARED_BUFFER=y
# CONFIG_DMA_FENCE_TRACE is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_GENERIC_ARCH_TOPOLOGY=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Generic Driver Options
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Bus devices
#
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARM_CCI=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_BRCMSTB_GISB_ARB is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MOXTET is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MVEBU_MBUS=y
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_SIMPLE_PM_BUS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_VEXPRESS_CONFIG is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_MHI_BUS=m
# CONFIG_MHI_BUS_DEBUG is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Bus devices
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CONNECTOR is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_GNSS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MTD=y
# CONFIG_MTD_TESTS is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
#
# Partition parsers
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MTD_AR7_PARTS is not set
# CONFIG_MTD_CMDLINE_PARTS is not set
CONFIG_MTD_OF_PARTS=y
# CONFIG_MTD_AFS_PARTS is not set
# CONFIG_MTD_REDBOOT_PARTS is not set
# end of Partition parsers
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# User Modules And Translation Layers
#
CONFIG_MTD_BLKDEVS=y
CONFIG_MTD_BLOCK=y
# CONFIG_FTL is not set
# CONFIG_NFTL is not set
# CONFIG_INFTL is not set
# CONFIG_RFD_FTL is not set
# CONFIG_SSFDC is not set
# CONFIG_SM_FTL is not set
# CONFIG_MTD_OOPS is not set
# CONFIG_MTD_SWAP is not set
# CONFIG_MTD_PARTITIONED_MASTER is not set
#
# RAM/ROM/Flash chip drivers
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MTD_CFI=m
# CONFIG_MTD_JEDECPROBE is not set
CONFIG_MTD_GEN_PROBE=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MTD_CFI_ADV_OPTIONS is not set
CONFIG_MTD_MAP_BANK_WIDTH_1=y
CONFIG_MTD_MAP_BANK_WIDTH_2=y
CONFIG_MTD_MAP_BANK_WIDTH_4=y
CONFIG_MTD_CFI_I1=y
CONFIG_MTD_CFI_I2=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MTD_CFI_INTELEXT=m
CONFIG_MTD_CFI_AMDSTD=m
CONFIG_MTD_CFI_STAA=m
CONFIG_MTD_CFI_UTIL=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of RAM/ROM/Flash chip drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Mapping drivers for chip access
#
# CONFIG_MTD_COMPLEX_MAPPINGS is not set
# CONFIG_MTD_PHYSMAP is not set
# CONFIG_MTD_INTEL_VR_NOR is not set
# CONFIG_MTD_PLATRAM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Mapping drivers for chip access
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_DATAFLASH is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_MTD_MCHP23K256 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MTD_SST25L is not set
# CONFIG_MTD_SLRAM is not set
# CONFIG_MTD_PHRAM is not set
# CONFIG_MTD_MTDRAM is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MTD_BLOCK2MTD=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOCG3 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Self-contained MTD device drivers
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
#
# NAND
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MTD_NAND_CORE=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MTD_ONENAND is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MTD_NAND_ECC_SW_HAMMING=m
# CONFIG_MTD_NAND_ECC_SW_HAMMING_SMC is not set
CONFIG_MTD_RAW_NAND=m
# CONFIG_MTD_NAND_ECC_SW_BCH is not set
#
# Raw/parallel NAND flash controllers
#
CONFIG_MTD_NAND_DENALI=m
CONFIG_MTD_NAND_DENALI_PCI=m
CONFIG_MTD_NAND_DENALI_DT=m
CONFIG_MTD_NAND_CAFE=m
CONFIG_MTD_NAND_ORION=m
CONFIG_MTD_NAND_MARVELL=m
CONFIG_MTD_NAND_BRCMNAND=m
# CONFIG_MTD_NAND_MXIC is not set
CONFIG_MTD_NAND_GPIO=m
CONFIG_MTD_NAND_PLATFORM=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MTD_NAND_CADENCE is not set
# CONFIG_MTD_NAND_ARASAN is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Misc
#
CONFIG_MTD_SM_COMMON=m
CONFIG_MTD_NAND_NANDSIM=m
CONFIG_MTD_NAND_RICOH=m
CONFIG_MTD_NAND_DISKONCHIP=m
# CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADVANCED is not set
CONFIG_MTD_NAND_DISKONCHIP_PROBE_ADDRESS=0
# CONFIG_MTD_NAND_DISKONCHIP_BBTWRITE is not set
# CONFIG_MTD_SPI_NAND is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
#
# ECC engine support
#
CONFIG_MTD_NAND_ECC=y
# end of ECC engine support
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# end of NAND
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# LPDDR & LPDDR2 PCM memory drivers
#
# CONFIG_MTD_LPDDR is not set
# CONFIG_MTD_LPDDR2_NVM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of LPDDR & LPDDR2 PCM memory drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MTD_SPI_NOR=y
CONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y
# CONFIG_MTD_UBI is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MTD_HYPERBUS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_DTC=y
CONFIG_OF=y
# CONFIG_OF_UNITTEST is not set
CONFIG_OF_FLATTREE=y
CONFIG_OF_EARLY_FLATTREE=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_OF_KOBJ=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_OF_DYNAMIC=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_OF_ADDRESS=y
CONFIG_OF_IRQ=y
CONFIG_OF_NET=y
CONFIG_OF_RESERVED_MEM=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_OF_RESOLVE=y
CONFIG_OF_OVERLAY=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ARCH_MIGHT_HAVE_PC_PARPORT=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_PARPORT=m
# CONFIG_PARPORT_PC is not set
CONFIG_PARPORT_AX88796=m
# CONFIG_PARPORT_1284 is not set
CONFIG_PARPORT_NOT_PC=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_BLK_DEV=y
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_BLK_DEV_NULL_BLK=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_BLK_DEV_PCIESSD_MTIP32XX is not set
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_ZRAM=m
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_ZRAM_WRITEBACK=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ZRAM_MEMORY_TRACKING is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_BLK_DEV_UMEM is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_BLK_DEV_CRYPTOLOOP=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_COUNT=8
CONFIG_BLK_DEV_RAM_SIZE=4096
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CDROM_PKTCDVD is not set
Enable CONFIG_ATA_OVER_ETH https://github.com/armbian/build/issues/788
2017-09-30 23:01:57 +02:00
CONFIG_ATA_OVER_ETH=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIRTIO_BLK=m
add rbd module to configs it was missing in (#1835)
2020-03-06 19:25:58 +00:00
CONFIG_BLK_DEV_RBD=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_BLK_DEV_RSXX is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# NVME Support
#
CONFIG_NVME_CORE=y
CONFIG_BLK_DEV_NVME=y
# CONFIG_NVME_MULTIPATH is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_NVME_HWMON is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NVME_FABRICS=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_NVME_FC is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NVME_TCP=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NVME_TARGET is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of NVME Support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Misc devices
#
# CONFIG_AD525X_DPOT is not set
# CONFIG_DUMMY_IRQ is not set
# CONFIG_PHANTOM is not set
# CONFIG_TIFM_CORE is not set
# CONFIG_ICS932S401 is not set
# CONFIG_ENCLOSURE_SERVICES is not set
# CONFIG_HP_ILO is not set
# CONFIG_APDS9802ALS is not set
# CONFIG_ISL29003 is not set
# CONFIG_ISL29020 is not set
# CONFIG_SENSORS_TSL2550 is not set
# CONFIG_SENSORS_BH1770 is not set
# CONFIG_SENSORS_APDS990X is not set
# CONFIG_HMC6352 is not set
# CONFIG_DS1682 is not set
# CONFIG_LATTICE_ECP3_CONFIG is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_SRAM=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_SRAM_EXEC=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_PCI_ENDPOINT_TEST is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_XILINX_SDFEC is not set
CONFIG_MISC_RTSX=m
CONFIG_PVPANIC=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_HISI_HIKEY_USB=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_C2PORT is not set
#
# EEPROM support
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_EEPROM_AT24=m
CONFIG_EEPROM_AT25=m
CONFIG_EEPROM_LEGACY=m
CONFIG_EEPROM_MAX6875=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_EEPROM_93CX6=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_EEPROM_93XX46=m
CONFIG_EEPROM_IDT_89HPESX=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_EEPROM_EE1004=m
# end of EEPROM support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CB710_CORE is not set
#
# Texas Instruments shared transport line discipline
#
# CONFIG_TI_ST is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Texas Instruments shared transport line discipline
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SENSORS_LIS3_SPI is not set
# CONFIG_SENSORS_LIS3_I2C is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_ALTERA_STAPL is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ECHO is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MISC_ALCOR_PCI=m
CONFIG_MISC_RTSX_PCI=m
CONFIG_MISC_RTSX_USB=m
CONFIG_HABANA_AI=m
# end of Misc devices
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_SCSI_MOD=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RAID_ATTRS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_BLK_DEV_SR is not set
Enable iSCSI kernel options for mvebu-next
2018-02-17 16:50:52 +03:00
CONFIG_CHR_DEV_SG=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CHR_DEV_SCH is not set
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
#
# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
Enable iSCSI kernel options for mvebu-next
2018-02-17 16:50:52 +03:00
CONFIG_SCSI_ISCSI_ATTRS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of SCSI Transports
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SCSI_LOWLEVEL=y
Enable iSCSI kernel options for mvebu-next
2018-02-17 16:50:52 +03:00
CONFIG_ISCSI_TCP=m
CONFIG_ISCSI_BOOT_SYSFS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SCSI_CXGB3_ISCSI is not set
# CONFIG_SCSI_CXGB4_ISCSI is not set
# CONFIG_SCSI_BNX2_ISCSI is not set
# CONFIG_BE2ISCSI is not set
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_HPSA is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_3W_SAS is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC94XX is not set
# CONFIG_SCSI_MVSAS is not set
# CONFIG_SCSI_MVUMI is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ESAS2R is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_MEGARAID_SAS is not set
# CONFIG_SCSI_MPT3SAS is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_SCSI_MPT2SAS is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_SCSI_SMARTPQI is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SCSI_UFSHCD is not set
# CONFIG_SCSI_HPTIOP is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_SCSI_MYRB=m
CONFIG_SCSI_MYRS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SCSI_SNIC is not set
# CONFIG_SCSI_DMX3191D is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_SCSI_FDOMAIN_PCI is not set
CONFIG_SCSI_GDTH=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_STEX is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_QLA_ISCSI is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_WD719X is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_SCSI_PM8001 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SCSI_VIRTIO=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SCSI_DH is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of SCSI device support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ATA=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_SATA_HOST=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ATA_VERBOSE_ERROR=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_ATA_FORCE=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_ARCH_WANT_LIBATA_LEDS=y
CONFIG_ATA_LEDS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SATA_PMP=y
#
# Controllers with non-SFF native interface
#
Small Clearfog fixes
2017-04-14 22:42:14 +02:00
CONFIG_SATA_AHCI=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SATA_MOBILE_LPM_POLICY=0
Small Clearfog fixes
2017-04-14 22:42:14 +02:00
CONFIG_SATA_AHCI_PLATFORM=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_AHCI_CEVA is not set
CONFIG_AHCI_MVEBU=y
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_AHCI_QORIQ is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_ACARD_AHCI is not set
# CONFIG_SATA_SIL24 is not set
CONFIG_ATA_SFF=y
#
# SFF controllers with custom DMA interface
#
# CONFIG_PDC_ADMA is not set
# CONFIG_SATA_QSTOR is not set
# CONFIG_SATA_SX4 is not set
CONFIG_ATA_BMDMA=y
#
# SATA SFF controllers with BMDMA
#
# CONFIG_ATA_PIIX is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_SATA_DWC=m
# CONFIG_SATA_DWC_OLD_DMA is not set
# CONFIG_SATA_DWC_DEBUG is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SATA_MV=y
# CONFIG_SATA_NV is not set
# CONFIG_SATA_PROMISE is not set
# CONFIG_SATA_SIL is not set
# CONFIG_SATA_SIS is not set
# CONFIG_SATA_SVW is not set
# CONFIG_SATA_ULI is not set
# CONFIG_SATA_VIA is not set
# CONFIG_SATA_VITESSE is not set
#
# PATA SFF controllers with BMDMA
#
# CONFIG_PATA_ALI is not set
# CONFIG_PATA_AMD is not set
# CONFIG_PATA_ARTOP is not set
# CONFIG_PATA_ATIIXP is not set
# CONFIG_PATA_ATP867X is not set
# CONFIG_PATA_CMD64X is not set
# CONFIG_PATA_CYPRESS is not set
# CONFIG_PATA_EFAR is not set
# CONFIG_PATA_HPT366 is not set
# CONFIG_PATA_HPT37X is not set
# CONFIG_PATA_HPT3X2N is not set
# CONFIG_PATA_HPT3X3 is not set
# CONFIG_PATA_IT8213 is not set
# CONFIG_PATA_IT821X is not set
# CONFIG_PATA_JMICRON is not set
# CONFIG_PATA_MARVELL is not set
# CONFIG_PATA_NETCELL is not set
# CONFIG_PATA_NINJA32 is not set
# CONFIG_PATA_NS87415 is not set
# CONFIG_PATA_OLDPIIX is not set
# CONFIG_PATA_OPTIDMA is not set
# CONFIG_PATA_PDC2027X is not set
# CONFIG_PATA_PDC_OLD is not set
# CONFIG_PATA_RADISYS is not set
# CONFIG_PATA_RDC is not set
# CONFIG_PATA_SCH is not set
# CONFIG_PATA_SERVERWORKS is not set
# CONFIG_PATA_SIL680 is not set
# CONFIG_PATA_SIS is not set
# CONFIG_PATA_TOSHIBA is not set
# CONFIG_PATA_TRIFLEX is not set
# CONFIG_PATA_VIA is not set
# CONFIG_PATA_WINBOND is not set
#
# PIO-only SFF controllers
#
# CONFIG_PATA_CMD640_PCI is not set
# CONFIG_PATA_MPIIX is not set
# CONFIG_PATA_NS87410 is not set
# CONFIG_PATA_OPTI is not set
# CONFIG_PATA_RZ1000 is not set
#
# Generic fallback / legacy drivers
#
# CONFIG_ATA_GENERIC is not set
# CONFIG_PATA_LEGACY is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_MD=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_BLK_DEV_MD=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MD_LINEAR=m
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID10=m
CONFIG_MD_RAID456=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MD_MULTIPATH=m
CONFIG_MD_FAULTY=m
CONFIG_MD_CLUSTER=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_BCACHE=m
# CONFIG_BCACHE_DEBUG is not set
# CONFIG_BCACHE_CLOSURES_DEBUG is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_BCACHE_ASYNC_REGISTRATION is not set
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
CONFIG_BLK_DEV_DM_BUILTIN=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BLK_DEV_DM=m
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
# CONFIG_DM_DEBUG is not set
CONFIG_DM_BUFIO=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING is not set
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
CONFIG_DM_BIO_PRISON=m
CONFIG_DM_PERSISTENT_DATA=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_DM_UNSTRIPED is not set
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
CONFIG_DM_CRYPT=m
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_THIN_PROVISIONING=m
CONFIG_DM_CACHE=m
CONFIG_DM_CACHE_SMQ=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DM_WRITECACHE=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_DM_EBS is not set
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
# CONFIG_DM_ERA is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DM_CLONE=m
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_DM_MIRROR=m
# CONFIG_DM_LOG_USERSPACE is not set
CONFIG_DM_RAID=m
CONFIG_DM_ZERO=m
CONFIG_DM_MULTIPATH=m
# CONFIG_DM_MULTIPATH_QL is not set
# CONFIG_DM_MULTIPATH_ST is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_DM_MULTIPATH_HST is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_DM_DELAY=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_DM_DUST=m
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
# CONFIG_DM_UEVENT is not set
# CONFIG_DM_FLAKEY is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_DM_VERITY=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_DM_VERITY_FEC is not set
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
# CONFIG_DM_SWITCH is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_DM_LOG_WRITES=m
CONFIG_DM_INTEGRITY=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_DM_ZONED=m
Update configs (#2345) * Update configs
2020-11-14 16:47:12 +01:00
CONFIG_TARGET_CORE=m
CONFIG_TCM_IBLOCK=m
CONFIG_TCM_FILEIO=m
CONFIG_TCM_PSCSI=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_LOOPBACK_TARGET is not set
Update configs (#2345) * Update configs
2020-11-14 16:47:12 +01:00
CONFIG_ISCSI_TARGET=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_FIREWIRE_NOSY is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of IEEE 1394 (FireWire) support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NETDEVICES=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_MII=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NET_CORE=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_BONDING=m
CONFIG_DUMMY=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_WIREGUARD=m
# CONFIG_WIREGUARD_DEBUG is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_EQUALIZER is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NET_FC=y
CONFIG_IFB=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_NET_TEAM=m
CONFIG_NET_TEAM_MODE_BROADCAST=m
CONFIG_NET_TEAM_MODE_ROUNDROBIN=m
CONFIG_NET_TEAM_MODE_RANDOM=m
CONFIG_NET_TEAM_MODE_ACTIVEBACKUP=m
CONFIG_NET_TEAM_MODE_LOADBALANCE=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_MACVLAN=m
CONFIG_MACVTAP=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_IPVLAN_L3S=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_IPVLAN=m
CONFIG_IPVTAP=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_VXLAN=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_GENEVE=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BAREUDP is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_GTP=m
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_MACSEC=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_NETCONSOLE is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RIONET=m
CONFIG_RIONET_TX_SIZE=128
CONFIG_RIONET_RX_SIZE=128
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_TUN=m
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_TAP=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_TUN_VNET_CROSS_LE is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_VETH=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIRTIO_NET=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_NLMON=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VRF=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VSOCKMON=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ARCNET is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ATM_DRIVERS=y
CONFIG_ATM_DUMMY=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_ATM_TCP=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_ATM_LANAI is not set
# CONFIG_ATM_ENI is not set
# CONFIG_ATM_NICSTAR is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_IA is not set
# CONFIG_ATM_FORE200E is not set
# CONFIG_ATM_HE is not set
# CONFIG_ATM_SOLOS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Distributed Switch Architecture drivers
#
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
# CONFIG_B53 is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_NET_DSA_BCM_SF2 is not set
# CONFIG_NET_DSA_LOOP is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_DSA_LANTIQ_GSWIP=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_NET_DSA_MT7530 is not set
CONFIG_NET_DSA_MV88E6060=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_NET_DSA_MICROCHIP_KSZ9477 is not set
# CONFIG_NET_DSA_MICROCHIP_KSZ8795 is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_NET_DSA_MV88E6XXX=m
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_NET_DSA_MV88E6XXX_GLOBAL2=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_NET_DSA_MV88E6XXX_PTP is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_NET_DSA_MSCC_SEVILLE=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_NET_DSA_AR9331 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_DSA_SJA1105=m
# CONFIG_NET_DSA_SJA1105_PTP is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_NET_DSA_QCA8K is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_DSA_REALTEK_SMI=m
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_NET_DSA_SMSC_LAN9303_I2C is not set
# CONFIG_NET_DSA_SMSC_LAN9303_MDIO is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_DSA_VITESSE_VSC73XX=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_DSA_VITESSE_VSC73XX_SPI=m
CONFIG_NET_DSA_VITESSE_VSC73XX_PLATFORM=m
# end of Distributed Switch Architecture drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ETHERNET=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_NET_VENDOR_ADAPTEC is not set
# CONFIG_NET_VENDOR_AGERE is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_NET_VENDOR_ALACRITECH is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_ALTEON is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ALTERA_TSE is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_NET_VENDOR_AMAZON is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_AMD is not set
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_NET_VENDOR_AQUANTIA is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_ARC is not set
# CONFIG_NET_VENDOR_ATHEROS is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_NET_VENDOR_AURORA is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_BROADCOM is not set
# CONFIG_NET_VENDOR_BROCADE is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VENDOR_CADENCE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MACB is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_CAVIUM is not set
# CONFIG_NET_VENDOR_CHELSIO is not set
# CONFIG_NET_VENDOR_CIRRUS is not set
# CONFIG_NET_VENDOR_CISCO is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VENDOR_CORTINA=y
CONFIG_GEMINI_ETHERNET=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_DM9000 is not set
# CONFIG_DNET is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_DEC is not set
# CONFIG_NET_VENDOR_DLINK is not set
# CONFIG_NET_VENDOR_EMULEX is not set
# CONFIG_NET_VENDOR_EZCHIP is not set
# CONFIG_NET_VENDOR_FARADAY is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_VENDOR_GOOGLE=y
# CONFIG_GVE is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_HISILICON is not set
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_NET_VENDOR_HUAWEI=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_INTEL is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_JME is not set
CONFIG_NET_VENDOR_MARVELL=y
CONFIG_MV643XX_ETH=y
CONFIG_MVMDIO=y
Update pine64-dev and marvell-next kernel configs
2016-11-30 20:38:04 +03:00
CONFIG_MVNETA_BM_ENABLE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MVNETA=y
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_MVNETA_BM=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MVPP2=y
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_PRESTERA=m
CONFIG_PRESTERA_PCI=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_MELLANOX is not set
# CONFIG_NET_VENDOR_MICREL is not set
# CONFIG_NET_VENDOR_MICROCHIP is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VENDOR_MICROSEMI=y
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_MSCC_OCELOT_SWITCH_LIB=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MSCC_OCELOT_SWITCH is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_MYRI is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_FEALNX is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_NATSEMI is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VENDOR_NETERION=y
# CONFIG_S2IO is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_VXGE is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_NETRONOME is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VENDOR_NI=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NI_XGE_MANAGEMENT_ENET=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_NVIDIA is not set
# CONFIG_NET_VENDOR_OKI is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ETHOC is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VENDOR_PACKET_ENGINES=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
CONFIG_NET_VENDOR_PENSANDO=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_QLOGIC is not set
# CONFIG_NET_VENDOR_QUALCOMM is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_NET_VENDOR_RDC is not set
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_NET_VENDOR_REALTEK=y
CONFIG_8139CP=m
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=y
CONFIG_8139TOO_TUNE_TWISTER=y
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
CONFIG_R8169=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_RENESAS is not set
# CONFIG_NET_VENDOR_ROCKER is not set
# CONFIG_NET_VENDOR_SAMSUNG is not set
# CONFIG_NET_VENDOR_SEEQ is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_NET_VENDOR_SOLARFLARE is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_SILAN is not set
# CONFIG_NET_VENDOR_SIS is not set
# CONFIG_NET_VENDOR_SMSC is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VENDOR_SOCIONEXT=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_NET_VENDOR_SUN is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NET_VENDOR_SYNOPSYS=y
# CONFIG_DWC_XLGMAC is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_NET_VENDOR_TEHUTI is not set
# CONFIG_NET_VENDOR_TI is not set
# CONFIG_NET_VENDOR_VIA is not set
# CONFIG_NET_VENDOR_WIZNET is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NET_VENDOR_XILINX=y
# CONFIG_XILINX_AXI_EMAC is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_XILINX_LL_TEMAC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_PHYLINK=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_PHYLIB=y
CONFIG_SWPHY=y
CONFIG_LED_TRIGGER_PHY=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_FIXED_PHY=y
CONFIG_SFP=m
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# MII PHY device drivers
#
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_AMD_PHY is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_ADIN_PHY is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_AQUANTIA_PHY is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_AX88796B_PHY=m
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_BROADCOM_PHY is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BCM54140_PHY is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_BCM7XXX_PHY is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BCM84881_PHY is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_BCM87XX_PHY is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_CICADA_PHY is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_CORTINA_PHY is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_DAVICOM_PHY is not set
# CONFIG_ICPLUS_PHY is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_LXT_PHY is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
# CONFIG_INTEL_XWAY_PHY is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_LSI_ET1011C_PHY is not set
CONFIG_MARVELL_PHY=y
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_MARVELL_10G_PHY is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_MICREL_PHY is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MICROCHIP_PHY=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MICROCHIP_T1_PHY is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_MICROSEMI_PHY is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NATIONAL_PHY=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_NXP_TJA11XX_PHY is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_AT803X_PHY is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_QSEMI_PHY=m
Updated configs, changing 8812/11/14 driver on all next kernels, removing deprecated patch
2017-10-30 16:10:53 +01:00
CONFIG_REALTEK_PHY=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_RENESAS_PHY is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_ROCKCHIP_PHY=m
CONFIG_SMSC_PHY=m
CONFIG_STE10XP=m
CONFIG_TERANETICS_PHY=m
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_DP83822_PHY is not set
# CONFIG_DP83TC811_PHY is not set
CONFIG_DP83848_PHY=m
# CONFIG_DP83867_PHY is not set
# CONFIG_DP83869_PHY is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_VITESSE_PHY=m
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_XILINX_GMII2RGMII is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MICREL_KS8995MA is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_MDIO_DEVICE=y
CONFIG_MDIO_BUS=y
CONFIG_OF_MDIO=y
CONFIG_MDIO_DEVRES=y
# CONFIG_MDIO_BITBANG is not set
# CONFIG_MDIO_BCM_UNIMAC is not set
# CONFIG_MDIO_HISI_FEMAC is not set
CONFIG_MDIO_I2C=m
# CONFIG_MDIO_MVUSB is not set
# CONFIG_MDIO_MSCC_MIIM is not set
# CONFIG_MDIO_IPQ4019 is not set
# CONFIG_MDIO_IPQ8064 is not set
#
# MDIO Multiplexers
#
# CONFIG_MDIO_BUS_MUX_GPIO is not set
# CONFIG_MDIO_BUS_MUX_MULTIPLEXER is not set
# CONFIG_MDIO_BUS_MUX_MMIOREG is not set
#
# PCS device drivers
#
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_PCS_XPCS=m
CONFIG_PCS_LYNX=m
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# end of PCS device drivers
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_PLIP=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_PPP=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_MPPE=m
CONFIG_PPP_MULTILINK=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_PPPOATM=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_PPPOE=m
CONFIG_PPTP=m
CONFIG_PPPOL2TP=m
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_SLIP=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_SLHC=m
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_USB_NET_DRIVERS=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_USB_RTL8150=m
CONFIG_USB_RTL8152=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_LAN78XX=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_USB_USBNET=m
CONFIG_USB_NET_AX8817X=m
CONFIG_USB_NET_AX88179_178A=m
CONFIG_USB_NET_CDCETHER=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_USB_NET_CDC_EEM=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_USB_NET_CDC_NCM=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_USB_NET_HUAWEI_CDC_NCM=m
CONFIG_USB_NET_CDC_MBIM=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_USB_NET_DM9601 is not set
# CONFIG_USB_NET_SR9700 is not set
# CONFIG_USB_NET_SR9800 is not set
# CONFIG_USB_NET_SMSC75XX is not set
# CONFIG_USB_NET_SMSC95XX is not set
# CONFIG_USB_NET_GL620A is not set
CONFIG_USB_NET_NET1080=m
Re-enable USB_NET_PLUSB in linux-mvebu dev and next Enables use of Prolific USB-to-USB bridges which was only available in default kernel.
2019-01-29 12:09:25 +10:00
CONFIG_USB_NET_PLUSB=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_USB_NET_MCS7830 is not set
CONFIG_USB_NET_RNDIS_HOST=m
CONFIG_USB_NET_CDC_SUBSET_ENABLE=m
CONFIG_USB_NET_CDC_SUBSET=m
# CONFIG_USB_ALI_M5632 is not set
# CONFIG_USB_AN2720 is not set
CONFIG_USB_BELKIN=y
CONFIG_USB_ARMLINUX=y
# CONFIG_USB_EPSON2888 is not set
# CONFIG_USB_KC2190 is not set
CONFIG_USB_NET_ZAURUS=m
# CONFIG_USB_NET_CX82310_ETH is not set
# CONFIG_USB_NET_KALMIA is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_USB_NET_QMI_WWAN=m
CONFIG_USB_HSO=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_USB_NET_INT51X1 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_USB_IPHETH is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_USB_SIERRA_NET=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_USB_VL600 is not set
# CONFIG_USB_NET_CH9200 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_USB_NET_AQC111=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_WLAN=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_WLAN_VENDOR_ADMTEK is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ATH_COMMON=m
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_WLAN_VENDOR_ATH=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_ATH_DEBUG is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_ATH5K=m
# CONFIG_ATH5K_DEBUG is not set
CONFIG_ATH5K_PCI=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ATH9K_HW=m
CONFIG_ATH9K_COMMON=m
CONFIG_ATH9K_BTCOEX_SUPPORT=y
CONFIG_ATH9K=m
CONFIG_ATH9K_PCI=y
# CONFIG_ATH9K_AHB is not set
# CONFIG_ATH9K_DEBUGFS is not set
# CONFIG_ATH9K_DYNACK is not set
# CONFIG_ATH9K_WOW is not set
CONFIG_ATH9K_RFKILL=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_ATH9K_CHANNEL_CONTEXT=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ATH9K_PCOEM=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ATH9K_PCI_NO_EEPROM is not set
Updated configs, changing 8812/11/14 driver on all next kernels, removing deprecated patch
2017-10-30 16:10:53 +01:00
CONFIG_ATH9K_HTC=m
# CONFIG_ATH9K_HTC_DEBUGFS is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_ATH9K_HWRNG=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_CARL9170=m
CONFIG_CARL9170_LEDS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_CARL9170_DEBUGFS is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_CARL9170_WPC=y
CONFIG_CARL9170_HWRNG=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_ATH6KL is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_AR5523=m
CONFIG_WIL6210=m
CONFIG_WIL6210_ISR_COR=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
# CONFIG_WIL6210_DEBUGFS is not set
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
CONFIG_ATH10K=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ATH10K_CE=y
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
CONFIG_ATH10K_PCI=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_ATH10K_SDIO is not set
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_ATH10K_USB=m
Marvell / Solidrun Clearfog next (4.4.6) configuration Docker ready and verbose on/off uboot script addon
2016-03-21 11:36:24 +01:00
# CONFIG_ATH10K_DEBUG is not set
# CONFIG_ATH10K_DEBUGFS is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_WCN36XX is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_ATH11K=m
CONFIG_ATH11K_PCI=m
# CONFIG_ATH11K_DEBUG is not set
# CONFIG_ATH11K_DEBUGFS is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_WLAN_VENDOR_ATMEL is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_WLAN_VENDOR_BROADCOM=y
Clean up and update Clearfog kernel configs
2016-11-19 21:38:54 +03:00
CONFIG_B43=m
CONFIG_B43_BCMA=y
CONFIG_B43_SSB=y
CONFIG_B43_BUSES_BCMA_AND_SSB=y
# CONFIG_B43_BUSES_BCMA is not set
# CONFIG_B43_BUSES_SSB is not set
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_SDIO=y
CONFIG_B43_BCMA_PIO=y
CONFIG_B43_PIO=y
CONFIG_B43_PHY_G=y
CONFIG_B43_PHY_N=y
CONFIG_B43_PHY_LP=y
CONFIG_B43_PHY_HT=y
CONFIG_B43_LEDS=y
CONFIG_B43_HWRNG=y
# CONFIG_B43_DEBUG is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_LEDS=y
CONFIG_B43LEGACY_HWRNG=y
# CONFIG_B43LEGACY_DEBUG is not set
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BRCMUTIL=m
CONFIG_BRCMSMAC=m
CONFIG_BRCMFMAC=m
CONFIG_BRCMFMAC_PROTO_BCDC=y
CONFIG_BRCMFMAC_PROTO_MSGBUF=y
CONFIG_BRCMFMAC_SDIO=y
# CONFIG_BRCMFMAC_USB is not set
CONFIG_BRCMFMAC_PCIE=y
# CONFIG_BRCM_TRACING is not set
# CONFIG_BRCMDBG is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_WLAN_VENDOR_CISCO=y
CONFIG_WLAN_VENDOR_INTEL=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_IPW2100=m
CONFIG_IPW2100_MONITOR=y
# CONFIG_IPW2100_DEBUG is not set
CONFIG_IPW2200=m
CONFIG_IPW2200_MONITOR=y
CONFIG_IPW2200_RADIOTAP=y
CONFIG_IPW2200_PROMISCUOUS=y
CONFIG_IPW2200_QOS=y
# CONFIG_IPW2200_DEBUG is not set
CONFIG_LIBIPW=m
# CONFIG_LIBIPW_DEBUG is not set
CONFIG_IWLEGACY=m
CONFIG_IWL4965=m
CONFIG_IWL3945=m
#
# iwl3945 / iwl4965 Debugging Options
#
# CONFIG_IWLEGACY_DEBUG is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_IWLEGACY_DEBUGFS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of iwl3945 / iwl4965 Debugging Options
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IWLWIFI=m
CONFIG_IWLWIFI_LEDS=y
CONFIG_IWLDVM=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_IWLMVM=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_IWLWIFI_OPMODE_MODULAR=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_IWLWIFI_BCAST_FILTERING is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
#
# Debugging Options
#
# CONFIG_IWLWIFI_DEBUG is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_IWLWIFI_DEBUGFS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Debugging Options
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_WLAN_VENDOR_INTERSIL is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_WLAN_VENDOR_MARVELL=y
# CONFIG_LIBERTAS is not set
# CONFIG_LIBERTAS_THINFIRM is not set
CONFIG_MWIFIEX=m
CONFIG_MWIFIEX_SDIO=m
# CONFIG_MWIFIEX_PCIE is not set
# CONFIG_MWIFIEX_USB is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_MWL8K=m
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_WLAN_VENDOR_MEDIATEK=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_MT7601U=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MT76_CORE=m
CONFIG_MT76_LEDS=y
CONFIG_MT76_USB=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MT76x02_LIB=m
CONFIG_MT76x02_USB=m
CONFIG_MT76x0_COMMON=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MT76x0U=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MT76x0E=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MT76x2_COMMON=m
CONFIG_MT76x2E=m
CONFIG_MT76x2U=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_MT7603E is not set
# CONFIG_MT7615E is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MT7663U is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_MT7663S is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MT7915E is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
CONFIG_WLAN_VENDOR_MICROCHIP=y
# CONFIG_WILC1000_SDIO is not set
# CONFIG_WILC1000_SPI is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_WLAN_VENDOR_RALINK=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_RT2X00=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_RT2400PCI=m
CONFIG_RT2500PCI=m
CONFIG_RT61PCI=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_RT2800PCI=m
CONFIG_RT2800PCI_RT33XX=y
CONFIG_RT2800PCI_RT35XX=y
CONFIG_RT2800PCI_RT53XX=y
CONFIG_RT2800PCI_RT3290=y
CONFIG_RT2500USB=m
CONFIG_RT73USB=m
CONFIG_RT2800USB=m
CONFIG_RT2800USB_RT33XX=y
CONFIG_RT2800USB_RT35XX=y
Updated configs, changing 8812/11/14 driver on all next kernels, removing deprecated patch
2017-10-30 16:10:53 +01:00
CONFIG_RT2800USB_RT3573=y
CONFIG_RT2800USB_RT53XX=y
CONFIG_RT2800USB_RT55XX=y
CONFIG_RT2800USB_UNKNOWN=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_RT2800_LIB=m
CONFIG_RT2800_LIB_MMIO=m
CONFIG_RT2X00_LIB_MMIO=m
CONFIG_RT2X00_LIB_PCI=m
CONFIG_RT2X00_LIB_USB=m
CONFIG_RT2X00_LIB=m
CONFIG_RT2X00_LIB_FIRMWARE=y
CONFIG_RT2X00_LIB_CRYPTO=y
CONFIG_RT2X00_LIB_LEDS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_RT2X00_LIB_DEBUGFS is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_RT2X00_DEBUG is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_WLAN_VENDOR_REALTEK=y
Updated configs, changing 8812/11/14 driver on all next kernels, removing deprecated patch
2017-10-30 16:10:53 +01:00
CONFIG_RTL8180=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_RTL8187=m
CONFIG_RTL8187_LEDS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_RTL_CARDS=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_RTL8192CE=m
CONFIG_RTL8192SE=m
CONFIG_RTL8192DE=m
CONFIG_RTL8723AE=m
CONFIG_RTL8723BE=m
CONFIG_RTL8188EE=m
CONFIG_RTL8192EE=m
CONFIG_RTL8821AE=m
CONFIG_RTL8192CU=m
CONFIG_RTLWIFI=m
CONFIG_RTLWIFI_PCI=m
CONFIG_RTLWIFI_USB=m
# CONFIG_RTLWIFI_DEBUG is not set
CONFIG_RTL8192C_COMMON=m
CONFIG_RTL8723_COMMON=m
CONFIG_RTLBTCOEXIST=m
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
CONFIG_RTL8XXXU=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_RTL8XXXU_UNTESTED is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RTW88=m
Fix wireless problems
2020-09-30 15:43:31 +02:00
CONFIG_RTW88_CORE=m
CONFIG_RTW88_PCI=m
CONFIG_RTW88_8822B=m
CONFIG_RTW88_8822C=m
CONFIG_RTW88_8723D=m
CONFIG_RTW88_8822BE=m
CONFIG_RTW88_8822CE=m
CONFIG_RTW88_8723DE=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_RTW88_8821CE is not set
Fix wireless problems
2020-09-30 15:43:31 +02:00
# CONFIG_RTW88_DEBUG is not set
# CONFIG_RTW88_DEBUGFS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_WLAN_VENDOR_RSI=y
# CONFIG_RSI_91X is not set
CONFIG_WLAN_VENDOR_ST=y
# CONFIG_CW1200 is not set
CONFIG_WLAN_VENDOR_TI=y
# CONFIG_WL1251 is not set
# CONFIG_WL12XX is not set
# CONFIG_WL18XX is not set
# CONFIG_WLCORE is not set
CONFIG_RTL8723DU=m
Enable RTL8723DS for all kernels Driver troubles were fixed upstream and now it builds everywhere Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
2020-05-03 11:35:37 +02:00
CONFIG_RTL8723DS=m
Changes to build script and patches adjustment (#1423) - change console welcome text - changed display manager to lightdm by default and remove nodm completly - desktop login manager enabled by default, toogle can be done with armbian-config - added URL to the build script and commit hash to /etc/armbian-release file - added debconf-utils,html2text,mmc-utils,sunxi-tools to the base and additional pkg list - added synaptic package manager and onboard keyboard to the desktop base - changed motd console welcome text to: Welcome to Debian Stretch with Armbian Linux 5.1.6-sunxi - added "logout" to the panel/menu - added normal users to additional groups: disk tty users games * Adjust tabs and alter displaying build options at the end - hide empty ones * Fix wrong MOTD message, adjust logic to autologin by default and request login for both notebooks * Making fs cache naming more intuitive, rename script * Move additional kernel drivers into separate file. Add AUFS for K5.1 this way, attach wireguard sources to last known working tag. master is broken atm * Add two more extra wireless drivers 88x2BU, (improved) 8811EU and introduce switch EXTRAWIFI which is enabled by default * Move 8812AU to the same version we have now. More recent has some performance issues in AP mode. Adjust configuration, add mvebut-dev 5.1.y kernel * Enable Wireguard also on 3.10.y since it was fixed upstream. Attach bach to master branch since its working now * Rockchip64 & RK3399 - upstream patches and remove deprecated patches, mvebu64 add DEV kernel attached to 5.1.y * Enable BT on Tinkerboard CLI images as well * cubox-i move to 5.1.y and enable missing HDMI * Bugfixes for adding wireless driver to Kconfig. Adjusted RK3399 kernel due to upstream changes at FriendlyARM - does not boot yet. Changes has to be extract from their commits. Removed patches with RTL8188EU since we add more recent driver with a new precedure. Small fixes mvebu-default, udoo-next, s56818-next, ... remove deprecated patches. * Boot-able RK3399-default config, add upstream patches for K4.4.y mvebu-default/udoo-next * Adjust overclocking patch to meet upstream changes * Odroid XU4 - remove deprecated kernel patches
2019-06-26 07:31:11 +02:00
CONFIG_RTL8822BU=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_RTL8821CU=m
[ mvebu ] Update kernel configurations
2020-03-02 21:05:26 +01:00
CONFIG_88XXAU=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_RTL8192EU is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_RTL8189FS=m
CONFIG_RTL8189ES=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_WLAN_VENDOR_ZYDAS=y
CONFIG_USB_ZD1201=m
CONFIG_ZD1211RW=m
# CONFIG_ZD1211RW_DEBUG is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_WLAN_VENDOR_QUANTENNA=y
Fix wireless problems
2020-09-30 15:43:31 +02:00
CONFIG_QTNFMAC=m
CONFIG_QTNFMAC_PCIE=m
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_MAC80211_HWSIM is not set
Fix wireless problems
2020-09-30 15:43:31 +02:00
CONFIG_USB_NET_RNDIS_WLAN=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_VIRT_WIFI=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# WiMAX Wireless Broadband devices
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_WIMAX_I2400M=m
CONFIG_WIMAX_I2400M_USB=m
CONFIG_WIMAX_I2400M_DEBUG_LEVEL=8
# end of WiMAX Wireless Broadband devices
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_WAN is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_IEEE802154_DRIVERS=m
CONFIG_IEEE802154_FAKELB=m
CONFIG_IEEE802154_AT86RF230=m
# CONFIG_IEEE802154_AT86RF230_DEBUGFS is not set
CONFIG_IEEE802154_MRF24J40=m
CONFIG_IEEE802154_CC2520=m
CONFIG_IEEE802154_ATUSB=m
CONFIG_IEEE802154_ADF7242=m
CONFIG_IEEE802154_CA8210=m
# CONFIG_IEEE802154_CA8210_DEBUGFS is not set
CONFIG_IEEE802154_MCR20A=m
CONFIG_IEEE802154_HWSIM=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_VMXNET3 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_NETDEVSIM is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NET_FAILOVER=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ISDN is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
CONFIG_NVM=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_NVM_PBLK is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Input device support
#
CONFIG_INPUT=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_INPUT_LEDS=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_INPUT_FF_MEMLESS=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_INPUT_POLLDEV=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_INPUT_SPARSEKMAP is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_INPUT_MATRIXKMAP=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
add gamepad and joystick support where missing (#2446) * [rockchip64-current] add gamepad and joystick support Added modules similar to rockchip64-legacy * [meson{64}-current] add gamepad and joystick support * [gitignore] temp vim files * [sunxi{64}-current] add gamepad and joystick support * [mvebu{64}-current] add gamepad and joystick support * [misc dev] add gamepad and joystick support * [meson and sunxi legacy] add gamepad and joystick support * [misc legacy] add gamepad and joystick support
2020-12-14 22:44:14 +05:30
CONFIG_INPUT_JOYDEV=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_KEYBOARD_ADC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_KEYBOARD_ADP5588 is not set
# CONFIG_KEYBOARD_ADP5589 is not set
CONFIG_KEYBOARD_ATKBD=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_KEYBOARD_QT1050=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_KEYBOARD_QT1070 is not set
# CONFIG_KEYBOARD_QT2160 is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_KEYBOARD_DLINK_DIR685 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_KEYBOARD_LKKBD is not set
CONFIG_KEYBOARD_GPIO=y
# CONFIG_KEYBOARD_GPIO_POLLED is not set
# CONFIG_KEYBOARD_TCA6416 is not set
# CONFIG_KEYBOARD_TCA8418 is not set
# CONFIG_KEYBOARD_MATRIX is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_KEYBOARD_LM8323 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_KEYBOARD_LM8333 is not set
# CONFIG_KEYBOARD_MAX7359 is not set
# CONFIG_KEYBOARD_MCS is not set
# CONFIG_KEYBOARD_MPR121 is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_OPENCORES is not set
# CONFIG_KEYBOARD_SAMSUNG is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_OMAP4 is not set
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_KEYBOARD_TM2_TOUCHKEY is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_CAP11XX is not set
# CONFIG_KEYBOARD_BCM is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_MOUSE_PS2_BYD=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MOUSE_PS2_CYPRESS=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_ELANTECH is not set
# CONFIG_MOUSE_PS2_SENTELIC is not set
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
CONFIG_MOUSE_PS2_FOCALTECH=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_MOUSE_PS2_SMBUS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_BCM5974 is not set
# CONFIG_MOUSE_CYAPA is not set
# CONFIG_MOUSE_ELAN_I2C is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_MOUSE_GPIO is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_USB is not set
add gamepad and joystick support where missing (#2446) * [rockchip64-current] add gamepad and joystick support Added modules similar to rockchip64-legacy * [meson{64}-current] add gamepad and joystick support * [gitignore] temp vim files * [sunxi{64}-current] add gamepad and joystick support * [mvebu{64}-current] add gamepad and joystick support * [misc dev] add gamepad and joystick support * [meson and sunxi legacy] add gamepad and joystick support * [misc legacy] add gamepad and joystick support
2020-12-14 22:44:14 +05:30
CONFIG_INPUT_JOYSTICK=y
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_JOYSTICK_ADC=m
add gamepad and joystick support where missing (#2446) * [rockchip64-current] add gamepad and joystick support Added modules similar to rockchip64-legacy * [meson{64}-current] add gamepad and joystick support * [gitignore] temp vim files * [sunxi{64}-current] add gamepad and joystick support * [mvebu{64}-current] add gamepad and joystick support * [misc dev] add gamepad and joystick support * [meson and sunxi legacy] add gamepad and joystick support * [misc legacy] add gamepad and joystick support
2020-12-14 22:44:14 +05:30
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
CONFIG_JOYSTICK_IFORCE=m
CONFIG_JOYSTICK_IFORCE_USB=m
# CONFIG_JOYSTICK_IFORCE_232 is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDJOY is not set
# CONFIG_JOYSTICK_ZHENHUA is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_JOYSTICK_DB9=m
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_JOYSTICK_GAMECON is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_JOYSTICK_TURBOGRAFX=m
add gamepad and joystick support where missing (#2446) * [rockchip64-current] add gamepad and joystick support Added modules similar to rockchip64-legacy * [meson{64}-current] add gamepad and joystick support * [gitignore] temp vim files * [sunxi{64}-current] add gamepad and joystick support * [mvebu{64}-current] add gamepad and joystick support * [misc dev] add gamepad and joystick support * [meson and sunxi legacy] add gamepad and joystick support * [misc legacy] add gamepad and joystick support
2020-12-14 22:44:14 +05:30
# CONFIG_JOYSTICK_AS5011 is not set
# CONFIG_JOYSTICK_JOYDUMP is not set
CONFIG_JOYSTICK_XPAD=m
CONFIG_JOYSTICK_XPAD_FF=y
CONFIG_JOYSTICK_XPAD_LEDS=y
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_JOYSTICK_WALKERA0701=m
add gamepad and joystick support where missing (#2446) * [rockchip64-current] add gamepad and joystick support Added modules similar to rockchip64-legacy * [meson{64}-current] add gamepad and joystick support * [gitignore] temp vim files * [sunxi{64}-current] add gamepad and joystick support * [mvebu{64}-current] add gamepad and joystick support * [misc dev] add gamepad and joystick support * [meson and sunxi legacy] add gamepad and joystick support * [misc legacy] add gamepad and joystick support
2020-12-14 22:44:14 +05:30
# CONFIG_JOYSTICK_PSXPAD_SPI is not set
# CONFIG_JOYSTICK_PXRC is not set
# CONFIG_JOYSTICK_FSIA6B is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_RMI4_CORE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_SERPORT=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SERIO_PARKBD=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_SERIO_ALTERA_PS2 is not set
# CONFIG_SERIO_PS2MULT is not set
# CONFIG_SERIO_ARC_PS2 is not set
# CONFIG_SERIO_APBPS2 is not set
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
# CONFIG_SERIO_GPIO_PS2 is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
CONFIG_USERIO=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GAMEPORT is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Hardware I/O ports
# end of Input device support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Character devices
#
CONFIG_TTY=y
CONFIG_VT=y
CONFIG_CONSOLE_TRANSLATIONS=y
CONFIG_VT_CONSOLE=y
CONFIG_VT_CONSOLE_SLEEP=y
CONFIG_HW_CONSOLE=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_VT_HW_CONSOLE_BINDING=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_UNIX98_PTYS=y
config: follow debian disable legacy ptys (#1561) Signed-off-by: Zhang Ning <832666+zhangn1985@users.noreply.github.com>
2019-09-17 04:14:09 +08:00
# CONFIG_LEGACY_PTYS is not set
[ general ] update kernel configs due to upstream changes
2019-04-17 11:41:23 +02:00
CONFIG_LDISC_AUTOLOAD=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Serial drivers
#
CONFIG_SERIAL_EARLYCON=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_DEPRECATED_OPTIONS=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_SERIAL_8250_16550A_VARIANTS=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
# CONFIG_SERIAL_8250_FINTEK is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_DMA=y
CONFIG_SERIAL_8250_PCI=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_SERIAL_8250_EXAR is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_RUNTIME_UARTS=4
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
Bugfix: adjust mvebu-current kernel config It boots up properly now @boards-marvell Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
2020-04-29 12:27:29 +02:00
# CONFIG_SERIAL_8250_ASPEED_VUART is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_RSA=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_SERIAL_8250_DWLIB=y
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
CONFIG_SERIAL_8250_FSL=y
Bugfix: adjust mvebu-current kernel config It boots up properly now @boards-marvell Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
2020-04-29 12:27:29 +02:00
CONFIG_SERIAL_8250_DW=y
# CONFIG_SERIAL_8250_EM is not set
# CONFIG_SERIAL_8250_RT288X is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_SERIAL_OF_PLATFORM=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Non-8250 serial port support
#
# CONFIG_SERIAL_EARLYCON_ARM_SEMIHOST is not set
# CONFIG_SERIAL_MAX3100 is not set
# CONFIG_SERIAL_MAX310X is not set
# CONFIG_SERIAL_UARTLITE is not set
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
# CONFIG_SERIAL_JSM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_SERIAL_SIFIVE=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SERIAL_SCCNXP is not set
# CONFIG_SERIAL_SC16IS7XX is not set
# CONFIG_SERIAL_BCM63XX is not set
# CONFIG_SERIAL_ALTERA_JTAGUART is not set
# CONFIG_SERIAL_ALTERA_UART is not set
# CONFIG_SERIAL_IFX6X60 is not set
# CONFIG_SERIAL_XILINX_PS_UART is not set
# CONFIG_SERIAL_ARC is not set
# CONFIG_SERIAL_RP2 is not set
# CONFIG_SERIAL_FSL_LPUART is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_SERIAL_FSL_LINFLEXUART is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SERIAL_CONEXANT_DIGICOLOR is not set
# CONFIG_SERIAL_ST_ASC is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SERIAL_SPRD is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_SERIAL_MVEBU_UART=y
CONFIG_SERIAL_MVEBU_CONSOLE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Serial drivers
CONFIG_SERIAL_MCTRL_GPIO=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_SYNCLINK_GT is not set
# CONFIG_ISI is not set
# CONFIG_N_HDLC is not set
# CONFIG_N_GSM is not set
# CONFIG_NOZOMI is not set
CONFIG_NULL_TTY=m
# CONFIG_TRACE_SINK is not set
CONFIG_HVC_DRIVER=y
# CONFIG_HVC_DCC is not set
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_SERIAL_DEV_BUS=y
CONFIG_SERIAL_DEV_CTRL_TTYPORT=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
CONFIG_PPDEV=m
CONFIG_VIRTIO_CONSOLE=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_IPMI_HANDLER is not set
CONFIG_HW_RANDOM=m
# CONFIG_HW_RANDOM_TIMERIOMEM is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_HW_RANDOM_BA431 is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_HW_RANDOM_OMAP is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HW_RANDOM_VIRTIO=m
CONFIG_HW_RANDOM_OPTEE=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_HW_RANDOM_CCTRNG is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_HW_RANDOM_XIPHERA=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_APPLICOM is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_DEVMEM=y
CONFIG_DEVKMEM=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RAW_DRIVER is not set
CONFIG_DEVPORT=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_TCG_TPM is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_XILLYBUS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Character devices
# CONFIG_RANDOM_TRUST_BOOTLOADER is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# I2C support
#
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_I2C_MUX=y
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# Multiplexer I2C Chip support
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_I2C_ARB_GPIO_CHALLENGE=m
CONFIG_I2C_MUX_GPIO=m
CONFIG_I2C_MUX_GPMUX=m
CONFIG_I2C_MUX_LTC4306=m
CONFIG_I2C_MUX_PCA9541=m
CONFIG_I2C_MUX_PCA954x=m
CONFIG_I2C_MUX_PINCTRL=m
CONFIG_I2C_MUX_REG=m
CONFIG_I2C_DEMUX_PINCTRL=m
CONFIG_I2C_MUX_MLXCPLD=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Multiplexer I2C Chip support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_I2C_HELPER_AUTO=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_I2C_SMBUS=m
CONFIG_I2C_ALGOBIT=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
# CONFIG_I2C_AMD756 is not set
# CONFIG_I2C_AMD8111 is not set
# CONFIG_I2C_I801 is not set
# CONFIG_I2C_ISCH is not set
# CONFIG_I2C_PIIX4 is not set
# CONFIG_I2C_NFORCE2 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_I2C_NVIDIA_GPU=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set
#
# I2C system bus drivers (mostly embedded / system-on-chip)
#
# CONFIG_I2C_CBUS_GPIO is not set
# CONFIG_I2C_DESIGNWARE_PLATFORM is not set
# CONFIG_I2C_DESIGNWARE_PCI is not set
# CONFIG_I2C_EMEV2 is not set
# CONFIG_I2C_GPIO is not set
CONFIG_I2C_MV64XXX=y
# CONFIG_I2C_OCORES is not set
# CONFIG_I2C_PCA_PLATFORM is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_I2C_PXA is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_I2C_RK3X is not set
# CONFIG_I2C_SIMTEC is not set
# CONFIG_I2C_XILINX is not set
#
# External I2C/SMBus adapter drivers
#
# CONFIG_I2C_DIOLAN_U2C is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_I2C_PARPORT=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_I2C_ROBOTFUZZ_OSIF is not set
# CONFIG_I2C_TAOS_EVM is not set
# CONFIG_I2C_TINY_USB is not set
#
# Other I2C/SMBus bus drivers
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_I2C_FSI=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of I2C Hardware Bus support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_I2C_STUB is not set
# CONFIG_I2C_SLAVE is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of I2C support
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_I3C=m
CONFIG_CDNS_I3C_MASTER=m
CONFIG_DW_I3C_MASTER=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SPI=y
Enable minimal kernel debug info - Enable KGDB support - Enable earlycon and earlyprintk support
2017-12-30 16:50:10 +08:00
# CONFIG_SPI_DEBUG is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SPI_MASTER=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SPI_MEM=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# SPI Master Controller Drivers
#
# CONFIG_SPI_ALTERA is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_SPI_ARMADA_3700=y
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_SPI_AXI_SPI_ENGINE is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SPI_BITBANG=m
CONFIG_SPI_BUTTERFLY=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SPI_CADENCE is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_SPI_CADENCE_QUADSPI is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_SPI_DESIGNWARE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SPI_FSI is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_SPI_NXP_FLEXSPI is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SPI_GPIO is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SPI_LM70_LLP=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SPI_FSL_SPI is not set
# CONFIG_SPI_OC_TINY is not set
CONFIG_SPI_ORION=y
# CONFIG_SPI_PXA2XX is not set
# CONFIG_SPI_ROCKCHIP is not set
# CONFIG_SPI_SC18IS602 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_SPI_SIFIVE is not set
# CONFIG_SPI_MXIC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SPI_XCOMM is not set
# CONFIG_SPI_XILINX is not set
# CONFIG_SPI_ZYNQMP_GQSPI is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SPI_AMD is not set
#
# SPI Multiplexer support
#
# CONFIG_SPI_MUX is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# SPI Protocol Masters
#
# CONFIG_SPI_SPIDEV is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_SPI_LOOPBACK_TEST is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SPI_TLE62X0 is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_SPI_SLAVE=y
# CONFIG_SPI_SLAVE_TIME is not set
# CONFIG_SPI_SLAVE_SYSTEM_CONTROL is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_SPI_DYNAMIC=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SPMI is not set
# CONFIG_HSI is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_PPS=m
# CONFIG_PPS_DEBUG is not set
# CONFIG_NTP_PPS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# PPS clients support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_PPS_CLIENT_KTIMER is not set
[ kernels general ] Support PPS via GPIO and Serial as LKM, add to https://github.com/armbian/build/pull/1349
2019-04-16 21:22:50 +02:00
CONFIG_PPS_CLIENT_LDISC=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_PPS_CLIENT_PARPORT=m
[ kernels general ] Support PPS via GPIO and Serial as LKM, add to https://github.com/armbian/build/pull/1349
2019-04-16 21:22:50 +02:00
CONFIG_PPS_CLIENT_GPIO=m
[ general ] update kernel configs due to upstream changes
2019-04-17 11:41:23 +02:00
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# PPS generators support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# PTP clock support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_PTP_1588_CLOCK=m
CONFIG_DP83640_PHY=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PTP_1588_CLOCK_INES is not set
# CONFIG_PTP_1588_CLOCK_IDT82P33 is not set
# CONFIG_PTP_1588_CLOCK_IDTCM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of PTP clock support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_PINCTRL=y
CONFIG_PINMUX=y
CONFIG_PINCONF=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_GENERIC_PINCONF=y
Enable minimal kernel debug info - Enable KGDB support - Enable earlycon and earlyprintk support
2017-12-30 16:50:10 +08:00
# CONFIG_DEBUG_PINCTRL is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_PINCTRL_MCP23S08 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_PINCTRL_SINGLE is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_PINCTRL_SX150X is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_PINCTRL_STMFX=m
# CONFIG_PINCTRL_OCELOT is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_PINCTRL_MVEBU=y
CONFIG_PINCTRL_DOVE=y
CONFIG_PINCTRL_ARMADA_370=y
CONFIG_PINCTRL_ARMADA_375=y
CONFIG_PINCTRL_ARMADA_38X=y
CONFIG_PINCTRL_ARMADA_39X=y
CONFIG_PINCTRL_ARMADA_XP=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
#
# Renesas pinctrl drivers
#
# end of Renesas pinctrl drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ARCH_HAVE_CUSTOM_GPIO_H=y
CONFIG_GPIOLIB=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_GPIOLIB_FASTPATH_LIMIT=512
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_OF_GPIO=y
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_GPIOLIB_IRQCHIP=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_DEBUG_GPIO is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_GPIO_SYSFS=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_GPIO_CDEV=y
CONFIG_GPIO_CDEV_V1=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_GPIO_GENERIC=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_GPIO_MAX730X=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Memory mapped GPIO drivers
#
# CONFIG_GPIO_74XX_MMIO is not set
# CONFIG_GPIO_ALTERA is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_GPIO_CADENCE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GPIO_DWAPB is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_GPIO_FTGPIO010 is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_GPIO_GENERIC_PLATFORM=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GPIO_GRGPIO is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_GPIO_HLWD is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_GPIO_LOGICVC is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_GPIO_MB86S7X is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_GPIO_MPC8XXX is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_GPIO_MVEBU=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_GPIO_SAMA5D2_PIOBU is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_GPIO_SIFIVE is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_GPIO_SYSCON=y
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_GPIO_XILINX is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GPIO_ZEVIO is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_GPIO_AMD_FCH is not set
# end of Memory mapped GPIO drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# I2C GPIO expanders
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_GPIO_ADP5588=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GPIO_ADNP is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_GPIO_GW_PLD is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GPIO_MAX7300 is not set
# CONFIG_GPIO_MAX732X is not set
CONFIG_GPIO_PCA953X=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_GPIO_PCA953X_IRQ=y
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_GPIO_PCA9570 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GPIO_PCF857X is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_GPIO_TPIC2810 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of I2C GPIO expanders
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# MFD GPIO expanders
#
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_HTC_EGPIO is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_GPIO_MAX77650=m
CONFIG_GPIO_TQMX86=m
# end of MFD GPIO expanders
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# PCI GPIO expanders
#
# CONFIG_GPIO_BT8XX is not set
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_GPIO_PCI_IDIO_16 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_GPIO_PCIE_IDIO_24=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GPIO_RDC321X is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of PCI GPIO expanders
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# SPI GPIO expanders
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_GPIO_74X164=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_GPIO_MAX3191X=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_GPIO_MAX7301=m
CONFIG_GPIO_MC33880=m
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_GPIO_PISOSR=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_GPIO_XRA1403=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of SPI GPIO expanders
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# USB GPIO expanders
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of USB GPIO expanders
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_GPIO_AGGREGATOR is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_GPIO_MOCKUP is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_W1=m
#
# 1-wire Bus Masters
#
# CONFIG_W1_MASTER_MATROX is not set
CONFIG_W1_MASTER_DS2490=m
CONFIG_W1_MASTER_DS2482=m
CONFIG_W1_MASTER_DS1WM=m
CONFIG_W1_MASTER_GPIO=m
CONFIG_W1_MASTER_SGI=m
# end of 1-wire Bus Masters
#
# 1-wire Slaves
#
CONFIG_W1_SLAVE_THERM=m
CONFIG_W1_SLAVE_SMEM=m
CONFIG_W1_SLAVE_DS2405=m
CONFIG_W1_SLAVE_DS2408=m
CONFIG_W1_SLAVE_DS2408_READBACK=y
CONFIG_W1_SLAVE_DS2413=m
CONFIG_W1_SLAVE_DS2406=m
CONFIG_W1_SLAVE_DS2423=m
CONFIG_W1_SLAVE_DS2805=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_W1_SLAVE_DS2430 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_W1_SLAVE_DS2431=m
CONFIG_W1_SLAVE_DS2433=m
# CONFIG_W1_SLAVE_DS2433_CRC is not set
CONFIG_W1_SLAVE_DS2438=m
CONFIG_W1_SLAVE_DS250X=m
CONFIG_W1_SLAVE_DS2780=m
CONFIG_W1_SLAVE_DS2781=m
CONFIG_W1_SLAVE_DS28E04=m
CONFIG_W1_SLAVE_DS28E17=m
# end of 1-wire Slaves
CONFIG_POWER_RESET=y
# CONFIG_POWER_RESET_BRCMKONA is not set
# CONFIG_POWER_RESET_BRCMSTB is not set
# CONFIG_POWER_RESET_GPIO is not set
# CONFIG_POWER_RESET_GPIO_RESTART is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_POWER_RESET_LINKSTATION is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_POWER_RESET_LTC2952 is not set
# CONFIG_POWER_RESET_QNAP is not set
# CONFIG_POWER_RESET_RESTART is not set
CONFIG_POWER_RESET_VERSATILE=y
CONFIG_POWER_RESET_SYSCON=y
CONFIG_POWER_RESET_SYSCON_POWEROFF=y
CONFIG_REBOOT_MODE=y
CONFIG_SYSCON_REBOOT_MODE=y
# CONFIG_NVMEM_REBOOT_MODE is not set
CONFIG_POWER_SUPPLY=y
# CONFIG_POWER_SUPPLY_DEBUG is not set
CONFIG_POWER_SUPPLY_HWMON=y
CONFIG_PDA_POWER=m
CONFIG_GENERIC_ADC_BATTERY=m
CONFIG_TEST_POWER=m
CONFIG_CHARGER_ADP5061=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BATTERY_CW2015 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BATTERY_DS2760=m
CONFIG_BATTERY_DS2780=m
CONFIG_BATTERY_DS2781=m
CONFIG_BATTERY_DS2782=m
CONFIG_BATTERY_SBS=m
CONFIG_CHARGER_SBS=m
CONFIG_MANAGER_SBS=m
CONFIG_BATTERY_BQ27XXX=m
CONFIG_BATTERY_BQ27XXX_I2C=m
CONFIG_BATTERY_BQ27XXX_HDQ=m
# CONFIG_BATTERY_BQ27XXX_DT_UPDATES_NVM is not set
CONFIG_BATTERY_MAX17040=m
CONFIG_BATTERY_MAX17042=m
CONFIG_BATTERY_MAX1721X=m
CONFIG_CHARGER_ISP1704=m
CONFIG_CHARGER_MAX8903=m
CONFIG_CHARGER_LP8727=m
CONFIG_CHARGER_GPIO=m
CONFIG_CHARGER_MANAGER=y
CONFIG_CHARGER_LT3651=m
CONFIG_CHARGER_DETECTOR_MAX14656=m
CONFIG_CHARGER_MAX77650=m
CONFIG_CHARGER_BQ2415X=m
CONFIG_CHARGER_BQ24190=m
CONFIG_CHARGER_BQ24257=m
CONFIG_CHARGER_BQ24735=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_CHARGER_BQ2515X is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CHARGER_BQ25890=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_CHARGER_BQ25980=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CHARGER_SMB347=m
CONFIG_BATTERY_GAUGE_LTC2941=m
CONFIG_CHARGER_RT9455=m
CONFIG_CHARGER_UCS1002=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_CHARGER_BD99954 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HWMON=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HWMON_VID=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HWMON_DEBUG_CHIP is not set
#
# Native drivers
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_AD7314=m
CONFIG_SENSORS_AD7414=m
CONFIG_SENSORS_AD7418=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
CONFIG_SENSORS_ADM1026=m
CONFIG_SENSORS_ADM1029=m
CONFIG_SENSORS_ADM1031=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_ADM1177 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_ADM9240=m
CONFIG_SENSORS_ADT7X10=m
CONFIG_SENSORS_ADT7310=m
CONFIG_SENSORS_ADT7410=m
CONFIG_SENSORS_ADT7411=m
CONFIG_SENSORS_ADT7462=m
CONFIG_SENSORS_ADT7470=m
CONFIG_SENSORS_ADT7475=m
CONFIG_SENSORS_AS370=m
CONFIG_SENSORS_ASC7621=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_AXI_FAN_CONTROL is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_ASPEED=m
CONFIG_SENSORS_ATXP1=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_SENSORS_CORSAIR_CPRO is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_DRIVETEMP is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_DS620=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_I5K_AMB=m
CONFIG_SENSORS_F71805F=m
CONFIG_SENSORS_F71882FG=m
CONFIG_SENSORS_F75375S=m
CONFIG_SENSORS_FTSTEUTATES=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_G760A=m
CONFIG_SENSORS_G762=m
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_SENSORS_GPIO_FAN=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_HIH6130=m
CONFIG_SENSORS_IIO_HWMON=m
CONFIG_SENSORS_IT87=m
CONFIG_SENSORS_JC42=m
CONFIG_SENSORS_POWR1220=m
CONFIG_SENSORS_LINEAGE=m
CONFIG_SENSORS_LTC2945=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_LTC2947_I2C is not set
# CONFIG_SENSORS_LTC2947_SPI is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_SENSORS_LTC2990=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_LTC4151=m
CONFIG_SENSORS_LTC4215=m
CONFIG_SENSORS_LTC4222=m
CONFIG_SENSORS_LTC4245=m
CONFIG_SENSORS_LTC4260=m
CONFIG_SENSORS_LTC4261=m
CONFIG_SENSORS_MAX1111=m
CONFIG_SENSORS_MAX16065=m
CONFIG_SENSORS_MAX1619=m
CONFIG_SENSORS_MAX1668=m
CONFIG_SENSORS_MAX197=m
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_SENSORS_MAX31722=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_MAX31730 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SENSORS_MAX6621=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_MAX6639=m
CONFIG_SENSORS_MAX6642=m
CONFIG_SENSORS_MAX6650=m
CONFIG_SENSORS_MAX6697=m
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
CONFIG_SENSORS_MAX31790=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_MCP3021=m
CONFIG_SENSORS_TC654=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_SENSORS_MR75203=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_ADCXX=m
CONFIG_SENSORS_LM63=m
CONFIG_SENSORS_LM70=m
CONFIG_SENSORS_LM73=m
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_SENSORS_LM75=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
CONFIG_SENSORS_LM87=m
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_LM92=m
CONFIG_SENSORS_LM93=m
CONFIG_SENSORS_LM95234=m
CONFIG_SENSORS_LM95241=m
CONFIG_SENSORS_LM95245=m
CONFIG_SENSORS_PC87360=m
CONFIG_SENSORS_PC87427=m
CONFIG_SENSORS_NTC_THERMISTOR=m
CONFIG_SENSORS_NCT6683=m
CONFIG_SENSORS_NCT6775=m
CONFIG_SENSORS_NCT7802=m
CONFIG_SENSORS_NCT7904=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SENSORS_NPCM7XX=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_OCC_P8_I2C=m
CONFIG_SENSORS_OCC=m
CONFIG_SENSORS_PCF8591=m
CONFIG_PMBUS=m
CONFIG_SENSORS_PMBUS=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_SENSORS_ADM1266=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_ADM1275=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_BEL_PFE is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_IBM_CFFPS=m
CONFIG_SENSORS_INSPUR_IPSPS=m
CONFIG_SENSORS_IR35221=m
CONFIG_SENSORS_IR38064=m
# CONFIG_SENSORS_IRPS5401 is not set
CONFIG_SENSORS_ISL68137=m
CONFIG_SENSORS_LM25066=m
# CONFIG_SENSORS_LTC2978 is not set
CONFIG_SENSORS_LTC3815=m
CONFIG_SENSORS_MAX16064=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_MAX16601 is not set
# CONFIG_SENSORS_MAX20730 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_MAX20751=m
CONFIG_SENSORS_MAX31785=m
CONFIG_SENSORS_MAX34440=m
CONFIG_SENSORS_MAX8688=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_SENSORS_MP2975=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_PXE1610=m
CONFIG_SENSORS_TPS40422=m
CONFIG_SENSORS_TPS53679=m
CONFIG_SENSORS_UCD9000=m
CONFIG_SENSORS_UCD9200=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_XDPE122 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_ZL6100=m
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_SENSORS_PWM_FAN=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_SHT15=m
CONFIG_SENSORS_SHT21=m
CONFIG_SENSORS_SHT3x=m
CONFIG_SENSORS_SHTC1=m
CONFIG_SENSORS_SIS5595=m
CONFIG_SENSORS_DME1737=m
CONFIG_SENSORS_EMC1403=m
CONFIG_SENSORS_EMC2103=m
CONFIG_SENSORS_EMC6W201=m
CONFIG_SENSORS_SMSC47M1=m
CONFIG_SENSORS_SMSC47M192=m
CONFIG_SENSORS_SMSC47B397=m
CONFIG_SENSORS_SCH56XX_COMMON=m
CONFIG_SENSORS_SCH5627=m
CONFIG_SENSORS_SCH5636=m
CONFIG_SENSORS_STTS751=m
CONFIG_SENSORS_SMM665=m
CONFIG_SENSORS_ADC128D818=m
CONFIG_SENSORS_ADS7828=m
CONFIG_SENSORS_ADS7871=m
CONFIG_SENSORS_AMC6821=m
CONFIG_SENSORS_INA209=m
CONFIG_SENSORS_INA2XX=m
CONFIG_SENSORS_INA3221=m
CONFIG_SENSORS_TC74=m
CONFIG_SENSORS_THMC50=m
CONFIG_SENSORS_TMP102=m
CONFIG_SENSORS_TMP103=m
CONFIG_SENSORS_TMP108=m
CONFIG_SENSORS_TMP401=m
CONFIG_SENSORS_TMP421=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SENSORS_TMP513 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_VT1211=m
CONFIG_SENSORS_VT8231=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SENSORS_W83773G=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SENSORS_W83781D is not set
# CONFIG_SENSORS_W83791D is not set
# CONFIG_SENSORS_W83792D is not set
# CONFIG_SENSORS_W83793 is not set
# CONFIG_SENSORS_W83795 is not set
# CONFIG_SENSORS_W83L785TS is not set
# CONFIG_SENSORS_W83L786NG is not set
# CONFIG_SENSORS_W83627HF is not set
# CONFIG_SENSORS_W83627EHF is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_SENSORS_INTEL_M10_BMC_HWMON=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_THERMAL=y
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_THERMAL_NETLINK is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_THERMAL_STATISTICS is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_THERMAL_EMERGENCY_POWEROFF_DELAY_MS=0
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_THERMAL_HWMON=y
CONFIG_THERMAL_OF=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_THERMAL_WRITABLE_TRIPS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE=y
# CONFIG_THERMAL_DEFAULT_GOV_FAIR_SHARE is not set
# CONFIG_THERMAL_DEFAULT_GOV_USER_SPACE is not set
# CONFIG_THERMAL_GOV_FAIR_SHARE is not set
CONFIG_THERMAL_GOV_STEP_WISE=y
# CONFIG_THERMAL_GOV_BANG_BANG is not set
# CONFIG_THERMAL_GOV_USER_SPACE is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CPU_THERMAL=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_CPU_FREQ_THERMAL=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_THERMAL_EMULATION is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_THERMAL_MMIO=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_DOVE_THERMAL is not set
CONFIG_ARMADA_THERMAL=y
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_GENERIC_ADC_THERMAL is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_CORE=y
[ mvebu ] Watchdog kernel config changes (#1355) * Disable watchdog NOWAYOUT in order to be able to stop watchdog during runtime. * Make ORION watchdog a module instead of in-kernel to give more flexibility to user.
2019-04-26 00:12:54 +08:00
# CONFIG_WATCHDOG_NOWAYOUT is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_WATCHDOG_OPEN_TIMEOUT=0
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_WATCHDOG_SYSFS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Watchdog Pretimeout Governors
#
CONFIG_WATCHDOG_PRETIMEOUT_GOV=y
CONFIG_WATCHDOG_PRETIMEOUT_GOV_SEL=m
CONFIG_WATCHDOG_PRETIMEOUT_GOV_NOOP=y
CONFIG_WATCHDOG_PRETIMEOUT_GOV_PANIC=y
CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_NOOP=y
# CONFIG_WATCHDOG_PRETIMEOUT_DEFAULT_GOV_PANIC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Watchdog Device Drivers
#
Add OMV 4 module dependencies and a workaround for ram2log that OMV can make use ZRAM powered ramlog. It is also helpful in case of sudden crash. Nginx can't start without log places into its subdir. We create them on start.
2018-07-04 14:19:50 +00:00
CONFIG_SOFT_WATCHDOG=m
Adjust MVEBU packagin patch and configuration
2018-07-24 12:31:31 +00:00
# CONFIG_SOFT_WATCHDOG_PRETIMEOUT is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_GPIO_WATCHDOG is not set
# CONFIG_XILINX_WATCHDOG is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_ZIIRAVE_WATCHDOG is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_ARMADA_37XX_WATCHDOG=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CADENCE_WATCHDOG is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_FTWDT010_WATCHDOG is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_DW_WATCHDOG is not set
[ mvebu ] Watchdog kernel config changes (#1355) * Disable watchdog NOWAYOUT in order to be able to stop watchdog during runtime. * Make ORION watchdog a module instead of in-kernel to give more flexibility to user.
2019-04-26 00:12:54 +08:00
CONFIG_ORION_WATCHDOG=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MAX63XX_WATCHDOG is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ARM_SMC_WATCHDOG is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_STPMIC1_WATCHDOG=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ALIM7101_WDT is not set
# CONFIG_I6300ESB_WDT is not set
# CONFIG_MEN_A21_WDT is not set
#
# PCI-based Watchdog Cards
#
# CONFIG_PCIPCWATCHDOG is not set
# CONFIG_WDTPCI is not set
#
# USB-based Watchdog Cards
#
# CONFIG_USBPCWATCHDOG is not set
CONFIG_SSB_POSSIBLE=y
Clean up and update Clearfog kernel configs
2016-11-19 21:38:54 +03:00
CONFIG_SSB=m
CONFIG_SSB_SPROM=y
CONFIG_SSB_BLOCKIO=y
CONFIG_SSB_PCIHOST_POSSIBLE=y
CONFIG_SSB_PCIHOST=y
CONFIG_SSB_B43_PCI_BRIDGE=y
CONFIG_SSB_SDIOHOST_POSSIBLE=y
CONFIG_SSB_SDIOHOST=y
CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y
CONFIG_SSB_DRIVER_PCICORE=y
# CONFIG_SSB_DRIVER_GPIO is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_BCMA_POSSIBLE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BCMA=m
Clean up and update Clearfog kernel configs
2016-11-19 21:38:54 +03:00
CONFIG_BCMA_BLOCKIO=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BCMA_HOST_PCI_POSSIBLE=y
CONFIG_BCMA_HOST_PCI=y
# CONFIG_BCMA_HOST_SOC is not set
CONFIG_BCMA_DRIVER_PCI=y
# CONFIG_BCMA_DRIVER_GMAC_CMN is not set
# CONFIG_BCMA_DRIVER_GPIO is not set
# CONFIG_BCMA_DEBUG is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Multifunction device drivers
#
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MFD_CORE=m
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_MFD_ACT8945A is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_AS3711 is not set
# CONFIG_MFD_AS3722 is not set
# CONFIG_PMIC_ADP5520 is not set
# CONFIG_MFD_AAT2870_CORE is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_MFD_ATMEL_FLEXCOM is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_ATMEL_HLCDC is not set
# CONFIG_MFD_BCM590XX is not set
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
# CONFIG_MFD_BD9571MWV is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_MFD_AXP20X_I2C is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MFD_MADERA is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_ASIC3 is not set
# CONFIG_PMIC_DA903X is not set
# CONFIG_MFD_DA9052_SPI is not set
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_DA9055 is not set
# CONFIG_MFD_DA9062 is not set
# CONFIG_MFD_DA9063 is not set
# CONFIG_MFD_DA9150 is not set
# CONFIG_MFD_DLN2 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MFD_GATEWORKS_GSC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_MC13XXX_SPI is not set
# CONFIG_MFD_MC13XXX_I2C is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MFD_MP2629 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_HI6421_PMIC is not set
# CONFIG_HTC_PASIC3 is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_LPC_ICH is not set
# CONFIG_LPC_SCH is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MFD_IQS62X is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_JANZ_CMODIO is not set
# CONFIG_MFD_KEMPLD is not set
# CONFIG_MFD_88PM800 is not set
# CONFIG_MFD_88PM805 is not set
# CONFIG_MFD_88PM860X is not set
# CONFIG_MFD_MAX14577 is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
# CONFIG_MFD_MAX77620 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MFD_MAX77650=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_MAX77686 is not set
# CONFIG_MFD_MAX77693 is not set
# CONFIG_MFD_MAX77843 is not set
# CONFIG_MFD_MAX8907 is not set
# CONFIG_MFD_MAX8925 is not set
# CONFIG_MFD_MAX8997 is not set
# CONFIG_MFD_MAX8998 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MFD_MT6360 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_MT6397 is not set
# CONFIG_MFD_MENF21BMC is not set
# CONFIG_EZX_PCAP is not set
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_MFD_CPCAP is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_VIPERBOARD is not set
# CONFIG_MFD_RETU is not set
# CONFIG_MFD_PCF50633 is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_MFD_PM8XXX is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_RDC321X is not set
# CONFIG_MFD_RT5033 is not set
# CONFIG_MFD_RC5T583 is not set
# CONFIG_MFD_RK808 is not set
# CONFIG_MFD_RN5T618 is not set
# CONFIG_MFD_SEC_CORE is not set
# CONFIG_MFD_SI476X_CORE is not set
# CONFIG_MFD_SM501 is not set
# CONFIG_MFD_SKY81452 is not set
# CONFIG_ABX500_CORE is not set
# CONFIG_MFD_STMPE is not set
CONFIG_MFD_SYSCON=y
# CONFIG_MFD_TI_AM335X_TSCADC is not set
# CONFIG_MFD_LP3943 is not set
# CONFIG_MFD_LP8788 is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_MFD_TI_LMU is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_PALMAS is not set
# CONFIG_TPS6105X is not set
# CONFIG_TPS65010 is not set
# CONFIG_TPS6507X is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_MFD_TPS65086 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_TPS65090 is not set
# CONFIG_MFD_TPS65217 is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_MFD_TI_LP873X is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_MFD_TI_LP87565 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_TPS65218 is not set
# CONFIG_MFD_TPS6586X is not set
# CONFIG_MFD_TPS65910 is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_TPS65912_SPI is not set
# CONFIG_MFD_TPS80031 is not set
# CONFIG_TWL4030_CORE is not set
# CONFIG_TWL6040_CORE is not set
# CONFIG_MFD_WL1273_CORE is not set
# CONFIG_MFD_LM3533 is not set
# CONFIG_MFD_TC3589X is not set
# CONFIG_MFD_T7L66XB is not set
# CONFIG_MFD_TC6387XB is not set
# CONFIG_MFD_TC6393XB is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MFD_TQMX86=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_VX855 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MFD_LOCHNAGAR is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_ARIZONA_SPI is not set
# CONFIG_MFD_WM8400 is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM831X_SPI is not set
# CONFIG_MFD_WM8350_I2C is not set
# CONFIG_MFD_WM8994 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MFD_ROHM_BD718XX=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MFD_ROHM_BD70528 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MFD_ROHM_BD71828 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MFD_STPMIC1=m
CONFIG_MFD_STMFX=m
# CONFIG_RAVE_SP_CORE is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_MFD_INTEL_M10_BMC=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Multifunction device drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_REGULATOR=y
# CONFIG_REGULATOR_DEBUG is not set
CONFIG_REGULATOR_FIXED_VOLTAGE=y
# CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
# CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_REGULATOR_88PG86X=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_REGULATOR_ACT8865=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_AD5398 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_REGULATOR_BD718XX=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_DA9210 is not set
# CONFIG_REGULATOR_DA9211 is not set
# CONFIG_REGULATOR_FAN53555 is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_REGULATOR_FAN53880 is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_REGULATOR_GPIO=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_ISL9305 is not set
# CONFIG_REGULATOR_ISL6271A is not set
# CONFIG_REGULATOR_LP3971 is not set
# CONFIG_REGULATOR_LP3972 is not set
# CONFIG_REGULATOR_LP872X is not set
# CONFIG_REGULATOR_LP8755 is not set
# CONFIG_REGULATOR_LTC3589 is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_REGULATOR_LTC3676 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_MAX1586 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_REGULATOR_MAX77650=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_MAX8649 is not set
# CONFIG_REGULATOR_MAX8660 is not set
# CONFIG_REGULATOR_MAX8952 is not set
# CONFIG_REGULATOR_MAX8973 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_REGULATOR_MAX77826 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_REGULATOR_MCP16502=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_REGULATOR_MP5416 is not set
# CONFIG_REGULATOR_MP8859 is not set
# CONFIG_REGULATOR_MP886X is not set
# CONFIG_REGULATOR_MPQ7920 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_MT6311 is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_REGULATOR_PCA9450 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_PFUZE100 is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_REGULATOR_PV88060 is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
# CONFIG_REGULATOR_PV88080 is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_REGULATOR_PV88090 is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
# CONFIG_REGULATOR_PWM is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_REGULATOR_RASPBERRYPI_TOUCHSCREEN_ATTINY=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_REGULATOR_ROHM=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_REGULATOR_RT4801=m
CONFIG_REGULATOR_RTMV20=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_REGULATOR_SLG51000 is not set
CONFIG_REGULATOR_STPMIC1=m
# CONFIG_REGULATOR_SY8106A is not set
# CONFIG_REGULATOR_SY8824X is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_REGULATOR_SY8827N is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_TPS51632 is not set
# CONFIG_REGULATOR_TPS62360 is not set
# CONFIG_REGULATOR_TPS65023 is not set
# CONFIG_REGULATOR_TPS6507X is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_REGULATOR_TPS65132 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_REGULATOR_TPS6524X is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_REGULATOR_VCTRL=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
# CONFIG_RC_CORE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_MEDIA_CEC_SUPPORT=y
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_CEC_CH7322 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_USB_PULSE8_CEC is not set
# CONFIG_USB_RAINSHADOW_CEC is not set
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_MEDIA_SUPPORT=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_MEDIA_SUPPORT_FILTER=y
CONFIG_MEDIA_SUBDRV_AUTOSELECT=y
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# Media device types
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_MEDIA_DIGITAL_TV_SUPPORT=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MEDIA_RADIO_SUPPORT=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MEDIA_SDR_SUPPORT=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MEDIA_PLATFORM_SUPPORT is not set
# CONFIG_MEDIA_TEST_SUPPORT is not set
# end of Media device types
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_VIDEO_DEV=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_MEDIA_CONTROLLER=y
CONFIG_DVB_CORE=m
#
# Video4Linux options
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_VIDEO_V4L2=m
CONFIG_VIDEO_V4L2_I2C=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_V4L2_SUBDEV_API is not set
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
# CONFIG_VIDEO_ADV_DEBUG is not set
# CONFIG_VIDEO_FIXED_MINOR_RANGES is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_TUNER=m
CONFIG_V4L2_FWNODE=m
CONFIG_VIDEOBUF_GEN=m
CONFIG_VIDEOBUF_VMALLOC=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# end of Video4Linux options
#
# Media controller options
#
CONFIG_MEDIA_CONTROLLER_DVB=y
# end of Media controller options
#
# Digital TV options
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_DVB_MMAP is not set
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_NET=y
CONFIG_DVB_MAX_ADAPTERS=16
# CONFIG_DVB_DYNAMIC_MINORS is not set
# CONFIG_DVB_DEMUX_SECTION_LOSS_LOG is not set
# CONFIG_DVB_ULE_DEBUG is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# end of Digital TV options
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# Media drivers
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
#
# Drivers filtered as selected at 'Filter media drivers'
#
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_MEDIA_USB_SUPPORT=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
#
# Webcam devices
#
CONFIG_USB_VIDEO_CLASS=m
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
CONFIG_USB_M5602=m
CONFIG_USB_STV06XX=m
CONFIG_USB_GL860=m
CONFIG_USB_GSPCA_BENQ=m
CONFIG_USB_GSPCA_CONEX=m
CONFIG_USB_GSPCA_CPIA1=m
CONFIG_USB_GSPCA_DTCS033=m
CONFIG_USB_GSPCA_ETOMS=m
CONFIG_USB_GSPCA_FINEPIX=m
CONFIG_USB_GSPCA_JEILINJ=m
CONFIG_USB_GSPCA_JL2005BCD=m
CONFIG_USB_GSPCA_KINECT=m
CONFIG_USB_GSPCA_KONICA=m
CONFIG_USB_GSPCA_MARS=m
CONFIG_USB_GSPCA_MR97310A=m
CONFIG_USB_GSPCA_NW80X=m
CONFIG_USB_GSPCA_OV519=m
CONFIG_USB_GSPCA_OV534=m
CONFIG_USB_GSPCA_OV534_9=m
CONFIG_USB_GSPCA_PAC207=m
CONFIG_USB_GSPCA_PAC7302=m
CONFIG_USB_GSPCA_PAC7311=m
CONFIG_USB_GSPCA_SE401=m
CONFIG_USB_GSPCA_SN9C2028=m
CONFIG_USB_GSPCA_SN9C20X=m
CONFIG_USB_GSPCA_SONIXB=m
CONFIG_USB_GSPCA_SONIXJ=m
CONFIG_USB_GSPCA_SPCA500=m
CONFIG_USB_GSPCA_SPCA501=m
CONFIG_USB_GSPCA_SPCA505=m
CONFIG_USB_GSPCA_SPCA506=m
CONFIG_USB_GSPCA_SPCA508=m
CONFIG_USB_GSPCA_SPCA561=m
CONFIG_USB_GSPCA_SPCA1528=m
CONFIG_USB_GSPCA_SQ905=m
CONFIG_USB_GSPCA_SQ905C=m
CONFIG_USB_GSPCA_SQ930X=m
CONFIG_USB_GSPCA_STK014=m
CONFIG_USB_GSPCA_STK1135=m
CONFIG_USB_GSPCA_STV0680=m
CONFIG_USB_GSPCA_SUNPLUS=m
CONFIG_USB_GSPCA_T613=m
CONFIG_USB_GSPCA_TOPRO=m
CONFIG_USB_GSPCA_TOUPTEK=m
CONFIG_USB_GSPCA_TV8532=m
CONFIG_USB_GSPCA_VC032X=m
CONFIG_USB_GSPCA_VICAM=m
CONFIG_USB_GSPCA_XIRLINK_CIT=m
CONFIG_USB_GSPCA_ZC3XX=m
CONFIG_USB_PWC=m
# CONFIG_USB_PWC_DEBUG is not set
CONFIG_USB_PWC_INPUT_EVDEV=y
CONFIG_VIDEO_CPIA2=m
CONFIG_USB_ZR364XX=m
CONFIG_USB_STKWEBCAM=m
CONFIG_USB_S2255=m
CONFIG_VIDEO_USBTV=m
#
# Analog TV USB devices
#
CONFIG_VIDEO_PVRUSB2=m
CONFIG_VIDEO_PVRUSB2_SYSFS=y
CONFIG_VIDEO_PVRUSB2_DVB=y
# CONFIG_VIDEO_PVRUSB2_DEBUGIFC is not set
CONFIG_VIDEO_HDPVR=m
CONFIG_VIDEO_STK1160_COMMON=m
CONFIG_VIDEO_STK1160=m
CONFIG_VIDEO_GO7007=m
CONFIG_VIDEO_GO7007_USB=m
CONFIG_VIDEO_GO7007_LOADER=m
CONFIG_VIDEO_GO7007_USB_S2250_BOARD=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# Analog/digital TV USB devices
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_AU0828=m
CONFIG_VIDEO_AU0828_V4L2=y
CONFIG_VIDEO_CX231XX=m
CONFIG_VIDEO_CX231XX_ALSA=m
CONFIG_VIDEO_CX231XX_DVB=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# Digital TV USB devices
#
CONFIG_DVB_USB_V2=m
CONFIG_DVB_USB_AF9015=m
CONFIG_DVB_USB_AF9035=m
CONFIG_DVB_USB_ANYSEE=m
CONFIG_DVB_USB_AU6610=m
CONFIG_DVB_USB_AZ6007=m
CONFIG_DVB_USB_CE6230=m
CONFIG_DVB_USB_EC168=m
CONFIG_DVB_USB_GL861=m
CONFIG_DVB_USB_MXL111SF=m
CONFIG_DVB_USB_RTL28XXU=m
CONFIG_DVB_USB_DVBSKY=m
CONFIG_DVB_USB_ZD1301=m
# CONFIG_DVB_TTUSB_BUDGET is not set
# CONFIG_DVB_TTUSB_DEC is not set
# CONFIG_SMS_USB_DRV is not set
# CONFIG_DVB_B2C2_FLEXCOP_USB is not set
# CONFIG_DVB_AS102 is not set
#
# Webcam, TV (analog/digital) USB devices
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_EM28XX=m
CONFIG_VIDEO_EM28XX_V4L2=m
CONFIG_VIDEO_EM28XX_ALSA=m
CONFIG_VIDEO_EM28XX_DVB=m
#
# Software defined radio USB devices
#
CONFIG_USB_AIRSPY=m
CONFIG_USB_HACKRF=m
CONFIG_USB_MSI2500=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
# CONFIG_MEDIA_PCI_SUPPORT is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RADIO_ADAPTERS=y
# CONFIG_RADIO_SI470X is not set
# CONFIG_RADIO_SI4713 is not set
# CONFIG_USB_MR800 is not set
# CONFIG_USB_DSBR is not set
# CONFIG_RADIO_MAXIRADIO is not set
# CONFIG_RADIO_SHARK is not set
# CONFIG_RADIO_SHARK2 is not set
# CONFIG_USB_KEENE is not set
# CONFIG_USB_RAREMONO is not set
# CONFIG_USB_MA901 is not set
# CONFIG_RADIO_TEA5764 is not set
# CONFIG_RADIO_SAA7706H is not set
# CONFIG_RADIO_TEF6862 is not set
# CONFIG_RADIO_WL1273 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_CX2341X=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_VIDEO_TVEEPROM=m
CONFIG_CYPRESS_FIRMWARE=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEOBUF2_CORE=m
CONFIG_VIDEOBUF2_V4L2=m
CONFIG_VIDEOBUF2_MEMOPS=m
CONFIG_VIDEOBUF2_VMALLOC=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# end of Media drivers
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MEDIA_HIDE_ANCILLARY_SUBDRV=y
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# Media ancillary drivers
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_MEDIA_ATTACH=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# audio, video and radio I2C drivers auto-selected by 'Autoselect ancillary drivers'
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_MSP3400=m
CONFIG_VIDEO_CS53L32A=m
CONFIG_VIDEO_UDA1342=m
CONFIG_VIDEO_WM8775=m
CONFIG_VIDEO_SONY_BTF_MPX=m
CONFIG_VIDEO_SAA711X=m
CONFIG_VIDEO_TVP5150=m
CONFIG_VIDEO_TW2804=m
CONFIG_VIDEO_TW9903=m
CONFIG_VIDEO_TW9906=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Video and audio decoders
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_CX25840=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Camera sensor devices
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_HI556 is not set
# CONFIG_VIDEO_IMX214 is not set
# CONFIG_VIDEO_IMX219 is not set
# CONFIG_VIDEO_IMX258 is not set
# CONFIG_VIDEO_IMX274 is not set
# CONFIG_VIDEO_IMX290 is not set
# CONFIG_VIDEO_IMX319 is not set
# CONFIG_VIDEO_IMX355 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_OV2640=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_OV2659 is not set
# CONFIG_VIDEO_OV2680 is not set
# CONFIG_VIDEO_OV2685 is not set
# CONFIG_VIDEO_OV5640 is not set
# CONFIG_VIDEO_OV5645 is not set
# CONFIG_VIDEO_OV5647 is not set
# CONFIG_VIDEO_OV6650 is not set
# CONFIG_VIDEO_OV5670 is not set
# CONFIG_VIDEO_OV5675 is not set
# CONFIG_VIDEO_OV5695 is not set
# CONFIG_VIDEO_OV7251 is not set
# CONFIG_VIDEO_OV772X is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_OV7640=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_OV7670 is not set
# CONFIG_VIDEO_OV7740 is not set
# CONFIG_VIDEO_OV8856 is not set
# CONFIG_VIDEO_OV9640 is not set
# CONFIG_VIDEO_OV9650 is not set
# CONFIG_VIDEO_OV13858 is not set
# CONFIG_VIDEO_VS6624 is not set
# CONFIG_VIDEO_MT9M001 is not set
# CONFIG_VIDEO_MT9M032 is not set
# CONFIG_VIDEO_MT9M111 is not set
# CONFIG_VIDEO_MT9P031 is not set
# CONFIG_VIDEO_MT9T001 is not set
# CONFIG_VIDEO_MT9T112 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIDEO_MT9V011=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_MT9V032 is not set
# CONFIG_VIDEO_MT9V111 is not set
# CONFIG_VIDEO_SR030PC30 is not set
# CONFIG_VIDEO_NOON010PC30 is not set
# CONFIG_VIDEO_M5MOLS is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_VIDEO_RDACM20 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_RJ54N1 is not set
# CONFIG_VIDEO_S5K6AA is not set
# CONFIG_VIDEO_S5K6A3 is not set
# CONFIG_VIDEO_S5K4ECGX is not set
# CONFIG_VIDEO_S5K5BAF is not set
# CONFIG_VIDEO_SMIAPP is not set
# CONFIG_VIDEO_ET8EK8 is not set
# CONFIG_VIDEO_S5C73M3 is not set
# end of Camera sensor devices
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Lens drivers
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_AD5820 is not set
# CONFIG_VIDEO_AK7375 is not set
# CONFIG_VIDEO_DW9714 is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_VIDEO_DW9768 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_DW9807_VCM is not set
# end of Lens drivers
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Flash devices
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VIDEO_ADP1653 is not set
# CONFIG_VIDEO_LM3560 is not set
# CONFIG_VIDEO_LM3646 is not set
# end of Flash devices
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# SPI I2C drivers auto-selected by 'Autoselect ancillary drivers'
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# Media SPI Adapters
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CXD2880_SPI_DRV=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Media SPI Adapters
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_MEDIA_TUNER=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# Tuner drivers auto-selected by 'Autoselect ancillary drivers'
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_MEDIA_TUNER_SIMPLE=m
CONFIG_MEDIA_TUNER_TDA8290=m
CONFIG_MEDIA_TUNER_TDA827X=m
CONFIG_MEDIA_TUNER_TDA18271=m
CONFIG_MEDIA_TUNER_TDA9887=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MEDIA_TUNER_TEA5761=m
CONFIG_MEDIA_TUNER_TEA5767=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MEDIA_TUNER_MSI001=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_MEDIA_TUNER_MT20XX=m
CONFIG_MEDIA_TUNER_MT2060=m
CONFIG_MEDIA_TUNER_MT2063=m
CONFIG_MEDIA_TUNER_QT1010=m
CONFIG_MEDIA_TUNER_XC2028=m
CONFIG_MEDIA_TUNER_XC5000=m
CONFIG_MEDIA_TUNER_XC4000=m
CONFIG_MEDIA_TUNER_MXL5005S=m
CONFIG_MEDIA_TUNER_MXL5007T=m
CONFIG_MEDIA_TUNER_MC44S803=m
CONFIG_MEDIA_TUNER_TDA18218=m
CONFIG_MEDIA_TUNER_FC0011=m
CONFIG_MEDIA_TUNER_FC0012=m
CONFIG_MEDIA_TUNER_FC0013=m
CONFIG_MEDIA_TUNER_TDA18212=m
CONFIG_MEDIA_TUNER_E4000=m
CONFIG_MEDIA_TUNER_FC2580=m
CONFIG_MEDIA_TUNER_TUA9001=m
CONFIG_MEDIA_TUNER_SI2157=m
CONFIG_MEDIA_TUNER_IT913X=m
CONFIG_MEDIA_TUNER_R820T=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MEDIA_TUNER_QM1D1C0042=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# DVB Frontend drivers auto-selected by 'Autoselect ancillary drivers'
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# Multistandard (satellite) frontends
#
CONFIG_DVB_M88DS3103=m
#
# Multistandard (cable + terrestrial) frontends
#
CONFIG_DVB_DRXK=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_TDA18271C2DD=m
CONFIG_DVB_SI2165=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_MN88472=m
CONFIG_DVB_MN88473=m
#
# DVB-S (satellite) frontends
#
CONFIG_DVB_STV6110=m
CONFIG_DVB_STV0900=m
CONFIG_DVB_CX24116=m
CONFIG_DVB_TS2020=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_TDA10071=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# DVB-T (terrestrial) frontends
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_DRXD=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_MT352=m
CONFIG_DVB_ZL10353=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_TDA10048=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_AF9013=m
CONFIG_DVB_EC100=m
CONFIG_DVB_CXD2820R=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_DVB_CXD2841ER=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_RTL2830=m
CONFIG_DVB_RTL2832=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_RTL2832_SDR=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_SI2168=m
CONFIG_DVB_ZD1301_DEMOD=m
#
# DVB-C (cable) frontends
#
CONFIG_DVB_TDA10023=m
#
# ATSC (North American/Korean Terrestrial/Cable DTV) frontends
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_LGDT330X=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_LGDT3305=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_LGDT3306A=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_LG2160=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_S5H1409=m
CONFIG_DVB_AU8522=m
CONFIG_DVB_AU8522_DTV=m
CONFIG_DVB_AU8522_V4L=m
CONFIG_DVB_S5H1411=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# ISDB-T (terrestrial) frontends
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_S921=m
CONFIG_DVB_MB86A20S=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
#
# ISDB-S (satellite) & ISDB-T (terrestrial) frontends
#
CONFIG_DVB_TC90522=m
#
# Digital terrestrial only tuners/PLL
#
CONFIG_DVB_PLL=m
#
# SEC control devices for DVB-S
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_DRX39XYJ=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_ISL6423=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DVB_A8293=m
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
CONFIG_DVB_AF9033=m
#
# Common Interface (EN50221) controller drivers
#
CONFIG_DVB_SP2=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# end of Media ancillary drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Graphics support
#
CONFIG_VGA_ARB=y
CONFIG_VGA_ARB_MAX_GPUS=16
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_IMX_IPUV3_CORE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_DRM is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# ARM devices
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of ARM devices
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Frame buffer Devices
#
# CONFIG_FB is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Frame buffer Devices
#
# Backlight & LCD device support
#
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_LCD_L4F00242T03=m
CONFIG_LCD_LMS283GF05=m
CONFIG_LCD_LTV350QV=m
CONFIG_LCD_ILI922X=m
CONFIG_LCD_ILI9320=m
CONFIG_LCD_TDO24M=m
CONFIG_LCD_VGG2432A4=m
CONFIG_LCD_PLATFORM=m
CONFIG_LCD_AMS369FG06=m
CONFIG_LCD_LMS501KF03=m
CONFIG_LCD_HX8357=m
CONFIG_LCD_OTM3225A=m
CONFIG_BACKLIGHT_CLASS_DEVICE=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_BACKLIGHT_KTD253=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_BACKLIGHT_PWM=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BACKLIGHT_QCOM_WLED is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_BACKLIGHT_ADP8860=m
CONFIG_BACKLIGHT_ADP8870=m
CONFIG_BACKLIGHT_LM3630A=m
CONFIG_BACKLIGHT_LM3639=m
CONFIG_BACKLIGHT_LP855X=m
CONFIG_BACKLIGHT_GPIO=m
CONFIG_BACKLIGHT_LV5207LP=m
CONFIG_BACKLIGHT_BD6107=m
CONFIG_BACKLIGHT_ARCXCNN=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BACKLIGHT_LED is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Backlight & LCD device support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Console display driver support
#
CONFIG_DUMMY_CONSOLE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Console display driver support
# end of Graphics support
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
CONFIG_SOUND=m
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SND_SEQ_DEVICE=m
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
CONFIG_SND_RAWMIDI=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_SND_OSSEMUL is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
CONFIG_SND_PCM_TIMER=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SND_HRTIMER is not set
# CONFIG_SND_DYNAMIC_MINORS is not set
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
# CONFIG_SND_SUPPORT_OLD_API is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SND_PROC_FS=y
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
# CONFIG_SND_VERBOSE_PROCFS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_SEQ_MIDI_EVENT=m
CONFIG_SND_SEQ_MIDI=m
CONFIG_SND_SEQ_VIRMIDI=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SND_DRIVERS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SND_DUMMY=m
CONFIG_SND_ALOOP=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_MTS64=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SND_PORTMAN2X4=m
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
# CONFIG_SND_PCI is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# HD-Audio
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of HD-Audio
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SND_HDA_PREALLOC_SIZE=64
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
# CONFIG_SND_ARM is not set
# CONFIG_SND_SPI is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_SND_USB=y
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
CONFIG_SND_USB_AUDIO=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SND_USB_AUDIO_USE_MEDIA_CONTROLLER=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SND_USB_UA101 is not set
# CONFIG_SND_USB_CAIAQ is not set
# CONFIG_SND_USB_6FIRE is not set
# CONFIG_SND_USB_HIFACE is not set
# CONFIG_SND_BCD2000 is not set
# CONFIG_SND_USB_POD is not set
# CONFIG_SND_USB_PODHD is not set
# CONFIG_SND_USB_TONEPORT is not set
# CONFIG_SND_USB_VARIAX is not set
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
# CONFIG_SND_SOC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# HID support
#
CONFIG_HID=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HID_BATTERY_STRENGTH=y
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
CONFIG_HIDRAW=y
CONFIG_UHID=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HID_GENERIC=y
#
# Special HID drivers
#
# CONFIG_HID_A4TECH is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_HID_ACCUTOUCH is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_ACRUX is not set
# CONFIG_HID_APPLE is not set
# CONFIG_HID_APPLEIR is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_HID_ASUS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_AUREAL is not set
# CONFIG_HID_BELKIN is not set
# CONFIG_HID_BETOP_FF is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_HID_BIGBEN_FF=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_CHERRY is not set
# CONFIG_HID_CHICONY is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_HID_CORSAIR is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_HID_COUGAR=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_HID_MACALLY=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_PRODIKEYS is not set
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
# CONFIG_HID_CMEDIA is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_CP2112 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_HID_CREATIVE_SB0540 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_CYPRESS is not set
# CONFIG_HID_DRAGONRISE is not set
# CONFIG_HID_EMS_FF is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_HID_ELAN is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_ELECOM is not set
# CONFIG_HID_ELO is not set
# CONFIG_HID_EZKEY is not set
# CONFIG_HID_GEMBIRD is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_HID_GFRM is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_HID_GLORIOUS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_HOLTEK is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_HID_VIVALDI=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_HID_GT683R is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_KEYTOUCH is not set
# CONFIG_HID_KYE is not set
# CONFIG_HID_UCLOGIC is not set
# CONFIG_HID_WALTOP is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_HID_VIEWSONIC=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HID_GYRATION=m
CONFIG_HID_ICADE=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_HID_ITE is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_HID_JABRA is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_TWINHAN is not set
# CONFIG_HID_KENSINGTON is not set
# CONFIG_HID_LCPOWER is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
# CONFIG_HID_LED is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_LENOVO is not set
# CONFIG_HID_LOGITECH is not set
# CONFIG_HID_MAGICMOUSE is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_HID_MALTRON=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_HID_MAYFLASH is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_HID_REDRAGON=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_MICROSOFT is not set
# CONFIG_HID_MONTEREY is not set
# CONFIG_HID_MULTITOUCH is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_HID_NTI is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_NTRIG is not set
# CONFIG_HID_ORTEK is not set
# CONFIG_HID_PANTHERLORD is not set
# CONFIG_HID_PENMOUNT is not set
# CONFIG_HID_PETALYNX is not set
# CONFIG_HID_PICOLCD is not set
# CONFIG_HID_PLANTRONICS is not set
# CONFIG_HID_PRIMAX is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_HID_RETRODE is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HID_ROCCAT=m
CONFIG_HID_SAITEK=m
CONFIG_HID_SAMSUNG=m
CONFIG_HID_SONY=m
CONFIG_SONY_FF=y
CONFIG_HID_SPEEDLINK=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_HID_STEAM is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_STEELSERIES is not set
# CONFIG_HID_SUNPLUS is not set
# CONFIG_HID_RMI is not set
# CONFIG_HID_GREENASIA is not set
# CONFIG_HID_SMARTJOYPLUS is not set
# CONFIG_HID_TIVO is not set
# CONFIG_HID_TOPSEED is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_HID_THINGM is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_THRUSTMASTER is not set
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_HID_UDRAW_PS3 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_HID_U2FZERO=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_WACOM is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_HID_WIIMOTE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_HID_XINMO is not set
# CONFIG_HID_ZEROPLUS is not set
# CONFIG_HID_ZYDACRON is not set
# CONFIG_HID_SENSOR_HUB is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
# CONFIG_HID_ALPS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_HID_MCP2221 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Special HID drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# USB HID support
#
CONFIG_USB_HID=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HID_PID=y
Minimize marvell kernel configs
2017-02-26 22:13:13 +03:00
CONFIG_USB_HIDDEV=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of USB HID support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# I2C HID support
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_I2C_HID=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of I2C HID support
# end of HID support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_SUPPORT=y
CONFIG_USB_COMMON=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_USB_LED_TRIG=y
# CONFIG_USB_ULPI_BUS is not set
# CONFIG_USB_CONN_GPIO is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB=y
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_USB_PCI=y
Let USB device negotiation appear in dmesg output
2017-11-23 20:37:51 +01:00
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Miscellaneous USB options
#
CONFIG_USB_DEFAULT_PERSIST=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_USB_FEW_INIT_RETRIES is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_USB_DYNAMIC_MINORS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_USB_OTG is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_USB_OTG_PRODUCTLIST is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_USB_LEDS_TRIGGER_USBPORT=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_USB_AUTOSUSPEND_DELAY=2
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_USB_MON is not set
#
# USB Host Controller Drivers
#
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_XHCI_HCD=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_USB_XHCI_DBGCAP is not set
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_USB_XHCI_PCI=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_USB_XHCI_PCI_RENESAS is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_USB_XHCI_PLATFORM=y
CONFIG_USB_XHCI_MVEBU=y
CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_EHCI_TT_NEWSCHED=y
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_USB_EHCI_PCI=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_USB_EHCI_FSL=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_USB_EHCI_HCD_ORION=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_EHCI_HCD_PLATFORM=y
CONFIG_USB_OXU210HP_HCD=m
CONFIG_USB_ISP116X_HCD=m
CONFIG_USB_FOTG210_HCD=m
CONFIG_USB_MAX3421_HCD=m
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_PCI=y
CONFIG_USB_OHCI_HCD_PLATFORM=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_U132_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_HCD_ISO=y
CONFIG_USB_R8A66597_HCD=m
CONFIG_USB_HCD_BCMA=m
CONFIG_USB_HCD_SSB=m
CONFIG_USB_HCD_TEST_MODE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# USB Device Class drivers
#
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_ACM=m
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_USB_PRINTER=m
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_WDM=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_TMC=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may
#
#
# also be needed; see USB_STORAGE Help for more info
#
CONFIG_USB_STORAGE=y
# CONFIG_USB_STORAGE_DEBUG is not set
Merge MVEBU to stable
2018-05-24 14:18:01 +02:00
CONFIG_USB_STORAGE_REALTEK=m
CONFIG_REALTEK_AUTOPM=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m
CONFIG_USB_STORAGE_JUMPSHOT=m
CONFIG_USB_STORAGE_ALAUDA=m
CONFIG_USB_STORAGE_ONETOUCH=m
CONFIG_USB_STORAGE_KARMA=m
CONFIG_USB_STORAGE_CYPRESS_ATACB=m
CONFIG_USB_STORAGE_ENE_UB6250=m
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_USB_UAS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USBIP_CORE=m
# CONFIG_USBIP_VHCI_HCD is not set
# CONFIG_USBIP_HOST is not set
# CONFIG_USBIP_DEBUG is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_USB_CDNS3 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_USB_MUSB_HDRC is not set
# CONFIG_USB_DWC3 is not set
# CONFIG_USB_DWC2 is not set
# CONFIG_USB_CHIPIDEA is not set
# CONFIG_USB_ISP1760 is not set
#
# USB port drivers
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_USS720=m
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_SIMPLE=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_SERIAL_AIRCABLE=m
CONFIG_USB_SERIAL_ARK3116=m
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_CH341=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_SERIAL_CP210X=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_SERIAL_FTDI_SIO=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_F81232=m
CONFIG_USB_SERIAL_F8153X=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_IUU=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_METRO=m
CONFIG_USB_SERIAL_MOS7720=m
# CONFIG_USB_SERIAL_MOS7715_PARPORT is not set
CONFIG_USB_SERIAL_MOS7840=m
CONFIG_USB_SERIAL_MXUPORT=m
CONFIG_USB_SERIAL_NAVMAN=m
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_SERIAL_PL2303=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_SERIAL_OTI6858=m
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_SERIAL_QCAUX=m
CONFIG_USB_SERIAL_QUALCOMM=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_SERIAL_SPCP8X5=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_SERIAL_SIERRAWIRELESS=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_SERIAL_SYMBOL=m
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
Add USB serial to mvebu0next kernel config
2016-12-11 23:40:19 +03:00
CONFIG_USB_SERIAL_WWAN=m
CONFIG_USB_SERIAL_OPTION=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_SERIAL_OPTICON=m
CONFIG_USB_SERIAL_XSENS_MT=m
CONFIG_USB_SERIAL_WISHBONE=m
CONFIG_USB_SERIAL_SSU100=m
CONFIG_USB_SERIAL_QT2=m
CONFIG_USB_SERIAL_UPD78F0730=m
CONFIG_USB_SERIAL_DEBUG=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# USB Miscellaneous drivers
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_ADUTUX=m
CONFIG_USB_SEVSEG=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_CYPRESS_CY7C63=m
CONFIG_USB_CYTHERM=m
CONFIG_USB_IDMOUSE=m
CONFIG_USB_FTDI_ELAN=m
CONFIG_USB_APPLEDISPLAY=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_APPLE_MFI_FASTCHARGE is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_USB_SISUSBVGA=m
CONFIG_USB_LD=m
CONFIG_USB_TRANCEVIBRATOR=m
CONFIG_USB_IOWARRIOR=m
CONFIG_USB_TEST=m
CONFIG_USB_EHSET_TEST_FIXTURE=m
CONFIG_USB_ISIGHTFW=m
CONFIG_USB_YUREX=m
CONFIG_USB_EZUSB_FX2=m
CONFIG_USB_HUB_USB251XB=m
CONFIG_USB_HSIC_USB3503=y
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_USB_HSIC_USB4604 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_USB_LINK_LAYER_TEST is not set
# CONFIG_USB_CHAOSKEY is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_USB_ATM=m
# CONFIG_USB_SPEEDTOUCH is not set
# CONFIG_USB_CXACRU is not set
# CONFIG_USB_UEAGLEATM is not set
# CONFIG_USB_XUSBATM is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# USB Physical Layer drivers
#
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_USB_PHY=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_NOP_USB_XCEIV is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_USB_GPIO_VBUS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_USB_ISP1301 is not set
# CONFIG_USB_ULPI is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of USB Physical Layer drivers
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_USB_GADGET is not set
# CONFIG_TYPEC is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_USB_ROLE_SWITCH=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MMC=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_PWRSEQ_EMMC=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_PWRSEQ_SD8787 is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_PWRSEQ_SIMPLE=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_MINORS=8
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set
#
# MMC/SD/SDIO Host Controller Drivers
#
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
# CONFIG_MMC_DEBUG is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_IO_ACCESSORS=y
# CONFIG_MMC_SDHCI_PCI is not set
CONFIG_MMC_SDHCI_PLTFM=y
# CONFIG_MMC_SDHCI_OF_ARASAN is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MMC_SDHCI_OF_ASPEED is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MMC_SDHCI_OF_AT91 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MMC_SDHCI_OF_DWCMSHC=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_MMC_SDHCI_CADENCE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MMC_SDHCI_DOVE=y
CONFIG_MMC_SDHCI_PXAV3=y
# CONFIG_MMC_SDHCI_F_SDH30 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MMC_SDHCI_MILBEAUT is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MMC_ALCOR=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MMC_TIFM_SD is not set
CONFIG_MMC_MVSDIO=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
# CONFIG_MMC_SPI is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MMC_CB710 is not set
# CONFIG_MMC_VIA_SDMMC is not set
# CONFIG_MMC_DW is not set
# CONFIG_MMC_VUB300 is not set
# CONFIG_MMC_USHC is not set
# CONFIG_MMC_USDHI6ROL0 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MMC_REALTEK_PCI=m
CONFIG_MMC_REALTEK_USB=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_MMC_CQHCI=m
# CONFIG_MMC_HSQ is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MMC_TOSHIBA_PCI is not set
# CONFIG_MMC_MTK is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_MMC_SDHCI_XENON is not set
mvebu: config: Update linux-mvebu-current.config Debian Buster use nftables backend for iptables command. Added support for nftable Added PCIe support Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2020-01-02 18:17:06 +07:00
# CONFIG_MMC_SDHCI_OMAP is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_MMC_SDHCI_AM654=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MEMSTICK is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NEW_LEDS=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_LEDS_CLASS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_CLASS_FLASH is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_LEDS_CLASS_MULTICOLOR is not set
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_LEDS_BRIGHTNESS_HW_CHANGED=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
#
# LED drivers
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_LEDS_AN30259A=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_LEDS_AW2013 is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_BCM6328 is not set
# CONFIG_LEDS_BCM6358 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_LEDS_CR0014114=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_LEDS_EL15203000 is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_LM3530 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_LEDS_LM3532=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_LM3642 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_LEDS_LM3692X=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_PCA9532 is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_LEDS_GPIO=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_LP3944 is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_LEDS_LP3952 is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_LEDS_LP50XX=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_LEDS_LP55XX_COMMON is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_LP8860 is not set
# CONFIG_LEDS_PCA955X is not set
# CONFIG_LEDS_PCA963X is not set
# CONFIG_LEDS_DAC124S085 is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
# CONFIG_LEDS_PWM is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_REGULATOR is not set
# CONFIG_LEDS_BD2802 is not set
# CONFIG_LEDS_LT3593 is not set
# CONFIG_LEDS_NS2 is not set
# CONFIG_LEDS_TCA6507 is not set
# CONFIG_LEDS_TLC591XX is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_LEDS_MAX77650=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_LEDS_LM355x is not set
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
# CONFIG_LEDS_IS31FL319X is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_LEDS_IS31FL32XX=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
#
# LED driver for blink(1) USB RGB LED is under Special HID drivers (HID_THINGM)
#
# CONFIG_LEDS_BLINKM is not set
Helios4 cleanup. Adding default branch
2018-01-07 09:58:52 +01:00
# CONFIG_LEDS_SYSCON is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_LEDS_MLXREG=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_LEDS_USER=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_LEDS_SPI_BYTE=m
CONFIG_LEDS_TI_LMU_COMMON=m
CONFIG_LEDS_LM3697=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
#
# LED Triggers
#
CONFIG_LEDS_TRIGGERS=y
CONFIG_LEDS_TRIGGER_TIMER=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_LEDS_TRIGGER_ONESHOT=m
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_LEDS_TRIGGER_DISK=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_LEDS_TRIGGER_MTD=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_LEDS_TRIGGER_HEARTBEAT=y
# CONFIG_LEDS_TRIGGER_BACKLIGHT is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_LEDS_TRIGGER_CPU=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_LEDS_TRIGGER_ACTIVITY=m
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_LEDS_TRIGGER_GPIO=m
CONFIG_LEDS_TRIGGER_DEFAULT_ON=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
#
# iptables trigger is under Netfilter config (LED target)
#
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_LEDS_TRIGGER_TRANSIENT=m
CONFIG_LEDS_TRIGGER_CAMERA=m
CONFIG_LEDS_TRIGGER_PANIC=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_LEDS_TRIGGER_NETDEV=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_LEDS_TRIGGER_PATTERN=m
CONFIG_LEDS_TRIGGER_AUDIO=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_ACCESSIBILITY is not set
# CONFIG_INFINIBAND is not set
CONFIG_EDAC_ATOMIC_SCRUB=y
CONFIG_EDAC_SUPPORT=y
Bugfix: adjust mvebu-current kernel config It boots up properly now @boards-marvell Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
2020-04-29 12:27:29 +02:00
CONFIG_EDAC=m
CONFIG_EDAC_LEGACY_SYSFS=y
# CONFIG_EDAC_DEBUG is not set
CONFIG_EDAC_ARMADA_XP=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_RTC_SYSTOHC=y
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"
# CONFIG_RTC_DEBUG is not set
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_RTC_NVMEM=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# RTC interfaces
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RTC_INTF_SYSFS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_RTC_INTF_PROC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_RTC_INTF_DEV=y
# CONFIG_RTC_INTF_DEV_UIE_EMUL is not set
# CONFIG_RTC_DRV_TEST is not set
#
# I2C RTC drivers
#
# CONFIG_RTC_DRV_ABB5ZES3 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RTC_DRV_ABEOZ9=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RTC_DRV_ABX80X is not set
# CONFIG_RTC_DRV_DS1307 is not set
# CONFIG_RTC_DRV_DS1374 is not set
# CONFIG_RTC_DRV_DS1672 is not set
# CONFIG_RTC_DRV_HYM8563 is not set
# CONFIG_RTC_DRV_MAX6900 is not set
# CONFIG_RTC_DRV_RS5C372 is not set
# CONFIG_RTC_DRV_ISL1208 is not set
# CONFIG_RTC_DRV_ISL12022 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_RTC_DRV_ISL12026=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RTC_DRV_X1205 is not set
# CONFIG_RTC_DRV_PCF8523 is not set
# CONFIG_RTC_DRV_PCF85063 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_RTC_DRV_PCF85363=m
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_RTC_DRV_PCF8563 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RTC_DRV_PCF8583 is not set
# CONFIG_RTC_DRV_M41T80 is not set
# CONFIG_RTC_DRV_BQ32K is not set
CONFIG_RTC_DRV_S35390A=y
# CONFIG_RTC_DRV_FM3130 is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_RTC_DRV_RX8010 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RTC_DRV_RX8581 is not set
# CONFIG_RTC_DRV_RX8025 is not set
# CONFIG_RTC_DRV_EM3027 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RTC_DRV_RV3028=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_RTC_DRV_RV3032=m
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_RTC_DRV_RV8803 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RTC_DRV_SD3078=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# SPI RTC drivers
#
# CONFIG_RTC_DRV_M41T93 is not set
# CONFIG_RTC_DRV_M41T94 is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_RTC_DRV_DS1302=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RTC_DRV_DS1305 is not set
# CONFIG_RTC_DRV_DS1343 is not set
# CONFIG_RTC_DRV_DS1347 is not set
# CONFIG_RTC_DRV_DS1390 is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
# CONFIG_RTC_DRV_MAX6916 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RTC_DRV_R9701 is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_RTC_DRV_RX4581 is not set
CONFIG_RTC_DRV_RX6110=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RTC_DRV_RS5C348 is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_RTC_DRV_MAX6902 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RTC_DRV_PCF2123 is not set
# CONFIG_RTC_DRV_MCP795 is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_RTC_I2C_AND_SPI=y
#
# SPI and I2C RTC drivers
#
# CONFIG_RTC_DRV_DS3232 is not set
# CONFIG_RTC_DRV_PCF2127 is not set
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
# CONFIG_RTC_DRV_RV3029C2 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Platform RTC drivers
#
# CONFIG_RTC_DRV_CMOS is not set
# CONFIG_RTC_DRV_DS1286 is not set
# CONFIG_RTC_DRV_DS1511 is not set
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_DS1685_FAMILY is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_DS2404 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T35 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_MSM6242 is not set
# CONFIG_RTC_DRV_BQ4802 is not set
# CONFIG_RTC_DRV_RP5C01 is not set
# CONFIG_RTC_DRV_V3020 is not set
# CONFIG_RTC_DRV_ZYNQMP is not set
#
# on-CPU RTC drivers
#
CONFIG_RTC_DRV_MV=y
CONFIG_RTC_DRV_ARMADA38X=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RTC_DRV_CADENCE=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_RTC_DRV_FTRTC010=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_RTC_DRV_R7301 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# HID Sensor RTC drivers
#
CONFIG_DMADEVICES=y
# CONFIG_DMADEVICES_DEBUG is not set
#
# DMA Devices
#
CONFIG_ASYNC_TX_ENABLE_CHANNEL_SWITCH=y
CONFIG_DMA_ENGINE=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_DMA_VIRTUAL_CHANNELS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_DMA_OF=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
# CONFIG_ALTERA_MSGDMA is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_DW_AXI_DMAC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_FSL_EDMA is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_FSL_QDMA=m
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_INTEL_IDMA64 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MV_XOR=y
# CONFIG_NBPFAXI_DMA is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PLX_DMA is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_XILINX_ZYNQMP_DPDMA is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_QCOM_HIDMA_MGMT=m
CONFIG_QCOM_HIDMA=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_DW_DMAC is not set
# CONFIG_DW_DMAC_PCI is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_DW_EDMA=m
CONFIG_DW_EDMA_PCIE=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SF_PDMA is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# DMA Clients
#
kernel: mvebu-next: Enable offload support for the async_tx api Without enabling this support, the hardware XOR (MV_XOR) is not used by the system. It is enabled in mvebu-default.config Some discussion, https://forum.armbian.com/topic/6033-helios4-support/?do=findComment&comment=69649
2019-01-18 00:00:14 -08:00
CONFIG_ASYNC_TX_DMA=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_DMATEST is not set
CONFIG_DMA_ENGINE_RAID=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
#
# DMABUF options
#
# CONFIG_SYNC_FILE is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_UDMABUF is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_DMABUF_MOVE_NOTIFY is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_DMABUF_SELFTESTS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_DMABUF_HEAPS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of DMABUF options
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AUXDISPLAY=y
CONFIG_HD44780=m
CONFIG_IMG_ASCII_LCD=m
CONFIG_PARPORT_PANEL=m
CONFIG_PANEL_PARPORT=0
CONFIG_PANEL_PROFILE=5
# CONFIG_PANEL_CHANGE_MESSAGE is not set
# CONFIG_CHARLCD_BL_OFF is not set
# CONFIG_CHARLCD_BL_ON is not set
CONFIG_CHARLCD_BL_FLASH=y
CONFIG_PANEL=m
CONFIG_CHARLCD=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_UIO is not set
# CONFIG_VIRT_DRIVERS is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIRTIO=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_VIRTIO_MENU=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_VIRTIO_PCI is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIRTIO_BALLOON=m
CONFIG_VIRTIO_INPUT=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_VIRTIO_MMIO is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VDPA is not set
CONFIG_VHOST_IOTLB=m
CONFIG_VHOST=m
CONFIG_VHOST_MENU=y
CONFIG_VHOST_NET=m
CONFIG_VHOST_SCSI=m
CONFIG_VHOST_VSOCK=m
# CONFIG_VHOST_CROSS_ENDIAN_LEGACY is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Microsoft Hyper-V guest support
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Microsoft Hyper-V guest support
# CONFIG_GREYBUS is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_STAGING=y
# CONFIG_PRISM2_USB is not set
# CONFIG_COMEDI is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_RTL8192U=m
CONFIG_RTLLIB=m
CONFIG_RTLLIB_CRYPTO_CCMP=m
CONFIG_RTLLIB_CRYPTO_TKIP=m
CONFIG_RTLLIB_CRYPTO_WEP=m
CONFIG_RTL8192E=m
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
# CONFIG_RTL8723BS is not set
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_R8712U=m
CONFIG_R8188EU=m
CONFIG_88EU_AP_MODE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_RTS5208 is not set
# CONFIG_VT6655 is not set
# CONFIG_VT6656 is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# IIO staging drivers
#
#
# Accelerometers
#
# CONFIG_ADIS16203 is not set
# CONFIG_ADIS16240 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Accelerometers
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Analog to digital converters
#
# CONFIG_AD7816 is not set
# CONFIG_AD7280 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Analog to digital converters
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Analog digital bi-direction converters
#
# CONFIG_ADT7316 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Analog digital bi-direction converters
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Capacitance to digital converters
#
# CONFIG_AD7150 is not set
# CONFIG_AD7746 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Capacitance to digital converters
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Direct Digital Synthesis
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AD9832=m
CONFIG_AD9834=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Direct Digital Synthesis
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Network Analyzer, Impedance Converters
#
# CONFIG_AD5933 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Network Analyzer, Impedance Converters
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Active energy metering IC
#
# CONFIG_ADE7854 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Active energy metering IC
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Resolver to digital converters
#
# CONFIG_AD2S1210 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Resolver to digital converters
# end of IIO staging drivers
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_STAGING_MEDIA is not set
#
# Android
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Android
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_STAGING_BOARD is not set
# CONFIG_LTE_GDM724X is not set
# CONFIG_GS_FPGABOOT is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_UNISYSSPAR is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MOST_COMPONENTS is not set
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
# CONFIG_KS7010 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_PI433 is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
#
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# Gasket devices
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Gasket devices
CONFIG_XIL_AXIS_FIFO=m
CONFIG_FIELDBUS_DEV=m
CONFIG_HMS_ANYBUSS_BUS=m
CONFIG_ARCX_ANYBUS_CONTROLLER=m
CONFIG_HMS_PROFINET=m
# CONFIG_QLGE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_WFX is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_GOLDFISH is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_CHROME_PLATFORMS is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_MELLANOX_PLATFORM is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_HAVE_CLK=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CLKDEV_LOOKUP=y
CONFIG_HAVE_CLK_PREPARE=y
CONFIG_COMMON_CLK=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_COMMON_CLK_MAX9485=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_COMMON_CLK_SI5341 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_COMMON_CLK_SI5351 is not set
Solidrun Marvell Armada Clearfog kernel 4.4.x config update
2016-02-11 10:04:59 +01:00
# CONFIG_COMMON_CLK_SI514 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_COMMON_CLK_SI544 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_COMMON_CLK_SI570 is not set
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
# CONFIG_COMMON_CLK_CDCE706 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_COMMON_CLK_CDCE925 is not set
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
# CONFIG_COMMON_CLK_CS2000_CP is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CLK_QORIQ=y
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
# CONFIG_COMMON_CLK_PWM is not set
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_COMMON_CLK_VC5 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_COMMON_CLK_BD718XX=m
# CONFIG_COMMON_CLK_FIXED_MMIO is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MVEBU_CLK_COMMON=y
CONFIG_MVEBU_CLK_CPU=y
CONFIG_MVEBU_CLK_COREDIV=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_ARMADA_AP_CP_HELPER=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ARMADA_370_CLK=y
CONFIG_ARMADA_375_CLK=y
CONFIG_ARMADA_38X_CLK=y
CONFIG_ARMADA_39X_CLK=y
CONFIG_ARMADA_XP_CLK=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_ARMADA_AP_CPU_CLK=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_DOVE_CLK=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_HWSPINLOCK is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Clock Source drivers
#
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_TIMER_OF=y
CONFIG_TIMER_PROBE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CLKSRC_MMIO=y
CONFIG_ARMADA_370_XP_TIMER=y
CONFIG_ORION_TIMER=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_ARM_GLOBAL_TIMER=y
CONFIG_CLKSRC_ARM_GLOBAL_TIMER_SCHED_CLOCK=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MICROCHIP_PIT64B is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Clock Source drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_MAILBOX is not set
# CONFIG_IOMMU_SUPPORT is not set
#
# Remoteproc drivers
#
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_REMOTEPROC is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Remoteproc drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Rpmsg drivers
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_RPMSG_VIRTIO is not set
# end of Rpmsg drivers
# CONFIG_SOUNDWIRE is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# SOC (System On Chip) specific Drivers
#
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
#
# Amlogic SoC drivers
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Amlogic SoC drivers
#
# Aspeed SoC drivers
#
# end of Aspeed SoC drivers
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
#
# Broadcom SoC drivers
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SOC_BRCMSTB=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Broadcom SoC drivers
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# NXP/Freescale QorIQ SoC drivers
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_QUICC_ENGINE is not set
# CONFIG_FSL_RCPM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of NXP/Freescale QorIQ SoC drivers
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
#
# i.MX SoC drivers
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of i.MX SoC drivers
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
#
# Qualcomm SoC drivers
#
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_QCOM_QMI_HELPERS=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Qualcomm SoC drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SOC_TI is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Xilinx SoC drivers
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_XILINX_VCU is not set
# end of Xilinx SoC drivers
# end of SOC (System On Chip) specific Drivers
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_PM_DEVFREQ is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_EXTCON=y
#
# Extcon Device Drivers
#
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_EXTCON_ADC_JACK is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_EXTCON_FSA9480=m
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
# CONFIG_EXTCON_GPIO is not set
# CONFIG_EXTCON_MAX3355 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_EXTCON_PTN5150=m
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
# CONFIG_EXTCON_RT8973A is not set
# CONFIG_EXTCON_SM5502 is not set
CONFIG_EXTCON_USB_GPIO=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MEMORY=y
CONFIG_MVEBU_DEVBUS=y
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
CONFIG_IIO=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_IIO_BUFFER=y
CONFIG_IIO_BUFFER_CB=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_IIO_BUFFER_DMA=m
CONFIG_IIO_BUFFER_DMAENGINE=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_IIO_BUFFER_HW_CONSUMER is not set
CONFIG_IIO_KFIFO_BUF=m
CONFIG_IIO_TRIGGERED_BUFFER=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_IIO_CONFIGFS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_IIO_TRIGGER=y
CONFIG_IIO_CONSUMERS_PER_TRIGGER=2
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_IIO_SW_DEVICE is not set
# CONFIG_IIO_SW_TRIGGER is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_IIO_TRIGGERED_EVENT=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Accelerometers
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_ADIS16201=m
CONFIG_ADIS16209=m
CONFIG_ADXL345=m
CONFIG_ADXL345_I2C=m
CONFIG_ADXL345_SPI=m
CONFIG_ADXL372=m
CONFIG_ADXL372_SPI=m
CONFIG_ADXL372_I2C=m
CONFIG_BMA180=m
CONFIG_BMA220=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BMA400 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BMC150_ACCEL=m
CONFIG_BMC150_ACCEL_I2C=m
CONFIG_BMC150_ACCEL_SPI=m
CONFIG_DA280=m
CONFIG_DA311=m
CONFIG_DMARD06=m
CONFIG_DMARD09=m
CONFIG_DMARD10=m
CONFIG_IIO_ST_ACCEL_3AXIS=m
CONFIG_IIO_ST_ACCEL_I2C_3AXIS=m
CONFIG_IIO_ST_ACCEL_SPI_3AXIS=m
CONFIG_KXSD9=m
CONFIG_KXSD9_SPI=m
CONFIG_KXSD9_I2C=m
CONFIG_KXCJK1013=m
CONFIG_MC3230=m
CONFIG_MMA7455=m
CONFIG_MMA7455_I2C=m
CONFIG_MMA7455_SPI=m
CONFIG_MMA7660=m
CONFIG_MMA8452=m
CONFIG_MMA9551_CORE=m
CONFIG_MMA9551=m
CONFIG_MMA9553=m
CONFIG_MXC4005=m
CONFIG_MXC6255=m
CONFIG_SCA3000=m
CONFIG_STK8312=m
CONFIG_STK8BA50=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Accelerometers
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Analog to digital converters
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AD_SIGMA_DELTA=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_AD7091R5 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AD7124=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_AD7192 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AD7266=m
CONFIG_AD7291=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_AD7292 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AD7298=m
CONFIG_AD7476=m
CONFIG_AD7606=m
CONFIG_AD7606_IFACE_PARALLEL=m
CONFIG_AD7606_IFACE_SPI=m
CONFIG_AD7766=m
CONFIG_AD7768_1=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_AD7780 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AD7791=m
CONFIG_AD7793=m
CONFIG_AD7887=m
CONFIG_AD7923=m
CONFIG_AD7949=m
CONFIG_AD799X=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_AD9467 is not set
# CONFIG_ADI_AXI_ADC is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CC10001_ADC=m
CONFIG_ENVELOPE_DETECTOR=m
CONFIG_HI8435=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_HX711 is not set
# CONFIG_INA2XX_ADC is not set
# CONFIG_LTC2471 is not set
# CONFIG_LTC2485 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_LTC2496 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_LTC2497=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_MAX1027 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MAX11100=m
CONFIG_MAX1118=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_MAX1241 is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_MAX1363 is not set
# CONFIG_MAX9611 is not set
# CONFIG_MCP320X is not set
# CONFIG_MCP3422 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MCP3911=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_NAU7802 is not set
# CONFIG_SD_ADC_MODULATOR is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_TI_ADC081C=m
CONFIG_TI_ADC0832=m
CONFIG_TI_ADC084S021=m
CONFIG_TI_ADC12138=m
CONFIG_TI_ADC108S102=m
CONFIG_TI_ADC128S052=m
CONFIG_TI_ADC161S626=m
CONFIG_TI_ADS1015=m
CONFIG_TI_ADS7950=m
CONFIG_TI_ADS8344=m
CONFIG_TI_ADS8688=m
CONFIG_TI_ADS124S08=m
CONFIG_TI_TLC4541=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_VF610_ADC is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_XILINX_XADC=m
# end of Analog to digital converters
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Analog Front Ends
#
# CONFIG_IIO_RESCALE is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Analog Front Ends
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Amplifiers
#
# CONFIG_AD8366 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_HMC425 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Amplifiers
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Chemical Sensors
#
# CONFIG_ATLAS_PH_SENSOR is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ATLAS_EZO_SENSOR is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BME680=m
CONFIG_BME680_I2C=m
CONFIG_BME680_SPI=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_CCS811 is not set
# CONFIG_IAQCORE is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_PMS7003=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_SCD30_CORE is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SENSIRION_SGP30=m
CONFIG_SPS30=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_VZ89X is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Chemical Sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Hid Sensor IIO Common
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Hid Sensor IIO Common
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_IIO_MS_SENSORS_I2C=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# SSP Sensor Common
#
# CONFIG_IIO_SSP_SENSORHUB is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of SSP Sensor Common
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_IIO_ST_SENSORS_I2C=m
CONFIG_IIO_ST_SENSORS_SPI=m
CONFIG_IIO_ST_SENSORS_CORE=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Digital to analog converters
#
# CONFIG_AD5064 is not set
# CONFIG_AD5360 is not set
# CONFIG_AD5380 is not set
# CONFIG_AD5421 is not set
# CONFIG_AD5446 is not set
# CONFIG_AD5449 is not set
# CONFIG_AD5592R is not set
# CONFIG_AD5593R is not set
# CONFIG_AD5504 is not set
# CONFIG_AD5624R_SPI is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AD5686=m
CONFIG_AD5686_SPI=m
CONFIG_AD5696_I2C=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_AD5755 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AD5758=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_AD5761 is not set
# CONFIG_AD5764 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_AD5770R is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_AD5791 is not set
# CONFIG_AD7303 is not set
# CONFIG_AD8801 is not set
# CONFIG_DPOT_DAC is not set
# CONFIG_DS4424 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_LTC1660=m
# CONFIG_LTC2632 is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_M62332 is not set
# CONFIG_MAX517 is not set
# CONFIG_MAX5821 is not set
# CONFIG_MCP4725 is not set
# CONFIG_MCP4922 is not set
# CONFIG_TI_DAC082S085 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_TI_DAC5571=m
CONFIG_TI_DAC7311=m
CONFIG_TI_DAC7612=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_VF610_DAC is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Digital to analog converters
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# IIO dummy driver
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of IIO dummy driver
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Frequency Synthesizers DDS/PLL
#
#
# Clock Generator/Distribution
#
# CONFIG_AD9523 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Clock Generator/Distribution
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Phase-Locked Loop (PLL) frequency synthesizers
#
# CONFIG_ADF4350 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_ADF4371=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Phase-Locked Loop (PLL) frequency synthesizers
# end of Frequency Synthesizers DDS/PLL
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Digital gyroscope sensors
#
# CONFIG_ADIS16080 is not set
# CONFIG_ADIS16130 is not set
# CONFIG_ADIS16136 is not set
# CONFIG_ADIS16260 is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_ADXRS290=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_ADXRS450 is not set
# CONFIG_BMG160 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_FXAS21002C is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_MPU3050_I2C is not set
# CONFIG_IIO_ST_GYRO_3AXIS is not set
# CONFIG_ITG3200 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Digital gyroscope sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Health Sensors
#
#
# Heart Rate Monitors
#
# CONFIG_AFE4403 is not set
# CONFIG_AFE4404 is not set
# CONFIG_MAX30100 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MAX30102=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Heart Rate Monitors
# end of Health Sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Humidity sensors
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AM2315=m
CONFIG_DHT11=m
CONFIG_HDC100X=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_HDC2010=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HTS221=m
CONFIG_HTS221_I2C=m
CONFIG_HTS221_SPI=m
CONFIG_HTU21=m
CONFIG_SI7005=m
CONFIG_SI7020=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Humidity sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Inertial measurement units
#
# CONFIG_ADIS16400 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_ADIS16460 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ADIS16475 is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_ADIS16480 is not set
# CONFIG_BMI160_I2C is not set
# CONFIG_BMI160_SPI is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_FXOS8700_I2C is not set
# CONFIG_FXOS8700_SPI is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_KMX61 is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_INV_ICM42600_I2C is not set
# CONFIG_INV_ICM42600_SPI is not set
Update linux-mvebu-current.config (#1707)
2020-01-02 10:58:10 +01:00
# CONFIG_INV_MPU6050_I2C is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_INV_MPU6050_SPI is not set
# CONFIG_IIO_ST_LSM6DSX is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Inertial measurement units
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_IIO_ADIS_LIB=m
CONFIG_IIO_ADIS_LIB_BUFFER=y
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Light sensors
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_ADJD_S311=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ADUX1020 is not set
# CONFIG_AL3010 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AL3320A=m
CONFIG_APDS9300=m
CONFIG_APDS9960=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_AS73211=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_BH1750=m
CONFIG_BH1780=m
CONFIG_CM32181=m
CONFIG_CM3232=m
CONFIG_CM3323=m
CONFIG_CM3605=m
CONFIG_CM36651=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_GP2AP002 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_GP2AP020A00F=m
CONFIG_SENSORS_ISL29018=m
CONFIG_SENSORS_ISL29028=m
CONFIG_ISL29125=m
CONFIG_JSA1212=m
CONFIG_RPR0521=m
CONFIG_LTR501=m
CONFIG_LV0104CS=m
CONFIG_MAX44000=m
CONFIG_MAX44009=m
CONFIG_NOA1305=m
CONFIG_OPT3001=m
CONFIG_PA12203001=m
CONFIG_SI1133=m
CONFIG_SI1145=m
CONFIG_STK3310=m
CONFIG_ST_UVIS25=m
CONFIG_ST_UVIS25_I2C=m
CONFIG_ST_UVIS25_SPI=m
CONFIG_TCS3414=m
CONFIG_TCS3472=m
CONFIG_SENSORS_TSL2563=m
CONFIG_TSL2583=m
CONFIG_TSL2772=m
CONFIG_TSL4531=m
CONFIG_US5182D=m
CONFIG_VCNL4000=m
CONFIG_VCNL4035=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VEML6030 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VEML6070=m
CONFIG_VL6180=m
CONFIG_ZOPT2201=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Light sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Magnetometer sensors
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AK8974=m
CONFIG_AK8975=m
CONFIG_AK09911=m
CONFIG_BMC150_MAGN=m
CONFIG_BMC150_MAGN_I2C=m
CONFIG_BMC150_MAGN_SPI=m
CONFIG_MAG3110=m
CONFIG_MMC35240=m
CONFIG_IIO_ST_MAGN_3AXIS=m
CONFIG_IIO_ST_MAGN_I2C_3AXIS=m
CONFIG_IIO_ST_MAGN_SPI_3AXIS=m
CONFIG_SENSORS_HMC5843=m
CONFIG_SENSORS_HMC5843_I2C=m
CONFIG_SENSORS_HMC5843_SPI=m
CONFIG_SENSORS_RM3100=m
CONFIG_SENSORS_RM3100_I2C=m
CONFIG_SENSORS_RM3100_SPI=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Magnetometer sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Multiplexers
#
# CONFIG_IIO_MUX is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Multiplexers
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Inclinometer sensors
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Inclinometer sensors
#
# Triggers - standalone
#
CONFIG_IIO_INTERRUPT_TRIGGER=m
CONFIG_IIO_SYSFS_TRIGGER=m
# end of Triggers - standalone
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
#
# Linear and angular position sensors
#
# end of Linear and angular position sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Digital potentiometers
#
# CONFIG_AD5272 is not set
# CONFIG_DS1803 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MAX5432=m
CONFIG_MAX5481=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_MAX5487 is not set
# CONFIG_MCP4018 is not set
# CONFIG_MCP4131 is not set
# CONFIG_MCP4531 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MCP41010=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_TPL0102 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Digital potentiometers
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Digital potentiostats
#
# CONFIG_LMP91000 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Digital potentiostats
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Pressure sensors
#
# CONFIG_ABP060MG is not set
CONFIG_BMP280=m
CONFIG_BMP280_I2C=m
CONFIG_BMP280_SPI=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_DLHL60D is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_DPS310=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_HP03 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_ICP10100 is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_MPL115_I2C is not set
# CONFIG_MPL115_SPI is not set
# CONFIG_MPL3115 is not set
# CONFIG_MS5611 is not set
# CONFIG_MS5637 is not set
# CONFIG_IIO_ST_PRESS is not set
# CONFIG_T5403 is not set
# CONFIG_HP206C is not set
# CONFIG_ZPA2326 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Pressure sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Lightning sensors
#
# CONFIG_AS3935 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Lightning sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Proximity and distance sensors
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_ISL29501=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_LIDAR_LITE_V2 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MB1232=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PING is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_RFD77402 is not set
# CONFIG_SRF04 is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SX9310 is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_SX9500 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SRF08=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_VCNL3020 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VL53L0X_I2C=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Proximity and distance sensors
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Resolver to digital converters
#
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_AD2S90 is not set
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_AD2S1200 is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Resolver to digital converters
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
#
# Temperature sensors
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_LTC2983 is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MAXIM_THERMOCOUPLE=m
CONFIG_MLX90614=m
CONFIG_MLX90632=m
CONFIG_TMP006=m
CONFIG_TMP007=m
Enable IIO and add bmp280 sensor module
2019-08-02 13:08:36 +02:00
# CONFIG_TSYS01 is not set
# CONFIG_TSYS02D is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_MAX31856 is not set
# end of Temperature sensors
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_NTB is not set
# CONFIG_VME_BUS is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
CONFIG_PWM=y
CONFIG_PWM_SYSFS=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PWM_DEBUG is not set
enable "next" branch on Helios4
2017-12-30 16:41:37 +08:00
# CONFIG_PWM_FSL_FTM is not set
# CONFIG_PWM_PCA9685 is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# IRQ chip support
#
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_IRQCHIP=y
CONFIG_ARM_GIC=y
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_ARM_GIC_MAX_NR=1
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_ARMADA_370_XP_IRQ=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_AL_FIC is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ORION_IRQCHIP=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of IRQ chip support
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_IPACK_BUS is not set
# CONFIG_RESET_CONTROLLER is not set
#
# PHY Subsystem
#
CONFIG_GENERIC_PHY=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_GENERIC_PHY_MIPI_DPHY=y
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_USB_LGM_PHY=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_BCM_KONA_USB2_PHY is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PHY_CADENCE_TORRENT is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_PHY_CADENCE_DPHY is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PHY_CADENCE_SALVO is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_PHY_FSL_IMX8MQ_USB=m
CONFIG_PHY_MIXEL_MIPI_DPHY=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ARMADA375_USBCLUSTER_PHY=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_PHY_MVEBU_A3700_COMPHY=m
CONFIG_PHY_MVEBU_A3700_UTMI=m
CONFIG_PHY_MVEBU_A38X_COMPHY=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_PHY_MVEBU_CP110_COMPHY=m
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
CONFIG_PHY_MVEBU_SATA=y
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_PHY_PXA_28NM_HSIC=m
CONFIG_PHY_PXA_28NM_USB2=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_PHY_CPCAP_USB=m
# CONFIG_PHY_MAPPHONE_MDM6600 is not set
CONFIG_PHY_OCELOT_SERDES=m
# end of PHY Subsystem
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_POWERCAP is not set
# CONFIG_MCB is not set
#
# Performance monitor support
#
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ARM_CCI_PMU=m
# CONFIG_ARM_CCI400_PMU is not set
# CONFIG_ARM_CCI5xx_PMU is not set
# CONFIG_ARM_CCN is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ARM_PMU=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Performance monitor support
CONFIG_RAS=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_USB4 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Android
#
# CONFIG_ANDROID is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Android
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DAX=m
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_NVMEM=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_NVMEM_SYSFS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
#
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# HW tracing support
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_STM=m
CONFIG_STM_PROTO_BASIC=m
CONFIG_STM_PROTO_SYS_T=m
CONFIG_STM_DUMMY=m
CONFIG_STM_SOURCE_CONSOLE=m
# CONFIG_STM_SOURCE_HEARTBEAT is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_INTEL_TH is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of HW tracing support
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_FPGA is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_FSI=m
# CONFIG_FSI_NEW_DEV_NODE is not set
# CONFIG_FSI_MASTER_GPIO is not set
# CONFIG_FSI_MASTER_HUB is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_FSI_MASTER_ASPEED is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_FSI_SCOM is not set
# CONFIG_FSI_SBEFIFO is not set
CONFIG_TEE=m
#
# TEE drivers
#
CONFIG_OPTEE=m
CONFIG_OPTEE_SHM_NUM_PRIV_PAGES=1
# end of TEE drivers
CONFIG_MULTIPLEXER=m
#
# Multiplexer drivers
#
CONFIG_MUX_ADG792A=m
CONFIG_MUX_ADGS1408=m
CONFIG_MUX_GPIO=m
CONFIG_MUX_MMIO=m
# end of Multiplexer drivers
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_PM_OPP=y
# CONFIG_SIOX is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_SLIMBUS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_INTERCONNECT is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_COUNTER=m
CONFIG_FTM_QUADDEC=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_MICROCHIP_TCB_CAPTURE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_MOST=m
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_MOST_USB_HDM is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_MOST_CDEV=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Device Drivers
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# File systems
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
CONFIG_DCACHE_WORD_ACCESS=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_VALIDATE_FS_PARSER=y
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_FS_IOMAP=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_EXT4_FS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_EXT4_DEBUG is not set
CONFIG_JBD2=y
# CONFIG_JBD2_DEBUG is not set
CONFIG_FS_MBCACHE=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_REISERFS_FS=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_REISERFS_CHECK is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_JFS_FS=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_JFS_POSIX_ACL=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_JFS_SECURITY=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_JFS_DEBUG is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_JFS_STATISTICS=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_XFS_FS=m
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_XFS_SUPPORT_V4=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_XFS_QUOTA=y
CONFIG_XFS_POSIX_ACL=y
CONFIG_XFS_RT=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_XFS_ONLINE_SCRUB is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_XFS_WARN is not set
# CONFIG_XFS_DEBUG is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_GFS2_FS=m
CONFIG_GFS2_FS_LOCKING_DLM=y
CONFIG_OCFS2_FS=m
CONFIG_OCFS2_FS_O2CB=m
CONFIG_OCFS2_FS_USERSPACE_CLUSTER=m
CONFIG_OCFS2_FS_STATS=y
CONFIG_OCFS2_DEBUG_MASKLOG=y
# CONFIG_OCFS2_DEBUG_FS is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_BTRFS_FS=y
CONFIG_BTRFS_FS_POSIX_ACL=y
# CONFIG_BTRFS_FS_CHECK_INTEGRITY is not set
# CONFIG_BTRFS_FS_RUN_SANITY_TESTS is not set
# CONFIG_BTRFS_DEBUG is not set
# CONFIG_BTRFS_ASSERT is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_BTRFS_FS_REF_VERIFY is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NILFS2_FS=m
CONFIG_F2FS_FS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_F2FS_STAT_FS=y
CONFIG_F2FS_FS_XATTR=y
CONFIG_F2FS_FS_POSIX_ACL=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_F2FS_FS_SECURITY=y
CONFIG_F2FS_CHECK_FS=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
# CONFIG_F2FS_FAULT_INJECTION is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_F2FS_FS_COMPRESSION is not set
# CONFIG_ZONEFS_FS is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_FS_POSIX_ACL=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_EXPORTFS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_EXPORTFS_BLOCK_OPS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_FILE_LOCKING=y
Clearfog next patches fix for 4.5.1
2016-04-19 10:37:25 +02:00
CONFIG_MANDATORY_FILE_LOCKING=y
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_FS_ENCRYPTION=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_FS_ENCRYPTION_ALGS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_FS_VERITY=y
# CONFIG_FS_VERITY_DEBUG is not set
CONFIG_FS_VERITY_BUILTIN_SIGNATURES=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_FANOTIFY=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
Make kernels OMV friendly -- see #36
2017-04-02 16:06:55 +02:00
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
Add cpufreq support for mvebu-next
2017-04-15 13:12:05 +03:00
# CONFIG_PRINT_QUOTA_WARNING is not set
# CONFIG_QUOTA_DEBUG is not set
CONFIG_QUOTA_TREE=m
CONFIG_QFMT_V1=m
CONFIG_QFMT_V2=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_QUOTACTL=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_AUTOFS4_FS=m
CONFIG_AUTOFS_FS=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_FUSE_FS=y
CONFIG_CUSE=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VIRTIO_FS=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_OVERLAY_FS=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
# CONFIG_OVERLAY_FS_REDIRECT_DIR is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW=y
Update mvebu-next to 4.13
2017-09-06 13:22:18 +03:00
# CONFIG_OVERLAY_FS_INDEX is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_OVERLAY_FS_METACOPY is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Caches
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_FSCACHE=m
CONFIG_FSCACHE_STATS=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
# CONFIG_FSCACHE_HISTOGRAM is not set
# CONFIG_FSCACHE_DEBUG is not set
# CONFIG_FSCACHE_OBJECT_LIST is not set
Update mvebu kernel configs
2017-05-28 19:22:20 +03:00
CONFIG_CACHEFILES=m
# CONFIG_CACHEFILES_DEBUG is not set
# CONFIG_CACHEFILES_HISTOGRAM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Caches
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# CD-ROM/DVD Filesystems
#
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_ISO9660_FS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_JOLIET=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_ZISOFS=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_UDF_FS=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of CD-ROM/DVD Filesystems
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# DOS/FAT/EXFAT/NT Filesystems
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
CONFIG_FAT_FS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MSDOS_FS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_FAT_DEFAULT_UTF8=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_EXFAT_FS=m
CONFIG_EXFAT_DEFAULT_IOCHARSET="utf8"
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NTFS_RW=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# end of DOS/FAT/EXFAT/NT Filesystems
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_SYSCTL=y
CONFIG_PROC_PAGE_MONITOR=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_PROC_CHILDREN=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_KERNFS=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MEMFD_CREATE=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_CONFIGFS_FS=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Pseudo filesystems
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_MISC_FILESYSTEMS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_ORANGEFS_FS=m
CONFIG_ADFS_FS=m
# CONFIG_ADFS_FS_RW is not set
CONFIG_AFFS_FS=m
CONFIG_ECRYPT_FS=y
CONFIG_ECRYPT_FS_MESSAGING=y
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=m
CONFIG_EFS_FS=m
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_JFFS2_FS_WRITEBUFFER=y
# CONFIG_JFFS2_FS_WBUF_VERIFY is not set
# CONFIG_JFFS2_SUMMARY is not set
CONFIG_JFFS2_FS_XATTR=y
CONFIG_JFFS2_FS_POSIX_ACL=y
CONFIG_JFFS2_FS_SECURITY=y
CONFIG_JFFS2_COMPRESSION_OPTIONS=y
CONFIG_JFFS2_ZLIB=y
CONFIG_JFFS2_LZO=y
CONFIG_JFFS2_RTIME=y
# CONFIG_JFFS2_RUBIN is not set
# CONFIG_JFFS2_CMODE_NONE is not set
# CONFIG_JFFS2_CMODE_PRIORITY is not set
# CONFIG_JFFS2_CMODE_SIZE is not set
CONFIG_JFFS2_CMODE_FAVOURLZO=y
CONFIG_CRAMFS=m
CONFIG_CRAMFS_BLOCKDEV=y
CONFIG_CRAMFS_MTD=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_SQUASHFS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_SQUASHFS_FILE_CACHE is not set
CONFIG_SQUASHFS_FILE_DIRECT=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_SQUASHFS_DECOMP_SINGLE is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_SQUASHFS_DECOMP_MULTI is not set
CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_SQUASHFS_XATTR=y
CONFIG_SQUASHFS_ZLIB=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SQUASHFS_LZ4=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_SQUASHFS_LZO=y
CONFIG_SQUASHFS_XZ=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_SQUASHFS_ZSTD=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_SQUASHFS_4K_DEVBLK_SIZE=y
CONFIG_SQUASHFS_EMBEDDED=y
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_VXFS_FS=m
CONFIG_MINIX_FS=m
CONFIG_OMFS_FS=m
CONFIG_HPFS_FS=m
CONFIG_QNX4FS_FS=m
CONFIG_QNX6FS_FS=m
# CONFIG_QNX6FS_DEBUG is not set
CONFIG_ROMFS_FS=m
CONFIG_ROMFS_BACKED_BY_BLOCK=y
# CONFIG_ROMFS_BACKED_BY_MTD is not set
# CONFIG_ROMFS_BACKED_BY_BOTH is not set
CONFIG_ROMFS_ON_BLOCK=y
CONFIG_PSTORE=y
CONFIG_PSTORE_DEFLATE_COMPRESS=y
CONFIG_PSTORE_LZO_COMPRESS=m
CONFIG_PSTORE_LZ4_COMPRESS=m
CONFIG_PSTORE_LZ4HC_COMPRESS=m
CONFIG_PSTORE_842_COMPRESS=y
# CONFIG_PSTORE_ZSTD_COMPRESS is not set
CONFIG_PSTORE_COMPRESS=y
CONFIG_PSTORE_DEFLATE_COMPRESS_DEFAULT=y
# CONFIG_PSTORE_LZO_COMPRESS_DEFAULT is not set
# CONFIG_PSTORE_LZ4_COMPRESS_DEFAULT is not set
# CONFIG_PSTORE_LZ4HC_COMPRESS_DEFAULT is not set
# CONFIG_PSTORE_842_COMPRESS_DEFAULT is not set
CONFIG_PSTORE_COMPRESS_DEFAULT="deflate"
# CONFIG_PSTORE_CONSOLE is not set
# CONFIG_PSTORE_PMSG is not set
CONFIG_PSTORE_RAM=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PSTORE_BLK is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SYSV_FS=m
CONFIG_UFS_FS=m
CONFIG_UFS_FS_WRITE=y
# CONFIG_UFS_DEBUG is not set
CONFIG_EROFS_FS=m
# CONFIG_EROFS_FS_DEBUG is not set
CONFIG_EROFS_FS_XATTR=y
CONFIG_EROFS_FS_POSIX_ACL=y
CONFIG_EROFS_FS_SECURITY=y
# CONFIG_EROFS_FS_ZIP is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_AUFS_FS=m
CONFIG_AUFS_BRANCH_MAX_127=y
# CONFIG_AUFS_BRANCH_MAX_511 is not set
# CONFIG_AUFS_BRANCH_MAX_1023 is not set
# CONFIG_AUFS_BRANCH_MAX_32767 is not set
CONFIG_AUFS_SBILIST=y
# CONFIG_AUFS_HNOTIFY is not set
# CONFIG_AUFS_EXPORT is not set
# CONFIG_AUFS_XATTR is not set
# CONFIG_AUFS_FHSM is not set
# CONFIG_AUFS_RDU is not set
# CONFIG_AUFS_DIRREN is not set
# CONFIG_AUFS_SHWH is not set
# CONFIG_AUFS_BR_RAMFS is not set
# CONFIG_AUFS_BR_FUSE is not set
CONFIG_AUFS_BR_HFSPLUS=y
CONFIG_AUFS_BDEV_LOOP=y
# CONFIG_AUFS_DEBUG is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NETWORK_FILESYSTEMS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NFS_FS=m
CONFIG_NFS_V2=m
CONFIG_NFS_V3=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFS_V3_ACL=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NFS_V4=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFS_SWAP=y
Update mvebu kernel configs
2017-05-28 19:22:20 +03:00
CONFIG_NFS_V4_1=y
CONFIG_NFS_V4_2=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_PNFS_FILE_LAYOUT=m
CONFIG_PNFS_BLOCK=m
Update mvebu kernel configs
2017-05-28 19:22:20 +03:00
CONFIG_PNFS_FLEXFILE_LAYOUT=m
CONFIG_NFS_V4_1_IMPLEMENTATION_ID_DOMAIN="kernel.org"
CONFIG_NFS_V4_1_MIGRATION=y
CONFIG_NFS_V4_SECURITY_LABEL=y
CONFIG_NFS_FSCACHE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NFS_DEBUG=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_NFS_DISABLE_UDP_SUPPORT=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_NFS_V4_2_READ_PLUS is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NFSD=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NFSD_PNFS=y
CONFIG_NFSD_BLOCKLAYOUT=y
CONFIG_NFSD_SCSILAYOUT=y
CONFIG_NFSD_FLEXFILELAYOUT=y
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_NFSD_V4_2_INTER_SSC is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NFSD_V4_SECURITY_LABEL=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_GRACE_PERIOD=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_NFS_ACL_SUPPORT=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_SUNRPC_GSS=y
Update mvebu kernel configs
2017-05-28 19:22:20 +03:00
CONFIG_SUNRPC_BACKCHANNEL=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_SUNRPC_SWAP=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_RPCSEC_GSS_KRB5=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_SUNRPC_DISABLE_INSECURE_ENCTYPES is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SUNRPC_DEBUG=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CEPH_FS=m
Consolidate CEPH and CIFS settings
2018-09-04 22:04:13 +02:00
CONFIG_CEPH_FSCACHE=y
CONFIG_CEPH_FS_POSIX_ACL=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CEPH_FS_SECURITY_LABEL=y
Consolidate CEPH and CIFS settings
2018-09-04 22:04:13 +02:00
CONFIG_CIFS=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CIFS_STATS2=y
[ general ] Attach Realtek 8811, 8812, 8814 and 8821 drivers source, remove our old patches, adjust configs, tested on all combinations
2019-02-07 15:24:06 +01:00
CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CIFS_WEAK_PW_HASH=y
Consolidate CEPH and CIFS settings
2018-09-04 22:04:13 +02:00
CONFIG_CIFS_UPCALL=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CIFS_XATTR=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CIFS_POSIX=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CIFS_DEBUG=y
# CONFIG_CIFS_DEBUG2 is not set
# CONFIG_CIFS_DEBUG_DUMP_KEYS is not set
CONFIG_CIFS_DFS_UPCALL=y
Update mvebu kernel configs
2017-05-28 19:22:20 +03:00
CONFIG_CIFS_FSCACHE=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CODA_FS=m
CONFIG_AFS_FS=m
# CONFIG_AFS_DEBUG is not set
CONFIG_AFS_FSCACHE=y
# CONFIG_AFS_DEBUG_CURSOR is not set
Update mvebu kernel configs
2017-05-28 19:22:20 +03:00
CONFIG_9P_FS=m
CONFIG_9P_FSCACHE=y
CONFIG_9P_FS_POSIX_ACL=y
CONFIG_9P_FS_SECURITY=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NLS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NLS_DEFAULT="utf8"
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NLS_CODEPAGE_437=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_NLS_CODEPAGE_737=m
CONFIG_NLS_CODEPAGE_775=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
CONFIG_NLS_CODEPAGE_855=m
CONFIG_NLS_CODEPAGE_857=m
CONFIG_NLS_CODEPAGE_860=m
CONFIG_NLS_CODEPAGE_861=m
CONFIG_NLS_CODEPAGE_862=m
CONFIG_NLS_CODEPAGE_863=m
CONFIG_NLS_CODEPAGE_864=m
CONFIG_NLS_CODEPAGE_865=m
CONFIG_NLS_CODEPAGE_866=m
CONFIG_NLS_CODEPAGE_869=m
CONFIG_NLS_CODEPAGE_936=m
CONFIG_NLS_CODEPAGE_950=m
CONFIG_NLS_CODEPAGE_932=m
CONFIG_NLS_CODEPAGE_949=m
CONFIG_NLS_CODEPAGE_874=m
CONFIG_NLS_ISO8859_8=m
CONFIG_NLS_CODEPAGE_1250=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
CONFIG_NLS_ISO8859_3=m
CONFIG_NLS_ISO8859_4=m
CONFIG_NLS_ISO8859_5=m
CONFIG_NLS_ISO8859_6=m
CONFIG_NLS_ISO8859_7=m
CONFIG_NLS_ISO8859_9=m
CONFIG_NLS_ISO8859_13=m
CONFIG_NLS_ISO8859_14=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_KOI8_R=m
CONFIG_NLS_KOI8_U=m
CONFIG_NLS_MAC_ROMAN=m
CONFIG_NLS_MAC_CELTIC=m
CONFIG_NLS_MAC_CENTEURO=m
CONFIG_NLS_MAC_CROATIAN=m
CONFIG_NLS_MAC_CYRILLIC=m
CONFIG_NLS_MAC_GAELIC=m
CONFIG_NLS_MAC_GREEK=m
CONFIG_NLS_MAC_ICELAND=m
CONFIG_NLS_MAC_INUIT=m
CONFIG_NLS_MAC_ROMANIAN=m
CONFIG_NLS_MAC_TURKISH=m
CONFIG_NLS_UTF8=m
CONFIG_DLM=m
# CONFIG_DLM_DEBUG is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_UNICODE=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_UNICODE_NORMALIZATION_SELFTEST is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_IO_WQ=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of File systems
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Security options
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_KEYS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_KEYS_REQUEST_CACHE=y
CONFIG_PERSISTENT_KEYRINGS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ENCRYPTED_KEYS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_KEY_DH_OPERATIONS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_SECURITY_DMESG_RESTRICT is not set
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_SECURITY=y
CONFIG_SECURITYFS=y
CONFIG_SECURITY_NETWORK=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SECURITY_NETWORK_XFRM=y
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_SECURITY_PATH=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_LSM_MMAP_MIN_ADDR=0
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_HAVE_HARDENED_USERCOPY_ALLOCATOR=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_HARDENED_USERCOPY=y
CONFIG_HARDENED_USERCOPY_FALLBACK=y
CONFIG_FORTIFY_SOURCE=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_STATIC_USERMODEHELPER is not set
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
# CONFIG_SECURITY_SELINUX_DISABLE is not set
CONFIG_SECURITY_SELINUX_DEVELOP=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_SECURITY_SELINUX_SIDTAB_HASH_BITS=9
CONFIG_SECURITY_SELINUX_SID2STR_CACHE_SIZE=256
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SECURITY_SMACK=y
# CONFIG_SECURITY_SMACK_BRINGUP is not set
CONFIG_SECURITY_SMACK_NETFILTER=y
CONFIG_SECURITY_SMACK_APPEND_SIGNALS=y
CONFIG_SECURITY_TOMOYO=y
CONFIG_SECURITY_TOMOYO_MAX_ACCEPT_ENTRY=2048
CONFIG_SECURITY_TOMOYO_MAX_AUDIT_LOG=1024
# CONFIG_SECURITY_TOMOYO_OMIT_USERSPACE_LOADER is not set
CONFIG_SECURITY_TOMOYO_POLICY_LOADER="/sbin/tomoyo-init"
CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER="/sbin/init"
# CONFIG_SECURITY_TOMOYO_INSECURE_BUILTIN_SETTING is not set
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_SECURITY_APPARMOR=y
CONFIG_SECURITY_APPARMOR_HASH=y
CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
# CONFIG_SECURITY_APPARMOR_DEBUG is not set
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
# CONFIG_SECURITY_LOADPIN is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SECURITY_YAMA=y
CONFIG_SECURITY_SAFESETID=y
CONFIG_SECURITY_LOCKDOWN_LSM=y
CONFIG_SECURITY_LOCKDOWN_LSM_EARLY=y
CONFIG_LOCK_DOWN_KERNEL_FORCE_NONE=y
# CONFIG_LOCK_DOWN_KERNEL_FORCE_INTEGRITY is not set
# CONFIG_LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY is not set
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_INTEGRITY=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_INTEGRITY_SIGNATURE=y
CONFIG_INTEGRITY_ASYMMETRIC_KEYS=y
CONFIG_INTEGRITY_TRUSTED_KEYRING=y
CONFIG_INTEGRITY_PLATFORM_KEYRING=y
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_INTEGRITY_AUDIT=y
# CONFIG_IMA is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY is not set
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
# CONFIG_EVM is not set
# CONFIG_DEFAULT_SECURITY_SELINUX is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_DEFAULT_SECURITY_SMACK is not set
# CONFIG_DEFAULT_SECURITY_TOMOYO is not set
CONFIG_DEFAULT_SECURITY_APPARMOR=y
# CONFIG_DEFAULT_SECURITY_DAC is not set
CONFIG_LSM="lockdown,yama,integrity,apparmor"
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Kernel hardening options
#
#
# Memory initialization
#
CONFIG_INIT_STACK_NONE=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_INIT_ON_FREE_DEFAULT_ON is not set
# end of Memory initialization
# end of Kernel hardening options
# end of Security options
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_XOR_BLOCKS=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_ASYNC_CORE=m
CONFIG_ASYNC_MEMCPY=m
CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO=y
#
# Crypto core or helper
#
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_ALGAPI2=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_AEAD=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_AEAD2=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_CRYPTO_SKCIPHER=y
CONFIG_CRYPTO_SKCIPHER2=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_HASH2=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_RNG=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_RNG2=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_RNG_DEFAULT=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_AKCIPHER2=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_AKCIPHER=y
Enable a bunch of networking options for marvell
2016-10-31 19:42:26 +03:00
CONFIG_CRYPTO_KPP2=y
CONFIG_CRYPTO_KPP=y
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_CRYPTO_ACOMP2=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_MANAGER2=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_USER=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_MANAGER_DISABLE_TESTS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_GF128MUL=y
CONFIG_CRYPTO_NULL=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_NULL2=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_PCRYPT=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_CRYPTD=y
CONFIG_CRYPTO_AUTHENC=m
CONFIG_CRYPTO_TEST=m
Update mvebu-next to 4.10.x
2017-02-26 20:33:09 +03:00
CONFIG_CRYPTO_SIMD=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_ENGINE=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Public-key cryptography
#
CONFIG_CRYPTO_RSA=y
CONFIG_CRYPTO_DH=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_ECC=m
CONFIG_CRYPTO_ECDH=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_ECRDSA=m
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_CRYPTO_SM2=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_CRYPTO_CURVE25519 is not set
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Authenticated Encryption with Associated Data
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_CCM=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_GCM=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_CHACHA20POLY1305=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CRYPTO_AEGIS128=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_AEGIS128_SIMD=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_SEQIV=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_ECHAINIV=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Block modes
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_CBC=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CRYPTO_CFB=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_CTR=y
CONFIG_CRYPTO_CTS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_ECB=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_LRW=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_OFB=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_PCBC=m
CONFIG_CRYPTO_XTS=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_KEYWRAP=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_NHPOLY1305=m
CONFIG_CRYPTO_ADIANTUM=m
CONFIG_CRYPTO_ESSIV=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Hash modes
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_CMAC=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_VMAC=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Digest
#
CONFIG_CRYPTO_CRC32C=y
Clearfog fixes for Vanilla kernel, configuration update
2016-06-21 10:20:45 +02:00
CONFIG_CRYPTO_CRC32=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_CRYPTO_XXHASH=y
CONFIG_CRYPTO_BLAKE2B=y
# CONFIG_CRYPTO_BLAKE2S is not set
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_CRYPTO_CRCT10DIF=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_GHASH=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_POLY1305=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_MD4=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_MD5=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_CRYPTO_MICHAEL_MIC=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_RMD128=m
CONFIG_CRYPTO_RMD160=m
CONFIG_CRYPTO_RMD256=m
CONFIG_CRYPTO_RMD320=m
CONFIG_CRYPTO_SHA1=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_SHA256=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_SHA512=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_SHA3=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CRYPTO_SM3=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_STREEBOG=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_TGR192=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_WP512=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Ciphers
#
CONFIG_CRYPTO_AES=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_AES_TI=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_ANUBIS=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_ARC4=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_BLOWFISH=m
CONFIG_CRYPTO_BLOWFISH_COMMON=m
CONFIG_CRYPTO_CAMELLIA=m
CONFIG_CRYPTO_CAST_COMMON=m
CONFIG_CRYPTO_CAST5=m
CONFIG_CRYPTO_CAST6=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_DES=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_FCRYPT=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_KHAZAD=m
CONFIG_CRYPTO_SALSA20=m
Update mvebu-next branch to 4.11
2017-05-14 19:11:33 +03:00
CONFIG_CRYPTO_CHACHA20=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_SEED=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_SERPENT=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CRYPTO_SM4=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_TEA=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_TWOFISH=m
CONFIG_CRYPTO_TWOFISH_COMMON=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Compression
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_LZO=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_842=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_LZ4=m
CONFIG_CRYPTO_LZ4HC=m
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_CRYPTO_ZSTD=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Random Number Generation
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_ANSI_CPRNG=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_DRBG_MENU=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_DRBG_HMAC=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_DRBG_HASH=y
CONFIG_CRYPTO_DRBG_CTR=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_DRBG=y
CONFIG_CRYPTO_JITTERENTROPY=y
CONFIG_CRYPTO_USER_API=m
CONFIG_CRYPTO_USER_API_HASH=m
CONFIG_CRYPTO_USER_API_SKCIPHER=m
CONFIG_CRYPTO_USER_API_RNG=m
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_CRYPTO_USER_API_RNG_CAVP is not set
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_USER_API_AEAD=m
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
CONFIG_CRYPTO_USER_API_ENABLE_OBSOLETE=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_STATS=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CRYPTO_HASH_INFO=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
#
# Crypto library routines
#
CONFIG_CRYPTO_LIB_AES=y
CONFIG_CRYPTO_LIB_ARC4=m
CONFIG_CRYPTO_LIB_BLAKE2S_GENERIC=m
CONFIG_CRYPTO_LIB_BLAKE2S=m
CONFIG_CRYPTO_ARCH_HAVE_LIB_CHACHA=m
CONFIG_CRYPTO_LIB_CHACHA_GENERIC=m
CONFIG_CRYPTO_LIB_CHACHA=m
CONFIG_CRYPTO_ARCH_HAVE_LIB_CURVE25519=m
CONFIG_CRYPTO_LIB_CURVE25519_GENERIC=m
CONFIG_CRYPTO_LIB_CURVE25519=m
CONFIG_CRYPTO_LIB_DES=m
CONFIG_CRYPTO_LIB_POLY1305_RSIZE=9
CONFIG_CRYPTO_ARCH_HAVE_LIB_POLY1305=m
CONFIG_CRYPTO_LIB_POLY1305_GENERIC=m
CONFIG_CRYPTO_LIB_POLY1305=m
CONFIG_CRYPTO_LIB_CHACHA20POLY1305=m
CONFIG_CRYPTO_LIB_SHA256=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRYPTO_HW=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRYPTO_DEV_HIFN_795X=m
# CONFIG_CRYPTO_DEV_HIFN_795X_RNG is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CRYPTO_DEV_ATMEL_I2C=m
CONFIG_CRYPTO_DEV_ATMEL_ECC=m
CONFIG_CRYPTO_DEV_ATMEL_SHA204A=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_CRYPTO_DEV_MARVELL=m
CONFIG_CRYPTO_DEV_MARVELL_CESA=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRYPTO_DEV_VIRTIO=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_CRYPTO_DEV_SAFEXCEL is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_CRYPTO_DEV_CCREE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_CRYPTO_DEV_AMLOGIC_GXL is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_ASYMMETRIC_KEY_TYPE=y
CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
CONFIG_X509_CERTIFICATE_PARSER=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_PKCS8_PRIVATE_KEY_PARSER=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_PKCS7_MESSAGE_PARSER=y
CONFIG_PKCS7_TEST_KEY=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SIGNED_PE_FILE_VERIFICATION=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Certificates for signature checking
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_MODULE_SIG_KEY="certs/signing_key.pem"
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SYSTEM_TRUSTED_KEYRING=y
CONFIG_SYSTEM_TRUSTED_KEYS=""
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SYSTEM_EXTRA_CERTIFICATE=y
CONFIG_SYSTEM_EXTRA_CERTIFICATE_SIZE=4096
CONFIG_SECONDARY_TRUSTED_KEYRING=y
CONFIG_SYSTEM_BLACKLIST_KEYRING=y
CONFIG_SYSTEM_BLACKLIST_HASH_LIST=""
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Certificates for signature checking
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
#
# Library routines
#
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_RAID6_PQ=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RAID6_PQ_BENCHMARK=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_LINEAR_RANGES=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_PACKING=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_BITREVERSE=y
CONFIG_HAVE_ARCH_BITREVERSE=y
CONFIG_GENERIC_STRNCPY_FROM_USER=y
CONFIG_GENERIC_STRNLEN_USER=y
CONFIG_GENERIC_NET_UTILS=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CORDIC=m
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PRIME_NUMBERS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_RATIONAL=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_GENERIC_PCI_IOMAP=y
CONFIG_ARCH_USE_CMPXCHG_LOCKREF=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CRC_CCITT=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRC16=y
Update mvebu-next to 4.12
2017-07-12 21:58:34 +03:00
CONFIG_CRC_T10DIF=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRC_ITU_T=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CRC32=y
# CONFIG_CRC32_SELFTEST is not set
CONFIG_CRC32_SLICEBY8=y
# CONFIG_CRC32_SLICEBY4 is not set
# CONFIG_CRC32_SARWATE is not set
# CONFIG_CRC32_BIT is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CRC64=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CRC4=m
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_CRC7=m
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_LIBCRC32C=y
Update mvebu-next kernel config
2017-02-06 18:54:57 +03:00
CONFIG_CRC8=m
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_XXHASH=y
Add more options to mvebu kernels
2017-02-07 16:22:06 +03:00
CONFIG_AUDIT_GENERIC=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
# CONFIG_RANDOM32_SELFTEST is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_842_COMPRESS=y
CONFIG_842_DECOMPRESS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_ZLIB_INFLATE=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_ZLIB_DEFLATE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_LZO_COMPRESS=y
CONFIG_LZO_DECOMPRESS=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_LZ4_COMPRESS=m
CONFIG_LZ4HC_COMPRESS=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_LZ4_DECOMPRESS=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
CONFIG_ZSTD_COMPRESS=y
CONFIG_ZSTD_DECOMPRESS=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_XZ_DEC=y
CONFIG_XZ_DEC_X86=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_XZ_DEC_IA64=y
CONFIG_XZ_DEC_ARM=y
CONFIG_XZ_DEC_ARMTHUMB=y
CONFIG_XZ_DEC_SPARC=y
CONFIG_XZ_DEC_BCJ=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_XZ_DEC_TEST=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_DECOMPRESS_GZIP=y
CONFIG_DECOMPRESS_BZIP2=y
CONFIG_DECOMPRESS_LZMA=y
CONFIG_DECOMPRESS_XZ=y
CONFIG_DECOMPRESS_LZO=y
CONFIG_DECOMPRESS_LZ4=y
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
CONFIG_DECOMPRESS_ZSTD=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_GENERIC_ALLOCATOR=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_REED_SOLOMON=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_REED_SOLOMON_ENC8=y
CONFIG_REED_SOLOMON_DEC8=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_REED_SOLOMON_ENC16=y
CONFIG_REED_SOLOMON_DEC16=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_TEXTSEARCH=y
CONFIG_TEXTSEARCH_KMP=m
CONFIG_TEXTSEARCH_BM=m
CONFIG_TEXTSEARCH_FSM=m
CONFIG_ASSOCIATIVE_ARRAY=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT_MAP=y
CONFIG_HAS_DMA=y
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
CONFIG_DMA_OPS=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_NEED_DMA_MAP_STATE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_DMA_DECLARE_COHERENT=y
CONFIG_ARCH_HAS_SETUP_DMA_OPS=y
CONFIG_ARCH_HAS_TEARDOWN_DMA_OPS=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_DMA_NONCOHERENT_MMAP=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_DMA_REMAP=y
CONFIG_DMA_CMA=y
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_DMA_PERNUMA_CMA is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
#
# Default contiguous memory area size:
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CMA_SIZE_MBYTES=128
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CMA_SIZE_SEL_MBYTES=y
# CONFIG_CMA_SIZE_SEL_PERCENTAGE is not set
# CONFIG_CMA_SIZE_SEL_MIN is not set
# CONFIG_CMA_SIZE_SEL_MAX is not set
CONFIG_CMA_ALIGNMENT=8
# CONFIG_DMA_API_DEBUG is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SGL_ALLOC=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_CPU_RMAP=y
CONFIG_DQL=y
CONFIG_GLOB=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_GLOB_SELFTEST=m
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_NLATTR=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_CLZ_TAB=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_IRQ_POLL=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_MPILIB=y
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_SIGNATURE=y
More fixes for Marvell Armada, kernel configuration for NEXT / DEV, fixed failed patch, u-boot packaging, ...
2016-01-08 19:50:53 +01:00
CONFIG_LIBFDT=y
Updated Marvel configuration for legacy and next
2016-01-23 08:54:04 +01:00
CONFIG_OID_REGISTRY=y
Updated Clearfog NEXT config, added BASE model as separate DTB. http://forum.solid-run.com/viewtopic.php?f=32&t=3072&sid=2a2244355bc4da18da7487952fc34e7a
2016-09-12 12:05:22 +02:00
CONFIG_SG_POOL=y
Update mvebu-next kernel to 4.9.1
2017-01-06 19:50:00 +03:00
CONFIG_SBITMAP=y
Update mvebu-{next,dev} kernel to 4.14
2017-11-25 17:46:35 +03:00
# CONFIG_STRING_SELFTEST is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Library routines
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Kernel hacking
#
#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_PRINTK_CALLER is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4
# CONFIG_BOOT_PRINTK_DELAY is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DYNAMIC_DEBUG=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_DYNAMIC_DEBUG_CORE=y
CONFIG_SYMBOLIC_ERRNAME=y
CONFIG_DEBUG_BUGVERBOSE=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of printk and dmesg options
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Compile-time checks and compiler options
#
# CONFIG_DEBUG_INFO is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_FRAME_WARN=1024
# CONFIG_STRIP_ASM_SYMS is not set
# CONFIG_READABLE_ASM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_HEADERS_INSTALL is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_SECTION_MISMATCH is not set
CONFIG_SECTION_MISMATCH_WARN_ONLY=y
# CONFIG_DEBUG_FORCE_WEAK_PER_CPU is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Compile-time checks and compiler options
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
#
# Generic Kernel Debugging Instruments
#
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_MAGIC_SYSRQ=y
CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x1
CONFIG_MAGIC_SYSRQ_SERIAL=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_MAGIC_SYSRQ_SERIAL_SEQUENCE=""
CONFIG_DEBUG_FS=y
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
CONFIG_DEBUG_FS_ALLOW_ALL=y
# CONFIG_DEBUG_FS_DISALLOW_MOUNT is not set
# CONFIG_DEBUG_FS_ALLOW_NONE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_HAVE_ARCH_KGDB=y
# CONFIG_KGDB is not set
# CONFIG_UBSAN is not set
# end of Generic Kernel Debugging Instruments
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_DEBUG_KERNEL=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_DEBUG_MISC=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
# Memory Debugging
#
CONFIG_PAGE_EXTENSION=y
# CONFIG_DEBUG_PAGEALLOC is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_PAGE_OWNER is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_PAGE_POISONING is not set
# CONFIG_DEBUG_RODATA_TEST is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_DEBUG_WX is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_OBJECTS is not set
# CONFIG_SLUB_DEBUG_ON is not set
# CONFIG_SLUB_STATS is not set
CONFIG_HAVE_DEBUG_KMEMLEAK=y
# CONFIG_DEBUG_KMEMLEAK is not set
# CONFIG_DEBUG_STACK_USAGE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SCHED_STACK_END_CHECK is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_VM is not set
CONFIG_ARCH_HAS_DEBUG_VIRTUAL=y
# CONFIG_DEBUG_VIRTUAL is not set
CONFIG_DEBUG_MEMORY_INIT=y
# CONFIG_DEBUG_PER_CPU_MAPS is not set
# CONFIG_DEBUG_HIGHMEM is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_CC_HAS_KASAN_GENERIC=y
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_CC_HAS_WORKING_NOSANITIZE_ADDRESS=y
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Memory Debugging
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_SHIRQ is not set
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# Debug Oops, Lockups and Hangs
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
#
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_PANIC_ON_OOPS is not set
CONFIG_PANIC_ON_OOPS_VALUE=0
CONFIG_PANIC_TIMEOUT=0
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_SOFTLOCKUP_DETECTOR is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_DETECT_HUNG_TASK=y
CONFIG_DEFAULT_HUNG_TASK_TIMEOUT=120
# CONFIG_BOOTPARAM_HUNG_TASK_PANIC is not set
CONFIG_BOOTPARAM_HUNG_TASK_PANIC_VALUE=0
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_WQ_WATCHDOG is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_TEST_LOCKUP is not set
# end of Debug Oops, Lockups and Hangs
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
#
# Scheduler Debugging
#
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
# CONFIG_SCHED_DEBUG is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_SCHED_INFO=y
# CONFIG_SCHEDSTATS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# end of Scheduler Debugging
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_TIMEKEEPING is not set
#
# Lock Debugging (spinlocks, mutexes, etc...)
#
CONFIG_LOCK_DEBUGGING_SUPPORT=y
# CONFIG_PROVE_LOCKING is not set
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_MUTEXES is not set
# CONFIG_DEBUG_WW_MUTEX_SLOWPATH is not set
# CONFIG_DEBUG_RWSEMS is not set
# CONFIG_DEBUG_LOCK_ALLOC is not set
# CONFIG_DEBUG_ATOMIC_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
# CONFIG_LOCK_TORTURE_TEST is not set
# CONFIG_WW_MUTEX_SELFTEST is not set
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_SCF_TORTURE_TEST=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Lock Debugging (spinlocks, mutexes, etc...)
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_STACKTRACE is not set
# CONFIG_WARN_ALL_UNSEEDED_RANDOM is not set
# CONFIG_DEBUG_KOBJECT is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
#
# Debug kernel data structures
#
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_LIST is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_DEBUG_PLIST is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_SG is not set
# CONFIG_DEBUG_NOTIFIERS is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_BUG_ON_DATA_CORRUPTION is not set
# end of Debug kernel data structures
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_CREDENTIALS is not set
#
# RCU Debugging
#
Fix compilation errors on mvebu current / dev Fixed by reverting https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpio?h=v5.10.12&id=43f2e6077f441d681f0337ab91f7c4c2d4c62761 which needs closer examination when time permits.
2021-01-30 19:17:25 +01:00
CONFIG_TORTURE_TEST=m
CONFIG_RCU_SCALE_TEST=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_RCU_TORTURE_TEST is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_RCU_REF_SCALE_TEST is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_RCU_CPU_STALL_TIMEOUT=21
Bugfix: adjust mvebu-current kernel config It boots up properly now @boards-marvell Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
2020-04-29 12:27:29 +02:00
CONFIG_RCU_TRACE=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_RCU_EQS_DEBUG is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_RCU_STRICT_GRACE_PERIOD is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of RCU Debugging
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_DEBUG_WQ_FORCE_RR_CPU is not set
# CONFIG_DEBUG_BLOCK_EXT_DEVT is not set
# CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set
# CONFIG_LATENCYTOP is not set
CONFIG_HAVE_FUNCTION_TRACER=y
CONFIG_HAVE_DYNAMIC_FTRACE=y
CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_HAVE_C_RECORDMCOUNT=y
Bugfix: adjust mvebu-current kernel config It boots up properly now @boards-marvell Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
2020-04-29 12:27:29 +02:00
CONFIG_TRACE_CLOCK=y
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_TRACING_SUPPORT=y
# CONFIG_FTRACE is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_SAMPLES is not set
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
# CONFIG_STRICT_DEVMEM is not set
#
# arm Debugging
#
# CONFIG_ARM_PTDUMP_DEBUGFS is not set
CONFIG_UNWINDER_ARM=y
CONFIG_ARM_UNWIND=y
# CONFIG_DEBUG_USER is not set
CONFIG_DEBUG_LL=y
# CONFIG_DEBUG_MVEBU_UART0 is not set
CONFIG_DEBUG_MVEBU_UART0_ALTERNATE=y
# CONFIG_DEBUG_MVEBU_UART1_ALTERNATE is not set
# CONFIG_DEBUG_ICEDCC is not set
# CONFIG_DEBUG_SEMIHOSTING is not set
# CONFIG_DEBUG_LL_UART_8250 is not set
# CONFIG_DEBUG_LL_UART_PL01X is not set
[AR-609] Switch mvebu-current to 5.10.y (reusing config and patches from -dev) (#2547) * mvebu-current move to lk5.10.y * mvebu-current update patches based on -dev * mvebu-current update kernel config
2021-01-22 13:20:44 +01:00
# CONFIG_DEBUG_UART_FLOW_CONTROL is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
CONFIG_DEBUG_LL_INCLUDE="debug/8250.S"
CONFIG_DEBUG_UART_8250=y
CONFIG_DEBUG_UART_PHYS=0xf1012000
CONFIG_DEBUG_UART_VIRT=0xfec12000
CONFIG_DEBUG_UART_8250_SHIFT=2
# CONFIG_DEBUG_UART_8250_WORD is not set
# CONFIG_DEBUG_UART_8250_PALMCHIP is not set
CONFIG_DEBUG_UNCOMPRESS=y
CONFIG_UNCOMPRESS_INCLUDE="debug/uncompress.h"
CONFIG_EARLY_PRINTK=y
# CONFIG_PID_IN_CONTEXTIDR is not set
# CONFIG_CORESIGHT is not set
# end of arm Debugging
#
# Kernel Testing and Coverage
#
# CONFIG_KUNIT is not set
# CONFIG_NOTIFIER_ERROR_INJECTION is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_ARCH_HAS_KCOV=y
CONFIG_CC_HAS_SANCOV_TRACE_PC=y
# CONFIG_KCOV is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
CONFIG_RUNTIME_TESTING_MENU=y
# CONFIG_LKDTM is not set
# CONFIG_TEST_LIST_SORT is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_TEST_MIN_HEAP is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_TEST_SORT is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
# CONFIG_RBTREE_TEST is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_REED_SOLOMON_TEST=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_INTERVAL_TREE_TEST is not set
# CONFIG_PERCPU_TEST is not set
# CONFIG_ATOMIC64_SELFTEST is not set
# CONFIG_ASYNC_RAID6_TEST is not set
CONFIG_TEST_HEXDUMP=m
# CONFIG_TEST_STRING_HELPERS is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_TEST_STRSCPY=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_TEST_KSTRTOX is not set
# CONFIG_TEST_PRINTF is not set
# CONFIG_TEST_BITMAP is not set
# CONFIG_TEST_UUID is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_TEST_XARRAY=m
# CONFIG_TEST_OVERFLOW is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_TEST_RHASHTABLE is not set
# CONFIG_TEST_HASH is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_TEST_IDA is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_TEST_LKM is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# CONFIG_TEST_BITOPS is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_TEST_VMALLOC=m
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_TEST_USER_COPY is not set
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_TEST_BPF=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_TEST_BLACKHOLE_DEV=m
# CONFIG_FIND_BIT_BENCHMARK is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_TEST_FIRMWARE is not set
# CONFIG_TEST_SYSCTL is not set
# CONFIG_TEST_UDELAY is not set
# CONFIG_TEST_STATIC_KEYS is not set
# CONFIG_TEST_KMOD is not set
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
CONFIG_TEST_MEMCAT_P=m
WIP: Merge kernel features from upstream (#1856) * Merge kernel features from upstream part 1 * Update Rockchip and sunxi64 * Adding common features for mvebu and mvebu64 * add upstream patch character device -> media driver (#1877) * meson64 and sunxi with current * modified config character device -> media driver * add upstream patch character device -> media driver * add upstream patch character device -> media driver * set sunxi-current kernel config to allow for tc classification (#1876) * Updated kernel configs Co-authored-by: MalikSiraj <37216310+MalikSiraj@users.noreply.github.com> Co-authored-by: ChrisDumont <chrisdumont@telus.net>
2020-04-27 12:22:55 +02:00
CONFIG_TEST_STACKINIT=m
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# CONFIG_TEST_MEMINIT is not set
[AR-558] Switch mvebu current to LK5.9 (based on previous mvebu-dev) (#2405) * mvebu-current switch to lk5.9 * mvebu-current update patches from dev * Remove mvebu DFS patches
2020-12-03 10:24:27 +01:00
# CONFIG_TEST_FREE_PAGES is not set
Move mvebu DEFAULT, NEXT and DEV branch to next kernel (LTS) and U-boot #1426 (#1487) * Initial Mvebu RFC https://github.com/armbian/build/issues/1426 Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: add missing patches Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu: change making u-boot targets to standard way, adjust patches and config Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * helios4: set default branch to use U-Boot 2018.11 Switch over to U-Boot 2018.11 that has been used for some time in next branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Enable DEV branch Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: Add RTC support on Clearfog and Helios4 Added DM driver for mvebu RTC and enable it on Clearfog and Helios4 configuration. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * helios4: Added SPI NOR flash target Build bootable SPI NOR flash image. Change the boot order to USB -> SATA -> MMC Signed-off-by: Aditya Prayoga <aditya@kobol.io> * Restore SPI support on U-Boot 2019.04 * mvebu: kernel: Added Wake-On-GPIO and WoL support The patch set was missing during transition. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update Old versions of U-Boot did not configure correctly the ODT on data signals of DDR RAM on SolidRun's ARMADA A388 SOMs. According to SolidRun Knowledge Base, the changes already pushed to mainline U-Boot. But then it was overwritten when Marvell DDR Training Tool updated [URL] https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * [#1429] mvebu: u-boot: Add revision id for Armada 38x B0 Added patch for SolidRun U-Boot v2018.01 and for Helios4 U-Boot v2018.11 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * clearfog: Added SPI NOR flash target Build bootable SPI NOR flash image. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: clearfog: DEV branch use mainline U-Boot Also move clearfog base patch into its own board folder. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: enable U-Boot uart target Normal MMC image can be used for uart boot using following command: ./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX But on Helios4, the SPL failed to continue the booting process if ECC is enabled, so disable it. Since the usage of uart boot is more for rescue/debug, disable autoboot. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: NEXT branch use mainline U-Boot Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: fix fancontrol related bug during buster testing - On kernel 4.19, cpu thermal sensor changed the name from armada_thermal into f10e4078.thermal. Added this new name to udev rules - Since DEFAULT branch now use kernel 4.14, update fancontrol configuration - Load lm75 kernel module - On kernel 4.19, cpu temp reading about 20 degree C lower, update fancontrol configuration. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: Override vendor provided fancontrol unit systemd emit following message on dmesg systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update the unit file accordingly. Override and change the value in the unit file to remove the message. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: DEV branch use its own u-boot patch folder The patches are copied over from u-boot-mvebu-next Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: u-boot: Make clearfog model distinction more obvious While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * lib: Use apt-get install instead of dpkg on install_deb_chroot() dpkg -i does not install dependencies required by the package. This is needed if the BSP package requires other package that is not installed during debootstrap. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Move various tweak to family_tweak_bsp() Various tweak in family_tweaks_s() only applied to SD card image. Move it to family_tweaks_bsp() so it will also included on the BSP package and applied to existing user. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: mvebu: helios4: Add /etc/modules to BSP On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel module. Pack the file into BSP so user no longer needed to modify it. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Make zbud as built-in module To remove the following error: [ 1.705485] zswap: default zpool zbud not available [ 1.705488] zswap: pool creation failed Signed-off-by: Aditya Prayoga <aditya@kobol.io> * bootscripts: mvebu: Add default value for spi_workaround Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452) On kernel 4.19, armada_thermal driver has been fixed to address Marvell's Errata #132698 (The changes first appear on LK 4.16). The result is temperature reading is around 20 degree Celsius lower. Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19 which is incorrect. Instead of adding some logic on what condition to apply the tweak, it is better to remove the tweak and patch the kernel instead. Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in motd") which is part of #1421 solution. [URL] https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/ Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: unified fancontrol config Since LK 4.14 on DEFAULT branch already patched and the temp reading is same as LK 4.19 on NEXT branch, it is no longer needed to separate fancontrol configuration file. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: helios4: Remove rev id patch The patch is already applied in helios4 repo, no need to have it in armbian. This revert helios4 part of commit 7411c55 Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: enable PCIe support and PCIe reset Signed-off-by: Aditya Prayoga <aditya@kobol.io> * u-boot: clearfog: add boot-marvell.cmd backward compatibility The patches added missing variable that used on boot-marvell.cmd and also adjust the some memory addresses to prevent crash due to usage of fdt_high and initrd_high. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu: helios4: tweak regarding temperature setting Make fan speed similar compared to pre-patched armada-thermal. Target PWM value around 70 during idle. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: sources: clearfog to use u-boot 2018.01 for NEXT branch This changes also affect Helios4. Moved the shared U-Boot source setting back to Helios4 for NEXT branch. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * config: boards: build Stretch image for Clearfog and Helios4 Also remove DEV from Helios4 CLI_TARGET Signed-off-by: Aditya Prayoga <aditya@kobol.io> * kernel: mvebu-next: Disable access to SPI Flash User need to set spi_workaround=yes to enable SPI Flash access and lost access to internal SATA. Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-next: adjust kernel config * mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building. * Adjust kernel config, add AUFS Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com> * mvebu-next: Adjust kernel config, add debug GPIO Signed-off-by: Aditya Prayoga <aditya@kobol.io> * mvebu-dev: separate Clearfog Base U-boot configuration file and patch Signed-off-by: Aditya Prayoga <aditya@kobol.io>
2019-07-31 17:51:00 +07:00
# CONFIG_MEMTEST is not set
[mvebu-current] switch to lk5.8
2020-09-29 17:18:28 +02:00
# end of Kernel Testing and Coverage
[ mvebu ] Update kernel config
2020-01-19 15:38:18 +01:00
# end of Kernel hacking
Reference in a new issue Copy permalink