On 06/10/2017 03:13 PM, Hauke Mehrtens wrote:
> Hi,
>
> As many already acknowledged this proposal I would like to call for an
> official vote among the LEDE committers till 14.6.2017 on this proposal.
> I counted the following replays to the proposal already as an
> acknow
On 06/26/2017 11:59 PM, Hauke Mehrtens wrote:
> On 06/10/2017 03:13 PM, Hauke Mehrtens wrote:
>> Hi,
>>
>> As many already acknowledged this proposal I would like to call for an
>> official vote among the LEDE committers till 14.6.2017 on this proposal.
>> I cou
Some days ago I received an invitation from the Bundesamt für Sicherheit
in der Informationstechnik (BSI) (English: Federal Office for
Information Security) to a kickoff meeting regarding the “Technische
Richtlinie Breitband-Router” (English: Technical guideline broadband
router) in Bonn, Germany o
Hi,
I am working on merging the missing commits from the OpenWrt git
repository into the LEDE repository.
Here is a list of all non merge commits from the OpenWrt git repository
and their corresponding LEDE commit IDs:
https://github.com/hauke/openwrt-lede-merge/blob/master/commits.csv
I only lo
On 10/22/2017 10:21 PM, Zoltan HERPAI wrote:
> From: Marek Vasut
>
> Add package with the DT compiler v1.4.1 .
>
> Signed-off-by: Marek Vasut
This package is already in the package feed:
https://github.com/openwrt/packages/blob/master/libs/dtc/Makefile
_
0644
> package/kernel/dtc/patches/0001-scripts-dtc-Update-to-version-with-overlays.patch
> create mode 100644
> target/linux/ar71xx/files/arch/mips/ath79/mach-anonabox-pro.c
> create mode 100644
> target/linux/ar71xx/files/arch/mips/ath79/mach-cf-e214n-v2.c
> create
On 10/22/2017 10:28 PM, Zoltan HERPAI wrote:
> Hi,
>
> Zoltan HERPAI wrote:
>> Hi Hauke,
>>
>> On Sun, 22 Oct 2017, Hauke Mehrtens wrote:
>>
>>> I am working on merging the missing commits from the OpenWrt git
>>> repository into the LEDE
On 10/19/2017 10:18 PM, Hauke Mehrtens wrote:
> On 10/18/2017 08:58 PM, Hauke Mehrtens wrote:
>> Hi,
>>
>> We have ELCE and the OpenWrt summit next week in Prague and a lot of
>> people will be there.
>>
>> I would like to have a meeting next Wednesday even
On 10/24/2017 09:47 PM, Hans Dedecker wrote:
> On Tue, Oct 24, 2017 at 7:17 PM, Mathias Kresin wrote:
>> 2017-10-24 16:59 GMT+02:00 Zoltan HERPAI :
>>> Hi Jo,
>>>
>>> On Tue, 24 Oct 2017, Jo-Philipp Wich wrote:
>>>
Hi,
comments inline.
> Signed-off-by: Imre Kaloz
On 10/23/2017 12:55 AM, Hauke Mehrtens wrote:
> On 10/19/2017 10:18 PM, Hauke Mehrtens wrote:
>> On 10/18/2017 08:58 PM, Hauke Mehrtens wrote:
>>> Hi,
>>>
>>> We have ELCE and the OpenWrt summit next week in Prague and a lot of
>>> people will be there
On 10/26/2017 09:05 PM, Dave Taht wrote:
> Hannu Nyman writes:
>
>> Zoltan HERPAI kirjoitti 26.10.2017 klo 18:41:
>>> + -
>>> + * 2 oz. Orange Juice Combine all juices in a
>>> + * 2 oz. Pineapple Juice tall glass filled with
>>
Thanks for this good work Zoltan, this is not any easy patch.
On 11/04/2017 07:04 PM, Zoltan HERPAI wrote:
> Given that we've decided to sail under the same flag for
> the benefit of the whole community, and acknowledge the
> achievements of the LEDE project, let's start the final
> steps of the m
ssid
> merge: packages: update branding in core packages
> merge: busybox: update CONFIG_NSLOOKUP in busybox config and
> respective patch
> merge: uhttpd: update cert generation to match system defaults
> merge: etc: update remaining files
Acked-by: Hauke Mehrtens
On 11/22/2017 07:14 PM, Shankar Unni wrote:
> Just enquiring about the status of Linux 4.14 support for LEDE/OpenWrt,
> now that it's been released and gone into the LTS phase (i.e. is it
> being worked on by anyone currently?).
>
> Much thanks in advance,
Hi Shankar,
I am currently working on k
On 11/18/2017 04:29 PM, Noah Meyerhans wrote:
> Hi John. Thanks for sending this summary and working on the re-merge. I
> have a couple of questions based on your summary. I haven't tracked the
> remerge effort in detail, so please forgive me if these have already
> been covered.
>
> On Tue, Nov 0
The OpenWrt and the LEDE project are happily announcing the unification
of both projects under the OpenWrt name.
After long and sometimes slowly moving discussions about the specifics
of the re-merge, with multiple similar proposals but little subsequent
action, we're happy to announce that both p
On 01/08/2018 06:57 AM, Felix Fietkau wrote:
>
>
>> On 8. Jan 2018, at 10:31, Florian Fainelli wrote:
>>
>> When building with an external kernel tree, do not check the different
>> platform files since this is almost guaranteed they are going to differ.
>>
>> Signed-off-by: Florian Fainelli
>
On 01/17/2018 08:41 PM, Zoltan HERPAI wrote:
> Signed-off-by: Zoltan HERPAI
> ---
> package/firmware/linux-firmware/x86.mk | 9 +
> 1 file changed, 9 insertions(+)
> create mode 100644 package/firmware/linux-firmware/x86.mk
>
> diff --git a/package/firmware/linux-firmware/x86.mk
> b/pa
On 01/18/2018 01:51 PM, Nick Lowe wrote:
> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
> properly address this? There are fixes to mitigate Spectre.
We even need a patch for GCC which will be in GCC 8 and 7.3.
For master we should backport it to GCC 5.5, but what do we want
On 01/18/2018 11:41 PM, Zoltan HERPAI wrote:
>
>
> On Thu, 18 Jan 2018, Hauke Mehrtens wrote:
>
>> On 01/18/2018 01:51 PM, Nick Lowe wrote:
>>> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
>>> properly address this? There are fixes to
On 02/09/2018 09:46 PM, Philip Prindeville wrote:
>
>
>> On Jan 18, 2018, at 2:15 PM, Hauke Mehrtens wrote:
>>
>> On 01/18/2018 01:51 PM, Nick Lowe wrote:
>>> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to
>>> properly address
On 02/01/2018 11:35 PM, Tim Harvey wrote:
> Signed-off-by: Tim Harvey
> ---
> target/linux/generic/config-4.14 | 9 -
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/target/linux/generic/config-4.14
> b/target/linux/generic/config-4.14
> index fa389bf..89f2f43 100644
>
Hi Tim,
sorry that I haven't reviewed this earlyer, but now I saw some problems,
see my comments inline.
Can you please create a follow up patch based on current master branch.
On 01/24/2018 12:15 AM, Tim Harvey wrote:
> The Cavium OCTEON TX is an ARM 64-bit SoC leveraging CPU cores and
> peripe
On 02/13/2018 09:46 PM, Hauke Mehrtens wrote:
> Hi Tim,
>
> sorry that I haven't reviewed this earlyer, but now I saw some problems,
> see my comments inline.
>
> Can you please create a follow up patch based on current master branch.
>
> On 01/24/2018 12:15 AM, Ti
On 02/15/2018 05:34 PM, Tim Harvey wrote:
> Testted on a Gateworks GW54xx. Does not support enabling imx-drm modules
> yet as those will need some adjustments based on kernel configs.
>
> v3:
> - included missing patch for pcie enumeration fix
>
> v2:
> - move dwc pci patch to generic (Koen)
>
On 02/15/2018 05:34 PM, Tim Harvey wrote:
> Backport of: http://patchwork.ozlabs.org/patch/860701/
>
> Signed-off-by: Tim Harvey
> ---
> .../generic/pending-4.14/812-pci-dwc-fix-enumeration.patch| 11
> +++
> 1 file changed, 11 insertions(+)
> create mode 100644
> target/linux/ge
On 02/15/2018 06:42 PM, Tim Harvey wrote:
> On Tue, Feb 13, 2018 at 12:51 PM, Hauke Mehrtens wrote:
>> On 02/13/2018 09:46 PM, Hauke Mehrtens wrote:
>>> Hi Tim,
>>>
>>> sorry that I haven't reviewed this earlyer, but now I saw some problems,
>>&
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 I haven't tested the
SFP functionality, would be nice if someone could test if that s
On 02/18/2018 12:35 PM, John Crispin wrote:
>
>
> On 17/02/18 13:30, Hauke Mehrtens wrote:
>> On 02/15/2018 05:34 PM, Tim Harvey wrote:
>>> Testted on a Gateworks GW54xx. Does not support enabling imx-drm modules
>>> yet as those will need some adjustments ba
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/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
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
On 03/01/2018 10:58 PM, Linus Walleij wrote:
> On Mon, Feb 26, 2018 at 9:28 PM, Linus Walleij
> wrote:
>
>> I have a forward-port hack-ish thing for Gemini,
>> this 500K patch on top of openwrt HEAD:
>>
>> https://dflund.se/~triad/krad/gemini/0001-gemini-Forward-port-to-v4.14.patch
>
> I update
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
On 03/06/2018 11:43 PM, Linus Walleij wrote:
> On Mon, Feb 26, 2018 at 9:28 PM, Linus Walleij
> wrote:
>
>> I have a forward-port hack-ish thing for Gemini,
>> this 500K patch on top of openwrt HEAD:
>>
>> https://dflund.se/~triad/krad/gemini/0001-gemini-Forward-port-to-v4.14.patch
>
> I have u
For more information and the latest flashing guide:
> please visit the OpenWrt Wiki Page for the MR24:
> <https://openwrt.org/toh/meraki/mr24#flashing>
>
> Cc: Hauke Mehrtens
> Signed-off-by: Christian Lamparter
> Signed-off-by: Chris Blake
> ---
> target/linux/a
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 05/05/2018 11:25 AM, Linus Walleij wrote:
> On Fri, May 4, 2018 at 11:49 PM, Linus Walleij
> wrote:
>> On Fri, May 4, 2018 at 11:37 PM, Roman Yeryomin wrote:
>>
The GPIO LEDs does not come up though?
CONFIG_LEDS_GPIO is not in config, and
/sys/class/leds is empty.
Doe
On 05/20/2018 11:42 AM, Rosysong wrote:
> Hi all,
> Using nftables to control the traffic flow through ip address has
> been succeed on my Linux PC, then I ported the same
> nft script into OpenWrt trunk. Unfortunately, it failed (has no effect on
> restricting the speed of client). Is th
This makes mbedtls use the POSIX API directly and not use the own
abstraction layer.
The size of the ipkg decreased by about 100 bytes.
Signed-off-by: Hauke Mehrtens
---
package/libs/mbedtls/patches/200-config.patch | 9 +
1 file changed, 9 insertions(+)
diff --git a/package/libs
This make sit possible to store informations about a session and reuse
it later. When used by a server it increases the time to create a new
TLS session from about 1 second to less than 0.1 seconds.
The size of the ipkg file increased by about 800 Bytes.
Signed-off-by: Hauke Mehrtens
The soversion was changed in this version again and is now aligned with
the 2.7.2 version.
The size of the ipkg file stayed mostly the same.
Signed-off-by: Hauke Mehrtens
---
package/libs/mbedtls/Makefile | 4 +-
package/libs/mbedtls/patches/200-config.patch | 53
This allows the client to reuse the settings from a previous session and
no full key exchange is needed.
The partially key exchange takes less than 0.1 seconds compared to over
a second needed for a full key exchange.
Signed-off-by: Hauke Mehrtens
---
ustream-mbedtls.c | 14
The cipher suites should be set after the default settings are done,
otherwise the settings will be overwritten with the defaults later on
again.
Also make the list of supported cipher suites match what Chrome tries to
use.
Signed-off-by: Hauke Mehrtens
---
ustream-mbedtls.c | 27
private commits from it.
This was the original version number which caused problems:
OpenWrt-r6727+10
Now it uses this version number:
OpenWrt-r6727
Signed-off-by: Hauke Mehrtens
---
target/linux/ar71xx/image/generic.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target
On 05/20/2018 12:25 PM, Rosysong wrote:
> I am using mips(ramips) target.
>
>
I tested this with lantiq and with kernel 4.9 nftables was working like
expected and with kernel 4.14 it does not work any more.
I do not know if this is caused by the more recent kernel or the flow
offloading.
Hauke
On 05/22/2018 10:09 AM, Rosysong wrote:
> Hi Hauke,
> Do you mean my nftables commands (limit rate xxx) can work on
> your lantiq (4.14 kernel) target ?
> I also choose kmod-nf-flow and kmod-nft-offload modules, but it
> can not restrict the traffic flow on specific ip
On 05/06/2018 07:17 PM, Paul Oranje wrote:
>
>
>> Op 30 apr. 2018, om 08:39 heeft John Crispin het volgende
>> geschreven:
>>
>> On 30/03/18 17:34, Hauke Mehrtens wrote:
>>> If the package doe not contain a PKG_HASH just skip the check instead of
&g
We would like to create a lede 17.01.5 release soon, the last release,
lede 17.01.4, was done on 18. October 2017 which was a long time ago.
We are planning to do the build by end of next week, around 2. June 2018.
This release would be build form the lede-17.01 stable branch and
contain all the f
On 05/25/2018 12:27 PM, Stijn Segers wrote:
> Hauke Mehrtens schreef op 24 mei 2018 21:06:55 CEST:
>> We would like to create a lede 17.01.5 release soon, the last release,
>> lede 17.01.4, was done on 18. October 2017 which was a long time ago.
>> We are planning to do the
On 05/24/2018 09:06 PM, Hauke Mehrtens wrote:
> We would like to create a lede 17.01.5 release soon, the last release,
> lede 17.01.4, was done on 18. October 2017 which was a long time ago.
> We are planning to do the build by end of next week, around 2. June 2018.
>
> This r
This activates the TLS session cache in mbedtls and makes use of it in
ustream-ssl.
The browser can now reuse the cryptographic data from a previous
handshake which makes the subsequent handshake much faster.
This is a backport from master.
Hauke Mehrtens (2):
mbedtls: update mbedtls to
From: John Crispin
5322f9d mbedtls: Fix setting allowed cipher suites
e8a1469 mbedtls: Add support for a session cache
Signed-off-by: John Crispin
---
package/libs/ustream-ssl/Makefile | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/libs/ustream-ssl/Makefile
This make sit possible to store informations about a session and reuse
it later. When used by a server it increases the time to create a new
TLS session from about 1 second to less than 0.1 seconds.
The size of the ipkg file increased by about 800 Bytes.
Signed-off-by: Hauke Mehrtens
From: John Crispin
527e700 ustream-ssl: Remove RC4 from ciphersuite in server mode.
39a6ce2 ustream-ssl: Enable ECDHE with OpenSSL.
45ac930 remove polarssl support
Signed-off-by: John Crispin
---
package/libs/ustream-ssl/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
dif
This fixes some minor security problems and other bugs.
Signed-off-by: Hauke Mehrtens
---
package/libs/mbedtls/Makefile | 6 +++---
package/libs/mbedtls/patches/300-soversion-compatibility.patch | 8
2 files changed, 7 insertions(+), 7 deletions
On 06/08/2018 04:42 PM, Achim Gottinger wrote:
> Disable caam support in default config and enable it only for the p1020
> target.
> The generic target is used for the wdr4900-v1 tp-link router which does
> not have an enabled caam engine.
> If caam is build in for this target it adds non functiona
zram.ko needs CONFIG_BLK_DEV activated and it is by default for all
other targets in OpenWrt.
This makes zram.ko compile again.
Compile tested only.
Signed-off-by: Hauke Mehrtens
---
target/linux/mediatek/mt7622/config-4.14 | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux
Neon and vfpv4 are mandatory extensions in the ARM64 instruction set
now, do not activate them explicitly. GCC will make use of these
extension now by default.
This makes it possible to share the toolchain with other Cortex A53
SoCs.
Compile tested only.
Signed-off-by: Hauke Mehrtens
Signed-off-by: Hauke Mehrtens
---
package/boot/arm-trusted-firmware-sunxi/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/boot/arm-trusted-firmware-sunxi/Makefile
b/package/boot/arm-trusted-firmware-sunxi/Makefile
index d2554f4ebc..7bd042bdab 100644
dtc-warning := $(dtc-warning-$(findstring 1,
$(KBUILD_ENABLE_EXTRA_GCC_CHECKS)))
dtc-warning += $(dtc-warning-$(findstring 2,
$(KBUILD_ENABLE_EXTRA_GCC_CHECKS)))
-@@ -70,11 +70,11 @@ DTC_FLAGS += $(dtc-warning)
+@@ -68,11 +68,11 @@ DTC_FLAGS += $(dtc-warning)
else
# Disable noisy check
The device tree files are now matching the kernel 4.17 and this will be
send also for integration into mainline U-Boot.
Signed-off-by: Hauke Mehrtens
---
...i-h3-Sync-OTG-and-HCI-nodes-from-Linux-DT.patch | 63 ++
.../320-sunxi-Add-support-for-Orange-Pi-R1.patch | 58 +++--
.../patches
t to.
Signed-off-by: Hauke Mehrtens
---
include/kernel-version.mk| 4 ++--
target/linux/apm821xx/config-4.4 | 1 +
target/linux/ar71xx/config-4.4 | 1 +
target/linux/ar71xx/patches-4.4
On 06/13/2018 12:25 PM, Andrey Melnikov wrote:
> Hello. Sorry for private mail, but after ML moving - forwarding via
> gmane is lost, I can't write to ML anymore.
You can just write to openwrt-devel@lists.openwrt.org
>
> Just for curious - when you merge sunxi patches from your staging
> tree? I
Hi,
The deadline to submit a proposal for a talk or workshop at the OpenWrt
Summit 2018 in Lisbon, Portugal on October 29th & 30th was extended till
July 11th 2018.
The CFP is open until July 11th https://www.papercall.io/openwrtsummit2018
At least some developers plane to visit the OpenWrt summ
On 07/02/2018 10:26 AM, Evgeniy Didin wrote:
> From: Evgeniy Didin
>
> In the latest version of u-boot (2018.05) there was a swith to
> Hush shell for ARC AXS10x boards(arc770/archs38):
> commit 9249d74781e1 ("ARC: AXS10x: Enable hush shell").
> In Hush shell using "$()" to declare envitonment v
-kernel.bin is too big
When the size check is removed it is working again.
I do not have this device and do not know if we can just remove this
size check or if we should solve this problem in a different way.
Signed-off-by: Hauke Mehrtens
---
target/linux/at91/image/legacy.mk | 1 -
1 file changed
On Debian 9 nasm does not build when we force it to use ranlib, for
macOSX this is needed. Only force this on macOSX and not on any other
OS, this should fix the build of nasm on Linux systems.
Fixes: d3a7587eb95 ("toolchain/nasm: fix missing AR/RANLIB variables")
Signed-off-by: Hauk
The OpenWrt Community is proud to announce the Fifth service release of
stable OpenWrt/LEDE 17.01 series, which is the first service release
after the remerger of the LEDE and OpenWrt projects.
OpenWrt/LEDE 17.01.5 “Reboot” incorporates a fair number of fixes back
ported from the development branc
I pushed the au1000 and gemini target to kernel 3.10 because all older
kernel versions are not supported any more in trunk. I do *not* have a
device to test this, these new kernel versions are untested on these boards.
If someone owns a "Cortina Systems CS351x" or a "RMI/AMD AU1x00" board
please b
On 07/06/2014 10:10 PM, Roman Yeryomin wrote:
> On 6 July 2014 21:34, Hauke Mehrtens wrote:
>> I pushed the au1000 and gemini target to kernel 3.10 because all older
>> kernel versions are not supported any more in trunk. I do *not* have a
>> device to test this, these ne
On 07/06/2014 08:34 PM, Hauke Mehrtens wrote:
> I pushed the au1000 and gemini target to kernel 3.10 because all older
> kernel versions are not supported any more in trunk. I do *not* have a
> device to test this, these new kernel versions are untested on these boards.
>
> If
On 07/15/2014 07:06 PM, Bruno Randolf wrote:
> Another problem I noted when upgrading from AA to BB on MTX-1:
>
> # sysupgrade -n /tmp/openwrt-au1000-au1500-jffs2-128k-sysupgrade.bin
> tar: openwrt-au1000-au1500-jffs2-128k.fs: not found in archive
> Invalid image contents
> Image check 'platform_c
On 07/20/2014 10:39 AM, Maarten Bezemer wrote:
> Update the kernel of the orion target to version 3.14.12.
> Refresh orion config and patches to match the changes in the kernel
>
> Tested on WRT350N-v2 device.
>
> Signed-off-by: Maarten Bezemer
> ---
> Makefile
On 07/20/2014 10:58 AM, Maarten Bezemer wrote:
> Update the kernel of the orion target to version 3.10.44.
> Refresh orion config and patches to match the changes in the kernel
>
> Tested on WRT350N-v2 device.
>
> Signed-off-by: Maarten Bezemer
> ---
> Makefile
On 08/13/2014 03:48 AM, Álvaro Fernández Rojas wrote:
> Fixes "sh: 0x: bad number".
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> diff --git a/package/kernel/broadcom-wl/files/lib/wifi/broadcom.sh
> b/package/kernel/broadcom-wl/files/lib/wifi/broadcom.sh
> index 83afa06..de3a91f 100644
>
On 08/17/2014 11:08 PM, Rafał Miłecki wrote:
> Signed-off-by: Rafał Miłecki
> ---
> This patch can't be applied yet, because SPI driver depends on the:
> dc6be9f54a4ecb0a09765d1f515ed947d86b7528
> bcma: use NS prefix for names of Northstar specific cores
>
> Hauke: I don't know magic tricks for u
On 08/18/2014 08:59 PM, Rafał Miłecki wrote:
> It it used by brcm47xx and bcm53xx targets, so put patches in generic.
>
> Signed-off-by: Rafał Miłecki
> ---
> V2: Update bcm53xx kernel config
> V3: Use V2 of patch for "nvram" partition (avoids two "nvram"s)
> ---
> .../027-mtd-bcm47xxpart-get-nv
On 08/20/2014 07:24 PM, Rafał Miłecki wrote:
> I found this explanation:
> http://wiki.openwrt.org/doc/techref/filesystems#can.we.switch.the.filesystem.to.be.entirely.jffs2
> but I'm looking for more details.
>
> I wanted to run OpenWrt on bcm53xx using initramfs and flash with
> overlay data part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/30/2014 06:45 PM, Matthias Schiffer wrote:
> On 08/30/2014 06:42 PM, Matthias Schiffer wrote:
>> Hi, I've noticed that the code produced by Barrier Breaker's
>> toolchain sometimes has significantly worse performance that that
>> built by Attitud
On 07/28/2014 12:37 AM, Ning Ye wrote:
> Hi All,
>
> Hyper-V support for X86 or X86_64 were noticeably missing. There is a
> previous patch for Kernel 3.3 but never maintained or merged into trunk.
> Here's my take on adding the Hyper-V support for the current kernel. No new
> sub targets o
On 09/16/2014 02:52 PM, Claudio Thomas wrote:
> On 16.09.2014 14:44, Felix Fietkau wrote:
>> On 2014-09-16 13:47, Claudio Thomas wrote:
>>> Hi,
>>> I until now was still using the trunk for testing and working, but today
>>> I the first time checked out the 14.07/openwrt.git at git.openwrt.git.
>>>
On 09/24/2014 10:57 PM, Łukasz Baj wrote:
> Right now these libraries are in oldpackages repository. Currently I'm
> working with some project which uses this stuff to handle Apple devices
> in OpenWrt environment. I was able to update all that libraries and I
> can take care of maintain them.
>
>
On 12/02/2014 08:39 PM, Rafał Miłecki wrote:
> It follows OpenWrt's global logic in netifd-wireless.sh. We should use
> CCMP unless TKIP was really requested.
>
> Signed-off-by: Rafał Miłecki
> ---
> package/kernel/broadcom-wl/files/lib/wifi/broadcom.sh | 2 +-
> 1 file changed, 1 insertion(+),
On 12/07/2014 01:30 AM, Rafał Miłecki wrote:
> I've bcm53xx device which has two usable flashes:
> 1) SPI serial flash for CFE + firmware + NVRAM
> 2) NAND flash for extra data
>
> Because of general design of OpenWrt firmware my image contains two
> partitions: kernel and rootfs (SquashFS). Autom
On 12/07/2014 01:18 AM, Rafał Miłecki wrote:
> bcm_nand uses (and depends on) OF, so there isn't much sense to use
> cmdlinepart
>
> Signed-off-by: Rafał Miłecki
> ---
> drivers/mtd/nand/bcm_nand.c | 7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/nand/
On 12/19/2014 03:45 PM, Marc Nicholas wrote:
> So let me turn my question around: given there seems to be some work on
> the 3.18 kernel, is there a timeline for this to go into the development
> trunk? :)
>
> Thx.
>
> -m
>
> --
> Marc Nicholas
> CTO, Wimoto Technologies Inc.
> Unit 2, 300 Don
On 12/22/2014 05:43 PM, Ram Marzin wrote:
>> Did I read it right - it relies on hw (to offload the cpu) but is hw
>> independent?
>> Does it mean you support Octeon or Realtek fastpath hw too?
>
> No, it does not rely on hardware, it is a pure SW solution.
>
> - Ram
Would it be possible to add
I added support for kernel 3.14 for the ep93xx target [0] in trunk, but
I do not have any hardware to test this, the commit was only compile tested.
If you have some hardware that is supported by the ep93xx target please
build an image with kernel 3.14 and test it on your device. If this
image boo
I added support for kernel 3.14 for the mpc52xx target [0] in trunk, but
I do not have any hardware to test this, the commit was only compile tested.
If you have some hardware that is supported by the mpc52xx target please
build an image with kernel 3.14 and test it on your device. If this
image b
I added support for kernel 3.14 for the mpc83xx target [0] in trunk, but
I do not have any hardware to test this, the commit was only compile tested.
If you have some hardware that is supported by the mpc83xx target please
build an image with kernel 3.14 and test it on your device. If this
image b
On 02/06/2015 08:16 PM, Daniel Golle wrote:
> Hi!
>
> I started using Jonas' b53 driver for the Lamobo R1 board in OpenWrt.
> To make things more convenient, I'd like to have the port mapping
> inside the device-tree, so port enumeration would be consistent.
> swconfig supports that (of_switch_loa
On 04/05/2015 10:18 AM, Dirk Neukirchen wrote:
> this module gets only (?) build on omap because of config symbol differences
> it seems
>
> fixes buildbot error:
> http://buildbot.openwrt.org:8010/builders/omap/builds/337/steps/compile_5/logs/stdio
>
> Signed-off-by: Dirk Neukirchen
> ---
> p
On 04/11/2015 09:59 AM, Rafał Miłecki wrote:
> On 5 April 2015 at 20:03, Nathan Hintz wrote:
>> The mips74k subtarget of brcm47xx configures gcc to compile for mips32r2;
>> however, the generated kernel config for 3.14 and later kernels ends up
>> with CPU_MIPS32_R1 and CPU_MIPSR1 selected. The g
Hi Enrico,
On 9/4/19 6:48 PM, Martin Blumenstingl wrote:
> Hi Enrico,
>
> On Wed, Sep 4, 2019 at 12:07 PM Enrico Mioso wrote:
>>
>> Hi there!
>>
>> So I am trying to get ethernet working on this AR10 device.
>> It has 3 GPHYs:
I did some fixes for the reset bits,, the rest is ok.
>>
>>
This updates hostapd to version 2.9 release.
I tested AP mode and also mesh on 5GHz.
Hauke Mehrtens (7):
hostapd: Update to version 2.8
hostapd: backport some Fixes from upstream hostapd
hostapd: update to version 2.9
hostapd: use config option CONFIG_NO_LINUX_PACKET_SOCKET_WAR
hostapd
601 - 700 of 1895 matches
Mail list logo
