aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/at91
Commit message (Collapse)AuthorAgeFilesLines
* treewide: replace backticks by $(...) in gen_*_img.sh scriptsAdrian Schmutzler2019-09-291-1/+1
| | | | | | | | This replaces deprecated backticks by more versatile $(...) syntax. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> [decapitalized patch subject at submitter's request] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* at91:sam9x: create sdcard imagesSandeep Sheriker M2019-09-211-2/+42
| | | | | | create sdcard images for sam9x25 & sam9x35 ek targets. Signed-off-by: Sandeep Sheriker M <sandeep.sheriker@microchip.com>
* at91:sama5: create fit imageSandeep Sheriker M2019-09-212-1/+5
| | | | | | | create fit image & add it to sdcard image for sama5 target device. Signed-off-by: Sandeep Sheriker M <sandeep.sheriker@microchip.com>
* at91/image/sama5.mk: check for sama5d4_xplained deviceSandeep Sheriker M2019-08-171-3/+7
| | | | | | | check for sama5d4_xplained device while copying at91bootstrap binary to sdcard image. Signed-off-by: Sandeep Sheriker M <sandeep.sheriker@microchip.com>
* at91: remove Build/at91-sdcard commandSandeep Sheriker M2019-08-171-35/+0
| | | | | | | remove at91-sdcard build command from Makefile as this is moved to respective subtarget Makefile. Signed-off-by: Sandeep Sheriker M <sandeep.sheriker@microchip.com>
* at91: add uboot environmentsSandeep Sheriker M2019-08-172-1/+24
| | | | | | add uboot environments to sdcard image Signed-off-by: Sandeep Sheriker M <sandeep.sheriker@microchip.com>
* at91: move at91-sdcard command to sama5.mkSandeep Sheriker M2019-08-171-0/+33
| | | | Signed-off-by: Sandeep Sheriker M <sandeep.sheriker@microchip.com>
* at91bootstrap: add sama5d27_som1_eksd1_uboot as default defconfigSandeep Sheriker M2019-08-171-3/+7
| | | | Signed-off-by: Sandeep Sheriker M <sandeep.sheriker@microchip.com>
* at91: split up DEVICE_TITLEMoritz Warning2019-08-021-19/+39
| | | | | | DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Signed-off-by: Moritz Warning <moritzwarning@web.de>
* at91:renaming subtraget legacy to sam9xSandeep Sheriker M2019-05-306-12/+12
| | | | | | renaming subtraget legacy to sam9x for adding new sam9 soc's Signed-off-by: Sandeep Sheriker M <sandeep.sheriker@microchip.com>
* at91: Update kernel to version 4.14Hauke Mehrtens2019-05-309-912/+44
| | | | | | | | This adds support for kernel 4.14 to the target and directly make it the default kernel version to use. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Sandeep Sheriker <sandeepsheriker.mallikarjun@microchip.com>
* at91: Merge SAMA5 subtargetsHauke Mehrtens2019-05-3014-129/+87
| | | | | | | | | Instead of maintaining 3 very similar subtargets merge them into one. This does not use the Arm NEON extension any more, because the SAMA5D3 does not support NEON. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Sandeep Sheriker <sandeepsheriker.mallikarjun@microchip.com>
* at91: Clean up kernel configurationHauke Mehrtens2019-05-302-20/+1
| | | | | | | | This removes some settings which are normally set by the generic configuration and should not be changed. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Sandeep Sheriker <sandeepsheriker.mallikarjun@microchip.com>
* at91: Refresh kernel configurationHauke Mehrtens2019-05-305-179/+65
| | | | | | | | | | | The configuration of the sama5d4 subtarget was used as the default configuration and then the subtarget configurations were adapted. The resulting kernel configuration without any extra modules selected is still the same. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Sandeep Sheriker <sandeepsheriker.mallikarjun@microchip.com>
* kernel: Activate CONFIG_SYN_COOKIES for all targetsHauke Mehrtens2019-05-111-1/+0
| | | | | | | | | | Some targets deactivated CONFIG_SYN_COOKIES, for unknown reasons, use the default setting from the generic configuration which activates CONFIG_SYN_COOKIES. This should prevent SYN flooding. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: Build: Split kmod-regmapHauke Mehrtens2019-01-271-1/+1
| | | | | | | | | | | | | | | | | | | | | | | This reduces the needed modifications to the mainline Linux kernel and also makes the regmap package work with an out of tree kernel which does not have these modifications. The regmap-core is only added when it is really build as a module. The regmap-core is normally bool so it cannot be built as a module in an unmodified kernel. When it is selected by on other kernel module it will always be selected as build in and it also does not show up in $(LINUX_DIR)/modules.builtin as it is not supposed to be a kernel module. When it is not in $(LINUX_DIR)/modules.builtin the build system expects it to be built as a .ko file. Just check if the module is really there and only add it in that case. This splits the regmap package into multiple packages, one for each bus type. This way only the bus maps which are really needed have to be added. This also splits the I2C, SPI and MMIO regmap into separate packages to not require all these subsystems to build them, on an unmodified upstream kernel this also causes problems in some situations. Signed-off-by: Hauke Mehrtens <hauke.mehrtens@intel.com>
* at91: dts: Unify naming of gpio-keys nodesPetr Štetiar2019-01-242-2/+2
| | | | | | | | | | | | | | In DTS Checklist[1] we're now demanding proper generic node names, as the name of a node should reflect the function of the device and use generic name for that[2]. Everybody seems to be copy&pasting from DTS files available in the repository today, so let's unify that naming there as well and provide proper examples. 1. https://openwrt.org/submitting-patches#dts_checklist 2. https://github.com/devicetree-org/devicetree-specification/blob/master/source/devicetree-basics.rst#generic-names-recommendation Signed-off-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [split up]
* kernel: Deactivate CONFIG_COMPAT_BRKHauke Mehrtens2018-12-261-1/+0
| | | | | | | | | CONFIG_COMPAT_BRK disables the heap randomization which is only needed for very old and ancient user space applications, I am not aware that we run any of these, just deactivate this option for these targets to allow heap randomization. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* treewide: dts: Remove default-state=off property from all gpio LED nodesPetr Štetiar2018-12-171-3/+0
| | | | | | | | | | | | | | | | | | >From the Documentation/devicetree/bindings/leds/common.txt: - default-state : The initial state of the LED. Valid values are "on", "off", and "keep". If the LED is already on or off and the default-state property is set the to same value, then no glitch should be produced where the LED momentarily turns off (or on). The "keep" setting will keep the LED at whatever its current state is, without producing a glitch. The default is off if this property is not present. So setting the default-state of the LEDs to `off` is redundant as `off` is default LED state anyway. We should remove it as almost every new PR/patch submission contains this property by default which seems to be just copy&paste from some DTS file already present in the tree. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: bump 4.9 to 4.9.143Koen Vandeputte2018-12-101-0/+1
| | | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 950-0063-Improve-__copy_to_user-and-__copy_from_user-performa.patch - 201-extra_optimization.patch New symbol: - CONFIG_HARDEN_BRANCH_PREDICTOR Compile-tested on: ar7, at91, brcm2708, ixp4xx, layerscape, orion Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [fix brcm2708/950-0149-Update-vfpmodule.c.patch] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: enable memory compactionFelix Fietkau2018-10-091-1/+0
| | | | | | | | | | | Compaction is the only memory management component to form high order (larger physically contiguous) memory blocks reliably. The page allocator relies on compaction heavily and the lack of the feature can lead to unexpected OOM killer invocations for high order memory requests. You shouldn't disable this option unless there really is a strong reason for it. Signed-off-by: Felix Fietkau <nbd@nbd.name> Signed-off-by: Michal Hrusecky <michal.hrusecky@nic.cz>
* treewide: fix some cosmetic glitches in dts filesPaul Wassi2018-08-273-31/+29
| | | | | | | | | | | - fix single spaces hidden by a tab - replace indentation with spaces by tabs - make empty lines empty - drop trailing whitespace - drop unnecessary blank lines Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* at91: do not build image for at91-q5xr5Hauke Mehrtens2018-08-121-1/+1
| | | | | | | | The kernel image of the at91-q5xr5 is getting too bing now and this is breaking the build. Remove the image for the at91-q5xr5 from the build to at least build images for the other devices. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: only optimized for size if small_flashMathias Kresin2018-07-121-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | Add a new config option to allow to select the default compile optimization level for the kernel. Select the optimization for size by default if the small_flash feature is set. Otherwise "Optimize for performance" is set. Add the small_flash feature flag to all (sub)targets which had the optimization for size in their default kernel config. Remove CC_OPTIMIZE_FOR_* symbols from all kernel configs to apply the new setting. Exceptions to the above are: - lantiq, where the optimization for size is only required for the xway_legacy subtarget but was set for the whole target - mediatek, ramips/mt7620 & ramips/mt76x8 where boards should have plenty of space and an optimization for size doesn't make much sense - rb532, which has 128MByte flash Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: remove DEVMEM and DEVKMEM from target's configLuis Araneda2018-07-071-2/+0
| | | | | | | | | These options are handled by generic configuration Targets that need these options should select KERNEL_DEVMEM and/or KERNEL_DEVKMEM options on OpenWRT's config Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* kernel: bump 4.9 to 4.9.100Koen Vandeputte2018-05-182-35/+13
| | | | | | | | | | | Refreshed all patches Added new ARM64 symbol: ARM64_ERRATUM_1024718 Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* at91: sama5d4: fix bad mkubifs optionsJo-Philipp Wich2018-05-131-1/+1
| | | | | | | | | | | Drop the "-x lzo" compression type override from MKUBIFS_OPTS since we do not support it in mkfs.ubifs. Attempting to use LZO compression results in "Error: bad compressor name". The build system also appends an explicit "--compr=zlib" to the mkfs command line, turning the "-x" flag into a no-op anyway. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* at91: cleanup kernel configurationsJo-Philipp Wich2018-05-115-1104/+141
| | | | | | | | | | The subtarget configurations contained a lot of reduntant symbols, arbitrary overrides and symbols set to =m. Remove most of these redundant settings to shrink the subtarget configurations to a manageable size. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* at91: sama5d2: remove CONFIG_XZ_DEC overrideJo-Philipp Wich2018-05-111-5/+0
| | | | | | | | | Fixes the following error spotted by the buildbot: Package kmod-fs-squashfs is missing dependencies for the following libraries: xz_dec.ko Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* at91: add missing config symbolsJo-Philipp Wich2018-05-112-0/+3
| | | | Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* at91: refreshing kernel configurations.Sandeep Sheriker Mallikarjun2018-05-055-2435/+1202
| | | | | | refreshing kernel configurations for sama5 and legacy subtarget. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: Add SAMA5D2 PTC EK boardSandeep Sheriker Mallikarjun2018-05-053-0/+453
| | | | | | | Add target device as at91-sama5d2_ptc_ek in SAMA5D2 subtarget and build images for SAMA5D2 PTC Ek board. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: reorganize at91 subtargetsSandeep Sheriker Mallikarjun2018-05-0513-113/+2777
| | | | | | | | | | | reorganizing at91 subtargets based on sama5 soc features and this fix below problems. 1. able to set neon flags to sama5d2 & sama5d4 subtargets. 2. fix the make clean which removes all the subtargets in bin folder. 3. able to configure kernel specific to subtarget. 4. able to set vfpu4 flags to samad3 subtargets. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: sdcard image with ext4 rootfsSandeep Sheriker Mallikarjun2018-05-052-2/+3
| | | | | | | creating sdcard image with ext4 rootfs only and ignoring creating other filesystem in sdcard image. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: Add SAMA5D27 SOM1 EK boardSandeep Sheriker Mallikarjun2018-05-053-5/+924
| | | | | | | Add support for SAMA5D27 SOM1 with target device as at91-sama5d27_som1_ek in SAMA5 subtarget and build images for SAMA5D27 SOM1 Ek board. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: fix sdcard create imageSandeep Sheriker Mallikarjun2018-05-051-7/+9
| | | | | | | | copying at91bootstrap and uboot binaries to sdcard image is done based on device name instead of dts name and this avoids creating multiple u-boot and at91bootstrap binaries. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: sama5: remove neon and VFPv4 supportSandeep Sheriker Mallikarjun2018-04-301-3/+1
| | | | | | | | | sama5d2 & samad4 have neon feature and sama5d3 does not have neon feature due to which sama5d3 boot fails with error message Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004. removing neon & VFPv4 support to fix this Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: fix build error for wb50n.Sandeep Sheriker Mallikarjun2018-04-301-10/+14
| | | | | | | when external kernel is selected from menuconfig, device wb50n is not avaliable and build fails. As a fix adding checks for external kernel. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: fix image building with CONFIG_TARGET_MULTI_PROFILEJo-Philipp Wich2018-02-142-11/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current image build code has a number of race conditions and interface contract violations in the custom image build steps: - Build/install-zImage, solely used by at91, relies on $(PROFILE_SANITIZED) which is not available when building with CONFIG_TARGET_MULTI_PROFILE - Build/at91-sdcard, which may run concurrently, creates scratch files at fixed locations and manipulates target files directly which can lead to file corruption and other unexpected failures Rename the install-zImage macro to at91-install-zImage and move it to the at91 image Makefile since this target is the sole user. Also utilize "$@" as output file name and switch the usage of $(PROFILE_SANITIZED) to $(DEVICE_NAME) in order to fix naming under multi profile builds. Fix the at91-sdcard macro to construct scratch file paths relative to "$@", which is guaranteed to be unique and store the final artifact output in "$@" as well, instead of inside $(BIN_DIR). The generic image build code takes care of moving a build steps "$@" output to the final destination in a concurrency-safe manner. Finally remove the broken install-zImage from the generic image-commands Makefile. Fixes: d7a679a036 ("at91: Install zImage.") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* at91: create device specific sdcard imagesHauke Mehrtens2018-01-111-4/+4
| | | | | | | | | | Without this patch one sdcard image with the following name is created for all devices: openwrt-at91-sama5--sdcard.img.gz This makes the build system create device specific versions like: openwrt-at91-sama5-at91-sama5d2_xplained-sdcard.img.gz Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* at91: sama5: activate fpuHauke Mehrtens2018-01-021-0/+2
| | | | | | | This activates neon and VFPv4 support for this target. The CPU support these feature so also use them. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* at91: create sdcard image for sama5Sandeep Sheriker Mallikarjun2017-12-162-0/+79
| | | | | | | | | create sdcard image using gen_at91_sdcard_img.sh for sama5 platform and sdcard image partition layout is: P0: Boot (fat32) - contains(at91bootstrap,u-boot,zImage & dtb) p1: Rootfs (ext4) Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
* at91: remove unused at91part driverHauke Mehrtens2017-10-221-122/+0
| | | | | | | There is no patch in the kernel 4.4 and 4.9 patches which adds this driver to the build system. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* at91: update to kernel 4.9Hauke Mehrtens2017-10-229-23/+26
| | | | | | | This brings the at91 target to kernel 4.9. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Ben Whitten <ben.whitten@gmail.com>
* at91: fix legacy buildHauke Mehrtens2017-10-161-2/+1
| | | | | | | | | | | The build system took the DTB_SIZE definition from Default and not from production-dtb under some conditions. Move the size definitions to Default now as it is only used in production-dtb anyway. Thanks Mathias Kresin for helping me with this. Fixes: c2f052acaeb ("at91: convert boards to generic build target") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* at91: add support for the WB50N module from LairdBen Whitten2017-10-154-0/+348
| | | | | | | | | | | | | | This module from Laird includes the following: - CPU Atmel SoC SAMA5D31 - Wifi QCA6004 - Bluetooth CSR8811 - RAM 64MB LPDDR - FLASH 128MB The flash is a dual image layout, kernel a/b, rootfs a/b, and a user partition. Signed-off-by: Ben Whitten <ben.whitten@gmail.com>
* at91: add support for the WB45N module from LairdBen Whitten2017-10-154-0/+253
| | | | | | | | | | | | | | This module from Laird includes the following: - CPU Atmel SoC ARM926EJS - Wifi AR6003 - Bluetooth CSR8510 - RAM 64MB LPDDR - FLASH 128MB The flash is a dual image layout, kernel a/b, rootfs a/b, and a user partition. Signed-off-by: Ben Whitten <ben.whitten@gmail.com>
* at91: separate MKUBIFS opts to defaults in the sub targetBen Whitten2017-10-153-13/+18
| | | | | | | Instead of applying global defaults based on selected board, transition to using a per board setting for UBIFS and UBINIZE. Signed-off-by: Ben Whitten <ben.whitten@gmail.com>
* at91: refresh kernel config, enable UBI block and DMABen Whitten2017-10-151-1/+6
| | | | | | | | | The platform generates squashfs images in a UBI block but misses the kernel module to be able to mount the block. DMA is also enabled to allow systems which include them in the DTS to use it. Signed-off-by: Ben Whitten <ben.whitten@gmail.com>
* at91: Add ext4 filesystemSandeep Sheriker Mallikarjun2017-10-141-1/+1
| | | | | | | Add ext4 filesystem for creating sdcard image with ext4 rootfs and removing ext2 as it superset of ext4. Signed-off-by: Sandeep Sheriker Mallikarjun <sandeepsheriker.mallikarjun@microchip.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-15 06:24:10 +0000