ibc code.
Commit 60c1f0f64d23 is from 13. Oct 2006.
Hauke
>> On Feb 15, 2018, at 3:52 PM, Hauke Mehrtens wrote:
>>
>> Remove this old patch which prevents showing the xfrm ports for SCTP
>>
>> This was added in commit 60c1f0f64d23 ("finally move buildroot-ng to t
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
On 02/18/2018 11:21 PM, Andrey Jr. Melnikov wrote:
> Fix this patch before release. Or drop it if no one has seen this damage and
> does not complain.
Hi Andrey,
What is the problem with this patch?
Hauke
>
>> Hauke Mehrtens wrote:
>>> This modifies the patches in a
This updates musl from a commit between 1.1.18 and 1.1.19 to the final
release of the version 1.1.19.
Signed-off-by: Hauke Mehrtens
---
toolchain/musl/common.mk | 8 +--
...suppress-some-more-Linux-uapi-definitions.patch | 59 --
.../musl/patches
On 02/17/2018 03:25 PM, Hauke Mehrtens wrote:
> Hi,
>
> I would like to use kernel 4.14 by default on the mvebu target soon.
> If you are aware of any regressions compared to kernel 4.9 then please
> report them, now.
>
> I only have a Linksys device here for testing and
this is only compile tested.
Fixes: f791fb4af450 ("kernel: add linux 4.9 support")
Fixes: b3f95490b9be ("kernel: generic: Add kernel 4.14 support")
Reported-by: Andrey Jr. Melnikov
Signed-off-by: Hauke Mehrtens
---
.../680-NET-skip-GRO-for-foreign-MAC-addresses
On 02/26/2018 02:16 PM, Henrique de Moraes Holschuh wrote:
> FWIW, I had issues with the ath10k-firmware currently in OpenWRT master,
> it would crash with 100% reproducibly in TP-Link Archer C60v2 (there is
> already a PR open adding support for this device).
>
> These issues are fixed in the new
Hi Linus,
[adding lede-dev]
Nice work, for this patch and especially for upstreaming the code into
mainline Linux.
On 02/26/2018 09:28 PM, Linus Walleij wrote:
> Hi,
>
> I have a forward-port hack-ish thing for Gemini,
> this 500K patch on top of openwrt HEAD:
>
> https://dflund.se/~triad/krad/
On 02/27/2018 10:45 PM, Linus Walleij wrote:
> On Tue, Feb 27, 2018 at 4:46 PM, Hauke Mehrtens wrote:
>
>>> I have a forward-port hack-ish thing for Gemini,
>>> this 500K patch on top of openwrt HEAD:
>>>
>>> https://dflund.se/~triad/krad/gemi
On 03/04/2018 11:39 AM, Peter Denison wrote:
> When migrating a package from the unmaintained 'oldpackages' feed to the
> main 'packages' feed:
>
> 1) Should I try to preserve history? If so, how do I do that on just one
> directory (my git-fu is not that good)?
No this is not needed, you can add
n the OpenWrt master branch. Can you
please send a patch which adds the additional settings to the device
tree on top of the current OpenWrt master branch.
Hauke
>
> On Fri, Dec 29, 2017 at 01:53:46PM +0100, Hauke Mehrtens wrote:
>> Hi antony,
>>
>> On 12/28/2017 06:21 P
On 02/28/2018 11:34 AM, Marek Behun wrote:
> Hello,
>
> the mt7530 switch driver is now in mainline kernel as a DSA driver. The
> LEDE ramips target ethernet driver though doesn't use it yet, and I've
> been thinking what all would have to be done to port the ethernet
> driver to use it, if it eve
On 02/27/2018 11:37 AM, Rafał Miłecki wrote:
> There has been some talk on upcoming 17.01 fix release and Meltdown/Spectre.
>
> Quick summary:
> 1) Most of LEDE supported devices aren't affected
> 2) For most LEDE use cases these vulnerabilities don't matter
> 3) 17.01 uses 4.4.116 which includes
On 02/16/2018 01:46 PM, John Crispin wrote:
> Hi,
>
> whats on the critical todo list for the upcoming release ? i still have
> a few minor things that I'll be adding shortly, apart from that I am
> currently not aware of any huge problems. the release will be a mix
> between 4.9 and 4.14 afaik !?
On 03/04/2018 04:40 PM, Felix Fietkau wrote:
> On 2018-03-04 16:15, Hauke Mehrtens wrote:
>> There is also a pull request for busybox 2.28.1 at github, this will
>> probably also introduce some more regressions, so I am not sure if we
>> should take it before or after
and update of
packages depending on mbedtls to handle the changed ABI.
Signed-off-by: Hauke Mehrtens
---
package/libs/mbedtls/Makefile | 4 +-
package/libs/mbedtls/patches/200-config.patch | 83 ---
package/libs/ustream-ssl/Makefile | 2
On 03/04/2018 06:40 PM, Rosen Penev wrote:
> I would like this to be backported to 17.01 as well. The mentioned
> Archer C7v2 runs 17.01. No impact between 17.01 and master.
>
> On Sun, Mar 4, 2018 at 9:31 AM, Rosen Penev wrote:
>> This reverts commit 8d755ef052dca29db3b8da74149d9c7d74a54842.
>>
On 03/04/2018 07:44 PM, Florian Fainelli wrote:
> +Jonas,
>
> On 03/04/2018 05:09 AM, TheWerthFam wrote:
>> Full kernel log below. I remove the 8192cu wifi driver since it doesn't
>> work in AP mode and use a rt2800 base usb dongle.. Additionally grep
>> output of config-4.14 for SWCONFIG
>> grep
et/Articles/634787/
>>>
>>> Anything else I can do to diagnose?
>> Well, we were facing these problems quite some time ago with armbian.
>> Some time around kernel 4.8 or 4.9, the DSA version of a b53 driver got
>> into mainline kernel, so swconfig didn't
Hi,
I tried to make the crappy Realtek rtl8189fs/rtl8189es/rtl8723bs wifi
drivers work in OpenWrt, but gave up for now. I just want to write my
current observations.
When OpenWrt finds a nl80211 compatible wifi device it deletes all the
existing virtual interfaces and then creates the configured
On 03/12/2018 09:48 PM, Arjen de Korte wrote:
> Citeren Felix Fietkau :
>
>> On 2018-03-12 21:02, Arjen de Korte wrote:
>>> Citeren LEDE Commits :
>>>
nbd pushed a commit to openwrt/openwrt.git, branch master:
https://git.lede-project.org/e28551b103f4999b36d3725a23b59f507830f48a
>
.
This should fix the compile problems seen in build bot from time to time
by not depending on the host libssl-dev package any more but using the
LibreSSL version from OpenWrt.
Signed-off-by: Hauke Mehrtens
---
package/boot/uboot-mxs/Makefile| 2 +-
.../uboot-mxs/patches/001-add
On 03/17/2018 12:34 PM, Michael Heimpold wrote:
> Hi Hauke,
>
> some comments below.
>
> Am Freitag, 16. März 2018, 19:05:10 CET schrieb Hauke Mehrtens:
>> Use the UBOOT_MAKE_FLAGS defined in include/u-boot.mk and do not
>> overwrite them to compile the host tools a
On 03/16/2018 01:53 AM, Rosen Penev wrote:
> Some boards like the Turris Omnia have an RTC chip that does not get
> initialized. Initializing the RTC at the driver level helps get rid of
> bootloader hacks that write special register values.
Please line break your commit message.
Will you send
also true for the other devices.
Signed-off-by: Hauke Mehrtens
---
...s-armada-385-linksys-Disable-internal-RTC.patch | 28 ++
1 file changed, 28 insertions(+)
create mode 100644
target/linux/mvebu/patches-4.14/010-ARM-dts-armada-385-linksys-Disable-internal-RTC.patch
diff
Hi,
After the upgrade to GCC 7.3 the kernel on the apm821xx target gets too
big for the meraki_mr24 device and the build in build bot is failing.
Could you please have a look at this problem:
http://phase1.builds.lede-project.org/builders/apm821xx%2Fnand
Hauke
___
[forwarded from the OpenWrt mailing list]
Hi Everyone,
It's official, OpenWrt Summit will be in Lisbon, Portugal on October
29th & 30th! We can't wait to see you there.
The CFP is open until May 15th - https://www.papercall.io/openwrtsummit2018
You can submit 20 or 40 minute talks, and 2 or 4
automatically load the depended modules like mac80211.
Fixes: 3888e77c1c68 ("ath10k-ct driver: use dma_alloc_coherent, 4.13 based
driver")
Fixes: 23a388fe41ec ("ath10k-ct: Force loading mac80211 and ath modules.")
Signed-off-by: Hauke Mehrtens
---
package/kernel/ath10k-ct/Makefil
On 03/29/2018 07:11 PM, Evgeniy Didin wrote:
> Hello,
>
> Trying to add support of drivers/net/wireless/rsi/rsi91x driver in mac80211
> we faced with problem,
> that the version of backports is quite old(2017-11-01), and at least one
> significant commit for rsi91x was later than this version:
>
On 03/29/2018 09:55 PM, Sebastian Fleer wrote:
> After building coreboot myself, I discovered that the board names
> changed again - they now seem to be the same as before.
> https://github.com/pcengines/coreboot/commit/3578e9fb6dac753ec9365c88a8556ca1b90a8deb
>
>
> I guess the "PC Engines apuX"
s-armada-385-linksys-Disable-internal-RTC.patch
+++
b/target/linux/mvebu/patches-4.14/423-ARM-dts-armada-385-linksys-Disable-internal-RTC.patch
@@ -17,7 +17,7 @@ Signed-off-by: Hauke Mehrtens
--- a/arch/arm/boot/dts/armada-385-linksys.dtsi
+++ b/arch/arm/boot/dts/armada-385-linksys.dtsi
-@@
These functions are not declared in any header file and only used in
same compile unit, mark them as static to remove one gcc warning and
make it easier for the compiler to optimize them out.
Signed-off-by: Hauke Mehrtens
---
.../utils/mtd-utils/patches/130-lzma_jffs2.patch | 38
/lantiq/xrx200/packages/ubi-utils_2.0.1-1_mips_24kc.ipk
Signed-off-by: Hauke Mehrtens
---
package/utils/mtd-utils/Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/utils/mtd-utils/Makefile b/package/utils/mtd-utils/Makefile
index cf0983164a..806bba8a4f 100644
--- a/package
This fixes some minor security problems.
Signed-off-by: Hauke Mehrtens
---
package/libs/mbedtls/Makefile | 4 +--
package/libs/mbedtls/patches/200-config.patch | 36 +--
2 files changed, 20 insertions(+), 20 deletions(-)
diff --git a/package/libs
-1_mips_24kc.ipk
24114 bin/packages/mips_24kc/base/libnl-nf_3.4.0-1_mips_24kc.ipk
131134 bin/packages/mips_24kc/base/libnl-route_3.4.0-1_mips_24kc.ipk
Signed-off-by: Hauke Mehrtens
---
package/libs/libnl/Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/libs/libnl/Makefile b/package/libs
If the package doe not contain a PKG_HASH just skip the check instead of
making the download fail. The scripts/download.pl script will
automatically skip the hash check in case the hash value equals skip,
otherwise it fails.
Signed-off-by: Hauke Mehrtens
---
include/download.mk | 4 ++--
1 file
* Refreshed patches.
* Deleted 210-Revert-led-core-Fix-brightness-setting-when-setting-.patch (was
accepted upstream)
* Deleted 812-pci-dwc-fix-enumeration.patch (was accepted upstream)
Compile and run tested on lantiq
Signed-off-by: Hauke Mehrtens
---
include/kernel-version.mk
This now makes sure that the beginning of the version number gets checked
and "4.4.5" will not match was a supported version.
GCC 8 and GCC 9 are now marked as supported, but we probably have to fix
some problems for them.
Closes: FS#1433
Signed-off-by: Hauke Mehrtens
---
incl
should
CVE-2018-1050: Denial of Service Attack on external print server.
Signed-off-by: Hauke Mehrtens
---
package/network/services/samba36/Makefile | 2 +-
.../samba36/patches/028-CVE-2016-2125-v3.6.patch | 59 +
...494-v3-6.patch => 029-CVE-2017-7494-v3-6.patch} | 0
.
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
On 02/16/2018 01:46 PM, John Crispin wrote:
> Hi,
>
> whats on the critical todo list for the upcoming release ? i still have
> a few minor things that I'll be adding shortly, apart from that I am
> currently not aware of any huge problems. the release will be a mix
> between 4.9 and 4.14 afaik !?
On 04/02/2018 11:28 AM, Gio wrote:
> On Wednesday, 14 June 2017 20:41:12 CEST Daniel Golle wrote:
>> I noticed that the Linux built-in bridge now supports filtering by VLAN
>> tags. This can be much more efficient than using ebtables for the same
>> task, hence I wonder if there is any reason to ke
On 04/02/2018 10:54 AM, Jaap Buurman wrote:
> Dear Hauke,
>
> Quick question from my side: I was wondering why Ramips will probably
> stay with 4.9, even though the patches for 4.14 have been in master
> for quite a while. Since flow_offload is part of master, and it
> requires 4.14, I think 4.14
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
Signed-off-by: Hauke Mehrtens
---
include/kernel-version.mk | 4
.8.html
This increases the kernel size of an lzma compressed Lantiq xrx200
kernel by 4.774 Bytes.
Without brdige vlan:
1.771.351 bt_homehub-v5a-kernel.bin
With brdige vlan:
1.776.125 bt_homehub-v5a-kernel.bin
Signed-off-by: Hauke Mehrtens
---
target/linux/generic/config-4.14 | 2 +-
target
On 04/05/2018 11:58 AM, Syrone Wong wrote:
> Hi,
>
> I closed my PR due to
> https://github.com/openwrt/openwrt/commit/56d0dd56e9c6efa79d03b6417dc0ae5449343001.
> I tried to understand patches in tools/mtd-utils but failed. I
> appreciate if anyone keeps going.
>
>
> Best Regards,
> Syrone Wong
On 05/05/2016 08:56 AM, John Crispin wrote:
> Hi,
>
> It would be nice if there was a process in place that would allow
> community members to easily be able to test images on devices and report
> the results some place. after some time thinking of different ways to do
> this I came up with one po
On 05/04/2016 11:38 PM, Kus wrote:
> Greetings
>
> I'd like to propose that all commits (at least to master) going forward be
> signed with the commiter's gpg key.
>
> https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work
>
> Thoughts?
If we would add signed commits, it should be optional
On 05/04/2016 11:49 PM, Vittorio G (VittGam) wrote:
> Hi,
>
> On 04/05/2016 22:30:40 CEST, Bert Vermeulen wrote:
>> Hi all,
>>
>> Very happy to see this project reboot happening. An acknowledgement of
>> the issues facing OpenWRT was long overdue. I'd like some clarity on
>> some things that aren'
On 05/05/2016 10:03 PM, Bert Vermeulen wrote:
> On 05/05/2016 04:09 PM, Hauke Mehrtens wrote:
>> I think we should encourage everyone to upstream the patches, I think in
>> one of the statics I saw that OpenWrt ranked 3. or 4. in contribution to
>> the kernel among the Linux
lantiq
>> asterisk-tapi
>>
>> Regards
>>
>> On Mon, Oct 3, 2016 at 1:56 AM, Hauke Mehrtens wrote:
>>> On 09/23/2016 09:02 PM, Daniel Golle wrote:
>>>> On Fri, Sep 23, 2016 at 08:14:24PM +0200, Dennis Schneck wrote:
>>>>>
>>>
Hi Daniel,
This sounds interesting.
I have some questions regarding phase 1.
1. Do you want to have an API to switch for example a smart plug on and
off and an other call to get the temperature from a temperature sensor?
2. Should this more focus on local IoT sensors line a temperature sensor
c
>>
>> PS: many thanks to Gilles Mazoyer for his work on bcm63xx from which i
>> copied some portions of conditionals and makefile
>>
>> regards
>>
>> Eddi
>>
>> On Mon, Oct 31, 2016 at 9:47 PM, Hauke Mehrtens wrote:
>>> Thanks for the l
On 2016-12-05 11:57, Daniel Golle wrote:
Hi Felix,
On Thu, Dec 01, 2016 at 04:51:30PM +0100, Felix Fietkau wrote:
On 2016-12-01 16:38, Daniel Golle wrote:
> Hi Felix,
>
> On Thu, Dec 01, 2016 at 04:12:38PM +0100, Felix Fietkau wrote:
>> On 2016-12-01 16:05, Daniel Golle wrote:
>> > I was follow
This makes it possible to activate the gpio and the pinctl debugging
from LEDE menuconfig.
Signed-off-by: Hauke Mehrtens
---
config/Config-kernel.in | 8
1 file changed, 8 insertions(+)
diff --git a/config/Config-kernel.in b/config/Config-kernel.in
index d8ca76c..3c69c86 100644
--- a
This just adds the kmods for these kernel modules.
This is found on some Lantiq / Intel reference boards.
Signed-off-by: Hauke Mehrtens
---
package/kernel/linux/modules/hwmon.mk | 30 ++
1 file changed, 30 insertions(+)
diff --git a/package/kernel/linux/modules
On 12/08/2016 02:00 PM, John Crispin wrote:
>
>
> On 07/12/2016 22:45, Hauke Mehrtens wrote:
>> This just adds the kmods for these kernel modules.
>> This is found on some Lantiq / Intel reference boards.
>>
>> Signed-off-by: Hauke Mehrtens
>> ---
>>
This was introduced in kernel 4.4, but broken there and fixed in 4.5.
I would like to activate it, but I am scared about the boot loader
around giving us all sorts of command lines.
Signed-off-by: Hauke Mehrtens
---
.../patches-4.4/094-MIPS-Fix-macro-typo.patch | 33
On 12/09/2016 08:08 AM, John Crispin wrote:
>
>
> On 09/12/2016 00:21, Hauke Mehrtens wrote:
>> This was introduced in kernel 4.4, but broken there and fixed in 4.5.
>> I would like to activate it, but I am scared about the boot loader
>> around giving us all sorts of
These options are needed to create /dev/mem or /dev/kmem .
/dev/mem is needed by the io tool to access raw hardware memory, which
is helpful when debugging and developing drivers.
Signed-off-by: Hauke Mehrtens
---
config/Config-kernel.in | 14 ++
1 file changed, 14 insertions
We had multiple meetings to find a solution to solve the problems
between the OpenWrt and the LEDE project and to discuss a possible
merge. Everyone with commit access to LEDE and all OpenWrt core
developers were invited to these meetings. We had productive and
friendly discussions about the proble
On 12/25/2016 07:12 PM, Martin Blumenstingl wrote:
> Hi John, Hi Hauke,
>
> On Fri, Dec 9, 2016 at 8:08 AM, John Crispin wrote:
>>
>>
>> On 09/12/2016 00:21, Hauke Mehrtens wrote:
>>> This was introduced in kernel 4.4, but broken there and fixed in 4.5.
&g
On 12/28/2016 09:41 PM, Ben Mulvihill wrote:
> On Wed, 2016-12-28 at 19:26 +, Mohammed Berdai wrote:
>> Hi,
>>
>> I managed to test the latest LEDE commits after missing daily tests for a
>> few weeks due to a busy schedule.
>>
>> The switch to dwc2 module caused kernel panics on ARV4518pw,
Hi,
It looks like the kernel prefers the console parameter given in the boot
command line over the stdout-path parameter. On some boards the boot
loader provides this parameter to the kernel and then the serial does
not work. At least the VR200v, ARV4518pw and ARV7518pw are affected:
https://bugs.
On 01/01/2017 11:21 AM, Mathias Kresin wrote:
> The clock source is set by the ltq-hcd driver but are not by the
> dwc2 driver. Without having the correct clock set the dwc driver
> fails to reset the usb core and errors out. The values for supported
> lantiq targets are exactly the same as set b
using stdout-path instead of cmdline argument
Signed-off-by: Hauke Mehrtens
---
target/linux/lantiq/dts/ACMP252.dts | 4
target/linux/lantiq/dts/ARV4510PW.dts | 4
target/linux/lantiq/dts/ARV4518PWR01.dtsi | 4
target/linux/lantiq/dts/ARV4519PW.dts | 4
target
This makes the code use the same settings aas the vendor sdrivers.
Signed-off-by: Hauke Mehrtens
---
target/linux/lantiq/dts/amazonse.dtsi | 3 +-
target/linux/lantiq/dts/ar9.dtsi | 6 +-
target/linux/lantiq/dts/danube.dtsi| 2 +-
target
On 01/06/2017 08:26 PM, Martin Blumenstingl wrote:
> Hi Hauke,
>
> (CC'ing Mathias as he was looking into some of the USB issues as well)
>
> On Fri, Jan 6, 2017 at 8:06 PM, Hauke Mehrtens wrote:
>> This makes the code use the same settings aas the vendor sdrivers
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.
On 01/06/2017 08:19 PM, Philip Prindeville wrote:
_
On 01/06/2017 11:31 PM, Antti Seppälä wrote:
> On 6 January 2017 at 21:32, Hauke Mehrtens wrote:
>> On 01/06/2017 08:26 PM, Martin Blumenstingl wrote:
>>> Hi Hauke,
>>>
>>> (CC'ing Mathias as he was looking into some of the USB issues as well)
>
On 01/07/2017 12:25 PM, Antti Seppälä wrote:
> On 7 January 2017 at 04:01, Hauke Mehrtens wrote:
>> On 01/06/2017 11:31 PM, Antti Seppälä wrote:
>>> On 6 January 2017 at 21:32, Hauke Mehrtens wrote:
>>>> On 01/06/2017 08:26 PM, Martin Blumenstingl wrote:
>&
and the vendor Code base.
Signed-off-by: Hauke Mehrtens
---
If some of these dwc2 values should be changed, please suggest changes,
I am not an expert on this.
This was only tested on vrx200 devices not on any other SoC, please
test and report back, I would like to get this into the next release
On 01/07/2017 07:29 PM, Hauke Mehrtens wrote:
> This adds USB initialization fixes for Danube, Amazon SE and xrx300 and
> should fix the clock on at least Danube which hopefully fixes FS#351.
>
> The xrx200 usb driver now uses more memory for the dwc2 fifos, this was
> increa
On 01/07/2017 07:51 PM, Hauke Mehrtens wrote:
> On 01/07/2017 07:29 PM, Hauke Mehrtens wrote:
>> This adds USB initialization fixes for Danube, Amazon SE and xrx300 and
>> should fix the clock on at least Danube which hopefully fixes FS#351.
>>
>> The xrx200 usb driver n
rxkad will be build into af-rxrpc now and is of type boolean.
Signed-off-by: Hauke Mehrtens
---
package/kernel/linux/modules/netsupport.mk | 4 ++--
target/linux/generic/config-4.9| 3 +++
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/package/kernel/linux/modules
From: Hauke Mehrtens
This combines the usage of external kernel tree with the cloning of the
kernel tree form git. The new kernel will be cloned into an external
directory and then used from there.
Signed-off-by: Hauke Mehrtens
---
include/kernel-defaults.mk | 17 +++--
1 file
Hi Felix,
On 2017-02-28 07:11, Felix Fietkau wrote:
On 2017-02-20 15:10, Mehrtens, Hauke wrote:
When I compile MIPS malta with the LEDE patches on kernel 4.9 I get
this error in the kernel build:
CC arch/mips/boot/compressed/decompress.o
OBJCOPY arch/mips/boot/compressed/vmlinux.bin
On 03/03/2017 09:12 PM, Philip Prindeville wrote:
> I dug into this… Problem was with CONFIG_EXTRA_OPTIMIZATION having “-fno-plt”
> in it.
>
> This was being passed into the ‘gcc’ that was being used to bootstrap gcc.
>
> Wondering if that’s not a bug.
>
> Shouldn’t the build of the cross-gcc i
On 05/06/2016 05:05 PM, Daniel Dickinson wrote:
> Hi all,
>
> I have noticed that some of the policies of this project are already
> veering towards a brand of technical elitism that I feel is completely
> contrary to the stated goal of having a stronger community.
>
> A strong community welcom
On 05/06/2016 05:05 PM, Daniel Dickinson wrote:
> Hi all,
>
> I have noticed that some of the policies of this project are already
> veering towards a brand of technical elitism that I feel is completely
> contrary to the stated goal of having a stronger community.
>
> A strong community welcom
On 05/06/2016 10:04 AM, Bruno Randolf wrote:
> Hi,
>
> Taking this from lede-adm to lede-dev where I'm allowed to post...
no problem.
> On 06/05/16 02:33, Alexander Couzens wrote:
>>> +== What devices does LEDE targets?
>>> +
>>> +LEDE mainly targets embedded devices capable of running Linux.
Hi John,
How does the Lantiq NAND sysupgrade stuff work?
I see there are sysupgrade packages with a squasfs and a ubifs root file
system. Are both file systems still supported and needed? I see that
other targets only have a squasfs support.
Do the devices with NAND flash all use UBI by default
On 05/09/2016 10:19 PM, Bjørn Mork wrote:
> Rafał Miłecki writes:
>
>> -# Copyright (C) 2007 OpenWrt.org
>> +# Copyright (C) 2016 LEDE project
>
I am not a lawyer and the following statements could be wrong.
> I've always wondered about the OpenWrt copyright assigment process, and
> this looks
Hi,
On 05/21/2016 07:35 AM, Dirk Neukirchen wrote:
> wolfssl has a fine grained feature and compatibility control
> for compiling stunnel, lighthttp or (partly) openssl dropin
> ustream-ssl uses features that require normally
> HAVE_SNI, HAVE_STUNNEL and the openssl compatibility headers
>
> ar7
Hi,
On 05/21/2016 10:07 AM, Michał Osowiecki wrote:
> Cisco RV042G is Cavium based router with BCM53125 switch and BCM54612E
> connected to port 8, and port 5 acts as cpu port. Probably Linksys
> LRT214 and LRT224 will be affected by this patch too (boards are
> identical).
> I don't know if there
add lede-dev
On 05/24/2016 10:31 PM, Hauke Mehrtens wrote:
> Hi,
>
> As it looks like the IRC meeting will not happen, because not so big
> interest by the people not already involved in LEDE and problems finding
> a time, lets discuss on the mailing list like suggested by Jow.
&g
On 05/27/2016 01:43 AM, Delbar Jos wrote:
> Hi all,
>
> At Technicolor we have followed with great interest the recent proposals to
> enhance OpenWrt with an open source solution for TR-069 remote management. As
> one of the world's largest vendors of modems and routers for carrier
> applicatio
On 05/27/2016 12:43 PM, David Lang wrote:
> On Thu, 26 May 2016, Delbar Jos wrote:
>
>> We are conscious of the fact that together with the proposals made by
>> Felix, Luka and Wojtek we are now looking at many "competing"
>> proposals. As a next step, we recommend to organize a workshop, at a
>>
On 05/28/2016 03:36 PM, Dave Taht wrote:
> On Sat, May 28, 2016 at 5:34 AM, Hauke Mehrtens wrote:
>> On 05/27/2016 12:43 PM, David Lang wrote:
>>> On Thu, 26 May 2016, Delbar Jos wrote:
>>>
>>>> We are conscious of the fact that together with the proposals
On 06/01/2016 12:30 AM, Alexander Couzens wrote:
> On Tue, 31 May 2016 22:46:11 +0200
> Oswald Buddenhagen wrote:
>
>> you're undoing work by hauke et. al from just a few weeks ago. ;)
> ooops. ;P
Not really, I was converting this to the new image build system. This is
just a minor change.
I th
Hi Daniel,
I work on creating an OpenWrt image which I can just flash over an UGW
(Lantiq's/Intel's OpenWrt distribution) distribution with the normal
U-Boot. Then you do not have to touch the bootloader or the flash layout
and can just run OpenWrt. UGW is mostly focused on NAND flash based
device
header at the same position
as in that kernel and add our own at the end. The kernel should not
have a problem when there are some additional members and just ignore
them.
Signed-off-by: Hauke Mehrtens
---
.../520-squashfs_update_xz_comp_opts.patch | 25 --
.../520
Signed-off-by: Hauke Mehrtens
---
.../492-try-auto-mounting-ubi0-rootfs-in-init-do_mounts.c.patch | 3 ++-
.../492-try-auto-mounting-ubi0-rootfs-in-init-do_mounts.c.patch | 3 ++-
.../492-try-auto-mounting-ubi0-rootfs-in-init-do_mounts.c.patch | 5 +++--
3 files changed, 7
In company networks everything except the http and https protocol is
often causes problems, because the network administrators try to block
everything else. To make it easier to use LEDE in company networks use
the https/http protocol for git access when possible.
Signed-off-by: Hauke Mehrtens
On 06/22/2016 06:01 PM, Conor O'Gorman wrote:
> On 21/06/16 21:05, Hauke Mehrtens wrote:
>> In the upstream kernel and the upstream squashfs4 tools the xz
>> compression header looks the following:
>> struct disk_comp_opts {
>> __le32 dictionar
From: Hauke Mehrtens
Extract the other p54 firmware files into the prism54-firmware package.
Signed-off-by: Hauke Mehrtens
---
package/firmware/prism54-firmware/Makefile | 75 --
package/kernel/mac80211/Makefile | 48 ++-
2 files changed
From: Hauke Mehrtens
Instead of downloading the firmware for prism54 devices in the
wireless.mk do it in an extra package Makefile. To ship the complete
source code Intel ships our modified OpenWrt/LEDE + the content of the
dl directory. We do not want to have any files in the dl/ directory
From: Hauke Mehrtens
The libmagic shipped with RedHat 5 does not define
MAGIC_NO_CHECK_COMPRESS and MAGIC_NO_CHECK_COMPRESS. e2fsprogs should
check for that otherwise the build will fail.
Signed-off-by: Hauke Mehrtens
---
tools/e2fsprogs/patches/010-old-libmagic.patch | 11 +++
1 file
From: Hauke Mehrtens
This adds this commit from normal libnl to libnl-tiny:
https://github.com/tgraf/libnl/commit/2dbc1ca76c5b82c40749e609eb83877418abb006
commit 2dbc1ca76c5b82c40749e609eb83877418abb006
Author: dima
Date: Wed Oct 13 17:53:34 2010 +0300
Generic Netlink multicast groups
On 06/30/2016 08:15 AM, Dirk Neukirchen wrote:
> On 29.06.2016 23:14, Hauke Mehrtens wrote:
>> From: Hauke Mehrtens
>>
>> The libmagic shipped with RedHat 5 does not define
>
> As a reference - RHEL4: Mar/2017, RHEL5:Nov/2020
> src: https://access.redhat.com/supp
301 - 400 of 453 matches
Mail list logo
