On 12-09-16 06:10, Yousong Zhou wrote:
> On 12 September 2016 at 00:12, Stijn Tintel wrote:
>> Signed-off-by: Stijn Tintel
>> ---
>> package/boot/uboot-envtools/files/ar71xx | 1 +
>> target/linux/ar71xx/base-files/etc/board.d/01_leds | 5 +
>> .../linux/ar71xx/base-files/etc/board
On Wednesday, October 12, 2016 2:05:15 PM CEST Matthias Schiffer wrote:
> On 10/12/2016 01:42 PM, Jonas Gorski wrote:
> > On 11 October 2016 at 13:37, Christian Lamparter
> > wrote:
> >> Previously, wifi detect simply dumped its generated wireless
> >> configuration out to STDOUT. A second step wa
For those of you who are attending OpenWrt Summit, I'm looking forward
to seeing you!
For those who aren't able to make it, I wanted to let you know that
OpenWrt Summit will be live streamed on Youtube. We have links for
almost all the sessions at OpenWrtSummit.org and the last few will be
added b
Hello,
On Wednesday, October 12, 2016 1:32:38 PM CEST Jonas Gorski wrote:
> On 11 October 2016 at 13:37, Christian Lamparter
> wrote:
> > Currently, the wifi detection script is executed as part of
> > the (early) boot process. Pluggable wifi USB devices, which
> > are inserted at a later time ar
2016-10-12 13:32 GMT+02:00 Jonas Gorski :
>> diff --git a/package/kernel/mac80211/Makefile
>> b/package/kernel/mac80211/Makefile
>> index 91c9362..f320326 100644
>> --- a/package/kernel/mac80211/Makefile
>> +++ b/package/kernel/mac80211/Makefile
>> @@ -1732,6 +1732,8 @@ define KernelPackage/cfg802
Hi,
I have been using openWRT CC 1505, but want to start using LEDE. I built
for the WPJ344, but didn't get pings to or from my PC.
I have a serial connection to the wpj344, so i can look at demsg without
an eth connection.
For CC, the relevent lines are (some spacing added):
...
[0.85]
Hi,
Found the bug.
In going from CC linux 3.16.36 to LEDE 4.4.24, I guess a lot of changes
had to be made. But, also, the sense and name of
\target\linux\generic\files\include\linux\ar8216_platform.h struct
ar8327_pad_cfg bool mac06_exchange_dis
was changed from mac06_exchange_en, without
If core packages are overridden, CONFIG_OVERRIDE_PKGS is set
based on the scan order of packages, which eventually causes
that config value to be modified on each build and with
that causes the build process to warn for configuration
being out of sync.
This commit changes the CONFIG_OVERRIDE_PKGS
- unify configs of host/target
- disable stuff to decrease build time
- disable interactive gettextize: see
http://lists.busybox.net/pipermail/buildroot/2014-April/093394.html
Signed-off-by: Dirk Neukirchen
---
package/libs/gettext-full/Makefile | 18 ++
packa
Daniel Engberg asked for updates and I have this series in my local tree
since some time but hesitated to commit
I did several builds with all packages/kmods for ar71xx and
probably other targets I cannot remember and have seen no issues
from this patch on my build system
__
0.19.8.1 gettext-full uses "archive-version" of 0.19.8
to replace makros, leading to breakage of PKG_FIXUP:=gettext-version
Signed-off-by: Dirk Neukirchen
---
include/autotools.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/autotools.mk b/include/autotools.mk
inde
Signed-off-by: Dirk Neukirchen
---
package/libs/gettext/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/libs/gettext/Makefile b/package/libs/gettext/Makefile
index cb4ee12..1672b47 100644
--- a/package/libs/gettext/Makefile
+++ b/package/libs/gettext/Makefile
Matthias Schiffer wrote:
> Hi,
> {*} means that the package can't be disabled completely, but it can be set
> to M. This should give you the desired behaviour.
Right, ok. This is one of those things that's not in the Kconfig
legend. (Not in kernel upstream either, just magic knowledge) I
presume
When selecting devices from the Target Devices menu, the brand choices
of naming makes it confusing to find particular devices by name, as the
sorting is case sensitve. AirTight came after ALFA, and devolo and
jjPlus both came after Zyxel.
This does _not_ apply to the Target Profile list, as that
TARGET_MULTI_PROFILE and TARGET_PER_DEVICE_ROOTFS get some help text to
try and clarify their behaviour.
Signed-off-by: Karl Palsson
---
scripts/target-metadata.pl | 17 +
1 file changed, 17 insertions(+)
diff --git a/scripts/target-metadata.pl b/scripts/target-metadata.pl
index
OpenWrt uses ancient u-boot thats not reproducible.
There are multiple upstream changes that introduce
reproducible builds like:
859e92b775fd8ebcfacc591eaf621b677c95b6f7
(not used here - the CMD_DATE/TIMESTAMP functionality
seems to be disabled by config)
70d39f57146a6cb94736db39c770c3d95e07bedb
On 10/12/2016 01:42 PM, Jonas Gorski wrote:
> On 11 October 2016 at 13:37, Christian Lamparter
> wrote:
>> Previously, wifi detect simply dumped its generated wireless
>> configuration out to STDOUT. A second step was needed to
>> append the configuration to /etc/config/wireless (or create
>> it,
On 10 October 2016 at 03:24, YuheiOKAWA wrote:
> SOC:MT7621A
> RAM:256MiB
> NOR:MX25L51245G
>
> Non Wireless Router.
>
> Issue: soft reboot problem. SPI Flash donot exit 4byte address mode.
>
> Signed-off-by: YuheiOKAWA
There is some problem with patchwork and name assigned to Yuhei:
On 12 October 2016 at 13:16, Karl Palsson wrote:
> Rafał Miłecki wrote:
>> There are some (rare) devices with a button for disabling LEDs
>> (e.g. ASUS RT-AC68U). I'm looking for a way to support such a
>> feature. Maybe at some point we could also support it as an
>> extra feature triggerable f
On 11 October 2016 at 13:37, Christian Lamparter
wrote:
> Previously, wifi detect simply dumped its generated wireless
> configuration out to STDOUT. A second step was needed to
> append the configuration to /etc/config/wireless (or create
> it, if it didn't exist).
>
> With this patch, The wifi d
Hi,
On 11 October 2016 at 13:37, Christian Lamparter
wrote:
> Currently, the wifi detection script is executed as part of
> the (early) boot process. Pluggable wifi USB devices, which
> are inserted at a later time are not automatically
> detected and therefore they don't show up in LuCI.
>
> A u
On 10/12/2016 12:59 PM, Karl Palsson wrote:
>
> Hi,
>
> I was trying to add help text to the generated Kconfig for the
> CONFIG_TARGET_MULTI_PROFILE and CONFIG_TARGET_PER_DEVICE_ROOTFS
> settings based on some irc conversations with nbd, and was trying
> out the behaviour to verify my help text.
Rafał Miłecki wrote:
> There are some (rare) devices with a button for disabling LEDs
> (e.g. ASUS RT-AC68U). I'm looking for a way to support such a
> feature. Maybe at some point we could also support it as an
> extra feature triggerable from UI.
>
> So basically I probably need to add some s
From: Alexandru Ardelean
We seem to be getting timeout for ubus wait_for calls
every now and then.
And it's not reliably reproducible.
Looking at the code the only thing that would look like
a potetntial reason, is that between the ubus_lookup() and
ubus_register_event_handler() calls, there's a
On 10/07/2016 03:19 PM, Zefir Kurtisi wrote:
> On 10/07/2016 02:15 PM, Alexandru Ardelean wrote:
>> On Fri, Oct 7, 2016 at 3:09 PM, Felix Fietkau wrote:
>>> Instead of introducing yet another timer, wouldn't it also be possible
>>> to close this race window by registering the event handler before
Hi,
I was trying to add help text to the generated Kconfig for the
CONFIG_TARGET_MULTI_PROFILE and CONFIG_TARGET_PER_DEVICE_ROOTFS
settings based on some irc conversations with nbd, and was trying
out the behaviour to verify my help text.
The text I've got for per device rootfs is:
"When disabl
Sorry was to quick about this one. Qemu 2.7.0 added a glib2 dependency,
which worked for me because I had glib2 installed in my local directory.
Please ignore this one. Thanks!
On 12.10.2016 10:37, Ulrich Weber wrote:
> needed to support VHDS format for Azure.
> Allows qemu-img to use " -f raw -o
On 2016-10-12 10:37, Ulrich Weber wrote:
> needed to support VHDS format for Azure.
> Allows qemu-img to use " -f raw -o subformat=fixed"
>
> Signed-off-by: Ulrich Weber
The new qemu version has a build dependency on glib (+ development
headers). Please either backport the format support to the o
There are some (rare) devices with a button for disabling LEDs (e.g.
ASUS RT-AC68U). I'm looking for a way to support such a feature. Maybe
at some point we could also support it as an extra feature triggerable
from UI.
So basically I probably need to add some smart /etc/rc.button/
handler. Unfort
needed to support VHDS format for Azure.
Allows qemu-img to use " -f raw -o subformat=fixed"
Signed-off-by: Ulrich Weber
---
tools/qemu/Makefile | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/qemu/Makefile b/tools/qemu/Makefile
index bffbaa4..4370039 100644
---
30 matches
Mail list logo
