aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm27xx/bcm2708
Commit message (Collapse)AuthorAgeFilesLines
* Revert "bcm27xx: bcm27xx: update defconfig"Christian Lamparter2022-02-241-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts all four commits dbb45421bab "bcm27xx: bcm2708: update defconfig" 332f69583ad "bcm27xx: bcm2709: update defconfig" a478202d74b "bcm27xx: bcm2710: update defconfig" 82da1dfd69a "bcm27xx: bcm2711: update defconfig" this also highlighted an unrelated kconfig failure that warrants investigation. But for now it is important for the bcm27xx target to come back again. |* |* Restart config... |* |* |* Allow override default queue discipline |* |Allow override default queue discipline (NET_SCH_DEFAULT) [Y/n/?] y | Default queuing discipline | 1. Fair Queue (DEFAULT_FQ) (NEW) | 2. Controlled Delay (DEFAULT_CODEL) (NEW) | > 3. Fair Queue Controlled Delay (DEFAULT_FQ_CODEL) | 4. Stochastic Fair Queue (DEFAULT_SFQ) (NEW) | 5. Priority FIFO Fast (DEFAULT_PFIFO_FAST) | choice[1-5?]: |Error in reading or end of file. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bcm27xx: bcm2708: update defconfigJohn Audia2022-02-201-3/+0
| | | | | | | | | | Enabled CONFIG_ALL_KMODS and ran make kernel_menuconfig against bcm2708 to update defconfig. Some of the removed symbols are present in target/linux/generic/config-5.10 while others were removed by the make target. Signed-off-by: John Audia <graysky@archlinux.us> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (wrapped)
* kernel: 5.10: consolidate mac80211 crypto optionsSergey Ryazanov2021-12-171-2/+0
| | | | | | | | | | | | | | | | | | | | | | Each of - CRYPTO_AEAD2 - CRYPTO_AEAD - CRYPTO_GF128MUL - CRYPTO_GHASH - CRYPTO_HASH2 - CRYPTO_HASH - CRYPTO_MANAGER2 - CRYPTO_MANAGER - CRYPTO_NULL2 either directly required for mac80211 crypto support, or directly selected by such options. Support for the mac80211 crypto was enabled in the generic config since c7182123b9 ("kernel: make cryptoapi support needed by mac80211 built-in"). So move the above options from the target configs to the generic config to make it clear why do we need them. CC: Felix Fietkau <nbd@nbd.name> Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: filter out both Clang and LLD versionsSergey Ryazanov2021-12-171-1/+0
| | | | | | | | Both CLANG_VERSION and LLD_VERISON are autogenerated runtime configuration options, so add them to the kernel configuration filter and remove from generic and per-target configs to keep configs clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* bcm27xx: remove obsolete kernel 5.4Adrian Schmutzler2021-10-051-356/+0
| | | | | | | With the upgrade to kernel 5.10 per default the old version is no longer required to be in tree. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm27xx: add RPI_AXIPERF symbolStijn Tintel2021-10-052-0/+2
| | | | | | | | When KERNEL_PERF_EVENTS is enabled in OpenWrt, or PERF_EVENTS in the kernel config, the RPI_AXIPERF is exposed. Add it to the subtarget kernel configs to avoid build failures. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* bcm27xx: add SND_SOC_AD193X_{I2C,SPI} symbolsStijn Tintel2021-10-052-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When building an image for the bcm27xx target, some combinations of config options will fail to build due the SND_SOC_AD193X_I2C and SND_SOC_AD193X_SPI kernel config symbols being missing. The problem only occurs on bcm27xx as the target contains a patch that modifies the Kconfig file containing the symbols; in the vanilla kernel, there is no string after the tristate keyword so the symbol is not exposed. The _I2C symbol depends on I2C, which is enabled in the kernel configs of all bcm27xx subtargets. The _SPI symbol depends on SPI_MASTER, which is exposed by either kmod-mmc-spi, kmod-spi-bitbang, kmod-spi-dev, kmod-spi-bcm2835 or kmod-spi-bcm2835-aux. Both symbols are defined in the sound/soc/codecs directory, which is only included when SND_SOC is enabled, so this problem doesn't occur when kmod-sound-soc-core is not enabled. As the kmod-sound-soc-bcm2835-i2s package disables the SND_SOC_AD193X_SPI symbol, it also doesn't occur when kmod-sound-soc-bcm2835-i2s is enabled. As there are several possible config combinations that do exhibit this problem, it is best to solve it by adding the missing symbols to the subtarget kernel configs. By doing this we can remove them from the kmod-sound-soc-bcm2835-i2s package. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* bcm27xx: add kernel 5.10 supportÁlvaro Fernández Rojas2021-08-211-0/+366
| | | | | | | | | | | Rebased RPi foundation patches on linux 5.10.59, removed applied and reverted patches, wireless patches and defconfig patches. bcm2708: boot tested on RPi B+ v1.2 bcm2709: boot tested on RPi 4B v1.1 4G bcm2711: boot tested on RPi 4B v1.1 4G Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* treewide: switch the timer frequency to 100 HzRui Salvaterra2021-04-211-2/+0
| | | | | | | | Some targets select HZ=100, others HZ=250. There's no reason to select a higher timer frequency (and 100 Hz are available in every architecture), so change all targets to 100 Hz. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* bcm27xx: import latest patches from the RPi foundationÁlvaro Fernández Rojas2021-02-181-61/+7
| | | | | | | | | bcm2708: boot tested on RPi B+ v1.2 bcm2709: boot tested on RPi 3B v1.2 and RPi 4B v1.1 4G bcm2710: boot tested on RPi 3B v1.2 bcm2711: boot tested on RPi 4B v1.1 4G Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: Remove 2FS_FS_XATTR and F2FS_STAT_FS symbols from target configsHauke Mehrtens2020-10-111-1/+0
| | | | | | | This config option was moved to the generic kernel configuration. Fixes: ab1bd576562b ("kernel: move F2FS_FS_XATTR and F2FS_STAT_FS symbols to generic") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: clean up XATTR config symbolsPaul Spooren2020-10-091-1/+0
| | | | | | | | | | | | | Extended attributes are required for overlayfs and have hence been long ago enabled for jffs2, but should be enabled unconditionally for all other filesystems which may potentially serve as overlayfs' upper directory. Previously it was inconsistently added in multiple targets. Add symbols to generic kernel config and remove all *_XATTR symbols from target configs. Signed-off-by: Paul Spooren <mail@aparcar.org> [keep things as they are for squashfs, improve commit message] Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: unify CONFIG_GPIO_SYSFS in kernel configsFelix Fietkau2020-08-061-1/+0
| | | | | | Enable it for all platforms Signed-off-by: Felix Fietkau <nbd@nbd.name>
* treewide: kernel: drop redundant USB_EHCI_HCD=n config symbolPetr Štetiar2020-07-091-1/+0
| | | | | | | | | Commit e53ec043bae1 ("kirkwood: move usb support to modules") has moved this config symbol into generic configs, so it could be removed from other configs. Suggested-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* bcm27xx: update to latest patches from RPi foundationÁlvaro Fernández Rojas2020-05-281-1/+3
| | | | | | | Also removes random module and switches to new bcm2711 thermal driver. Boot tested on RPi 4B v1.1 4G. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: update patches from RPi foundationÁlvaro Fernández Rojas2020-05-281-1/+7
| | | | | | | | | bcm2708: boot tested on RPi B+ v1.2 bcm2709: boot tested on RPi 3B v1.2 bcm2710: boot tested on RPi 3B v1.2 bcm2711: boot tested on RPi 4B v1.1 4G Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: remove linux 4.19 supportÁlvaro Fernández Rojas2020-05-281-411/+0
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: update 5.4 patches from RPi foundationÁlvaro Fernández Rojas2020-03-311-0/+2
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: refresh linux 5.4 configsÁlvaro Fernández Rojas2020-03-231-9/+0
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: move TEO governor to generic configTomasz Maciej Nowak2020-03-171-1/+0
| | | | | | | | This new symbol popped up in few places. Disable it in generic config. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [fixed merge conflict in generic/config-5.4] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* bcm27xx: sync 5.4 patches with RPi FoundationÁlvaro Fernández Rojas2020-03-161-4/+0
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: 5.4: move some kconfig options to genericYousong Zhou2020-03-101-6/+0
| | | | | | | | | | | CONFIG_64BIT_TIME=y CONFIG_KASAN_STACK=1 CONFIG_UBSAN_ALIGNMENT=y CONFIG_UNIX_SCM=y CONFIG_DMA_DECLARE_COHERENT=y CONFIG_OF_RESERVED_MEM=y Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* bcm27xx: bcm2708: refresh linux 5.4 configÁlvaro Fernández Rojas2020-03-011-18/+30
| | | | | | I missed this when adding linux 5.4 support Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: add linux 5.4 supportÁlvaro Fernández Rojas2020-02-291-0/+411
| | | | | | Tested on bcm2710 (Raspberry Pi 3B). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: rename target to bcm27xxAdrian Schmutzler2020-02-142-0/+424
This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Despite, since subtargets range from bcm2708 to bcm2711, it seems appropriate to use bcm27xx instead of bcm2708 (again, as already done for BOARDNAME). This also renames the packages brcm2708-userland and brcm2708-gpu-fw. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Álvaro Fernández Rojas <noltari@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 03:46:14 +0000