aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ipq806x: fix EA8500 switch controlPavel Kubelun2018-05-222-8/+36
| | | | | | | | | | | | | | | | | EA8500 has pcie2 slot unequipped. By EA8500 hw design default pcie2 reset gpio (gpio63) is used to reset the switch. That's why enabling pcie2 brings the switch into a working state. So let's just control the gpio63 without enabling the pcie2 slot. We have to remove the pcie2_pins node so the gpio63 is not defined twice. Because pcie2 node has a reference to pcie2_pins we have to remove it as well. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: move mmc specific nodes into v1.0 dtsiPavel Kubelun2018-05-224-150/+150
| | | | | | | | | These nodes are common for all revisions so put it into SoC v1.0 dtsi file. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: fix pcie tx termination offsetPavel Kubelun2018-05-222-0/+24
| | | | | | | | | | | | | | According to GPL tarballs and QSDK related branch tx termination offset for ipq8064 SoC version >= 2.0 should be equal to 0 and not 7. https://github.com/paul-chambers/netgear-r7800/blob/master/git_home/linux.git/sourcecode/arch/arm/mach-msm/board-ipq806x.c#L1682-L1685 Fix this. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: apply updated USB PHY settings to v2.0 SoCPavel Kubelun2018-05-224-22/+34
| | | | | | | | | | | | | | | | | | | USB PHY power settings introduced for ipq8065 SoC with commit 644a0d5 "ipq8065: adjust SS USB PHY power settings" According to that commit msg and in correspondence to GPL tarballs and related QSDK branch those settings are applied to ipq8064 SoCs of version >= 2.0. https://github.com/paul-chambers/netgear-r7800/blob/master/git_home/linux.git/sourcecode/arch/arm/mach-msm/board-ipq806x.c#L2507-L2514 Now as we have clarified that mass market boards are of SoC v2.0 move those USB PHY settings from ipq8065 (v3.0 SoC) dtsi to ipq8064 v2.0 dtsi. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: reference ipq8065 as ipq8064 v3.0Pavel Kubelun2018-05-228-8/+6
| | | | | | | | | | | ipq8065 is ipq8064 v3.0 > socinfo_init: v6, id=280, ver=3.0, raw_id=17, raw_ver=17, hw_plat=0, hw_plat_ver=65536 Include dtsi accordingly and remove the unneeded qcom-ipq8065-v1.0.dtsi Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: move mass market ipq8064 to v2 dtsiPavel Kubelun2018-05-2210-10/+10
| | | | | | | | | | | | | | | | | According to OEM bootlog entry mass market devices are ipq8064 SoC v2.0: > socinfo_init: v6, id=202, ver=2.0, raw_id=2064, raw_ver=2064, hw_plat=0, hw_plat_ver=65536 I've checked C2600, EA8500 and VR2600v but couldn't find other boards bootlog. I think it's safe to assume that other boards are also v2.0. R7500 may be an exception because it was the first device to hit the market. So switch to v2.0 dtsi. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: introduce ipq8064 SoC v2 dtsiPavel Kubelun2018-05-222-0/+2
| | | | | | | | | | | | | | | According to QCA internal numbering there are 3 versions of ipq8064/5 SoC: ipq8064 v1.0 - probably ipq8064 evaluation boards only ipq8064 v2.0 - probably ipq8064 mass market boards only ipq8064 v3.0 - aka ipq8065, boards based on ipq8065. Each next revision includes configuration differences from previous revision and adds something new. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* kernel: iqp806x low latency kernel does not bootMarc Benoit2018-05-222-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It keeps failing (R7800) with the stack trace below BUG: scheduling while atomic: kworker/0:1/26/0x00000002 (unwind_backtrace) from [<c02121d0>] (show_stack+0x10/0x14) (show_stack) from [<c03932e4>] (dump_stack+0x7c/0x9c) (dump_stack) from [<c0239b90>] (__schedule_bug+0x5c/0x80) (__schedule_bug) from [<c05b7260>] (__schedule+0x50/0x3f4) (__schedule) from [<c05b76a8>] (schedule+0xa4/0xd4) (schedule) from [<c05ba430>] (schedule_hrtimeout_range_clock+0xc8/0x100) (schedule_hrtimeout_range_clock) from [<c05ba480>] (schedule_hrtimeout_range+0x18/0x20) (schedule_hrtimeout_range) from [<c05b9f78>] (usleep_range+0x48/0x50) (usleep_range) from [<c03f333c>] (__clk_hfpll_enable+0x44/0xd0) (__clk_hfpll_enable) from [<c03f3474>] (clk_hfpll_set_rate+0xac/0xc4) (clk_hfpll_set_rate) from [<c03ec390>] (clk_change_rate+0xf4/0x1fc) (clk_change_rate) from [<c03ec510>] (clk_core_set_rate_nolock+0x78/0x94) (clk_core_set_rate_nolock) from [<c03ec54c>] (clk_set_rate+0x20/0x30) (clk_set_rate) from [<c0424168>] (dev_pm_opp_set_rate+0x190/0x26c) (dev_pm_opp_set_rate) from [<c04a8548>] (set_target+0x40/0x108) (set_target) from [<c04a4.140>] (__cpufreq_driver_target+0x3f4/0x488) (__cpufreq_driver_target) from [<c04a7494>] (od_dbs_timer+0xcc/0x154) (od_dbs_timer) from [<c04a7998>] (dbs_work_handler+0x2c/0x54) (dbs_work_handler) from [<c02309e8>] (process_one_work+0x1c0/0x2f0) (process_one_work) from [<c02319a8>] (worker_thread+0x2a4/0x404) (worker_thread) from [<c0235944>] (kthread+0xd8/0xe8) (kthread) from [<c020eef0>] (ret_from_fork+0x14/0x24) Signed-off-by: Marc Benoit <marcb62185@gmail.com> [slh: rebase for kernel v4.14 as well] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: define KERNEL_SIZE in KB instead of byte for the image generationStefan Lippers-Hollmann2018-05-221-5/+5
| | | | Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: increase kernel partition size for the Netgear Nighthawk X4 R7500v2Stefan Lippers-Hollmann2018-05-223-7/+7
| | | | | | | | | | | | | | | | | | Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the 2 MB reserved for the kernel partition by the OEM firmware anymore. This patch increases the kernel partition from 2 MB to 4 MB, at the expense of the rootfs, for all supported kernels. WARNING: This breaks sysupgrade! Flashing a firmware containing this changed partitioning from an older image with 2 MB reserved for the kernel partion requires the tftp recovery procedure, thereby losing all settings. This change follows the functional example of the Netgear r7800, but has not been runtime tested on a Netgear Nighthawk X4 R7500v2. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: increase kernel partition size for the Netgear Nighthawk X4 R7500Stefan Lippers-Hollmann2018-05-223-7/+7
| | | | | | | | | | | | | | | | | | | Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the 2 MB reserved for the kernel partition by the OEM firmware anymore. This patch increases the kernel partition from 2 MB to 4 MB, at the expense of the rootfs, for all supported kernels. WARNING: This breaks sysupgrade! Flashing a firmware containing this changed partitioning from an older image with 2 MB reserved for the kernel partion requires the tftp recovery procedure, thereby losing all settings. This change follows the functional example of the Netgear r7800, but has not been runtime tested on a Netgear Nighthawk X4 R7500 Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Cc: Jonas Gorski <jonas.gorski@gmail.com>
* ipq806x: increase kernel partition size for the Netgear Nighthawk X4 D7800Stefan Lippers-Hollmann2018-05-223-7/+7
| | | | | | | | | | | | | | | | | | | Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the 2 MB reserved for the kernel partition by the OEM firmware anymore. This patch increases the kernel partition from 2 MB to 4 MB, at the expense of the rootfs, for all supported kernels. WARNING: This breaks sysupgrade! Flashing a firmware containing this changed partitioning from an older image with 2 MB reserved for the kernel partion requires the tftp recovery procedure, thereby losing all settings. This change follows the functional example of the Netgear r7800, but has not been runtime tested on a Netgear Nighthawk X4 D7800. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Cc: Tathagata Das <tathagata@alumnux.com>
* ipq806x: increase kernel partition size for the TP-Link Archer VR2600vStefan Lippers-Hollmann2018-05-223-7/+7
| | | | | | | | | | | | | | | | | | The default image does not fit 2 MB anymore, expand kernel partition to 3 MB. Upgrading should work transparently via sysupgrade in both directions. Another option would be to merge "kernel" and "rootfs" into a single "firmware" partition using MTD_SPLIT_TPLINK_FW, but just changing the sizes of the existing partitioning has been deemed safer in the absence of an actual runtime test on an affected device; the maximum for rootfs changes from 10.4 MB to 9.4 MB. This change follows the example for the TP-Link Archer C2600, but has not been runtime tested on a TP-Link Archer VR2600v. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Cc: Sebastian Quilitz <zeraphim@x-pantion.de>
* ipq806x: increase kernel partition size for the TP-Link Archer C2600Stefan Lippers-Hollmann2018-05-222-5/+10
| | | | | | | | | | | | | | | | | | The default image does not fit 2 MB anymore, expand os-image partition to 4 MB. Upgrading works transparently via sysupgrade in both directions. Another option would have been to merge "os-image" and "rootfs" into a single "firmware" partition using MTD_SPLIT_TPLINK_FW, but just changing the sizes of the existing partitioning has been deemed safer and actually tested on an affected device; the maximum for rootfs changes from 27 MB to 25 MB. Run-tested on TP-Link Archer C2600. Signed-off-by: Joris de Vries <joris@apptrician.nl> [slh: extend comments and commit message, rename rootfs] Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: increase kernel partition size for the Netgear r7800Stefan Lippers-Hollmann2018-05-223-7/+7
| | | | | | | | | | | | | | | | | | | Starting with kernel 4.14 and gcc 7, the kernel doesn't fit into the 2 MB reserved for the kernel partition by the OEM firmware anymore. This patch increases the kernel partition from 2 MB to 4 MB, at the expense of the rootfs, for all supported kernels. WARNING: This breaks sysupgrade! Flashing a firmware containing this changed partitioning from an older image with 2 MB reserved for the kernel partion requires the tftp recovery procedure, thereby losing all settings. This patch is based on a corresponding change by Pavel Kubelun <be.dissent@gmail.com> and has been tested by Michael Yartys <michael.yartys@protonmail.com> Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: cleanup kernel configRam Chandra Jangir2018-05-221-14/+8
| | | | | | | | | | Disable MSM8960, MSM8974 and APQ8084 - since these are different SoC's than IPQ806x Removed unrequired serial configs - since ipq806x uses SERIAL_MSM only Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org> Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq806x: add kernel 4.14 supportRam Chandra Jangir2018-05-2268-0/+25602
| | | | | | | | | | | | | | | | | | - Rebased the patches for 4.14 - Dropped spi-qup and 0027, 0028, 0029 clk patches since it's already included in upstream. Tested on IPQ AP148 Board: 1) NOR boot and NAND boot 2) Tested USB and PCIe interfaces 3) WDOG test 4) cpu frequency scaling 5) ethernet, 2G and 5G WiFi 6) ubi sysupgrade Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org> Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* ipq40xx: add eva-image for FRITZ!Box 4040David Bauer2018-05-221-1/+4
| | | | | | | | | This commit adds an EVA flashable image for the FRITZ!Box 4040. The image contains the U-Boot with OpenWRT appended to it. This way we remove the need to use UART for initial flashing. Signed-off-by: David Bauer <mail@david-bauer.net>
* build: add apend-uboot commandDavid Bauer2018-05-221-0/+4
| | | | | | | This commit adds an append-uboot command to append U-Boot from the bin-directory. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: change wifi led trigger for Archer C50v3David Bauer2018-05-221-2/+2
| | | | | | | | This commit alters the TP-Link Archer C50v3 LED settings to use the phy trigger instead of the netdev one. This way the WiFi status is displayed even if the wifi interface name is altered. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: fix Archer C50v3 LED mappingDavid Bauer2018-05-221-4/+4
| | | | | | | This commit fixes the wrong LED mapping of the Archer C50 v3. Commit was tested with an EU device. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: enable rtl8366rb phyLucian Cristian2018-05-221-0/+1
| | | | | | is needed for at least tplink wr1043nd-v1 Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* ath79: fix loader-okli, lzma-loaderLucian Cristian2018-05-221-0/+1
| | | | | | | booting will hang most of the times on tl-wr1043nd-v1 without a KERNEL_CMDLINE value add anything as a placeholder as kernel command line is taken from DTS Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* build: prevent spurious package rebuilds under CONFIG_AUTOREMOVEJo-Philipp Wich2018-05-221-1/+1
| | | | | | | | | | | | | | | | When CONFIG_AUTOREMOVE is enabled, the build system touches an additional ".autoremove" stamp file in the cleaned build directory. Since the autoremove stamp file is touched after the compile process completed, it ends up being the most recent file of the package build directory, causing the timestamp.pl check of depends.mk to erroneously declare the ".built" and ".prepared" stamp files as stale, triggering a forced clean-build submake process. Fix the problem by using the ".built" stamp file as modification time reference when touching the ".autoremove" stamp file. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: Add support for PISEN TS-D084Chuanhong Guo2018-05-2211-0/+117
| | | | | | | | | | | | | | | | | | PISEN TS-D084 is an wireless router with a battery and integrated power supply based on Atheros AR9331. Specification: - 400/400/200 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 1x 10/100 Mbps Ethernet - 1T1R 2.4 GHz (AR9331) - 1x USB 2.0 Flash instruction: The manufacturer are using exactly the same firmware header as TP-LINK TL-WR703N (including device ID!). Simply upload the factory firmware into WebUI and flashing is done. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* kernel: enable THIN_ARCHIVES by defaultSergey Ryazanov2018-05-2225-24/+1
| | | | | | | | THIN_ARCHIVES option is enabled by default in the kernel configuration and no one target config disables it. So enable it by default and remove this symbol from target specific configs to keep them light. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: enable FUTEX_PI by defaultSergey Ryazanov2018-05-2225-24/+1
| | | | | | | | | New FUTEX_PI configuration symbol enabled if FUTEX and RT_MUTEX symbols are enabled. Both of these symbols are enabled by default in the generic config, so enable FUTEX_PI by default too to keep platform specific configs minimal. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: enable EXPORTFS by defaultSergey Ryazanov2018-05-2225-25/+1
| | | | | | | | OVERLAY_FS config symbol selects EXPORTFS since 4.12 kernel, we have OVERLAY_FS enabled by default, so enable EXPORTFS in the generic config of 4.14 and remove this option from platform specific configs. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: disable DRM_LIB_RANDOM by defaultSergey Ryazanov2018-05-2225-24/+1
| | | | | | | DRM_LIB_RANDOM config symbol selected only by DRM_DEBUG_MM_SELFTEST which is disable by default, so disable DRM_LIB_RANDOM by default too. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: disable DMA_{NOOP|VIRT}_OPS by defaultSergey Ryazanov2018-05-2225-48/+2
| | | | | | | These options do not used by any supported arch, so disable them by default to make arch configs a bit more clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: disable ARCH_WANTS_THP_SWAP by defaultSergey Ryazanov2018-05-2225-24/+1
| | | | | | | | Only one arch (x86_64) enables this option. So disable ARCH_WANTS_THP_SWAP by default and remove referencies to it from all configs (except x86_64) to make them clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* arc770: remove source-onlyEvgeniy Didin2018-05-221-1/+1
| | | | | | | | | | | | | | In commit 8b9cdebc9c53 ("arc770: mark as source-only") arc770 was marked as source-only because of iproute2 compile issues. With uClibc-ng version 1.0.30 issues with iproute2 were fixed. Lets remove "source-only" for arc770 as soon as uClibc-ng version will be updated to 1.0.30. Patch for uClibc-ng is here: https://patchwork.ozlabs.org/patch/917547/ Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org>
* uClibc-ng: update to 1.0.30Evgeniy Didin2018-05-221-2/+2
| | | | | | | | | | | | | | uClibc-ng 1.0.28 does not provide PF_VSOCK/AF_VSOCK definitions, which causes iproute2 v4.16.0 compile errors. In commit 57f2f80383b5 ("bits/socket.h: add missing defines") necessary defines were included and iproute2 builds fine. This commit now is part of uClibc-ng 1.0.30. Lets update uClibc-ng to latest 1.0.30 version. Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org>
* ar71xx: Fix build for dap-1330-a1 boardHauke Mehrtens2018-05-221-1/+1
| | | | | | | | | | | | | | | | Using a version number of 16 character causes a buffer overflow in the version number overwriting the first bit of the signature in the mkdapimg2 tool. I am not sure if the version number should be null terminated or not. This patch reduces the size of the version number by removing the number of private commits from it. This was the original version number which caused problems: OpenWrt-r6727+10 Now it uses this version number: OpenWrt-r6727 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath25: drop 4.9 kernel supportSergey Ryazanov2018-05-2212-3850/+0
| | | | Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* ath25: switch to 4.14 kernelSergey Ryazanov2018-05-221-1/+1
| | | | Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* ath25: add kernel 4.14 supportSergey Ryazanov2018-05-2212-0/+3865
| | | | | | Copy and refresh patches and config from 4.9, no more work is need. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: merge kmod-fbcon with kmod-fbTomasz Maciej Nowak2018-05-211-36/+14
| | | | | | | | | | | | | As of commit in kernel: 6104c37094 fbcon: Make fbcon a built-time depency for fbdev framebuffer console is build in into framebuffer module and there's no standalone fbcon module. Therefore drop the kmod-fbcon and enable console in kmod-fb. The only targets which use these modules are imx6 and geode, both are on kernel 4.14 so no fallback for other kernels is introduced. Being at that this commit also fixes autoload of fbdev for x86. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* build: use busybox gzip compatible force optionMathew McBride2018-05-211-1/+1
| | | | | | | | | | commit 138c763 ("build: add --force option to gzip in Build/gzip") added the --force flag to the gzip invocation. Under environments with busybox gzip (e.g Alpine Linux), this fails as busybox only recognizes "-f". Signed-off-by: Mathew McBride <matt@traverse.com.au>
* nftables: bump to 0.8.5 versionRosy Song2018-05-218-1594/+8
| | | | Signed-off-by: Rosy Song <rosysong@rosinson.com>
* libnftnl: bump to 1.1.0Rosy Song2018-05-213-1706/+3
| | | | Signed-off-by: Rosy Song <rosysong@rosinson.com>
* mvebu: initial support for Marvell Armada 7k and 8k DB boardsDamir Samardzic2018-05-213-0/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add initial support for cortex-a72 based Armada DB-88F8040-Modular and DB-88F7040-Modular development boards. DB-88F8040-Modular specifications: - Quad-core ARMv8 Cortex A72 CPU (up to 2 GHz) - DDR4 DIMM - 64 bits + ECC - 2 x 128 Mb SPI NOR flash memory - 2 x 1G Ethernet port via RGMII (RJ45) - 2 x SD card ports (4 bit port on CP, 8 bit port on AP) - 2 SERDES modules with the following interfaces each: - 2 x SATA Rev 3.0 port (Port1 via SERDES module CON4 (active port), Port0 via SERDES Module CON2 or CON1 (optional port)) - 3 x PCI Express (PCIe) Gen 3.0 (Port2 via SERDES module CON5 (active port), Port1 via SERDES module CON7 (optional port), Port0 via SERDES module CON6 (optional port)) - 2 x USB3 (USB 2.0 backward compatible) host (via SERDES module CON9 and CON10) - 1 x 10G port over SFP+ connector (via SERDES module CON8) - 1 x MCI interface by two over USB Type C connector - 4 x serial COM port driven by the 88F8040 UART interface and converted to USB via FTDI IC - I2C Master Interface - CP I2C 2x EEPROM @ Address 0x50 and 0x57 - 1 x I/O Expander @ Address 0x21 - Sample at Reset (SatR) memory device @ Address 0x4C and 0x4E - I2C Slave Interface (via SERDES module) - Connection to each device on the board via an I2C multiplexer - JTAG interface for CPU emulator - Board dimensions: 270 mm x 240 mm (main + SERDES module) - SERDES Module Dimensions: 70 mm x 105 mm DB-88F7040-Modular specifications: - Quad-core ARMv8 Cortex A72 CPU - CPU core operating speed of up to 1.6 GHz for Dual Core, 1.4 GHz for Quad Core - DDR4 - 32 bit + ECC on Module - SLM1366-V1 (DB-DDR4-40B-MODULE) 4 GByte 32-bit - 1 x 128Mb SPI NOR flash memory - 2 x 1G Ethernet port: 1 over RGMII (RJ45) and 1 over SGMII - SD card 4 bits port on AP - eMMc Module on CP - 1 SERDES Modules with the following interfaces each: - 1 x SATA Rev 3.0 port (via SERDES module CON4) - 1 x PCI Express (PCIe) Gen 3.0 (via SERDES module CON5) - 2 x USB 3.0 (USB 2.0 backward compatible) host (via SERDES module CON9 and CON10) - 1 x 10G port over SFP+ connector (via SERDES module CON8) - 2 x MCi interface by one over USB Type C connector - 4 x Serial COM port driven by the 88F7040 UA - RT interface and converted to USB via FTDI IC - I2C Master Interface - 2 x EEPROM at address 0x57 and 0x50 in AP and 2 x EEPROM at address 0x57 and 0x50 in CP - 1 x I/O Expander at address 0x21 - Sample at Reset (SatR) memory device at address 0x4C and 0x4E - I2C Slave Interface (via SERDES module) - Connection to each device on the board via an I2C multiplexer - JTAG interface for CPU emulator - Board dimensions - 270 mm x 240 mm (main + SERDES module) - SERDES Module Dimensions - 70 mm x 105 mm Booting from USB flash drive (dd sdcard image to the flash drive): 1. reset U-Boot environment: env default -a saveenv 2. prepare U-Boot manually (make sure to set correct dtb file name): setenv bootargs_root 'root=/dev/sda2 rw rootdelay=2 ip=dhcp' setenv fdtfile armada-7040-db.dtb setenv image_name Image setenv bootcmd 'usb start; ext4load usb 0:1 $kernel_addr $image_name; ext4load usb 0:1 $fdt_addr $fdtfile; setenv bootargs $console $mtdparts $bootargs_root; booti $kernel_addr - $fdt_addr' saveenv boot Signed-off-by: Damir Samardzic <damir.samardzic@sartura.hr>
* mvebu: initial support for Marvell Armada 3720 DB boardDamir Samardzic2018-05-214-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add initial support for Marvell Armada cortex-a53 based DB-88F3720-DDR3-Modular development board. Specifications: - Dual core ARMv8 Cortex-A53 CPU (up to 1.0 GHz) - 4Gb 16-bit DDR3/3L DRAM memory - 128Mb SPI NOR flash memory - 8Gb eMMC NAND flash memory - 1 x SATA Rev 3.0 port - 1 x PCI Express (PCIe) Gen 2.0 or 1 x mini PCI Express (PCIe) Gen 2.0 - 1 x 1G Ethernet port via RGMII (RJ45) - 1 x SD card port - 1 x USB3 (USB2 backward) host\device port via type C connector - 1 x USB2 host port via type A connector - 1 x serial COM port driven by the 88F3720 UART interface and converted to USB via FTDI IC (option to connect the UART DB9 adapter) - I2C Master Interface: - 1 x EEPROM @ address 0x57 - 1 x I/O Expanders @ address 0x22 - Sample at Reset (SatR) memory device @ address 0x4C - RTC clock generator PT7C4337AWE @ address 0x68 - USB3 switch PI5USB30213XEA @ address 0x0D - ID component of PHY module @ address 0x24 - 1 x JTAG interface for CPU emulator - 1 x SETM and JTAG debug interface - 1 x power connector for HDD supply - 1 x 12V DC jack power connector - Board dimensions: 150 mm x 179 mm - LED interface for system status Booting from SD card: 1. reset U-Boot environment: env default -a saveenv 2. prepare U-Boot with boot script: setenv bootcmd "load mmc 0:1 0x4d00000 boot.scr; source 0x4d00000" saveenv or manually: setenv fdt_name armada-3720-db.dtb setenv image_name Image setenv bootcmd 'mmc dev 0; ext4load mmc 0:1 $kernel_addr $image_name;ext4load mmc 0:1 $fdt_addr $fdt_name;setenv bootargs $console root=/dev/mmcblk1p2 rw rootwait; booti $kernel_addr - $fdt_addr' saveenv Signed-off-by: Damir Samardzic <damir.samardzic@sartura.hr>
* kernel: Add support spi-nor, Eon EN25QH32YuheiOKAWA2018-05-214-0/+40
| | | | | | | | | | Support Add spi-nor chip EN25QH32. JEDEC is 1c7016. Can't boot issue, new revision hardware is EN25QH32 flash chip. example, MZK-DP150N (ramips). https://bugs.openwrt.org/index.php?do=details&task_id=1534 Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com>
* kernel: Add configfs support for USB HID gadgetHarvey Phillips2018-05-211-0/+17
| | | | | | | Added a rule to usb.mk to build usb_f_hid.ko for configfs support Tested on a Raspberry Pi Zero W Signed-off-by: Harvey Phillips <xcellerator@gmx.com>
* ath10k-firmware: Fix mirror hash sumHauke Mehrtens2018-05-211-1/+1
| | | | | | | | This now matches what was generated locally on my PC and the file on the mirror server. Fixes: 349fe46103359 ("ath10k-firmware: Update QCA988X firmware to the latest version") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* openwrt-keyring: bundle latest usign certificatesJo-Philipp Wich2018-05-201-3/+3
| | | | | | Includes the public usign certificates used by the 18.06.* release builds. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* base-files: depend on openwrt-keyringJo-Philipp Wich2018-05-201-1/+1
| | | | Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* openwrt-keyring: rename from lede-keyringJo-Philipp Wich2018-05-201-7/+8
| | | | | | | Also let the new openwrt-keyring package provide lede-keyring for backwards compatibility. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* wireguard: bump to 20180519Jason A. Donenfeld2018-05-191-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * chacha20poly1305: add mips32 implementation "The OpenWRT Commit" - this significantly speeds up performance on cheap plastic MIPS routers, and presumably the remaining MIPS32r2 super computers out there. * timers: reinitialize state on init * timers: round up instead of down in slack_time * timers: remove slack_time * timers: clear send_keepalive timer on sending handshake response * timers: no need to clear keepalive in persistent keepalive Andrew He and I have helped simplify the timers and remove some old warts, making the whole system a bit easier to analyze. * tools: fix errno propagation and messages Error messages are now more coherent. * device: remove allowedips before individual peers This avoids an O(n^2) traversal in favor of an O(n) one. Before systems with many peers would grind when deleting the interface. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 12:57:53 +0000