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
nfighting 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:/
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
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 ce
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 state
-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
.
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
-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
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
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
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
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-a
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
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
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
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
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
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
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 f
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
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
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 En
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
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/0
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 - cla
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
^
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/
atch (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 Se
atch (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 Se
= 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/t
n, 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/ka
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,
Sy
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
atch (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
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
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
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-ve
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
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
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.
* 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
* 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
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
* 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
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
-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
* 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
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
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/ke
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 quic
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 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...
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
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
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_
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
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
.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_PEE
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 se
: 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 se
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
Led
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
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
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
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
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
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
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
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
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
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/Mak
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://list
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
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
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/ma
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
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 br
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.in
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),
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).
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 ok
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
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
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 MT7
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
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
___
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-e
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 im
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
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
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
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
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/p
-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
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 pr
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
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
97 matches
Mail list logo
