[LEDE-DEV] Arcadyan vrv9510kwac23

2016-10-25 Thread Juan Rios
Hello again, I have been working on adding support for this router with the help of SCApi and we got it to the point that Ethernet ports works, leds and buttons works and wifi card 0xa8d6 43222 works. The wifi card don't have sprom and I had to write a patch to add fallback sprom support for

[LEDE-DEV] [LEDE-DEV, netifd] proto-shell: add helpers for generic options in proto handlers

2016-10-25 Thread Marcin Jurkowski
Adding helpers for virtual interfaces generic options in ncm, qmi, mbim and directip protocols as suggested by Felix in https://lists.openwrt.org/pipermail/openwrt-devel/2016-February/039794.html Signed-off-by: Marcin Jurkowski --- scripts/netifd-proto.sh | 13 +

[LEDE-DEV] [PATCH] ath10k-ct: Add QCA9888/9886 support, fix compat issue.

2016-10-25 Thread greearb
From: Ben Greear This should fix problems with latest backports, and also adds driver support for QCA9888 chipset. Signed-off-by: Ben Greear --- package/kernel/ath10k-ct/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

Re: [LEDE-DEV] [RFC] brcm47xx: bump kernel to 4.4

2016-10-25 Thread p . wassi
> It seems I'm experiencing the same crazy problem. Local builds work > for me (as explained in commit message), but image from buildbot > doesn't boot. This is some totally crazy thing :| I opt for staying at 4.4 and not reverting, since the issue already occured on kernel 4.1 for the WRT54GL

Re: [LEDE-DEV] [PATCH v4 2/5] linux/mtd: add id for mx25u3235f needed by ZyXEL NBG6817

2016-10-25 Thread Arjen de Korte
Citeren André Valentin : Signed-off-by: André Valentin --- .../patches-4.4/477-mtd-add-spi-nor-add-mx25u3235f.patch | 10 ++ 1 file changed, 10 insertions(+) create mode 100644

[LEDE-DEV] [PATCH v4 1/5] ipq806x/nbg6817: add support for ZyXEL NBG6817

2016-10-25 Thread André Valentin
CPU: 2x1.8GHz ARM, RAM: 512MiB Storage: 4MiB serial Flash, 3.9GiB MMC NIC: 2x1GBit/s, Switch with 5 external and 2 internal ports WiFi: Dualband, ath10k 2.4GHz, 5GHz MU-MIMO For installation copy xx-mmcblk0p4-kernel.bin and xx-mmcblk0p5-rootfs-full.bin to device. Then run: cat

[LEDE-DEV] [PATCH v4 0/5] ipq806x: add support for ZyXEL NBG6817

2016-10-25 Thread André Valentin
Support for NBG6817 comes with several challenges: -enable mmc support on platform -use fstools rootfs split on block devices ( creates a loop dev with offset ) -extend sysupgrade support to format the loop fs and save config Changes to v3: -build sysupgrade images padded to overlay block size

[LEDE-DEV] [PATCH v4 3/5] ipq806x/nbg6817: add sysupgrade support

2016-10-25 Thread André Valentin
Add new way of flashing to mmc devices based on rootfs split with loop devices. Signed-off-by: André Valentin --- .../ipq806x/base-files/lib/upgrade/platform.sh | 12 +++ .../linux/ipq806x/base-files/lib/upgrade/zyxel.sh | 87 ++ 2 files changed,

Re: [LEDE-DEV] Actual community change and additional developers compared to OpenWrt

2016-10-25 Thread David Lang
On Mon, 24 Oct 2016, Jo-Philipp Wich wrote: I would be interested in a more contributor oriented insight at this point. For example it took me a while to realize that being on Github suddenly means that people edit C code via the web interface without any means to syntax / compile / run test

[LEDE-DEV] [PATCH v4 4/5] package/basefiles: add mkfs.ext4 and losetup binaries to ramfs list

2016-10-25 Thread André Valentin
mkfs.ext4 und losetup are needed for sysupgrade support on mmc devices with automatic rootfs split (loopback device usage). Signed-off-by: André Valentin --- package/base-files/files/lib/upgrade/common.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [LEDE-DEV] [PATCH v4 2/5] linux/mtd: add id for mx25u3235f needed by ZyXEL NBG6817

2016-10-25 Thread André Valentin
Hi, Am 25.10.2016 um 08:58 schrieb Arjen de Korte:> Citeren André Valentin : > >> Signed-off-by: André Valentin >> --- >> .../patches-4.4/477-mtd-add-spi-nor-add-mx25u3235f.patch | 10 >> ++ >> 1 file changed, 10 insertions(+) >>

