Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page

On 10/01/18 22:56, Thomas Endt wrote: Hi John, First results on a private demowiki, see: https://lede-project.org/_media/wiki/ledewiki-owrtstyling.jpg looking pretty cool !! thanks for the effort. 1) red marking: What are we going to do with the sidebar (raw, untouched styling; could be

Re: [OpenWrt-Devel] [PATCH 2/3] ipq-wifi: select board-2.bin at runtime

11.01.2018 07:23, Mathias Kresin: 10.01.2018 11:15, Thomas Hebb: Currently, we solve the problem of different IPQ4019 boards needing different sets of Wi-Fi calibration data (board-2.bin) by using an ipq-wifi-* package to overwrite board-2.bin in the filesystem. This presents a problem when we

Re: [OpenWrt-Devel] [PATCH 3/3] ipq806x: add Netgear EX6100v2/EX6150v2 support

Hey Thomas, I only had a brief look at the patch. Might be there is more stuff to change. Find my comments inline. 10.01.2018 11:15, Thomas Hebb: This patch adds support for the Netgear EX6100v2 and EX6150v2 Wi-Fi range extenders. Hardware: SoC:Qualcomm IPQ4018 RAM:256 MiB FLASH:

Re: [OpenWrt-Devel] [PATCH 2/3] ipq-wifi: select board-2.bin at runtime

10.01.2018 11:15, Thomas Hebb: Currently, we solve the problem of different IPQ4019 boards needing different sets of Wi-Fi calibration data (board-2.bin) by using an ipq-wifi-* package to overwrite board-2.bin in the filesystem. This presents a problem when we need the same image to support

[OpenWrt-Devel] [PATCH] ar71xx: disable devicetree support

While we'd like to convert ar71xx to DT-based configuration eventually, we aren't quite there yet, and shipping half-baked DT support that is not used at all wastes precious space. Saves ~120KB before LZMA, ~33KB after LZMA. Run-tested on TP-Link CPE510 and TL-WR841 v7. Signed-off-by: Matthias

Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page

Hi John, First results on a private demowiki, see: https://lede-project.org/_media/wiki/ledewiki-owrtstyling.jpg 1) red marking: What are we going to do with the sidebar (raw, untouched styling; could be beautified)? Keep or remove? 2) blue marking: I remember there was some discussion about a

[OpenWrt-Devel] [PATCH 3/3] ipq806x: add Netgear EX6100v2/EX6150v2 support

This patch adds support for the Netgear EX6100v2 and EX6150v2 Wi-Fi range extenders. Hardware: SoC:Qualcomm IPQ4018 RAM:256 MiB FLASH: 16 MiB Winbond W25Q128 ETH:Qualcomm IPQ4018 Gigabit PHY, 1 port WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11b/g/n 2x2 WLAN2: Qualcomm Atheros

[OpenWrt-Devel] [PATCH 02/15] metadata: make srcpackage extensible

Turn the srcpackage values into hashes to allow storing more information than just binary package names. Signed-off-by: Matthias Schiffer --- scripts/feeds | 2 +- scripts/metadata.pm | 6 -- scripts/package-metadata.pl | 2 +- 3 files

[OpenWrt-Devel] [PATCH 11/15] metadata: handle target build depends together with host build depends

Target build depends are similar to host build depends in that they refer to source packages rather than binary packages. Therefore, it makes sense to handle them together, rather than putting them in a list together with runtime depends and trying to figure out if the entries refer to source or

[OpenWrt-Devel] [PATCH 09/15] build: remove package preconfig feature

This feature has been unused for years, and its scope is too limited to be actually useful. Signed-off-by: Matthias Schiffer --- include/package-dumpinfo.mk | 16 +--- package/Makefile| 3 --- scripts/metadata.pm | 20

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 00/15] Metadata generator refactoring, cleanup and PROVIDES improvements

On 01/08/2018 03:52 PM, Matthias Schiffer wrote: > When attempting to fix FS#837, I decided to treat our metadata generator to > a greater refactoring, which resulted in this patchset. FS#837 is fixed in > patch 13. > > I also removed two seemingly obsolete features, "preconfig" and "package >

[OpenWrt-Devel] [PATCH 12/15] metadata: simplify generation of build depends from runtime depends

Runtime depends cannot have a buildtype suffix, and they never refer to source package names. In addition, this adds warnings about unsatisfiable dependencies. Furthermore, this change fixes the generation of conditional build dependencies for virtual packages provided by different source

[OpenWrt-Devel] [PATCH 15/15] include/package-dumpinfo.mk: don't duplicate source package information for every binary package

