On 01-06-16 17:14, Jo-Philipp Wich wrote:
> Enable support for DMI decoding in the kernel so that we can access
> manufacturer and model information via sysfs.
>
> Signed-off-by: Jo-Philipp Wich
> ---
> target/linux/x86/config-4.4 | 3 ++-
> 1 file changed, 2 insertions(+), 1
On 17-05-16 23:37, Felix Fietkau wrote:
> On 2016-05-17 23:12, Daniel Golle wrote:
>> * build for pentium4 instead of i486
>> * enable PAE
>> * enable EFI support
>> * enable KVM guest and host support
Is anyone running KVM on a 32bit host? I would leave out KVM host
support here.
> I like this
Always use the kernel version in the patch directory names for
clearness and consistency across all targets.
This series is in my staging tree at
https://git.lede-project.org/?p=lede/stintel/staging.git;a=summary
Stijn Tintel (4):
au1000: rename patches directory to patches-3.18
omap: rename
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
.../100-wrt350nv2_openwrt_partition_map.patch | 31 +
.../patches-3.18/101-wnr854t_partition_map.patch | 24 +++
.../orion/patches-3.18/200-dt2_board_support.patch | 26
.../orion/patches-3.
Hi Ben,
On 12-08-16 16:19, Ben Greear wrote:
>
>
> On 08/11/2016 11:36 PM, John Crispin wrote:
>> Hi,
>>
>> the V2 does not address the changes i request in V1. these were
>>
>> * explain why we need this and what it does. right now we only know it
>> "reports certain bugs" which is really very
Hi all,
As we prefer cherry-picking commits from master into the lede-17.01
branch, please don't send changes that can be cherry-picked as a patch.
If you want a commit from master in lede-17.01, please send a mail
requesting to cherry-pick them, with the commit(s) you want in a list in
the same
On 05-02-17 17:49, Stijn Segers wrote:
> Bumps kernel from .46 to .47.
>
This has to be done in master first, then cherry-picked into lede-17.01.
Stijn
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
On 10-02-17 18:11, Dave Taht wrote:
> About the biggest request from the field seems to be supplying RA and
> dhcpv6 dns on a more real IPv6 address than fe80 to make android users
> happier (https://github.com/dtaht/dnsmasq-lede/issues/11).
Is this only a problem for Android users? I ran into a
Hi,
I would like to cherry-pick the following commit to lede-17.01:
0bf85ef dropbear: enable SHA256 HMACs
Please ACK/NAK.
Thanks,
Stijn
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/boot/uboot-envtools/files/ar71xx | 1 +
target/linux/ar71xx/base-files/etc/board.d/01_leds | 5 +
.../linux/ar71xx/base-files/etc/board.d/02_network | 5 +
.../etc/hotplug.d/firmware/11-ath10k-caldata
Based on mkwrgimg.c.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
tools/firmware-utils/Makefile| 1 +
tools/firmware-utils/src/mkwrggimg.c | 282 +++
2 files changed, 283 insertions(+)
create mode 100644 tools/firmware-utils/src/mkwrg
from the D-Link GPL code. The mkwrggimg utility
also works for the D-Link DAP-2553. For more info, see
https://forum.openwrt.org/viewtopic.php?id=52048
Stijn Tintel (5):
firmware-utils: mkwrggimg: new tool for D-Link DAP-2695
kernel: mtdsplit: add support for WRGG images
mtd: add fixwrgg
Based on fixseama.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/system/mtd/src/Makefile | 3 +-
package/system/mtd/src/mtd.c| 28 +-
package/system/mtd/src/mtd.h| 1 +
package/system/mtd/src/wrgg.c | 189
package/
On 24-10-16 02:37, James Feeney wrote:
> What are thoughts about backporting the DirtyCOW patch to the Lede kernels? I
> did not see any mention in the Lede-dev Archives.
>
Most targets use kernel 4.4. As the 4.4 kernel has been updated to
4.4.26 on Friday [0], these targets are no longer
On 24-10-16 03:10, Stijn Tintel wrote:
> On 24-10-16 02:37, James Feeney wrote:
>> What are thoughts about backporting the DirtyCOW patch to the Lede kernels?
>> I
>> did not see any mention in the Lede-dev Archives.
>>
> Most targets use kernel 4.4. As t
Based on mkwrgimg.c.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
tools/firmware-utils/Makefile| 1 +
tools/firmware-utils/src/mkwrggimg.c | 282 +++
2 files changed, 283 insertions(+)
create mode 100644 tools/firmware-utils/src/mkwrg
images
Remove ucidef_set_interfaces_lan_wan
Stijn Tintel (7):
firmware-utils: mkwrggimg: new tool for D-Link DAP-2695
kernel: mtdsplit: add support for WRGG images
mtd: fix endianness detection on musl
mtd: add fixwrgg command
ar71xx/base-files: rename 09_fix-trx-header 09_fix-checksum
Based on fixseama.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/system/mtd/src/Makefile | 3 +-
package/system/mtd/src/mtd.c| 28 +-
package/system/mtd/src/mtd.h| 1 +
package/system/mtd/src/wrgg.c | 190
package/
Support splitting WRGG images, found in some D-Link devices (e.g.
DAP-2695).
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
target/linux/ar71xx/config-4.4 | 1 +
target/linux/generic/config-3.18 | 1 +
target/linux/generic/conf
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
target/linux/ar71xx/image/Makefile | 5 -
target/linux/ar71xx/image/legacy.mk | 6 --
2 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
On 21-10-16 18:34, Stijn Tintel wrote:
> This patch series adds support for D-Link DAP-2695 rev. A1.
>
>
FYI, this series is also available in my staging tree at
https://git.lede-project.org/?p=lede/stintel/staging.git;a=shortlog;h=refs/heads/dap-2695-
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/boot/uboot-envtools/files/ar71xx | 1 +
target/linux/ar71xx/base-files/etc/board.d/01_leds | 5 +
.../linux/ar71xx/base-files/etc/board.d/02_network | 3 +
.../etc/hotplug.d/firmware/11-ath10k-caldata
On 16-11-16 09:54, Koen Vandeputte wrote:
> Hi Paul,
>
> First of all, thank you for reviewing and testing the patch.
>
>
> Let me share in detail how I prepare the kernel update patch:
>
> - Pull the latest git state 3 times
> - On two of them, I apply my custom .config and feeds for the hardware
On 16-11-16 07:43, p.wa...@gmx.at wrote:
> From: Paul Wassi
>
> Refresh patches for all targets that support kernel 4.4.
> compile/run-tested on kirkwood, ar71xx, brcm47xx.
>
> Signed-off-by: Paul Wassi
> ---
> This patch is meant to be applied upon 4.4.31!
>
On 02-11-16 10:45, p.wa...@gmx.at wrote:
>> I find it quite odd that it doesnt apply cleanly to my LEDE tree at git rev
> I've just gone throgh the changes, and there is definitely more than just
> 'refreshing' the line numbers/offsets. This is seen at [1]. Have a special
> look
> at [2] at the
On 12-09-16 06:10, Yousong Zhou wrote:
> On 12 September 2016 at 00:12, Stijn Tintel <st...@linux-ipv6.be> wrote:
>> Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
>> ---
>> package/boot/uboot-envtools/files/ar71xx | 1 +
>> target/linux/ar71
On 14-10-16 20:19, Chris Blake wrote:
> The following patch adds support for the PC Engines APU2 Embedded Board
> as a profile under the X86_64 target. More information on this board can
> be found at www.pcengines.ch/apu2c4.htm
>
> Note that this patch is a part of an RFC, and should not be
On 06-01-17 20:38, Hauke Mehrtens wrote:
> Please do not send a mail with just an attachment, oldpackage is frozen
> since some years, please send add the package to the official openwrt
> package repository, add yourself as a maintainer and send a pull request
> on github.
There are PRs for this
o allow selectively enabling services on ignored
>interfaces
>
> - the README to clarify the fact that "ra", "ndp", "dhcpv4" and "dhcpv6" can
>now override "option ignore"
>
> Signed-off-by: Jo-Philipp Wich <j...@mein.io>
Tested-by: Stijn Tintel <st...@linux-ipv6.be>
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
s
> image), the old wget2nand script and rootfs tarballs are gone.
>
Tested sysupgrade on RB2011L-IN while booted from the initramfs image,
and then again after booting from flash.
Thanks!
Tested-by: Stijn Tintel <st...@linux-ipv6.be>
___
Lede-de
On 10-01-17 11:22, Sujith wrote:
> wpa_supplicant allows only SAE as the key management
> type for mesh mode. The recent key_mgmt rework unconditionally
> added WPA-PSK - this breaks interface bringup and wpa_s
> throws this error message:
>
> Line 10: key_mgmt for mesh network should be open or
Enable support for stronger SHA256-based algorithms in hostapd and
wpa_supplicant when using WPA-EAP or WPA-PSK with 802.11w enabled.
We cannot unconditionally enable it, as it requires hostapd to be
compiled with 802.11w support, which is disabled in the -mini variants.
Signed-off-by: Stijn
/stintel/staging.git;a=summary
Stijn Tintel (3):
wpa_supplicant: rework wpa_key_mgmt handling
hostapd: add function to handle wpa_key_mgmt
hostapd: enable SHA256-based algorithms
package/network/services/hostapd/files/netifd.sh | 32 +---
1 file changed, 17 insertions(+), 15
Rework wpa_key_mgmt handling for wpa_supplicant to be consistent with
how it is done for hostapd.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/network/services/hostapd/files/netifd.sh | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/p
Now that wpa_key_mgmt handling for hostapd and wpa_supplicant are
consistent, we can move parts of it to a dedicated function.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/network/services/hostapd/files/netifd.sh | 19 ++-
1 file changed, 10 insertions
On 27-12-16 12:57, Stijn Tintel wrote:
> While the standard does not require SHA256-based algorithms when PFM is
> mandatory, there's not much of a point in keeping the old algorithms
> enabled.
>
> See http://lists.shmoo.com/pipermail/hostap/2014-November/031283.html
Please ignor
Rework wpa_key_mgmt handling for wpa_supplicant to be consistent with
how it is done for hostapd.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/network/services/hostapd/files/netifd.sh | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/p
Enable support for stronger SHA256-based algorithms in hostapd and
wpa_supplicant when using WPA-EAP or WPA-PSK with 802.11w enabled.
We cannot unconditionally enable it, as it requires hostapd to be
compiled with 802.11w support, which is disabled in the -mini variants.
Signed-off-by: Stijn
ized other patches
>> I think those patches fit into the "uncategorized other patches" category so
>> why don't we use 900-?
> I'd also like to have space for "uncategorized other patches" added
> before patches backported from raspberrypi/linux. 950 would allow
> using 900-949 numbers for such stuff. And in case we need patches on
> top of raspberrypi/linux (as Felix suggested) we may use 951-999.
>
950 sounds good to me.
Acked-by: Stijn Tintel <st...@linux-ipv6.be>
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
the _GLIBCXX_USE_CXX11_ABI macro when uClibc++
is selected as the preferred standard C++ library.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
rules.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rules.mk b/rules.mk
index ed796a5..bf051b7 100644
--- a/ru
On 15-03-17 10:20, Bastian Bittorf wrote:
> * Stijn Tintel <st...@linux-ipv6.be> [15.03.2017 10:03]:
>> work on Raspberry Pi. My main question now is: is there any interest in
>> having Kodi for LEDE at all, or should I not bother preparing it for
>> submission.
> i l
Hi all,
After a minor cleanup, I published [0] Kodi and dependencies for running
on the brcm2708 target (Raspberry Pi). Dependencies for this are in the
kodi branches of my LEDE staging tree [1], and my fork of the packages
feed [2].
I am currently working on x86 support, but it's taking longer
On 15-03-17 13:45, Mirko Vogt wrote:
> On 03/15/2017 11:57 AM, Daniel Engberg wrote:
>> Hi,
> Huhu,
>
>> While I applaud your achievement I'd don't see such projects viable in
>> terms of maintainability and longevity.
> Applauds from me as well! I started doing so with XBMC a couple of years
>
On 15-03-17 11:57, Daniel Engberg wrote:
> Hi,
Hi Daniel,
Can you please check why your mail client breaks up the mailing-list
thread each time you reply? This is quite annoying as it breaks the flow
of conversation. It's even worse than top-posting, please fix this.
Thanks,
Stijn
Last week I managed to get Kodi to build for LEDE, and I am running it
on my Raspberry Pi Zero W. It's mostly quick and dirty, definitely not
ready to push to the repository, and in its current form it will only
work on Raspberry Pi. My main question now is: is there any interest in
having Kodi
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
target/linux/brcm2708/base-files/etc/board.d/02_network | 3 +++
target/linux/brcm2708/base-files/etc/diag.sh| 3 ++-
target/linux/brcm2708/base-files/lib/brcm2708.sh| 3 +++
3 files changed, 8 insertions(+), 1 de
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
.../linux/brcm2708/base-files/etc/board.d/02_network | 6 +++---
target/linux/brcm2708/base-files/etc/diag.sh | 8
target/linux/brcm2708/base-files/lib/brcm2708.sh | 20 ++--
.../lib/p
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
.../brcm2708/base-files/etc/board.d/02_network | 3 +
target/linux/brcm2708/base-files/etc/diag.sh | 3 +-
target/linux/brcm2708/base-files/lib/brcm2708.sh | 3 +
target/linux/brcm2708/image/Makefile
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/kernel/brcm2708-gpu-fw/Makefile | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/package/kernel/brcm2708-gpu-fw/Makefile
b/package/kernel/brcm2708-gpu-fw/Makefile
index 2a5a043..7e80530
On 31-07-17 18:11, John Crispin wrote:
> Hi,
>
> I rebased my ages old kernel patch cleanup series. It can be found
> here [1].
>
> the series annotates all patches and splits them up into 3 folders
> backports/pending/hacks.
I would prefer to keep the patches-X.Y directory and use backport,
On 27-06-17 10:43, Yury Shvedov wrote:
> Fixed with acct_interval patch (your changes was not appeared at github
> for now).
>
> By the way, I believe, that configuring RADIUS, (even AUTH) without
> WPA-EAP will not break anything at all (that is not definitely).
> But I definitely saw the piece
On 25-06-17 22:40, Kevin Darbyshire-Bryant wrote:
> 10 attempts at login before dropping connection is too many, 3 tries and
> you're out.
>
As we are changing a default, it might annoy users for whatever reason.
Since this is done at compile time, there is no easy way to revert to
the old
UX_DIR)/.config > $(LINUX_RECONFIG_TARGET)
>
>install: $(LINUX_DIR)/.image
This fixes FS #366 for me. Thanks a lot!
Tested-by: Stijn Tintel <st...@linux-ipv6.be>
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
On 13-05-17 14:48, Bryan Mayland wrote:
> Hello, I work on an open source project which uses the Raspberry Pi
> with LEDE as the host board. I've noticed that the kernel config does
> not include the BCM2835 cpufreq driver and therefore the CPU remains
> locked at the frequency set by the
On 14-06-17 14:51, Yury Shvedov wrote:
> RADIUS protocol could be used not only for authentication but for
> accounting too. Accounting could be configured for any type of networks.
> However there no way to configure NAS Identifier for non-WPA-EAP
> networks without this patch.
The patch is
On 29-05-17 14:04, Yury Shvedov wrote:
> Hi, I'm new here and I wonder why there is still no UCI option to configure
> Radius-Accounting-Interim-Interval.
> I've made a patch to fix that and like to share it to others and ask is there
> any serious reason for lack of such
> option?
>
> Make an
On 27-06-17 08:23, Yury Shvedov wrote:
> Like that?
No, the patch is still mangled, and it is not sent with git send-email,
but with Thunderbird. Please have a look at
https://www.kernel.org/pub/software/scm/git/docs/git-send-email.html,
you can pass your SMTP server credentials to it.
On 27-06-17 09:34, yshve...@wimarksystems.com wrote:
> From: Yury Shvedov
>
> Sorry, I've tried to configure my thunderbird properly to use it as
> patch sender. But it seems unsuccessfully. Do I understand you
> correctly about grouping acct_* values?
>
No worries,
On 27-06-17 10:21, Yury Shvedov wrote:
> RADIUS protocol could be used not only for authentication but for
> accounting too. Accounting could be configured for any type of networks.
> However there no way to configure NAS Identifier for non-WPA-EAP
> networks without this patch.
The patch is not
On 29-05-17 09:03, John Crispin wrote:
> (resend, this time as plain text)
>
> Hi,
>
> here is a V3 of the remerge proposal, I tried to fold all the comments
> people made into it, if anything is missing let me know. Please
> remeber that post remerge anything can be voted on, so cluttering the
>
On 18-09-17 15:06, Roman Yeryomin wrote:
> On 18 September 2017 at 12:27, Stijn Tintel <st...@linux-ipv6.be> wrote:
>> On 17-09-17 21:35, Roman Yeryomin wrote:
>>> Signed-off-by: Roman Yeryomin <ro...@advem.lv>
>>> ---
>> Hi Roman,
>>
>> I h
On 17-09-17 21:35, Roman Yeryomin wrote:
> Signed-off-by: Roman Yeryomin
> ---
Hi Roman,
I have merged your series in my staging tree, but the commit author
doesn't match the SoB line. Do you prefer to use the address above, or
leroi.li...@gmail.com in both?
Thanks,
Stijn
On 17-09-17 11:49, Hauke Mehrtens wrote:
> On 09/17/2017 01:41 AM, Florian Fainelli wrote:
>> Delete a bunch of fixes that are already included.
>> Refresh patches.
>> Compile-tested on malta/mipsel
>> Runtime-tested on malta/mipsel
>>
>> Signed-off-by: Florian Fainelli
>
On 17-09-17 07:05, Maxim Gorbachyov wrote:
> Because mktemp() is evil.
>
Hi, please add a reference when making such claims.
Thanks,
Stijn
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
On 07-10-17 14:43, Hauke Mehrtens wrote:
> What is your opinion on this topic? Am I missing some arguments?
> Currently I would prefer solution 3 going with kernel 4.9 and 4.14.
I actually preferred to have a 2nd major release in 2017, using only
kernel 4.9, and then a 3rd major release early 2018
On 25-09-17 18:43, Stijn Tintel wrote:
> On 25-09-17 00:20, Baptiste Jonglez wrote:
>> On 24-09-17, Stijn Tintel wrote:
>>> My bad. When we update a package, we bump the version in the Makefile
>>> and remove the current hash, then run "make package/foo/dowload; ma
On 08-10-17 16:20, Jason A. Donenfeld wrote:
> On Sun, Oct 8, 2017 at 3:04 PM, Jason A. Donenfeld wrote:
>> In that case, I'll take a closer look at the patches LEDE ships for
>> the package and merging them into the upstream repo.
> If you don't wind up removing that, future
On 16-10-17 13:12, Koen Vandeputte wrote:
>
>
> On 2017-10-16 11:48, Nick Lowe wrote:
>> Referencing https://www.krackattacks.com/
>>
>> Patches can be found at: https://w1.fi/security/2017-1/ and an
>> advisory at http://seclists.org/oss-sec/2017/q4/83
>>
>> Patches can also be found committed at
On 16-10-17 13:15, Stijn Tintel wrote:
> On 16-10-17 13:12, Koen Vandeputte wrote:
>>
>> On 2017-10-16 11:48, Nick Lowe wrote:
>>> Referencing https://www.krackattacks.com/
>>>
>>> Patches can be found at: https://w1.fi/security/2017-1/ and an
>>>
On 04-09-17 18:07, Koen Vandeputte wrote:
> - Deleted upstreamed patches & parts
> - Refreshed all
>
> Compile tested: full-option package + tools (hostapd + wpa_supplicant)
>
Does this actually compile without modifying libubox? I have a similar
update queued in my staging tree [1], but it fails
On 05-09-17 10:22, Koen Vandeputte wrote:
>
> On 2017-09-05 08:23, Stijn Tintel wrote:
>> On 04-09-17 18:07, Koen Vandeputte wrote:
>>> - Deleted upstreamed patches & parts
>>> - Refreshed all
>>>
>>> Compile tested: full-option package + tools
On 05-09-17 10:37, Stijn Tintel wrote:
> On 05-09-17 10:22, Koen Vandeputte wrote:
>> On 2017-09-05 08:23, Stijn Tintel wrote:
>>> On 04-09-17 18:07, Koen Vandeputte wrote:
>>>> - Deleted upstreamed patches & parts
>>>> - Refreshed all
>>>>
On 24-09-17 23:57, Baptiste Jonglez wrote:
> Hi,
>
> On 24-09-17, Stijn Tintel wrote:
>> On 03-09-17 15:01, Baptiste Jonglez wrote:
>>> Note: if some users of scripts/download.pl knowingly provide an empty hash
>>> because they don't need checksum verification
On 03-09-17 15:01, Baptiste Jonglez wrote:
> From: Baptiste Jonglez
>
> Currently, if the provided hash is unsupported (length different from 32
> or 64 bytes), we happily download the requested file without any kind of
> checksum verification.
>
> This is quite dangerous
Since version 8.0, gdbserver seems to have a hard dependency on
libstdc++, even with --disable-libstdcxx.
Fixes CVE-2017-9778.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
V2: add hard dependency on libstdc++
Also in my staging tree: https://git.lede-project.org/a96fc0d9
p
On 25-09-17 00:20, Baptiste Jonglez wrote:
> On 24-09-17, Stijn Tintel wrote:
>> My bad. When we update a package, we bump the version in the Makefile
>> and remove the current hash, then run "make package/foo/dowload; make
>> package/foo/check FIXUP=1". This d
On 25-09-17 20:18, Felix Fietkau wrote:
> On 2017-09-25 15:36, Stijn Tintel wrote:
>> Since version 8.0, gdbserver seems to have a hard dependency on
>> libstdc++, even with --disable-libstdcxx.
>>
>> Fixes CVE-2017-9778.
>>
>> Signed-off-by: Stijn Tintel
The empty version.sh script causes a problem when run by make:
make[3]: /usr/bin/env bash: Shell program not found
Adding a shebang line in version.sh seems to solve it.
Fixes FS#977.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/network/utils/iw/Makefile | 3 +--
On 30-09-17 14:56, Hauke Mehrtens wrote:
> The /bin/config_generate script and some other scripts are assuming the
> /etc/config directory exists in the image. This is true in case for
> example the package firewall, dropbear or dnsmasq are included, which
> are adding the files under
("hostapd: update to version 2017-08-24")
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
package/network/services/hostapd/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/network/services/hostapd/Makefile
b/package/network/services/hostapd/Makefile
On 28-09-17 03:14, Ben Greear wrote:
> Any idea what might be causing this?
>
>
> Configuring kmod-i2c-algo-bit.
> Configuring kmod-igb.
> Configuring ath10k-firmware-qca6174.
> Configuring ppp-mod-pppoe.
> Collected errors:
> * satisfy_dependencies_for: Cannot satisfy the following
On 27-09-17 10:31, Felix Fietkau wrote:
> On 2017-09-26 17:10, Stijn Tintel wrote:
>> On 25-09-17 20:18, Felix Fietkau wrote:
>>> On 2017-09-25 15:36, Stijn Tintel wrote:
>>>> Since version 8.0, gdbserver seems to have a hard dependency on
>>>> libstdc++,
On 03-10-17 03:31, David Lang wrote:
> note that the kernel currently under development (4.14) is tagged to
> be a LTS kernel (6 years of support), so it would be good to work on
> that if possible.
I would prefer to have a release based on 4.9 first. Many targets have
already received extensive
On 25-09-17 14:38, Stijn Tintel wrote:
> Since version 8.0, there is a dependency on libstdc++, and gdb does not
> build against uClibc++. Disable building of the libstdc++-v3, instead of
> adding a hard dependency on libstdcpp. Adding a ~350KB dependency to
> gdbserver will
-2017-9778.
Signed-off-by: Stijn Tintel <st...@linux-ipv6.be>
---
This patch is also in my staging tree:
https://git.lede-project.org/f3d16da8
package/devel/gdb/Makefile | 7 ---
package/devel/gdb/patches/110-shared_libgcc.patch
On 29-08-17 09:09, Philip Prindeville wrote:
> Hi all,
>
> I don’t know if sysupgrade is the problem, or if this is where things
> manifest.
>
> But I recently (within the last week, but I only rebase once or twice a week)
> started seeing issues with doing sysupgrade on x86_64 hardware.
>
> The
On 18-10-17 01:40, Aaron Z wrote:
> On Tue, Oct 17, 2017 at 3:24 AM, Felix Fietkau wrote:
>> On 2017-10-17 01:53, Jim Gettys wrote:
>>> Will this require a upgrade of the base image, or can we just upgrade
>>> packages? If so,
>>> which ones?
>>>
On 18-10-17 14:20, Aaron Z wrote:
> On Tue, Oct 17, 2017 at 10:28 PM, Stijn Tintel <st...@linux-ipv6.be> wrote:
>> On 18-10-17 01:40, Aaron Z wrote:
>>> On Tue, Oct 17, 2017 at 3:24 AM, Felix Fietkau <n...@nbd.name> wrote:
>>>> On 2017-10-17 01:53,
different options? Or is that too much assumption?
Either way:
Tested-by: Stijn Tintel <st...@linux-ipv6.be>
Stijn
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
The LEDE Community is proud to announce the fourth service release of
stable LEDE 17.01 series.
LEDE 17.01.4 “Reboot” incorporates a fair number of fixes back ported
from the development branch during the last two weeks.
---
Some selected highlights of the service release are:
Linux kernel
unctionality. I keep running into this breakage when
using the script to bump kernel version, or when bumping packages I
maintain. While I agree that adding another knob seems cumbersome, I
would like to be able to use the broken functionality, so
Acked-by: Stijn Tintel <s
On 26-10-17 11:50, Baptiste Jonglez wrote:
> When the new "--skip-hash" option is passed to scripts/download.pl, hash
> verification of the downloaded files is completely skipped. This can be
> useful when bumping package version, since the hash may not be known in
> advanc
> + [ -z "$hostname" ] && hostname="$(cat /proc/sys/kernel/hostname)"
> [ "$broadcast" = 1 ] && broadcast="-B" || broadcast=
> [ "$release" = 1 ] && release="-R" || release=
> [ -n "$client
On 07-12-17 12:04, Timo Sigurdsson wrote:
> Hi,
>
> Stijn Tintel schrieb am 07.12.2017 01:35:
>
>> On 14-11-17 21:41, Timo Sigurdsson wrote:
>>> Increase PKG_RELEASE after latest changes to hostapd, so downstream
>>> users can fetch updates via opkg.
>&
an issue a
>
> "make package/mypackage/download PKG_HASH=none"
>
> to download ignoring the Makefile checksum while preserving the error
> semantics of unset PKG_HASH cases.
>
> Ideally I'd like to push the "none" variant but wanted to share
On 14-11-17 21:41, Timo Sigurdsson wrote:
> Increase PKG_RELEASE after latest changes to hostapd, so downstream
> users can fetch updates via opkg.
>
You should have bumped PKG_RELEASE in the previous commit. I've done
that in my staging tree.
Thanks,
Stijn
On 09-05-18 03:03, Etienne Champetier wrote:
> Hi All,
>
> 2018-01-18 13:59 GMT-08:00 Etienne Champetier :
>> Hi All,
>>
>> Could someone enable this https://github.com/integration/dco on the
>> whole OpenWrt github org? (or at least on the packages repo)
> Friendly
On 21-01-18 19:21, Jo-Philipp Wich wrote:
> Hi,
>
> ACK from me as well.
>
>> ACK to enable it for packages, not sure if it makes sense for core as we
>> enforce this in the project git repo already, and Github is just a mirror.
> It does make sense to provide immediate feedback on Github pull
On 09-02-18 01: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:
On 19-01-18 15:02, Piotr Dymacz wrote:
>
>
> On 19.01.2018 13:09, Etienne Champetier wrote:
>
>> We can also make it mandatory (show "required" on the fail test line)
>> Also this is a good minimum check to have on ALL repo
>> There are many ways to do it, enabling DCO is a 2 minutes job (if
>>
1 - 100 of 102 matches
Mail list logo