Re: [LEDE-DEV] [PATCH] [PATCH] fstools: added f2fs to block-mount, really correct indentation

2016-10-25 Thread John Crispin
Hi, after some recent changes in the fstools repo this patch applies but causes a compile error. could you please rebase/test/send the patch there were also a lot of whitespace errors. please use tabs to indent your c code John On 21/10/2016 14:54, Alberto Bursi wrote: > added the code

[LEDE-DEV] [RFCv2 0/3] Fix and improve PROVIDES handling

2016-10-25 Thread Jo-Philipp Wich
Various packages in the feeds and within the base repository provide multiple build variants with slightly varying feature sets and in some cases packages rely on functionality that can be supported by entirely different packages, like using either openssl-util or px5g to generate an RSA

[LEDE-DEV] [RFCv2 2/3] include: properly update .install stamp files

2016-10-25 Thread Jo-Philipp Wich
Right now the $(PKG_INSTALL_STAMP) files are only written if a package is selected as <*> but never deleted or emptied if the corresponding package is getting deselected. For ordinary packages this usually is no problem as the package/install recipe performs its own check for enabled packages

[LEDE-DEV] [RFCv2 3/3] iproute2: rename ip to ip-tiny and let both ip-tiny and ip-full provide "ip"

2016-10-25 Thread Jo-Philipp Wich
Rename the "ip" package declaration to "ip-tiny" and let both "ip-tiny" and "ip-full" provide the virtual "ip" package. This allows users to freely choose the "ip" command variant while other packages can continue to depend on "ip" without needing to enforce a specific variant. Note that this

[LEDE-DEV] [PATCH] package/boot/uboot-kirkwood: bump to upstream 2016.09.01

2016-10-25 Thread p . wassi
From: Paul Wassi Bump U-Boot for Kirkwood to upstream 2016.09.01. Local patches cleaned up and reworked. Rename OpenWrt/LEDE occurrences. Signed-off-by: Paul Wassi --- This patch bumps uboot-kirkwood to 2016.09.01, some of the local patches can be dropped then

[LEDE-DEV] make -j 4: race between Image/Prepare and device images?

2016-10-25 Thread Rafał Miłecki
Hi, I just discovered why I was getting some crazy results during my various kernel tests. It seems that LEDE doesn't rebuild images as expected with make -j N. I think that some/all images may be generated before Image/Prepare step. // I did initial build with CONFIG_KERNEL_KALLSYMS=y $ ls

Re: [LEDE-DEV] [RFC] brcm47xx: bump kernel to 4.4

2016-10-25 Thread Rafał Miłecki
On 25 October 2016 at 09:55, Hannu Nyman wrote: > On 25.10.2016 9:13, p.wa...@gmx.at wrote: >>> >>> It seems I'm experiencing the same crazy problem. Local builds work >>> for me (as explained in commit message), but image from buildbot >>> doesn't boot. This is some totally

[LEDE-DEV] [PATCH netifd 1/2] bridge: Don't use device name as bridge member name

2016-10-25 Thread Hans Dedecker
The bridge name is a copy of the device name; but the device name can change which is the case when an aliased interface is used as bridge member. This will result into unwanted side effects like bridge reload triggering a topology change effect after doing network reload; therefore use the

Re: [LEDE-DEV] [RFC] brcm47xx: bump kernel to 4.4

2016-10-25 Thread Hannu Nyman
On 25.10.2016 9:13, p.wa...@gmx.at wrote: It seems I'm experiencing the same crazy problem. Local builds work for me (as explained in commit message), but image from buildbot doesn't boot. This is some totally crazy thing :| I opt for staying at 4.4 and not reverting, since the issue already

Re: [LEDE-DEV] [RFC] brcm47xx: bump kernel to 4.4

2016-10-25 Thread Rafał Miłecki
On 25 October 2016 at 10:00, Jo-Philipp Wich wrote: > did you ever test local builds with all additional kmods (including all > kmods from feeds) enabled as ? I guess this will bump the kernel > size somewhat due to additional subsystems which are getting enabled. No, I never

[LEDE-DEV] [PATCH] package/boot/uboot-kirkwood: fix default bootcmd for Seagate Dockstar

2016-10-25 Thread p . wassi
From: Paul Wassi Fix the default value for the 'bootcmd' environment variable. Therefore make the default bootcmd work for buildbot's images. Signed-off-by: Paul Wassi --- The images generated for Dockstar (and probably other devices as well) have an

