Re: [LEDE-DEV] Syslog-ng Makefile typo

Hi, although the content of the patch looks good the format is incorrect. you really want to generate the patch using git and then use git format-patch/send-email to export and mail it. we cannot merge it in this format i am afraid. please also make sure to add a Signed-off-by line John

Re: [LEDE-DEV] Syslog-ng Makefile typo

Hello, Sorry for miss and late. Changes bellow. I do not found any other "depracated" function. One question about klogd and syslog-ng kernel messagess. On Linux, the klogd daemon can be used in addition to syslog-ng to read kernel messages and forward them to syslog-ng. klogd used to

Re: [LEDE-DEV] [PATCH] ar71xx/ath79: mark soft_config as writeable in mach-rb941.c

Hi please fix the subject, git log --oneline target/linux/ar71xx will tell you the correct format amd ... On 18/01/2017 01:24, ha...@slashdirt.org wrote: > From: Thibaut VARENE > > This is necessary for rbcfg to work. this description is pointless ;) please add something

Re: [LEDE-DEV] [PATCH] This patch adds support for the Netgear WN3000RPv3 N300 repeater.

On 17 January 2017 at 23:12, wrote: > From: Thibaut VARENE > > It uses the same trick as for the EX2700 to pass the Second Part > Magic Check from the bootloader (as described here > https://forum.openwrt.org/viewtopic.php?pid=312577#p312577 ) > >

[LEDE-DEV] [PATCH] ramips: Add back sdhci-mt7620 driver to default config

The driver no longer causes kernel panics and CPU hangs. Signed-off by: Rosen Penev --- target/linux/ramips/image/mt7621.mk | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/target/linux/ramips/image/mt7621.mk b/target/linux/ramips/image/mt7621.mk

Re: [LEDE-DEV] Making staging tree appear on cgit?

On Tue, 2017-01-17 at 11:10 -0800, Florian Fainelli wrote: > Hi, > > Are there specific instructions not currently documented at: > https://lede-project.org/docs/guide-developer/the-source-code > > that are needed in order to make one's staging tree appear on cgit? > > Thanks! There should be

Re: [LEDE-DEV] [OpenWrt-Devel] Any interest in adding runit to OpenWRT?

The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- On Tue, Dec 27, 2016 at 1:07 AM,

Re: [LEDE-DEV] Files across reboot are not persisiting

On 2017-01-17 19:41, K.Mani wrote: > When we create a file on the booted board and reboot the file > doesn't persist. > Environment: > OpenWRT branch "Barrier Breaker" on Annapurna board, with > ALpine-v1(soc) is having NOR flash(MX25U25635F) 32MB The version you're asking about is not

Re: [LEDE-DEV] forum limitations

On Tue, 2017-01-17 at 09:32 -0800, David Lang wrote: > currently new users (for some definition of 'new', I have 63 posts starting  > within a day or two of when the forum was created) are limited to 3 replies in > a  > topic. > > This limit is really easy to hit in a technical discussion and is

[LEDE-DEV] Making staging tree appear on cgit?

Hi, Are there specific instructions not currently documented at: https://lede-project.org/docs/guide-developer/the-source-code that are needed in order to make one's staging tree appear on cgit? Thanks! -- Florian ___ Lede-dev mailing list

[LEDE-DEV] Files across reboot are not persisiting

When we create a file on the booted board and reboot the file doesn't persist. Environment: OpenWRT branch "Barrier Breaker" on Annapurna board, with ALpine-v1(soc) is having NOR flash(MX25U25635F) 32MB I think mounting of rootfs_data type jffs2 is not happening in Preinit!

Re: [LEDE-DEV] Syslog-ng Makefile typo

Actually, I take that back. Milan, can you please update the top line of files/syslog-ng.conf also? It needs to read “3.9” instead (assuming there aren’t any syntactic constructs in that file that are now deprecated from 3.8 to 3.9… if there were, the file would need to be updated as well…

Re: [LEDE-DEV] [PATCH 4/4] x86: Add APU2 LED Driver

On 2017-01-17 19:29, Chris Blake wrote: > Felix, > > I have been working on moving the LED driver to a package, but have > some concerns about implementation. Specifically, this would hit the > same issue I had with the Meraki MR18 LED Driver (NU801) around having > the LEDs/Reset button

Re: [LEDE-DEV] [PATCH 4/4] x86: Add APU2 LED Driver

On Sat, Jan 14, 2017 at 11:13 AM, Felix Fietkau wrote: > On 2017-01-14 18:04, Chris Blake wrote: >> On Sat, Jan 14, 2017 at 10:41 AM, Chris Blake >> wrote: >>> On Sat, Jan 14, 2017 at 10:31 AM, Felix Fietkau wrote: On 2017-01-14

[LEDE-DEV] forum limitations

currently new users (for some definition of 'new', I have 63 posts starting within a day or two of when the forum was created) are limited to 3 replies in a topic. This limit is really easy to hit in a technical discussion and is going to drive people to create extra topics to work around the

Re: [LEDE-DEV] [PATCH netifd] interface-ip: route proto config support (FS#170)

On Tue, Jan 17, 2017 at 5:00 PM, Dave Täht wrote: > Thank you Hans, this made my day. > > On 1/17/17 6:34 AM, Toke Høiland-Jørgensen wrote: >> Hans Dedecker writes: >> >>> Route proto support is usefull when using route distribution >>> via a routing daemon.

Re: [LEDE-DEV] [PATCH netifd] interface-ip: route proto config support (FS#170)

Thank you Hans, this made my day. On 1/17/17 6:34 AM, Toke Høiland-Jørgensen wrote: > Hans Dedecker writes: > >> Route proto support is usefull when using route distribution >> via a routing daemon. >> The route proto parameter can be specified via the route proto >> uci

[LEDE-DEV] [PATCH] netifd: Add option to configure locktime for each device

The UCI parameter neighlocktime allows to control the hardware address to IP mapping lock time in the IPv4 neighbour table. The IPv6 lock time was not set because it is not used at all in any kernel versions, hardware address override being controlled in this case by the override flag present in

Re: [LEDE-DEV] [PATCH netifd] interface-ip: route proto config support (FS#170)

Hans Dedecker writes: > Route proto support is usefull when using route distribution > via a routing daemon. > The route proto parameter can be specified via the route proto > uci config parameter and can hold the string values redirect, > kernel, static, gated, ra, mrt,

Re: [LEDE-DEV] LEDE 17.01 branched

> On Jan 16, 2017, at 1:37 PM, Jo-Philipp Wich wrote: > > this is just a heads-up to inform you that LEDE master has been branched > into a new branch "lede-17.01" now. And a hearty congratulations to everyone who helped get us this far. Thanks! I haven't seen these discussed

[LEDE-DEV] [PATCH netifd] interface-ip: route proto config support (FS#170)

Route proto support is usefull when using route distribution via a routing daemon. The route proto parameter can be specified via the route proto uci config parameter and can hold the string values redirect, kernel, static, gated, ra, mrt, zebra, bind, dnrouted, xorp, ntk, dhcp, mrouted, babel or

Re: [LEDE-DEV] [PATCH v2 09/14] rt2x00: rt2x00pci: set PCI MWI only if supported

Hi John, On Tue, Jan 17, 2017 at 08:34:44AM +0100, John Crispin wrote: > here is the original thread related to this patch > > http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2012-November/012227.html nah, that was me apparently trying to submit this upstream once before

Re: [LEDE-DEV] [PATCH] cns3xxx: restore mpcore watchdog

Hi Tim, Koen, Thanks for submitting this - I agree with Felix that we should add back the functionality if possible. The issue mentioned in the commit which removed the driver from mainline linux [1] regarding 'Nothing ensures the userspace ioctl() will end-up kicking the watchdog on the

Re: [LEDE-DEV] [PATCH 2/2] generic: keep module aliases inside .modinfo

On 11 January 2017 at 19:57, Yousong Zhou wrote: > It seems module aliases are actually essential info. E.g. other modules > may call xt_request_find_match(NFPROTO_IPV{4,6}, "hashlimit", 1) and the > kernel will request user mode modprobe helper for ipt_hashlimit and >

Re: [LEDE-DEV] [PATCH v3 0/2] ar71xx: fix making firmwares for Linksys WRT400N

Hi, On 29 December 2016 at 15:26, Yousong Zhou wrote: > I believe the situation at the moment for WRT400N is like this > > - factory image is broken and will brick the device because the utility >wrt400n will truncate the kernel to 1MB. > - sysupgrade image is