Re: [LEDE-DEV] mac80211 / wireless drivers update
On 2017-01-31 23:22, Tim Harvey wrote: > On Fri, Jan 27, 2017 at 2:15 AM, Felix Fietkau wrote: >> Hi everybody, >> >> I just pushed an update of the mac80211 package to the current >> wireless-testing version in preparation for adding Linux 4.9 support. >> You can find my tree here: >> https://git.lede-project.org/?p=lede/nbd/staging.git;a=summary >> >> Please test it with your favorite wifi driver and let me know if >> anything breaks. >> >> - Felix > > Hi Felix, > > Thanks for posting your 4.9 work in progress! > > I used it to get some patches ready for imx6 4.9 support and found > that the mtd/ubi patches needed some work for 4.9 so you likely didn't > get to those yet. My tree can be found here: > https://github.com/Gateworks/lede/commit/a6d5376f806bee1ac90f1036d0b4eabd2da06da7 Thanks. I folded your fixes into my commits, reworked them a bit and added your S-o-b to my main 4.9 update commit. - Felix ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] telephony: adding telephony functionality
Dear All, after some investigation on my DWR-512 board I discovered the hw architecture of the telephone voice channel embedded in the router. The board embeds one 3g modem plugged on the mini pcie slot and one proslic device (si3210 - subscriber line interface circuit). The hw architecture is shown below. T V | | +---+ +---+ IRQ | | PCM bus | | events +---| si |<=>| 3g |-+ | | 3210 | | modem | | | +---+ +---+ | | ^ ^ | | | | | | | spidev1.0 | | | | | ttyUSB0/1 | | +---+ | | | | |---+ | +-->| uP | | gpio1 | |<+ +---+ ttyUSB1 The si3210 is controlled by the uP through the second channel of the spi bus (currently I'm using the spidev driver). The si3210 is able to report several events through one IRQ line connected to the gpio1. The audio channel (tx,rx) are transferred using the PCM interface. The si3210 is slave on the PCM bus, the master is the 3g modem. The rt5350 have a pcm interface, but it seems not connected (I need to investigate further with more dedicated test). The 3g modem is connected through the USB bus, there are several interface among which 2 cdc-ether and 4 ttyUSB. The device can be controlled using the AT cmd using the ttyUSB0 and ttyUSB1. The telephone events are reported only on the ttyUSB1 channel. Currently I developed some userspace tools to initialize the si3210 and control its operations (including setup a working call). My next plan is to develop a driver for the si3210 and then one userspace daemon to enable the telephone voice (and sms) channel functions. The si3210 driver shall be platform independent, because it will be plugged on the top of the spi driver and shall provide system call to the userspace (it could also be used to implement a Asterisk dahdi driver if someone find it useful). Have someone some comments about this plan? Are any similar project known, where I can look? ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] LEDE v17.01.0-rc1
Hi, The LEDE Community is proud to announce the first release candidate of the upcoming LEDE 17.01 stable version series. It incorporates thousands of commits made during the course of the last months and allows us to refine the code base for the final v17.01.0 version. With this release, the LEDE development team closes out an intense effort to modernize many parts of OpenWrt and incorporate many new modules, packages, and technologies. --- Some selected highlights since the OpenWrt Chaos Calmer release are: * Linux kernel updated to version 4.4.42 (from 3.18 in Chaos Calmer) * Update of essential software: * dnsmasq updated to 2.76 (from 2.73 in Chaos Calmer) * busybox updated to 1.25.1 (from 1.23.2 in Chaos Calmer) * mbedtls version 2.4.0 (updated from polarssl 1.3.14 in Chaos Calmer) * openssl updated to 1.0.2k * Improved Security Features * Use SHA256 instead of MD5 to validate source code for upstream packages * mbedtls: disable SSLv3 support * OpenSSL: disable support for compression, heartbeats, NPN, Whirlpool, and J-PAKE * Memory Corruption Mitigation Methods * gcc -Wformat -Wformat-security * User space Stack-Smashing Protection (Regular) * Kernel space Stack-Smashing Protection (Regular) * buffer-overflows detection (FORTIFY_SOURCE) (Conservative) * RELRO protection (Full) * Improved Networking Support * Smart Queue Management (SQM) minimizes bufferbloat by using the cake and fq_codel qdisc's. //[[:docs:howto:sqm|More...]]// * Improvements to the WiFi stack eliminating bufferbloat on ath9k, mt76 and some ath10k chipsets * Airtime fairness scheduler for ath9k to prevent slow stations from hogging too much airtime * Various stability and regression fixes to the Linux wireless stack and ath9k in particular * Provide alternative Candela-Tech ath10k-ct driver * Updated toolchain * musl 1.1.15 * gcc 5.4.0 * binutils 2.25.1 * Platform and Driver Support * Lantiq * Added redistributable DSL firmware * Updated DSL phy drivers * Added new targets:tickets * apm821xx (AppliedMicro APM821xx) * arc770 (Synopsys DesignWare ARC 770D) * archs38 (Synopsys DesignWare ARC HS38) * armvirt (QEMU ARM Virtual Machine) * ipq806x (Qualcomm Atheros IPQ806X) * layerscape (NXP Layerscape) * zynq (Xilinx Zynq 7000 SoCs) * Reorganized x86 target: * Drop dedicated Xen DomU target, merged with x86/generic * Enable AES-NI support * Removed targets: * realview, replaced by armvirt * ppc44x, disabled due to code brokeness * netlogic, dropped due to no available hardware * Build system improvements * Separation of base system and community feeds to simplify distribution of binary package updates * Fixes and enhancements in package dependency handling, better support for virtual provides * Per-device rootfs images to better tune package selection to each individual device profile * New image build code improving compilation times and simplifying device profile declarations * New package/.../check make target to run a series of standard diagnostics on Makefiles * Support for fetching sources using Curl * Generate reproducible source tarballs when packing SCM checkouts * Image Builder / SDK * Rework library bundling to allow for better portability between different Linux distributions * Add support for building kernel modules using the SDK * Added support for a many new routers and boards --- Known issues: * Available space on devices with only 4MB flash is very low, users requiring extra packages might want to consider using the image builder to repack custom images * The available memory on devices with 16MB RAM might be too low to reliably run opkg or sysupgrade operations, especially in conjunction with LuCI * The source snapshot tarballs produced by Github do not correctly compile all packages due to missing Git history information, this will be fixed with the next RC * The SDK tarballs embed a wrong revision and might report "r0+3043" instead of "r3042", this is a cosmetic issue which will get fixed with the next RC * Any outstanding issues reported at https://bugs.lede-project.org/ --- For the latest information about the 17.01 release and for detailed change logs, refer to the wiki page at: https://lede-project.org/releases/17.01/ To download the v17.01.0-rc1 images, navigate to: https://downloads.lede-project.org/releases/17.01.0-rc1/ --- A big thank you goes to all our active package maintainers, testers, documenters and supporters. Have fun! The LEDE Community signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailm
Re: [LEDE-DEV] mac80211 / wireless drivers update
On Fri, Jan 27, 2017 at 2:15 AM, Felix Fietkau wrote: > Hi everybody, > > I just pushed an update of the mac80211 package to the current > wireless-testing version in preparation for adding Linux 4.9 support. > You can find my tree here: > https://git.lede-project.org/?p=lede/nbd/staging.git;a=summary > > Please test it with your favorite wifi driver and let me know if > anything breaks. > > - Felix Hi Felix, Thanks for posting your 4.9 work in progress! I used it to get some patches ready for imx6 4.9 support and found that the mtd/ubi patches needed some work for 4.9 so you likely didn't get to those yet. My tree can be found here: https://github.com/Gateworks/lede/commit/a6d5376f806bee1ac90f1036d0b4eabd2da06da7 Regards, Tim ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] Bounty: simplify extracting/restoring kernel .config
On 01/31/2017 07:34 PM, Felix Fietkau wrote: > On 2017-01-31 16:21, Zoltan Gyarmati wrote: >> Adding an i2c RTC to the RT5350F-OLinuXino board. >> It's already requires patching the dts file to enable the i2c port, but >> that change i want to sent to upstream (as that is generally useful), >> while adding my type of RTC chip to the device tree is specific to my >> config, so i would like to keep it separated. The obvious solution is >> to to maintain my customization patches on the top of the upstream, but >> if it's possible i want to avoid that, for which it would be perfect to >> keep it in an 'env'. >> Thx, > In the future this will be handled at runtime via device tree overlays. That sounds good, it would be nice to have device tree overlay configuration support in OpenWrt. Thx for the info, regards, > > - Felix Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] Release Candidate Test Plan - first draft
On Tue, Jan 31, 2017 at 05:20:13PM +0100, Daniel Golle wrote: > openvpn-mbedtls didn't like my vpn server for some reason: > The certificate is signed with an unacceptable hash. > > openvpn-openssl worked without any problems. This looks similar to this bug report: https://bugs.lede-project.org/index.php?do=details&task_id=405 Maybe your VPN server use an old hash algorithm (MD5, SHA1)? signature.asc Description: PGP signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] Bounty: simplify extracting/restoring kernel .config
On 2017-01-31 16:21, Zoltan Gyarmati wrote: > Adding an i2c RTC to the RT5350F-OLinuXino board. > It's already requires patching the dts file to enable the i2c port, but > that change i want to sent to upstream (as that is generally useful), > while adding my type of RTC chip to the device tree is specific to my > config, so i would like to keep it separated. The obvious solution is > to to maintain my customization patches on the top of the upstream, but > if it's possible i want to avoid that, for which it would be perfect to > keep it in an 'env'. > Thx, In the future this will be handled at runtime via device tree overlays. - Felix ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] ar71xx: GPIO driver backport
Backport the ath79 GPIO driver to kernel 4.4.
Benefits this driver has compared with the old one:
- support for the interrupt controller
- module removable
The new code using the generic MMIO GPIO driver starts in
kernel 4.6, therefore this patch won't be useful anymore
when this version is adopted. The intention is to integrate
the patch into the stable release 17.01
Patch tested in an AR7240 based board.
Signed-off-by: Daniel Gonzalez Cabanelas
diff --git a/target/linux/ar71xx/config-4.4 b/target/linux/ar71xx/config-4.4
index 4b2f736..d3ecf4d 100644
--- a/target/linux/ar71xx/config-4.4
+++ b/target/linux/ar71xx/config-4.4
@@ -267,6 +267,7 @@ CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GPIOLIB=y
CONFIG_GPIOLIB_IRQCHIP=y
+CONFIG_GPIO_ATH79=y
CONFIG_GPIO_DEVRES=y
# CONFIG_GPIO_LATCH is not set
CONFIG_GPIO_NXP_74HC153=y
diff --git
a/target/linux/ar71xx/patches-4.4/455-gpio-ath79-driver_backport-irqchip.patch
b/target/linux/ar71xx/patches-4.4/455-gpio-ath79-driver_backport-irqchip.patch
new file mode 100644
index 000..e0f8622
--- /dev/null
+++
b/target/linux/ar71xx/patches-4.4/455-gpio-ath79-driver_backport-irqchip.patch
@@ -0,0 +1,469 @@
+--- a/drivers/gpio/gpio-ath79.c
b/drivers/gpio/gpio-ath79.c
+@@ -1,145 +1,237 @@
+ /*
+ * Atheros AR71XX/AR724X/AR913X GPIO API support
+ *
++ * Copyright (C) 2015 Alban Bedel
+ * Copyright (C) 2010-2011 Jaiganesh Narayanan
+ * Copyright (C) 2008-2011 Gabor Juhos
+ * Copyright (C) 2008 Imre Kaloz
+ *
+- * Parts of this file are based on Atheros' 2.6.15/2.6.31 BSP
+- *
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 as published
+ * by the Free Software Foundation.
+ */
+
+ #include
++#include
+ #include
+ #include
++#include
++#include
++#include
+
+-#include
++#define AR71XX_GPIO_REG_OE0x00
++#define AR71XX_GPIO_REG_IN0x04
++#define AR71XX_GPIO_REG_SET 0x0c
++#define AR71XX_GPIO_REG_CLEAR 0x10
++
++#define AR71XX_GPIO_REG_INT_ENABLE0x14
++#define AR71XX_GPIO_REG_INT_TYPE 0x18
++#define AR71XX_GPIO_REG_INT_POLARITY 0x1c
++#define AR71XX_GPIO_REG_INT_PENDING 0x20
++#define AR71XX_GPIO_REG_INT_MASK 0x24
+
+ struct ath79_gpio_ctrl {
+- struct gpio_chip chip;
++ struct bgpio_chip bgc;
+ void __iomem *base;
+ spinlock_t lock;
++ unsigned long both_edges;
+ };
+
+-#define to_ath79_gpio_ctrl(c) container_of(c, struct ath79_gpio_ctrl, chip)
+
+-static void ath79_gpio_set_value(struct gpio_chip *chip,
+- unsigned gpio, int value)
++static inline struct ath79_gpio_ctrl *to_ath79_gpio_ctrl(struct gpio_chip *gc)
+ {
+- struct ath79_gpio_ctrl *ctrl = to_ath79_gpio_ctrl(chip);
++ struct bgpio_chip *bgc = to_bgpio_chip(gc);
+
+- if (value)
+- __raw_writel(BIT(gpio), ctrl->base + AR71XX_GPIO_REG_SET);
+- else
+- __raw_writel(BIT(gpio), ctrl->base + AR71XX_GPIO_REG_CLEAR);
++ return container_of(bgc, struct ath79_gpio_ctrl, bgc);
+ }
+
+-static int ath79_gpio_get_value(struct gpio_chip *chip, unsigned gpio)
++static struct ath79_gpio_ctrl *irq_data_to_ath79_gpio(struct irq_data *data)
+ {
+- struct ath79_gpio_ctrl *ctrl = to_ath79_gpio_ctrl(chip);
++ struct gpio_chip *gc = irq_data_get_irq_chip_data(data);
++ return to_ath79_gpio_ctrl(gc);
++}
+
+- return (__raw_readl(ctrl->base + AR71XX_GPIO_REG_IN) >> gpio) & 1;
++static u32 ath79_gpio_read(struct ath79_gpio_ctrl *ctrl, unsigned reg)
++{
++ return readl(ctrl->base + reg);
+ }
+
+-static int ath79_gpio_direction_input(struct gpio_chip *chip,
+- unsigned offset)
++static void ath79_gpio_write(struct ath79_gpio_ctrl *ctrl,
++ unsigned reg, u32 val)
+ {
+- struct ath79_gpio_ctrl *ctrl = to_ath79_gpio_ctrl(chip);
+- unsigned long flags;
++ return writel(val, ctrl->base + reg);
++}
+
+- spin_lock_irqsave(&ctrl->lock, flags);
++static bool ath79_gpio_update_bits(
++ struct ath79_gpio_ctrl *ctrl, unsigned reg, u32 mask, u32 bits)
++{
++ u32 old_val, new_val;
+
+- __raw_writel(
+- __raw_readl(ctrl->base + AR71XX_GPIO_REG_OE) & ~BIT(offset),
+- ctrl->base + AR71XX_GPIO_REG_OE);
++ old_val = ath79_gpio_read(ctrl, reg);
++ new_val = (old_val & ~mask) | (bits & mask);
+
+- spin_unlock_irqrestore(&ctrl->lock, flags);
++ if (new_val != old_val)
++ ath79_gpio_write(ctrl, reg, new_val);
+
+- return 0;
++ return new_val != old_val;
+ }
+
+-static int ath79_gpio_direction_output(struct gpio_chip *chip,
+- unsigned offset, int value)
++static void ath79_gpio_irq_unmask(struct irq_data *data)
+ {
+- struct ath79_gpio_ctrl *ctrl = to_ath79_gpio_ctrl(chip);
++ struct ath79_gpio_ctrl
Re: [LEDE-DEV] Release Candidate Test Plan - first draft
Hi! Tested the release candidate on octeon/erlite, most things work nicely so far. Upgrading from 15.05 was tricky though because octeon_board_name is broken in 15.05 and i needed to manually fix it so sysupgrade would work (octeon_board_name() returned 'cavium,octeon-3860' instead of 'erlite' on 15.05) Imho we should make a note on each board which successfully booted the release and make a note whether it was flashed using sysupgrade or factory method and if any hacks or special work-arounds were needed, ie stuff like the octeon_board_name problem mentioned above... Package problems: (I) dnsmasq REFUSED queries no matter from which interface they came. I replaced it with unbound and odhcpd which solved the problem. 16:31:38.423896 IP 192.168.225.237.56085 > 192.168.225.1.domain: 56063+ A? google.com. (28) 16:31:38.427000 IP 192.168.225.1.domain > 192.168.225.237.56085: 56063 Refused 0/0/0 (28) The same configuration worked without any problem for almost a year with more than 100 days uptime on 15.05. (II) openvpn-mbedtls didn't like my vpn server for some reason: The certificate is signed with an unacceptable hash. openvpn-openssl worked without any problems. Should I file bugs for those openvpn-mbedtls and dnsmasq problems? In case of openvpn-mbedtls I'm not sure whether it is a bug or a feature... Cheers Daniel On Mon, Jan 30, 2017 at 03:14:08PM -0500, Rich Brown wrote: > Folks, > > There have been a couple questions on the forum about what needs to be tested > in the LEDE release candidate. > > I put together a draft of a note that lists how to install, what to test, and > how to report problems. It's at: > https://lede-project.org/playground/releasecandidatetestplan > > Comments, updates, etc. welcomed. > > Rich > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH netifd] interface: add prefix assignment priority support
In case of prefix delegation prefixes are assigned to one or more
configured downstream interfaces. The delegated prefix length in
combination with the assignment length of the downstream interfaces
determines the number of subnets which can be allocated from the
delegated prefix.
The interface ip6weight parameter allows to prioritize the allocation
of subnets to interfaces in case of multiple configured downstream
interfaces.
The order of interface prefix assignment from a delegated prefix is
based on the following parameters:
-Primary key is prefix assignment based on the configured interface ip6hint
-Secondary key is the requested downstream interface prefix length,
interfaces configured with the smallest ip6hint will be assigned first
-Third key is the assigned interface ip6weight in case of equal prefix
assignment length; interfaces having the highest ip6weight will be
assigned first
-Finally the alphabetical order of the interfaces in case of equal
ip6weight
Signed-off-by: Hans Dedecker
---
interface-ip.c | 57 -
interface-ip.h | 1 +
interface.c| 6 ++
interface.h| 1 +
ubus.c | 2 ++
5 files changed, 50 insertions(+), 17 deletions(-)
diff --git a/interface-ip.c b/interface-ip.c
index f8dab84..c20f0ba 100644
--- a/interface-ip.c
+++ b/interface-ip.c
@@ -850,6 +850,23 @@ static bool interface_prefix_assign(struct list_head *list,
return false;
}
+/* Sorting of assignment entries : */
+/* Primary on assignment length : smallest assignment first */
+/* Secondary on assignment weight : highest weight first*/
+/* Finally alphabetical order of interface names*/
+static int prefix_assignment_cmp(const void *k1, const void *k2, void *ptr)
+{
+ const struct device_prefix_assignment *a1 = k1, *a2 = k2;
+
+ if (a1->length != a2->length)
+ return a1->length - a2->length;
+
+ if (a1->weight != a2->weight)
+ return a2->weight - a1->weight;
+
+ return strcmp(a1->name, a2->name);
+}
+
static void interface_update_prefix_assignments(struct device_prefix *prefix,
bool setup)
{
struct device_prefix_assignment *c;
@@ -894,7 +911,13 @@ static void interface_update_prefix_assignments(struct
device_prefix *prefix, bo
}
bool assigned_any = false;
- struct list_head assign_later = LIST_HEAD_INIT(assign_later);
+ struct {
+ struct avl_node node;
+ } *entry, *n_entry;
+ struct avl_tree assign_later;
+
+ avl_init(&assign_later, prefix_assignment_cmp, false, NULL);
+
vlist_for_each_element(&interfaces, iface, node) {
if (iface->assignment_length < 48 ||
iface->assignment_length > 64)
@@ -923,6 +946,7 @@ static void interface_update_prefix_assignments(struct
device_prefix *prefix, bo
c->length = iface->assignment_length;
c->assigned = iface->assignment_hint;
+ c->weight = iface->assignment_weight;
c->addr = in6addr_any;
c->enabled = false;
memcpy(c->name, iface->name, namelen);
@@ -935,27 +959,25 @@ static void interface_update_prefix_assignments(struct
device_prefix *prefix, bo
"of size %hhu for %s, trying
other\n", c->length, c->name);
}
- struct list_head *next = &assign_later;
- struct device_prefix_assignment *n;
- list_for_each_entry(n, &assign_later, head) {
- if (n->length < c->length) {
- next = &n->head;
- break;
- }
- }
- list_add_tail(&c->head, next);
+ entry = calloc(1, sizeof(*entry));
+ if (!entry)
+ continue;
+
+ entry->node.key = c;
+ avl_insert(&assign_later, &entry->node);
}
if (c->assigned != -1)
assigned_any = true;
}
- // Then try to assign all other + failed custom assignments
- while (!list_empty(&assign_later)) {
- c = list_first_entry(&assign_later, struct
device_prefix_assignment, head);
- list_del(&c->head);
-
+ /* Then try to assign all other + failed custom assignments */
+ avl_for_each_element_safe(&assign_later, entry, node, n_entry) {
bool assigned = false;
+
+ c = (struct device_prefix_assignment *)entry->node.key;
+ avl_delete(&assign_later, &entry->node);
+
do {
assigned =
interface_prefix_assign(&prefix->assignments, c);
} while (!assi
Re: [LEDE-DEV] [OpenWrt-Devel] Bounty: simplify extracting/restoring kernel .config
On 01/31/2017 04:05 PM, Felix Fietkau wrote: > On 2017-01-31 16:04, Zoltan Gyarmati wrote: >> On 01/31/2017 10:19 AM, Felix Fietkau wrote: >>> On 2017-01-29 22:37, Philip Prindeville wrote: Hi. I’m working on a project where I need to be able to force certain kernel configuration parameters from a script, to automate building tailored kernels for performance testing, certification, etc. I love the way that I can use “scripts/diffconfig.sh” to save the deltas into a file… update the cloning/checkout of master over time, yet retain my saved overrides by doing a “cp ../my.config .config ; make defconfig oldconfig” and always end up with a known/good configuration. Alas, I can’t do the same for the target kernel in a scripted way. I’d like to put out a bounty for doing so. If you’re interested, contact me via email to discuss the deliverable and the terms of payment. Ideally, this would be of broad enough applicability that I’d want to upstream this back to OpenWRT for everyone, so keep that in mind as well. >>> This is already implemented. You can put any kernel configuration >>> overrides into env/kernel-config. >>> Generating those is fairly easy too, you can use this command: >>> make kernel_menuconfig CONFIG_TARGET=env >>> You can also put a full kernel config in that file instead of a delta. >>> Running make kernel_oldconfig CONFIG_TARGET=env afterwards will reduce >>> that full config to a delta relative to the defaults that LEDE uses. >> Dear Felix & All, >> >> might be slightly off-topic, but: Is there any similar mechanism to >> customize/override not only the kernel config but also the device tree file? > Not really. What's your use case for this? Adding an i2c RTC to the RT5350F-OLinuXino board. It's already requires patching the dts file to enable the i2c port, but that change i want to sent to upstream (as that is generally useful), while adding my type of RTC chip to the device tree is specific to my config, so i would like to keep it separated. The obvious solution is to to maintain my customization patches on the top of the upstream, but if it's possible i want to avoid that, for which it would be perfect to keep it in an 'env'. Thx, > > - Felix > Zoltan Gyarmati https://zgyarmati.de Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] Bounty: simplify extracting/restoring kernel .config
On 2017-01-31 16:04, Zoltan Gyarmati wrote: > On 01/31/2017 10:19 AM, Felix Fietkau wrote: >> On 2017-01-29 22:37, Philip Prindeville wrote: >>> Hi. >>> >>> I’m working on a project where I need to be able to force certain >>> kernel configuration parameters from a script, to automate building >>> tailored kernels for performance testing, certification, etc. >>> >>> I love the way that I can use “scripts/diffconfig.sh” to save the >>> deltas into a file… update the cloning/checkout of master over time, >>> yet retain my saved overrides by doing a “cp ../my.config .config ; >>> make defconfig oldconfig” and always end up with a known/good >>> configuration. >>> >>> Alas, I can’t do the same for the target kernel in a scripted way. >>> >>> I’d like to put out a bounty for doing so. If you’re interested, >>> contact me via email to discuss the deliverable and the terms of >>> payment. >>> >>> Ideally, this would be of broad enough applicability that I’d want to >>> upstream this back to OpenWRT for everyone, so keep that in mind as >>> well. >> This is already implemented. You can put any kernel configuration >> overrides into env/kernel-config. >> Generating those is fairly easy too, you can use this command: >> make kernel_menuconfig CONFIG_TARGET=env >> You can also put a full kernel config in that file instead of a delta. >> Running make kernel_oldconfig CONFIG_TARGET=env afterwards will reduce >> that full config to a delta relative to the defaults that LEDE uses. > > Dear Felix & All, > > might be slightly off-topic, but: Is there any similar mechanism to > customize/override not only the kernel config but also the device tree file? Not really. What's your use case for this? - Felix ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [OpenWrt-Devel] Bounty: simplify extracting/restoring kernel .config
On 01/31/2017 10:19 AM, Felix Fietkau wrote: > On 2017-01-29 22:37, Philip Prindeville wrote: >> Hi. >> >> I’m working on a project where I need to be able to force certain >> kernel configuration parameters from a script, to automate building >> tailored kernels for performance testing, certification, etc. >> >> I love the way that I can use “scripts/diffconfig.sh” to save the >> deltas into a file… update the cloning/checkout of master over time, >> yet retain my saved overrides by doing a “cp ../my.config .config ; >> make defconfig oldconfig” and always end up with a known/good >> configuration. >> >> Alas, I can’t do the same for the target kernel in a scripted way. >> >> I’d like to put out a bounty for doing so. If you’re interested, >> contact me via email to discuss the deliverable and the terms of >> payment. >> >> Ideally, this would be of broad enough applicability that I’d want to >> upstream this back to OpenWRT for everyone, so keep that in mind as >> well. > This is already implemented. You can put any kernel configuration > overrides into env/kernel-config. > Generating those is fairly easy too, you can use this command: > make kernel_menuconfig CONFIG_TARGET=env > You can also put a full kernel config in that file instead of a delta. > Running make kernel_oldconfig CONFIG_TARGET=env afterwards will reduce > that full config to a delta relative to the defaults that LEDE uses. Dear Felix & All, might be slightly off-topic, but: Is there any similar mechanism to customize/override not only the kernel config but also the device tree file? > > - Felix > ___ > openwrt-devel mailing list > openwrt-de...@lists.openwrt.org > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel Thx in advance, regards, Zoltan Gyarmati https://zgyarmati.de signature.asc Description: OpenPGP digital signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH] bcm53xx: fix LAN MAC address for devices that use eth2 originally
From: Rafał Miłecki We override default Ethernet interface with eth0 which often uses random MAC due to missing proper NVRAM entry. Fix this by manually assigning MAC in the config. Signed-off-by: Rafał Miłecki --- target/linux/bcm53xx/base-files/etc/board.d/02_network | 6 ++ 1 file changed, 6 insertions(+) diff --git a/target/linux/bcm53xx/base-files/etc/board.d/02_network b/target/linux/bcm53xx/base-files/etc/board.d/02_network index 672b1349df..3c19b574b8 100755 --- a/target/linux/bcm53xx/base-files/etc/board.d/02_network +++ b/target/linux/bcm53xx/base-files/etc/board.d/02_network @@ -50,6 +50,12 @@ netgear,r8500) ifname=eth0 ucidef_add_switch "switch0" \ "0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "5t@$ifname" + + # These devices should use eth2 and their eth0 interface often has no + # MAC assigned. Manually assign eth2's MAC to the LAN. + et2macaddr="$(echo $(nvram get et2macaddr))" + [ -n "$et2macaddr" ] && ucidef_set_interface_macaddr "lan" "$et2macaddr" + board_config_flush exit 0 ;; -- 2.11.0 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] python3 compile error
Hello, Today I start a fresh new build for Clearfog Pro on Ubuntu 16.04. I got a error message from python3 as make[2]: Entering directory '/home/lx/clearfog/octu-lede/feeds/packages/lang/python3' CFLAGS="-Os -pipe -mcpu=cortex-a9 -mfpu=vfpv3-d16 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap /home/lx/clearfog/octu-lede/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/Python-3.6.0:Python-3.6.0 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -DNDEBUG -fno-inline -I/home/lx/clearfog/octu-lede/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/usr/include -I/home/lx/clearfog/octu-lede/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/include -I/home/lx/clearfog/octu-lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl-1.1.16_eabi/usr/include -I/home/lx/clearfog/octu-lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl-1.1.16_eabi/include/fortify -I/home/lx/clearfog/octu-lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl-1.1.16_eabi/include " CXXFLAGS="-Os -pipe -mcpu=cortex-a9 -mfpu=vfpv3-d16 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap /home/lx/clearfog/octu-lede/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/Python-3.6.0:Python-3.6.0 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -DNDEBUG -fno-inline -I/home/lx/clearfog/octu-lede/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/usr/include -I/home/lx/clearfog/octu-lede/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/include -I/home/lx/clearfog/octu-lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl-1.1.16_eabi/usr/include -I/home/lx/clearfog/octu-lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl-1.1.16_eabi/include/fortify -I/home/lx/clearfog/octu-lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl-1.1.16_eabi/include " LDFLAGS="-L/home/lx/clearfog/octu-lede/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/usr/lib -L/home/lx/clearfog/octu-lede/staging_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/lib -L/home/lx/clearfog/octu-lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl-1.1.16_eabi/usr/lib -L/home/lx/clearfog/octu-lede/staging_dir/toolchain-arm_cortex-a9+vfpv3_gcc-5.4.0_musl-1.1.16_eabi/lib -znow -zrelro -L/home/lx/clearfog/octu-lede/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/Python-3.6.0" make -C /home/lx/clearfog/octu-lede/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/Python-3.6.0/. AR="arm-openwrt-linux-muslgnueabi-gcc-ar" AS="arm-openwrt-linux-muslgnueabi-gcc -c -Os -pipe -mcpu=cortex-a9 -mfpu=vfpv3-d16 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap /home/lx/clearfog/octu-lede/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/Python-3.6.0:Python-3.6.0 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro" LD=arm-openwrt-linux-muslgnueabi-ld NM="arm-openwrt-linux-muslgnueabi-gcc-nm" CC="arm-openwrt-linux-muslgnueabi-gcc" GCC="arm-openwrt-linux-muslgnueabi-gcc" CXX="arm-openwrt-linux-muslgnueabi-g++" RANLIB="arm-openwrt-linux-muslgnueabi-gcc-ranlib" STRIP=arm-openwrt-linux-muslgnueabi-strip OBJCOPY=arm-openwrt-linux-muslgnueabi-objcopy OBJDUMP=arm-openwrt-linux-muslgnueabi-objdump SIZE=arm-openwrt-linux-muslgnueabi-size CROSS="arm-openwrt-linux-muslgnueabi-" ARCH="arm" CROSS_COMPILE=yes LD="arm-openwrt-linux-muslgnueabi-gcc" PGEN=pgen3 ; make[3]: Entering directory '/home/lx/clearfog/octu-lede/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/Python-3.6.0' running build running build_ext INFO: Can't locate Tcl/Tk libs and/or headers building '_curses' extension arm-openwrt-linux-muslgnueabi-gcc -fPIC -Wno-unused-result -Wsign-compare -DNDEBUG -Os -pipe -mcpu=cortex-a9 -mfpu=vfpv3-d16 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap /home/lx/clearfog/octu-lede/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/Python-3.6.0:Python-3.6.0 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -Os -pipe -mcpu=cortex-a9 -mfpu=vfpv3-d16 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap /home/lx/clearfog/octu-lede/build_dir/target-arm_cortex-a9+vfpv3_musl-1.1.16_eabi/Python-3.6.0:Python-3.6.0 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -DNDEBUG -fno-inline -Os -pipe -mcpu=cortex-a9 -mfpu=vfpv3-d16 -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -iremap /ho
Re: [LEDE-DEV] LEDE-17.01 Final Release Notes available
On Tue, 2017-01-31 at 10:54 +0100, Baptiste Jonglez wrote: > > - IPv6 support: since that was the focus of CC, at least mention that > nothing was intentionally broken (and maybe there were some > improvement?)] What was the IPv6 problem? I updated my VDSL router and separate AP to 17.01 over the weekend, and haven't seen any problems. My ISP does do prefix delegation and I suppose I *ought* to check that works out of the box, but haven't looked hard at it yet. I did have missing *Legacy* IP routing for a while until I finally noticed, but that was just a configuration issue :) smime.p7s Description: S/MIME cryptographic signature ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] LEDE-17.01 Final Release Notes available
Hi,
Thanks for taking care of this!
On Fri, Jan 27, 2017 at 06:57:40PM -0500, Rich Brown wrote:
> Since no changes have occurred to the release notes in the last 5 days, I
> assume they are complete and final.
>
> If you wish to prove me wrong, please send me a note, or update them directly
> at: https://lede-project.org/playground/draft-release-notes
I have added a few more things, like precise version numbers of some
software compared to CC.
Some things I am not sure about:
- for the toolchain, there are both GCC 6.3.0 and GCC 5.4.0 in the source,
which one is used for which architecture?
Some things that I think should be there:
- IPv6 support: since that was the focus of CC, at least mention that
nothing was intentionally broken (and maybe there were some
improvement?)
- support for 3G/4G modem: I think there was some work in this direction
- release management: mention that this release should be future-proof,
unlike CC which broke kernel dependencies in a minor release. Also,
packages will get {bugfix,security} updates throughout the lifetime of
the release.
I will try to improve these points today of tomorrow.
> I have pasted the current text below for your reading pleasure. Thanks, and
> congratulations on the great work!
>
> Rich
>
> ---
>
> LEDE 17.xx First Stable Release - MMM 2017
>
> _
> //\ ____ ___ ___
>/ LE/ \| | | __| \| __|
> /DE /\ | |__| _|| |) | _|
> // LE \ ||___|___/|___| lede-project.org
> \\ DE /
> \LE \/ ---
>\ DE\ /Reboot (17.01-SNAPSHOT, r-1234567)
> \\/---
>
> THIS IS THE FINAL DRAFT. LAST CHANCE TO MAKE IT BETTER.
> [Final changes include updating “17.xx” everywhere, “MMM 2017” everywhere,
> final “Reboot” name/version/commit, actual URL for downloads.]
>
> The LEDE Project (“Linux Embedded Development Environment”) is a Linux
> operating system based on OpenWrt. It is a complete replacement for the
> vendor-supplied firmware of a wide range of wireless routers and non-network
> devices. See the Table of Hardware for supported devices. For more
> information about LEDE Project organization, see the About LEDE pages.
>
> Get LEDE Firmware at: http://downloads.lede-project.org/releases/
>
> Highlights In LEDE 17.xx
>
> The LEDE Community is proud to announce the first stable release of LEDE
> 17.xx. It incorporates thousands of commits over the last nine months of
> effort. With this release, the LEDE development team closes out an intense
> effort to modernize many parts of OpenWrt and incorporate many new modules,
> packages, and technologies. These are some of the highlights compared to
> OpenWrt Chaos Calmer:
>
> • Linux kernel updated to version 4.4.42
> • Improved Security Features
> • Memory Corruption Mitigation Methods
> • gcc -Wformat -Wformat-security
> • User space Stack-Smashing Protection (Regular)
> • Kernel space Stack-Smashing Protection (Regular)
> • buffer-overflows detection (FORTIFY_SOURCE)
> (Conservative)
> • RELRO protection (Full)
> • Improved Networking Support
> • Smart Queue Management (SQM) minimizes bufferbloat by using
> the cake and fq_codel qdisc's. More...
> • Improvements to the WiFi stack eliminating bufferbloat on
> ath9k (and some ath10k) chipsets
> • Improved Performance
> • Nothing specific.
> • Updated toolchain
> • musl 1.1.15
> • gcc 5.4.0
> • binutils 2.25.1
> • Platform and Driver Support
> • Lantiq
> • Added redistributable DSL firmware
> • Updated DSL phy drivers
> • Added new targets:
> • apm821xx (AppliedMicro APM821xx)
> • arc770 (Synopsys DesignWare ARC 770D)
> • archs38 (Synopsys DesignWare ARC HS38)
> • armvirt (QEMU ARM Virtual Machine)
> • ipq806x (Qualcomm Atheros IPQ806X)
> • layerscape (NXP Layerscape)
> • zynq (Xilinx Zynq 7000 SoCs)
> • New build system supports easier branching
> • Building different root file systems for different devices at
> once
> • Added support for a many new routers and boards
> • And lots and lots of other advancements…
> As always, a big thank you goes to all our active package maintainers,
> testers, documenters, and supporters.
>
> Have fun!
>
> The LEDE Community
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradea
Re: [LEDE-DEV] Build error Arcadyan VGV7510KW22(NOR) / o2 6431 - asterisk13
Hi Baptiste, >Please report this bug to the specific package feed: >https://github.com/openwrt/telephony thanks, i did https://github.com/openwrt/telephony/issues/133[https://github.com/openwrt/telephony/issues/133] Dennis Gesendet: Dienstag, 31. Januar 2017 um 10:30 Uhr Von: "Baptiste Jonglez" An: "Dennis Schneck" Cc: lede-dev@lists.infradead.org Betreff: Re: [LEDE-DEV] Build error Arcadyan VGV7510KW22(NOR) / o2 6431 - asterisk13 Hi Dennis, Please report this bug to the specific package feed: https://github.com/openwrt/telephony[https://github.com/openwrt/telephony] It simply looks like a missing dependency (libxml), but bug reports like this should go there, so that maintainers can do something. Baptiste On Tue, Jan 31, 2017 at 10:10:13AM +0100, Dennis Schneck wrote: > Hello, > i downloaded the source with: git clone > https://github.com/lede-project/source[https://github.com/lede-project/source] > > Select for VGV7510KW22 ( see attach please! .config as _config ) > > Target System (Lantiq) > Subtarget (XRX200) > Target Profile (o2 Box 6431 / Arcadyan VGV7510KW22 (NOR) > > > Base system -> block-mount > Base system -> sqm-scripts > > Kernel modules -> Filesystems -> kmod-fs-ext4 > Kernel modules -> USB Support -> kmod-usb-storage > > LuCI -> Collections -> luci > LuCI -> Applications -> luci-app-sqm > > Firmware -> dsl-vrx200-firmware-xdsl-b > > Network -> Telephony -> asterisk13 > Network -> Telephony -> asterisk13 ->asterisk13-app-directed_pickup > Network -> Telephony -> asterisk13 ->asterisk13-app-read > Network -> Telephony -> asterisk13 ->asterisk13-app-stack > Network -> Telephony -> asterisk13 ->asterisk13-app-system > Network -> Telephony -> asterisk13 ->asterisk13-cdr > Network -> Telephony -> asterisk13 ->asterisk13-cdr-csv > Network -> Telephony -> asterisk13 ->asterisk13-chan-sip > Network -> Telephony -> asterisk13 ->asterisk13-codec-a-mu > Network -> Telephony -> asterisk13 ->asterisk13-codec-alaw > Network -> Telephony -> asterisk13 ->asterisk13-codec-g722 > Network -> Telephony -> asterisk13 ->asterisk13-codec-g726 > Network -> Telephony -> asterisk13 ->asterisk13-codec-gsm > Network -> Telephony -> asterisk13 ->asterisk13-codec-ilbc > Network -> Telephony -> asterisk13 ->asterisk13-codec-resample > Network -> Telephony -> asterisk13 ->asterisk13-codec-ulaw > Network -> Telephony -> asterisk13 ->asterisk13-format-gsm > Network -> Telephony -> asterisk13 ->asterisk13-format-sln > Network -> Telephony -> asterisk13 ->asterisk13-func-blacklist > Network -> Telephony -> asterisk13 ->asterisk13-func-groupcount > Network -> Telephony -> asterisk13 ->asterisk13-pbx-spool > Network -> Telephony -> asterisk13 ->asterisk13-res-rtp-asterisk > > Languages -> perl > Languages -> perl -> perl-html-tree > Languages -> perl -> perl-http-message > > Mail -> mailsend > > > > But asterisk13 build fail. > > checking for strcasestr... yes > checking for strndup... yes > checking for strnlen... yes > checking for strsep... yes > checking for unsetenv... yes > checking for vasprintf... yes > checking for initscr in -lncurses... yes > checking curses.h usability... yes > checking curses.h presence... yes > checking for curses.h... yes > checking for a sed that does not truncate output... > /home/dennis/Downloads/o26431-vmmc_v3/source/staging_dir/host/bin/sed > checking for xml2-config... > /home/dennis/Downloads/o26431-vmmc_v3/source/staging_dir/target-mips_24kc_musl-1.1.16/host/bin/xml2-config > configure: error: Could not find required 'Libxml2' development package > make[3]: *** [Makefile:291: > /home/dennis/Downloads/o26431-vmmc_v3/source/build_dir/target-mips_24kc_musl-1.1.16/asterisk-13.9.1/.configured_yyy] > Error 1 > make[3]: Leaving directory > '/home/dennis/Downloads/o26431-vmmc_v3/source/feeds/telephony/net/asterisk-13.x' > make[2]: *** [package/Makefile:108: > package/feeds/telephony/asterisk-13.x/compile] Error 2 > make[2]: Leaving directory '/home/dennis/Downloads/o26431-vmmc_v3/source' > make[1]: *** [package/Makefile:102: > /home/dennis/Downloads/o26431-vmmc_v3/source/staging_dir/target-mips_24kc_musl-1.1.16/stamp/.package_compile] > Error 2 > make[1]: Leaving directory '/home/dennis/Downloads/o26431-vmmc_v3/source' > make: *** > [/home/dennis/Downloads/o26431-vmmc_v3/source/include/toplevel.mk:199: world] > Error 2 > > > > How to fix this ? > > Many thanks to Stefan Koch for his helping hand! > > > Using Manjaro Linux to build the Image > have installed this packages: > > pacman -S --needed subversion asciidoc bash bc binutils bzip2 fastjar flex > git gcc util-linux gawk intltool zlib make cdrkit ncurses openssl patch > perl-extutils-makemaker rsync sdcc unzip wget gettext libxslt boost libusb > bin86 sharutils b43-fwcutter findutils > > https://wiki.openwrt.org/doc/howto/buildroot.exigence[https://wiki.openwrt.org/doc/howto/buildroot.exigence] > > Thanks > > Dennis > > $ make > Checking 'rsync'... ok. > make[1] world > make[2] target/compile > make[
Re: [LEDE-DEV] Build error Arcadyan VGV7510KW22(NOR) / o2 6431 - asterisk13
Hi Dennis, Please report this bug to the specific package feed: https://github.com/openwrt/telephony It simply looks like a missing dependency (libxml), but bug reports like this should go there, so that maintainers can do something. Baptiste On Tue, Jan 31, 2017 at 10:10:13AM +0100, Dennis Schneck wrote: > Hello, > i downloaded the source with: git clone https://github.com/lede-project/source > > Select for VGV7510KW22 ( see attach please! .config as _config ) > > Target System (Lantiq) > Subtarget (XRX200) > Target Profile (o2 Box 6431 / Arcadyan VGV7510KW22 (NOR) > > > Base system -> block-mount > Base system -> sqm-scripts > > Kernel modules -> Filesystems -> kmod-fs-ext4 > Kernel modules -> USB Support -> kmod-usb-storage > > LuCI -> Collections -> luci > LuCI -> Applications -> luci-app-sqm > > Firmware -> dsl-vrx200-firmware-xdsl-b > > Network -> Telephony -> asterisk13 > Network -> Telephony -> asterisk13 ->asterisk13-app-directed_pickup > Network -> Telephony -> asterisk13 ->asterisk13-app-read > Network -> Telephony -> asterisk13 ->asterisk13-app-stack > Network -> Telephony -> asterisk13 ->asterisk13-app-system > Network -> Telephony -> asterisk13 ->asterisk13-cdr > Network -> Telephony -> asterisk13 ->asterisk13-cdr-csv > Network -> Telephony -> asterisk13 ->asterisk13-chan-sip > Network -> Telephony -> asterisk13 ->asterisk13-codec-a-mu > Network -> Telephony -> asterisk13 ->asterisk13-codec-alaw > Network -> Telephony -> asterisk13 ->asterisk13-codec-g722 > Network -> Telephony -> asterisk13 ->asterisk13-codec-g726 > Network -> Telephony -> asterisk13 ->asterisk13-codec-gsm > Network -> Telephony -> asterisk13 ->asterisk13-codec-ilbc > Network -> Telephony -> asterisk13 ->asterisk13-codec-resample > Network -> Telephony -> asterisk13 ->asterisk13-codec-ulaw > Network -> Telephony -> asterisk13 ->asterisk13-format-gsm > Network -> Telephony -> asterisk13 ->asterisk13-format-sln > Network -> Telephony -> asterisk13 ->asterisk13-func-blacklist > Network -> Telephony -> asterisk13 ->asterisk13-func-groupcount > Network -> Telephony -> asterisk13 ->asterisk13-pbx-spool > Network -> Telephony -> asterisk13 ->asterisk13-res-rtp-asterisk > > Languages -> perl > Languages -> perl -> perl-html-tree > Languages -> perl -> perl-http-message > > Mail -> mailsend > > > > But asterisk13 build fail. > > checking for strcasestr... yes > checking for strndup... yes > checking for strnlen... yes > checking for strsep... yes > checking for unsetenv... yes > checking for vasprintf... yes > checking for initscr in -lncurses... yes > checking curses.h usability... yes > checking curses.h presence... yes > checking for curses.h... yes > checking for a sed that does not truncate output... > /home/dennis/Downloads/o26431-vmmc_v3/source/staging_dir/host/bin/sed > checking for xml2-config... > /home/dennis/Downloads/o26431-vmmc_v3/source/staging_dir/target-mips_24kc_musl-1.1.16/host/bin/xml2-config > configure: error: Could not find required 'Libxml2' development package > make[3]: *** [Makefile:291: > /home/dennis/Downloads/o26431-vmmc_v3/source/build_dir/target-mips_24kc_musl-1.1.16/asterisk-13.9.1/.configured_yyy] > Error 1 > make[3]: Leaving directory > '/home/dennis/Downloads/o26431-vmmc_v3/source/feeds/telephony/net/asterisk-13.x' > make[2]: *** [package/Makefile:108: > package/feeds/telephony/asterisk-13.x/compile] Error 2 > make[2]: Leaving directory '/home/dennis/Downloads/o26431-vmmc_v3/source' > make[1]: *** [package/Makefile:102: > /home/dennis/Downloads/o26431-vmmc_v3/source/staging_dir/target-mips_24kc_musl-1.1.16/stamp/.package_compile] > Error 2 > make[1]: Leaving directory '/home/dennis/Downloads/o26431-vmmc_v3/source' > make: *** > [/home/dennis/Downloads/o26431-vmmc_v3/source/include/toplevel.mk:199: world] > Error 2 > > > > How to fix this ? > > Many thanks to Stefan Koch for his helping hand! > > > Using Manjaro Linux to build the Image > have installed this packages: > > pacman -S --needed subversion asciidoc bash bc binutils bzip2 fastjar flex > git gcc util-linux gawk intltool zlib make cdrkit ncurses openssl patch > perl-extutils-makemaker rsync sdcc unzip wget gettext libxslt boost libusb > bin86 sharutils b43-fwcutter findutils > > https://wiki.openwrt.org/doc/howto/buildroot.exigence > > Thanks > > Dennis > > $ make > Checking 'rsync'... ok. > make[1] world > make[2] target/compile > make[3] -C target/linux compile > make[2] package/cleanup > make[2] package/compile > make[3] -C package/libs/toolchain compile > make[3] -C package/libs/libnl-tiny compile > make[3] -C package/libs/libjson-c compile > make[3] -C package/utils/lua compile > make[3] -C package/libs/libubox compile > make[3] -C package/system/ubus compile > make[3] -C package/system/uci compile > make[3] -C package/network/config/netifd compile > make[3] -C package/system/ubox compile > make[3] -C package/libs/ncurses host-compile > make[3] -C package/libs/ncurses c
Re: [LEDE-DEV] Bounty: simplify extracting/restoring kernel .config
On 2017-01-29 22:37, Philip Prindeville wrote: > Hi. > > I’m working on a project where I need to be able to force certain > kernel configuration parameters from a script, to automate building > tailored kernels for performance testing, certification, etc. > > I love the way that I can use “scripts/diffconfig.sh” to save the > deltas into a file… update the cloning/checkout of master over time, > yet retain my saved overrides by doing a “cp ../my.config .config ; > make defconfig oldconfig” and always end up with a known/good > configuration. > > Alas, I can’t do the same for the target kernel in a scripted way. > > I’d like to put out a bounty for doing so. If you’re interested, > contact me via email to discuss the deliverable and the terms of > payment. > > Ideally, this would be of broad enough applicability that I’d want to > upstream this back to OpenWRT for everyone, so keep that in mind as > well. This is already implemented. You can put any kernel configuration overrides into env/kernel-config. Generating those is fairly easy too, you can use this command: make kernel_menuconfig CONFIG_TARGET=env You can also put a full kernel config in that file instead of a delta. Running make kernel_oldconfig CONFIG_TARGET=env afterwards will reduce that full config to a delta relative to the defaults that LEDE uses. - Felix ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
