On Fri, Jan 19, 2018 at 3:02 AM, Val Kulkov wrote:
> On 18 January 2018 at 19:49, Alberto Bursi wrote:
>>
>>
>>
>> On 01/19/2018 01:05 AM, Val Kulkov wrote:
>>>
>>> There is more than a handful of PRs currently bit-rotting in
>>> openwrt/packages that are ready for merging, with all requested
>>>
This patch include GL.iNet vendor name in the
machine name for GL.iNet vendor products.
Signed-off-by: Kyson Lok
---
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar150.c | 2 +-
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar300.c | 2 +-
target/linux/ar71xx/files/arch/mips/ath79/mac
The mach name of GL AR150 and GL AR300 is inconsistent
with other products.
Signed-off-by: Kyson Lok
---
target/linux/ar71xx/base-files/lib/ar71xx.sh | 4 ++--
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar150.c | 2 +-
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar300.c
Hello Kyson,
On 19.01.2018 02:54, Kyson Lok wrote:
The mach name of GL AR150 and GL AR300 is inconsistent
with other products.
Thank you for your patch.
Please, include also vendor name (GL.iNet) in the machine name.
--
Cheers,
Piotr
Signed-off-by: Kyson Lok
---
target/linux/ar71xx/bas
The mach name of GL AR150 and GL AR300 is inconsistent
with other products.
Signed-off-by: Kyson Lok
---
target/linux/ar71xx/base-files/lib/ar71xx.sh | 4 ++--
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar150.c | 2 +-
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar300.c
The mach name of GL AR150 and GL AR300 is inconsistent
with other products.
Signed-off-by: Kyson Lok
---
target/linux/ar71xx/base-files/lib/ar71xx.sh | 4 ++--
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar150.c | 2 +-
target/linux/ar71xx/files/arch/mips/ath79/mach-gl-ar300.c
On 18 January 2018 at 19:49, Alberto Bursi wrote:
>
>
>
> On 01/19/2018 01:05 AM, Val Kulkov wrote:
>>
>> There is more than a handful of PRs currently bit-rotting in
>> openwrt/packages that are ready for merging, with all requested
>> changes in place since many months ago. Auto-closing such PRs
On 01/19/2018 01:05 AM, Val Kulkov wrote:
There is more than a handful of PRs currently bit-rotting in
openwrt/packages that are ready for merging, with all requested
changes in place since many months ago. Auto-closing such PRs will
offend the contributors who would see their effort go down th
On 18 January 2018 at 03:44, Jo-Philipp Wich wrote:
> Hi John, Alex,
>
> I have no problem with closing / autorejecting open tickets in patchwork
> as long as they somehow remain available for future reference.
>
>> To add here. Would it be possible/desire-able to add an auto-timeout
>> to patchwo
Am 17.01.2018 um 21:50 schrieb Christian Schoenebeck:
>> Independently of this, I'm the opinion, ddns for ipv6 can't work with a
>> deal-in or modem connection. My wan interface is
>> pppoe-wan. If the logical interface wan_6 is started, it (or pppoe-wan)
>> doesn't have a global ipv6 address. It
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 mitigate Spectre.
We even need a patch for GCC which will be in GCC 8 and 7.3.
For master we shou
On Thu, 18 Jan 2018, Hauke Mehrtens wrote:
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/fir
Hi All,
2018-01-18 1:30 GMT-08:00 Piotr Dymacz :
> Hi,
>
> On 18.01.2018 09:44, Jo-Philipp Wich wrote:
>>
>> Hi John, Alex,
>>
>> I have no problem with closing / autorejecting open tickets in patchwork
>> as long as they somehow remain available for future reference.
>
>
> ACK.
>
> Would it be po
Hi All,
Could someone enable this https://github.com/integration/dco on the
whole OpenWrt github org? (or at least on the packages repo)
Thanks
Etienne
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/l
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
Some MikroTik devices are using a Winbond NAND flash. Linux treats
it as an unknown NAND before version 4.11:
nand: device found, Manufacturer ID: 0xef, Chip ID: 0xf1
nand: Unknown NAND 128MiB 3,3V 8-bit
nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Backport a patch
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
The existing read functionality feeds the complete JSON to jshn as a
cmdline argument, leading to `-ash: jshn: Argument list too long`
errors for JSONs bigger than ca. 100KB.
This commit adds the ability to read the JSON directly from a file if
wanted, removing this shell-imposed size limit.
Test
Hi John,
Here's v3 of the patch with separate error handlers for the
different fail cases.
Cheers,
Christian
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Tested-by: Koen Vandeputte
Targets: cns3xxx
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Tested-by: Koen Vandeputte
Targets: imx6
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Refresh patches.
Remove upstreamed patches:
target/linux/generic/patches-4.4/030-2-smsc75xx-use-skb_cow_head-to-deal-with-cloned-skbs.patch
target/linux/generic/patches-4.4/030-3-cx82310_eth-use-skb_cow_head-to-deal-with-cloned-skb.patch
target/linux/generic/patches-4.4/030-4-sr9700-use-skb_cow_he
Refresh patches.
CVEs completely or partially addressed:
CVE-2017-5715
CVE-2017-5753
CVE-2017-17741
CVE-2017-1000410
Signed-off-by: Kevin Darbyshire-Bryant
---
include/kernel-version.mk | 4 ++--
.../generic/hack-4.14/904-debloat_dma_buf.patch| 2 +-
.../666-Add-
Refresh patches.
Remove upstreamed patches:
target/linux/generic/backport-4.9/023-2-smsc75xx-use-skb_cow_head-to-deal-with-cloned-skbs.patch
target/linux/generic/backport-4.9/023-3-cx82310_eth-use-skb_cow_head-to-deal-with-cloned-skb.patch
target/linux/generic/backport-4.9/023-4-sr9700-use-skb_cow
Refresh patches.
Remove upstreamed patches:
target/linux/generic/patches-4.4/030-2-smsc75xx-use-skb_cow_head-to-deal-with-cloned-skbs.patch
target/linux/generic/patches-4.4/030-3-cx82310_eth-use-skb_cow_head-to-deal-with-cloned-skb.patch
target/linux/generic/patches-4.4/030-4-sr9700-use-skb_cow_he
Refresh patches.
Remove upstreamed patches:
target/linux/generic/backport-4.9/023-2-smsc75xx-use-skb_cow_head-to-deal-with-cloned-skbs.patch
target/linux/generic/backport-4.9/023-3-cx82310_eth-use-skb_cow_head-to-deal-with-cloned-skb.patch
target/linux/generic/backport-4.9/023-4-sr9700-use-skb_cow
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.
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Add bit definitions for the 'hardware options' tag which is used in
the MikroTik devices' hardware configurations. These values can be
used in board setup codes, to do different initialization sequences.
The values were obtained from the RouterOS 6.41-rc38 patches.
Additionally, introduce two help
The patch adds support for the MikroTik RB911-2Hn (911 Lite2)
and the RB911-5Hn (911 Lite5) boards:
https://mikrotik.com/product/RB911-2Hn
https://mikrotik.com/product/RB911-5Hn
The two boards are using the same hardware design, the only difference
between the two is the supported wireless ba
Add patches for the leds-gpio driver to make it usable with
open-drain and open-source kind of GPIO lines.
This type of functionality is required by various MikroTik boards.
Signed-off-by: Gabor Juhos
---
...llow-to-use-OPEN_-DRAIN-SOURCE-flags-with.patch | 45 ++
...llow-to
The patch set add support for the MikroTik RB911 Lite2 (RB911-2Hn) and
MikroTik RB911 Lite5 (RB911-5Hn) boards.
Gabor Juhos (4):
ar71xx: add definitions for RouterBOARD hardware option bits
ar71xx: mach-rbspi: return rb_info from rbspi_platform_setup
ar71xx: make leds-gpio usable with single
Modify the rbspi_platform_setup() function to return the pointer of the
rb_info structure. This allows board specific setup routines to access
the various fields of the information. It is useful for investigating
the hardware option bits for example.
Also update the board setup codes, to ensure th
On 17/01/18 20:41, Zoltan HERPAI wrote:
Hi,
This series will add support for microcode update on x86 targets,
in light of the recent security issues.
While other distributions use an early initramfs approach to update
the microcode as early as possible, in OpenWrt the earliest place
where we
The patch 0022-dts-ipq4019-support-ARMv7-PMU.patch
was merged into 4.8-rc1.
Signed-off-by: Christian Lamparter
---
.../0022-dts-ipq4019-support-ARMv7-PMU.patch | 28 --
1 file changed, 28 deletions(-)
delete mode 100644
target/linux/ipq806x/patches-4.9/0022-dts-ipq401
On 18/01/2018 11:21, Mauro Mozzarelli wrote:
Quick question on lede to openwrt remerge (sorry I do not read all the
messages..)
What is the merged openwrt trunk development repository now?
This?
https://github.com/lede-project/source.git
[so far I have been using this which gets updated]
Quick question on lede to openwrt remerge (sorry I do not read all the
messages..)
What is the merged openwrt trunk development repository now?
This?
https://github.com/lede-project/source.git
[so far I have been using this which gets updated]
Or this?
https://github.com/openwrt/openwrt.gi
On 01/18/2018 10:34 AM, Mauro Mozzarelli wrote:
> Since about the last 10 days, when I do a make menuconfig, on exit save I
> do get the following warnings that I had not seen before (it is a long list
> and I include only some excerpts). I also pulled a fresh trunk in case I
> missed something in
A lot of targets have more than sufficient space to allow
building the kernel for speed iso size.
Export this performance option to the main config:
- Making it easy accessable for users
- Discarding the need to adjust it in the kernel config each time
when building from scratch and only using "m
Since about the last 10 days, when I do a make menuconfig, on exit save
I do get the following warnings that I had not seen before (it is a long
list and I include only some excerpts). I also pulled a fresh trunk in
case I missed something in the updates, but they did not go away. Am I
doing an
On 18/01/18 09:14, John Crispin wrote:
rather than using flock for procd enabled services we add locking to the
rc.common code.
Signed-off-by: John Crispin
---
package/base-files/files/etc/rc.common | 6 ++
package/system/procd/files/procd.sh| 15 ---
2 files changed,
rather than using flock for procd enabled services we add locking to the
rc.common code.
Signed-off-by: John Crispin
---
package/base-files/files/etc/rc.common | 6 ++
package/system/procd/files/procd.sh| 15 ---
2 files changed, 6 insertions(+), 15 deletions(-)
diff --git
This reverts commit 2277cd1249a6952228f36b768beea117c91123a0.
Signed-off-by: John Crispin
---
package/utils/busybox/Config-defaults.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/utils/busybox/Config-defaults.in
b/package/utils/busybox/Config-defaults.in
index 4e
42 matches
Mail list logo
