Live long, OpenWRT/LEDE!
2018-01-05 7:49 GMT+01:00 Levente :
> I'm happy to see the unified project.
>
> I cloned the source code, and it is working fine, however I noticed
> that some parts are still pulled from the LEDE git server. Is this
> intentional? Will all parts moved to OpenWrt's reposit
I'm happy to see the unified project.
I cloned the source code, and it is working fine, however I noticed
that some parts are still pulled from the LEDE git server. Is this
intentional? Will all parts moved to OpenWrt's repository?
Thanks,
Levente
On Fri, Jan 5, 2018 at 12:15 AM, Hauke Mehrte
Hi Hauke,
> -Original Message-
> From: Hauke Mehrtens [mailto:ha...@hauke-m.de]
> Sent: 2018年1月4日 4:47
> To: Y.b. Lu ; lede-dev@lists.infradead.org
> Subject: Re: [PATCH] layerscape: activate fpu feature
>
> On 01/03/2018 04:21 AM, Y.b. Lu wrote:
> > Hi Hauke,
> >
> > The layerscape main
On Sat, Jul 8, 2017 at 11:16 AM, Felix Fietkau wrote:
> On 2017-07-08 11:04, Hauke Mehrtens wrote:
>> The build bots are not setting CONFIG_ALL any more, so activate this
>> module by default why any of the ALL* options is selected.
>>
>> Signed-off-by: Hauke Mehrtens
> I think it would be more u
On 01/04/2018 08:43 PM, Sandeep Sheriker Mallikarjun wrote:
> neon and VFPv4 support is added to this target and uboot-at91 build
> fails due to TARGET_CFLAGS -mfloat-abi set to hard. as a fix, setting
> uboot-at91 CFLAGS -mfloat-abi=soft.
>
> Signed-off-by: Sandeep Sheriker Mallikarjun
>
> ---
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
1. enabled DMA controller options
2. Enabled CMA options
3. enabled VFP options
4. Add Atmel SD/MMC Driver
Signed-off-by: Sandeep Sheriker Mallikarjun
---
target/linux/at91/sama5/config-default | 43 ++
1 file changed, 43 insertions(+)
diff --git a/target/linux/
Refresh patches to tidy up fuzz. No functional changes
Signed-off-by: Kevin Darbyshire-Bryant
---
.../utils/busybox/patches/500-move-traceroute-applets-to-bin.patch | 4 ++--
package/utils/busybox/patches/600-cve-2017-16544.patch | 7 +--
2 files changed, 3 insertions(+), 8 dele
Refresh patches to tidy up fuzz. No functional changes
Signed-off-by: Kevin Darbyshire-Bryant
---
.../patches/010-lua-5.1.3-lnum-full-260308.patch | 47 +++---
.../012-lnum-fix-ltle-relational-operators.patch | 4 +-
package/utils/lua/patches/020-shared_liblua.patch | 2 +
The fixes following problems
1. changing prefix at91bootstrap to AT91bootstrap will fix the default
selection of at91bootstrap for the selected sama5 subtarget.
2. fixed missing default selection of sama5d4 nand flash for the
selected sama5d4 subtarget.
3. corrected at91bootstrap Title name.
Hi Hauke,
I have fixed this in bit different way and verified it on sama5 devices.
submitted the patch and below the patch link for your reference.
https://patchwork.ozlabs.org/patch/855787/
Regards,
Sandeep Sheriker M
On 01/03/2018 04:18 PM, Hauke Mehrtens wrote:
On 01/02/2018 07:26 PM, S
neon and VFPv4 support is added to this target and uboot-at91 build
fails due to TARGET_CFLAGS -mfloat-abi set to hard. as a fix, setting
uboot-at91 CFLAGS -mfloat-abi=soft.
Signed-off-by: Sandeep Sheriker Mallikarjun
---
package/boot/uboot-at91/Makefile | 2 +-
1 file changed, 1 insertion(+),
By default, when the imx6 PCIe RC boots up, the subordinate is set
equally to the secondary bus (1), and does not alter afterwards.
This means that theoretically, the highest bus reachable downstream is
bus 1.
Before upstream commit a20c7f36bd3d ("PCI: Do not allocate more buses
than available in
From: Rafał Miłecki
Alloc globdir buffer dynamically and simply use realloc when needed.
This fixes e.g. segmentation fault in jffs2reset due to an infinite
recurrency when dealing with longs paths.
Signed-off-by: Rafał Miłecki
---
libfstools/overlay.c | 21 +
1 file change
Refresh patches to tidy up fuzz. No functional changes
Signed-off-by: Kevin Darbyshire-Bryant
---
.../argp-standalone/patches/001-throw-in-funcdef.patch | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/package/libs/argp-standalone/patches/001-throw-in-funcd
Some additional info on this:
The issue is caused by the imx6 PCIe Root Complex which is not properly
configured on boot.
The subordinate should be set to 0xff (maximum bus nr that is reachable
downstream)
lspci -v:
[ Node 3 | node-3 ] lspci -v
00:00.0 PCI bridge: Synopsys, Inc. Device abcd
On 04/01/18 13:17, Kristian Evensen wrote:
On Thu, Oct 19, 2017 at 3:02 PM, Kristian Evensen
wrote:
When SIGTERM times out, procd sends SIGKILL and then restarts the
process once SIGCHLD has been received. This all works fine, with one
exception - respawn is not restored when instance_start()
Hello Hans,
Thanks for committing !
In the multi-homing case, you would typically have two RAs on the same
interface with one PIO per RA.
Therefore you would define two software interfaces, each with a prefix-filter
option making sure a single prefix is included in each RA.
So I think it would w
On Thu, Jan 4, 2018 at 11:12 AM, Pierre Pfister (ppfister)
wrote:
> Hello Hans and happy new year !
>
> As requested in your comment to v1, I have updated the README file.
> Would you mind reviewing this new version of the patch ?
>
> Thanks,
>
> - Pierre
Hi Pierre,
Also a happy new year!
I've re
On Thu, Oct 19, 2017 at 3:02 PM, Kristian Evensen
wrote:
> When SIGTERM times out, procd sends SIGKILL and then restarts the
> process once SIGCHLD has been received. This all works fine, with one
> exception - respawn is not restored when instance_start() is called from
> instance_exit(). The rea
Hello Hans and happy new year !
As requested in your comment to v1, I have updated the README file.
Would you mind reviewing this new version of the patch ?
Thanks,
- Pierre
> Le 8 déc. 2017 à 15:15, ppfis...@cisco.com a écrit :
>
> From: Pierre Pfister
>
> IETF is moving toward implementing
On Thu, Jan 4, 2018 at 9:01 AM, Olof Sivertsson wrote:
> Hi Hans,
>
>>
>> I'm unable to reproduce the reported netifd crash by using a proto
>> shell handler having no proto_init_config function.
>> Looking into the code the proto_handler config_params parameter is
>> always assigned the proto she
22 matches
Mail list logo
