aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* imx-uuc: updated to latest git HEADKrystian Kozak2018-06-081-3/+3
| | | | | | | | | | 8e29d86 linuxrc: remove superfluous shebang line 12d2045 gitignore: remove Windows stuff 57d8969 Add travis hint 8edf4cc sdimage: use fsync before closing the device (fixes #1) d395b31 uuc: fix some compiler warnings Signed-off-by: Krystian Kozak <krystian.kozak20@gmail.com>
* busybox: udhcpc: no MSG_DONTROUTE when sending packetAdi Shammout2018-06-072-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts a change made in Sep 2017 [1] which introduced MSG_DONTROUTE flag to prevent udhcpc from reaching out to servers on a different subnet. That change violates RFC2131 by forcing fully configured clients, who got their configurations through an offer relayed by a DHCP relay, from renewing through a unicast request directly to the DHCP server, resulting in the client resorting to boradcasting lease extension requests instead of unicasting them, further breaking RFC2131. The problem with MSG_DONTROUTE appears when talking to a properly configured DHCP server that rejects non-compliant requests. Such server will reject lease extension attempts sent via broadcast rather than unicast, as is the case with Finnish ISPs Telia and DNA as well as Estonian ISP Starman. Once the lease expires without renewal, udhcpc enters init mode, taking down the interfaces with it, and thus causing interruption on every lease expiry. On some ISPs (such as the ones mentioned above) that can be once every 10-20 minutes. The interruptions appear in the logs as such: ---- udhcpc: sending renew to x.x.x.x udhcpc: send: Network unreachable udhcpc: sending renew to 0.0.0.0 udhcpc: sending renew to 0.0.0.0 ... udhcpc: lease lost, entering init state Interface 'wan' has lost the connection Interface 'wan' is now down Network alias 'eth0' link is down udhcpc: sending select for y.y.y.y udhcpc: lease of y.y.y.y obtained, lease time 1200 Network alias 'eth0' link is up Interface 'wan' is now up ---- During lease extension, a fully configured client should be able to reach out to the server from which it recieved the lease for extension, regardless in which network it is; that's up to the gateway to find. [2] This patch ensures that. [1] http://lists.busybox.net/pipermail/busybox-cvs/2017-September/037402.html [2] https://www.netmanias.com/en/post/techdocs/6000/dhcp-network-protocol/ understanding-dhcp-relay-agents Signed-off-by: Adi Shammout <adi.shammout@outlook.com> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* logd: create log directory for log_fileKarl Palsson2018-06-072-1/+3
| | | | | | | If log_file is specified, make sure its directory exists. Signed-off-by: Karl Palsson <karlp@etactica.com> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* ath79: fix qca956x SoC bootLucian Cristian2018-06-071-0/+17
| | | | | | based on old ar71xx irq.c driver Signed-off-by: Lucian Cristian <lucian.cristian@gmail.com>
* ar71xx: add support for OCEDO KoalaDavid Bauer2018-06-0714-0/+206
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the OCEDO Koala SOC: Qualcomm QCA9558 (Scorpion) RAM: 128MB FLASH: 16MiB WLAN1: QCA9558 2.4 GHz 802.11bgn 3x3 WLAN2: QCA9880 5 GHz 802.11nac 3x3 INPUT: RESET button LED: Power, LAN, WiFi 2.4, WiFi 5, SYS Serial: Header Next to Black metal shield Pinout is 3.3V - GND - TX - RX (Arrow Pad is 3.3V) The Serial setting is 115200-8-N-1. Tested and working: - Ethernet - 2.4 GHz WiFi - 5 GHz WiFi - TFTP boot from ramdisk image - Installation via ramdisk image - OpenWRT sysupgrade - Buttons - LEDs Installation seems to be possible only through booting an OpenWRT ramdisk image. Hold down the reset button while powering on the device. It will load a ramdisk image named 'koala-uImage-initramfs-lzma.bin' from 192.168.100.8. Note: depending on the present software, the device might also try to pull a file called 'koala-uimage-factory'. Only the name differs, it is still used as a ramdisk image. Wait for the ramdisk image to boot. OpenWRT can be written to the flash via sysupgrade or mtd. Due to the flip-flop bootloader which we not (yet) support, you need to set the partition the bootloader is selecting. It is possible from the initramfs image with > fw_setenv bootcmd run bootcmd_1 Afterwards you can reboot the device. Signed-off-by: David Bauer <mail@david-bauer.net>
* hostapd: make cli treat UNKNOWN COMMAND as failingDenton Gentry2018-06-071-0/+13
| | | | | | | | | | | Avoid infinite loop at 100% CPU when running hostapd_cli if CONFIG_CTRL_IFACE_MIB is not defined. _newselect(4, [3], NULL, NULL, ...) recvfrom(3, "UNKNOWN COMMAND\n", 4095, 0, NULL, NULL) = 16 sendto(3, "STA-NEXT UNKNOWN COMMAND", 24, 0, NULL, 0) = 24 Signed-off-by: Denton Gentry <denny@geekhold.com>
* ipq806x: Enlarge R7800 flash - use netgear partitionHannu Nyman2018-06-071-8/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Increase the available flash memory size in Netgear R7800 by taking into the use the unused "netgear" partition that is located after the firmware partition. Available flash space for kernel+rootfs+overlay increases by 68 MB from 32 MB to 100 MB. In a typical build, overlay space increases from 15 to 85, increasing the package installation possibilities greatly. Reverting to the OEM firmware is still possible, as the OEM firmware contains logic to initialise the "netgear" partition if its contents do not match expectations. In OEM firmware, "netgear" contains 6 UBI sub-partitions that are defined in /etc/netgear.cfg and initialisation is done by /etc/preinit Tested with Openwrt master r7093-4fdc6ca31b and OEM V1.0.2.52 Reference to forum discussion in Netgear R7800 exploration thread: https://forum.lede-project.org/t/netgear-r7800-exploration-ipq8065-qca9984/285/1118 (messages 1118-1158) Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
* ipq806x: Limit NR_CPUS to 2Rosen Penev2018-06-071-1/+1
| | | | | | | | | | ipq806x is all dual core processors. ipq807x is quad core. Removes this from dmesg: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ethtool: Update to 4.16Rosen Penev2018-06-071-2/+2
| | | | | | Tested on Turris Omnia (mvebu). Signed-off-by: Rosen Penev <rosenp@gmail.com>
* iperf: Update to 2.0.11Rosen Penev2018-06-071-2/+2
| | | | | | Tested on Turris Omnia (mvebu). Signed-off-by: Rosen Penev <rosenp@gmail.com>
* gdb: Update to 8.1Rosen Penev2018-06-071-2/+2
| | | | | | Tested on Turris Omnia (mvebu). Signed-off-by: Rosen Penev <rosenp@gmail.com>
* strace: Update to 4.22Rosen Penev2018-06-071-3/+3
| | | | | | | | | SourceForge is deprecated according to upstream, so switch to main site for downloads. Tested on Turris Omnia (mvebu). Signed-off-by: Rosen Penev <rosenp@gmail.com>
* kernel: bump 4.9 to 4.9.106Koen Vandeputte2018-06-074-165/+187
| | | | | | | | | Refreshed all patches Compile-tested on: ar71xx Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: add WLAN, Ethernet-Switch with LAN/WAN and Status LED to DorinCatrinel Catrinescu2018-06-073-6/+15
| | | | Signed-off-by: Catrinel Catrinescu <cc@80211.de>
* zynq: remove support for kernel 4.4Luis Araneda2018-06-071-752/+0
| | | | Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: switch to kernel 4.14Luis Araneda2018-06-071-2/+2
| | | | | | | | Also, remove the source-only qualifier Run-tested: ZedBoard Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: refresh kernel 4.14 configurationLuis Araneda2018-06-071-101/+78
| | | | Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: copy config to kernel 4.14Luis Araneda2018-06-071-0/+752
| | | | | | | The file will be used as a base configuration for kernel 4.14 Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* uboot-zynq: update to 2017.03Luis Araneda2018-06-072-5/+5
| | | | | | Compile-tested: ZedBoard Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: fix detection of the zybo boardLuis Araneda2018-06-071-3/+8
| | | | | | | | | | The board_name was being tested for "xlnx,zynq-zybo", but the .dts compatible string is "digilent,zynq-zybo" Also, sorted the boards alphabetically, and added an error message for unsupported boards Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: remove hard-coded network configurationLuis Araneda2018-06-072-20/+0
| | | | | | | | | | This is no longer necessary since commit 57776e6 (base-files: remove default /etc/config/network, generate it via board.d instead) Run-tested: ZedBoard Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: reworked image creation processLuis Araneda2018-06-073-198/+30
| | | | | | | | | | | | | | | | | | | After commit a1248da (zynq: convert to new image build code), all boards, became unbootable, entering into a boot loop. Replace the compressed kernel zImage by an uncompressed Image, which is compressed after with gzip. Also, enable the creation of an initramfs image by default. Change images' filename to match the compatible string from the respective .dts file (<vendor>_<model>). Also, use the shared mkits.sh script and remove the target specific one. Fixes: FS#1204 Run-tested: ZedBoard Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* brcm2708: Update brcm2708-gpu-fw packageChristo Nedev2018-06-071-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem - rapsberry pi 3 b/b+ does not boot with bcm2710 images! How Raspberry Pi boots Actualy? When Raspberry is switched on GPU is activated. 1. GPU execute First stage bootloader from ROM. First stage bootloader mount the FAT boot partition on the SD card and execute second stage bootloader (bootcode.bin). 2. Second stage bootloader (bootcode.bin) activate SDRAM. Load the GPU firmware (start.elf). 3. GPU firmware (start.elf) a) display Rainbow splash. b) read firmware configuration file config.txt and split the RAM using fixup.dat. c) loads a cmdline.txt d) enables the CPU. e) loads the kernel image configurable via config.txt In your target/linux/brcm2708/image/config.txt 493 ## kernel (string) 494 ## Alternative name to use when loading kernel. 495 ## 496 #kernel="" it is not configured! But in your target/linux/brcm2708/image/Makefile 75 KERNEL_IMG := kernel8.img 76 DEVICE_TITLE := Raspberry Pi 3B/3B+ you have kernel8.img GPU Firmware search order by default for a PI 3 is: kernel8.img if found boot in 64 bit mode kernel8-32.img if found boot in 32 bit mode kernel7.img if found boot in 32 bit mode kernel.img if found boot in 32 bit mode But a PI 2 will start the search from kernel7.img and a PI 1 only looks for kernel.img. Оbviously the kernel has been found. But something goes wrong and the device is restarted. In your package/kernel/brcm2708-gpu-fw/Makefile 11 PKG_NAME:=brcm2708-gpu-fw 12 PKG_VERSION:=2017-08-08 13 PKG_RELEASE:=e7ba7ab135f5a68b2c00a919ea9ac8d5528a5d5b boot loader is 10 monts old. In conclusion, the best way to solve the problem is to update the boot loader! Fixup_cd.dat and start_cd.elf files are not necessary. These are used when GPU memory is set to 16 MB, which disables some GPU features. I did not remove them just in case! cheers Signed-off-by: Christo Nedev <christo.nedev@gmail.com>
* ramips: fix reboot with W25Q256 with 4-address-mode enabledDaniel Golle2018-06-071-0/+73
| | | | | | | | | | | | | | | Some board vendors actually changed the loader to expect the chip to come up in 4-address-mode and flipped the ADP bit in the flash chip's configuration register which makes it come up in 4-address-mode. Hence it doesn't make sense to avoid switching to 4-address-mode on those boards but the opposite as otherwise reboot hangs eg. on the WrtNode2 boards. Fix this by checking the ADP register and only using SPI_NOR_4B_READ_OP on chips which have ADP==0 (come up in 3-byte mode). See also datasheet section 7.1.11 Power Up Address Mode (ADP) Fixes: 22d982ea0 ("ramips: add support for switching between 3-byte and 4-byte addressing on w25q256 flash") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ebtables: update to latest git 2018-06-06Hans Dedecker2018-06-061-3/+3
| | | | | | | 5699354 extensions: fix build failure on fc28 e6359ee build: update ebtables.h from kernel and drop local unused copy Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ar71xx: switch CPE/WBS 210/510 to okli-loaderMatthias Schiffer2018-06-061-1/+4
| | | | | | | | | | | | | | | | | | | | | We recently increased the kernel partition size of the CPE/WBS 210/510. This works fine for new installations of the factory image, but on sysupgrades, the partition table read by the bootloader is not adjusted. This limits the maximum size of the kernel loaded by the bootloader to the old partition size. While adjusting the partition table would be a cleanest solution, such a migration would have to happen before an upgrade to a new version with a newer kernel. This is error-prone and would require a two-step upgrade, as we mark the partition table partition read-only. Instead, switch from the lzma-loader with embedded kernel to the okli-loader, so only the tiny lzma-loader is loaded by the bootloader as "kernel", and the lzma-loader will then load the rest of the kernel by itself. Fixes: e39847ea2f70 ("ar71xx: increase kernel partition size for CPE/WBS 210/510") Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ath79: lzma-loader: sync with ar71xx targetMatthias Schiffer2018-06-067-11/+29
| | | | | | | | | | | | | | Import all improvements made in the lzma-loader since development on the ath79 target started. This also reverts fe594bf90d09 ("ath79: fix loader-okli, lzma-loader"), as is obsoleted by 2ad60168b6af ("ar71xx: lzma-loader: move padding workaround to gzip step"). Likely, many of the changes should be ported to the ramips lzma-loader as well, but I don't have a device to test this. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: make loader-okli build step more genericMatthias Schiffer2018-06-061-2/+3
| | | | | | Add support for different loader types. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: lzma-loader: constify kernel argv arrayMatthias Schiffer2018-06-061-1/+1
| | | | | | | By making the kernel argv array const, the .data section can always be omitted from the laoder binary. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: lzma-loader: set page size to 4KBMatthias Schiffer2018-06-061-1/+1
| | | | | | | | The text section in the ELF loader is aligned to the maximum page size, which defaults to 64KB. Reduce it to the actual page size to avoid wasting flash space for this alignment. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ar71xx: lzma-loader: move padding workaround to gzip stepMatthias Schiffer2018-06-062-2/+5
| | | | | | | | | | | | | | | | | | | | | | | Some devices (TP-Link TL-WR1043ND v1) don't boot reliably when the uncompressed loader is too small. This was workarounded in the loader by adding 512KB of padding to the .data section of the loader binary. This approach had two issues: - The padding was only working when .data was non-empty (otherwise the section would become NOBITS, omitting it in the binary). .data was only empty when no CMDLINE was set, leading to further workarounds like fe594bf90d09 ("ath79: fix loader-okli, lzma-loader"), and this workaround was only effective because a missing "const" led to the kernel argv being stored in .data instead of .rodata - The padding was not only added to the compressed .gz loader, but also uncompressed .bin and .elf loaders. The prevented embedding the kernel cmdline in the loader for non-gz loader types. To fix both issues, move the creation of the padding from the linker script to the gzip step. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* base-files: fix UCI config parsing and callback handlingTony Ambardar2018-06-062-9/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are several long-standing issues present in the UCI shell API as documented in https://wiki.openwrt.org/doc/devel/config-scripting. They relate both to high-level, user-defined callback functions used to process UCI config files, and also to low-level functions used within scripts generally. The related problems have been encountered now and in the past, e.g. https://forum.openwrt.org/viewtopic.php?id=54295, and include: a) UCI parsing option() function and user-defined option_cb() callbacks being erroneously called during processing of "list" config file entries; b) normal usage of the low-level config_set() unexpectedy calling any defined option_cb() if present; and c) handling of the list_cb() not respecting the NO_CALLBACK variable. Root causes include a function stack "inversion", where the low-level config_set() function incorrectly calls the high-level option() function, intended only for processing the "option" keyword of UCI config files. This change addresses the inversion and other issues, making the option handling code more consistent and smaller, and simplifying developers' usage of UCI callbacks. Signed-off-by: Tony Ambardar <itugrok@yahoo.com> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
* kernel: bump 4.14 to 4.14.48Stijn Tintel2018-06-0546-383/+550
| | | | | | | | | | | | | | | | | | Remove upstreamed patches: generic/pending/101-clocksource-mips-gic-timer-fix-clocksource-counter-w.patch generic/pending/103-MIPS-c-r4k-fix-data-corruption-related-to-cache-coherence.patch generic/pending/182-net-qmi_wwan-add-BroadMobi-BM806U-2020-2033.patch lantiq/0025-MIPS-lantiq-gphy-Remove-reboot-remove-reset-asserts.patch Update patches that no longer apply: generic/pending/811-pci_disable_usb_common_quirks.patch ath79/0009-MIPS-ath79-add-lots-of-missing-registers.patch Fixes CVE-2018-6412. Compile-tested: octeon, x86/64. Runtime-tested: octeon, x86/64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* scripts: Replace obsolete POSIX tmpnam in slugimage.pl with File::Temp functionTed Hess2018-06-051-4/+4
| | | | Signed-off-by: Ted Hess <thess@kitschensync.net>
* hostapd: properly build hostapd-only SSL variantsDaniel Golle2018-06-051-11/+11
| | | | | | | Make sure hostapd-openssl is actually build against OpenSSL, same for wolfSSL. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: modules: package module for Exar 8250 UARTsDaniel Golle2018-06-052-0/+97
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: backport patch to fix dst handling for offloaded connectionsFelix Fietkau2018-06-051-0/+49
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* hostapd: expose device taxonomy signature via ubusFelix Fietkau2018-06-051-0/+6
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* hostapd: add support for client taxonomy in the full configFelix Fietkau2018-06-052-5/+29
| | | | | | | This can be used to fingerprint clients to try to identify the exact model Signed-off-by: Felix Fietkau <nbd@nbd.name>
* gcc: remove support for version 6.3.0Felix Fietkau2018-06-0526-929/+0
| | | | | | It is obsoleted by gcc 7 Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mt76: update to the latest versionFelix Fietkau2018-06-051-3/+3
| | | | | | | | | | | | | | | 20c0766 mt7603: adjust rx hang watchdog for MT7628 664e321 mt7603: add extra PSE hang check signature for MT7628 f24b56f update MT7628 firmware to the latest version d87e4b0 mt7603: clear PSE reset bit if PSE reset fails 0ef26ef mt76: only stop tx queues on offchannel, not during the entire scan f399da3 mt76: prevent tx scheduling during channel change 21c1e1e mt76: move ieee80211_hw allocation to common core 730c292 mt76: wait for pending tx to complete before switching channel fcbb49e mt76x2: use udelay instead of usleep_range in mt76x2_mac_stop 792dbe0 mt7603: do not hold dev->mutex while flushing dev->mac_work Signed-off-by: Felix Fietkau <nbd@nbd.name>
* map: make tunnel encapsulation limit support configurable (FS#1501)Hans Dedecker2018-06-042-8/+10
| | | | | | | | | | | | Be compatible with ISPs which don't support the destination option header containing the tunnel encapsulation limit as reported in FS#1501. Setting the uci parameter encaplimit to ignore; allows to disable the insertion of the destination option header in the map-e packets. Otherwise the tunnel encapsulation limit value can be set to a value from 0 till 255 by setting the encaplimit uci parameter accordingly. If no encaplimit value is specified the default value is 4 as before. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* netifd: update to latest git HEAD (FS#1501)Hans Dedecker2018-06-041-4/+4
| | | | | | a580028 system-linux: make encaplimit configurable for ip6 tunnels (FS#1501) Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* odhcp6c: make ds-lite/map tunnel encapsulation limit support configurable ↵Hans Dedecker2018-06-043-3/+9
| | | | | | | | | | | | | | (FS#1501) Be compatible with ISPs which don't support the destination option header containing the tunnel encapsulation limit as reported in FS#1501 for dynamic created ds-lite/map interfaces. Setting the uci parameter encaplimit_dslite/map to ignore; allows to disable the insertion of the destination option header for the dynamic created ds-lite/map interface. Otherwise the tunnel encapsulation limit value can be set to a value from 0 till 255 by setting the encaplimit_dslite/map uci parameter accordingly. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ds-lite: make tunnel encapsulation limit support configurable (FS#1501)Hans Dedecker2018-06-042-3/+7
| | | | | | | | | | | | Be compatible with ISPs which don't support the destination option header containing the tunnel encapsulation limit as reported in FS#1501. Setting the uci parameter encaplimit to ignore; allows to disable the insertion of the destination option header in the ds-lite packets. Otherwise the tunnel encapsulation limit value can be set to a value from 0 till 255 by setting the encaplimit uci parameter accordingly. If no encaplimit value is specified the default value is 4 as before. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* mvebu: fix broken console on WRT32X (venom)Michael Gray2018-06-013-0/+208
| | | | | | | | | | | | | | | The console bootarg is being corrupted on boot, causing various issues including broken sysupgrade. Utilising the bootargs mangle patch from other targets, hardcode the console arguments and fetch the rootfs from the bootloader. Kernel command line: console=ttyS0,115200 root=/dev/mtdblock8 Bootloader command line (ignored): console= root=/dev/mtdblock8 Please cherry pick to 18.06 too Signed-off-by: Michael Gray <michael.gray@lantisproject.com>
* oxnas: bring in new oxnas targetDaniel Golle2018-06-0139-0/+6351
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Reboot the oxnas target based on Linux 4.14 by rebasing our support on top of the now-existing upstream kernel support. This commit brings oxnas support to the level of v4.17 having upstream drivers for Ethernet, Serial and NAND flash. Botch up OpenWrt's local drivers for EHCI, SATA and PCIe based on the new platform code and device-tree. Re-introduce base-files from old oxnas target which works for now but needs further clean-up towards generic board support. Functional issues: * PCIe won't come up (hence no USB3 on Shuttle KD20) * I2C bus of Akitio myCloud device is likely not to work (missing debounce support in new pinctrl driver) Code-style issues: * plla/pllb needs further cleanup -- currently their users or writing into the syscon regmap after acquireling the clk instead of using defined clk_*_*() functions to setup multipliers and dividors. * PCIe phy needs its own little driver. * SATA driver is a monster and should be split into an mfd having a raidctrl regmap, sata controller, sata ports and sata phy. Tested on MitraStar STG-212 aka. Medion Akoya MD86xxx and Shuttle KD20. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* uboot-oxnas: fix build with newer GCCDaniel Golle2018-06-012-0/+593
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* oxnas: kill old oxnas targetDaniel Golle2018-06-0162-15085/+0
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* netifd: drop conflicting 'device' interface propertyIvan Shapovalov2018-06-013-5/+1
| | | | | | | | | | Do not set device runtime property on interfaces in the hotplug handler and in fixup_interfaces(). This property conflicts with device option in several proto handlers (mainly QMI and other WWAN/3G protos) and does not seem to be used anywhere. Signed-off-by: Ivan Shapovalov <intelfx@intelfx.name> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [PKG_RELEASE increase]
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-01 11:12:29 +0000