[LEDE-DEV] [PATCH] ar71xx: add ath10k driver and firmware for Netgear R6100 to firmware image
A Netgear R6100 owner reported the LEDE images lack the ath10k driver and firmware [1]. This patch adds both to the R6100 image. [1] https://forum.lede-project.org/t/netgear-r6100-5ghz-wifi-not-working-after-initial-install/ Signed-off-by: Stijn Segers --- target/linux/ar71xx/image/nand.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ar71xx/image/nand.mk b/target/linux/ar71xx/image/nand.mk index 2929662886..ce710a43aa 100644 --- a/target/linux/ar71xx/image/nand.mk +++ b/target/linux/ar71xx/image/nand.mk @@ -68,7 +68,7 @@ TARGET_DEVICES += z1 define LegacyDevice/R6100 DEVICE_TITLE := NETGEAR R6100 - DEVICE_PACKAGES := kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-usb-ledtrig-usbport + DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca988x kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-usb-ledtrig-usbport endef LEGACY_DEVICES += R6100 -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] openwrt and lede - remerge proposal
risons at hand - you get the gist. OpenWrt has served its purpose. It is time to part ways. It looks like some people have resigned to adopting the name again for the greater good, because they want this mess to be over with (understandably). The last vote tally I found [3] was a tie on the most contentious issue - the name. A week ago [4], Hauke states there is a majority in favour of re-adopting the OpenWrt name. I have been looking up and down but seem to have overlooked the final tally - I cannot find it? Can somebody link me? I'm sure a lot of people want this to be fixed, want things to be right again. Most of those have the best interests of the community and both projects in mind, but some do not, and the latter seem to be waging a war of attrition. I enjoy being part of the LEDE community. I never felt OpenWrt was much of a community in the months prior to the fork, and I'd hate to see LEDE go the same way as OpenWrt right before. There will be infighting again, snide remarks, stalled development... And meanwhile, people will say 'hey we need new blood', but that won't come with such a backstabbing culture. My two cents. Cheers Stijn Segers [0] http://lists.infradead.org/pipermail/lede-dev/2017-May/007403.html [1] http://lists.infradead.org/pipermail/lede-dev/2017-May/007342.html [2] http://lists.infradead.org/pipermail/lede-dev/2017-May/007347.html [3] http://lists.infradead.org/pipermail/lede-adm/2017-May/000461.html [4] http://lists.infradead.org/pipermail/lede-adm/2017-May/000462.html [5] http://lists.infradead.org/pipermail/lede-adm/2017-March/000436.html [6] http://lists.infradead.org/pipermail/lede-adm/2017-May/000461.html ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] openwrt and lede - remerge proposal
Of course you only see you numbered your notes the wrong way *after* you send your e-mail... The second [3] and [4] should have been [5] and [6] (see inline). Stijn Segers schreef op 2017-05-11 12:53: Hey guys, This might be a bit lengthy, but I should get this off my chest. I feel people are mostly looking at the upside and glossing over the negatives, which is a time bomb, and both projects do not deserve this. Paul's e-mail [0] already touches a lot of the relevant points, and it motivated me to add my own insights to what so far seems to have been a 'good news show' as we say in Dutch. While, like most people, I'm happy progress has been made towards a re-merge, there still seems quite some passive-agressive behaviour present coming from certain people championing OpenWrt [1] - which, from where I stand, seemed one of the reasons for starting LEDE. Stifling 'free' speech (recently, even to the point of removing messages about the pending re-merge on the OpenWrt forums) was another one; clearly, that one is still very much present as well. One could say old habits die hard, but it still feels like par for the course. What's up with that? You want to remerge with the LEDE project, yet you cannot tolerate any discussion about the actual process on the OpenWrt forums? That's some fine duplicity right there. I can't help but feel very uneasy about this. I'm not implying people who stuck with OpenWrt don't want the best for the project and community (most do), but we all know LEDE was created to remedy exactly these (and other) shortcomings, which made OpenWrt languish to the point it had come to a standstill. Not only did LEDE try to tackle these problems; it has succeeded beyond expectation. Developers are more accessible, you can actually talk to people instead of getting your head bit off, contributions are booming, and the atmosphere overall is friendly and helpful. Discussion is encouraged, not repressed Soviet-style. Some of the OpenWrt veterans come across as if they want the re-merge to be rushed, ignoring the actual issues that caused the fork in the first place. In itself, the desire to re-merge might a noble intent, if it didn't taste so much like driven by ulterior, more selfish motives. At the same time, while OpenWrt have little to offer beyond the OpenWrt name and legacy (which, at this point, feels more and more rotten to me, despite all the good things that once came from it), they field some pretty hard nos - very astonishing, given the position they are in: no to abandoning the OpenWrt name, no to abandoning the OpenWrt 'house style' [1]. Luckily, not everyone shares that same attitude [2], but it leaves a very bad taste. Almost like some people haven't learnt from the whole ordeal, and went back to their old ways pretty quickly. It feels pushy, and seems to boil down to 'it's all fine and dandy what you did, but it's still OpenWrt; don't get any illusions, you're not running the show'. This is very toxic, even more so when you realise that an overwhelming majority of active (!) OpenWrt developers either started or joined the LEDE project. Some of the vocal veterans sticking with OpenWrt hardly contribute any code anymore, and haven't done so in a while, or other valuable input, but they were most vocal when the split happened, pointing fingers and accusing people (ironically, people who *did* contribute code, actively maintained infrastructure, and had the interests of the project and community at heart). Again, they are yelling the hardest now, and waving that OpenWrt flag like there's no tomorrow. Imre nothing short of ignores the whole LEDE effort by stating explicitly that LEDE 17.01 (which Hauke put forward as an official OpenWrt 15.01 successor in an initial communication draft about the merge [3]) was NOT its successor [4]. Combined with his push for the OpenWrt name and keeping pretty much everything else OpenWrt (the dysfunctional homepage, the forums), it reeks of a coverup: LEDE was a hiccup, an anomaly, a gene malfunction, something that needs to be corrected and removed from the 'history books' as soon as possible, so it can all feel hunky dory again - and mostly, so it looks and smells like OpenWrt. By now, that smell has turned into quite a stench though. Luckily, the industry and a lot of end users seem to be impervious to it... For me, the OpenWrt name and project by now feels tainted. For months on end, you could browse the OpenWrt forums, or hang in #openwrt and never catch a dev or someone who knew what was (or wasn't) going on. Backends went down, sites disappeared, and it doesn't help to keep pointing to the OpenWrt name 'because the industry only knows OpenWrt', or 'because end users still don't know about LEDE'. Linux has been around for two decades now, and a lot of people with a computer sti
Re: [LEDE-DEV] [OpenWrt-Devel] openwrt and lede - remerge proposal
Thanks for the reply Imre. Imre Kaloz schreef op 2017-05-11 15:13: Well hello there, On 2017-05-11 12:53, Stijn Segers wrote: While, like most people, I'm happy progress has been made towards a re-merge, there still seems quite some passive-agressive behaviour present coming from certain people championing OpenWrt [1] - which, from where I stand, seemed one of the reasons for starting LEDE. Stifling 'free' speech (recently, even to the point of removing messages about the pending re-merge on the OpenWrt forums) was another one; clearly, that one is still very much present as well. One could say old habits die hard, but it still feels like par for the course. What's up with that? You want to remerge with the LEDE project, yet you cannot tolerate any discussion about the actual process on the OpenWrt forums? That's some fine duplicity right there. I guess our vocabularies differ quite a bit, given I see no passive-aggressive statements there. Well, the 'Our design might be from 2000 but LEDE's is from 95' does come across as agressive, and the wink certainly doesn't make it any lighter. But you're right, I might just be reading into it. Either way, I have seen your mails right after the split as well, granted, your tone is more constructive at the moment, which is great. But those mails were full of anger, like a bull in a china shop, or a kid losing his toy. I hope you just misunderstood the ways some things have been worded, as your mail overemphasized certain parts to twist the picture. I could very well say you're championing yourself but somehow I don't see mails from you sent to any lists nor me about questioning the forum moderators' behavior. Of course you could have also stepped up and volunteer to be one, but either of these would have required more energy then this mail. Don't get me wrong, I'm not questioning if you're right, but you should also be a bit more empathetic and understand a few things. First of all, forum moderator rights have been given out as we didn't have time to do it ourselves. This also means that after the first few days we didn't spend our time on monitoring what people with moderator rights are doing. Understandably. But you also know that if people go berserk, that gives the project as a whole a bad name. It only further deteriorated the atmosphere. Some LEDE members hoped the OpenWrt forum would have been more welcoming to the project in the short term, since LEDE members from the onset made it clear that they did not intend to divide the community; but that didn't work out. But like you say: we're just human after all, and good intentions often aren't enough. Second, and this might be harder to accept, but to a certain degree when the first reply to anything is "OpenWrt is dead, go with LEDE", your behavior might generate a hostile reply. A statement a lot of people certainly fielded, but I'm not one to say that. Yet, you cannot deny between LEDE and OpenWrt, since the split, the latter has been showing a considerably weaker pulse. Again, I'm not saying this is right, I'm saying this is standard human behavior. Back to my reply you love referring to: for me it seems you are the one who can't tolerate the discussion and would like to silence opinions (or how they can be expressed) you don't like. You might prefer baroque, I'm free to like renaissance. Pointing the finger the other way does not invalidate my observations in any way, unfortunately. I can't help but feel very uneasy about this. I'm not implying people who stuck with OpenWrt don't want the best for the project and community (most do), but we all know LEDE was created to remedy exactly these (and other) shortcomings, which made OpenWrt languish to the point it had come to a standstill. Not only did LEDE try to tackle these problems; it has succeeded beyond expectation. Developers are more accessible, you can actually talk to people instead of getting your head bit off, contributions are booming, and the atmosphere overall is friendly and helpful. Discussion is encouraged, not repressed Soviet-style. The reasons of the fork have been discussed quite a few times, and if you think any project will be free of internal politics over a decade, you might want to look into the history of FOSS projects in general :) I might be a bit naive, indeed :). As the rest of your mail is mostly FUD, No doubt, just like the lethargy was all make believe, right? Two mails in, but it won't be long before we get into a Godwin here, I reckon. let's stick to facts if you consider replying. I asked about the facts - the final tally on the most contentious issue - and I'm not finding that fact. We both know that was the major issue at hand, one of the few non-negotiable items for you (and
Re: [LEDE-DEV] openwrt and lede - remerge proposal
Davig Lang wrote: The (soon to be former) LEDE developers don't want @openwrt.org addresses, so providing a way to not break the existing addresses and not giving out new ones doesn't seem like it is upsetting to any of the developers. Let's not get ahead of ourselves. The thread title states 'proposal', and as far as I understand it, it's a 'package deal' that still has to be voted on. There is 'some are more equal than others' and there is not breaking existing communications channels. The aftermath of the split showed there's good reason for disabling them altogether: people using their @openwrt e-mail addresses to claim legitimacy and authority while being barely visible in the day-to-day dealings of the project. You can never eliminate @openwrt.org addresses from all the documentation on the Internet, or from everyone's address books, so it makes sense to have the existing addresses keep working. Indeed you cannot, but you could obsolete existing addresses perfectly fine, and just have them forward e-mail to one general contact address. Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] kernel: update 17.01 kernel 4.4 to 4.4.68
Bump the 17.01 tree kernel to 4.4.68. Trunk 4.4 and 17.01 4.4 have diverged, talked this through with jow, he was okay with a clean diff against 17.01 and not a backported trunk patch. The following patches were applied upstream: 062-[1-6]-MIPS-* series 042-0004-mtd-bcm47xxpart-fix-parsing-first-block Reintroduced lantiq/patches-4.4/0050-MIPS-Lantiq-Fix-cascaded-IRQ-setup, as it was incorrectly included upstream thus dropped from LEDE, but subsequently reverted upstream. Compile-tested on: ar71xx, ramips/mt7621, x86/64. Run-tested on: ar71xx, ramips/mt7621. Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 +- .../patches-4.4/910-unaligned_access_hacks.patch | 4 +- .../patches-4.4/0029-Add-dwc_otg-driver.patch | 2 +- ...le-CONFIG_MEMCG-but-leave-it-disabled-due.patch | 4 +- ...Restore-IO-APIC-irq_chip-retrigger-callba.patch | 46 .../brcm63xx/patches-4.4/577-board_VH4032N.patch | 6 +- ...m47xxpart-don-t-fail-because-of-bit-flips.patch | 4 +- ...part-fix-parsing-first-block-after-aligne.patch | 40 --- .../062-01-MIPS-Introduce-irq_stack.patch | 70 - ...2-MIPS-Stack-unwinding-while-on-IRQ-stack.patch | 42 ...hange-28-to-thread_info-if-coming-from-us.patch | 48 - ...IPS-Switch-to-the-irq_stack-in-interrupts.patch | 116 - ...05-MIPS-Select-HAVE_IRQ_EXIT_ON_IRQ_STACK.patch | 21 ...ack-Fix-erroneous-jal-to-plat_irq_dispatc.patch | 35 --- .../patches-4.4/630-packet_socket_type.patch | 4 +- .../666-Add-support-for-MAP-E-FMRs-mesh-mode.patch | 22 ++-- ...jecting-with-source-address-failed-policy.patch | 22 ++-- ...dwc3-Validate-the-maximum_speed-parameter.patch | 2 +- .../096-08-usb-dwc3-remove-num_event_buffers.patch | 12 +-- .../096-09-usb-dwc3-drop-ev_buffs-array.patch | 4 +- ...b-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch | 2 +- .../linux/lantiq/patches-4.4/0047-irq-fixes.patch | 4 +- .../0050-MIPS-Lantiq-Fix-cascaded-IRQ-setup.patch | 87 ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 4 +- ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 4 +- .../100-clk-sunxi-add-dram-gates-support.patch | 2 +- .../107-clk-sunxi-add-h3-usbphy-clocks.patch | 2 +- .../110-clk-sunxi-add-ve-for-sun457i.patch | 4 +- 28 files changed, 143 insertions(+), 474 deletions(-) delete mode 100644 target/linux/brcm2708/patches-4.4/0577-x86-ioapic-Restore-IO-APIC-irq_chip-retrigger-callba.patch delete mode 100644 target/linux/generic/patches-4.4/042-0004-mtd-bcm47xxpart-fix-parsing-first-block-after-aligne.patch delete mode 100644 target/linux/generic/patches-4.4/062-01-MIPS-Introduce-irq_stack.patch delete mode 100644 target/linux/generic/patches-4.4/062-02-MIPS-Stack-unwinding-while-on-IRQ-stack.patch delete mode 100644 target/linux/generic/patches-4.4/062-03-MIPS-Only-change-28-to-thread_info-if-coming-from-us.patch delete mode 100644 target/linux/generic/patches-4.4/062-04-MIPS-Switch-to-the-irq_stack-in-interrupts.patch delete mode 100644 target/linux/generic/patches-4.4/062-05-MIPS-Select-HAVE_IRQ_EXIT_ON_IRQ_STACK.patch delete mode 100644 target/linux/generic/patches-4.4/062-06-MIPS-IRQ-Stack-Fix-erroneous-jal-to-plat_irq_dispatc.patch create mode 100644 target/linux/lantiq/patches-4.4/0050-MIPS-Lantiq-Fix-cascaded-IRQ-setup.patch diff --git a/include/kernel-version.mk b/include/kernel-version.mk index b56bb237d9..9f30cf2088 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -3,10 +3,10 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .43 -LINUX_VERSION-4.4 = .61 +LINUX_VERSION-4.4 = .68 LINUX_KERNEL_HASH-3.18.43 = 1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c -LINUX_KERNEL_HASH-4.4.61 = 30dee7164615ad8184eba4ea6f4906b3ceb2fe462a8a4a929c8e9aab8d4a31da +LINUX_KERNEL_HASH-4.4.68 = 3231c1822ed552877d12c96ba32944ddc017d346fab9c6dd4f31c3e9f026bdbf ifdef KERNEL_PATCHVER LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER))) diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch index e7df08b0d2..7e3ba4c8d5 100644 --- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch +++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch @@ -310,7 +310,7 @@ if (t->parms.flags & IP6_TNL_F_USE_ORIG_FWMARK) --- a/net/ipv6/ip6_tunnel.c +++ b/net/ipv6/ip6_tunnel.c -@@ -1407,7 +1407,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str +@@ -1409,7 +1409,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str dsfield = ipv6_get_dsfield(ipv6h); if (t->parms.flags & IP6_TNL_F_USE_ORIG_TCLASS) @@ -621,7 +621,7 @@ * XXX skbs on the gro_list have all been parsed and pulled --- a/include/net/addrconf.h +++ b/include/net/addrconf.h -@@ -43,7 +
[LEDE-DEV] [PATCH] kernel: update kernel 4.4 to 4.4.69
Bump the 17.01 tree kernel to 4.4.69. Trunk 4.4 and 17.01 4.4 have diverged, talked this through with jow, he was okay with a clean diff against 17.01 and not a backported trunk patch. The following patches were applied upstream: * 062-[1-6]-MIPS-* series * 042-0004-mtd-bcm47xxpart-fix-parsing-first-block Reintroduced lantiq/patches-4.4/0050-MIPS-Lantiq-Fix-cascaded-IRQ-setup, as it was incorrectly included upstream thus dropped from LEDE, but subsequently reverted upstream. Thanks to Kevin Darbyshire-Bryant for pointing me to it. Compile-tested on: ar71xx, ramips/mt7621, x86/64. Run-tested on: ar71xx, ramips/mt7621, x86/64. Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 +- .../patches-4.4/910-unaligned_access_hacks.patch | 4 +- .../patches-4.4/0029-Add-dwc_otg-driver.patch | 2 +- ...le-CONFIG_MEMCG-but-leave-it-disabled-due.patch | 4 +- ...Restore-IO-APIC-irq_chip-retrigger-callba.patch | 46 .../brcm63xx/patches-4.4/577-board_VH4032N.patch | 6 +- ...m47xxpart-don-t-fail-because-of-bit-flips.patch | 4 +- ...part-fix-parsing-first-block-after-aligne.patch | 40 --- .../062-01-MIPS-Introduce-irq_stack.patch | 70 - ...2-MIPS-Stack-unwinding-while-on-IRQ-stack.patch | 42 ...hange-28-to-thread_info-if-coming-from-us.patch | 48 - ...IPS-Switch-to-the-irq_stack-in-interrupts.patch | 116 - ...05-MIPS-Select-HAVE_IRQ_EXIT_ON_IRQ_STACK.patch | 21 ...ack-Fix-erroneous-jal-to-plat_irq_dispatc.patch | 35 --- .../patches-4.4/630-packet_socket_type.patch | 4 +- .../666-Add-support-for-MAP-E-FMRs-mesh-mode.patch | 22 ++-- ...jecting-with-source-address-failed-policy.patch | 22 ++-- ...dwc3-Validate-the-maximum_speed-parameter.patch | 2 +- .../096-08-usb-dwc3-remove-num_event_buffers.patch | 12 +-- .../096-09-usb-dwc3-drop-ev_buffs-array.patch | 4 +- ...b-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch | 2 +- .../linux/lantiq/patches-4.4/0047-irq-fixes.patch | 4 +- .../0050-MIPS-Lantiq-Fix-cascaded-IRQ-setup.patch | 87 ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 4 +- ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 4 +- .../100-clk-sunxi-add-dram-gates-support.patch | 2 +- .../107-clk-sunxi-add-h3-usbphy-clocks.patch | 2 +- .../110-clk-sunxi-add-ve-for-sun457i.patch | 4 +- 28 files changed, 143 insertions(+), 474 deletions(-) delete mode 100644 target/linux/brcm2708/patches-4.4/0577-x86-ioapic-Restore-IO-APIC-irq_chip-retrigger-callba.patch delete mode 100644 target/linux/generic/patches-4.4/042-0004-mtd-bcm47xxpart-fix-parsing-first-block-after-aligne.patch delete mode 100644 target/linux/generic/patches-4.4/062-01-MIPS-Introduce-irq_stack.patch delete mode 100644 target/linux/generic/patches-4.4/062-02-MIPS-Stack-unwinding-while-on-IRQ-stack.patch delete mode 100644 target/linux/generic/patches-4.4/062-03-MIPS-Only-change-28-to-thread_info-if-coming-from-us.patch delete mode 100644 target/linux/generic/patches-4.4/062-04-MIPS-Switch-to-the-irq_stack-in-interrupts.patch delete mode 100644 target/linux/generic/patches-4.4/062-05-MIPS-Select-HAVE_IRQ_EXIT_ON_IRQ_STACK.patch delete mode 100644 target/linux/generic/patches-4.4/062-06-MIPS-IRQ-Stack-Fix-erroneous-jal-to-plat_irq_dispatc.patch create mode 100644 target/linux/lantiq/patches-4.4/0050-MIPS-Lantiq-Fix-cascaded-IRQ-setup.patch diff --git a/include/kernel-version.mk b/include/kernel-version.mk index b56bb237d9..9660969877 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -3,10 +3,10 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .43 -LINUX_VERSION-4.4 = .61 +LINUX_VERSION-4.4 = .69 LINUX_KERNEL_HASH-3.18.43 = 1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c -LINUX_KERNEL_HASH-4.4.61 = 30dee7164615ad8184eba4ea6f4906b3ceb2fe462a8a4a929c8e9aab8d4a31da +LINUX_KERNEL_HASH-4.4.69 = 207bbc50aaf827d667a2762312bd6127887cc669ff7a7270b876e7102b8f84fa ifdef KERNEL_PATCHVER LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER))) diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch index e7df08b0d2..7e3ba4c8d5 100644 --- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch +++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch @@ -310,7 +310,7 @@ if (t->parms.flags & IP6_TNL_F_USE_ORIG_FWMARK) --- a/net/ipv6/ip6_tunnel.c +++ b/net/ipv6/ip6_tunnel.c -@@ -1407,7 +1407,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str +@@ -1409,7 +1409,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str dsfield = ipv6_get_dsfield(ipv6h); if (t->parms.flags & IP6_TNL_F_USE_ORIG_TCLASS) @@ -621,7 +621,7 @@ * XXX skbs on the gro_list have all been parsed and pulled ---
Re: [LEDE-DEV] [PATCH] kernel: bump 4.4 to 4.4.102
Refreshed all patches. Removed upstream ramips patch: 0063-set-CM_GCR_BASE_CMDEFTGT_MEM-according-to-datasheet.patch Compile-tested: ar71xx, ramips, x86 Run-tested: ar71xx, ramips/mt7621, x86/64 (Ramips and x86 have been tested on 17.01 but I suppose that does not really matter.) Tested-by: Stijn Segers francesco.borromini at inventati.org Signed-off-by: Etienne Haarsma bladeoner112 at gmail.com ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] Curl: apply CVE 2017-8816 and 2017-8817 security patches
This commit adds the upstream patches for CVE 2017-8816 and 2017-8817 to the
17.01
cURL package.
Compile-tested on ar71xx, ramips and x86.
Signed-off-by: Stijn Segers
---
package/network/utils/curl/Makefile| 2 +-
.../utils/curl/patches/105-CVE-2017-8816.patch | 67 ++
.../utils/curl/patches/106-CVE-2017-8817.patch | 141 +
3 files changed, 209 insertions(+), 1 deletion(-)
create mode 100644 package/network/utils/curl/patches/105-CVE-2017-8816.patch
create mode 100644 package/network/utils/curl/patches/106-CVE-2017-8817.patch
diff --git a/package/network/utils/curl/Makefile
b/package/network/utils/curl/Makefile
index 758532e30a..5d829547aa 100644
--- a/package/network/utils/curl/Makefile
+++ b/package/network/utils/curl/Makefile
@@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
PKG_NAME:=curl
PKG_VERSION:=7.52.1
-PKG_RELEASE:=5
+PKG_RELEASE:=6
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.bz2
PKG_SOURCE_URL:=http://curl.haxx.se/download/ \
diff --git a/package/network/utils/curl/patches/105-CVE-2017-8816.patch
b/package/network/utils/curl/patches/105-CVE-2017-8816.patch
new file mode 100644
index 00..4d2b3162a8
--- /dev/null
+++ b/package/network/utils/curl/patches/105-CVE-2017-8816.patch
@@ -0,0 +1,67 @@
+From 7947c50bcd09cf471c95511739bc66d2cb506ee2 Mon Sep 17 00:00:00 2001
+From: Daniel Stenberg
+Date: Mon, 6 Nov 2017 23:51:52 +0100
+Subject: [PATCH] ntlm: avoid integer overflow for malloc size
+
+Reported-by: Alex Nichols
+Assisted-by: Kamil Dudka and Max Dymond
+
+CVE-2017-8816
+
+Bug: https://curl.haxx.se/docs/adv_2017-11e7.html
+---
+ lib/curl_ntlm_core.c | 23 +--
+ 1 file changed, 21 insertions(+), 2 deletions(-)
+
+diff --git a/lib/curl_ntlm_core.c b/lib/curl_ntlm_core.c
+index 1309bf0d9..e8962769c 100644
+--- a/lib/curl_ntlm_core.c
b/lib/curl_ntlm_core.c
+@@ -616,23 +616,42 @@ CURLcode Curl_hmac_md5(const unsigned char *key,
unsigned int keylen,
+ Curl_HMAC_final(ctxt, output);
+
+ return CURLE_OK;
+ }
+
++#ifndef SIZE_T_MAX
++/* some limits.h headers have this defined, some don't */
++#if defined(_LP64) || defined(_I32LPx)
++#define SIZE_T_MAX 18446744073709551615U
++#else
++#define SIZE_T_MAX 4294967295U
++#endif
++#endif
++
+ /* This creates the NTLMv2 hash by using NTLM hash as the key and Unicode
+ * (uppercase UserName + Domain) as the data
+ */
+ CURLcode Curl_ntlm_core_mk_ntlmv2_hash(const char *user, size_t userlen,
+const char *domain, size_t domlen,
+unsigned char *ntlmhash,
+unsigned char *ntlmv2hash)
+ {
+ /* Unicode representation */
+- size_t identity_len = (userlen + domlen) * 2;
+- unsigned char *identity = malloc(identity_len);
++ size_t identity_len;
++ unsigned char *identity;
+ CURLcode result = CURLE_OK;
+
++ /* we do the length checks below separately to avoid integer overflow risk
++ on extreme data lengths */
++ if((userlen > SIZE_T_MAX/2) ||
++ (domlen > SIZE_T_MAX/2) ||
++ ((userlen + domlen) > SIZE_T_MAX/2))
++return CURLE_OUT_OF_MEMORY;
++
++ identity_len = (userlen + domlen) * 2;
++ identity = malloc(identity_len);
++
+ if(!identity)
+ return CURLE_OUT_OF_MEMORY;
+
+ ascii_uppercase_to_unicode_le(identity, user, userlen);
+ ascii_to_unicode_le(identity + (userlen << 1), domain, domlen);
+--
+2.15.0
+
diff --git a/package/network/utils/curl/patches/106-CVE-2017-8817.patch
b/package/network/utils/curl/patches/106-CVE-2017-8817.patch
new file mode 100644
index 00..e5ce0fed23
--- /dev/null
+++ b/package/network/utils/curl/patches/106-CVE-2017-8817.patch
@@ -0,0 +1,141 @@
+From 0acc0c7c120afa6d60bfc7932c04361720b6e74d Mon Sep 17 00:00:00 2001
+From: Daniel Stenberg
+Date: Fri, 10 Nov 2017 08:52:45 +0100
+Subject: [PATCH] wildcardmatch: fix heap buffer overflow in setcharset
+
+The code would previous read beyond the end of the pattern string if the
+match pattern ends with an open bracket when the default pattern
+matching function is used.
+
+Detected by OSS-Fuzz:
+https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4161
+
+CVE-2017-8817
+
+Bug: https://curl.haxx.se/docs/adv_2017-ae72.html
+---
+ lib/curl_fnmatch.c | 9 +++--
+ tests/data/Makefile.inc | 2 +-
+ tests/data/test1163 | 52 +
+ 3 files changed, 56 insertions(+), 7 deletions(-)
+ create mode 100644 tests/data/test1163
+
+diff --git a/lib/curl_fnmatch.c b/lib/curl_fnmatch.c
+index da83393b4..8a1e106c4 100644
+--- a/lib/curl_fnmatch.c
b/lib/curl_fnmatch.c
+@@ -131,10 +131,13 @@ static int setcharset(unsigned char **p, unsigned char
*charset)
+ unsigned char lastchar = 0;
+ bool something_found = FALSE;
+ unsigned char c;
+ for(;;) {
+ c = **p;
++if(!c)
++ return SETCHARSET_FAIL;
++
+ switch(state) {
+ case CURLFNM_SCHS
Re: [LEDE-DEV] [PATCH] kernel: bump 4.4 to 4.4.107 for 17.01
Compile-tested on: ar71xx, ramips/mt7621, x86/64. Run-tested on: ramips/mt7621. Tested-by: Stijn Segers ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v1] kernel: bump 4.4 to 4.4.108 for 17.01
Refresh patches.
[Compile-tested on ar71xx, ramips/mt7621 and x86/64. Run-tested on
ramips/mt7621 by Stijn Segers]
Signed-off-by: Kevin Darbyshire-Bryant
Tested-by: Stijn Segers
---
include/kernel-version.mk
| 4 ++--
target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
| 2 +-
.../204-net-igb-register-mii_bus-for-SerDes-w-external-phy.patch
| 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 1e699a4e4b..fc7f46f6e2 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,10 +3,10 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .107
+LINUX_VERSION-4.4 = .108
LINUX_KERNEL_HASH-3.18.43 =
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.107 =
d25dc23c8b05d34518ede68f03668cd344f805049a16bc4f189da90533881a17
+LINUX_KERNEL_HASH-4.4.108 =
5a001198625ce9f7b0ef1e4b43e033aea859e1ef3509532412cce8f0375ba51a
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip
$(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git
a/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
b/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
index cc19b8ef33..5f46885708 100644
--- a/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
+++ b/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
@@ -1,6 +1,6 @@
--- a/net/netlink/af_netlink.c
+++ b/net/netlink/af_netlink.c
-@@ -1187,24 +1187,7 @@ void netlink_detachskb(struct sock *sk,
+@@ -1228,24 +1228,7 @@ void netlink_detachskb(struct sock *sk,
static struct sk_buff *netlink_trim(struct sk_buff *skb, gfp_t
allocation)
{
diff --git
a/target/linux/imx6/patches-4.4/204-net-igb-register-mii_bus-for-SerDes-w-external-phy.patch
b/target/linux/imx6/patches-4.4/204-net-igb-register-mii_bus-for-SerDes-w-external-phy.patch
index 1d3dcb29ab..4f99418a01 100644
---
a/target/linux/imx6/patches-4.4/204-net-igb-register-mii_bus-for-SerDes-w-external-phy.patch
+++
b/target/linux/imx6/patches-4.4/204-net-igb-register-mii_bus-for-SerDes-w-external-phy.patch
@@ -246,7 +246,7 @@ Signed-off-by: Tim Harvey
#ifdef CONFIG_IGB_HWMON
igb_sysfs_exit(adapter);
#endif
-@@ -3111,6 +3243,12 @@ static int __igb_open(struct net_device
+@@ -3113,6 +3245,12 @@ static int __igb_open(struct net_device
if (!resuming)
pm_runtime_put(&pdev->dev);
@@ -259,7 +259,7 @@ Signed-off-by: Tim Harvey
/* start the watchdog. */
hw->mac.get_link_status = 1;
schedule_work(&adapter->watchdog_task);
-@@ -7104,21 +7242,41 @@ void igb_alloc_rx_buffers(struct igb_rin
+@@ -7106,21 +7244,41 @@ void igb_alloc_rx_buffers(struct igb_rin
static int igb_mii_ioctl(struct net_device *netdev, struct ifreq
*ifr, int cmd)
{
struct igb_adapter *adapter = netdev_priv(netdev);
--
2.14.3 (Apple Git-98)
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v1] kernel: bump 4.4 to 4.4.109 for 17.01
Hi Kevin, FYI - I am getting these messages when applying: $ git am ../patches/main/0001-kernel-update-17.01-kernel-4.4-to-4.4.109.patch Applying: kernel: bump 4.4 to 4.4.109 for 17.01 .git/rebase-apply/patch:86: space before tab in indent. xhci->quirks |= XHCI_TRUST_TX_LENGTH; .git/rebase-apply/patch:967: space before tab in indent. val &= ~MVNETA_GMAC0_PORT_ENABLE; .git/rebase-apply/patch:968: space before tab in indent. mvreg_write(pp, MVNETA_GMAC_CTRL_0, val); .git/rebase-apply/patch:969: trailing whitespace. .git/rebase-apply/patch:974: space before tab in indent. udelay(200); warning: squelched 1 whitespace error warning: 6 lines add whitespace errors. Besides that - running builds as we speak :-). Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v1] kernel: bump 4.4 to 4.4.109 for 17.01
Refresh patches. Run-tested: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant Tested-by: Stijn Segers ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v1] kernel: bump 4.9 to 4.9.75
Alberto, Despite the disinformation Intel initially spread, it looks like AMD processors are not vulnerable to Meltdown (which these patches should address). Spectre is a different thing altogether, and affects AMD and Intel as well, but these are other CVEs. Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Switches between LTS kernels and removal of previous LTSes
Sorry, now the non-HTML version... Hi guys, I remember there was quite a bit of gnashing of teeth, when targets in master dropped 4.4 support so quickly after 17.01 had been released (which made it very cumbersome to backport 4.4 kernel bumps from master to the stable branch). Wouldn't it be wiser to keep 4.9 kernels around for targets that are being bumped to 4.14? Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v1] kernel: bump 4.4 to 4.4.111 for 17.01
Compile-tested on ar71xx, ramips/mt7621 and x86/64. Run-tested on ar71xx, ramips/mt7621. Tested-by: Stijn Segers ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] ar71xx: Netgear WNR200v4: do not include USB packages [17.01]
The Netgear WNR2000v4 does not have a USB port. Hence, including USB packages into the default images is useless. It looks like the WNR2000v4 definition in master is OK. Signed-off-by: Stijn Segers --- target/linux/ar71xx/image/legacy-devices.mk | 1 - 1 file changed, 1 deletion(-) diff --git a/target/linux/ar71xx/image/legacy-devices.mk b/target/linux/ar71xx/image/legacy-devices.mk index 87423ce55c..6667bef97e 100644 --- a/target/linux/ar71xx/image/legacy-devices.mk +++ b/target/linux/ar71xx/image/legacy-devices.mk @@ -440,7 +440,6 @@ LEGACY_DEVICES += WNR2000V3 define LegacyDevice/WNR2000V4 DEVICE_TITLE := NETGEAR WNR2000V4 - DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport endef LEGACY_DEVICES += WNR2000V4 -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH v2] ar71xx: Netgear WNR2000v4: do not include USB packages [17.01]
The Netgear WNR2000v4 does not have a USB port. Hence, including USB packages into the default images is useless. It looks like the WNR2000v4 definition in master is OK. v2 fixes the silly typo in the patch title (WNR2000v4 instead of WNR200v4) Signed-off-by: Stijn Segers --- target/linux/ar71xx/image/legacy-devices.mk | 1 - 1 file changed, 1 deletion(-) diff --git a/target/linux/ar71xx/image/legacy-devices.mk b/target/linux/ar71xx/image/legacy-devices.mk index 87423ce55c..6667bef97e 100644 --- a/target/linux/ar71xx/image/legacy-devices.mk +++ b/target/linux/ar71xx/image/legacy-devices.mk @@ -440,7 +440,6 @@ LEGACY_DEVICES += WNR2000V3 define LegacyDevice/WNR2000V4 DEVICE_TITLE := NETGEAR WNR2000V4 - DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport endef LEGACY_DEVICES += WNR2000V4 -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH 2/5] firmware: add microcode package for AMD64
Hi Zoltan, I told you on IRC I'd check on an APU2, but that's in production on a remote site so if it goes belly up people won't be happy. So when you mentioned Ryzen on the mailing list here I figured I could as well do it on my desktop ;-). Dmesg excerpts below. I added the 17h microcode file to /lib/firmware/amd-ucode/ manually, but it looks like it works. Tested with master and kernel 4.4.112 (courtesy of Kevin's patch). [ 0.408053] smpboot: CPU0: AMD Ryzen 7 1800X Eight-Core Processor (family: 0x17, model: 0x1, stepping: 0x1) [ 0.418276] Performance Events: Fam17h core perfctr, AMD PMU driver. [snip] [ 2.281229] microcode: CPU0: patch_level=0x08001129 [ 2.281238] microcode: CPU1: patch_level=0x08001129 [ 2.281246] microcode: CPU2: patch_level=0x08001129 [ 2.284714] microcode: CPU3: patch_level=0x08001129 [ 2.284853] microcode: CPU4: patch_level=0x08001129 [ 2.284860] microcode: CPU5: patch_level=0x08001129 [ 2.284875] microcode: CPU6: patch_level=0x08001129 [ 2.284881] microcode: CPU7: patch_level=0x08001129 [ 2.284891] microcode: Microcode Update Driver: v2.01 , Peter Oruba Hope that helps. Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v1] kernel: bump 4.4 to 4.4.112
Tested-by: Stijn Segers Compile-tested on: x86/64. Run-tested on: x86/64. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v1] kernel: bump 4.4 to 4.4.112 for 17.01
Tested-by: Stijn Segers Compile-tested on: ar71xx, ramips/mt7621, x86/64 Run-tested on: ar71xx, ramips/mt7621, x86/64. ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH 0/5] x86: add support for microcode update
Ironically, 4.4.112 is reporting similar behaviour: # grep . /sys/devices/system/cpu/vulnerabilities/* /sys/devices/system/cpu/vulnerabilities/meltdown:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable /sys/devices/system/cpu/vulnerabilities/spectre_v2:Vulnerable root@PC Engines APU2:~# uname -a Linux PC Engines APU2 4.4.112 #0 SMP Thu Jan 18 18:46:12 2018 x86_64 GNU/Linux That's on 17.01, but it shouldn't matter. Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v2 0/5] mvebu: add kernel 4.14 support
Hi Hannu, See http://lists.infradead.org/pipermail/lede-dev/2018-January/010870.html Apparently supported as from 4.11 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v2 0/5] mvebu: add kernel 4.14 support
Sorry, my fingers might have been quicker than my thoughts. Was the first tthing I thought about, but haven't thoroughly checked the WRT3200ACM issue. Stijn Op zo, 21 jan 2018 om 9:04 , schreef Stijn Segers : Hi Hannu, See http://lists.infradead.org/pipermail/lede-dev/2018-January/010870.html Apparently supported as from 4.11 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v2] kernel: bump 4.4 to 4.4.113 for 17.01
Tested-by: Stijn Segers
Compile and run-tested on ar71xx / ramips/mt7621 / x86/64.
Op za, 27 jan 2018 om 5:05 , schreef Kevin Darbyshire-Bryant
:
Refresh patches.
Refresh x86/config for RETPOLINE.
More Meltdown & Spectre mitigation.
Signed-off-by: Kevin Darbyshire-Bryant
---
v2 - clarify this is for 17.01
include/kernel-version.mk |
4 ++--
...backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch |
2 +-
target/linux/generic/patches-4.4/221-module_exports.patch |
2 +-
target/linux/generic/patches-4.4/834-ledtrig-libata.patch |
8
target/linux/oxnas/patches-4.4/999-libata-hacks.patch |
4 ++--
target/linux/x86/config-4.4 |
4 +++-
6 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 344c33009e..c7b038a8e0 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,10 +3,10 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .112
+LINUX_VERSION-4.4 = .113
LINUX_KERNEL_HASH-3.18.43 =
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.112 =
544b42cbeed022896115c76a18fc97b4507d5b41d7ac0ce1dce9afd6ffd11ecd
+LINUX_KERNEL_HASH-4.4.113 =
b772d2898d2a791b5bf8bd597beccef385934e237f6c6bb1cf4c609940af773d
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip
$(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git
a/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
b/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
index 48714aa466..7cce9bc77f 100644
---
a/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
+++
b/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
@@ -47,7 +47,7 @@ Signed-off-by: Jacek Anaszewski
#include
#include
-@@ -4914,6 +4915,9 @@ void ata_qc_complete(struct ata_queued_c
+@@ -4915,6 +4916,9 @@ void ata_qc_complete(struct ata_queued_c
{
struct ata_port *ap = qc->ap;
diff --git
a/target/linux/generic/patches-4.4/221-module_exports.patch
b/target/linux/generic/patches-4.4/221-module_exports.patch
index 510a86c468..44c0a6dec6 100644
--- a/target/linux/generic/patches-4.4/221-module_exports.patch
+++ b/target/linux/generic/patches-4.4/221-module_exports.patch
@@ -54,7 +54,7 @@
}
--- a/scripts/Makefile.build
+++ b/scripts/Makefile.build
-@@ -299,7 +299,7 @@ targets += $(extra-y) $(MAKECMDGOALS) $(
+@@ -372,7 +372,7 @@ targets += $(extra-y) $(MAKECMDGOALS) $(
# Linker scripts preprocessor (.lds.S -> .lds)
#
---
quiet_cmd_cpp_lds_S = LDS $@
diff --git
a/target/linux/generic/patches-4.4/834-ledtrig-libata.patch
b/target/linux/generic/patches-4.4/834-ledtrig-libata.patch
index c3d187a098..ad63634479 100644
--- a/target/linux/generic/patches-4.4/834-ledtrig-libata.patch
+++ b/target/linux/generic/patches-4.4/834-ledtrig-libata.patch
@@ -69,7 +69,7 @@ Signed-off-by: Daniel Golle
/**
*ata_build_rw_tf - Build ATA taskfile for given read/write request
*@tf: Target ATA taskfile
-@@ -4780,6 +4793,9 @@ struct ata_queued_cmd *ata_qc_new_init(s
+@@ -4781,6 +4794,9 @@ struct ata_queued_cmd *ata_qc_new_init(s
if (tag < 0)
return NULL;
}
@@ -79,7 +79,7 @@ Signed-off-by: Daniel Golle
qc = __ata_qc_from_tag(ap, tag);
qc->tag = tag;
-@@ -5677,6 +5693,9 @@ struct ata_port *ata_port_alloc(struct a
+@@ -5678,6 +5694,9 @@ struct ata_port *ata_port_alloc(struct a
ap->stats.unhandled_irq = 1;
ap->stats.idle_irq = 1;
#endif
@@ -89,7 +89,7 @@ Signed-off-by: Daniel Golle
ata_sff_port_init(ap);
return ap;
-@@ -5698,6 +5717,12 @@ static void ata_host_release(struct devi
+@@ -5699,6 +5718,12 @@ static void ata_host_release(struct devi
kfree(ap->pmp_link);
kfree(ap->slave_link);
@@ -102,7 +102,7 @@ Signed-off-by: Daniel Golle
kfree(ap);
host->ports[i] = NULL;
}
-@@ -6144,7 +6169,23 @@ int ata_host_register(struct ata_host *h
+@@ -6145,7 +6170,23 @@ int ata_host_register(struct ata_host *h
host->ports[i]->print_id = atomic_inc_return(&ata_print_id);
host->ports[i]->local_port_no = i + 1;
}
diff --git a/target/linux/oxnas/patches-4.4/999-libata-hacks.patch
b/target/linux/oxnas/patches-4.4/999-libata-hacks.patch
index 1f4799dd88..ac278ab234 100644
--- a/target/linux/oxnas/patches-4.4/999-libata-hacks.patch
+++ b/target/linux/oxnas/patches-4.4/999-libata-hacks.patch
@@ -15,7 +15,7 @@
/* initialize internal qc */
/* XXX: T
Re: [LEDE-DEV] [PATCH v1 1/1] openssh: disable passwords for openssh server
Yousong Zhou schreef op 14 februari 2018 09:06:11 CET: >On 14 February 2018 at 11:53, Philip Prindeville > wrote: >> >>> On Feb 11, 2018, at 3:54 AM, Yousong Zhou >wrote: >>> >>> On 9 February 2018 at 08:28, Philip Prindeville >>> wrote: From: Philip Prindeville Allowing password logins leaves you vulnerable to dictionary attacks. We disable password-based authentication, limiting authentication to keys only which are more secure. Note: You'll need to pre-populate your image with some initial keys. To do this: 1. Create the appropriate directory as "mkdir -p files/root/.ssh" from your top-level directory; 2. Copy your "~/.ssh/id_rsa.pub" (or as appropriate) into "files/root/.ssh/authorized_keys" and indeed, you can collect keys from several sources this way by concatenating them; 3. Set the permissions on "authorized_keys" to 644 or 640. >>> >>> If forgetting doing this means I may need physical connection like >vga >>> monitor or serial connection to "unlock" the device, very likely I >>> will hate this security enforcement... It's just the inconvenience >>> regardless of whether the said situation should happen. As a user >I'd >>> like to keep this level of convenience as using password >>> authentication and turn it off when I see it appropriate. >>> >>>yousong >>> >> >> >> Well, we’re at an impasse because some people have said “this should >be the new norm and it’s a mistake not to disable it unconditionally” >and others have said the opposite, “yes, okay, let’s do this but only >as an option”. >> >> So I’m happy to go other way but we should reach a consensus. >> >> What if it *is* an option but depends on a virtual package that takes >a value (like CONFIG_SSH_PUBLIC_KEYS) and squirts that into the >/root/.ssh/authorized_keys file. >> >> Would that work for everyone? >> >> You could still lock yourself out of a box by (a) mis-formatting the >keys or (b) getting the wrong public keys that don’t match your >installed private keys, but getting this to be absolutely foolproof is >a fool's errand. >> >> So what constitutes “good enough”? >> >> -Philip >> > >No, it's just complicating things up. When people really cares about >the default settings' security, the will override the default by also >specifying files/etc/ssh/sshd_config besides >files/root/.ssh/authorized_keys. No need to pass on such complexity >as virtual packages and another config options for others. > >yousong > This only applies to OpenSSH, not Dropbear right? So this won't affect stock images? We should consider people rolling their own and using OpenSSH by default. This might be a nasty surprise - flash, reboot, realise you're locked out. SSH access from WAN is disabled by default anyway, as is access to the web interface. We already switched from telnet to SSH for initial login. I don't see any gaping security holes... On top of that, the project having a DIY spirit, if people start tinkering with SSH, they should know what they're doing. Just like when they start using LEDE/OpenWrt. My 2 cents Stijn >___ >Lede-dev mailing list >Lede-dev@lists.infradead.org >http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] x86/64: enable CONFIG_X86_VSYSCALL_EMULATION in kernel config
CONFIG_X86_VSYSCALL_EMULATION is disabled by default on x86/64, but without it the new KAISER stuff breaks in the way shown below: CC arch/x86/mm/kaiser.o arch/x86/mm/kaiser.c: In function 'kaiser_init': arch/x86/mm/kaiser.c:348:8: error: 'vsyscall_pgprot' undeclared (first use in this function) vsyscall_pgprot); ^ arch/x86/mm/kaiser.c:270:47: note: in definition of macro 'kaiser_add_user_map_early' int __ret = kaiser_add_user_map(start, size, flags); \ ^ arch/x86/mm/kaiser.c:348:8: note: each undeclared identifier is reported only once for each function it appears in vsyscall_pgprot); ^ arch/x86/mm/kaiser.c:270:47: note: in definition of macro 'kaiser_add_user_map_early' int __ret = kaiser_add_user_map(start, size, flags); \ ^ scripts/Makefile.build:269: recipe for target 'arch/x86/mm/kaiser.o' failed Signed-off-by: Stijn Segers --- target/linux/x86/64/config-default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/x86/64/config-default b/target/linux/x86/64/config-default index 7d38df3030..bad7dddbe3 100644 --- a/target/linux/x86/64/config-default +++ b/target/linux/x86/64/config-default @@ -343,7 +343,7 @@ CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_PM_TIMER=y # CONFIG_X86_POWERNOW_K8 is not set CONFIG_X86_TSC=y -# CONFIG_X86_VSYSCALL_EMULATION is not set +CONFIG_X86_VSYSCALL_EMULATION=y CONFIG_X86_X2APIC=y # CONFIG_X86_X32 is not set CONFIG_XEN=y -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] kernel: update 17.01 kernel to 4.4.116
This bumps the 4.4. kernel in LEDE 17.01 to 4.4.116.
More Meltdown & Spectre mitigation.
* Refresh patches.
* Refresh x86/config for RETPOLINE.
* Deleted 8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch
(accepted upstream)
* Deleted 8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch (accepted upstream)
* 650-pppoe_header_pad.patch does not apply anymore (code was replaced).
Bumps from 4.4.113 to 4.4.115 were handled by Kevin Darbyshire-Bryant.
Compile-tested on: ar71xx, ramips/mt7621, x86/64
Run-tested on: ar71xx, ramips/mt7621, x86/64
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
...onvert-IDE-trigger-to-common-disk-trigger.patch | 2 +-
.../004-register_gpio_driver_earlier.patch | 5 +-
.../patches-4.4/910-unaligned_access_hacks.patch | 12 ++--
...d-set-initial-ECC-params-based-on-info-fr.patch | 2 +-
...ify-at-boot-that-CMA-doesn-t-cross-a-256M.patch | 2 +-
.../051-0005-ovl-proper-cleanup-of-workdir.patch | 2 +-
.../generic/patches-4.4/204-module_strip.patch | 12 ++--
.../generic/patches-4.4/221-module_exports.patch | 2 +-
...bi-auto-create-ubiblock-device-for-rootfs.patch | 4 +-
...-set-ROOT_DEV-to-ubiblock-rootfs-if-unset.patch | 4 +-
...610-netfilter_match_bypass_default_checks.patch | 12 ++--
.../generic/patches-4.4/650-pppoe_header_pad.patch | 20 ---
...80-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 ++--
.../generic/patches-4.4/834-ledtrig-libata.patch | 8 +--
.../generic/patches-4.4/902-debloat_proc.patch | 2 +-
.../generic/patches-4.4/995-mangle_bootargs.patch | 2 +-
.../7017-fsl_qbman-add-qbman-driver.patch | 4 +-
...an-Enable-DPAA1-QBMan-for-ARM64-platforms.patch | 2 +-
...f-esdhc-add-remove-some-quirks-according-.patch | 11 +---
...rscape-Add-fsl-ls2085a-pcie-compatible-ID.patch | 25
...0-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch | 66 --
...ers-mmc-Add-compatible-string-for-LS1046A.patch | 2 +-
...mtd-backport-v4.7-0day-patches-from-Boris.patch | 66 +++---
...mtd-backport-v4.7-0day-patches-from-Boris.patch | 66 +++---
...0074-mtd-nand-import-nand_hw_control_init.patch | 6 +-
.../linux/oxnas/patches-4.4/999-libata-hacks.patch | 4 +-
.../0040-nand-add-mtk-nand-hack-hook.patch | 2 +-
.../patches-4.4/0901-spansion_nand_id_fix.patch| 4 +-
target/linux/x86/config-4.4| 4 +-
30 files changed, 126 insertions(+), 241 deletions(-)
delete mode 100644 target/linux/generic/patches-4.4/650-pppoe_header_pad.patch
delete mode 100644
target/linux/layerscape/patches-4.4/8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch
delete mode 100644
target/linux/layerscape/patches-4.4/8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 344c33009e..7fe6e7910b 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,10 +3,10 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .112
+LINUX_VERSION-4.4 = .116
LINUX_KERNEL_HASH-3.18.43 =
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.112 =
544b42cbeed022896115c76a18fc97b4507d5b41d7ac0ce1dce9afd6ffd11ecd
+LINUX_KERNEL_HASH-4.4.116 =
566fea5814627ee65cc1e6b9c4bfe2f7642ac36b6185e2a3dcb9e8ba1e325fa3
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git
a/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
b/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
index 48714aa466..7cce9bc77f 100644
---
a/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
+++
b/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
@@ -47,7 +47,7 @@ Signed-off-by: Jacek Anaszewski
#include
#include
-@@ -4914,6 +4915,9 @@ void ata_qc_complete(struct ata_queued_c
+@@ -4915,6 +4916,9 @@ void ata_qc_complete(struct ata_queued_c
{
struct ata_port *ap = qc->ap;
diff --git
a/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
b/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
index 0c07cb18c7..639e82c245 100644
--- a/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
+++ b/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
@@ -3,7 +3,7 @@ from mach files succeed.
--- a/drivers/gpio/gpio-ath79.c
+++ b/drivers/gpio/gpio-ath79.c
-@@ -202,4 +202,8 @@ static struct platform_driver ath79_gpio
+@@ -202,7 +202,11 @@ static struct platform_driver ath79_gpio
.probe = ath79_gpio_probe,
};
@@ -13,3 +13,6 @@ from mach files succeed.
+ return platform_driver_register(&ath79_gpio_driver);
+}
+postco
[LEDE-DEV] [PATCH] kernel: update 17.01 kernel to 4.4.116
This bumps the 4.4. kernel in LEDE 17.01 to 4.4.116.
More Meltdown & Spectre mitigation.
* Refresh patches.
* Refresh x86/config for RETPOLINE.
* Deleted 8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch
(accepted upstream)
* Deleted 8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch (accepted upstream)
* 650-pppoe_header_pad.patch does not apply anymore (code was replaced).
Bumps from 4.4.113 to 4.4.115 were handled by Kevin Darbyshire-Bryant.
Compile-tested on: ar71xx, ramips/mt7621, x86/64
Run-tested on: ar71xx, ramips/mt7621, x86/64
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
...onvert-IDE-trigger-to-common-disk-trigger.patch | 2 +-
.../004-register_gpio_driver_earlier.patch | 5 +-
.../patches-4.4/910-unaligned_access_hacks.patch | 12 ++--
...d-set-initial-ECC-params-based-on-info-fr.patch | 2 +-
...ify-at-boot-that-CMA-doesn-t-cross-a-256M.patch | 2 +-
.../051-0005-ovl-proper-cleanup-of-workdir.patch | 2 +-
.../generic/patches-4.4/204-module_strip.patch | 12 ++--
.../generic/patches-4.4/221-module_exports.patch | 2 +-
...bi-auto-create-ubiblock-device-for-rootfs.patch | 4 +-
...-set-ROOT_DEV-to-ubiblock-rootfs-if-unset.patch | 4 +-
...610-netfilter_match_bypass_default_checks.patch | 12 ++--
.../generic/patches-4.4/650-pppoe_header_pad.patch | 20 ---
...80-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 ++--
.../generic/patches-4.4/834-ledtrig-libata.patch | 8 +--
.../generic/patches-4.4/902-debloat_proc.patch | 2 +-
.../generic/patches-4.4/995-mangle_bootargs.patch | 2 +-
.../7017-fsl_qbman-add-qbman-driver.patch | 4 +-
...an-Enable-DPAA1-QBMan-for-ARM64-platforms.patch | 2 +-
...f-esdhc-add-remove-some-quirks-according-.patch | 11 +---
...rscape-Add-fsl-ls2085a-pcie-compatible-ID.patch | 25
...0-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch | 66 --
...ers-mmc-Add-compatible-string-for-LS1046A.patch | 2 +-
...mtd-backport-v4.7-0day-patches-from-Boris.patch | 66 +++---
...mtd-backport-v4.7-0day-patches-from-Boris.patch | 66 +++---
...0074-mtd-nand-import-nand_hw_control_init.patch | 6 +-
.../linux/oxnas/patches-4.4/999-libata-hacks.patch | 4 +-
.../0040-nand-add-mtk-nand-hack-hook.patch | 2 +-
.../patches-4.4/0901-spansion_nand_id_fix.patch| 4 +-
target/linux/x86/config-4.4| 4 +-
30 files changed, 126 insertions(+), 241 deletions(-)
delete mode 100644 target/linux/generic/patches-4.4/650-pppoe_header_pad.patch
delete mode 100644
target/linux/layerscape/patches-4.4/8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch
delete mode 100644
target/linux/layerscape/patches-4.4/8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 344c33009e..7fe6e7910b 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,10 +3,10 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .112
+LINUX_VERSION-4.4 = .116
LINUX_KERNEL_HASH-3.18.43 =
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.112 =
544b42cbeed022896115c76a18fc97b4507d5b41d7ac0ce1dce9afd6ffd11ecd
+LINUX_KERNEL_HASH-4.4.116 =
566fea5814627ee65cc1e6b9c4bfe2f7642ac36b6185e2a3dcb9e8ba1e325fa3
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git
a/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
b/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
index 48714aa466..7cce9bc77f 100644
---
a/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
+++
b/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
@@ -47,7 +47,7 @@ Signed-off-by: Jacek Anaszewski
#include
#include
-@@ -4914,6 +4915,9 @@ void ata_qc_complete(struct ata_queued_c
+@@ -4915,6 +4916,9 @@ void ata_qc_complete(struct ata_queued_c
{
struct ata_port *ap = qc->ap;
diff --git
a/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
b/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
index 0c07cb18c7..639e82c245 100644
--- a/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
+++ b/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
@@ -3,7 +3,7 @@ from mach files succeed.
--- a/drivers/gpio/gpio-ath79.c
+++ b/drivers/gpio/gpio-ath79.c
-@@ -202,4 +202,8 @@ static struct platform_driver ath79_gpio
+@@ -202,7 +202,11 @@ static struct platform_driver ath79_gpio
.probe = ath79_gpio_probe,
};
@@ -13,3 +13,6 @@ from mach files succeed.
+ return platform_driver_register(&ath79_gpio_driver);
+}
+postco
[LEDE-DEV] [PATCH v2] x86/64: enable CONFIG_X86_VSYSCALL_EMULATION in 17.01 4.4 kernel config
CONFIG_X86_VSYSCALL_EMULATION is disabled by default on x86/64, but without it the new KAISER stuff it breaks kernel 4.4 in the way shown below: CC arch/x86/mm/kaiser.o arch/x86/mm/kaiser.c: In function 'kaiser_init': arch/x86/mm/kaiser.c:348:8: error: 'vsyscall_pgprot' undeclared (first use in this function) vsyscall_pgprot); ^ arch/x86/mm/kaiser.c:270:47: note: in definition of macro 'kaiser_add_user_map_early' int __ret = kaiser_add_user_map(start, size, flags); \ ^ arch/x86/mm/kaiser.c:348:8: note: each undeclared identifier is reported only once for each function it appears in vsyscall_pgprot); ^ arch/x86/mm/kaiser.c:270:47: note: in definition of macro 'kaiser_add_user_map_early' int __ret = kaiser_add_user_map(start, size, flags); \ ^ scripts/Makefile.build:269: recipe for target 'arch/x86/mm/kaiser.o' failed Signed-off-by: Stijn Segers --- target/linux/x86/64/config-default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/x86/64/config-default b/target/linux/x86/64/config-default index 7d38df3030..bad7dddbe3 100644 --- a/target/linux/x86/64/config-default +++ b/target/linux/x86/64/config-default @@ -343,7 +343,7 @@ CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_PM_TIMER=y # CONFIG_X86_POWERNOW_K8 is not set CONFIG_X86_TSC=y -# CONFIG_X86_VSYSCALL_EMULATION is not set +CONFIG_X86_VSYSCALL_EMULATION=y CONFIG_X86_X2APIC=y # CONFIG_X86_X32 is not set CONFIG_XEN=y -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] x86/64: enable CONFIG_X86_VSYSCALL_EMULATION in kernel config
Op ma, 19 feb 2018 om 1:43 , schreef Syrone Wong : It's fixed by https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.9.y&id=83946c33b9b99b5bc6157cfbf3970265f006c2bf Best Regards, Syrone Wong Thanks, will send in a new patch. Stijn On Mon, Feb 19, 2018 at 4:46 AM, Stijn Segers wrote: CONFIG_X86_VSYSCALL_EMULATION is disabled by default on x86/64, but without it the new KAISER stuff breaks in the way shown below: CC arch/x86/mm/kaiser.o arch/x86/mm/kaiser.c: In function 'kaiser_init': arch/x86/mm/kaiser.c:348:8: error: 'vsyscall_pgprot' undeclared (first use in this function) vsyscall_pgprot); ^ arch/x86/mm/kaiser.c:270:47: note: in definition of macro 'kaiser_add_user_map_early' int __ret = kaiser_add_user_map(start, size, flags); \ ^ arch/x86/mm/kaiser.c:348:8: note: each undeclared identifier is reported only once for each function it appears in vsyscall_pgprot); ^ arch/x86/mm/kaiser.c:270:47: note: in definition of macro 'kaiser_add_user_map_early' int __ret = kaiser_add_user_map(start, size, flags); \ ^ scripts/Makefile.build:269: recipe for target 'arch/x86/mm/kaiser.o' failed Signed-off-by: Stijn Segers --- target/linux/x86/64/config-default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/x86/64/config-default b/target/linux/x86/64/config-default index 7d38df3030..bad7dddbe3 100644 --- a/target/linux/x86/64/config-default +++ b/target/linux/x86/64/config-default @@ -343,7 +343,7 @@ CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_PM_TIMER=y # CONFIG_X86_POWERNOW_K8 is not set CONFIG_X86_TSC=y -# CONFIG_X86_VSYSCALL_EMULATION is not set +CONFIG_X86_VSYSCALL_EMULATION=y CONFIG_X86_X2APIC=y # CONFIG_X86_X32 is not set CONFIG_XEN=y -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] x86/64: enable CONFIG_X86_VSYSCALL_EMULATION in kernel config
Op ma, 19 feb 2018 om 6:23 , schreef Stijn Segers : Op ma, 19 feb 2018 om 1:43 , schreef Syrone Wong : It's fixed by https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.9.y&id=83946c33b9b99b5bc6157cfbf3970265f006c2bf Best Regards, Syrone Wong Thanks, will send in a new patch. Stijn It turns out this patch already made it into 4.4.116 as well: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.4.y&id=4f3e6ab44b928ef70b77aa374886cb59fd9e4171 So please toss this patch. Evidently the X86_VSYSCALL_EMULATION bit didn't interfere with the patch, so 4.4.116 still compiled fine at first just like 4.4.115 and 4.4.114... Stijn On Mon, Feb 19, 2018 at 4:46 AM, Stijn Segers wrote: CONFIG_X86_VSYSCALL_EMULATION is disabled by default on x86/64, but without it the new KAISER stuff breaks in the way shown below: CC arch/x86/mm/kaiser.o arch/x86/mm/kaiser.c: In function 'kaiser_init': arch/x86/mm/kaiser.c:348:8: error: 'vsyscall_pgprot' undeclared (first use in this function) vsyscall_pgprot); ^ arch/x86/mm/kaiser.c:270:47: note: in definition of macro 'kaiser_add_user_map_early' int __ret = kaiser_add_user_map(start, size, flags); \ ^ arch/x86/mm/kaiser.c:348:8: note: each undeclared identifier is reported only once for each function it appears in vsyscall_pgprot); ^ arch/x86/mm/kaiser.c:270:47: note: in definition of macro 'kaiser_add_user_map_early' int __ret = kaiser_add_user_map(start, size, flags); \ ^ scripts/Makefile.build:269: recipe for target 'arch/x86/mm/kaiser.o' failed Signed-off-by: Stijn Segers --- target/linux/x86/64/config-default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/x86/64/config-default b/target/linux/x86/64/config-default index 7d38df3030..bad7dddbe3 100644 --- a/target/linux/x86/64/config-default +++ b/target/linux/x86/64/config-default @@ -343,7 +343,7 @@ CONFIG_X86_MINIMUM_CPU_FAMILY=64 CONFIG_X86_PM_TIMER=y # CONFIG_X86_POWERNOW_K8 is not set CONFIG_X86_TSC=y -# CONFIG_X86_VSYSCALL_EMULATION is not set +CONFIG_X86_VSYSCALL_EMULATION=y CONFIG_X86_X2APIC=y # CONFIG_X86_X32 is not set CONFIG_XEN=y -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] kernel: update 17.01 kernel to 4.4.117
Compile-tested on: ar71xx, ramips/mt7621, x86/64 Run-tested on: ar71xx, x86/64 Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/include/kernel-version.mk b/include/kernel-version.mk index 7fe6e7910b..fa4ca1eaf8 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -3,10 +3,10 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .43 -LINUX_VERSION-4.4 = .116 +LINUX_VERSION-4.4 = .117 LINUX_KERNEL_HASH-3.18.43 = 1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c -LINUX_KERNEL_HASH-4.4.116 = 566fea5814627ee65cc1e6b9c4bfe2f7642ac36b6185e2a3dcb9e8ba1e325fa3 +LINUX_KERNEL_HASH-4.4.117 = 120f490f9669784dd250a61f99003ad8906dcd746af2e4aad2ee73a4d42e4d68 ifdef KERNEL_PATCHVER LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER))) -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] kernel: bump 4.4 to 4.4.117
This bumps the 4.4. kernel in master to 4.4.117.
More Meltdown & Spectre mitigation.
* Refresh patches.
* Refresh x86/config for RETPOLINE.
* Deleted 8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch
(accepted upstream)
* Deleted 8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch (accepted upstream)
* Deleted 650-pppoe_header_pad.patch (does not apply anymore (code was
replaced)).
Bumps from 4.4.113 to 4.4.115 were handled by Kevin Darbyshire-Bryant.
Compile-tested on: ar71xx & oxnas.
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
.../004-register_gpio_driver_earlier.patch | 5 +-
.../patches-4.4/910-unaligned_access_hacks.patch | 12 ++--
...d-set-initial-ECC-params-based-on-info-fr.patch | 2 +-
5-03-mtd-nand-spi-nor-assign-MTD-of_node.patch | 2 +-
...4-mtd-nand-convert-to-nand_set_flash_node.patch | 4 +-
...nd-drop-unnecessary-partition-parser-data.patch | 8 +--
.../pending-4.4/001-mtdsplit_backport.patch| 2 +-
.../051-0005-ovl-proper-cleanup-of-workdir.patch | 2 +-
.../generic/pending-4.4/204-module_strip.patch | 12 ++--
.../generic/pending-4.4/221-module_exports.patch | 2 +-
...bi-auto-create-ubiblock-device-for-rootfs.patch | 4 +-
...-set-ROOT_DEV-to-ubiblock-rootfs-if-unset.patch | 4 +-
...610-netfilter_match_bypass_default_checks.patch | 14 ++---
.../generic/pending-4.4/650-pppoe_header_pad.patch | 20 --
...80-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 +--
.../generic/pending-4.4/834-ledtrig-libata.patch | 8 +--
.../generic/pending-4.4/902-debloat_proc.patch | 2 +-
.../generic/pending-4.4/995-mangle_bootargs.patch | 2 +-
...mtd-backport-v4.7-0day-patches-from-Boris.patch | 72 +++---
...0074-mtd-nand-import-nand_hw_control_init.patch | 6 +-
.../linux/oxnas/patches-4.4/999-libata-hacks.patch | 4 +-
22 files changed, 92 insertions(+), 109 deletions(-)
delete mode 100644 target/linux/generic/pending-4.4/650-pppoe_header_pad.patch
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 293100ecf8..2b201daca3 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,12 +3,12 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
-LINUX_VERSION-4.4 = .112
+LINUX_VERSION-4.4 = .117
LINUX_VERSION-4.9 = .82
LINUX_VERSION-4.14 = .20
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
-LINUX_KERNEL_HASH-4.4.112 =
544b42cbeed022896115c76a18fc97b4507d5b41d7ac0ce1dce9afd6ffd11ecd
+LINUX_KERNEL_HASH-4.4.117 =
120f490f9669784dd250a61f99003ad8906dcd746af2e4aad2ee73a4d42e4d68
LINUX_KERNEL_HASH-4.9.82 =
4b710b2701daafeb8e4db4c06f0ed3e62a6d20d6213a4927769c89ae42a9b180
LINUX_KERNEL_HASH-4.14.20 =
4ab7f42aa6af9c1e3b00cba6b1fa305a87407666aaa2fae555f7fbdaafb6d292
diff --git
a/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
b/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
index 0c07cb18c7..639e82c245 100644
--- a/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
+++ b/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
@@ -3,7 +3,7 @@ from mach files succeed.
--- a/drivers/gpio/gpio-ath79.c
+++ b/drivers/gpio/gpio-ath79.c
-@@ -202,4 +202,8 @@ static struct platform_driver ath79_gpio
+@@ -202,7 +202,11 @@ static struct platform_driver ath79_gpio
.probe = ath79_gpio_probe,
};
@@ -13,3 +13,6 @@ from mach files succeed.
+ return platform_driver_register(&ath79_gpio_driver);
+}
+postcore_initcall(ath79_gpio_init);
+
+ MODULE_DESCRIPTION("Atheros AR71XX/AR724X/AR913X GPIO API support");
+ MODULE_LICENSE("GPL v2");
diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
index a8d8c15c3b..9a440b4505 100644
--- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
+++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
@@ -491,7 +491,7 @@
memcpy(p, foc->val, foc->len);
--- a/net/ipv4/igmp.c
+++ b/net/ipv4/igmp.c
-@@ -529,7 +529,7 @@ static struct sk_buff *add_grec(struct s
+@@ -533,7 +533,7 @@ static struct sk_buff *add_grec(struct s
if (!skb)
return NULL;
psrc = (__be32 *)skb_put(skb, sizeof(__be32));
@@ -664,7 +664,7 @@
#define IP6_MF 0x0001
#define IP6_OFFSET 0xFFF8
-@@ -417,8 +417,8 @@ static inline void __ipv6_addr_set_half(
+@@ -418,8 +418,8 @@ static inline void __ipv6_addr_set_half(
}
#endif
#endif
@@ -675,7 +675,7 @@
}
static inline void ipv6_addr_set(struct in6_addr *addr,
-@@ -477,6 +477,8 @@ static inline bool ipv6_prefix_equal(con
+@@ -478,6 +478,8 @@ static inline bool ipv6_prefix_equal(con
const __be32 *a1 = addr1->s6_addr32;
const __be32 *a2 = addr2->s6_addr
[LEDE-DEV] [PATCH] kernel: bump 4.14 to 4.14.23
This patch bumps the 4.14 kernel to .23.
- Refreshed patches.
- Deleted
bcm53xx/patches-4.14/089-PCI-iproc-Fix-NULL-pointer-dereference-for-BCMA.patch.
Has been accepted upstream.
- Deleted
generic/pending-4.14/821-usb-Remove-annoying-warning-about-bogus-URB.patch. The
upstream URB code was changed,
the patch no longer applies. I discussed this with the patch author and
removed it for now, we'll see how it goes.
Compile-tested on: ramips/mt7621, x86/64
Run-tested on: ramips/mt7621, x86/64
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
...roc-Fix-NULL-pointer-dereference-for-BCMA.patch | 80 --
.../025-tcp-allow-drivers-to-tweak-TSQ-logic.patch | 8 +--
...36-netfilter-exit_net-cleanup-check-added.patch | 4 +-
.../linux/generic/hack-4.14/721-phy_packets.patch | 8 +--
.../generic/hack-4.14/901-debloat_sock_diag.patch | 2 +-
.../linux/generic/hack-4.14/902-debloat_proc.patch | 4 +-
...c_node_mem_map-with-ARCH_PFN_OFFSET-calcu.patch | 2 +-
...-mounting-ubi0-rootfs-in-init-do_mounts.c.patch | 4 +-
.../pending-4.14/655-increase_skb_pad.patch| 2 +-
...80-NET-skip-GRO-for-foreign-MAC-addresses.patch | 2 +-
...b-Remove-annoying-warning-about-bogus-URB.patch | 76
.../generic/pending-4.14/920-mangle_bootargs.patch | 4 +-
target/linux/mediatek/patches-4.14/0064-dts.patch | 6 +-
...dule-eeprom-ethtool-access-into-netdev-co.patch | 4 +-
...409-sfp-use-netdev-sfp_bus-for-start-stop.patch | 2 +-
.../patches-4.14/411-sfp-add-sfp-compatible.patch | 2 +-
.../0013-owrt-hack-fix-mt7688-cache-issue.patch| 4 +-
18 files changed, 31 insertions(+), 187 deletions(-)
delete mode 100644
target/linux/bcm53xx/patches-4.14/089-PCI-iproc-Fix-NULL-pointer-dereference-for-BCMA.patch
delete mode 100644
target/linux/generic/pending-4.14/821-usb-Remove-annoying-warning-about-bogus-URB.patch
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 293100ecf8..4e23f0de1d 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -5,12 +5,12 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
LINUX_VERSION-4.4 = .112
LINUX_VERSION-4.9 = .82
-LINUX_VERSION-4.14 = .20
+LINUX_VERSION-4.14 = .23
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
LINUX_KERNEL_HASH-4.4.112 =
544b42cbeed022896115c76a18fc97b4507d5b41d7ac0ce1dce9afd6ffd11ecd
LINUX_KERNEL_HASH-4.9.82 =
4b710b2701daafeb8e4db4c06f0ed3e62a6d20d6213a4927769c89ae42a9b180
-LINUX_KERNEL_HASH-4.14.20 =
4ab7f42aa6af9c1e3b00cba6b1fa305a87407666aaa2fae555f7fbdaafb6d292
+LINUX_KERNEL_HASH-4.14.23 =
9a97ba2baaed9aa7711524ae3b9179579efb902d76a814a916aefe5712ca
remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst https://,,$(1
sanitize_uri=$(call qstrip,$(subst @,_,$(subst :,_,$(subst .,_,$(subst
-,_,$(subst /,_,$(1)))
diff --git
a/target/linux/bcm53xx/patches-4.14/089-PCI-iproc-Fix-NULL-pointer-dereference-for-BCMA.patch
b/target/linux/bcm53xx/patches-4.14/089-PCI-iproc-Fix-NULL-pointer-dereference-for-BCMA.patch
deleted file mode 100644
index 2cdefc26ff..00
---
a/target/linux/bcm53xx/patches-4.14/089-PCI-iproc-Fix-NULL-pointer-dereference-for-BCMA.patch
+++ /dev/null
@@ -1,80 +0,0 @@
-From 3b65ca50d24ce33cb92d88840e289135c92b40ed Mon Sep 17 00:00:00 2001
-From: Ray Jui
-Date: Thu, 11 Jan 2018 12:36:16 -0800
-Subject: [PATCH] PCI: iproc: Fix NULL pointer dereference for BCMA
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-With the inbound DMA mapping supported added, the iProc PCIe driver
-parses DT property "dma-ranges" through call to
-"of_pci_dma_range_parser_init()". In the case of BCMA, this results in a
-NULL pointer deference due to a missing of_node.
-
-Fix this by adding a guard in pcie-iproc-platform.c to only enable the
-inbound DMA mapping logic when DT property "dma-ranges" is present.
-
-Fixes: dd9d4e7498de3 ("PCI: iproc: Add inbound DMA mapping support")
-Reported-by: Rafał Miłecki
-Signed-off-by: Ray Jui
-[lorenzo.pieral...@arm.com: updated commit log]
-Signed-off-by: Lorenzo Pieralisi
-Tested-by: Rafał Miłecki
-cc: # 4.10+
- drivers/pci/host/pcie-iproc-platform.c | 7 +++
- drivers/pci/host/pcie-iproc.c | 8 +---
- drivers/pci/host/pcie-iproc.h | 2 ++
- 3 files changed, 14 insertions(+), 3 deletions(-)
-
a/drivers/pci/host/pcie-iproc-platform.c
-+++ b/drivers/pci/host/pcie-iproc-platform.c
-@@ -92,6 +92,13 @@ static int iproc_pcie_pltfm_probe(struct
- pcie->need_ob_cfg = true;
- }
-
-+ /*
-+ * DT nodes are not used by all platforms that use the iProc PCIe
-+ * core driver. For platforms that require explict inbound mapping
-+ * configuration, "dma-ranges" would have been present in DT
-+ */
-+ pcie->need_ib_cfg = of_property_r
[LEDE-DEV] [PATCH] [17.01] kernel: bump 4.4 to 4.4.119
Bump the 4.4 kernel for the 17.01 release to 4.4.119. Refresh patches. Compile-tested: ar71xx, ramips/mt7621, x86/64 Run-tested: ar71xx, x86/64 Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 +-- .../patches-4.4/910-unaligned_access_hacks.patch | 2 +- .../patches-4.4/0029-Add-dwc_otg-driver.patch | 2 +- ...fd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch | 2 +- .../patches-4.4/0551-kbuild-add-fno-PIE.patch | 2 +- ...d-Steal-gcc-s-pie-from-the-very-beginning.patch | 2 +- .../patches-4.4/201-extra_optimization.patch | 2 +- .../patches-4.4/202-reduce_module_size.patch | 2 +- .../generic/patches-4.4/204-module_strip.patch | 13 --- .../666-Add-support-for-MAP-E-FMRs-mesh-mode.patch | 40 +++--- .../patches-4.4/901-debloat_sock_diag.patch| 2 +- .../096-08-usb-dwc3-remove-num_event_buffers.patch | 12 +++ .../096-09-usb-dwc3-drop-ev_buffs-array.patch | 4 +-- ...Added-FSL-MC-specific-member-to-the-msi_d.patch | 4 +-- ...-dts-mediatek-add-xHCI-usb-phy-for-mt8173.patch | 2 +- ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 9 ++--- ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 9 ++--- .../linux/oxnas/patches-4.4/800-oxnas-ehci.patch | 2 +- 18 files changed, 54 insertions(+), 61 deletions(-) diff --git a/include/kernel-version.mk b/include/kernel-version.mk index 7fe6e7910b..10d03a1461 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -3,10 +3,10 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .43 -LINUX_VERSION-4.4 = .116 +LINUX_VERSION-4.4 = .119 LINUX_KERNEL_HASH-3.18.43 = 1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c -LINUX_KERNEL_HASH-4.4.116 = 566fea5814627ee65cc1e6b9c4bfe2f7642ac36b6185e2a3dcb9e8ba1e325fa3 +LINUX_KERNEL_HASH-4.4.119 = 4f1f9b7b6b2ee93597239d89bb3b6b60c71ebd8c91d706fadd36f515c68443e6 ifdef KERNEL_PATCHVER LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER))) diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch index 9a440b4505..72d964df63 100644 --- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch +++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch @@ -310,7 +310,7 @@ if (t->parms.flags & IP6_TNL_F_USE_ORIG_FWMARK) --- a/net/ipv6/ip6_tunnel.c +++ b/net/ipv6/ip6_tunnel.c -@@ -1410,7 +1410,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str +@@ -1307,7 +1307,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str dsfield = ipv6_get_dsfield(ipv6h); if (t->parms.flags & IP6_TNL_F_USE_ORIG_TCLASS) diff --git a/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch b/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch index 1f652dc998..561fcaed10 100644 --- a/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch +++ b/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch @@ -4592,7 +4592,7 @@ dwc_otg: Remove duplicate gadget probe/unregister function +module_exit(fsg_cleanup); --- a/drivers/usb/host/Kconfig +++ b/drivers/usb/host/Kconfig -@@ -735,6 +735,19 @@ config USB_HWA_HCD +@@ -737,6 +737,19 @@ config USB_HWA_HCD To compile this driver a module, choose M here: the module will be called "hwa-hc". diff --git a/target/linux/brcm2708/patches-4.4/0083-mfd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch b/target/linux/brcm2708/patches-4.4/0083-mfd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch index e3101e0131..859a08db3a 100644 --- a/target/linux/brcm2708/patches-4.4/0083-mfd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch +++ b/target/linux/brcm2708/patches-4.4/0083-mfd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch @@ -390,7 +390,7 @@ Subject: [PATCH] mfd: Add Raspberry Pi Sense HAT core driver + --- a/drivers/video/fbdev/Kconfig +++ b/drivers/video/fbdev/Kconfig -@@ -2505,3 +2505,16 @@ config FB_SM712 +@@ -2506,3 +2506,16 @@ config FB_SM712 This driver is also available as a module. The module will be called sm712fb. If you want to compile it as a module, say M here and read . diff --git a/target/linux/brcm2708/patches-4.4/0551-kbuild-add-fno-PIE.patch b/target/linux/brcm2708/patches-4.4/0551-kbuild-add-fno-PIE.patch index 5bfbbf667c..c3b5adc7c4 100644 --- a/target/linux/brcm2708/patches-4.4/0551-kbuild-add-fno-PIE.patch +++ b/target/linux/brcm2708/patches-4.4/0551-kbuild-add-fno-PIE.patch @@ -29,7 +29,7 @@ Signed-off-by: Greg Kroah-Hartman --- a/Makefile +++ b/Makefile -@@ -622,6 +622,8 @@ KBUILD_CFLAGS += $(call cc-disable-warni +@@ -624,6 +624,8 @@ KBUILD_CFLAGS += $(call cc-disable-warni KBUILD_CFLAGS += $(call cc-disable-warning, format-truncation) KBUILD_CFLAGS += $(call cc-disable-warning, format-overflow) KBUILD_CFLAGS += $(call cc-disable-warning, int-in-bool-context) diff --git
[LEDE-DEV] [PATCH] kernel: bump 4.4 to 4.4.119
This bumps the 4.4. kernel in master to 4.4.119.
Includes more Meltdown & Spectre mitigation.
* Refresh patches.
* Refresh x86/config for RETPOLINE.
* Deleted 8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch
(accepted upstream)
* Deleted 8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch (accepted upstream)
* Deleted 650-pppoe_header_pad.patch (does not apply anymore (code was
replaced)).
Bumps from 4.4.112 to 4.4.115 were handled by Kevin Darbyshire-Bryant.
Compile-tested on: ar71xx & oxnas.
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
.../004-register_gpio_driver_earlier.patch | 5 +-
.../patches-4.4/910-unaligned_access_hacks.patch | 14 ++--
...d-set-initial-ECC-params-based-on-info-fr.patch | 2 +-
5-03-mtd-nand-spi-nor-assign-MTD-of_node.patch | 2 +-
...4-mtd-nand-convert-to-nand_set_flash_node.patch | 4 +-
...nd-drop-unnecessary-partition-parser-data.patch | 12 ++--
.../pending-4.4/001-mtdsplit_backport.patch| 2 +-
.../051-0005-ovl-proper-cleanup-of-workdir.patch | 2 +-
.../pending-4.4/201-extra_optimization.patch | 2 +-
.../pending-4.4/202-reduce_module_size.patch | 2 +-
.../generic/pending-4.4/204-module_strip.patch | 19 ++---
.../generic/pending-4.4/208-disable-modorder.patch | 4 +-
.../generic/pending-4.4/221-module_exports.patch | 2 +-
...bi-auto-create-ubiblock-device-for-rootfs.patch | 4 +-
...-set-ROOT_DEV-to-ubiblock-rootfs-if-unset.patch | 4 +-
...610-netfilter_match_bypass_default_checks.patch | 14 ++--
.../generic/pending-4.4/650-pppoe_header_pad.patch | 20 --
.../666-Add-support-for-MAP-E-FMRs-mesh-mode.patch | 40 +--
...80-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 +--
.../generic/pending-4.4/834-ledtrig-libata.patch | 8 +--
.../pending-4.4/901-debloat_sock_diag.patch| 2 +-
.../generic/pending-4.4/902-debloat_proc.patch | 2 +-
.../generic/pending-4.4/995-mangle_bootargs.patch | 2 +-
...mtd-backport-v4.7-0day-patches-from-Boris.patch | 81 ++
...0074-mtd-nand-import-nand_hw_control_init.patch | 6 +-
.../linux/oxnas/patches-4.4/800-oxnas-ehci.patch | 2 +-
.../linux/oxnas/patches-4.4/999-libata-hacks.patch | 4 +-
28 files changed, 128 insertions(+), 147 deletions(-)
delete mode 100644 target/linux/generic/pending-4.4/650-pppoe_header_pad.patch
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 293100ecf8..0f90e80cdd 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,12 +3,12 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
-LINUX_VERSION-4.4 = .112
+LINUX_VERSION-4.4 = .119
LINUX_VERSION-4.9 = .82
LINUX_VERSION-4.14 = .20
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
-LINUX_KERNEL_HASH-4.4.112 =
544b42cbeed022896115c76a18fc97b4507d5b41d7ac0ce1dce9afd6ffd11ecd
+LINUX_KERNEL_HASH-4.4.119 =
4f1f9b7b6b2ee93597239d89bb3b6b60c71ebd8c91d706fadd36f515c68443e6
LINUX_KERNEL_HASH-4.9.82 =
4b710b2701daafeb8e4db4c06f0ed3e62a6d20d6213a4927769c89ae42a9b180
LINUX_KERNEL_HASH-4.14.20 =
4ab7f42aa6af9c1e3b00cba6b1fa305a87407666aaa2fae555f7fbdaafb6d292
diff --git
a/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
b/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
index 0c07cb18c7..639e82c245 100644
--- a/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
+++ b/target/linux/ar71xx/patches-4.4/004-register_gpio_driver_earlier.patch
@@ -3,7 +3,7 @@ from mach files succeed.
--- a/drivers/gpio/gpio-ath79.c
+++ b/drivers/gpio/gpio-ath79.c
-@@ -202,4 +202,8 @@ static struct platform_driver ath79_gpio
+@@ -202,7 +202,11 @@ static struct platform_driver ath79_gpio
.probe = ath79_gpio_probe,
};
@@ -13,3 +13,6 @@ from mach files succeed.
+ return platform_driver_register(&ath79_gpio_driver);
+}
+postcore_initcall(ath79_gpio_init);
+
+ MODULE_DESCRIPTION("Atheros AR71XX/AR724X/AR913X GPIO API support");
+ MODULE_LICENSE("GPL v2");
diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
index a8d8c15c3b..72d964df63 100644
--- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
+++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
@@ -310,7 +310,7 @@
if (t->parms.flags & IP6_TNL_F_USE_ORIG_FWMARK)
--- a/net/ipv6/ip6_tunnel.c
+++ b/net/ipv6/ip6_tunnel.c
-@@ -1410,7 +1410,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str
+@@ -1307,7 +1307,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str
dsfield = ipv6_get_dsfield(ipv6h);
if (t->parms.flags & IP6_TNL_F_USE_ORIG_TCLASS)
@@ -491,7 +491,7 @@
memcpy(p, foc->val, foc->len);
--- a/net/ipv4/igmp.c
+++ b/net/ipv4/igmp.c
-@@ -529,7 +529,7 @@ static struct sk_buff *
[LEDE-DEV] [PATCH] kernel: bump 4.4 to 4.4.120 for 17.01
Bump the 4.4 kernel for the 17.01 release to 4.4.119. Refresh patches. Compile-tested: ar71xx, ramips/mt7621, x86/64 Run-tested: ar71xx, x86/64 Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 +-- .../patches-4.4/910-unaligned_access_hacks.patch | 2 +- .../patches-4.4/0029-Add-dwc_otg-driver.patch | 2 +- ...fd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch | 2 +- .../patches-4.4/0551-kbuild-add-fno-PIE.patch | 2 +- ...d-Steal-gcc-s-pie-from-the-very-beginning.patch | 2 +- .../patches-4.4/201-extra_optimization.patch | 2 +- .../patches-4.4/202-reduce_module_size.patch | 2 +- .../generic/patches-4.4/204-module_strip.patch | 13 --- .../666-Add-support-for-MAP-E-FMRs-mesh-mode.patch | 40 +++--- ...jecting-with-source-address-failed-policy.patch | 18 +- .../patches-4.4/901-debloat_sock_diag.patch| 2 +- .../096-08-usb-dwc3-remove-num_event_buffers.patch | 12 +++ .../096-09-usb-dwc3-drop-ev_buffs-array.patch | 4 +-- ...Added-FSL-MC-specific-member-to-the-msi_d.patch | 4 +-- ...-dts-mediatek-add-xHCI-usb-phy-for-mt8173.patch | 2 +- ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 9 ++--- ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 9 ++--- .../linux/oxnas/patches-4.4/800-oxnas-ehci.patch | 2 +- 19 files changed, 63 insertions(+), 70 deletions(-) diff --git a/include/kernel-version.mk b/include/kernel-version.mk index 7fe6e7910b..5cc0200893 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -3,10 +3,10 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .43 -LINUX_VERSION-4.4 = .116 +LINUX_VERSION-4.4 = .120 LINUX_KERNEL_HASH-3.18.43 = 1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c -LINUX_KERNEL_HASH-4.4.116 = 566fea5814627ee65cc1e6b9c4bfe2f7642ac36b6185e2a3dcb9e8ba1e325fa3 +LINUX_KERNEL_HASH-4.4.120 = a25f07372a2661c577e3c8a395bfb4a9f277518a01d097275604eccd3689f478 ifdef KERNEL_PATCHVER LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER))) diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch index 9a440b4505..72d964df63 100644 --- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch +++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch @@ -310,7 +310,7 @@ if (t->parms.flags & IP6_TNL_F_USE_ORIG_FWMARK) --- a/net/ipv6/ip6_tunnel.c +++ b/net/ipv6/ip6_tunnel.c -@@ -1410,7 +1410,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str +@@ -1307,7 +1307,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str dsfield = ipv6_get_dsfield(ipv6h); if (t->parms.flags & IP6_TNL_F_USE_ORIG_TCLASS) diff --git a/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch b/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch index 1f652dc998..561fcaed10 100644 --- a/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch +++ b/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch @@ -4592,7 +4592,7 @@ dwc_otg: Remove duplicate gadget probe/unregister function +module_exit(fsg_cleanup); --- a/drivers/usb/host/Kconfig +++ b/drivers/usb/host/Kconfig -@@ -735,6 +735,19 @@ config USB_HWA_HCD +@@ -737,6 +737,19 @@ config USB_HWA_HCD To compile this driver a module, choose M here: the module will be called "hwa-hc". diff --git a/target/linux/brcm2708/patches-4.4/0083-mfd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch b/target/linux/brcm2708/patches-4.4/0083-mfd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch index e3101e0131..859a08db3a 100644 --- a/target/linux/brcm2708/patches-4.4/0083-mfd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch +++ b/target/linux/brcm2708/patches-4.4/0083-mfd-Add-Raspberry-Pi-Sense-HAT-core-driver.patch @@ -390,7 +390,7 @@ Subject: [PATCH] mfd: Add Raspberry Pi Sense HAT core driver + --- a/drivers/video/fbdev/Kconfig +++ b/drivers/video/fbdev/Kconfig -@@ -2505,3 +2505,16 @@ config FB_SM712 +@@ -2506,3 +2506,16 @@ config FB_SM712 This driver is also available as a module. The module will be called sm712fb. If you want to compile it as a module, say M here and read . diff --git a/target/linux/brcm2708/patches-4.4/0551-kbuild-add-fno-PIE.patch b/target/linux/brcm2708/patches-4.4/0551-kbuild-add-fno-PIE.patch index 5bfbbf667c..c3b5adc7c4 100644 --- a/target/linux/brcm2708/patches-4.4/0551-kbuild-add-fno-PIE.patch +++ b/target/linux/brcm2708/patches-4.4/0551-kbuild-add-fno-PIE.patch @@ -29,7 +29,7 @@ Signed-off-by: Greg Kroah-Hartman --- a/Makefile +++ b/Makefile -@@ -622,6 +622,8 @@ KBUILD_CFLAGS += $(call cc-disable-warni +@@ -624,6 +624,8 @@ KBUILD_CFLAGS += $(call cc-disable-warni KBUILD_CFLAGS += $(call cc-disable-warning, format-truncation) KBUILD_CFLAGS += $(call cc-disable-warning, format-overflow) KBUILD_CFL
[LEDE-DEV] [PATCH] linux-firmware: bump firmware for Intel Wireless 8260AC to version 31
Bump the firmware for 8260AC and related hardware to version 31. Signed-off-by: Stijn Segers --- package/firmware/linux-firmware/intel.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/firmware/linux-firmware/intel.mk b/package/firmware/linux-firmware/intel.mk index 8cdbb48245..684513e5a6 100644 --- a/package/firmware/linux-firmware/intel.mk +++ b/package/firmware/linux-firmware/intel.mk @@ -143,7 +143,7 @@ $(eval $(call BuildPackage,iwlwifi-firmware-iwl7265d)) Package/iwlwifi-firmware-iwl8260c = $(call Package/firmware-default,Intel Wireless 8260 and 4165 firmware) define Package/iwlwifi-firmware-iwl8260c/install $(INSTALL_DIR) $(1)/lib/firmware - $(INSTALL_DATA) $(PKG_BUILD_DIR)/iwlwifi-8000C-27.ucode $(1)/lib/firmware + $(INSTALL_DATA) $(PKG_BUILD_DIR)/iwlwifi-8000C-31.ucode $(1)/lib/firmware endef $(eval $(call BuildPackage,iwlwifi-firmware-iwl8260c)) -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] prereq-mk: Change wget dependency to curl one.
Op za, 10 mrt 2018 om 7:03 , schreef Rosen Penev : On Sat, Mar 10, 2018 at 3:31 AM, Bjørn Mork wrote: Rosen Penev writes: curl is more common than GNU wget is. No. Yes. For example, Cygwin, Arch Linux, and my android phone all come with curl by default whereas wget is missing. wget has priority "important" in Debian, while curl is "optional". I don't think it makes much sense to tune the installation system for some weird distros no one actually use to build OpenWrt. Arch Linux is what I use to build OpenWrt. Arch users might catch the edge cases (notably the bleeding edge ones). Debian based systems tend to be more widespread than Arch ones, and running one or the other does not imply a more skilled user either way. Our wiki buildroot instructions seem to assume/favour a Debian-based system (that of course heavily depends on who wrote the entry) [1]. Distro/package management preferences aside, curl isn't mentioned at all on the buildroot wiki page. Wget is suggested as the tool of preference on *all* build platforms there (including Arch Linux). Look at the wider distro landscape: wget seems to be more prevalent. The Arch way isn't always the best way... Also: this has been brought up last year as well if I recall correctly. Same arguments were fielded. Stijn I've already made my case that curl is more common. The only issue would be if this commit would impact Debian or Ubuntu since they seem to be more common for building. Bjørn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev [1] https://wiki.openwrt.org/doc/howto/buildroot.exigence ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] kernel: bump 4.14 to 4.14.27
* Refreshed patches.
* Deleted 812-pci-dwc-fix-enumeration.patch (was accepted upstream)
Compile-tested: ramips/mt7621, x86/64
Run-tested: ramips/mt7621, x86/64
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
...match_table-parsing-for-partition-parsers.patch | 12 ++---
.../backport-4.14/011-kbuild-export-SUBARCH.patch | 6 +--
...ove-checksum-indirection-to-struct-nf_ipv.patch | 2 +-
...ove-checksum_partial-indirection-to-struc.patch | 2 +-
...emove-saveroute-indirection-in-struct-nf_.patch | 4 +-
...ove-route-indirection-to-struct-nf_ipv6_o.patch | 2 +-
...ove-reroute-indirection-to-struct-nf_ipv6.patch | 6 +--
...emove-route_key_size-field-in-struct-nf_a.patch | 2 +-
...emove-struct-nf_afinfo-and-its-helper-fun.patch | 4 +-
...emove-defensive-check-on-malformed-packet.patch | 4 +-
.../generic/hack-4.14/202-reduce_module_size.patch | 4 +-
.../generic/hack-4.14/207-disable-modorder.patch | 4 +-
.../linux/generic/hack-4.14/220-gc_sections.patch | 8 +--
.../generic/hack-4.14/221-module_exports.patch | 2 +-
.../pending-4.14/201-extra_optimization.patch | 2 +-
...610-netfilter_match_bypass_default_checks.patch | 8 +--
.../pending-4.14/812-pci-dwc-fix-enumeration.patch | 60 --
18 files changed, 38 insertions(+), 98 deletions(-)
delete mode 100644
target/linux/generic/pending-4.14/812-pci-dwc-fix-enumeration.patch
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index e24c96e9a6..04406cc473 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -5,12 +5,12 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
LINUX_VERSION-4.4 = .119
LINUX_VERSION-4.9 = .86
-LINUX_VERSION-4.14 = .25
+LINUX_VERSION-4.14 = .27
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
LINUX_KERNEL_HASH-4.4.119 =
4f1f9b7b6b2ee93597239d89bb3b6b60c71ebd8c91d706fadd36f515c68443e6
LINUX_KERNEL_HASH-4.9.86 =
a7cf6eb5efcf182f1760fdfc06118eecce5d8c9d82d6945e68fc15db990c6e85
-LINUX_KERNEL_HASH-4.14.25 =
6dcfbf79c068e51c1b06edb1ce58ddc9ca351f862bf2a144e96106ec3f21e587
+LINUX_KERNEL_HASH-4.14.27 =
0911a449c71a06c7232ece07dfcc041bd07efaf7e67799b9e2d0cf4bd9a028ea
remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst https://,,$(1
sanitize_uri=$(call qstrip,$(subst @,_,$(subst :,_,$(subst .,_,$(subst
-,_,$(subst /,_,$(1)))
diff --git
a/target/linux/brcm63xx/patches-4.14/120-mtd-add-of_match_table-parsing-for-partition-parsers.patch
b/target/linux/brcm63xx/patches-4.14/120-mtd-add-of_match_table-parsing-for-partition-parsers.patch
index 42b522ca0a..2e663259d1 100644
---
a/target/linux/brcm63xx/patches-4.14/120-mtd-add-of_match_table-parsing-for-partition-parsers.patch
+++
b/target/linux/brcm63xx/patches-4.14/120-mtd-add-of_match_table-parsing-for-partition-parsers.patch
@@ -52,9 +52,9 @@ Signed-off-by: Jonas Gorski
cur_offset = slave->offset + slave->mtd.size;
}
-@@ -1162,7 +1161,9 @@ int parse_mtd_partitions(struct mtd_info
- types = types_of;
- }
+@@ -1134,7 +1133,9 @@ static int mtd_part_of_parse(struct mtd_
+ const char *fixed = "fixed-partitions";
+ int ret, err = 0;
- np = of_get_child_by_name(mtd_get_of_node(master), "partitions");
+ np = mtd_get_of_node(master);
@@ -63,9 +63,9 @@ Signed-off-by: Jonas Gorski
of_property_for_each_string(np, "compatible", prop, compat) {
parser = mtd_part_get_compatible_parser(compat);
if (!parser)
-@@ -1178,8 +1179,12 @@ int parse_mtd_partitions(struct mtd_info
+@@ -1206,8 +1207,12 @@ int parse_mtd_partitions(struct mtd_info
+ types = types_of;
}
- of_node_put(np);
- if (!types)
+ if (!types) {
@@ -76,4 +76,4 @@ Signed-off-by: Jonas Gorski
+ }
for ( ; *types; types++) {
- pr_debug("%s: parsing partitions %s\n", master->name, *types);
+ /*
diff --git a/target/linux/generic/backport-4.14/011-kbuild-export-SUBARCH.patch
b/target/linux/generic/backport-4.14/011-kbuild-export-SUBARCH.patch
index 7080cd10a8..0ce7429591 100644
--- a/target/linux/generic/backport-4.14/011-kbuild-export-SUBARCH.patch
+++ b/target/linux/generic/backport-4.14/011-kbuild-export-SUBARCH.patch
@@ -10,10 +10,10 @@ Signed-off-by: Felix Fietkau
--- a/Makefile
+++ b/Makefile
-@@ -410,8 +410,8 @@ KERNELRELEASE = $(shell cat include/conf
- KERNELVERSION = $(VERSION)$(if $(PATCHLEVEL),.$(PATCHLEVEL)$(if
$(SUBLEVEL),.$(SUBLEVEL)))$(EXTRAVERSION)
+@@ -433,8 +433,8 @@ KBUILD_CFLAGS_MODULE := -DMODULE
+ KBUILD_LDFLAGS_MODULE := -T $(srctree)/scripts/module-common.lds
+ GCC_PLUGINS_CFLAGS :=
- export VERSION PATCHLEVEL SUBLEVEL KERNELRELEASE KERNELVERSION
-export ARCH SRCARCH CONFIG_SHELL HOSTCC HOSTCFLAGS CROSS_COMPILE AS LD CC
-export CPP AR NM STRIP OBJCOPY
[LEDE-DEV] [PATCH] Kernel: bump 4.14 to 4.14.27
* Patch 180-usb-xhci-add-support-for-performing-fake-doorbell.patch had to be
adjusted slightly because of upstream adapted code.
* Refreshed patches.
Compile-tested: ramips/mt7621, x86/64
Run-tested: ramips/mt7621, x86/64
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
...d-firmware-loader-for-uPD720201-and-uPD72.patch | 6 +-
.../802-usb-xhci-force-msi-renesas-xhci.patch | 4 +-
...-add-support-for-performing-fake-doorbell.patch | 4 +-
.../hack-4.14/661-use_fq_codel_by_default.patch| 2 +-
.../hack-4.14/702-phy_add_aneg_done_function.patch | 2 +-
.../generic/hack-4.14/904-debloat_dma_buf.patch| 4 +-
...180-net-phy-at803x-add-support-for-AT8032.patch | 8 +-
.../generic/pending-4.14/701-phy_extension.patch | 2 +-
...t-phy-at803x-allow-to-configure-via-pdata.patch | 8 +-
.../735-net-phy-at803x-fix-at8033-sgmii-mode.patch | 2 +-
...e-standard-large-page-OOB-layout-when-usi.patch | 2 +-
...se-usual-return-values-for-the-erase-hook.patch | 4 +-
...ovide-several-helpers-to-do-common-NAND-o.patch | 88 +++---
.../patches-4.14/0052-net-phy-add-FC.patch | 2 +-
.../patches-4.14/0034-NET-multi-phy-support.patch | 6 +-
.../0039-mtd-add-mt7621-nand-support.patch | 2 +-
.../0040-nand-hack-restore-write_page.patch| 4 +-
.../linux/ramips/patches-4.14/0040-nand-hack.patch | 8 +-
19 files changed, 81 insertions(+), 81 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index b289e03c7c..9a02bcb9f6 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -5,12 +5,12 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
LINUX_VERSION-4.4 = .121
LINUX_VERSION-4.9 = .87
-LINUX_VERSION-4.14 = .27
+LINUX_VERSION-4.14 = .29
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
LINUX_KERNEL_HASH-4.4.121 =
44a88268b5088dc326b30c9b9133ac35a9a200b636b7268d08f32abeae6ca729
LINUX_KERNEL_HASH-4.9.87 =
7ac9f6af69dc5a7e38bf35cc3fa889e3a4b22504a85f57fdc87734a8abe4c917
-LINUX_KERNEL_HASH-4.14.27 =
0911a449c71a06c7232ece07dfcc041bd07efaf7e67799b9e2d0cf4bd9a028ea
+LINUX_KERNEL_HASH-4.14.29 =
18f67b70ce9922c7ef95791bfd91f46e52ee9eb3e310978bb6ef6d2e93c14619
remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst https://,,$(1
sanitize_uri=$(call qstrip,$(subst @,_,$(subst :,_,$(subst .,_,$(subst
-,_,$(subst /,_,$(1)))
diff --git
a/target/linux/apm821xx/patches-4.14/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
b/target/linux/apm821xx/patches-4.14/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
index 144a06970f..49304ef870 100644
---
a/target/linux/apm821xx/patches-4.14/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
+++
b/target/linux/apm821xx/patches-4.14/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
@@ -44,7 +44,7 @@ Signed-off-by: Christian Lamparter
#include "xhci.h"
#include "xhci-trace.h"
-@@ -238,6 +240,458 @@ static void xhci_pme_acpi_rtd3_enable(st
+@@ -241,6 +243,458 @@ static void xhci_pme_acpi_rtd3_enable(st
static void xhci_pme_acpi_rtd3_enable(struct pci_dev *dev) { }
#endif /* CONFIG_ACPI */
@@ -503,7 +503,7 @@ Signed-off-by: Christian Lamparter
/* called during probe() after chip reset completes */
static int xhci_pci_setup(struct usb_hcd *hcd)
{
-@@ -273,6 +727,22 @@ static int xhci_pci_probe(struct pci_dev
+@@ -276,6 +730,22 @@ static int xhci_pci_probe(struct pci_dev
struct hc_driver *driver;
struct usb_hcd *hcd;
@@ -526,7 +526,7 @@ Signed-off-by: Christian Lamparter
driver = (struct hc_driver *)id->driver_data;
/* For some HW implementation, a XHCI reset is just not enough... */
-@@ -337,6 +807,16 @@ static void xhci_pci_remove(struct pci_d
+@@ -340,6 +810,16 @@ static void xhci_pci_remove(struct pci_d
{
struct xhci_hcd *xhci;
diff --git
a/target/linux/apm821xx/patches-4.14/802-usb-xhci-force-msi-renesas-xhci.patch
b/target/linux/apm821xx/patches-4.14/802-usb-xhci-force-msi-renesas-xhci.patch
index ec97f16e27..ae05d291f3 100644
---
a/target/linux/apm821xx/patches-4.14/802-usb-xhci-force-msi-renesas-xhci.patch
+++
b/target/linux/apm821xx/patches-4.14/802-usb-xhci-force-msi-renesas-xhci.patch
@@ -13,7 +13,7 @@ produce a noisy warning.
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
-@@ -196,7 +196,7 @@ static void xhci_pci_quirks(struct devic
+@@ -199,7 +199,7 @@ static void xhci_pci_quirks(struct devic
xhci->quirks |= XHCI_TRUST_TX_LENGTH;
if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
pdev->device == 0x0015)
@@ -44,7 +44,7 @@ produce a noisy warning.
hcd->msi_enabled = 1;
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
-@@ -1848,6 +1848,7 @@ struct xhci_hcd {
+@@ -1850,6 +1850,7 @@ struct xhci_hcd {
[LEDE-DEV] [PATCH v2] Kernel: bump 4.14 to 4.14.29
Right patch version this time, sorry!
* Patch 180-usb-xhci-add-support-for-performing-fake-doorbell.patch had to be
adjusted slightly because of upstream adapted code.
* Refreshed patches.
Compile-tested: ramips/mt7621, x86/64
Run-tested: ramips/mt7621, x86/64
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
...d-firmware-loader-for-uPD720201-and-uPD72.patch | 6 +-
.../802-usb-xhci-force-msi-renesas-xhci.patch | 4 +-
...-add-support-for-performing-fake-doorbell.patch | 4 +-
.../hack-4.14/661-use_fq_codel_by_default.patch| 2 +-
.../hack-4.14/702-phy_add_aneg_done_function.patch | 2 +-
.../generic/hack-4.14/904-debloat_dma_buf.patch| 4 +-
...180-net-phy-at803x-add-support-for-AT8032.patch | 8 +-
.../generic/pending-4.14/701-phy_extension.patch | 2 +-
...t-phy-at803x-allow-to-configure-via-pdata.patch | 8 +-
.../735-net-phy-at803x-fix-at8033-sgmii-mode.patch | 2 +-
...e-standard-large-page-OOB-layout-when-usi.patch | 2 +-
...se-usual-return-values-for-the-erase-hook.patch | 4 +-
...ovide-several-helpers-to-do-common-NAND-o.patch | 88 +++---
.../patches-4.14/0052-net-phy-add-FC.patch | 2 +-
.../patches-4.14/0034-NET-multi-phy-support.patch | 6 +-
.../0039-mtd-add-mt7621-nand-support.patch | 2 +-
.../0040-nand-hack-restore-write_page.patch| 4 +-
.../linux/ramips/patches-4.14/0040-nand-hack.patch | 8 +-
19 files changed, 81 insertions(+), 81 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index b289e03c7c..9a02bcb9f6 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -5,12 +5,12 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
LINUX_VERSION-4.4 = .121
LINUX_VERSION-4.9 = .87
-LINUX_VERSION-4.14 = .27
+LINUX_VERSION-4.14 = .29
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
LINUX_KERNEL_HASH-4.4.121 =
44a88268b5088dc326b30c9b9133ac35a9a200b636b7268d08f32abeae6ca729
LINUX_KERNEL_HASH-4.9.87 =
7ac9f6af69dc5a7e38bf35cc3fa889e3a4b22504a85f57fdc87734a8abe4c917
-LINUX_KERNEL_HASH-4.14.27 =
0911a449c71a06c7232ece07dfcc041bd07efaf7e67799b9e2d0cf4bd9a028ea
+LINUX_KERNEL_HASH-4.14.29 =
18f67b70ce9922c7ef95791bfd91f46e52ee9eb3e310978bb6ef6d2e93c14619
remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst https://,,$(1
sanitize_uri=$(call qstrip,$(subst @,_,$(subst :,_,$(subst .,_,$(subst
-,_,$(subst /,_,$(1)))
diff --git
a/target/linux/apm821xx/patches-4.14/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
b/target/linux/apm821xx/patches-4.14/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
index 144a06970f..49304ef870 100644
---
a/target/linux/apm821xx/patches-4.14/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
+++
b/target/linux/apm821xx/patches-4.14/801-usb-xhci-add-firmware-loader-for-uPD720201-and-uPD72.patch
@@ -44,7 +44,7 @@ Signed-off-by: Christian Lamparter
#include "xhci.h"
#include "xhci-trace.h"
-@@ -238,6 +240,458 @@ static void xhci_pme_acpi_rtd3_enable(st
+@@ -241,6 +243,458 @@ static void xhci_pme_acpi_rtd3_enable(st
static void xhci_pme_acpi_rtd3_enable(struct pci_dev *dev) { }
#endif /* CONFIG_ACPI */
@@ -503,7 +503,7 @@ Signed-off-by: Christian Lamparter
/* called during probe() after chip reset completes */
static int xhci_pci_setup(struct usb_hcd *hcd)
{
-@@ -273,6 +727,22 @@ static int xhci_pci_probe(struct pci_dev
+@@ -276,6 +730,22 @@ static int xhci_pci_probe(struct pci_dev
struct hc_driver *driver;
struct usb_hcd *hcd;
@@ -526,7 +526,7 @@ Signed-off-by: Christian Lamparter
driver = (struct hc_driver *)id->driver_data;
/* For some HW implementation, a XHCI reset is just not enough... */
-@@ -337,6 +807,16 @@ static void xhci_pci_remove(struct pci_d
+@@ -340,6 +810,16 @@ static void xhci_pci_remove(struct pci_d
{
struct xhci_hcd *xhci;
diff --git
a/target/linux/apm821xx/patches-4.14/802-usb-xhci-force-msi-renesas-xhci.patch
b/target/linux/apm821xx/patches-4.14/802-usb-xhci-force-msi-renesas-xhci.patch
index ec97f16e27..ae05d291f3 100644
---
a/target/linux/apm821xx/patches-4.14/802-usb-xhci-force-msi-renesas-xhci.patch
+++
b/target/linux/apm821xx/patches-4.14/802-usb-xhci-force-msi-renesas-xhci.patch
@@ -13,7 +13,7 @@ produce a noisy warning.
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
-@@ -196,7 +196,7 @@ static void xhci_pci_quirks(struct devic
+@@ -199,7 +199,7 @@ static void xhci_pci_quirks(struct devic
xhci->quirks |= XHCI_TRUST_TX_LENGTH;
if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
pdev->device == 0x0015)
@@ -44,7 +44,7 @@ produce a noisy warning.
hcd->msi_enabled = 1;
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
-@@ -1848,6 +1848,7 @@ struct xhci_h
[LEDE-DEV] [PATCH] Kernel: bump 4.4 to 4.4.124 for 17.01
* Refreshed patches
* Removed 087-Revert-led-core-Fix-brightness-setting-when-setting-.patch
(applied upstream)
Compile-tested on ar71xx, ramips/mt7621, x86/64
Run-tested on ar71xx
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 +-
.../patches-4.4/910-unaligned_access_hacks.patch | 2 +-
.../patches-4.4/0029-Add-dwc_otg-driver.patch | 2 +-
...core-Fix-brightness-setting-when-setting-.patch | 28 --
.../098-usb-dwc2-Remove-unnecessary-kfree.patch| 2 +-
...610-netfilter_match_bypass_default_checks.patch | 12 +--
...80-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 +-
.../generic/patches-4.4/721-phy_packets.patch | 2 +-
.../generic/patches-4.4/902-debloat_proc.patch | 4 +-
.../generic/patches-4.4/904-debloat_dma_buf.patch | 2 +-
...f-esdhc-add-remove-some-quirks-according-.patch | 2 +-
...ers-mmc-Add-compatible-string-for-LS1046A.patch | 2 +-
...mtd-backport-v4.7-0day-patches-from-Boris.patch | 112 ++---
...mtd-backport-v4.7-0day-patches-from-Boris.patch | 112 ++---
...0074-mtd-nand-import-nand_hw_control_init.patch | 2 +-
.../0032-USB-dwc2-add-device_reset.patch | 2 +-
.../0039-mtd-add-mt7621-nand-support.patch | 2 +-
.../0040-nand-add-mtk-nand-hack-hook.patch | 6 +-
.../patches-4.4/0901-spansion_nand_id_fix.patch| 4 +-
19 files changed, 142 insertions(+), 170 deletions(-)
delete mode 100644
target/linux/generic/patches-4.4/087-Revert-led-core-Fix-brightness-setting-when-setting-.patch
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 5cc0200893..deb13a6a82 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,10 +3,10 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .120
+LINUX_VERSION-4.4 = .124
LINUX_KERNEL_HASH-3.18.43 =
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.120 =
a25f07372a2661c577e3c8a395bfb4a9f277518a01d097275604eccd3689f478
+LINUX_KERNEL_HASH-4.4.124 =
59341c0af64bf0e2ba6f5305bff564286c228755827b8bebd002a9db2abc2129
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
index 72d964df63..7858abc64b 100644
--- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
+++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
@@ -359,7 +359,7 @@
for (p = *head; p; p = p->next) {
--- a/net/ipv4/route.c
+++ b/net/ipv4/route.c
-@@ -458,7 +458,7 @@ static struct neighbour *ipv4_neigh_look
+@@ -461,7 +461,7 @@ static struct neighbour *ipv4_neigh_look
else if (skb)
pkey = &ip_hdr(skb)->daddr;
diff --git a/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch
b/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch
index 561fcaed10..b94c0e0e06 100644
--- a/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch
+++ b/target/linux/brcm2708/patches-4.4/0029-Add-dwc_otg-driver.patch
@@ -670,7 +670,7 @@ dwc_otg: Remove duplicate gadget probe/unregister function
msleep(100);/* Cool down */
--- a/drivers/usb/core/message.c
+++ b/drivers/usb/core/message.c
-@@ -1909,6 +1909,85 @@ free_interfaces:
+@@ -1913,6 +1913,85 @@ free_interfaces:
if (cp->string == NULL &&
!(dev->quirks & USB_QUIRK_CONFIG_INTF_STRINGS))
cp->string = usb_cache_string(dev, cp->desc.iConfiguration);
diff --git
a/target/linux/generic/patches-4.4/087-Revert-led-core-Fix-brightness-setting-when-setting-.patch
b/target/linux/generic/patches-4.4/087-Revert-led-core-Fix-brightness-setting-when-setting-.patch
deleted file mode 100644
index 6378ed4351..00
---
a/target/linux/generic/patches-4.4/087-Revert-led-core-Fix-brightness-setting-when-setting-.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-From 4b98deaa353d8f7af3f7543d0b59497fe1275599 Mon Sep 17 00:00:00 2001
-Message-Id:
<4b98deaa353d8f7af3f7543d0b59497fe1275599.1520544136.git.mschif...@universe-factory.net>
-From: Matthias Schiffer
-Date: Thu, 8 Mar 2018 22:22:08 +0100
-Subject: [PATCH] Revert "led: core: Fix brightness setting when setting
- delay_off=0"
-
-This reverts commit 20ac8f72514b3af8b62c520d55656ded865eff00.
- drivers/leds/led-core.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/drivers/leds/led-core.c b/drivers/leds/led-core.c
-index 92b6798ef5b3..c1c3af089634 100644
a/drivers/leds/led-core.c
-+++ b/drivers/leds/led-core.c
-@@ -149,7 +149,7 @@ void led_blink_set(struct led_classdev *led_cdev,
- unsigned long *delay_on,
- unsigned long *delay_off)
- {
-- led_stop_software_blink(led_cdev);
-+ del_timer
Re: [LEDE-DEV] kernel version status
Hauke Mehrtens schreef op 1 april 2018 16:48:52 CEST: >The next OpenWrt release will use kernel 4.9 and kernel 4.14 depending >on the target. All targets that are *not* on either kernel 4.9 or 4.14 >will not be included in the next release. > >I did some overview of the kernel version some months ago here: >http://lists.infradead.org/pipermail/lede-dev/2017-October/009446.html >http://lists.infradead.org/pipermail/lede-dev/2018-February/011308.html > >Here is the current situation as of today: > > >The following targets are on kernel 4.14 and are fine: >* apm821xx >* archs38 >* armvirt >* bcm53xx >* cns3xxx >* imx6 >* ipq40xx >* kirkwood >* malta >* mediatek >* mvebu >* mxs >* octeon >* octeontx >* pistachio >* sunxi >* x86 > > >The following targets are on kernel 4.9 and are fine: >* ar71xx >* ar7 >* arc770 >* at91 > There are some patches for kernel 4.14 on the mailing list, > but it looks like nobody with the hardware wants to take care > of them. >* ath25 >* brcm2708 >* brcm47xx > There is a pull request with kernel 4.14 patches on github, we > will probably stay with kernel 4.9 for the next release. >* brcm63xx > patches for 4.14 are available in master >* ipq806x >* ixp4xx >* lantiq > patches for 4.14 are available in master, we will probably stay > with kernel 4.9 for the next release. >* layerscape >* mpc85xx >* omap > There is a pull request with kernel 4.14 patches on github. >* orion >* ramips > patches for 4.14 are available in master, we will probably stay John, are there any blockers preventing a move to 4.14? Been running it since Felix pushed support; haven't experienced any issues. Stijn > with kernel 4.9 for the next release. >* rb532 >* uml > > >The following targets are on kernel 4.4 and will probably not be >included in the next release: >* gemini > There are patches for kernel 4.14 on the mailing list, we will > probably get them in before the release and ship this with 4.14 >* oxnas >* zynq > >The following targets are on kernel 3.18 and will probably not be >included in the next release: >* adm5120 >* adm8668 >* au1000 >* mcs814x >* ppc40x >* ppc44x >* xburst > > >This target is on kernel 4.1 (WTF): >* omap24xx > > >All the targets which are not on kernel 4.9 or 4.14 will probably not >be >included in the next release, I also haven't seen any activity for any >of them expected the gemini target to get support for more recent >kernel >versions, if you need them please take care now. > >I am fine with the current status and do not see this as a blocker for >the next release, all important targets are on either 4.9 or 4.14, if >someone wants to see his target on a more recent version we are still >open for patches. > >Hauke > >___ >Lede-dev mailing list >Lede-dev@lists.infradead.org >http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.14 to 4.14.32
Op ma, 2 apr 2018 om 4:42 , schreef Hauke Mehrtens :
The following patches are now included upstream:
* 0052-MIPS-lantiq-fix-usb-clocks.patch
* 0053-MIPS-lantiq-enable-AHB-Bus-for-USB.patch
* 0060-lantiq-ase-enable-MFD-SYSCON.patch
Closes: FS#1466
Compile-tested on: ramips/mt7621, x86/64
Run-tested on: ramips/mt7621
Signed-off-by: Hauke Mehrtens
Tested-by: Stijn Segers
---
include/kernel-version.mk | 4 +--
.../generic/hack-4.14/207-disable-modorder.patch | 4 +--
.../hack-4.14/702-phy_add_aneg_done_function.patch | 2 +-
...c_node_mem_map-with-ARCH_PFN_OFFSET-calcu.patch | 2 +-
...80-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 +++---
.../generic/pending-4.14/701-phy_extension.patch | 2 +-
...-add-detach-callback-to-struct-phy_driver.patch | 2 +-
.../generic/pending-4.14/834-ledtrig-libata.patch | 8 ++---
.../0001-MIPS-lantiq-add-pcie-driver.patch | 4 +--
.../0052-MIPS-lantiq-fix-usb-clocks.patch | 25
---
.../0053-MIPS-lantiq-enable-AHB-Bus-for-USB.patch | 37
--
.../0060-lantiq-ase-enable-MFD-SYSCON.patch| 24
--
.../0048-net-core-add-RPS-balancer.patch | 6 ++--
.../patches-4.14/0052-net-phy-add-FC.patch | 2 +-
.../patches-4.14/411-sfp-add-sfp-compatible.patch | 2 +-
.../mvebu/patches-4.14/450-reprobe_sfp_phy.patch | 16 --
.../patches-4.14/0034-NET-multi-phy-support.patch | 6 ++--
17 files changed, 33 insertions(+), 123 deletions(-)
delete mode 100644
target/linux/lantiq/patches-4.14/0052-MIPS-lantiq-fix-usb-clocks.patch
delete mode 100644
target/linux/lantiq/patches-4.14/0053-MIPS-lantiq-enable-AHB-Bus-for-USB.patch
delete mode 100644
target/linux/lantiq/patches-4.14/0060-lantiq-ase-enable-MFD-SYSCON.patch
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 43f891c1c9..4be674ccdd 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -5,12 +5,12 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
LINUX_VERSION-4.4 = .121
LINUX_VERSION-4.9 = .91
-LINUX_VERSION-4.14 = .29
+LINUX_VERSION-4.14 = .32
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
LINUX_KERNEL_HASH-4.4.121 =
44a88268b5088dc326b30c9b9133ac35a9a200b636b7268d08f32abeae6ca729
LINUX_KERNEL_HASH-4.9.91 =
60caa752ec9fa1c426f6a2f37db3f268d0961b67a723b6443949112167b39832
-LINUX_KERNEL_HASH-4.14.29 =
18f67b70ce9922c7ef95791bfd91f46e52ee9eb3e310978bb6ef6d2e93c14619
+LINUX_KERNEL_HASH-4.14.32 =
cb0979bec663089a43b10cfbeae0cf9673544b0ff5968c33ede614ec0f43b680
remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst
https://,,$(1
sanitize_uri=$(call qstrip,$(subst @,_,$(subst :,_,$(subst
.,_,$(subst -,_,$(subst /,_,$(1)))
diff --git
a/target/linux/generic/hack-4.14/207-disable-modorder.patch
b/target/linux/generic/hack-4.14/207-disable-modorder.patch
index 8f817f32a7..8f99cde617 100644
--- a/target/linux/generic/hack-4.14/207-disable-modorder.patch
+++ b/target/linux/generic/hack-4.14/207-disable-modorder.patch
@@ -15,7 +15,7 @@ Signed-off-by: Felix Fietkau
--- a/Makefile
+++ b/Makefile
-@@ -1224,7 +1224,6 @@ all: modules
+@@ -1233,7 +1233,6 @@ all: modules
PHONY += modules
modules: $(vmlinux-dirs) $(if $(KBUILD_BUILTIN),vmlinux)
modules.builtin
@@ -23,7 +23,7 @@ Signed-off-by: Felix Fietkau
@$(kecho) ' Building modules, stage 2.';
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
-@@ -1253,7 +1252,6 @@ _modinst_:
+@@ -1262,7 +1261,6 @@ _modinst_:
rm -f $(MODLIB)/build ; \
ln -s $(CURDIR) $(MODLIB)/build ; \
fi
diff --git
a/target/linux/generic/hack-4.14/702-phy_add_aneg_done_function.patch
b/target/linux/generic/hack-4.14/702-phy_add_aneg_done_function.patch
index 61e460fda7..0453112a1f 100644
---
a/target/linux/generic/hack-4.14/702-phy_add_aneg_done_function.patch
+++
b/target/linux/generic/hack-4.14/702-phy_add_aneg_done_function.patch
@@ -15,7 +15,7 @@
--- a/drivers/net/phy/phy_device.c
+++ b/drivers/net/phy/phy_device.c
-@@ -1451,6 +1451,9 @@ int genphy_update_link(struct phy_device
+@@ -1458,6 +1458,9 @@ int genphy_update_link(struct phy_device
{
int status;
diff --git
a/target/linux/generic/pending-4.14/120-Fix-alloc_node_mem_map-with-ARCH_PFN_OFFSET-calcu.patch
b/target/linux/generic/pending-4.14/120-Fix-alloc_node_mem_map-with-ARCH_PFN_OFFSET-calcu.patch
index 43a1483c56..5ee89be5ad 100644
---
a/target/linux/generic/pending-4.14/120-Fix-alloc_node_mem_map-with-ARCH_PFN_OFFSET-calcu.patch
+++
b/target/linux/generic/pending-4.14/120-Fix-alloc_node_mem_map-with-ARCH_PFN_OFFSET-calcu.patch
@@ -71,7 +71,7 @@ Signed-off-by: Tobias Wolf
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
-@@ -6156,7 +6156,7 @@ static void __ref alloc_node_mem_map(str
+@@ -6147,7 +6147,7 @@ static void __ref alloc_node_mem_map(str
mem_map = NODE_DATA(0)->node_m
[LEDE-DEV] [PATCH] kernel: bump kernel 4.4 to 4.4.126 for 17.01
* Refreshed patches
Compile-tested: ar71xx, ramips/mt7621, x86/64
Run-tested: ar71xx
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 ++--
...onvert-IDE-trigger-to-common-disk-trigger.patch | 2 +-
...-add-a-round-up-ability-to-the-clock-divi.patch | 6 ++---
...cm2835-Support-for-clock-parent-selection.patch | 8 +++
.../0254-clk-bcm2835-Add-PWM-clock-support.patch | 2 +-
...-correctly-enable-fractional-clock-suppor.patch | 6 ++---
...-clk-bcm2835-clean-up-coding-style-issues.patch | 4 ++--
...35-expose-raw-clock-registers-via-debugfs.patch | 14 +--
...-remove-use-of-BCM2835_CLOCK_COUNT-in-dri.patch | 4 ++--
...-reorganize-bcm2835_clock_array-assignmen.patch | 4 ++--
...lk-bcm2835-enable-management-of-PCM-clock.patch | 2 +-
...lk-bcm2835-add-missing-PLL-clock-dividers.patch | 4 ++--
...lk-bcm2835-add-missing-osc-and-per-clocks.patch | 12 +-
...lk-bcm2835-Mark-the-VPU-clock-as-critical.patch | 4 ++--
...-Mark-GPIO-clocks-enabled-at-boot-as-crit.patch | 4 ++--
...-Skip-PLLC-clocks-when-deciding-on-a-new-.patch | 4 ++--
...-Mark-the-CM-SDRAM-clock-s-parent-as-crit.patch | 6 ++---
...-Don-t-rate-change-PLLs-on-behalf-of-divi.patch | 2 +-
...-Do-appropriate-name-lookups-for-DSI1-s-p.patch | 6 ++---
...2835-Add-an-enum-for-the-DSI1-pixel-clock.patch | 8 +++
...-Clamp-the-PLL-s-requested-rate-to-the-ha.patch | 2 +-
...clk-bcm2835-Fix-fixed_divider-of-pllh_aux.patch | 2 +-
...port-rate-change-propagation-on-bcm2835-c.patch | 6 ++---
...ow-rate-change-propagation-to-PLLH_AUX-on.patch | 2 +-
...-maybe-uninitialized-warning-in-bcm2835_c.patch | 2 +-
...-Don-t-rate-change-PLLs-on-behalf-of-DSI-.patch | 28 +++---
.../generic/patches-4.4/834-ledtrig-libata.patch | 8 +++
...c-Segregate-IFC-fcm-and-runtime-registers.patch | 20
...-pci-layerscape-add-MSI-interrupt-support.patch | 2 +-
...4-use-fixmap-region-for-permanent-FDT-map.patch | 9 ---
...0074-mtd-nand-import-nand_hw_control_init.patch | 2 +-
.../linux/oxnas/patches-4.4/999-libata-hacks.patch | 4 ++--
32 files changed, 98 insertions(+), 95 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index deb13a6a82..ccffa7aa0e 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,10 +3,10 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .124
+LINUX_VERSION-4.4 = .126
LINUX_KERNEL_HASH-3.18.43 =
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.124 =
59341c0af64bf0e2ba6f5305bff564286c228755827b8bebd002a9db2abc2129
+LINUX_KERNEL_HASH-4.4.126 =
e9c8f4c4cda89124e7c53bda979db3f9c12f7c177bee90ddd3ab38d5ae99cd58
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git
a/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
b/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
index 7cce9bc77f..6441866806 100644
---
a/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
+++
b/target/linux/apm821xx/patches-4.4/040-backport_leds-convert-IDE-trigger-to-common-disk-trigger.patch
@@ -47,7 +47,7 @@ Signed-off-by: Jacek Anaszewski
#include
#include
-@@ -4915,6 +4916,9 @@ void ata_qc_complete(struct ata_queued_c
+@@ -4936,6 +4937,9 @@ void ata_qc_complete(struct ata_queued_c
{
struct ata_port *ap = qc->ap;
diff --git
a/target/linux/brcm2708/patches-4.4/0252-clk-bcm2835-add-a-round-up-ability-to-the-clock-divi.patch
b/target/linux/brcm2708/patches-4.4/0252-clk-bcm2835-add-a-round-up-ability-to-the-clock-divi.patch
index b9b139ce9b..d9e82c78d2 100644
---
a/target/linux/brcm2708/patches-4.4/0252-clk-bcm2835-add-a-round-up-ability-to-the-clock-divi.patch
+++
b/target/linux/brcm2708/patches-4.4/0252-clk-bcm2835-add-a-round-up-ability-to-the-clock-divi.patch
@@ -16,7 +16,7 @@ Signed-off-by: Michael Turquette
--- a/drivers/clk/bcm/clk-bcm2835.c
+++ b/drivers/clk/bcm/clk-bcm2835.c
-@@ -1166,22 +1166,24 @@ static int bcm2835_clock_is_on(struct cl
+@@ -1170,22 +1170,24 @@ static int bcm2835_clock_is_on(struct cl
static u32 bcm2835_clock_choose_div(struct clk_hw *hw,
unsigned long rate,
@@ -49,7 +49,7 @@ Signed-off-by: Michael Turquette
/* clamp to min divider of 1 */
div = max_t(u32, div, 1 << CM_DIV_FRAC_BITS);
-@@ -1221,7 +1223,7 @@ static long bcm2835_clock_round_rate(str
+@@ -1225,7 +1227,7 @@ static long bcm2835_clock_round_rate(str
unsigned long *parent_rate)
{
struct bcm2835_clock *clock = bcm2835_clock_from_hw(hw);
@@ -58,7 +58,7 @@ Signed-off-by: Michael Turquette
return bcm2835_clock_rate_from_divisor(clock, *parent_rate, div);
}
-@@ -1290,
[LEDE-DEV] [PATCH] ramips: add usb packages into DIR-860L B1 profile
This patch adds the kmod-usb3 and kmod-usb-ledtrig-usbport packages to the DIR-860L B1 profile. The DIR-860L B1 has a USB 3 port. Signed-off-by: Stijn Segers --- target/linux/ramips/image/mt7621.mk | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/ramips/image/mt7621.mk b/target/linux/ramips/image/mt7621.mk index e0fbb61..5974408 100644 --- a/target/linux/ramips/image/mt7621.mk +++ b/target/linux/ramips/image/mt7621.mk @@ -72,6 +72,7 @@ define Device/dir-860l-b1 seama-seal -m "signature=wrgac13_dlink.2013gui_dir860lb" | \ check-size (IMAGE_SIZE) DEVICE_TITLE := D-Link DIR-860L B1 + DEVICE_PACKAGES := kmod-usb3 kmod-usb-ledtrig-usbport endef TARGET_DEVICES += dir-860l-b1 -- 2.10.1 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30
This patch bumps the 4.4 kernel from .28 to .30 and refreshes the patches. Compile-tested on ar71xx, x86/64, ramips/mt7621, brcm47xx and kirkwood. Run-tested on ar71xx & ramips/mt7621, brcm47xx and kirkwood (last two confirmed by P. Wassi). Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 ++-- ...-detect-JEDEC-incompatible-w25q128-using-.patch | 2 +- ...r-convert-to-spi_nor_-get-set-_flash_node.patch | 2 +- ...e-creds-with-the-ones-from-the-superblock.patch | 2 +- .../477-mtd-add-spi-nor-add-mx25u3235f.patch | 4 ++-- .../patches-4.4/0153-lantiq-VPE-softdog.patch | 1 - ...re-the-appended-dtb-address-in-a-variable.patch | 2 +- .../1074-mtd-nand-spi-nor-assign-MTD-of_node.patch | 2 +- ...r-convert-to-spi_nor_-get-set-_flash_node.patch | 2 +- .../1078-mtd-spi-nor-drop-flash_node-field.patch | 2 +- ...-remove-unnecessary-leading-space-from-db.patch | 2 +- ...-provide-default-erase_sector-implementat.patch | 4 ++-- ...-Fix-error-message-with-unrecognized-JEDE.patch | 2 +- ...i-nor-Check-the-return-value-from-read_sr.patch | 2 +- ...-mtd-spi-nor-Add-SPI-NOR-layer-PM-support.patch | 6 +++--- ...pi-nor-check-return-value-from-read-write.patch | 12 +-- ...94-mtd-spi-nor-stop-passing-around-retlen.patch | 14 ++--- .../1095-mtd-spi-nor-simplify-write-loop.patch | 4 ++-- .../1096-mtd-spi-nor-add-read-loop.patch | 2 +- ...pi_nor-Disable-Micron-flash-HW-protection.patch | 2 +- ...-nor-Support-R-W-for-S25FS-S-family-flash.patch | 6 +++--- ...105-mtd-spi-nor-add-DDR-quad-read-support.patch | 12 +-- ...s-mtd-spi-nor-Enable-QSPI-Flash-in-Kernel.patch | 4 ++-- ...or-fsl-quad-add-flash-S25FS-extra-support.patch | 6 +++--- ...nor-disable-4kb-sector-erase-for-s25fl128.patch | 2 +- ...c-fsl-move-mpc85xx.h-to-include-linux-fsl.patch | 2 +- .../7017-fsl_qbman-add-qbman-driver.patch | 2 +- ...o-Port-gpio-driver-to-support-layerscape-.patch | 2 +- .../8073-ls1012a-added-clock-configuration.patch | 2 +- ...mtd-backport-v4.7-0day-patches-from-Boris.patch | 24 +++--- ...d-SolidRun-Armada-388-Clearfog-A1-DT-file.patch | 4 ++-- .../0054-mtd-add-chunked-read-io-to-m25p80.patch | 6 +++--- 32 files changed, 72 insertions(+), 73 deletions(-) diff --git a/include/kernel-version.mk b/include/kernel-version.mk index f511420..f406719 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -4,11 +4,11 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .43 LINUX_VERSION-4.1 = .34 -LINUX_VERSION-4.4 = .28 +LINUX_VERSION-4.4 = .30 LINUX_KERNEL_MD5SUM-3.18.43 = b1faeb4a2e1e70ffe061bdbb3452840a LINUX_KERNEL_MD5SUM-4.1.34 = fba99f0f4765ebf01033e69518740a3c -LINUX_KERNEL_MD5SUM-4.4.28 = 841acb9109a893ab2f60b02355e1527e80fa09251e46339317f6984d69b1f4fc +LINUX_KERNEL_MD5SUM-4.4.30 = 9d249133bd12dde04f434bb4a5a4a23dd42ead721803c0ba4b5742efd239995c ifdef KERNEL_PATCHVER LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER))) diff --git a/target/linux/bcm53xx/patches-4.4/405-mtd-spi-nor-detect-JEDEC-incompatible-w25q128-using-.patch b/target/linux/bcm53xx/patches-4.4/405-mtd-spi-nor-detect-JEDEC-incompatible-w25q128-using-.patch index df252b2..a93dfb0 100644 --- a/target/linux/bcm53xx/patches-4.4/405-mtd-spi-nor-detect-JEDEC-incompatible-w25q128-using-.patch +++ b/target/linux/bcm53xx/patches-4.4/405-mtd-spi-nor-detect-JEDEC-incompatible-w25q128-using-.patch @@ -13,7 +13,7 @@ Signed-off-by: Rafał Miłecki --- a/drivers/mtd/spi-nor/spi-nor.c +++ b/drivers/mtd/spi-nor/spi-nor.c -@@ -873,6 +873,18 @@ static const struct flash_info *spi_nor_ +@@ -874,6 +874,18 @@ static const struct flash_info *spi_nor_ } dev_err(nor->dev, "unrecognized JEDEC id bytes: %02x, %2x, %2x\n", id[0], id[1], id[2]); diff --git a/target/linux/brcm63xx/patches-4.4/000-4.5-03-spi-nor-convert-to-spi_nor_-get-set-_flash_node.patch b/target/linux/brcm63xx/patches-4.4/000-4.5-03-spi-nor-convert-to-spi_nor_-get-set-_flash_node.patch index 3dce6c0..79af8a6 100644 --- a/target/linux/brcm63xx/patches-4.4/000-4.5-03-spi-nor-convert-to-spi_nor_-get-set-_flash_node.patch +++ b/target/linux/brcm63xx/patches-4.4/000-4.5-03-spi-nor-convert-to-spi_nor_-get-set-_flash_node.patch @@ -68,7 +68,7 @@ Reviewed-by: Boris Brezillon spifi->nor.write = nxp_spifi_write; --- a/drivers/mtd/spi-nor/spi-nor.c +++ b/drivers/mtd/spi-nor/spi-nor.c -@@ -,7 +,7 @@ int spi_nor_scan(struct spi_nor *nor, co +@@ -1112,7 +1112,7 @@ int spi_nor_scan(struct spi_nor *nor, co const struct flash_info *info = NULL; struct device *dev = nor->dev; struct mtd_info *mtd = &nor->mtd; diff --git a/target/linux/generic/patches-4.4/051-0002-ovl-override-creds-with-the-ones-from-the-superblock.patch b/target/linux/generic/patches-4.4/051-0002-ovl-override-creds-with-the-ones-from-the-superbloc
Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30
Hi, I rely on KanjiMonster's script to adjust the patches, so they apply cleanly. Without it, if you start a verbose build, you'd see 'patch applied with fuzz 2' etc. With the amount of patches a project like this one has, clean patches eliminate redundant output and allow you to zoom in quicker on the correct lines in the source code (and the part of the patch that breaks them). https://gist.github.com/KanjiMonster/dfcd1af3190aa7b2941f1bdcb119f25e Cheers Stijn Op di, 1 nov 2016 om 6:58 , schreef p.wa...@gmx.at: This patch bumps the 4.4 kernel from .28 to .30 and refreshes the patches. A question regarding the 'patch refreshing' and my previous patch for 4.4.29. I want to figure out where my workflow is erroneous, or what things I did not understand when refreshing a patch series during a kernel upgrade like this. For example let me take the first refreshing you submitted (besides 4.4.28->30 in kernel-version.mk): The file 'target/linux/bcm53xx/patches-4.4/405-mtd-spi-nor-detect-JEDEC-incompatible-w25q128-using-.patch' patches the kernel driver 'drivers/mtd/spi-nor/spi-nor.c' Now with your patch refreshing, you adjust the offsets in spi-nor.c However, this file (spi-nor.c) was last changed back in July (2016-07-14). So why is it required to refresh this patch on 4.4.28 -> .30, when this file was last changed during 4.4.15 -> .16 ? Don't get me wrong, I just want to understand where I have to adjust my workflow. Best regards, P. Wassi ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30
On 2016-11-02 03:17, Outback Dingo wrote: [...] I find it quite odd that it doesnt apply cleanly to my LEDE tree at git rev commit 411babb28a3091f693832fb30d475aa1e99c6d11 which is a merge of the latest ipfilters changes That's weird... Can't check now, at work, will check this evening. Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.30
Stijn Segers schreef op 2016-11-02 09:44: On 2016-11-02 03:17, Outback Dingo wrote: [...] I find it quite odd that it doesnt apply cleanly to my LEDE tree at git rev commit 411babb28a3091f693832fb30d475aa1e99c6d11 which is a merge of the latest ipfilters changes That's weird... Can't check now, at work, will check this evening. Stijn Stintel confirmed me the patch is fine, so that means the error is at your end... Patch has already been accepted in LEDE's patchwork as well, of course that doesn't guarantee it doesn't break, but still. Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] wireless became unstable after "mac80211: update to wireless-testing 2016-10-08" commit ad51e09fd1301484820a466a49447a34d7504882
There is a bug open for this: https://bugs.lede-project.org/index.php?do=details&task_id=241&order=id&sort=desc Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Smaller /overlay with latest snapshot on WDR-3600
Hi, 4,5 MiB sounds about right for a device with 8 MiB flash. If you do a factory reset, does the flash layout look identical to an older LEDE installation? It should, afaik, I haven't seen any changes in that sense in git lately. Most probably one of the packages you install afterwards grew in size (or maybe pulled in new dependencies). You might be better off using the image generator to include the packages you want in your image, prior to flashing it. That's more efficient space-wise. Hope this helps. Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] openssl build issue
On Fri, Dec 2, 2016 at 10:48 AM, Sudeepto Roy gmail.com> wrote:
Hi,
on my setup i am having trouble building openssl and the reason is a
creation if a file whose file name is bigger then 144 char.
make[5]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/apps'
make[4]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j'
rm -f
/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_*
touch
/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2
touch: cannot touch
'/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2':
File name too long
make[3]: ***
[/home/sudeepto/Documents/projects/lede/source/build_dir/target-mips_24kc_musl-1.1.15/openssl-1.0.2j/.configured_nnynnnynnyy_shared_no-err_no-sse2_no-ssl2_no-ssl2-method_no-heartbeats_no-engines_no-ec2m_no-ssl3_no-ssl3-method_no-hw_no-dtls_no-comp_no-sse2]
Error 1
make[3]: Leaving directory
`/home/sudeepto/Documents/projects/lede/source/package/libs/openssl'
make[2]: *** [package/libs/openssl/compile] Error 2
<<<
I don't see the same issue on another machine running Ubuntu 14.04 and
i had to make code changes to satisfy touch command on my working
machine. diff below
Do you know the significance of STAMP_CONFIGURED variable and will it
be ok to change this variable to have camel-case syntax. This makes
the file name sorter and we will have scope for future flags in case.
any comments if i should submit a patch for this?
Diff:
sudeepto at ubuntu:source$ git diff
diff --git a/package/libs/openssl/Makefile
b/package/libs/openssl/Makefile
index a09c148..0a10e30 100644
--- a/package/libs/openssl/Makefile
+++ b/package/libs/openssl/Makefile
@@ -168,7 +168,10 @@ else
endif
endif
-STAMP_CONFIGURED := $(STAMP_CONFIGURED)_$(subst
$(space),_,$(OPENSSL_OPTIONS))
+S_DIR := $(shell dirname $(STAMP_CONFIGURED))
+S_BASE := $(shell basename $(STAMP_CONFIGURED) | cut -d_ -f1)
+S_OPTION := $(subst $(space),_,$(OPENSSL_OPTIONS))
+STAMP_CONFIGURED := $(S_DIR)/$(S_BASE)_$(shell echo $(S_OPTION) | sed
-r 's/(^|_|-)([a-z])/\U\2/g')
define Build/Configure
[ -f $(STAMP_CONFIGURED) ] || { \
sudeepto at ubuntu:source$
Regards,
Sudeepto Roy
___
Lede-dev mailing list
Lede-dev at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Are you using an encrypted /home by any chance? I had similar errors, I
have my code outside /home for exactly that reason - because ecryptfs
doesn't like the long filenames.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] Kernel: update kernel 4.4 to version 4.4.37
Bump to .37 for all platforms supported by 4.4. All patches refreshed. Compile-tested on ar71xx, ramips/mt7621 and x86/64. Run-tested on ar71xx and ramips/mt7621. Signed-off-by: Stijn Segers --- ...tend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch index 96f20a4..c58830a 100644 --- a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch +++ b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch @@ -1,6 +1,6 @@ --- a/drivers/pci/probe.c +++ b/drivers/pci/probe.c -@@ -1938,7 +1938,8 @@ static void pcie_write_mrrs(struct pci_d +@@ -1964,7 +1964,8 @@ static void pcie_write_mrrs(struct pci_d /* In the "safe" case, do not configure the MRRS. There appear to be * issues with setting MRRS to 0 on a number of devices. */ -- 2.10.2 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] Kernel: bump to 4.4.38
This patch bumps 4.4 from .36 to .38 (and supersedes my incomplete patch
for .37). Compile-tested on ar71xx, ramips/mt7621 and x86/64.
Run-tested on ar71xx & ramips/mt7621.
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 ++--
.../patches-4.4/910-unaligned_access_hacks.patch | 2 +-
...ER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch | 2 +-
.../patches-4.4/630-packet_socket_type.patch | 4 ++--
.../patches-4.4/653-disable_netlink_trim.patch | 2 +-
.../666-Add-support-for-MAP-E-FMRs-mesh-mode.patch | 22 +++---
6 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 0cde467..eeb8195 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -4,11 +4,11 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
LINUX_VERSION-4.1 = .34
-LINUX_VERSION-4.4 = .36
+LINUX_VERSION-4.4 = .38
LINUX_KERNEL_MD5SUM-3.18.43 = b1faeb4a2e1e70ffe061bdbb3452840a
LINUX_KERNEL_MD5SUM-4.1.34 = fba99f0f4765ebf01033e69518740a3c
-LINUX_KERNEL_MD5SUM-4.4.36 = c23de77131c05a27e638026972ada85b
+LINUX_KERNEL_MD5SUM-4.4.38 =
77ed9e650b65788a1f9f371ba87c2e50b5ba7624bc834ae38b036f7f592816a6
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
index fc006f0..21cad91 100644
--- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
+++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
@@ -310,7 +310,7 @@
if (t->parms.flags & IP6_TNL_F_USE_ORIG_FWMARK)
--- a/net/ipv6/ip6_tunnel.c
+++ b/net/ipv6/ip6_tunnel.c
-@@ -1388,7 +1388,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str
+@@ -1397,7 +1397,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str
dsfield = ipv6_get_dsfield(ipv6h);
if (t->parms.flags & IP6_TNL_F_USE_ORIG_TCLASS)
diff --git
a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
index 96f20a4..c58830a 100644
---
a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
+++
b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
@@ -1,6 +1,6 @@
--- a/drivers/pci/probe.c
+++ b/drivers/pci/probe.c
-@@ -1938,7 +1938,8 @@ static void pcie_write_mrrs(struct pci_d
+@@ -1964,7 +1964,8 @@ static void pcie_write_mrrs(struct pci_d
/* In the "safe" case, do not configure the MRRS. There appear to be
* issues with setting MRRS to 0 on a number of devices.
*/
diff --git a/target/linux/generic/patches-4.4/630-packet_socket_type.patch
b/target/linux/generic/patches-4.4/630-packet_socket_type.patch
index b14afdd..eb79b2d 100644
--- a/target/linux/generic/patches-4.4/630-packet_socket_type.patch
+++ b/target/linux/generic/patches-4.4/630-packet_socket_type.patch
@@ -91,7 +91,7 @@ Signed-off-by: Felix Fietkau
if (sock->type == SOCK_PACKET)
po->prot_hook.func = packet_rcv_spkt;
-@@ -3707,6 +3710,16 @@ packet_setsockopt(struct socket *sock, i
+@@ -3713,6 +3716,16 @@ packet_setsockopt(struct socket *sock, i
po->xmit = val ? packet_direct_xmit : dev_queue_xmit;
return 0;
}
@@ -108,7 +108,7 @@ Signed-off-by: Felix Fietkau
default:
return -ENOPROTOOPT;
}
-@@ -3759,6 +3772,13 @@ static int packet_getsockopt(struct sock
+@@ -3765,6 +3778,13 @@ static int packet_getsockopt(struct sock
case PACKET_VNET_HDR:
val = po->has_vnet_hdr;
break;
diff --git a/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
b/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
index 2f64696..073550c 100644
--- a/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
+++ b/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
@@ -1,6 +1,6 @@
--- a/net/netlink/af_netlink.c
+++ b/net/netlink/af_netlink.c
-@@ -1795,27 +1795,7 @@ void netlink_detachskb(struct sock *sk,
+@@ -1812,27 +1812,7 @@ void netlink_detachskb(struct sock *sk,
static struct sk_buff *netlink_trim(struct sk_buff *skb, gfp_t allocation)
{
diff --git
a/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
b/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
index c4e1904..c86f4c7 100644
---
a/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
+++
b/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
@@ -296,7 +296,7 @@ Signed-off-by: Steven Barth
__skb_tunnel
Re: [LEDE-DEV] [PATCH] Kernel: update kernel 4.4 to version 4.4.37
Yep, I see that now... Shouldn't send stuff when I'm tired. I sent in a new one for .36 -> .38. Cheers Stijn Op za, 10 dec 2016 om 9:08 , schreef Koen Vandeputte : Hi Stijn, 2 comments about this patch: - The actual upgrade is missing (in file include/kernel-version.mk) - .38 has been released Regards, Koen On 2016-12-10 18:39, Stijn Segers wrote: Bump to .37 for all platforms supported by 4.4. All patches refreshed. Compile-tested on ar71xx, ramips/mt7621 and x86/64. Run-tested on ar71xx and ramips/mt7621. Signed-off-by: Stijn Segers --- ...tend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch index 96f20a4..c58830a 100644 --- a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch +++ b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch @@ -1,6 +1,6 @@ --- a/drivers/pci/probe.c +++ b/drivers/pci/probe.c -@@ -1938,7 +1938,8 @@ static void pcie_write_mrrs(struct pci_d +@@ -1964,7 +1964,8 @@ static void pcie_write_mrrs(struct pci_d /* In the "safe" case, do not configure the MRRS. There appear to be * issues with setting MRRS to 0 on a number of devices. */ ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [Frontpage] Stuff that cannot be found since switch to wiki software
Hi guys, I find the new frontpage to be rather messy compared to the old Jekyll setup before. It had a ton of 'quick links' up top, which may have looked a bit dense, but it did allow efficient access to crucial information for possible contributors. Someone was looking for info on how to send in patches (quite essential, if you ask me :P ) and he didn't find the info. Neither did I at first, I really had to dig and come up with this: https://lede-project.org/docs/guide-developer/the-source-code Can we get some of those old links back on the front page? Thanks! Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [Frontpage] Stuff that cannot be found since switch to wiki software
Hi Thomas, I already provided one of the links in my e-mail. Upon closer inspection, it's the only link that didn't make it. I have an old checkout here of the Jekyll frontpage, where there was a direct 'Development' link to text containing how to submit patches. It is a pity to see that buried under a generic 'Documentation' > 'Developer' > 'Submitting patches'. It took one click before, now takes three, yet it's one of the most important things for a project like this. Stuff like this should be easy to find, if people don't know their way around the homepage and only find it with a lot of digging, that means it's very well hidden. More importantly, it means they just might say 'F it'. I just saw now there's also a link in the text body of the home page, but that only adds to my point: such a link should be visible and intuitive; at this point, it is not. Thanks for considering this. Stijn P.S. Please use 'reply all' :-) Op wo, 14 dec 2016 om 12:19 , schreef Stijn Segers : Hi guys, I find the new frontpage to be rather messy compared to the old Jekyll setup before. It had a ton of 'quick links' up top, which may have looked a bit dense, but it did allow efficient access to crucial information for possible contributors. Someone was looking for info on how to send in patches (quite essential, if you ask me :P ) and he didn't find the info. Neither did I at first, I really had to dig and come up with this: https://lede-project.org/docs/guide-developer/the-source-code Can we get some of those old links back on the front page? Thanks! Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH v2] kernel: bump to 4.4.39
Hi Koen, I pulled your patch (not sure if you were talking about Stijn Tintel or me), I am getting whitespace errors: $ git apply --whitespace=fix ../patches/main/0001-Kernel-bump-to-4.4.39.patch ../patches/main/0001-Kernel-bump-to-4.4.39.patch:39: trailing whitespace. ../patches/main/0001-Kernel-bump-to-4.4.39.patch:63: trailing whitespace. ../patches/main/0001-Kernel-bump-to-4.4.39.patch:86: trailing whitespace. ../patches/main/0001-Kernel-bump-to-4.4.39.patch:106: trailing whitespace. ../patches/main/0001-Kernel-bump-to-4.4.39.patch:140: space before tab in indent. I think you'll need to fix before the patch gets accepted. Other than that: * Compile-tested on ar71xx / ramips/mt7621 / x86/64. * Run-tested on ar71xx / ramips/mt7621. Tested-by: Stijn Segers Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] can not install luci
Hi, There was a problem with opkg: https://git.lede-project.org/?p=source.git;a=commit;h=dc5f496a0df8d125ce172fc40100098b18da2300 Should be fixed now. Just a (rather transient ;-) ) patch of bad luck. Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] ppc44x: current snapshot stuck at 14 December
Buildbot logs are here: http://phase1.builds.lede-project.org/builders Last log for PPC: http://phase1.builds.lede-project.org/builders/ppc44x%2Fgeneric/builds/434 First error popping up: mv: cannot stat `arch/powerpc/boot/.addnote.tmp': No such file or directory make[5]: *** [arch/powerpc/boot/addnote] Error 1 make[4]: *** [uImage] Error 2 make[4]: *** Waiting for unfinished jobs Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] curl: vtls: s/SSLEAY/OPENSSL
Fixed an old leftover use of the USE_SSLEAY define which would make a socket get removed from the applications sockets to monitor when the multi_socket API was used, leading to timeouts. Pulled directly from upstream. Upstream curl bug: #1174 Signed-off-by: Stijn Segers --- lib/vtls/vtls.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/vtls/vtls.c b/lib/vtls/vtls.c index b808e1c..707f24b 100644 --- a/lib/vtls/vtls.c +++ b/lib/vtls/vtls.c @@ -484,7 +484,7 @@ void Curl_ssl_close_all(struct Curl_easy *data) curlssl_close_all(data); } -#if defined(USE_SSLEAY) || defined(USE_GNUTLS) || defined(USE_SCHANNEL) || \ +#if defined(USE_OPENSSL) || defined(USE_GNUTLS) || defined(USE_SCHANNEL) || \ defined(USE_DARWINSSL) || defined(USE_NSS) /* This function is for OpenSSL, GnuTLS, darwinssl, and schannel only. */ int Curl_ssl_getsock(struct connectdata *conn, curl_socket_t *socks, @@ -518,7 +518,7 @@ int Curl_ssl_getsock(struct connectdata *conn, (void)numsocks; return GETSOCK_BLANK; } -/* USE_SSLEAY || USE_GNUTLS || USE_SCHANNEL || USE_DARWINSSL || USE_NSS */ +/* USE_OPENSSL || USE_GNUTLS || USE_SCHANNEL || USE_DARWINSSL || USE_NSS */ #endif void Curl_ssl_close(struct connectdata *conn, int sockindex) ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH v2] Curl: fix HTTPS network timeouts with OpenSSL
Fixes HTTPS timeouts with OpenSSL. Upstream curl bug #1174. Upstream commit message: Fixed an old leftover use of the USE_SSLEAY define which would make a socket get removed from the applications sockets to monitor when the multi_socket API was used, leading to timeouts. Signed-off-by: Stijn Segers --- .../curl/patches/320-curl-https-openssl-fix.patch | 22 ++ 1 file changed, 22 insertions(+) create mode 100644 package/network/utils/curl/patches/320-curl-https-openssl-fix.patch diff --git a/package/network/utils/curl/patches/320-curl-https-openssl-fix.patch b/package/network/utils/curl/patches/320-curl-https-openssl-fix.patch new file mode 100644 index 00..9ecb2a95f8 --- /dev/null +++ b/package/network/utils/curl/patches/320-curl-https-openssl-fix.patch @@ -0,0 +1,22 @@ +diff --git a/lib/vtls/vtls.c b/lib/vtls/vtls.c +index b808e1c..707f24b 100644 +--- a/lib/vtls/vtls.c b/lib/vtls/vtls.c +@@ -484,7 +484,7 @@ void Curl_ssl_close_all(struct Curl_easy *data) + curlssl_close_all(data); + } + +-#if defined(USE_SSLEAY) || defined(USE_GNUTLS) || defined(USE_SCHANNEL) || \ ++#if defined(USE_OPENSSL) || defined(USE_GNUTLS) || defined(USE_SCHANNEL) || \ + defined(USE_DARWINSSL) || defined(USE_NSS) + /* This function is for OpenSSL, GnuTLS, darwinssl, and schannel only. */ + int Curl_ssl_getsock(struct connectdata *conn, curl_socket_t *socks, +@@ -518,7 +518,7 @@ int Curl_ssl_getsock(struct connectdata *conn, + (void)numsocks; + return GETSOCK_BLANK; + } +-/* USE_SSLEAY || USE_GNUTLS || USE_SCHANNEL || USE_DARWINSSL || USE_NSS */ ++/* USE_OPENSSL || USE_GNUTLS || USE_SCHANNEL || USE_DARWINSSL || USE_NSS */ + #endif + + void Curl_ssl_close(struct connectdata *conn, int sockindex) -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH v3] Curl: fix HTTPS network timeouts with OpenSSL
Hi John, I hope this works better then? Wasn't too sure about leaving in the e-mail etc. from upstream. This patch fixes HTTPS timeouts with OpenSSL. Upstream curl bug #1174. Cheers! Stijn Signed-off-by: Stijn Segers --- .../curl/patches/320-curl-https-openssl-fix.patch | 36 ++ 1 file changed, 36 insertions(+) create mode 100644 package/network/utils/curl/patches/320-curl-https-openssl-fix.patch diff --git a/package/network/utils/curl/patches/320-curl-https-openssl-fix.patch b/package/network/utils/curl/patches/320-curl-https-openssl-fix.patch new file mode 100644 index 00..259f618d46 --- /dev/null +++ b/package/network/utils/curl/patches/320-curl-https-openssl-fix.patch @@ -0,0 +1,36 @@ +From a7b38c9dc98481e4a5fc37e51a8690337c674dfb Mon Sep 17 00:00:00 2001 +From: Daniel Stenberg +Date: Mon, 26 Dec 2016 00:06:33 +0100 +Subject: [PATCH] vtls: s/SSLEAY/OPENSSL + +Fixed an old leftover use of the USE_SSLEAY define which would make a +socket get removed from the applications sockets to monitor when the +multi_socket API was used, leading to timeouts. + +Bug: #1174 +--- + lib/vtls/vtls.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/lib/vtls/vtls.c b/lib/vtls/vtls.c +index b808e1c..707f24b 100644 +--- a/lib/vtls/vtls.c b/lib/vtls/vtls.c +@@ -484,7 +484,7 @@ void Curl_ssl_close_all(struct Curl_easy *data) + curlssl_close_all(data); + } + +-#if defined(USE_SSLEAY) || defined(USE_GNUTLS) || defined(USE_SCHANNEL) || \ ++#if defined(USE_OPENSSL) || defined(USE_GNUTLS) || defined(USE_SCHANNEL) || \ + defined(USE_DARWINSSL) || defined(USE_NSS) + /* This function is for OpenSSL, GnuTLS, darwinssl, and schannel only. */ + int Curl_ssl_getsock(struct connectdata *conn, curl_socket_t *socks, +@@ -518,7 +518,7 @@ int Curl_ssl_getsock(struct connectdata *conn, + (void)numsocks; + return GETSOCK_BLANK; + } +-/* USE_SSLEAY || USE_GNUTLS || USE_SCHANNEL || USE_DARWINSSL || USE_NSS */ ++/* USE_OPENSSL || USE_GNUTLS || USE_SCHANNEL || USE_DARWINSSL || USE_NSS */ + #endif + + void Curl_ssl_close(struct connectdata *conn, int sockindex) -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] OpenWRT Quantenna radio driver for Netgear Nighthawk X4 R7500 (Tehttps://www.autistici.org/webmail/3/?_task=mail&_action=compose&_id=12641242995880cdf530713#stedon Designated Driver r49274)
Hi Patrick, Please see https://lede-project.org/docs/guide-developer/the-source-code?s[]=patch for submitting patches. I have no idea how Quantenna's licensing works - are third parties allowed to distribute it freely? Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] Kernel: bump to 4.4.44
Bump kernel to 4.4.44. Compile-tested on ar71xx, ramips/mt7621 and x86/64. .44 has been run-tested on the 17.01 branch here on ar71xx and mt7621. Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 +-- .../patches-4.4/910-unaligned_access_hacks.patch | 4 +-- .../920-usb-chipidea-AR933x-platform-support.patch | 20 +--- .../ar71xx/patches-4.4/930-chipidea-pullup.patch | 38 +- .../0111-mm-Remove-the-PFN-busy-warning.patch | 2 +- ...80-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 +++--- ...erial-imx-repair-and-complete-handshaking.patch | 16 - .../111-serial-imx-fix-polarity-of-RI.patch| 7 +--- ...let-irq-handler-return-IRQ_NONE-if-no-eve.patch | 9 ++--- ...imx-make-sure-unhandled-irqs-are-disabled.patch | 7 +--- ...mediatek-support-MTK-xHCI-host-controller.patch | 8 ++--- ...mediatek-support-MTK-xHCI-host-controller.patch | 8 ++--- ...5100_tco-Add-AMD-Mullins-platform-support.patch | 6 +--- ...5100_tco-Add-AMD-Carrizo-platform-support.patch | 6 +--- ...device-check-for-SB800-and-later-chipsets.patch | 18 -- ...5100_tco-properly-check-for-new-register-.patch | 12 +++ 16 files changed, 64 insertions(+), 111 deletions(-) diff --git a/include/kernel-version.mk b/include/kernel-version.mk index efd58e1462..199c2adb58 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -3,10 +3,10 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .43 -LINUX_VERSION-4.4 = .42 +LINUX_VERSION-4.4 = .44 LINUX_KERNEL_HASH-3.18.43 = 1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c -LINUX_KERNEL_HASH-4.4.42 = 324747568e92f203e3ee5ec8b291a868f58b870f1ad214fa64aa3507ed42e878 +LINUX_KERNEL_HASH-4.4.44 = fabdcf2703f22a5b8aa3a3407909f18fdeea610c3d0f418fdc29123ed04de748 ifdef KERNEL_PATCHVER LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER))) diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch index 21cad91161..2c014429f2 100644 --- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch +++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch @@ -491,7 +491,7 @@ memcpy(p, foc->val, foc->len); --- a/net/ipv4/igmp.c +++ b/net/ipv4/igmp.c -@@ -500,7 +500,7 @@ static struct sk_buff *add_grec(struct s +@@ -505,7 +505,7 @@ static struct sk_buff *add_grec(struct s if (!skb) return NULL; psrc = (__be32 *)skb_put(skb, sizeof(__be32)); @@ -610,7 +610,7 @@ goto next_ht; --- a/net/ipv6/ip6_offload.c +++ b/net/ipv6/ip6_offload.c -@@ -221,7 +221,7 @@ static struct sk_buff **ipv6_gro_receive +@@ -222,7 +222,7 @@ static struct sk_buff **ipv6_gro_receive continue; iph2 = (struct ipv6hdr *)(p->data + off); diff --git a/target/linux/ar71xx/patches-4.4/920-usb-chipidea-AR933x-platform-support.patch b/target/linux/ar71xx/patches-4.4/920-usb-chipidea-AR933x-platform-support.patch index 41eb7f2895..71649cacd6 100644 --- a/target/linux/ar71xx/patches-4.4/920-usb-chipidea-AR933x-platform-support.patch +++ b/target/linux/ar71xx/patches-4.4/920-usb-chipidea-AR933x-platform-support.patch @@ -1,8 +1,6 @@ -Index: linux-4.4.4/arch/mips/include/asm/mach-ath79/ar71xx_regs.h -=== linux-4.4.4.orig/arch/mips/include/asm/mach-ath79/ar71xx_regs.h 2016-03-31 21:43:10.595132564 +0300 -+++ linux-4.4.4/arch/mips/include/asm/mach-ath79/ar71xx_regs.h 2016-03-31 21:56:21.463152017 +0300 -@@ -641,6 +641,7 @@ +--- a/arch/mips/include/asm/mach-ath79/ar71xx_regs.h b/arch/mips/include/asm/mach-ath79/ar71xx_regs.h +@@ -644,6 +644,7 @@ #define AR933X_BOOTSTRAP_MDIO_GPIO_EN BIT(18) #define AR933X_BOOTSTRAP_EEPBUSY BIT(4) @@ -10,7 +8,7 @@ Index: linux-4.4.4/arch/mips/include/asm/mach-ath79/ar71xx_regs.h #define AR933X_BOOTSTRAP_REF_CLK_40 BIT(0) #define AR934X_BOOTSTRAP_SW_OPTION8 BIT(23) -@@ -670,6 +671,8 @@ +@@ -673,6 +674,8 @@ #define QCA956X_BOOTSTRAP_REF_CLK_40 BIT(2) @@ -19,10 +17,8 @@ Index: linux-4.4.4/arch/mips/include/asm/mach-ath79/ar71xx_regs.h #define AR934X_PCIE_WMAC_INT_WMAC_MISCBIT(0) #define AR934X_PCIE_WMAC_INT_WMAC_TX BIT(1) #define AR934X_PCIE_WMAC_INT_WMAC_RXLPBIT(2) -Index: linux-4.4.4/arch/mips/ath79/dev-usb.c -=== linux-4.4.4.orig/arch/mips/ath79/dev-usb.c 2016-03-31 21:43:10.407132560 +0300 -+++ linux-4.4.4/arch/mips/ath79/dev-usb.c 2016-03-31 21:43:10.707132567 +0300 +--- a/arch/mips/ath79/dev-usb.c b/arch/mips/ath79/dev-usb.c @@ -19,6 +19,9 @@ #include #include @@ -33,7 +29,7 @@ Index: linux-4.4.4/arch/mips/ath79/dev-usb.c #include #include -
[LEDE-DEV] [PATCH] Kernel: bump LEDE 17.01 kernel to 4.4.44
This bumps the 4.4 kernel for 17.01 to .44 as well.
Compile-tested on ar71xx, ramips/mt7621 and x86/64.
Run-tested on ar71xx and mt7621.
Signed-off-by: Stijn Segers
---
include/kernel-version.mk| 4 ++--
.../ar71xx/patches-4.4/910-unaligned_access_hacks.patch | 4 ++--
.../0111-mm-Remove-the-PFN-busy-warning.patch| 2 +-
.../680-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 +-
.../110-serial-imx-repair-and-complete-handshaking.patch | 16 ++--
.../patches-4.4/111-serial-imx-fix-polarity-of-RI.patch | 7 +--
...l-imx-let-irq-handler-return-IRQ_NONE-if-no-eve.patch | 9 ++---
...erial-imx-make-sure-unhandled-irqs-are-disabled.patch | 7 +--
...-xhci-mediatek-support-MTK-xHCI-host-controller.patch | 8
...-xhci-mediatek-support-MTK-xHCI-host-controller.patch | 8
10 files changed, 28 insertions(+), 47 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index efd58e1462..199c2adb58 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,10 +3,10 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .42
+LINUX_VERSION-4.4 = .44
LINUX_KERNEL_HASH-3.18.43 =
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.42 =
324747568e92f203e3ee5ec8b291a868f58b870f1ad214fa64aa3507ed42e878
+LINUX_KERNEL_HASH-4.4.44 =
fabdcf2703f22a5b8aa3a3407909f18fdeea610c3d0f418fdc29123ed04de748
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
index 21cad91161..2c014429f2 100644
--- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
+++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
@@ -491,7 +491,7 @@
memcpy(p, foc->val, foc->len);
--- a/net/ipv4/igmp.c
+++ b/net/ipv4/igmp.c
-@@ -500,7 +500,7 @@ static struct sk_buff *add_grec(struct s
+@@ -505,7 +505,7 @@ static struct sk_buff *add_grec(struct s
if (!skb)
return NULL;
psrc = (__be32 *)skb_put(skb, sizeof(__be32));
@@ -610,7 +610,7 @@
goto next_ht;
--- a/net/ipv6/ip6_offload.c
+++ b/net/ipv6/ip6_offload.c
-@@ -221,7 +221,7 @@ static struct sk_buff **ipv6_gro_receive
+@@ -222,7 +222,7 @@ static struct sk_buff **ipv6_gro_receive
continue;
iph2 = (struct ipv6hdr *)(p->data + off);
diff --git
a/target/linux/brcm2708/patches-4.4/0111-mm-Remove-the-PFN-busy-warning.patch
b/target/linux/brcm2708/patches-4.4/0111-mm-Remove-the-PFN-busy-warning.patch
index f643ec883c..a0602807ba 100644
---
a/target/linux/brcm2708/patches-4.4/0111-mm-Remove-the-PFN-busy-warning.patch
+++
b/target/linux/brcm2708/patches-4.4/0111-mm-Remove-the-PFN-busy-warning.patch
@@ -14,7 +14,7 @@ Signed-off-by: Eric Anholt
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
-@@ -6782,8 +6782,6 @@ int alloc_contig_range(unsigned long sta
+@@ -6785,8 +6785,6 @@ int alloc_contig_range(unsigned long sta
/* Make sure the range is really isolated. */
if (test_pages_isolated(outer_start, end, false)) {
diff --git
a/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
b/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
index 698d394b8c..eff8e829a6 100644
---
a/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
+++
b/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
@@ -17,7 +17,7 @@ Signed-off-by: Felix Fietkau
--- a/net/core/dev.c
+++ b/net/core/dev.c
-@@ -4222,6 +4222,9 @@ static enum gro_result dev_gro_receive(s
+@@ -4224,6 +4224,9 @@ static enum gro_result dev_gro_receive(s
enum gro_result ret;
int grow;
@@ -27,7 +27,7 @@ Signed-off-by: Felix Fietkau
if (!(skb->dev->features & NETIF_F_GRO))
goto normal;
-@@ -5381,6 +5384,48 @@ static void __netdev_adjacent_dev_unlink
+@@ -5383,6 +5386,48 @@ static void __netdev_adjacent_dev_unlink
&upper_dev->adj_list.lower);
}
@@ -76,7 +76,7 @@ Signed-off-by: Felix Fietkau
static int __netdev_upper_dev_link(struct net_device *dev,
struct net_device *upper_dev, bool master,
void *private)
-@@ -5452,6 +5497,7 @@ static int __netdev_upper_dev_link(struc
+@@ -5454,6 +5499,7 @@ static int __netdev_upper_dev_link(struc
goto rollback_lower_mesh;
}
@@ -84,7 +84,7 @@ Signed-off-by: Felix Fietkau
call_netdevice_notifiers_info(NETDEV_CHANGEUPPER, dev,
&changeupper_info.info);
Re: [LEDE-DEV] [PATCH] kernel: bump to 4.4.45
Compile-tested on master - ar71xx, ramips/mt7621, x86/64. Tested-by: Stijn Segers ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] x86: add GPIO to FEATURES so kmod-leds-apu2 gets exposed
Chris Blake's patch [1] added support for the APU2/3 LEDs and GPIOs but GPIO needs to be enabled in FEATURES for x86; since by default it is not, the kmod-leds-apu2 package will not show up in menuconfig. This patch adds GPIO support to the x86 Makefile so the kmod-leds-apu2 package gets exposed. Signed-off-by: Stijn Segers [1] http://patchwork.ozlabs.org/patch/719765/ --- target/linux/x86/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/x86/Makefile b/target/linux/x86/Makefile index f371b2ba3a..8b8e13e71d 100644 --- a/target/linux/x86/Makefile +++ b/target/linux/x86/Makefile @@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk ARCH:=i386 BOARD:=x86 BOARDNAME:=x86 -FEATURES:=squashfs ext4 vdi vmdk pcmcia targz fpu +FEATURES:=squashfs ext4 vdi vmdk pcmcia targz fpu gpio SUBTARGETS:=generic legacy geode 64 MAINTAINER:=Felix Fietkau -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] x86: add GPIO to FEATURES so kmod-leds-apu2 gets exposed
Nevermind me, I forgot to backport e3271d545d8f29f42a79d7cd5595858e67eb95e7 to 17.01... So please ignore this! Another reason not to be messing with computers past midnight >_> Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: bump to 4.4.46
Compile-tested on ar71xx, mt7621 and x86/64. Run-tested on ar71xx and mt7621. (Both on 17.01 branch). Tested-by: Stijn Segers ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] Kernel: bump LEDE 17.01 kernel to 4.4.47
Bumps kernel from .46 to .47. Compile-tested on ar71xx, ramips/mt7621 and x86/64. Run-tested on ramips/mt7621 and ar71xx. Signed-off-by: Stijn Segers --- include/kernel-version.mk | 4 ++-- .../cns3xxx/patches-4.4/200-broadcom_phy_reinit.patch | 2 +- ...w-rejecting-with-source-address-failed-policy.patch | 10 +- target/linux/ipq806x/patches-4.4/400-dsa-add-qca.patch | 2 +- ...1-sp5100_tco-Add-AMD-Mullins-platform-support.patch | 6 +- ...2-sp5100_tco-Add-AMD-Carrizo-platform-support.patch | 6 +- ...the-device-check-for-SB800-and-later-chipsets.patch | 18 +++--- ...g-sp5100_tco-properly-check-for-new-register-.patch | 12 8 files changed, 22 insertions(+), 38 deletions(-) diff --git a/include/kernel-version.mk b/include/kernel-version.mk index e06841dbad..ace1d9cce8 100644 --- a/include/kernel-version.mk +++ b/include/kernel-version.mk @@ -3,10 +3,10 @@ LINUX_RELEASE?=1 LINUX_VERSION-3.18 = .43 -LINUX_VERSION-4.4 = .46 +LINUX_VERSION-4.4 = .47 LINUX_KERNEL_HASH-3.18.43 = 1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c -LINUX_KERNEL_HASH-4.4.46 = bb944846c5901aa2cadaa20c3d953ec03ff707dc1178e6ac3851e98747872058 +LINUX_KERNEL_HASH-4.4.47 = ce0ac0016f37ba3e9bc8ad3765933b61c4072fcfe4c44804fc7b308cd7f94de7 ifdef KERNEL_PATCHVER LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER))) diff --git a/target/linux/cns3xxx/patches-4.4/200-broadcom_phy_reinit.patch b/target/linux/cns3xxx/patches-4.4/200-broadcom_phy_reinit.patch index c3f53874f9..f3ae5e6f2b 100644 --- a/target/linux/cns3xxx/patches-4.4/200-broadcom_phy_reinit.patch +++ b/target/linux/cns3xxx/patches-4.4/200-broadcom_phy_reinit.patch @@ -1,6 +1,6 @@ --- a/drivers/net/phy/broadcom.c +++ b/drivers/net/phy/broadcom.c -@@ -382,6 +382,11 @@ static int bcm5481_config_aneg(struct ph +@@ -414,6 +414,11 @@ static int bcm5481_config_aneg(struct ph /* Write bits 14:0. */ reg |= (1 << 15); phy_write(phydev, 0x18, reg); diff --git a/target/linux/generic/patches-4.4/670-ipv6-allow-rejecting-with-source-address-failed-policy.patch b/target/linux/generic/patches-4.4/670-ipv6-allow-rejecting-with-source-address-failed-policy.patch index 5e84542bf7..a82073b3e8 100644 --- a/target/linux/generic/patches-4.4/670-ipv6-allow-rejecting-with-source-address-failed-policy.patch +++ b/target/linux/generic/patches-4.4/670-ipv6-allow-rejecting-with-source-address-failed-policy.patch @@ -193,7 +193,7 @@ Signed-off-by: Jonas Gorski case -EAGAIN: rtm->rtm_type = RTN_THROW; break; -@@ -3362,6 +3399,8 @@ static int ip6_route_dev_notify(struct n +@@ -3363,6 +3400,8 @@ static int ip6_route_dev_notify(struct n #ifdef CONFIG_IPV6_MULTIPLE_TABLES net->ipv6.ip6_prohibit_entry->dst.dev = dev; net->ipv6.ip6_prohibit_entry->rt6i_idev = in6_dev_get(dev); @@ -202,7 +202,7 @@ Signed-off-by: Jonas Gorski net->ipv6.ip6_blk_hole_entry->dst.dev = dev; net->ipv6.ip6_blk_hole_entry->rt6i_idev = in6_dev_get(dev); #endif -@@ -3578,6 +3617,17 @@ static int __net_init ip6_route_net_init +@@ -3579,6 +3618,17 @@ static int __net_init ip6_route_net_init net->ipv6.ip6_blk_hole_entry->dst.ops = &net->ipv6.ip6_dst_ops; dst_init_metrics(&net->ipv6.ip6_blk_hole_entry->dst, ip6_template_metrics, true); @@ -220,7 +220,7 @@ Signed-off-by: Jonas Gorski #endif net->ipv6.sysctl.flush_delay = 0; -@@ -3596,6 +3646,8 @@ out: +@@ -3597,6 +3647,8 @@ out: return ret; #ifdef CONFIG_IPV6_MULTIPLE_TABLES @@ -229,7 +229,7 @@ Signed-off-by: Jonas Gorski out_ip6_prohibit_entry: kfree(net->ipv6.ip6_prohibit_entry); out_ip6_null_entry: -@@ -3613,6 +3665,7 @@ static void __net_exit ip6_route_net_exi +@@ -3614,6 +3666,7 @@ static void __net_exit ip6_route_net_exi #ifdef CONFIG_IPV6_MULTIPLE_TABLES kfree(net->ipv6.ip6_prohibit_entry); kfree(net->ipv6.ip6_blk_hole_entry); @@ -237,7 +237,7 @@ Signed-off-by: Jonas Gorski #endif dst_entries_destroy(&net->ipv6.ip6_dst_ops); } -@@ -3710,6 +3763,9 @@ int __init ip6_route_init(void) +@@ -3711,6 +3764,9 @@ int __init ip6_route_init(void) init_net.ipv6.ip6_prohibit_entry->rt6i_idev = in6_dev_get(init_net.loopback_dev); init_net.ipv6.ip6_blk_hole_entry->dst.dev = init_net.loopback_dev; init_net.ipv6.ip6_blk_hole_entry->rt6i_idev = in6_dev_get(init_net.loopback_dev); diff --git a/target/linux/ipq806x/patches-4.4/400-dsa-add-qca.patch b/target/linux/ipq806x/patches-4.4/400-dsa-add-qca.patch index c369ab914a..1cadba2009 100644 --- a/target/linux/ipq806x/patches-4.4/400-dsa-add-qca.patch +++ b/target/linux/ipq806x/patches-4.4/400-dsa-add-qca.patch @@ -820,7
Re: [LEDE-DEV] Help wanted with testing opkg improvements
Hi Alberto, I ran into the same,just remove the m4 patch manually before applying jow's second patch (disclaimer: I did this on a recent 17.01 tree). Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
Updates the 17.01 kernel to .51.
Compile-tested on:
* ar71xx
* ramips/mt7621
* x86/64
Run-tested on:
* ar71xx
* ramips/mt7621
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 ++--
.../901-Revert-bcma-switch-GPIO-portions-to-use-GPIOLIB_IRQC.patch| 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 21418b85bb..d88260f956 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,10 +3,10 @@
LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .50
+LINUX_VERSION-4.4 = .51
LINUX_KERNEL_HASH-3.18.43 =
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.50 =
e4944ca5bb0bdf63a7e97dc7fbdd38bcc820d8b3b57c4a3a7b3bf9c8a48216b7
+LINUX_KERNEL_HASH-4.4.51 =
ee51ad1c588608871ad25002fa6ae9623096f03b21f71530e6a2a2764be4b911
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git
a/target/linux/brcm47xx/patches-4.4/901-Revert-bcma-switch-GPIO-portions-to-use-GPIOLIB_IRQC.patch
b/target/linux/brcm47xx/patches-4.4/901-Revert-bcma-switch-GPIO-portions-to-use-GPIOLIB_IRQC.patch
index 7c2c54e338..4968c1bbac 100644
---
a/target/linux/brcm47xx/patches-4.4/901-Revert-bcma-switch-GPIO-portions-to-use-GPIOLIB_IRQC.patch
+++
b/target/linux/brcm47xx/patches-4.4/901-Revert-bcma-switch-GPIO-portions-to-use-GPIOLIB_IRQC.patch
@@ -223,7 +223,7 @@ Signed-off-by: Rafał Miłecki
}
--- a/include/linux/bcma/bcma_driver_chipcommon.h
+++ b/include/linux/bcma/bcma_driver_chipcommon.h
-@@ -649,6 +649,7 @@ struct bcma_drv_cc {
+@@ -646,6 +646,7 @@ struct bcma_drv_cc {
spinlock_t gpio_lock;
#ifdef CONFIG_BCMA_DRIVER_GPIO
struct gpio_chip gpio;
--
2.11.0
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
Hi Rafal, I talked this through with jow, a lot of targets have already dropped 4.4 support in trunk, which makes backporting 4.4 updates to 17.01 non-trivial. He was OK with me sending in a patch just for 17.01. Cheers Stijn Op do, 23 feb 2017 om 10:44 , schreef Rafał Miłecki : On 23 February 2017 at 22:35, Stijn Segers wrote: Updates the 17.01 kernel to .51. Compile-tested on: * ar71xx * ramips/mt7621 * x86/64 Run-tested on: * ar71xx * ramips/mt7621 Signed-off-by: Stijn Segers Why not the common way? Update kernel in master & cherry-pick to lede-17.01 branch? What makes this 17.01 specific? ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
please also prepare a separate patch for trunk, so we canmerge both, even if they are different patches John Hi John, Will do so this evening (CET), no access to my system from work. Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
So... I have been running on 4.4.51 on a few days now but it looks like there's some weird stuff going on on my DIR-860L... I don't know if this is merely a timeline coincidence or if it's something linked to .51 (or .50). I checked its uptime and it reported < 2h (flashed it two days ago), wifi connection periodically craps out, when I check if my desktop still has a wired connection, it shows the router doesn't respond to DHCP requests anymore either... DNS is broken as well. Restarting both dnsmasq (DHCP) and Unbound (DNS) services doesn't work, they keep hanging for some reason. I have a few traces like these in logread: Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.98] INFO: rcu_sched detected stalls on CPUs/tasks: Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.99] 3-...: (0 ticks this GP) idle=4b8/0/0 softirq=1265/1265 fqs=0 Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.00] (detected by 1, t=6004 jiffies, g=4116, c=4115, q=2999) Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.01] Task dump for CPU 3: Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.02] swapper/3 R running 0 0 1 0x0010 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] Stack : 0001 7fabc3c8 780022c0 804572a4 8040 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040675c 0001 0001 80406680 80406724 8040 8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 1100fc03 0003 87c74000 87c75ec0 8040 8005dbf8 1100fc03 0003 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040 804572a4 8005dbf0 8040 8001abd8 1100fc03 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 0004 804064a0 00a0 8001abe0 a0080040 50204041 0353017a 04405c16 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] ... Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.10] Call Trace:[<8001346c>] 0x8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.11] [<8005dbf8>] 0x8005dbf8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8005dbf0>] 0x8005dbf0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8001abd8>] 0x8001abd8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.13] [<8001abe0>] 0x8001abe0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.14] [<8021>] 0x8021 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.15] Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.15] rcu_sched kthread starved for 6019 jiffies! g4116 c4115 f0x0 s3 ->state=0x1 Any ideas what I should be looking for? Other stuff (ar71xx and x86/64 namely) are still up (uninterrupted since their last flash to a firmware with a 4.4.51 kernel) and I haven't gotten any complaints from their users. Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
Op za, 25 feb 2017 om 9:02 , schreef Stijn Segers : So... I have been running on 4.4.51 on a few days now but it looks like there's some weird stuff going on on my DIR-860L... I don't know if this is merely a timeline coincidence or if it's something linked to .51 (or .50). I checked its uptime and it reported < 2h (flashed it two days ago), wifi connection periodically craps out, when I check if my desktop still has a wired connection, it shows the router doesn't respond to DHCP requests anymore either... DNS is broken as well. Restarting both dnsmasq (DHCP) and Unbound (DNS) services doesn't work, they keep hanging for some reason. I have a few traces like these in logread: Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.98] INFO: rcu_sched detected stalls on CPUs/tasks: Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.99] 3-...: (0 ticks this GP) idle=4b8/0/0 softirq=1265/1265 fqs=0 Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.00] (detected by 1, t=6004 jiffies, g=4116, c=4115, q=2999) Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.01] Task dump for CPU 3: Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.02] swapper/3 R running 0 0 1 0x0010 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] Stack : 0001 7fabc3c8 780022c0 804572a4 8040 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040675c 0001 0001 80406680 80406724 8040 8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 1100fc03 0003 87c74000 87c75ec0 8040 8005dbf8 1100fc03 0003 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040 804572a4 8005dbf0 8040 8001abd8 1100fc03 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 0004 804064a0 00a0 8001abe0 a0080040 50204041 0353017a 04405c16 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] ... Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.10] Call Trace:[<8001346c>] 0x8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.11] [<8005dbf8>] 0x8005dbf8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8005dbf0>] 0x8005dbf0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8001abd8>] 0x8001abd8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.13] [<8001abe0>] 0x8001abe0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.14] [<8021>] 0x8021 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.15] Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.15] rcu_sched kthread starved for 6019 jiffies! g4116 c4115 f0x0 s3 ->state=0x1 Any ideas what I should be looking for? Other stuff (ar71xx and x86/64 namely) are still up (uninterrupted since their last flash to a firmware with a 4.4.51 kernel) and I haven't gotten any complaints from their users. Stijn As a follow-up, I reverted to a .49 build and that exhibits similar symptoms... Sun Feb 26 10:46:18 2017 kern.err kernel: [ 1292.42] INFO: rcu_sched detected stalls on CPUs/tasks: Sun Feb 26 10:46:18 2017 kern.err kernel: [ 1292.43] 1-...: (0 ticks this GP) idle=0be/0/0 softirq=101979/101979 fqs=0 Sun Feb 26 10:46:18 2017 kern.err kernel: [ 1292.44] (detected by 2, t=6004 jiffies, g=4716, c=4715, q=758) Sun Feb 26 10:46:18 2017 kern.info kernel: [ 1292.45] Task dump for CPU 1: Sun Feb 26 10:46:18 2017 kern.info kernel: [ 1292.46] swapper/1 R running 0 0 1 0x0010 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] Stack : 1400 0005 804572a4 8040 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] 8040675c 0001 0001 80406540 80406724 8040 8001346c Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] 0001 87c7 87c71ec0 8040 8005dbf8 1100fc03 0001 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] 8040 804572a4 8005dbf0 8040 8001abd8 1100fc03 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] 0004 804064a0 00a0 8001abe0 a0080240 50205861 03530172 04405c16 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] ... Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.54] Call Trace:[<8001346c>] 0x8001346c Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.55] [<8005dbf8>] 0x8005dbf8 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.56] [<8005dbf0>] 0x8005dbf0 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.57] [<8001abd8>] 0x8001abd8 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.57] [<8001abe0>] 0x8001abe0 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.58] Sun Feb 26 10:46:18 2017 kern.err kernel: [ 1292.58] rcu_sched kthread starved for 6018 jiffies! g4716 c4715 f0x0 s3 ->
[LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51
Okay, so I tracked it down to cake being the culprit. When I disable the Cake SQM instance, no more of those traces, and no more sudden reboots. If I can help debug this, let me know - I enabled a Cake SQM instance on an APU2 and so far that seems to run fine. So, in short: .50/51 bump is okay. Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51
Op di, 28 feb 2017 om 1:15 , schreef Eric Luehrsen : On 02/27/2017 03:17 PM, Stijn Segers wrote: Okay, so I tracked it down to cake being the culprit. When I disable the Cake SQM instance, no more of those traces, and no more sudden reboots. If I can help debug this, let me know - I enabled a Cake SQM instance on an APU2 and so far that seems to run fine. So, in short: .50/51 bump is okay. Cheers Stijn It wasn't long ago that HFSC was causing issues with 4.4. I am not sure it was all worked out. I withdrew HFSC based scripts from SQM despite being one of a few proponents otherwise. Maybe something else in the TC chain is the root cause. Maybe? Eric Dave Taht suggested I disable offloading (with ethtool -K tso off gso off gro off) to see if that changes anything, so I'll be testing that now. Cheers! Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51
Op di, 28 feb 2017 om 11:40 , schreef Martin Tippmann : On Mon, Feb 27, 2017 at 9:17 PM, Stijn Segers wrote: Okay, so I tracked it down to cake being the culprit. When I disable the Cake SQM instance, no more of those traces, and no more sudden reboots. If I can help debug this, let me know - I enabled a Cake SQM instance on an APU2 and so far that seems to run fine. cake: Maybe it's related - I'm seeing high cpu usage with cake on TP-Link 841N routers even with none, moderate traffic after a while. I don't see hanging tasks in the logs but the system feels sluggish even it's idle. filed a bug here: https://bugs.lede-project.org/index.php?do=details&task_id=563 don't have much info through. The same version is running fine on a MAC1200R with 128MB memory through. regards Martin OK... So I tried to disable offloading on the WAN interface (eth0.2 for the DIR-860L), but that throws the following error: # ethtool -K tso off gso off gro off eth0 Cannot get device feature names: No such device Same for any other devices I try... Is there a way to disable offloading without ethtool? Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51
Hi Baptiste, Thanks for your input. I found this thread [1] however which suggests offloading capabilities: "The GSW is found in all of the 1000mbit SoCs. it has 5 external ports, 1-2 cpu ports and 1 further port that the internal HW offloading engine connects to. The switch core used is a MT7530, which also exists as a standalone chip. [...]" Johh, is there a way to disable offloading on MT7530? Thanks! Stijn [1] https://lkml.org/lkml/2016/2/26/527 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51
Op wo, 1 mrt 2017 om 10:59 , schreef Sebastian Moeller : Hi Stijn, On Mar 1, 2017, at 10:46, Stijn Segers wrote: Hi Baptiste, Thanks for your input. I found this thread [1] however which suggests offloading capabilities: "The GSW is found in all of the 1000mbit SoCs. it has 5 external ports, 1-2 cpu ports and 1 further port that the internal HW offloading engine connects to. The switch core used is a MT7530, which also exists as a standalone chip. [...]" Johh, is there a way to disable offloading on MT7530? If you run “ethtool -k $IFACE” ethtool should show you which offloads the device supports and which can be toggled. Here is an example from a wndr3700v2 (eth1 being the dedicated WAN interface not connected to a switch) root@router:~# ethtool -k eth1 Features for eth1: rx-checksumming: off [fixed] tx-checksumming: off tx-checksum-ipv4: off [fixed] tx-checksum-ip-generic: off [fixed] tx-checksum-ipv6: off [fixed] tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] scatter-gather: off tx-scatter-gather: off [fixed] tx-scatter-gather-fraglist: off [fixed] tcp-segmentation-offload: off tx-tcp-segmentation: off [fixed] tx-tcp-ecn-segmentation: off [fixed] tx-tcp6-segmentation: off [fixed] udp-fragmentation-offload: off [fixed] generic-segmentation-offload: off [requested on] generic-receive-offload: on large-receive-offload: off [fixed] rx-vlan-offload: off [fixed] tx-vlan-offload: off [fixed] ntuple-filters: off [fixed] receive-hashing: off [fixed] highdma: off [fixed] rx-vlan-filter: off [fixed] vlan-challenged: off [fixed] tx-lockless: off [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: off [fixed] tx-ipip-segmentation: off [fixed] tx-sit-segmentation: off [fixed] tx-udp_tnl-segmentation: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: off loopback: off [fixed] rx-fcs: off [fixed] rx-all: off [fixed] tx-vlan-stag-hw-insert: off [fixed] rx-vlan-stag-hw-parse: off [fixed] rx-vlan-stag-filter: off [fixed] l2-fwd-offload: off [fixed] busy-poll: off [fixed] Best Regards Sebastian Thanks! Stijn [1] https://lkml.org/lkml/2016/2/26/527 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev Hi Sebastian, That does indeed return a long list, but it looks like the things that Dave Taht suggested I disable are already disabled? ethtool -K tso off gso off gro off Of those, only gso shows as tx-gso-robust [off]: fixed... # ethtool -k eth0 Features for eth0: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: on tx-checksum-ip-generic: off [fixed] tx-checksum-ipv6: on tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] scatter-gather: on tx-scatter-gather: on tx-scatter-gather-fraglist: off [fixed] tcp-segmentation-offload: on tx-tcp-segmentation: on tx-tcp-ecn-segmentation: off [fixed] tx-tcp6-segmentation: on udp-fragmentation-offload: off [fixed] generic-segmentation-offload: on generic-receive-offload: on large-receive-offload: off [fixed] rx-vlan-offload: off [fixed] tx-vlan-offload: on ntuple-filters: off [fixed] receive-hashing: off [fixed] highdma: off [fixed] rx-vlan-filter: off [fixed] vlan-challenged: off [fixed] tx-lockless: off [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: off [fixed] tx-ipip-segmentation: off [fixed] tx-sit-segmentation: off [fixed] tx-udp_tnl-segmentation: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: off loopback: off [fixed] rx-fcs: off [fixed] rx-all: off [fixed] tx-vlan-stag-hw-insert: off [fixed] rx-vlan-stag-hw-parse: off [fixed] rx-vlan-stag-filter: off [fixed] l2-fwd-offload: off [fixed] busy-poll: off [fixed] ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51
Thanks Sebastian, turned out to be a silly syntax error, I have it all disabled now. Ethtool -k and ethtool -K printing/requiring different stuff doesn't help of course :-) I re-enabled SQM, will see how that works out with the offloading disabled. Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Cake SQM killing my DIR-860L - was: [17.01] Kernel: bump to 4.4.51
Hi Dave, Dave Täht schreef op 2/3/17 13:10: On 3/2/17 11:51 AM, Stijn Segers wrote: > Thanks Sebastian, turned out to be a silly syntax error, I have it all > disabled now. Ethtool -k and ethtool -K printing/requiring different > stuff doesn't help of course :-) > > I re-enabled SQM, will see how that works out with the offloading disabled. Would be good to know. I lost a bit of sleep lately (given how badly we got bit by RCU on the ATF front, I worry about cake... but I can't see how that would break, there.) With my 50 Mbps VDSL2 downlink, I see a 25% load on one core tops. So that looks good. Checked uptime this morning, all hunky-dory. So I'll keep offloading disabled for now. Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Please help with submitting contributions
Hi Mauro, If you send your patch in with git send-email, you can track your patch here: https://patchwork.ozlabs.org/project/lede/list/ I have no idea how long you waited, if you feel it is taking too long or your patch is getting lost in the pile, you can always nudge a developer (which imho works best on IRC). If you check the list above, you'll see you're not the only one waiting for feedback (and then there's also the pull requests on Github) - so... You will need some patience, resources are a bit stretched. So... Chin up, all beginnings are difficult! Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] ath10k-firmware: move to firmware section in buildroot
This patch moves the ath10k firmware packages to the firmware submenu in the buildroot, where it belongs. Signed-off-by: Stijn Segers --- package/firmware/ath10k-firmware/Makefile | 20 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/package/firmware/ath10k-firmware/Makefile b/package/firmware/ath10k-firmware/Makefile index 624da6a..86f48d3 100644 --- a/package/firmware/ath10k-firmware/Makefile +++ b/package/firmware/ath10k-firmware/Makefile @@ -21,11 +21,9 @@ PKG_MAINTAINER:=Felix Fietkau include $(INCLUDE_DIR)/package.mk -WMENU:=Wireless Drivers - define Package/ath10k-firmware-default - SECTION:=kernel - CATEGORY:=Kernel modules + SECTION:=firmware + CATEGORY:=Firmware SUBMENU:=$(WMENU) URL:=$(PKG_SOURCE_URL) DEPENDS:= @@ -64,6 +62,8 @@ define Package/ath10k-firmware-qca988x $(Package/ath10k-firmware-default) DEFAULT:=PACKAGE_kmod-ath10k TITLE:=ath10k firmware for QCA988x devices + SECTION:=firmware + CATEGORY:=Firmware endef QCA988X_FIRMWARE_FILE:=firmware-5.bin_10.2.4.97-1 @@ -102,11 +102,15 @@ $(eval $(call Download,ath10k-firmware-qca9984-ct)) define Package/ath10k-firmware-qca99x0 $(Package/ath10k-firmware-default) TITLE:=ath10k firmware for QCA99x0 devices + SECTION:=firmware + CATEGORY:=Firmware endef define Package/ath10k-firmware-qca988x-ct $(Package/ath10k-firmware-default) TITLE:=ath10k CT 10.1 firmware for QCA988x devices + SECTION:=firmware + CATEGORY:=Firmware endef define Package/ath10k-firmware-qca988x-ct/description @@ -143,21 +147,29 @@ endef define Package/ath10k-firmware-qca99x0-ct $(Package/ath10k-firmware-default) TITLE:=ath10k CT 10.4.3 firmware for QCA99x0 devices + SECTION:=firmware + CATEGORY:=Firmware endef define Package/ath10k-firmware-qca9984-ct $(Package/ath10k-firmware-default) TITLE:=ath10k CT 10.4.3 firmware for QCA9984 devices + SECTION:=firmware + CATEGORY:=Firmware endef define Package/ath10k-firmware-qca9984 $(Package/ath10k-firmware-default) TITLE:=ath10k firmware for QCA9984 devices + SECTION:=firmware + CATEGORY:=Firmware endef define Package/ath10k-firmware-qca6174 $(Package/ath10k-firmware-default) TITLE:=ath10k firmware for QCA6174 devices + SECTION:=firmware + CATEGORY:=Firmware endef QCA99X0_BOARD_REV:=ddcec9efd245da9365c474f513a855a55f3ac7fe -- 2.1.4 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.22
Bumps 4.4 for all targets that support it.
Signed-off-by: Stijn Segers
---
.../patches-4.4/0036-bcm2708-vchiq-driver.patch | 4 ++--
.../052-02-ubifs-Implement-RENAME_WHITEOUT.patch| 17 +
.../680-NET-skip-GRO-for-foreign-MAC-addresses.patch| 2 +-
target/linux/generic/patches-4.4/721-phy_packets.patch | 8
.../linux/generic/patches-4.4/835-misc-owl_loader.patch | 10 +-
.../linux/generic/patches-4.4/904-debloat_dma_buf.patch | 2 +-
...xhci-mediatek-support-MTK-xHCI-host-controller.patch | 4 ++--
.../996-ATAG_DTB_COMPAT_CMDLINE_MANGLE.patch| 2 +-
...xhci-mediatek-support-MTK-xHCI-host-controller.patch | 4 ++--
.../ramips/patches-4.4/0200-linkit_bootstrap.patch | 2 +-
10 files changed, 28 insertions(+), 27 deletions(-)
diff --git a/target/linux/brcm2708/patches-4.4/0036-bcm2708-vchiq-driver.patch
b/target/linux/brcm2708/patches-4.4/0036-bcm2708-vchiq-driver.patch
index 5086521..02929f1 100644
--- a/target/linux/brcm2708/patches-4.4/0036-bcm2708-vchiq-driver.patch
+++ b/target/linux/brcm2708/patches-4.4/0036-bcm2708-vchiq-driver.patch
@@ -268,7 +268,7 @@ vchiq: hack: Add include depecated dma include file
* Watchdog
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
-@@ -533,6 +533,7 @@ source "drivers/misc/lis3lv02d/Kconfig"
+@@ -545,6 +545,7 @@ source "drivers/misc/lis3lv02d/Kconfig"
source "drivers/misc/altera-stapl/Kconfig"
source "drivers/misc/mei/Kconfig"
source "drivers/misc/vmw_vmci/Kconfig"
@@ -278,7 +278,7 @@ vchiq: hack: Add include depecated dma include file
source "drivers/misc/echo/Kconfig"
--- a/drivers/misc/Makefile
+++ b/drivers/misc/Makefile
-@@ -51,6 +51,7 @@ obj-$(CONFIG_INTEL_MEI) += mei/
+@@ -52,6 +52,7 @@ obj-$(CONFIG_INTEL_MEI) += mei/
obj-$(CONFIG_VMWARE_VMCI) += vmw_vmci/
obj-$(CONFIG_LATTICE_ECP3_CONFIG) += lattice-ecp3-config.o
obj-$(CONFIG_SRAM)+= sram.o
diff --git
a/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
b/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
index 9abb923..dd75ef4 100644
---
a/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
+++
b/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
@@ -292,30 +292,31 @@ Signed-off-by: Richard Weinberger
- err = ubifs_add_dirt(c, lnum, dlen2);
- if (err)
- goto out_ro;
+-
+- dent_key_init(c, &key, old_dir->i_ino, &old_dentry->d_name);
+- err = ubifs_tnc_remove_nm(c, &key, &old_dentry->d_name);
+- if (err)
+- goto out_ro;
+ offs += aligned_dlen1;
+ if (whiteout) {
+ dent_key_init(c, &key, old_dir->i_ino, &old_dentry->d_name);
+ err = ubifs_tnc_add_nm(c, &key, lnum, offs, dlen2,
&old_dentry->d_name);
+ if (err)
+ goto out_ro;
-
-- dent_key_init(c, &key, old_dir->i_ino, &old_dentry->d_name);
-- err = ubifs_tnc_remove_nm(c, &key, &old_dentry->d_name);
-- if (err)
-- goto out_ro;
++
+ ubifs_delete_orphan(c, whiteout->i_ino);
+ } else {
+ err = ubifs_add_dirt(c, lnum, dlen2);
+ if (err)
+ goto out_ro;
-
-- offs += aligned_dlen1 + aligned_dlen2;
++
+ dent_key_init(c, &key, old_dir->i_ino, &old_dentry->d_name);
+ err = ubifs_tnc_remove_nm(c, &key, &old_dentry->d_name);
+ if (err)
+ goto out_ro;
+ }
-+
+
+- offs += aligned_dlen1 + aligned_dlen2;
+ offs += aligned_dlen2;
if (new_inode) {
ino_key_init(c, &key, new_inode->i_ino);
diff --git
a/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
b/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
index a658bfe..cbd1a08 100644
---
a/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
+++
b/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
@@ -102,7 +102,7 @@ Signed-off-by: Felix Fietkau
return 0;
--- a/include/linux/netdevice.h
+++ b/include/linux/netdevice.h
-@@ -1638,6 +1638,8 @@ struct net_device {
+@@ -1637,6 +1637,8 @@ struct net_device {
struct netdev_hw_addr_list mc;
struct netdev_hw_addr_list dev_addrs;
diff --git a/target/linux/generic/patches-4.4/721-phy_packets.patch
b/target/linux/generic/patches-4.4/721-phy_packets.patch
index c3fbb95..7f288f8 100644
--- a/target/linux/generic/patches-4.4/721-phy_packets.patch
+++ b/target/linux/generic/patches-4.4/721-phy_packets.patch
@@ -1,6 +1,6 @@
--- a/include/linux/netdevice.h
+++ b
[LEDE-DEV] [PATCH v2] kernel: update kernel 4.4 to version 4.4.22
Forgot to update kernel-version.mk, so updated patch. Compile-tested on x86/64
and ar71xx; run-tested on x86/64 and ar71xx.
Signed-off-by: Stijn Segers
---
include/kernel-version.mk | 4 ++--
.../patches-4.4/0036-bcm2708-vchiq-driver.patch | 4 ++--
.../052-02-ubifs-Implement-RENAME_WHITEOUT.patch| 17 +
.../680-NET-skip-GRO-for-foreign-MAC-addresses.patch| 2 +-
target/linux/generic/patches-4.4/721-phy_packets.patch | 8
.../linux/generic/patches-4.4/835-misc-owl_loader.patch | 10 +-
.../linux/generic/patches-4.4/904-debloat_dma_buf.patch | 2 +-
...xhci-mediatek-support-MTK-xHCI-host-controller.patch | 4 ++--
.../996-ATAG_DTB_COMPAT_CMDLINE_MANGLE.patch| 2 +-
...xhci-mediatek-support-MTK-xHCI-host-controller.patch | 4 ++--
.../ramips/patches-4.4/0200-linkit_bootstrap.patch | 2 +-
11 files changed, 30 insertions(+), 29 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index d1f5eb2..0db1b35 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -4,11 +4,11 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .29
LINUX_VERSION-4.1 = .20
-LINUX_VERSION-4.4 = .21
+LINUX_VERSION-4.4 = .22
LINUX_KERNEL_MD5SUM-3.18.29 = b25737a0bc98e80d12200de93f239c28
LINUX_KERNEL_MD5SUM-4.1.20 = 075c38a3a23ca5bc80437b13606df00a
-LINUX_KERNEL_MD5SUM-4.4.21 = 9a59fa5f60f47aab78aaa5f0691b24a2
+LINUX_KERNEL_MD5SUM-4.4.22 = 404802389c7f0bbe94dda95f9d058d9e
ifdef KERNEL_PATCHVER
LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git a/target/linux/brcm2708/patches-4.4/0036-bcm2708-vchiq-driver.patch
b/target/linux/brcm2708/patches-4.4/0036-bcm2708-vchiq-driver.patch
index 5086521..02929f1 100644
--- a/target/linux/brcm2708/patches-4.4/0036-bcm2708-vchiq-driver.patch
+++ b/target/linux/brcm2708/patches-4.4/0036-bcm2708-vchiq-driver.patch
@@ -268,7 +268,7 @@ vchiq: hack: Add include depecated dma include file
* Watchdog
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
-@@ -533,6 +533,7 @@ source "drivers/misc/lis3lv02d/Kconfig"
+@@ -545,6 +545,7 @@ source "drivers/misc/lis3lv02d/Kconfig"
source "drivers/misc/altera-stapl/Kconfig"
source "drivers/misc/mei/Kconfig"
source "drivers/misc/vmw_vmci/Kconfig"
@@ -278,7 +278,7 @@ vchiq: hack: Add include depecated dma include file
source "drivers/misc/echo/Kconfig"
--- a/drivers/misc/Makefile
+++ b/drivers/misc/Makefile
-@@ -51,6 +51,7 @@ obj-$(CONFIG_INTEL_MEI) += mei/
+@@ -52,6 +52,7 @@ obj-$(CONFIG_INTEL_MEI) += mei/
obj-$(CONFIG_VMWARE_VMCI) += vmw_vmci/
obj-$(CONFIG_LATTICE_ECP3_CONFIG) += lattice-ecp3-config.o
obj-$(CONFIG_SRAM)+= sram.o
diff --git
a/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
b/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
index 9abb923..dd75ef4 100644
---
a/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
+++
b/target/linux/generic/patches-4.4/052-02-ubifs-Implement-RENAME_WHITEOUT.patch
@@ -292,30 +292,31 @@ Signed-off-by: Richard Weinberger
- err = ubifs_add_dirt(c, lnum, dlen2);
- if (err)
- goto out_ro;
+-
+- dent_key_init(c, &key, old_dir->i_ino, &old_dentry->d_name);
+- err = ubifs_tnc_remove_nm(c, &key, &old_dentry->d_name);
+- if (err)
+- goto out_ro;
+ offs += aligned_dlen1;
+ if (whiteout) {
+ dent_key_init(c, &key, old_dir->i_ino, &old_dentry->d_name);
+ err = ubifs_tnc_add_nm(c, &key, lnum, offs, dlen2,
&old_dentry->d_name);
+ if (err)
+ goto out_ro;
-
-- dent_key_init(c, &key, old_dir->i_ino, &old_dentry->d_name);
-- err = ubifs_tnc_remove_nm(c, &key, &old_dentry->d_name);
-- if (err)
-- goto out_ro;
++
+ ubifs_delete_orphan(c, whiteout->i_ino);
+ } else {
+ err = ubifs_add_dirt(c, lnum, dlen2);
+ if (err)
+ goto out_ro;
-
-- offs += aligned_dlen1 + aligned_dlen2;
++
+ dent_key_init(c, &key, old_dir->i_ino, &old_dentry->d_name);
+ err = ubifs_tnc_remove_nm(c, &key, &old_dentry->d_name);
+ if (err)
+ goto out_ro;
+ }
-+
+
+- offs += aligned_dlen1 + aligned_dlen2;
+ offs += aligned_dlen2;
if (new_inode) {
ino_key_init(c, &key, new_inode->i_ino);
diff --git
a/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
b/target/linux/generic/patches-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
index a658bfe..cbd1a08 100644
---
a/target/linux/gene
Re: [LEDE-DEV] [PATCH v2 5/6] x86: add intel microcode entries to grub config
Op do, 19 apr 2018 om 11:47 , schreef Tomasz Maciej Nowak
:
W dniu 18.04.2018 o 00:51, Philip Prindeville pisze:
> Is there a downside to forcing AMD to also do early firmware
updates?
AFAIK there shouldn't be any for either methods regarding AMD. I made
also a prototype for AMD, but as there are no downsides for current
method and I don't have any hardware to test it, it's being left out.
Hi Tomasz,
I have an AMD system I can test on, so if you can provide a 'generic'
patch, I'd be happy to try it.
Cheers
Stijn
>
>
>
>> On Apr 17, 2018, at 12:50 PM, Tomasz Maciej Nowak
wrote:
>>
>> Create initrd enries for x86 images, that'll load intel microcode
as
>> early as possible. Also restrict the late load of microcode to AMD
>> processors.
>>
>> Signed-off-by: Tomasz Maciej Nowak
>> ---
>> target/linux/x86/base-files/lib/preinit/02_load_x86_ucode | 6
--
>> target/linux/x86/image/Makefile | 4 ++--
>> target/linux/x86/image/grub-iso.cfg | 3 +++
>> target/linux/x86/image/grub.cfg | 3 +++
>> 4 files changed, 12 insertions(+), 4 deletions(-)
>>
>> diff --git
a/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
b/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
>> index fb309c75c1..d3a23e24b2 100644
>> --- a/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
>> +++ b/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
>> @@ -2,8 +2,10 @@
>> # Copyright (C) 2018 OpenWrt.org
>>
>> do_load_x86_ucode() {
>> - if [ -e "/sys/devices/system/cpu/microcode/reload" ]; then
>> - echo 1 > /sys/devices/system/cpu/microcode/reload
>> + if grep -q AuthenticAMD /proc/cpuinfo; then
>> + if [ -e "/sys/devices/system/cpu/microcode/reload" ]; then
>> + echo 1 > /sys/devices/system/cpu/microcode/reload
>> + fi
>>fi
>> }
>>
>> diff --git a/target/linux/x86/image/Makefile
b/target/linux/x86/image/Makefile
>> index cf1e1a9edf..523c07eb75 100644
>> --- a/target/linux/x86/image/Makefile
>> +++ b/target/linux/x86/image/Makefile
>> @@ -9,8 +9,8 @@ include $(INCLUDE_DIR)/image.mk
>>
>> export PATH=$(TARGET_PATH):/sbin
>>
>> -GRUB2_MODULES = biosdisk boot chain configfile ext2 linux ls
part_msdos reboot serial vga
>> -GRUB2_MODULES_ISO = biosdisk boot chain configfile iso9660 linux
ls part_msdos reboot serial vga
>> +GRUB2_MODULES = biosdisk boot chain configfile ext2 linux ls
part_msdos reboot serial test vga
>> +GRUB2_MODULES_ISO = biosdisk boot chain configfile iso9660 linux
ls part_msdos reboot serial test vga
>> GRUB_TERMINALS =
>> GRUB_SERIAL_CONFIG =
>> GRUB_TERMINAL_CONFIG =
>> diff --git a/target/linux/x86/image/grub-iso.cfg
b/target/linux/x86/image/grub-iso.cfg
>> index 3d47a95a4b..30b587bd1c 100644
>> --- a/target/linux/x86/image/grub-iso.cfg
>> +++ b/target/linux/x86/image/grub-iso.cfg
>> @@ -7,4 +7,7 @@ set root='(cd)'
>>
>> menuentry "OpenWrt" {
>>linux /boot/vmlinuz @CMDLINE@ noinitrd
>> + if [ -e /boot/intel-ucode.img ]; then
>> + initrd /boot/intel-ucode.img
>> + fi
>> }
>> diff --git a/target/linux/x86/image/grub.cfg
b/target/linux/x86/image/grub.cfg
>> index 9ec6b2d39c..dde24b95ce 100644
>> --- a/target/linux/x86/image/grub.cfg
>> +++ b/target/linux/x86/image/grub.cfg
>> @@ -7,6 +7,9 @@ set root='(@ROOT@)'
>>
>> menuentry "OpenWrt" {
>>linux /boot/vmlinuz @CMDLINE@ noinitrd
>> + if [ -e /boot/intel-ucode.img ]; then
>> + initrd /boot/intel-ucode.img
>> + fi
>> }
>> menuentry "OpenWrt (failsafe)" {
>>linux /boot/vmlinuz failsafe=true @CMDLINE@ noinitrd
>> --
>> 2.17.0
>>
>
>
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
>
--
TMN
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH 1/2] x86: add amd microcode entries to grub config
Hi Tomasz,
Op di, 24 apr 2018 om 2:56 , schreef Tomasz Maciej Nowak
:
Create initrd enries for x86 images, that'll load amd microcode as
early
as possible. Also remove the preinit script responsible for late load
of
microcode.
Signed-off-by: Tomasz Maciej Nowak
---
.../x86/base-files/lib/preinit/02_load_x86_ucode | 12
target/linux/x86/image/grub-iso.cfg | 3 +++
target/linux/x86/image/grub.cfg | 3 +++
3 files changed, 6 insertions(+), 12 deletions(-)
delete mode 100644
target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
I'm not sure what's going wrong here, I'm on a clean master tree but
your first patch does not apply:
$ git am 1.patch
Applying: x86: add amd microcode entries to grub config
error: patch failed:
target/linux/x86/base-files/lib/preinit/02_load_x86_ucode:1
error: target/linux/x86/base-files/lib/preinit/02_load_x86_ucode: patch
does not apply
error: patch failed: target/linux/x86/image/grub-iso.cfg:10
error: target/linux/x86/image/grub-iso.cfg: patch does not apply
error: patch failed: target/linux/x86/image/grub.cfg:10
error: target/linux/x86/image/grub.cfg: patch does not apply
Patch failed at 0001 x86: add amd microcode entries to grub config
$ ./scripts/getver.sh
r6755-d089a5d773
Second does apply cleanly.
Cheers
Stijn
diff --git
a/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
b/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
deleted file mode 100644
index d3a23e24b2..00
--- a/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
+++ /dev/null
@@ -1,12 +0,0 @@
-#!/bin/sh
-# Copyright (C) 2018 OpenWrt.org
-
-do_load_x86_ucode() {
- if grep -q AuthenticAMD /proc/cpuinfo; then
- if [ -e "/sys/devices/system/cpu/microcode/reload" ]; then
- echo 1 > /sys/devices/system/cpu/microcode/reload
- fi
- fi
-}
-
-boot_hook_add preinit_main do_load_x86_ucode
diff --git a/target/linux/x86/image/grub-iso.cfg
b/target/linux/x86/image/grub-iso.cfg
index 30b587bd1c..5a2d67b7b3 100644
--- a/target/linux/x86/image/grub-iso.cfg
+++ b/target/linux/x86/image/grub-iso.cfg
@@ -10,4 +10,7 @@ menuentry "OpenWrt" {
if [ -e /boot/intel-ucode.img ]; then
initrd /boot/intel-ucode.img
fi
+ if [ -e /boot/amd-ucode.img ]; then
+ initrd /boot/amd-ucode.img
+ fi
}
diff --git a/target/linux/x86/image/grub.cfg
b/target/linux/x86/image/grub.cfg
index dde24b95ce..caf38ec2c4 100644
--- a/target/linux/x86/image/grub.cfg
+++ b/target/linux/x86/image/grub.cfg
@@ -10,6 +10,9 @@ menuentry "OpenWrt" {
if [ -e /boot/intel-ucode.img ]; then
initrd /boot/intel-ucode.img
fi
+ if [ -e /boot/amd-ucode.img ]; then
+ initrd /boot/amd-ucode.img
+ fi
}
menuentry "OpenWrt (failsafe)" {
linux /boot/vmlinuz failsafe=true @CMDLINE@ noinitrd
--
2.17.0
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: bump 4.14 to 4.14.36
Compile-tested on: ramips/mt7621, x86/64.
Run-tested on: ramips/mt7621, x86/64.
Op di, 24 apr 2018 om 4:59 , schreef Koen Vandeputte
:
Refreshed all patches.
Compile-tested on: cns3xxx, imx6
Runtime-tested on: cns3xxx, imx6
Fixes for CVEs:
CVE-2018-1108
CVE-2018-1092
CVE-2018-1094
CVE-2018-1095
Signed-off-by: Koen Vandeputte
Tested-by: Stijn Segers
---
Note:
Requires the patch from Kevin D-B (kernel: bump 4.9 to 4.9.96) first
to avoid conflicts in kernel-version.h
include/kernel-version.mk | 4
++--
target/linux/cns3xxx/patches-4.14/075-spi_support.patch| 2
+-
...-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch | 4
++--
.../400-mtd-ubi-add-quirk-to-autoload-ubi-on-rt-ac58u.patch| 2
+-
.../patches-4.14/0006-reset-mediatek-mt2701-reset-driver.patch | 2
+-
target/linux/mediatek/patches-4.14/0064-dts.patch | 10
+-
6 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 9191bddc7d00..8d0a62347cbf 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -5,12 +5,12 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
LINUX_VERSION-4.4 = .121
LINUX_VERSION-4.9 = .96
-LINUX_VERSION-4.14 = .34
+LINUX_VERSION-4.14 = .36
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
LINUX_KERNEL_HASH-4.4.121 =
44a88268b5088dc326b30c9b9133ac35a9a200b636b7268d08f32abeae6ca729
LINUX_KERNEL_HASH-4.9.96 =
826f596eb5197f8b17304649c2990dd7b766f5c79076cae79f4261c40cea877f
-LINUX_KERNEL_HASH-4.14.34 =
782b6c4c85275c382c820e1934d3e6003ef468f43cfc5e7c22bc07c331a12bb9
+LINUX_KERNEL_HASH-4.14.36 =
cae24404d7b5812a331cbbc430b3ab75ca0f76eb16803528cbffbc42e768bc43
remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst
https://,,$(1
sanitize_uri=$(call qstrip,$(subst @,_,$(subst :,_,$(subst
.,_,$(subst -,_,$(subst /,_,$(1)))
diff --git a/target/linux/cns3xxx/patches-4.14/075-spi_support.patch
b/target/linux/cns3xxx/patches-4.14/075-spi_support.patch
index 8a51eb396b47..e38dbdb75e10 100644
--- a/target/linux/cns3xxx/patches-4.14/075-spi_support.patch
+++ b/target/linux/cns3xxx/patches-4.14/075-spi_support.patch
@@ -39,7 +39,7 @@
/**
--- a/drivers/spi/spi.c
+++ b/drivers/spi/spi.c
-@@ -1021,6 +1021,9 @@ static int spi_transfer_one_message(stru
+@@ -1027,6 +1027,9 @@ static int spi_transfer_one_message(stru
list_for_each_entry(xfer, &msg->transfers, transfer_list) {
trace_spi_transfer_start(msg, xfer);
diff --git
a/target/linux/generic/pending-4.14/490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch
b/target/linux/generic/pending-4.14/490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch
index 180d1407d24f..2a09caf44254 100644
---
a/target/linux/generic/pending-4.14/490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch
+++
b/target/linux/generic/pending-4.14/490-ubi-auto-attach-mtd-device-named-ubi-or-data-on-boot.patch
@@ -8,7 +8,7 @@ Signed-off-by: Daniel Golle
--- a/drivers/mtd/ubi/build.c
+++ b/drivers/mtd/ubi/build.c
-@@ -1157,6 +1157,49 @@ static struct mtd_info * __init open_mtd
+@@ -1168,6 +1168,49 @@ static struct mtd_info * __init open_mtd
return mtd;
}
@@ -58,7 +58,7 @@ Signed-off-by: Daniel Golle
static int __init ubi_init(void)
{
int err, i, k;
-@@ -1240,6 +1283,12 @@ static int __init ubi_init(void)
+@@ -1251,6 +1294,12 @@ static int __init ubi_init(void)
}
}
diff --git
a/target/linux/ipq40xx/patches-4.14/400-mtd-ubi-add-quirk-to-autoload-ubi-on-rt-ac58u.patch
b/target/linux/ipq40xx/patches-4.14/400-mtd-ubi-add-quirk-to-autoload-ubi-on-rt-ac58u.patch
index 86cb454619da..8a9da2c08813 100644
---
a/target/linux/ipq40xx/patches-4.14/400-mtd-ubi-add-quirk-to-autoload-ubi-on-rt-ac58u.patch
+++
b/target/linux/ipq40xx/patches-4.14/400-mtd-ubi-add-quirk-to-autoload-ubi-on-rt-ac58u.patch
@@ -17,7 +17,7 @@ Signed-off-by: Christian Lamparter
--- a/drivers/mtd/ubi/build.c
+++ b/drivers/mtd/ubi/build.c
-@@ -1170,6 +1170,9 @@ static void __init ubi_auto_attach(void)
+@@ -1181,6 +1181,9 @@ static void __init ubi_auto_attach(void)
mtd = open_mtd_device("ubi");
if (IS_ERR(mtd))
mtd = open_mtd_device("data");
diff --git
a/target/linux/mediatek/patches-4.14/0006-reset-mediatek-mt2701-reset-driver.patch
b/target/linux/mediatek/patches-4.14/0006-reset-mediatek-mt2701-reset-driver.patch
index a0fdc14f782c..a443adfe6486 100644
---
a/target/linux/mediatek/patches-4.14/0006-reset-mediatek-mt2701-reset-driver.patch
+++
b/target/linux/mediatek/patches-4.14/0006-reset-mediatek-mt2701-reset-driver.patch
@@ -16,7 +16,7 @@ Acked-by: Philipp Zabel
--- a/drivers/clk/mediatek/clk-mt2701.c
+++ b/drivers/clk/mediatek/clk-mt2701.c
-@@ -771,6 +771,8 @@ static void mtk_infrasys_init_early(stru
+@@ -
Re: [LEDE-DEV] [PATCH 1/2] x86: add amd microcode entries to grub config
Op di, 24 apr 2018 om 9:14 , schreef Tomasz Maciej Nowak
:
W dniu 24.04.2018 o 21:03, Stijn Segers pisze:
Hi Tomasz,
Op di, 24 apr 2018 om 2:56 , schreef Tomasz Maciej Nowak
:
Create initrd enries for x86 images, that'll load amd microcode as
early
as possible. Also remove the preinit script responsible for late
load of
microcode.
Signed-off-by: Tomasz Maciej Nowak
---
.../x86/base-files/lib/preinit/02_load_x86_ucode | 12
target/linux/x86/image/grub-iso.cfg | 3 +++
target/linux/x86/image/grub.cfg | 3 +++
3 files changed, 6 insertions(+), 12 deletions(-)
delete mode 100644
target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
I'm not sure what's going wrong here, I'm on a clean master tree
but your first patch does not apply:
$ git am 1.patch
Applying: x86: add amd microcode entries to grub config
error: patch failed:
target/linux/x86/base-files/lib/preinit/02_load_x86_ucode:1
error: target/linux/x86/base-files/lib/preinit/02_load_x86_ucode:
patch does not apply
error: patch failed: target/linux/x86/image/grub-iso.cfg:10
error: target/linux/x86/image/grub-iso.cfg: patch does not apply
error: patch failed: target/linux/x86/image/grub.cfg:10
error: target/linux/x86/image/grub.cfg: patch does not apply
Patch failed at 0001 x86: add amd microcode entries to grub config
$ ./scripts/getver.sh
r6755-d089a5d773
Hi.
I did wrongly spell myself out instead of "This series needs to be
applied on top of 'intel-microcode: load as early as possible'
series." it should be: "This series needs to be applied after
'intel-microcode: load as early as possible' series.". Sorry about it.
Nope - turns out I was too quick, my apologies :-(. I merely looked at
your first mail that actually had a patch for AMD and not at the one
preceding it (which stated I needed to apply the Intel series first).
Applied cleanly. How do I check whether it's functional? I grepped
dmesg for AMD or ucode, but nothing shows. Logread doesn't work at all
(but I reckon that's unrelated).
Dmesg does say full retpoline support has been enabled, but unless I'm
mistaken that was a compiler feature, not something that could be
solved with microcode alone?
Cheers
Stijn
Second does apply cleanly.
Cheers
Stijn
diff --git
a/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
b/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
deleted file mode 100644
index d3a23e24b2..00
--- a/target/linux/x86/base-files/lib/preinit/02_load_x86_ucode
+++ /dev/null
@@ -1,12 +0,0 @@
-#!/bin/sh
-# Copyright (C) 2018 OpenWrt.org
-
-do_load_x86_ucode() {
-if grep -q AuthenticAMD /proc/cpuinfo; then
-if [ -e "/sys/devices/system/cpu/microcode/reload" ]; then
-echo 1 > /sys/devices/system/cpu/microcode/reload
-fi
-fi
-}
-
-boot_hook_add preinit_main do_load_x86_ucode
diff --git a/target/linux/x86/image/grub-iso.cfg
b/target/linux/x86/image/grub-iso.cfg
index 30b587bd1c..5a2d67b7b3 100644
--- a/target/linux/x86/image/grub-iso.cfg
+++ b/target/linux/x86/image/grub-iso.cfg
@@ -10,4 +10,7 @@ menuentry "OpenWrt" {
if [ -e /boot/intel-ucode.img ]; then
initrd /boot/intel-ucode.img
fi
+if [ -e /boot/amd-ucode.img ]; then
+initrd /boot/amd-ucode.img
+fi
}
diff --git a/target/linux/x86/image/grub.cfg
b/target/linux/x86/image/grub.cfg
index dde24b95ce..caf38ec2c4 100644
--- a/target/linux/x86/image/grub.cfg
+++ b/target/linux/x86/image/grub.cfg
@@ -10,6 +10,9 @@ menuentry "OpenWrt" {
if [ -e /boot/intel-ucode.img ]; then
initrd /boot/intel-ucode.img
fi
+if [ -e /boot/amd-ucode.img ]; then
+initrd /boot/amd-ucode.img
+fi
}
menuentry "OpenWrt (failsafe)" {
linux /boot/vmlinuz failsafe=true @CMDLINE@ noinitrd
--
2.17.0
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
--
TMN
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] kernel: bump 4.14 to 4.14.37
Op do, 26 apr 2018 om 6:20 , schreef Koen Vandeputte
:
Refreshed all patches
Compile-tested on: cns3xxx, imx6
Runtime-tested on: cns3xxx, imx6
Compile-tested on: ramips/mt7621, x86/64
Run-tested on: ramips/mt7621, x86/64
Signed-off-by: Koen Vandeputte
Tested-by: Stijn Segers
---
include/kernel-version.mk
| 4 ++--
.../backport-4.14/336-netfilter-exit_net-cleanup-check-added.patch
| 2 +-
.../pending-4.14/610-netfilter_match_bypass_default_checks.patch
| 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 8d0a62347cbf..cf84e31f7b0f 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -5,12 +5,12 @@ LINUX_RELEASE?=1
LINUX_VERSION-3.18 = .71
LINUX_VERSION-4.4 = .121
LINUX_VERSION-4.9 = .96
-LINUX_VERSION-4.14 = .36
+LINUX_VERSION-4.14 = .37
LINUX_KERNEL_HASH-3.18.71 =
5abc9778ad44ce02ed6c8ab52ece8a21c6d20d21f6ed8a19287b4a38a50c1240
LINUX_KERNEL_HASH-4.4.121 =
44a88268b5088dc326b30c9b9133ac35a9a200b636b7268d08f32abeae6ca729
LINUX_KERNEL_HASH-4.9.96 =
826f596eb5197f8b17304649c2990dd7b766f5c79076cae79f4261c40cea877f
-LINUX_KERNEL_HASH-4.14.36 =
cae24404d7b5812a331cbbc430b3ab75ca0f76eb16803528cbffbc42e768bc43
+LINUX_KERNEL_HASH-4.14.37 =
8197e7ed3620713e412905430a7bf93e2048384042ffba189a66f0eeb6908e92
remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst
https://,,$(1
sanitize_uri=$(call qstrip,$(subst @,_,$(subst :,_,$(subst
.,_,$(subst -,_,$(subst /,_,$(1)))
diff --git
a/target/linux/generic/backport-4.14/336-netfilter-exit_net-cleanup-check-added.patch
b/target/linux/generic/backport-4.14/336-netfilter-exit_net-cleanup-check-added.patch
index 92d7942d8684..d930751d415f 100644
---
a/target/linux/generic/backport-4.14/336-netfilter-exit_net-cleanup-check-added.patch
+++
b/target/linux/generic/backport-4.14/336-netfilter-exit_net-cleanup-check-added.patch
@@ -80,7 +80,7 @@ Signed-off-by: Pablo Neira Ayuso
static void nfnl_queue_net_exit_batch(struct list_head
*net_exit_list)
--- a/net/netfilter/x_tables.c
+++ b/net/netfilter/x_tables.c
-@@ -1754,8 +1754,17 @@ static int __net_init xt_net_init(struct
+@@ -1785,8 +1785,17 @@ static int __net_init xt_net_init(struct
return 0;
}
diff --git
a/target/linux/generic/pending-4.14/610-netfilter_match_bypass_default_checks.patch
b/target/linux/generic/pending-4.14/610-netfilter_match_bypass_default_checks.patch
index ec269b6cd880..36118796094d 100644
---
a/target/linux/generic/pending-4.14/610-netfilter_match_bypass_default_checks.patch
+++
b/target/linux/generic/pending-4.14/610-netfilter_match_bypass_default_checks.patch
@@ -91,7 +91,7 @@ Signed-off-by: Felix Fietkau
for (i = sizeof(struct ipt_entry);
i < e->target_offset;
i += m->u.match_size) {
-@@ -1224,12 +1261,15 @@ compat_copy_entry_to_user(struct ipt_ent
+@@ -1226,12 +1263,15 @@ compat_copy_entry_to_user(struct ipt_ent
compat_uint_t origsize;
const struct xt_entry_match *ematch;
int ret = 0;
--
2.7.4
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH 1/2] x86: add amd microcode entries to grub config
Op di, 24 apr 2018 om 10:18 , schreef Tomasz Maciej Nowak : W dniu 24.04.2018 o 22:00, Stijn Segers pisze: [snip] I'm not sure what's going wrong here, I'm on a clean master tree but your first patch does not apply: $ git am 1.patch Applying: x86: add amd microcode entries to grub config error: patch failed: target/linux/x86/base-files/lib/preinit/02_load_x86_ucode:1 error: target/linux/x86/base-files/lib/preinit/02_load_x86_ucode: patch does not apply error: patch failed: target/linux/x86/image/grub-iso.cfg:10 error: target/linux/x86/image/grub-iso.cfg: patch does not apply error: patch failed: target/linux/x86/image/grub.cfg:10 error: target/linux/x86/image/grub.cfg: patch does not apply Patch failed at 0001 x86: add amd microcode entries to grub config $ ./scripts/getver.sh r6755-d089a5d773 Hi. I did wrongly spell myself out instead of "This series needs to be applied on top of 'intel-microcode: load as early as possible' series." it should be: "This series needs to be applied after 'intel-microcode: load as early as possible' series.". Sorry about it. Nope - turns out I was too quick, my apologies :-(. I merely looked at your first mail that actually had a patch for AMD and not at the one preceding it (which stated I needed to apply the Intel series first). Applied cleanly. How do I check whether it's functional? I grepped dmesg for AMD or ucode, but nothing shows. Logread doesn't work at all (but I reckon that's unrelated). You should grep -i for "microcode", it should say something like: "microcode updated early ..." probably on first line in kernel log. Strange thing is that logread doesn't work, but I don't know what's causing this. Hi Thomas, I just booted OpenWrt off my USB stick, grepping for microcode returned this: [2.038790] microcode: CPU0: patch_level=0x08001129 [2.043782] microcode: CPU1: patch_level=0x08001129 [2.114395] microcode: CPU2: patch_level=0x08001129 [2.119391] microcode: CPU3: patch_level=0x08001129 [2.124390] microcode: CPU4: patch_level=0x08001129 [2.129382] microcode: CPU5: patch_level=0x08001129 [2.134512] microcode: CPU6: patch_level=0x08001129 [2.139498] microcode: CPU7: patch_level=0x08001129 [2.144491] microcode: Microcode Update Driver: v2.2. Does that help you any? Tested on a Ryzen 1800X. I reckon logread not working might have to do with my using the combined-ext4 image, /tmp is kinda broken as well. Cheers Stijn Dmesg does say full retpoline support has been enabled, but unless I'm mistaken that was a compiler feature, not something that could be solved with microcode alone> Cheers Stijn Second does apply cleanly. Cheers Stijn [snip] -- TMN ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
