On 2016-01-10 21:00, Daniel Curran-Dickinson wrote:
> Hi Felix,
>
> I sent this to the list, but since you seem to have taken an interest in
> this, I'm also sending direct; don't take that as a need to rush, just
> thought you might be interested.
Please don't send duplicate emails to me and
On 7 January 2016 at 07:53, Rafał Miłecki wrote:
> On 30 December 2015 at 12:10, Rafał Miłecki wrote:
>> Supported syntax is inspired by ethtool. Example usage:
>> swconfig dev switch0 port 2 set link "duplex half speed 100 autoneg off"
>
> Any comments to
Buildbot has not initiated any new builds since Friday.
All buildslaves sit idle waiting for new orders.
http://buildbot.openwrt.org:8010/buildslaves
http://buildbot.openwrt.org:8010/builders
It looks like the buildbot has somehow lost its triggering schedule.
Hmmm...actually this may be a case of an old non-POSIX conformant shell
I once had to work in.
Anyway any modern POSIX-compliant shell doesn't have this issue.
Regards,
Daniel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Hi,
On 10/01/16 06:42 AM, bittorf wireless )) Bastian Bittorf wrote:
+
+start() {
+ if [ -e /dev/rtc ]; then
+ hwclock -s
please use the short form [ -e /dev/rtc ] && ...
Per private mail I've learned this is the current codebase standard, so
will follow that, but the
Actually I must have been smoking something when I thought I saw that
problem (and no I don't actually). I think it must have been in
combination with some other error that I misremembered.
I just checked both bash and ash (and the docs) and they 'do the right
thing'.
Regards,
Daniel
On
This removes one patch which was applied upstream with commit
67b9bcd36906e12a15ffec19463afbbd6a41660e. All other patches were
refreshed.
Signed-off-by: Martin Blumenstingl
---
include/kernel-version.mk | 4 +--
I did one other test I hadn't thought of originally:
#!/bin/sh
set -e
/bin/false && /bin/false
echo "not killed"
displays "not killed", so there still the issue that unlike if..then
with set -e, && fails to exit on error condition (for the purposes of
set -e it's like there is an implicit
Change MTD on WNDR4300 and WNDR3700v4 to fully utilize the 128MB flash.
Credit to @Tuochenlyu on GitHub. Original patch here:
https://github.com/openwrt-mirror/openwrt/commit/1dbb652ea0594c284710ace5e479c1ac7fdd1cbb
Formally submitting this patch so that it is available upstream.
---
This patch expands the MTD layout on the Netgear WNDR4300 and WNDR3700v4 to
allow use of the full 128MB flash.
I previously mentioned this patch here:
https://lists.openwrt.org/pipermail/openwrt-devel/2016-January/038507.html
The original patch can be found here:
Change MTD on WNDR4300 and WNDR3700v4 to fully utilize the 128MB flash.
Credit to @Tuochenlyu on GitHub.
Formally submitting this patch so that it is available upstream.
Signed-off-by: Chris Marchesi
---
target/linux/ar71xx/image/Makefile | 2 +-
1 file changed, 1
Great job!
May I know if the compile target for GL-AR150, GL-AR300, GL-Domino has been
backported to 15.05.1? They were submitted to trunk after CC1505. Hope they
have been back ported.
On Mon, Jan 11, 2016 at 8:12 PM, John Crispin wrote:
>
>
> On 11/01/2016 12:56, Hannu
On 11/01/16 04:05 PM, Felix Fietkau wrote:
On 2016-01-11 20:27, Eric Schultz wrote:
Felix,
Would it be unreasonable to have overridable defaults like suggested in
metadata.pl? Convention over configuration and all that.
I don't understand what you're asking. Could you elaborate?
To be
Oh crap - heh, forgot the no links part.
Will re-submit without links on the patch.
On Mon, Jan 11, 2016 at 9:33 PM, Chris Marchesi
wrote:
> Change MTD on WNDR4300 and WNDR3700v4 to fully utilize the 128MB flash.
>
> Credit to @Tuochenlyu on GitHub. Original patch
Anyone got any ideas on this one? Would just like to check to make sure I'm
not doing anything wrong or forgot to include a module before I go digging
further.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Change MTD on WNDR4300 and WNDR3700v4 to fully utilize the 128MB flash.
Credit to @Tuochenlyu on GitHub.
Formally submitting this patch so that it is available upstream.
---
target/linux/ar71xx/image/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
And one more time because I forgot the signoff.
Can you tell this is my first time doing an email PR? ;)
On Mon, Jan 11, 2016 at 9:42 PM, Chris Marchesi
wrote:
> Change MTD on WNDR4300 and WNDR3700v4 to fully utilize the 128MB flash.
>
> Credit to @Tuochenlyu on
Thanks. These patches are not back ported. Can this be done? If not
possible, that is OK. But if this can be back ported to CC15.05.1, that
would be very helpful.
including these patches.
ar71xx: add GL-AR150 support V3
ar71xx: add GL-AR300 support V3
ar71xx: add GL-Domino Pi support V3
On
Hi Felix,
On 11/01/16 03:28 PM, Felix Fietkau wrote:
> This is close to what I had in mind in my earlier response. Yes, it's
> ugly, but it's a lot less ugly than taking your approach without dealing
> with the issues that I pointed out.
Since a bit of ugliness for improved user experience
On correction on the comments in the patch: The install target is
actually not applicable because it only applies to packages selected as
y vs. m and refers to install into an actual image. Packages which are
m can only be recorded as built from a compile section, and marking
packages from
On correction on the comments in the patch: The install target is
actually not applicable because it only applies to packages selected as
y vs. m and refers to install into an actual image. Packages which are
m can only be recorded as built from a compile section, and marking
packages from
On 12 January 2016 at 03:00, alzhao wrote:
> May I know if the compile target for GL-AR150, GL-AR300, GL-Domino has been
> backported to 15.05.1? They were submitted to trunk after CC1505. Hope they
> have been back ported.
OpenWrt is open source with public repo:
(Re-submitting as I needed to subscribe first... )
Thnx for the info. I presume I should then submit my request for proposal
within this mailing list? If so here is a bit more details surrounding my
use case:
It all started with this really well made documentation that I wished to
impleted
Actually I thought of a solution, but it starts to get ugly. A choice
submemenu with non-duplicate (i.e. TARGET_SINGLE_...) symbols that also
select TARGET_SINGLE, AND have all the normal TARGET_... depend on
!(TARGET_SYMBOL && !TARGET_SINGLE_..profile).
That would probably work, but it's
This add support for IGMP Snooping on atheros switches (disabled by default),
which avoids flooding the network with multicast data.
Tested on TL-WDR4300: disabling IGMP Snooping results in multicast flooding
on each specific port, enabling it back again prevents each port from
receiving all
On 2016-01-11 20:27, Eric Schultz wrote:
> Felix,
>
> Would it be unreasonable to have overridable defaults like suggested in
> metadata.pl? Convention over configuration and all that.
I don't understand what you're asking. Could you elaborate?
- Felix
On 2016-01-11 21:11, Daniel Dickinson wrote:
> On 11/01/16 08:35 AM, Felix Fietkau wrote:
>> I like the idea of allowing the user to select multiple profiles.
>> However, there also needs to be a clean and simple way to select a
>> single profile without going through the list and deselecting
On 2016-01-11 21:23, Daniel Dickinson wrote:
> Actually I thought of a solution, but it starts to get ugly. A choice
> submemenu with non-duplicate (i.e. TARGET_SINGLE_...) symbols that also
> select TARGET_SINGLE, AND have all the normal TARGET_... depend on
> !(TARGET_SYMBOL &&
On 11.1.2016 13:40, John Crispin wrote:
15.05.1 is almost ready built. i had to do a refresh build to get
felix's fixes from last night included. base builds finished last night
and i started the SDK builder this morning which normally takes 2-3
days. with a bit of luck 15.05.1 is ready early
On Mon, Jan 11, 2016 at 2:59 PM, John Crispin wrote:
> 0x1F40-0x1F400FFF means that its size is 0x1000. i think you having
> a off-by-one thinko ...
...and I think you are right!
Sorry for the noise, please drop this patch.
___
The samba package has been rebuilt and was uploaded to the Barrier
Breaker 14.07 repository due to multiple security issues.
VERSION
3.6.25-1 => 3.6.25-1.1
CHANGELOG
[Mon, 11 Jan 2016 11:57:36 + e483830]
This is a patch for CVE-2015-5252, CVE-2015-5296 and CVE-2015-5299. A
patchset for
Remove the "DEU test manager" code which has not been used for more than
two years (as the kernel module is not installed anymore since
aa65888e08ec7279cfecc24c5bfe71cf9a016b91).
This fixes compilation on kernel 4.3 (which removes
aead_request_set_assoc) and newer.
Signed-off-by: Martin
According to the datasheet says that the xbar register range is
0x1F40-0x1F400FFF. Thanks to John Crispin for looking it up.
Signed-off-by: Martin Blumenstingl
---
target/linux/lantiq/dts/vr9.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On 11/01/2016 12:28, Hannu Nyman wrote:
> Are there any plans for a CC 15.05.1 maintenance release? Or will DD
> 16.xx be the next one?
>
> There have been so many fixes to 15.05 that personally I would like to
> see a maintenance release 15.05.1. There have been both security fixes,
> but also
On 11/01/2016 12:56, Hannu Nyman wrote:
> On 11.1.2016 13:40, John Crispin wrote:
>> 15.05.1 is almost ready built. i had to do a refresh build to get
>> felix's fixes from last night included. base builds finished last night
>> and i started the SDK builder this morning which normally takes 2-3
Are there any plans for a CC 15.05.1 maintenance release? Or will DD 16.xx be
the next one?
There have been so many fixes to 15.05 that personally I would like to see a
maintenance release 15.05.1. There have been both security fixes, but also
new/improved features that should be adopted more
On 2016-01-11 06:16, open...@daniel.thecshore.com wrote:
> From: Daniel Dickinson
>
> Certain platforms have large numbers of possible images, and it can be
> desirable to build neither all images nor only a single image,
> therefore this patch makes selecting
Hello,
this series adds linux 4.4 support to the lantiq target.
It depends on the linux/generic 4.4.0 update because -rc8 contains a
build-fix for MIPS devices.
I have tested it on two (VRX200) devices:
- VGV7510KW22 (seems to work fine)
- TD-W8970 (the mtd_reads in mtd_split seem to only return
On 11/01/2016 14:51, Martin Blumenstingl wrote:
> According to the datasheet says that the xbar register range is
> 0x1F40-0x1F400FFF. Thanks to John Crispin for looking it up.
>
> Signed-off-by: Martin Blumenstingl
> ---
>
Upstream linux 4.2 commit 84be456f883c4685680fba8e5154b5f72e92957e
"remove " requires us to include linux/scatterlist.h
instead. This also works with older kernels (at least 4.1, thanks to
Hauke Mehrtens for testing).
Signed-off-by: Martin Blumenstingl
---
The samba package has been rebuilt and was uploaded to the Chaos Calmer
15.05 repository due to multiple security issues.
VERSION
3.6.25-4 => 3.6.25-5
CHANGELOG
[Tue, 5 Jan 2016 11:01:00 + 98bacec]
This is a patch for CVE-2015-5252, CVE-2015-5296 and CVE-2015-5299. A
patchset for these
I was looking at slabinfo and noticed something about uci. Executing
"uci commit" increases amount of "dentry" active objects.
# echo 2 > /proc/sys/vm/drop_caches
# egrep "dentry|kmalloc-64" /proc/slabinfo
dentry 559 2040136 301 : tunables 120 608 : sla
On 2016-01-11 13:19, Felix Fietkau wrote:
> On 2016-01-11 12:57, Rafał Miłecki wrote:
>> I was looking at slabinfo and noticed something about uci. Executing
>> "uci commit" increases amount of "dentry" active objects.
>>
>> # echo 2 > /proc/sys/vm/drop_caches
>>
>> # egrep "dentry|kmalloc-64"
Hi,
short summary for the impatient readers: the following text dives into the
subtile differences between errexit (set -e) and exit status in shell scripting
Am Mon, 11 Jan 2016 05:14:18 -0500
schrieb Daniel Dickinson :
> I did one other test I hadn't thought of
On 11/01/2016 15:15, Martin Blumenstingl wrote:
> On Mon, Jan 11, 2016 at 2:59 PM, John Crispin wrote:
>> 0x1F40-0x1F400FFF means that its size is 0x1000. i think you having
>> a off-by-one thinko ...
> ...and I think you are right!
> Sorry for the noise, please drop
Felix,
Would it be unreasonable to have overridable defaults like suggested in
metadata.pl? Convention over configuration and all that.
Eric
On Mon, Jan 11, 2016 at 7:35 AM, Felix Fietkau wrote:
> On 2016-01-11 06:16, open...@daniel.thecshore.com wrote:
> > From: Daniel
On 11/01/16 08:35 AM, Felix Fietkau wrote:
Signed-off-by: Daniel Dickinson
---
scripts/metadata.pl | 32 +---
1 file changed, 29 insertions(+), 3 deletions(-)
diff --git a/scripts/metadata.pl b/scripts/metadata.pl
index
47 matches
Mail list logo