aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* generic: unlock Winbond flash on bootMatthias Schiffer2018-01-112-0/+74
| | | | | | | | | | | | The underlying issue breaking Spansion flash has been fixed with "mtd: spi-nor: wait until lock/unlock operations are ready" and "mtd: spi-nor: wait for SR_WIP to clear on initial unlock", so we can support unlocking for Winbond flash again. This is necessary to have writable flash on certain UBNT devices with some bootloader versions. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* sunxi: enable missing config symbolJo-Philipp Wich2018-01-111-0/+1
| | | | | | | | Enable CONFIG_MFD_AXP20X_I2C after the switch to Kernel 4.9, this symbol is reportedly required to get USB working on the Banana Pi. Ref: https://forum.lede-project.org/t/sunxi-kernel-4-9-usb-not-working/10513 Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* lantiq: create ATM/PTM interfaces with dsl as netdev nameMathias Kresin2018-01-102-1/+13
| | | | | | | | | | | | | | | | | | | | | Renaming an atm etherbride using 'ip link' (via hotplug) is racy since the original netdev might disappear before br2684ctl has finished appling it's setting: local2.notice br2684ctl[1667]: Interface "nas0" created sucessfully local2.notice br2684ctl[1667]: Communicating over ATM 0.8.35, encapsulation: LLC kern.info kernel: dsl0: renamed from nas0 kern.err kernel: br2684:br2684_regvcc: tried to attach to non-existent device local2.err br2684ctl[1667]: Could not configure interface:No such device or address By passing the final used netdev name to br2684ctl_wrap another race condition workaround will be enabled again. Change the lantiq ptm driver to create a netdev with the name dsl as well. Albeit the rename via 'ip link' works fine so far, using a different approach for ptm then atm could be confusing. Signed-off-by: Mathias Kresin <dev@kresin.me>
* armvirt: re-enable VFP supportJo-Philipp Wich2018-01-101-1/+0
| | | | | | | | | | Enable CONFIG_VFP again which was disabled during the 4.9 -> 4.14 bump. Boot tested both 32 and 64 bit subtargets using initramfs images with the qemu-system-arm and qemu-system-aarch64 emulators. Fixes: aa100b66f2 ("armvirt: bump to v4.14") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* armvirt: 64: add missing kernel config symbolsJo-Philipp Wich2018-01-101-0/+13
| | | | | Fixes: aa100b66f2 ("armvirt: bump to v4.14") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: bump 4.4 to 4.4.110Kevin Darbyshire-Bryant2018-01-1025-123/+134
| | | | | | | | | | Refresh patches Fixes: CVE-2017-5754 aka Meltdown Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> [fix typo in commit msg, conflict after 4.14 bump] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: bump 4.9 to 4.9.75Kevin Darbyshire-Bryant2018-01-1018-41/+41
| | | | | | | | | | | | | Refresh patches Fixes: CVE-2017-5754 aka Meltdown Tested-on: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [fix conflict after 4.14 bump] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kirkwood: sort occurrences of boardame alphabeticallyMathias Kresin2018-01-094-88/+87
| | | | | | | This restores the alphabetical sort that was present before the renaming of boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: add pogoplug v4Alberto Bursi2018-01-094-1/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | also known as POGO-V4-A3-02 or POGO-V4-A3-01 SoC: Marvell 88F6192 800Mhz SDRAM memory: 128MB Gigabit ethernet: 1 Marvell 88E1310 Flash memory: 128MB 2 status LEDs (one green one red) 1 "Eject" button on the back (used as "Reset" button) 1 USB 2.0 port (on upper side) 1 sata slot (power + data) for 2.5'' drives (upper side) 2 USB 3.0 ports from a controller on PCIe x1 of the SoC 1 full-size SDcard slot (fits a whole SD card into it) This device supports the (linux-only) kwboot tool to send a new uboot over serial console, so it is easy to unbrick in case the uboot is erased and the device won't boot. ----- Install instructions: ----- Since it's not possible to get ssh access to these devices, the only way to take control is to solder pins to get TTL serial access. Case can be opened by removing screws beneath two rubber feet at back of device, then lifting while prying the sides of the upper part out to unhook a latch on each side about 2/3rds of the way toward the front. Serial connection pins are those labeled "J11", left of SD as you face SD opening. Pins are (from left to right, i.e. the first in the list is the nearest to the SD slot) GND, Rx, Tx. Do not connect +V pin if you use a USB (self-powered) TTL-to-USB dongle. Any USB TTL-to-USB converter will work. Baud rate is 115200, parity "none", databits "8", flow control "none". Stock uboot is unable to read ubi partitions (nor usb) so we will replace it first with our uboot. Start a TFTP server at IP address 169.254.254.254, and place the uboot.kwb file in the folder of the server. Start the serial session and then power up the device. As soon as you see text on the serial start pressing random letter keys to stop the boot process. If you see something like the following line you can proceed: CE>> Otherwise if text is still scrolling by you missed the opportunity, pull the plug and try again. write printenv ethaddr The uboot will write something like this: ethaddr=00:50:43:00:02:02 This is the device's MAC address, also present in the sticker under the device. Write this down as we will need to add it in the new uboot configuration. Use the following commands to load the new uboot: tftp 0x20000 u-boot.kwb If the uboot confirms that the transfer was successful, then you can write it to flash with the following commands: nand erase 0 0x200000 nand write 0x20000 0 0x1c0000 if after the last command the uboot wrote "xxxx bytes written: OK" then it was written correctly and we can proceed. If it did not go well, try again or ask assistence in forums. Shutting down or rebooting at this time will brick the device, to unbrick it you will need to use the kwboot tool from a Linux PC or Virtual Machine. Now write: reset and press enter, the device will reboot and you should see again text scrolling by. Press a random key to stop it, and now you should see pogoplugv4> We now add the MAC address back, write: setenv ethaddr '00:50:43:00:02:02' Confirm that the uboot has understood by writing printenv ethaddr If all looks ok, save the setting with saveenv At this point the uboot is configured, and we only need to load the firmware in the flash memory. Follow the steps below in "Firmware recovery procedure". ---- Firmware recovery procedure ---- The new uboot allows easy recovery from a bad firmware upgrade where you can't access the device anymore over ssh or luci. Take a USB flash drive formatted as FAT32, and copy the initramfs image file in it (it will have "initramfs" in the file name), then rename it as "initramfs.bin". Insert the USB drive in the USB 2.0 port of the pogoplug (the port at the top). Power up the device, and wait for it to finish booting. The uboot should find and load the "initramfs.bin" from usb and if you are connected with serial you should see the linux kernel boot log (text scrolling by). Once it is done, press Enter and you will be greeted by the OpenWRT banner. If you were not connected with serial just wait a bit and, you will be able to access it with ssh or luci web interface (once you find its IP). The recovery "initramfs" images are run from RAM, so you will have to do a normal sysupgrade (firmware upgrade) to write a firmware image to flash memory. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it>
* kirkwood: sync image filename with boardnameMathias Kresin2018-01-091-34/+42
| | | | | | | | | | Use <manufacturer>_<modelname> as image name. Use the BOARD_NAME variable to ensure that the former used boardname is still used as the subdirectory name for the sysupgrade-tar image, to not break sysupgrade from earlier versions. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: use the generic board detectMathias Kresin2018-01-099-112/+42
| | | | | | | Drop the target specific detection function in favour of the generic one provided by base-files. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: use image metadataMathias Kresin2018-01-092-21/+4
| | | | | | | Append and enforce image metadata. Remove the device specific image checks, they are replaced by image metadata. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: fix nsa310b compatible stringsMathias Kresin2018-01-091-1/+1
| | | | | | Use a destinct compatible string fro the nsa310b. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: fix compatible string in ib62x0 dtsMathias Kresin2018-01-092-0/+9
| | | | | | | | There is no point in being that specifc in a generic dts covering a range of boards. Keep only the the generic compat string to use it for a devicetree based boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: drop support for orphaned boardsMathias Kresin2018-01-095-299/+3
| | | | | | | No image build code for the Guruplug, Sheevaplug and NSA310S exists. Drop support for the boards for now. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kirkwood: cleanup image build codeMathias Kresin2018-01-091-26/+8
| | | | | | | | | | | | | | Drop NAND_BLOCKSIZE, UBI_OPTS and UBIFS_OPTS. They are either used by not supported filesystems or by the legacy image build code. Add common used options/images to the default build code and override the options where necessary. Don't export the kernel image, it isn't required by any board. While at it, change the file extension for the sysupgrade images to bin. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ipq806x: drop kernel 4.4 leftoversMathias Kresin2018-01-0910-3628/+0
| | | | | | | | Remove the kernel 4.4 specific devicetree source files. Fixes: 3a3564ead5e4 ("ipq806x: remove v4.4 support") Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: fix Archer C7v4 5GHz MAC-addressDavid Bauer2018-01-091-1/+4
| | | | | | | | | | | The TP-Link firmware uses (primary_mac-1) as MAC-address for the 5GHz WiFi. This applies the same behaviour to LEDE. Currently, the MAC-address is retrieved from eth1, which does not exist on the Archer C7 v4. As a result from this, every C7 v4 with LEDE carries the same MAC-Address on the 5GHz WiFi. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: fix lenovo newifi-y1 switch and LED configChuanhong Guo2018-01-092-3/+5
| | | | | | | | | | | | | | There are 3 ethernet ports on Y1. LAN1 on port1, LAN2 on port0 and WAN on port4. Use a standalone switch configuration to match this and use the switch trigger so that LAN LED could indicate the connetction status for both lan ports correctly. This patch also drop the internet led configuration, because there is a WAN led for port4 and eth0.2 isn't always used as WAN. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: add missing soc compatibles to dtsMathias Kresin2018-01-092-2/+2
| | | | | | Add SoC compatibles where missing. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: firewrt: indicate boot status via LEDMathias Kresin2018-01-091-0/+1
| | | | | | | Add the Firefly FireWRT gree power LED to diag.sh to indicate the boot status via the power LED. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: remove obsolete '< KERNEL_VERSION(4, 4, 0)' checkGabor Juhos2018-01-091-5/+0
| | | | | | | | | Because the oldest supported kernel version on the ar71xx target is 4.4, the condition that the kernel version is smaller than 4.4.0 is always false. Remove the obsolete check from mach-rb4xx.c to clean up the code a bit. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* ar71xx: remove obsolete '< KERNEL_VERSION(4, 2, 0)' checkGabor Juhos2018-01-091-7/+0
| | | | | | | | | Because the oldest supported kernel version on the ar71xx target is 4.4, the condition that the kernel version is smaller than 4.2.0 is always false. Remove the obsolete check from ag71xx_main.c to clean up the code a bit. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* ar71xx: remove obsolete '< KERNEL_VERSION(3, 15, 0)' checksGabor Juhos2018-01-092-17/+0
| | | | | | | | | Because the oldest supported kernel version on the ar71xx target is 4.4, the condition that the kernel version is smaller than 3.15.0 is always false. Remove the obsolete checks from the target specific source files to clean up the code a bit. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* armvirt: bump to v4.14John Crispin2018-01-092-1/+253
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* malta: bump tp v4.14John Crispin2018-01-092-1/+310
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* malta: fix image prefix namesJohn Crispin2018-01-091-4/+4
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx/mikrotik: disable TP-Link TL-WR810N v2 board supportGabor Juhos2018-01-091-0/+1
| | | | | | It does not belongs to the MikroTik boards. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* ar71xx/mikrotik: disable unused MTD partitioning and split driversGabor Juhos2018-01-091-0/+6
| | | | | | Reduces the compressed kernel size by ~2.5KB. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* ar71xx/mikrotik: disable unused ethernet switch and phy driversGabor Juhos2018-01-091-0/+4
| | | | | | | | | | | | | | | | | | | | Disable the drivers for the following ethernet switches: Realtek RTL8306 Realtek RTL8366/8367 Marvell 88E6060 (DSA) Marvell 88E6063 (DSA) Also disable the phy driver for Marvell PHYs. None of the supported RouterBOARDs are using any device which needs these drivers. Disable the DSA framework too, because it is not required by the remaining switch drivers. This reduces the compressed kernel size by ~20KB. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* ar71xx: fix Kconfig dependency of the 88E6063 switch DSA driverGabor Juhos2018-01-092-2/+4
| | | | | | | | | | | | The Marvell 88E6063 ethernet switch driver depends on the DSA framework. Add a 'depends on NET_DSA' statement to its Kconfig entry to state that explicitly. Fixes the following Kconfig warning: warning: (NET_DSA_MV88E6060 && NET_DSA_MV88E6063) selects NET_DSA_TAG_TRAILER which has unmet direct dependencies (NET && NET_DSA) Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* ar71xx: sort kernel configurationsGabor Juhos2018-01-094-6/+6
| | | | | | | The symbols in some kernel configurations of the target are in wrong order. Sort them with kconfig.pl. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* octeon: add support for kernel 4.14Stijn Tintel2018-01-085-0/+465
| | | | | | Tested on EdgeRouter Lite. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ar71xx: fix compiler warnings in mdio-bitbang.c for 4.4Gabor Juhos2018-01-072-3/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Building Linux 4.4 for ar71xx throws the following warnings in drivers/net/phy/mdio-bitbang.c: CC drivers/net/phy/mdio-bitbang.o In file included from include/linux/irqflags.h:14:0, from drivers/net/phy/mdio-bitbang.c:20: drivers/net/phy/mdio-bitbang.c: In function 'mdiobb_read': include/linux/typecheck.h:11:18: warning: comparison of distinct pointer types lacks a cast (void)(&__dummy == &__dummy2); \ ^ include/linux/irqflags.h:63:3: note: in expansion of macro 'typecheck' typecheck(unsigned long, flags); \ ^ include/linux/irqflags.h:124:3: note: in expansion of macro 'raw_local_irq_save' raw_local_irq_save(flags); \ ^ drivers/net/phy/mdio-bitbang.c:162:2: note: in expansion of macro 'local_irq_save' local_irq_save(flags); ^ include/linux/typecheck.h:11:18: warning: comparison of distinct pointer types lacks a cast (void)(&__dummy == &__dummy2); \ ^ include/linux/irqflags.h:68:3: note: in expansion of macro 'typecheck' typecheck(unsigned long, flags); \ ^ include/linux/irqflags.h:126:39: note: in expansion of macro 'raw_local_irq_restore' #define local_irq_restore(flags) do { raw_local_irq_restore(flags); } while (0) ^ drivers/net/phy/mdio-bitbang.c:175:2: note: in expansion of macro 'local_irq_restore' local_irq_restore(flags); ^ drivers/net/phy/mdio-bitbang.c:159:11: warning: unused variable 'i' [-Wunused-variable] int ret, i; ^ In file included from include/linux/irqflags.h:14:0, from drivers/net/phy/mdio-bitbang.c:20: drivers/net/phy/mdio-bitbang.c: In function 'mdiobb_write': include/linux/typecheck.h:11:18: warning: comparison of distinct pointer types lacks a cast (void)(&__dummy == &__dummy2); \ ^ include/linux/irqflags.h:63:3: note: in expansion of macro 'typecheck' typecheck(unsigned long, flags); \ ^ include/linux/irqflags.h:124:3: note: in expansion of macro 'raw_local_irq_save' raw_local_irq_save(flags); \ ^ drivers/net/phy/mdio-bitbang.c:185:2: note: in expansion of macro 'local_irq_save' local_irq_save(flags); ^ include/linux/typecheck.h:11:18: warning: comparison of distinct pointer types lacks a cast (void)(&__dummy == &__dummy2); \ ^ include/linux/irqflags.h:68:3: note: in expansion of macro 'typecheck' typecheck(unsigned long, flags); \ ^ include/linux/irqflags.h:126:39: note: in expansion of macro 'raw_local_irq_restore' #define local_irq_restore(flags) do { raw_local_irq_restore(flags); } while (0) ^ drivers/net/phy/mdio-bitbang.c:200:2: note: in expansion of macro 'local_irq_restore' local_irq_restore(flags); ^ These are caused by the 900-mdio_bitbang_ignore_ta_value and 901-phy-mdio-bitbang-prevent-rescheduling-during-command patches. The first patch removes some code but it does not remove the variable which is used by the removed code only. The second patch adds local_irq_{save,restore} calls. The type of the argument of these calls must be 'unsigned long', but the patch defines the variable as 'long'. Fix both patches to silence the warnings. Signed-off-by: Gabor Juhos <juhosg@freemail.hu>
* lantiq: fix wbmr-hp-g300h image metadataMathias Kresin2018-01-041-2/+2
| | | | | | | The Annex A and Annex B version are using the same (old) userspace boardname. Update the SUPPORTED_DEVICES to allow an update from lede-17.01. Signed-off-by: Mathias Kresin <dev@kresin.me>
* x86: preinit: use board_name on Sm Super ServersPhilip Prindeville2018-01-041-1/+8
| | | | | | | | | Supermicro puts "Super Server" into their product_name DMI value for a whole slew of products, making this value about as useful as not having been filled in at all. Instead, fall back on the board_name instead. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* x86: preinit: make name rewrite into reusable functionPhilip Prindeville2018-01-041-6/+10
| | | | | | | | There might be other places (such as vendor-supplied preinit scripts) where we wish to take a DMI name and clean it up in a consistent way, so make the sed command into a function. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* kernel: bump 4.14 to 4.14.11Stijn Tintel2018-01-0314-41/+42
| | | | | | | | | | | | | | | Rename unwinder config symbols to match upstream changes. Refresh patches. Update patch that no longer applies: 202-reduce_module_size.patch Also enable CONFIG_PAGE_TABLE_ISOLATION. This feature was backported from 4.15 to the 4.14 stable series. It is enabled by default, so enable it in OpenWrt as well. Compile-tested on x86/64. Runtime-tested on x86/64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: move CONFIG_KASAN to generic configStijn Tintel2018-01-027-4/+3
| | | | | | | | | | While bumping 4.14, the kernel build failed due to missing CONFIG_KASAN symbol. Move it to generic config instead of defining it for all arm64 and x86/64 targets. It was only added in 4.0, so not needed in config-3.18. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* layerscape: activate fpu featureHauke Mehrtens2018-01-021-1/+1
| | | | | | | | The CPU sub type was set to a CPU version with FPU, but the FPU feature was not activated before, so a soft float toolchain was created. Activate also the FPU feature to create the correct toolchain. 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>
* kernel: bump 4.9 to 4.9.73Kevin Darbyshire-Bryant2018-01-0212-69/+80
| | | | | | | | Refresh patches. Runtime tested: ar71xx - Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* bcm53xx: use iflag=skip_bytes for dd command during sysupgradeRafał Miłecki2017-12-291-2/+2
| | | | | | | | | | | Since BusyBox 1.25.0 dd command supports iflag=skip_bytes which allows skipping requested amount of bytes without reducing blocksize. Thanks to this we can leave default blocksize and let dd work more efficiently. On Netgear R6250 "dd skip=58 iflag=skip_bytes" can be 5 times faster than "dd bs=58 skip=1" when extracting TRX out of CHK. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* brcm47xx: image: build firmware for Asus WL-500g DeluxeRafał Miłecki2017-12-291-0/+8
| | | | | | | | It's a device based on BCM5365P (0x5365 package 0x00). This SoC has USB 1.1 controller but device has two USB 2.0 parts. They are handled by PCI-based controllers: 1106:3038 UHCI and 1106:3104 EHCI. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add early support for kernel 4.14Rafał Miłecki2017-12-2920-0/+1702
| | | | | | Don't switch to it by default yet as it requires more testing. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: fix Omega2 compatible stringMathias Kresin2017-12-293-1/+3
| | | | | | | Change the compatibel from Omega to Omega2 and add the compatible string where missing. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix widora neo diag ledMathias Kresin2017-12-291-2/+4
| | | | | | | The diag LED is named widora:orange:wifi and can't be derived from the boardname. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix dts compatible stringThomas Nixon2017-12-292-2/+2
| | | | | | | | | | This was broken in 7bab49fd ("lantiq: add compatible strings to dts files"), causing for the dm200 garbled serial output during boot, and likely other issues. Signed-off-by: Thomas Nixon <tom@tomn.co.uk> [fix the compat string of the P2601HNFX as well] Signed-off-by: Mathias Kresin <dev@kresin.me>
* bcm53xx: make USB packages compatible with kernels 4.13+Rafał Miłecki2017-12-291-2/+6
| | | | | | In kernels 4.13+ modules are located in an extra "broadcom" subdir. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: add upstream patch fixing SPI controller driverRafał Miłecki2017-12-294-127/+214
| | | | | | | | | | | | That patch fixes handling SPI messages with two writing transfers. It's important when using e.g. by m25p80 driver which uses one transfer for opcode and another one for data. Thanks to that fix we can now drop m25p80 workaround patch. It means one less hack and also a better flash writing performance as there is no more data buf copying. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-13 14:21:44 +0000