Re: [OpenWrt-Devel] Changes in support for Mikrotik RB493G

2018-12-11 Thread Rafał Miłecki
On Sun, 9 Dec 2018 at 21:44, W. Michael Petullo wrote: > First, it seems that OpenWrt master has dropped YAFFS support. I cannot > find a clear statement on this, but I also cannot find how to build an > OpenWrt image that supports YAFFS. Because of this, I rely on an old >

[OpenWrt-Devel] 18.06-snapshots?

2018-12-11 Thread Daniel F. Dickinson
Hi, Just wondering if there are snapshots built for the backports etc done onto the 18.06 tree (e.g. in preparation for 18.06.2), or after release are there only adhoc builds for release candidates for the point release? If there are snapshots could the link be added to

[OpenWrt-Devel] Enabling initramfs images for PowerCloud CR5000 by default

2018-12-11 Thread Daniel F. Dickinson
Hi all, I'm wondering if it's possible to enable builds of initramfs (in addition to the main sysupgrade images) by default for PowerCloud CR5000 (and possibly CAP324, but see note) and CR3000. Previously one had to add a serial header to get these away from stock, but I've poked away and

[OpenWrt-Devel] [PATCH] ath79, brcm63xx: Fix debounce-interval properties in gpio-keys-polled nodes

2018-12-11 Thread Petr Štetiar
This patch fixes wrong usage of debounce-interval subnode property of gpio-keys-polled nodes, which was used inproperly in parent node, but it belongs to the subnodes, excerpt from the docs: Optional subnode-properties: - debounce-interval: Debouncing interval time in milliseconds.

Re: [OpenWrt-Devel] [PATCHv2] f2fs-tools: Update to 1.12.0

2018-12-11 Thread Rosen Penev
On Mon, Dec 10, 2018 at 1:59 AM Daniel Engberg wrote: > > Hi, > > I think we at least should wait until we get confirmation that patch #2 > is working on real hardware (ar71xx for instance) as intended. Also, I'm > not sure if it's your intention but the Github user offered to clean up > the

[OpenWrt-Devel] Someone want to update ath10k-ct fw?

2018-12-11 Thread Ben Greear
Hello, I have uploaded new builds for each of the CT firmware I maintain. The wave-1 stuff is in the same place as usual. The wave-2 (firmware-5) is in a new directory structure, with 'b' on the end, so for instance: greearb@ww2 downloads]$ ls -ltr ath10k-9984-10-4b total 1216 drwxrwsr-x. 2

Re: [OpenWrt-Devel] Changes in support for Mikrotik RB493G

2018-12-11 Thread Russell Senior
> "W" == W Michael Petullo writes: W> Changes in the last year or so have left me a little confused with W> the OpenWrt support for the Mikrotik RB493G. I generally compile my W> kernels and root disk images myself, namely by running "make W> menuconfig" and "make" in an OpenWrt source tree.

Re: [OpenWrt-Devel] [PATCH] ath10k-ct: update and use version based on 4.19

2018-12-11 Thread Ben Greear
On 12/10/18 2:23 PM, Hauke Mehrtens wrote: On 12/10/18 10:46 PM, Ben Greear wrote: On 12/10/18 1:35 PM, Hauke Mehrtens wrote: ---   package/kernel/ath10k-ct/Makefile  |  10 +-   ...h-all-IEs-for-variant-before-falling-back.patch |   8 +-  

Re: [OpenWrt-Devel] [PATCH] brcm63xx: perform a soft reset on the ehternet switch before its initializiation

2018-12-11 Thread Jonas Gorski
Hi, On Sun, 11 Nov 2018 at 15:15, Daniel Gonzalez Cabanelas wrote: > Add a switch reset on brcm63xx SoCs to ensure a sane state before > initializiating the switch. > > Performing this reset on BCM6368 solves the ticket #1925 on the > Observa VH4032N: > > - brcm63xx: VH4032N: no traffic