Eventually the BUILDONLY package flag could be replaced by simply creating a package Makefile without any BuildPackage calls. This will fail for now, as BuildPackage also causes the Makefile's compile target etc. to do something useful at all. Signed-off-by: Matthias Schiffer

[OpenWrt-Devel] [PATCH 10/15] treewide: fix build depends to refer to source package names

Build depends must refer to source packages rather than binary package names. Signed-off-by: Matthias Schiffer --- include/autotools.mk | 4 ++-- include/nls.mk | 2 +-

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 13/15] metadata: always resolve dependencies through provides list

Hi, [...] > diff --git a/scripts/package-metadata.pl b/scripts/package-metadata.pl > index 980ad24dc0..41e7108322 100755 > --- a/scripts/package-metadata.pl > +++ b/scripts/package-metadata.pl > @@ -101,14 +101,16 @@ my %dep_check; > sub __find_package_dep($$) { > my $pkg = shift; >

[OpenWrt-Devel] [PATCH 14/15] build: remove obsolete "package feature" feature

Package "features" seem to be unused for some time. In any case, custom Config.in snippets and package PROVIDES are a much more flexible way to express similar options. Signed-off-by: Matthias Schiffer --- include/package-dumpinfo.mk | 25

[OpenWrt-Devel] [PATCH 08/15] metadata: remove redundant fields from package hash

Signed-off-by: Matthias Schiffer --- scripts/metadata.pm | 3 --- scripts/package-metadata.pl | 8 2 files changed, 4 insertions(+), 7 deletions(-) diff --git a/scripts/metadata.pm b/scripts/metadata.pm index e636a45a33..50f91407d6 100644 ---

[OpenWrt-Devel] [PATCH 13/15] metadata: always resolve dependencies through provides list

Instead of adding virtual packages to the normal package list, keep a separate list for provides, make each package provide itself, and resolve all dependencies through this list. This allows to use PROVIDES to replace existing packages. Fixes FS#837. Signed-off-by: Matthias Schiffer

[OpenWrt-Devel] [PATCH 07/15] metadata: replace %subdir hash with a path field in source packages

Every single reference to subdir was concatenated with the source package name, so it makes sense to store the concatenated value instead. Signed-off-by: Matthias Schiffer --- scripts/metadata.pm | 12 +++- scripts/package-metadata.pl | 25

[OpenWrt-Devel] [PATCH 2/3] ipq-wifi: select board-2.bin at runtime

Currently, we solve the problem of different IPQ4019 boards needing different sets of Wi-Fi calibration data (board-2.bin) by using an ipq-wifi-* package to overwrite board-2.bin in the filesystem. This presents a problem when we need the same image to support multiple boards, as we do for the

[OpenWrt-Devel] [PATCH 1/3] build: allow custom config names in mkits.sh

This allows us to support the Netgear EX6100v2 and EX6150v2, whose bootloaders look for specific config names and refuse to boot if they're not present. Signed-off-by: Thomas Hebb --- include/image-commands.mk | 3 ++- scripts/mkits.sh | 12 2 files

[OpenWrt-Devel] [PATCH 06/15] metadata: change pkg->{src} field to hold a reference

We often want to access fields of a source packages through pkg->{src}. Allow accessing them directly instead of resolving the source hash through srcpackages. Signed-off-by: Matthias Schiffer --- scripts/feeds | 4 ++-- scripts/metadata.pm

[OpenWrt-Devel] [PATCH 05/15] metadata: interate over source packages when generating Makefile

All build dependencies are between source packages. Interating over source rather than binary packages simplifies parts of the code and prepares further improvement. As a side effect, this changes the implicit default variant of a few packages (the first defined is used now instead of the

[OpenWrt-Devel] [PATCH 04/15] metadata: move 'builddepends' from binary to source packages

Signed-off-by: Matthias Schiffer --- scripts/feeds | 20 +++- scripts/metadata.pm | 6 +++--- scripts/package-metadata.pl | 16 +++- 3 files changed, 21 insertions(+), 21 deletions(-) diff --git a/scripts/feeds

[OpenWrt-Devel] [PATCH 03/15] metadata: move 'buildtypes' from binary to source packages

Build types are a property of source rather than binary packages. This is a preparation for followup cleanup. Signed-off-by: Matthias Schiffer --- scripts/metadata.pm | 4 ++-- scripts/package-metadata.pl | 13 +++-- 2 files changed, 9

[OpenWrt-Devel] [PATCH 01/15] metadata: remove 'base-files' special case

Nothing explicitly depends on base-files, and even if it would, it would not cause any problems. Remove the unused special case. Signed-off-by: Matthias Schiffer --- scripts/package-metadata.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OpenWrt-Devel] [PATCH 00/15] Metadata generator refactoring, cleanup and PROVIDES improvements

When attempting to fix FS#837, I decided to treat our metadata generator to a greater refactoring, which resulted in this patchset. FS#837 is fixed in patch 13. I also removed two seemingly obsolete features, "preconfig" and "package features", which are not used by any package in the

Re: [OpenWrt-Devel] [PATCH RFC] mac80211: Don't check for platform files with external kernel trees

> On 8. Jan 2018, at 10:31, Florian Fainelli wrote: > > When building with an external kernel tree, do not check the different > platform files since this is almost guaranteed they are going to differ. > > Signed-off-by: Florian Fainelli But that

Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page

Hi Thomas, The OpenWrt wiki is actually running on my box, so you'll need me for that. Let's catch up on IRC how to get the targz to you. Regards, Zoltan H On Sat, 6 Jan 2018, Thomas Endt wrote: Hi John, Since the styling is based on CSS, we would need the OpenWrt wiki's CSS for that.

[OpenWrt-Devel] [PATCH RFC] mac80211: Don't check for platform files with external kernel trees

When building with an external kernel tree, do not check the different platform files since this is almost guaranteed they are going to differ. Signed-off-by: Florian Fainelli --- package/kernel/mac80211/Makefile | 9 +++-- 1 file changed, 7 insertions(+), 2

Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page

Hi John, Since the styling is based on CSS, we would need the OpenWrt wiki's CSS for that. Once we have that, it will be relatively easy. But instead of doing the merge of the wikis step by step, I would suggest a hard cut. 1.) Make OpenWrt wiki read only -> I can do that or Imre 2.) Create .tgz

Re: [OpenWrt-Devel] [LEDE-DEV] owrt landing page

Hi, I've been preparing some draft for a future landing page at https://lede-project.org/openwrt. Note that some of the linked pages are obviously still LEDE branded and the links to IRC, lists, forum need to be expanded to point to both OpenWrt and LEDE forums. Maybe someone can pick up from

[OpenWrt-Devel] owrt landing page

Hi, could someone please help us with rebranding the lede landing page to an openwrt colour/theme ? i would like to see this swithced over within the next 7 days. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

[OpenWrt-Devel] [RFC 1/2] downloads.mk: introduce name-agnostic PROJECT_GIT variable

Introduce a name-agnostic PROJECT_GIT variable poiting to https://git.openwrt.org/ and declare LEDE_GIT and OPENWRT_GIT as aliases to it. After some transition time we can drop this alias variables. Signed-off-by: Jo-Philipp Wich --- include/download.mk | 6 -- 1 file

[OpenWrt-Devel] [RFC 2/2] treewide: replace LEDE_GIT with PROJECT_GIT

Remove LEDE_GIT references in favor to the new name-agnostic PROJECT_GIT variable. Signed-off-by: Jo-Philipp Wich --- package/libs/librpc/Makefile | 2 +- package/libs/libubox/Makefile| 2 +- package/libs/uclient/Makefile| 2 +-

Re: [OpenWrt-Devel] [LEDE-DEV] [RFC 1/2] downloads.mk: introduce name-agnostic PROJECT_GIT variable

On 5 January 2018 at 10:53, Jo-Philipp Wich wrote: > Introduce a name-agnostic PROJECT_GIT variable poiting to > https://git.openwrt.org/ and declare LEDE_GIT and OPENWRT_GIT > as aliases to it. > > After some transition time we can drop this alias variables. > > Signed-off-by:

[OpenWrt-Devel] Espressobin mvebu64

Hi, First of all, congratulations on re-merge of OpenWrt and LEDE. Now to the problem being faced. I am trying to build OpenWrt for Espressobin (http://espressobin.net) as described in their wiki at http://wiki.espressobin.net/tiki-index.php?page=Build+From+Source+-+OpenWrt It built fine

[OpenWrt-Devel] OpenWrt LEDE merge

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

Re: [OpenWrt-Devel] [ICVPN] [WLANnews] Ideas wanted for Google Summer of Code 2018

Hi, I wish you a happy new year and I have news regarding the projects page. There's a simpler way to see if your project file is valid: If you look up your project file in github, the file is rendered. What you need to see is a table above the main text. It should look like this:

[OpenWrt-Devel] OpenWrt source replaced by former LEDE tree

Hi, following the agreed OpenWrt/LEDE re-merge procedure, we've replaced the OpenWrt Git tree with the LEDE Git tree now and archived the old repository. If you're working with older branches such as Chaos Calmer or Barrier Breaker, you do have to update your remotes in order to continue to be