Re: [LEDE-DEV] [RFC] brcm47xx: bump kernel to 4.4

2016-10-25 Thread Jo-Philipp Wich
Hi Rafal, did you ever test local builds with all additional kmods (including all kmods from feeds) enabled as ? I guess this will bump the kernel size somewhat due to additional subsystems which are getting enabled. ~ Jo ___ Lede-dev mailing list

Re: [LEDE-DEV] [RFC] brcm47xx: bump kernel to 4.4

2016-10-25 Thread Rafał Miłecki
On 25 October 2016 at 08:13, wrote: >> It seems I'm experiencing the same crazy problem. Local builds work >> for me (as explained in commit message), but image from buildbot >> doesn't boot. This is some totally crazy thing :| > > I opt for staying at 4.4 and not reverting,

Re: [LEDE-DEV] [RFC] brcm47xx: bump kernel to 4.4

2016-10-25 Thread p . wassi
> Anyway I finally debugged this local vs. buildbot difference to the > CONFIG_KERNEL_KALLSYMS. Images from buildbot have this symbol enabled > which slightly increases kernel size. Enough to stop it from booting > on WRT300N v1. There must be something more... What I had on WRT54GL:

[LEDE-DEV] LEDE Forum - Startup mode

2016-10-25 Thread Ted Hess
Hi all - First off, thanks for all the feedback, suggestions and volunteers. For starters, and perhaps to become permanent, we have set up a copy of Discourse (http://discourse.org) for testing and evaluation. It is a very popular package for new organizations and it has a pretty active community

[LEDE-DEV] [RFC v2] Adjusting ext4 filesystem defaults

2016-10-25 Thread Jo-Philipp Wich
This patch series tunes the ext4 default parameters in order to support online resize and to make resulting filesystem images more flexible. The changes should also fix the issue reported at http://lists.infradead.org/pipermail/lede-dev/2016-September/002518.html at least for x86 systems.

[LEDE-DEV] [RFC v2 3/3] config: ext4: increase x86 rootfs size to 2GB to support online resize2fs

2016-10-25 Thread Jo-Philipp Wich
The current default rootfs size of 256MB in conjunction with 4K blocks produces an ext4 filesystem which lacks the appropriate amount of backup GDT entries to support online-resizing. For x86 targets, increase the default rootfs size to 2048MB which allows online resizing the filesystem to up to

[LEDE-DEV] [RFC v2 2/3] config: ext4: drop option to set maximum number of inodes

2016-10-25 Thread Jo-Philipp Wich
There is very little practical use to limit the number of available inodes on an ext4 filesystem and the make_ext4fs utility is able to calculate useful defaults by itself. Drop the option to make resulting ext4 filesystems more flexible by default. Signed-off-by: Jo-Philipp Wich

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH] blobmsg_json: handle conversion of large integers from JSON

2016-10-25 Thread Florian Larysch
Hi, > IIUC, your change makes the type of fields vary upon their values. > I'm wondering how you suggest applications parse the resulting blob messages? you're right, this doesn't make sense. In my case, the only consumer was using blobmsg_format_json(), which handles element types dynamically.

Re: [LEDE-DEV] LEDE Forum - Startup mode

2016-10-25 Thread Vincenzo Romano
Just my humble opinion. That piece of software looks great. Isn't there any other free (as in beer) alternative? -- Vincenzo Romano - NotOrAnd.IT Information Technologies -- NON QVIETIS MARIBVS NAVTA PERITVS 2016-10-25 17:03 GMT+02:00 Ted Hess : > Hi all - > > First off,

[LEDE-DEV] Fwd: TP-Link Archer C7 boot loop

2016-10-25 Thread Jon
Hello all, am having a similar problem with a boot loop. After an attempted flash of a LEDE build, my router is in a 5-6 second loop. Am 20.08.2016 um 23:35 schrieb Jochen Demmer: > yesterday I bricked an Archer C7 v2 by installing some homebrew (buildroot) lede firmware. > It got stuck

Re: [LEDE-DEV] [RFC v2 3/3] config: ext4: increase x86 rootfs size to 2GB to support online resize2fs

2016-10-25 Thread Alberto Bursi
On 10/25/2016 01:02 PM, Jo-Philipp Wich wrote: > > For x86 targets, increase the default rootfs size to 2048MB which allows > online resizing the filesystem to up to 2TB which is the current theoretical > maximum for LEDE, due to missing GPT support on the root block device. > FYI: in the