This updates the mac80211 backport.
The removed patches are already integrated in the upstream version.
The 131-Revert-mac80211-aes-cmac-switch-to-shash-CMAC-driver.patch patch
was manually adapted to the changes in kernel 5.7.
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211
This updates the mac80211 backport to the latest minor version.
The removed patch was a backport from the upstream kernel which is now
integrated.
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211/Makefile | 8 +-
...-F2-blocksize-and-watermark-for-4359.patch | 2
This updates the mac80211 backport.
The removed patches are already integrated in the upstream version.
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211/Makefile | 6 +-
.../patches/ath/400-ath_move_debug_code.patch | 2 +-
...21
regressions found I would apply this to master in
about 1 week.
Hauke Mehrtens (4):
mac80211: Update to version 5.4.36-1
mac80211: Update to version 5.5.19
mac80211: Update to version 5.6.8-1
mac80211: Update to version 5.7-rc3-1
package/kernel/mac80211/Makefile | 8
On 5/1/20 11:07 PM, Paul Spooren wrote:
> Hi all,
>
> Google offers a program[0] to stipend people writing technical documentation
> for
> open source projects. The stipend is possible for anyone 18+ and not living
> in a
> US embargoed country, so unlike the Google Summer of Code project not
On 4/22/20 7:33 PM, Felix Fietkau wrote:
> On 2020-04-21 23:22, Hauke Mehrtens wrote:
>> This updates mac80211 in OpenWrt to version 5.7-rc2.
>> This update contains ath11k and many other ieee80211ax updates.
>> ath11k only works on the ipq807x devices.
>>
>> I t
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211/Makefile | 6 +-
.../patches/ath/404-regd_no_assoc_hints.patch | 4 +-
...21-ath10k_init_devices_synchronously.patch | 2 +-
.../ath/930-ath10k_add_tpt_led_trigger.patch | 4 +-
...-of-peer_bw_rxnss_override
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211/Makefile | 6 +-
.../patches/ath/400-ath_move_debug_code.patch | 2 +-
...21-ath10k_init_devices_synchronously.patch | 2 +-
.../ath/930-ath10k_add_tpt_led_trigger.patch | 4 +-
...-of-peer_bw_rxnss_override
shipped in OpenWrt master.
Hauke Mehrtens (3):
mac80211: Update to version 5.5.11
mac80211: Update to version 5.6.5-1
mac80211: Update to version 5.7-rc2-1
package/kernel/mac80211/Makefile | 8 +-
.../patches/ath/120-owl-loader-compat.patch | 6 +-
.../patches/ath/400
On 4/11/20 5:13 PM, David Bauer wrote:
> Hello Paul,
>
> On 4/3/20 10:58 PM, Paul Blazejowski wrote:
>> Hello David,
>>
>> It is great to hear to we're switching to 5.4 on ath79 target but i
>> wanted to bring to your attention that at least on the NAND subtargets
>> (for me wndr3700v4) we need
] Rebooting in 1 seconds..
The following GCC ticket was opened:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94506
Fixes: FS#2928
Signed-off-by: Hauke Mehrtens
---
...e-optimization-91355-optimized-code-.patch | 46 +++
1 file changed, 46 insertions(+)
create mode 100644
On 3/28/20 1:52 PM, Petr Štetiar wrote:
> Thanks! Merged into my staging tree at
> https://git.openwrt.org/openwrt/staging/ynezz.git
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
>
r-xp 00:02 272/lib/libc.so
> 77e1f000-77e21000 rwxp 00096000 00:02 272/lib/libc.so
> 77e21000-77e23000 rwxp 00:00 0
> 7fe23000-7fe44000 rw-p 00:00 0 [stack]
> 7ff63000-7ff64000 r--p 00:00 0 [vvar]
> 7
;rt2800_iq_search" [/drivers/net/wireless/ralink/rt2x00/rt2800lib] is
a static EXPORT_SYMBOL_GPL
WARNING: "rt2800_setbbptonegenerator"
[/drivers/net/wireless/ralink/rt2x00/rt2800lib] is a static EXPORT_SYMBOL_GPL
WARNING: "rt2800_rf_aux_tx1_loopback"
[/drivers/net/wire
On 3/28/20 12:12 PM, Evgeniy Didin wrote:
> This patch switches kernel version to 5.4 for archs38.
>
> Changes since v1:
> 1) Remove disabling of ath9k-htc package usage.
>On initial port in config-5.4 file the option
>"CONFIG_USB_SUPPORT" was missing what caused
>build failure.
> 2)
in glibc
2.28, but we still use them in ppp.
musl lib also provides these DES crypto functions. Without them we would
have to link ppp against openssl or an other crypto library.
Signed-off-by: Hauke Mehrtens
---
toolchain/glibc/common.mk | 6 +-
.../patches/001-regex-read
Without this change linux-atm does not build any more with glibc and
kernel 5.4, because SIOCGSTAMP is missing. This patch adds a missing
include to fix this compile problem.
Signed-off-by: Hauke Mehrtens
---
.../patches/410-missing-SIOCGSTAMP.patch | 20 +++
1 file changed
glibc 2.31 does not provide stime() any more, backport a fix from
current busybox master to avoid using this function.
Signed-off-by: Hauke Mehrtens
---
.../001-remove-stime-function-calls.patch | 84 +++
1 file changed, 84 insertions(+)
create mode 100644
package/utils
The removed patches are all integrated in the upstream version now.
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211/Makefile | 6 +-
...th9k-use-iowrite32-over-__raw_writel.patch | 40 -
.../patches/ath/120-owl-loader-compat.patch | 6 +-
.../patches/ath/404
The removed patches are all integrated in the upstream version now.
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211/Makefile | 6 +-
.../patches/ath/404-regd_no_assoc_hints.patch | 4 +-
...-ackto-to-max-timeout-in-ath_dynack_.patch | 2 +-
...set-but-not-used
there is an
undefined symbol and tcpdump and other builds are failing.
Fixes: 44f11353de04 ("libpcap: update to 1.9.1")
Signed-off-by: Hauke Mehrtens
---
package/libs/libpcap/Makefile | 4 +-
.../patches/100-debian_shared_lib.patch | 194 ++---
The removed patch is included in GCC 8.4.0.
Signed-off-by: Hauke Mehrtens
---
toolchain/gcc/Config.version | 2 +-
toolchain/gcc/common.mk | 4 +--
.../patches/8.3.0/090-rs6000-PR-89587.patch | 30 ---
.../002-case_insensitive.patch
The removed patch is included in GCC 9.3.0.
Signed-off-by: Hauke Mehrtens
---
toolchain/gcc/Config.version | 2 +-
toolchain/gcc/common.mk | 4 +-
...uninitialised_use_in_mips_split_move.patch | 55 ---
.../002-case_insensitive.patch
Hi,
I see this in my tmp/.config-package.in:
---
$ grep "https://git.openwrt.org/?p=openwrt/staging/hauke.git;a=shortlog;h=refs/heads/sanitizer
I do not understand this problem, what could be wrong here?
Hauke
signature.asc
Description: OpenPGP digital signature
Hi,
Based on recent events regarding COVID-19 the Battlemesh and the OpenWrt
developer meeting will not take place in May this year. We will monitor
the situation and plan to organize the event at a different date in
Calafou for instance in September.
Hauke
Forwarded Message
Hi,
I am working on updating mac80211 and the wireless drivers, see
https://git.openwrt.org/?p=openwrt/staging/hauke.git;a=shortlog;h=refs/heads/mac80211-5.6
This is currently on kernel 5.5, but 5.6 should not be a big problem.
I am not sure how we want to handle this for the next release, I see
Tested on Siemens WS-AP3610.
>
> CC: Hauke Mehrtens
> Signed-off-by: David Bauer
Acked-by: Hauke Mehrtens
We should still try to improve the upstream driver in the upstream
kernel, so we can use it when we switch to the next major kernel version
next year.
We should also improve
On 3/12/20 2:34 PM, Evgeniy Didin wrote:
> It is necessary to use GCC9 for building Linux 5.4.x version for
> archs38, in GCC8 the critical fixes are missing and ICE appears
> during building.
Is this problem specific to OpenWrt or is there a general problem with
arc Linux and gcc 8.3?
Should it
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
-
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
-
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
-
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
-
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
-
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
-
This removed the kernel 4.14 support for multiple targets which were
early switched to kernel 4.19. This should reduce the maintenance
efforts especially after or when we add kernel 5.4 support for these
targets. Some of these targets do not even compile against 4.14 any
more.
Hauke Mehrtens
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
-
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
-
This removed the kernel 4.14 support for multiple targets which were
early switched to kernel 4.19. This should reduce the maintenance
efforts especially after or when we add kernel 5.4 support for these
targets. Some of these targets do not even compile against 4.14 any
more.
Hauke Mehrtens
dev/null >
target/linux/generic/config-4.14-new
$ mv target/linux/generic/config-4.19-new target/linux/generic/config-4.19
Signed-off-by: Hauke Mehrtens
---
target/linux/generic/config-4.14 | 2 +-
target/linux/generic/config-4.19 | 8
2 files changed, 5 insertions(+), 5 deletions(-)
fixes")
Signed-off-by: Hauke Mehrtens
---
.../patches/400-portability_fixes.patch | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git
a/package/network/utils/linux-atm/patches/400-portability_fixes.patch
b/package/network/utils/linux-atm/p
This adds AP vlans support.
Signed-off-by: Hauke Mehrtens
---
package/kernel/ath10k-ct/Makefile | 6 ++--
...rolling-support-for-various-chipsets.patch | 36 +--
...h10k-4.16-use-tpt-trigger-by-default.patch | 4 +--
3 files changed, 23 insertions(+), 23 deletions
This makes ath10k-ct use the version based on kernel 5.4 by default.
Signed-off-by: Hauke Mehrtens
---
The update to version 5.4 is needed to make this driver compile against
kernel 5.4.
This got some minimal testing on IPQ4019 by me.
package/kernel/ath10k-ct/Makefile | 4
ath10k-ct supports the combination to select ADHOC (IBSS) mode and
different beacon intervals together. mac80211 does not like this
combination, but Ben says this is ok, so remove this check.
Signed-off-by: Hauke Mehrtens
---
.../patches/subsys/400-allow-ibss-mixed.patch | 29
On 10/19/19 1:43 PM, David Bauer wrote:
> Hello,
>
> while preparing the switch to 19.07 for the mesh-framework Gluon, we found an
> issue
> with ath10k, which results in an overflowing TX queue in the kernel. The
> QCA9880 does
> not send TX_DONE or TX_FAILED messages back to the driver, which
This fixes compile problems with kernel 5.4
Signed-off-by: Hauke Mehrtens
---
We need this update to make this driver compile against kernel 5.4,
but I do not have the hardware to run time test this change.
package/kernel/rtl8812au-ct/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3
On 1/12/20 5:44 AM, Rosen Penev wrote:
> f4f8f4a180366ee90fd8e153213db2cb746ca361 broke ffmpeg compilation with x86
>
> The reason is that ffmpeg's x86 assembly requires at least MMX, which the
> pentium CPU_TYPE was preventing.
As far as I understand it MMX is already needed and you just want
The kernel kernel address sanitizer is able to detect some memory
bugs in the kernel like out of range array accesses.
Signed-off-by: Hauke Mehrtens
---
config/Config-kernel.in | 52
target/linux/generic/config-4.14 | 1 +
target/linux/generic/config
Make it possible to activate some additional kernel debug options.
This can be used to debug some problems in kernel drivers.
Signed-off-by: Hauke Mehrtens
---
config/Config-kernel.in | 68
target/linux/generic/config-4.14 | 5 +++
target/linux/generic
The kernel Undefined Behavior Sanitizer is able to detect some memory
bugs in the kernel like out of range array accesses.
Signed-off-by: Hauke Mehrtens
---
config/Config-kernel.in | 35
target/linux/generic/config-4.14 | 4
target/linux/generic
The adds an option to activate KCOV (Code coverage for fuzzing).
Signed-off-by: Hauke Mehrtens
---
config/Config-kernel.in | 33 +
1 file changed, 33 insertions(+)
diff --git a/config/Config-kernel.in b/config/Config-kernel.in
index 3059a45f48..8e9e3518bf 100644
This option has now a different dependency and can be activated, set a
default value.
Fixes: 20b5a4ca01ca ("kernel: bump 4.19 to 4.19.101")
Signed-off-by: Hauke Mehrtens
---
target/linux/x86/config-4.14 | 1 +
target/linux/x86/config-4.19 | 1 +
2 files changed, 2 insertions(+)
Hi,
We would like to organize a public, free of charge OpenWrt developer
meeting at the Battlemesh this year. The Wireless Battle of the Mesh
(Battlemesh) is an event that aims at bringing together people from
across the world to test the performance of different routing protocols
for ad-hoc
On 1/26/20 4:55 PM, Hauke Mehrtens wrote:
> This backports some security relevant patches from libubox master. These
> patches should not change the existing API and ABI so that old
> applications still work like before without any recompilation.
> Application can not also use more
The removed patches are all integrated in the upstream version now.
Signed-off-by: Hauke Mehrtens
---
package/kernel/mac80211/Makefile | 6 +-
.../ath/930-ath10k_add_tpt_led_trigger.patch | 4 +-
...-of-peer_bw_rxnss_override-parameter.patch | 2 +-
...dling-for-VHT160
On 1/26/20 4:14 PM, Hauke Mehrtens wrote:
> This extends the blob_parse() function to check that no inner attribute
> is bigger than the outside attribute. The blob_parse_untrusted() should
> be used when we know the size of blob_attr *attr, in some other way.
>
> Signed-off-by:
Hi,
We plan to tag and build OpenWrt 19.07.1 and 18.06.7 on Wednesday evening.
Hauke
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
but not used.
OpenWrt master and 19.07.0 already have these patches by using a more
recent libubox version.
Signed-off-by: Hauke Mehrtens
---
This should not change the libubox ABI, but backports most of the
changes which are in master.
I hope I didn't miss anything important.
package/libs
This extends the blob_parse() function to check that no inner attribute
is bigger than the outside attribute. The blob_parse_untrusted() should
be used when we know the size of blob_attr *attr, in some other way.
Signed-off-by: Hauke Mehrtens
---
blob.c | 3 ++-
1 file changed, 2 insertions
On 1/19/20 6:56 PM, Hannu Nyman wrote:
> Hauke Mehrtens kirjoitti 19.1.2020 klo 19.17:
>> On 1/16/20 11:05 AM, Petr Štetiar wrote:
>>
>>> BTW it's still master + 2 stable releases which will receive the
>>> support? Once
>>> the 20.y is out, the 1
On 1/16/20 12:48 PM, Petr Štetiar wrote:
> Peter Geis [2020-01-15 21:15:41]:
>
> Hi,
Hi,
> tl;dr I'm going to vote in favor of skipping release with 4.19 and focus on
> 5.4 kernel.
>
> The 19.07 release was delayed by a few months, so this has affected the
> subsequent release as well. The
On 1/16/20 11:05 AM, Petr Štetiar wrote:
> Hauke Mehrtens [2020-01-16 00:00:33]:
>
> Hi,
Hi,
Sorry for answering so late, was busy with other stuff.
>> My preferred timeline would the the following:
>> * Beginning of February: freeze master for big changes (adding new
&g
ries
found in the staging directory.
Signed-off-by: Hauke Mehrtens
---
include/kernel.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/kernel.mk b/include/kernel.mk
index 38331768ed..b1b1e9e9c8 100644
--- a/include/kernel.mk
+++ b/include/kernel.mk
@@ -114,6 +114,7 @@ KERNEL_
Hi,
I meet with jow about 2 weeks ago and we talked about a lot of OpenWrt
related stuff, one of the topics was the release after 19.07.
As the 19.07 release is now done, I would like to follow up on this topic.
We thought that the time between the 19.07 branch and the final release
was way too
Hi,
The OpenWrt Community is proud to announce the sixth service release of
the stable OpenWrt 18.06 series. OpenWrt 18.06.6 incorporates security
updates for base packages, new versions of the Linux kernel, a bug fix
related to signature verification, and fixes for various devices.
Some
Hi,
The OpenWrt community is proud to announce the first stable release of
the OpenWrt 19.07 stable version series. It incorporates 3954 commits
since the previous release 18.06.0 and 85 commits since the previous
release candidate 19.07.0-rc2.
An upgrade from OpenWrt 18.06 to OpenWrt 19.07 is
On 1/8/20 7:24 AM, Petr Štetiar wrote:
> Hauke Mehrtens [2020-01-07 23:21:19]:
>
> Hi,
>
> thanks for your work.
>
>>> Hauke Mehrtens (6):
>>> buildsystem: Make PIE ASLR option tristate
>>> dnsmasq: Activate PIE by default
>>> dropbea
On 10/27/19 6:44 PM, Hauke Mehrtens wrote:
> This is a follow up patch on this discussion on the mailing list:
> https://patchwork.ozlabs.org/patch/1041647/
>
> This allows to activate PIE only for some packages where we thing it is
> necessary and not only globally for all of t
On 1/5/20 5:37 PM, Piotr Dymacz wrote:
> Hi Adrian, Tom,
>
> On 05.01.2020 16:57, m...@adrianschmutzler.de wrote:
>>> -Original Message-
>>> From: Tom Psyborg [mailto:pozega.tomis...@gmail.com]
>>> Sent: Sonntag, 5. Januar 2020 16:33
>>> To: m.
On 1/7/20 12:32 PM, Adrian Schmutzler wrote:
> Hi Hauke,
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
>> Behalf Of Hauke Mehrtens
>> Sent: Sonntag, 5. Januar 2020 14:54
>> To: m...@adrianschmutzler
On 1/7/20 12:39 PM, Adrian Schmutzler wrote:
> Hi Hauke,
>
> since you seem to have a mir3g, maybe you can look into the following MAC
> address issue/question when you find some time:
>
> For the mir3g, 02_network sets the lan_mac to factory 0xe006, while the
> address from 0xe000 set to is
On 1/7/20 9:09 PM, Eneas Queiroz wrote:
> On Mon, Jan 6, 2020 at 1:59 PM Hauke Mehrtens wrote:
>>
>> I cherry-picked it, but WPA3 still does not work for me.
>>
>> Hauke
>
> TLDR: WPA3 support with wolfssl is still not ideal.
>
> WPA3 success was reported
On 12/24/19 4:48 PM, Hauke Mehrtens wrote:
> Hi,
>
> I would like to tag 18.06.6 release in the evening of Wednesday 1.
> January and then start the builders.
>
> I would like to tag 19.07 final release on Friday 3. January and the
> start the builders on Saturday or Sunda
On 1/6/20 5:39 PM, e9hack wrote:
> Am 06.01.2020 um 17:20 schrieb Petr Štetiar:
>> e9hack [2020-01-06 16:59:47]:
>>
>>> it looks like that uhttpd/luci/rpcd is broken again. The call 'ubus call
>>> luci-rpc getWirelessDevices' does fail 'Command failed: Request timed out'.
>>
>> can you provide
On 1/2/20 1:04 AM, Eneas Queiroz wrote:
>
> On Wed, Jan 1, 2020 at 6:54 PM Hauke Mehrtens <mailto:ha...@hauke-m.de>> wrote:
>
> I will shift both releases (18.06.6 and 19.07.0 final) to Monday 6.
> January to get some security fixes in, please get your changes i
]
[522413.129459] ra = 004197ef in dnsmasq[40+23000]
This is happening in blockdata_write() when block->next is
dereferenced, but I am not sure if this is related to this problem or if
this is a different problem. I am unable to reproduce this problem.
Signed-off-by: Hauke Mehrt
On 1/5/20 5:37 PM, m...@adrianschmutzler.de wrote:
> Hi Hauke,
>
>> -Original Message-----
>> From: Hauke Mehrtens [mailto:ha...@hauke-m.de]
>> Sent: Sonntag, 5. Januar 2020 15:18
>> To: openwrt-devel@lists.openwrt.org
>> Cc: m...@adrianschmutzle
On 1/5/20 3:17 PM, Hauke Mehrtens wrote:
> Without this change sysupgrade from 18.06 to 19.07 is only possible with
> the -F option.
> In OpenWrt 18.06 the nand_do_platform_check() function is called with
> the board name mir3g only, if the tar does not use mir3g it will fail.
>
with the supported_devices
attribute to allow renaming. Do the renaming of the target between 19.07
and master like it is done for some other boards.
I tested the following sysupgrades successfully without -F
18.06 -> 19.07
19.07 -> master
master -> 19.07
Signed-off-by: Hauke Mehrtens
---
target/linux/ram
On 1/5/20 2:43 PM, m...@adrianschmutzler.de wrote:
> On 11/28/19 7:11 PM, Adrian Schmutzler wrote:
>> Hi Hauke,
>>
>>> The following are still on kernel 4.9:
>>> * ar7
>>> * ixp4xx
>>> * orion
>>
>> There are patches (actually from you, May 2019) on the list
On 1/5/20 11:40 AM, Petr Štetiar wrote:
> Hauke Mehrtens [2020-01-04 20:41:44]:
>
> Hi,
>
> thanks for the review!
>
>> Please annotate the function with:
>> __attribute__ ((format (printf, 2, 3)));
>
> Done.
>
>>> + va_start(va, fmt);
>
On 1/3/20 1:46 AM, Petr Štetiar wrote:
> Fixes following deficiencies:
>
> * unhandled read() errors
> * everything bundled in one long function, which is hard to follow and
>reason about
> * JSON parser errors are being ignored, anything else then
>json_tokener_continue is fatal error
thod")
> Cc: Rafał Miłecki
> Reported-by: Petr Novák
> Signed-off-by: Petr Štetiar
> ---
Reviewed-by: Hauke Mehrtens
> system.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/system.c b/system.c
> index 65d3f09b7fb6..5cd88e0d8227 100
On 1/3/20 1:53 PM, m...@adrianschmutzler.de wrote:
> Hi Hauke,
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
>> On Behalf Of Hauke Mehrtens
>> Sent: Donnerstag, 28. November 2019 19:42
>> To: Adri
On 12/24/19 4:48 PM, Hauke Mehrtens wrote:
> Hi,
>
> I would like to tag 18.06.6 release in the evening of Wednesday 1.
> January and then start the builders.
>
> I would like to tag 19.07 final release on Friday 3. January and the
> start the builders on Saturday or Sunda
On 12/24/19 8:50 PM, Tom Psyborg wrote:
> Hi
>
> And what about this one?
> https://bugs.openwrt.org/index.php?do=details_id=2593
>
> Some regulatorty bugs?
Here is an other one related to ath10k:
https://bugs.openwrt.org/index.php?do=details_id=2614
The reporter says it works with an older
On 12/24/19 10:50 PM, Petr Štetiar wrote:
> Khem Raj [2019-12-24 10:02:13]:
>
> Hi,
>
> use "PATCH libubox" subject prefix, because there is no blobmsg.c file in the
> main tree.
>
>> Fixes error: '__builtin_strcpy' offset 6 from the object at 'attr' is out of
>> the bounds of referenced
Hi,
I would like to tag 18.06.6 release in the evening of Wednesday 1.
January and then start the builders.
I would like to tag 19.07 final release on Friday 3. January and the
start the builders on Saturday or Sunday.
Are there any objections to these dates?
Both releases should fix all known
On 12/23/19 8:57 PM, Paul Fertser wrote:
> Hi Bjørn,
>
> On Mon, Dec 23, 2019 at 10:17:11AM +0100, Bjørn Mork wrote:
>> Paul Fertser writes:
>>> --- /dev/null
>>> +++
>>> b/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch
>>> @@ -0,0 +1,100 @@
>>> +---
On 12/23/19 10:17 AM, Bjørn Mork wrote:
> Paul Fertser writes:
>
>> --- /dev/null
>> +++
>> b/package/kernel/ath10k-ct/patches/960-0011-ath10k-limit-pci-buffer-size.patch
>> @@ -0,0 +1,100 @@
>> +--- a/ath10k-4.19/pci.c
>> b/ath10k-4.19/pci.c
>> +@@ -142,7 +142,11 @@ static struct ce_attr
On 11/27/19 6:29 PM, Daniel Danzberger wrote:
> This callback shows the currently active HTMODE of the device.
>
> Signed-off-by: Daniel Danzberger
> ---
> include/iwinfo.h | 4 ++-
> iwinfo_nl80211.c | 70
> 2 files changed, 73 insertions(+), 1
On 11/27/19 6:29 PM, Daniel Danzberger wrote:
> Signed-off-by: Daniel Danzberger
> ---
> iwinfo.c | 44
> 1 file changed, 44 insertions(+)
>
> diff --git a/iwinfo.c b/iwinfo.c
> index a76b72a..7f46e3e 100644
> --- a/iwinfo.c
> +++ b/iwinfo.c
This
On 12/18/19 11:09 PM, Xianjun Jiao (UGent-imec) wrote:
> Dear openwrt friends,
>
>
> A message may interest you. Our openwifi project is online:
>
> https://github.com/open-sdr/openwifi
>
>
> Full stack real time SDR (Software Defined Radio) Wi-Fi implementation
> on zynq FPGA with embedded
_SOC_FALCON
I would use these as a config options like CONFIG_ATH79 for the ath790
target.
as SOC names you can use these:
amazonse_
danube_
ar9_
vr9_
falcon_
Hauke
>
>> -Original Message-
>> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
>> On
On 12/15/19 2:27 PM, Daniel Golle wrote:
> Hi Adrian,
>
> On Sun, Dec 15, 2019 at 02:10:14PM +0100, m...@adrianschmutzler.de wrote:
>> Hi,
>>
>> I consider doing a DTS rename for lantiq target similar to what it's like on
>> ath79 and what I did for ramips earlier that year.
>>
>> However, I
On 12/6/19 12:23 AM, Hauke Mehrtens wrote:
> On 11/26/19 10:44 AM, Stijn Tintel wrote:
>> On 26/11/2019 00:34, Hauke Mehrtens wrote:
>>> It looks like there is a throughput problem with ath10k-ct on QCA9984,
>>> https://bugs.openwrt.org/index.php?do=details_id=2593
>
On 12/6/19 7:02 PM, Ben Greear wrote:
> On 12/6/19 9:44 AM, Joe Ayers wrote:
>>>
>>>
Possibly the same symptoms don't exist on 128MB RAM devices.
>>>
>>> Like there is some if condition, which is doing some nasty things on 64M
>>> devices? I admit, that I don't have ath10k-ct source code
On 11/26/19 10:44 AM, Stijn Tintel wrote:
> On 26/11/2019 00:34, Hauke Mehrtens wrote:
>> It looks like there is a throughput problem with ath10k-ct on QCA9984,
>> https://bugs.openwrt.org/index.php?do=details_id=2593
>> there are multiple reports in the Forum.
>>
&g
Hi,
The OpenWrt community is proud to announce the second release candidate
of the upcoming OpenWrt 19.07 stable version series. It incorporates 126
commits since the previous release candidate 19.07.0-rc1.
With this release, the OpenWrt project brings all supported targets back
to a single
Hi,
I plan to tag 19.07-rc2 on Saturday afternoon and then start the builders.
The problem seen with ath10k-ct will probably not be fixed in time for
19.07-rc2.
Hauke
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing
On 11/16/19 9:23 PM, Jo-Philipp Wich wrote:
> Disable the Netgear WNR2000v4 image by default as the device has
> insufficient flash space for release build images.
>
> Ref: https://forum.openwrt.org/t/devices-too-big-to-save-overlay/18161/11
> Signed-off-by: Jo-Philipp Wich
> ---
>
701 - 800 of 1807 matches
Mail list logo
