Re: [LEDE-DEV] [PATCH v3] ramips: build factory images for Buffalo WSR-1166DHP/WSR-1166DHP2

2016-12-11 Thread John Crispin 


On 11/12/2016 14:53, Mathias Kresin wrote:
> First of all, sorry for beeing late to the party and requesting changes
> to a V3.
> 
> 11.12.2016 02:17, FUKAUMI Naoki:
>> diff --git a/target/linux/ramips/image/mt7621.mk
>> b/target/linux/ramips/image/mt7621.mk
>> index 6d85511..23a79f5 100644
>> --- a/target/linux/ramips/image/mt7621.mk
>> +++ b/target/linux/ramips/image/mt7621.mk
>> @@ -192,8 +192,41 @@ define Device/wndr3700v5
>>  endef
>>  TARGET_DEVICES += wndr3700v5
>>
>> +define Build/wsr-factory-image
>> +$(STAGING_DIR_HOST)/bin/trx \
>> +-M $(2) \
>> +-m $(IMAGE_SIZE) \
>> +-f $(1) \
>> +-o $(1).trx
>> +$(STAGING_DIR_HOST)/bin/buffalo-enc \
>> +-l -m 'start' \
>> +-p $(3) -v '0.00' \
>> +-i $(1).trx -o $(1).trx.enc
>> +$(STAGING_DIR_HOST)/bin/buffalo-tag \
>> +-a MTK \
>> +-b $(3) -p $(3) \
>> +-l JP -r JP -r JP \
>> +-s \
>> +-v '0.00' -m '0.00' \
>> +-w 1 \
>> +-I $(1).trx.enc -o $(1).tag
>> +$(STAGING_DIR_HOST)/bin/buffalo-enc \
>> +-l -m 'start' \
>> +-p '' -v '' \
>> +-i $(1).tag -o $(1).tag.enc
>> +$(STAGING_DIR_HOST)/bin/mkdhpimg \
>> +$(1).tag.enc $(1).trx.enc \
>> +$(call imgname,initramfs,$(4))-factory.bin
>> +endef
>> +
>> +define Build/wsr-1166-factory-images
>> +$(call
>> Build/wsr-factory-image,$@,0x746f435c,WSR-1166DHP,wsr-1166dhp)
>> +$(call
>> Build/wsr-factory-image,$@,0x1fc384dd,WSR-1166DHP2,wsr-1166dhp2)
>> +endef
> 
> This looks like the old image build code we just got rid of. Would you
> please add multiple factory images to "Device/wsr-1166" instead.
> 
> Have a look at the DGN3500 image build code in the lantiq target for an
> example.
> 

i missed that, was too excited about the feature :)

this should be converted to the new style image code. i hvae dropped v3
from my tree.

John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.

2016-12-11 Thread Petr Štetiar 
Matti Laakso  [2016-12-09 11:35:35]:

> On 09.12.2016 11:27, Petr Štetiar wrote:
>> I knew, that there's only one profile defined, operator has deleted all other
>> profiles, there's currently only one APN defined.
>>
>>   AT+CGDCONT?
>>   +CGDCONT: 1,"IPV4V6","","0.0.0.0",0,0
>
> Well, there's no APN defined (it's an empty string), and who knows,  
> maybe the modem ignores the APN provided via QMI when enabling  
> autoconnect... Does your working Czech SIM card have a valid APN string?

It's getting quite strange as my Czech SIM gives me the same reply:

  +CGDCONT: 1,"IPV4V6","","0.0.0.0",0,0

-- ynezz

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH 1/2] lantiq: specify console using stdout-path instead of cmdline argument

2016-12-11 Thread Martin Blumenstingl 
Use devicetree's /chosen/stdout-path instead of the kernel command line
(embedded in the .dts-files) to specify the serial console. Using the
chosen node is recommended on devicetree based platforms.

Signed-off-by: Martin Blumenstingl 
---
 target/linux/lantiq/dts/ACMP252.dts   |  2 +-
 target/linux/lantiq/dts/ARV4510PW.dts |  2 +-
 target/linux/lantiq/dts/ARV4518PWR01.dtsi |  2 +-
 target/linux/lantiq/dts/ARV4519PW.dts |  2 +-
 target/linux/lantiq/dts/ARV4520PW.dts |  2 +-
 target/linux/lantiq/dts/ARV452CQW.dts |  2 +-
 target/linux/lantiq/dts/ARV7510PW22.dts   |  2 +-
 target/linux/lantiq/dts/ARV7518PW.dts |  2 +-
 target/linux/lantiq/dts/ARV7519PW.dts |  2 +-
 target/linux/lantiq/dts/ARV7519RW22.dts   |  2 +-
 target/linux/lantiq/dts/ARV7525PW.dts |  2 +-
 target/linux/lantiq/dts/ARV752DPW.dts |  2 +-
 target/linux/lantiq/dts/ARV752DPW22.dts   |  2 +-
 target/linux/lantiq/dts/BTHOMEHUBV2B.dts  |  2 +-
 target/linux/lantiq/dts/BTHOMEHUBV3A.dts  |  2 +-
 target/linux/lantiq/dts/BTHOMEHUBV5A.dts  |  2 +-
 target/linux/lantiq/dts/DGN1000B.dts  |  2 +-
 target/linux/lantiq/dts/DGN3500.dtsi  |  2 +-
 target/linux/lantiq/dts/EASY50712.dts |  2 +-
 target/linux/lantiq/dts/EASY50810.dts |  2 +-
 target/linux/lantiq/dts/EASY80920.dtsi|  2 +-
 target/linux/lantiq/dts/FRITZ3370.dts |  2 +-
 target/linux/lantiq/dts/FRITZ7320.dts |  2 +-
 target/linux/lantiq/dts/FRITZ7360SL.dts   |  2 +-
 target/linux/lantiq/dts/GIGASX76X.dts |  2 +-
 target/linux/lantiq/dts/H201L.dts |  2 +-
 target/linux/lantiq/dts/P2601HNFX.dts |  2 +-
 target/linux/lantiq/dts/P2812HNUFX.dtsi   |  2 +-
 target/linux/lantiq/dts/TDW89X0.dtsi  |  2 +-
 target/linux/lantiq/dts/VG3503J.dts   |  2 +-
 target/linux/lantiq/dts/VGV7510KW22.dtsi  |  2 +-
 target/linux/lantiq/dts/VGV7519.dtsi  |  2 +-
 target/linux/lantiq/dts/VR200v.dts|  2 +-
 target/linux/lantiq/dts/WBMR.dts  |  2 +-
 target/linux/lantiq/dts/WBMR300.dts   |  2 +-
 target/linux/lantiq/dts/amazonse.dtsi | 10 +-
 target/linux/lantiq/dts/ar9.dtsi  |  8 
 target/linux/lantiq/dts/danube.dtsi   |  7 ++-
 target/linux/lantiq/dts/falcon.dtsi   |  4 
 target/linux/lantiq/dts/vr9.dtsi  |  8 
 40 files changed, 70 insertions(+), 37 deletions(-)

diff --git a/target/linux/lantiq/dts/ACMP252.dts 
b/target/linux/lantiq/dts/ACMP252.dts
index 3961bf4..cb1ec75 100644
--- a/target/linux/lantiq/dts/ACMP252.dts
+++ b/target/linux/lantiq/dts/ACMP252.dts
@@ -6,7 +6,7 @@
model = "ACMP252 - AudioCodes MediaPack MP-252";
 
chosen {
-   bootargs = "console=ttyLTQ0,115200 init=/etc/preinit";
+   bootargs = "init=/etc/preinit";
};
 
memory@0 {
diff --git a/target/linux/lantiq/dts/ARV4510PW.dts 
b/target/linux/lantiq/dts/ARV4510PW.dts
index c34ffe8..3f10d66 100644
--- a/target/linux/lantiq/dts/ARV4510PW.dts
+++ b/target/linux/lantiq/dts/ARV4510PW.dts
@@ -8,7 +8,7 @@
model = "ARV4510PW - Wippies, Elisa";
 
chosen {
-   bootargs = "console=ttyLTQ0,115200 init=/etc/preinit";
+   bootargs = "init=/etc/preinit";
};
 
aliases {
diff --git a/target/linux/lantiq/dts/ARV4518PWR01.dtsi 
b/target/linux/lantiq/dts/ARV4518PWR01.dtsi
index 84c3c4a..6e92bf3 100644
--- a/target/linux/lantiq/dts/ARV4518PWR01.dtsi
+++ b/target/linux/lantiq/dts/ARV4518PWR01.dtsi
@@ -4,7 +4,7 @@
 
 / {
chosen {
-   bootargs = "console=ttyLTQ0,115200 init=/etc/preinit";
+   bootargs = "init=/etc/preinit";
};
 
aliases {
diff --git a/target/linux/lantiq/dts/ARV4519PW.dts 
b/target/linux/lantiq/dts/ARV4519PW.dts
index 77d466d..77a3f32 100644
--- a/target/linux/lantiq/dts/ARV4519PW.dts
+++ b/target/linux/lantiq/dts/ARV4519PW.dts
@@ -8,7 +8,7 @@
model = "ARV4519PW - Vodafone Netfaster IAD 2, Pirelli P.RG A4201G";
 
chosen {
-   bootargs = "console=ttyLTQ0,115200 init=/etc/preinit";
+   bootargs = "init=/etc/preinit";
};
 
aliases {
diff --git a/target/linux/lantiq/dts/ARV4520PW.dts 
b/target/linux/lantiq/dts/ARV4520PW.dts
index 0466968..4fa8082 100644
--- a/target/linux/lantiq/dts/ARV4520PW.dts
+++ b/target/linux/lantiq/dts/ARV4520PW.dts
@@ -8,7 +8,7 @@
model = "ARV4520PW - Easybox 800, WAV-281";
 
chosen {
-   bootargs = "console=ttyLTQ0,115200 init=/etc/preinit";
+   bootargs = "init=/etc/preinit";
};
 
aliases {
diff --git a/target/linux/lantiq/dts/ARV452CQW.dts 
b/target/linux/lantiq/dts/ARV452CQW.dts
index 21c5604..f2b8457 100644
--- a/target/linux/lantiq/dts/ARV452CQW.dts
+++ b/target/linux/lantiq/dts/ARV452CQW.dts
@@ -8,7 +8,7 @@
model = "ARV452CQW - Arcor 801";
 
chosen {
-   bootargs = "console=ttyLTQ0,115200 init=/etc/preinit";
+   bootargs = "init=/etc/preinit";
};

[LEDE-DEV] [PATCH 2/2] lantiq: remove "init" kernel command line parameter from bootargs

2016-12-11 Thread Martin Blumenstingl 
/etc/preinit has been the default init-script for a very long time (at
least since Linux 2.6.30 in OpenWrt). Remove the kernel command line
"init" parameter to get rid of duplicate and inconsistent definitions
of this parameter (some boards, like FRITZ3370 for example did not use
it at all, while it's just copy and paste on others).

Signed-off-by: Martin Blumenstingl 
---
 target/linux/lantiq/dts/ACMP252.dts   | 4 
 target/linux/lantiq/dts/ARV4510PW.dts | 4 
 target/linux/lantiq/dts/ARV4518PWR01.dtsi | 4 
 target/linux/lantiq/dts/ARV4519PW.dts | 4 
 target/linux/lantiq/dts/ARV4520PW.dts | 4 
 target/linux/lantiq/dts/ARV452CQW.dts | 4 
 target/linux/lantiq/dts/ARV7510PW22.dts   | 4 
 target/linux/lantiq/dts/ARV7518PW.dts | 4 
 target/linux/lantiq/dts/ARV7519PW.dts | 4 
 target/linux/lantiq/dts/ARV7519RW22.dts   | 4 
 target/linux/lantiq/dts/ARV7525PW.dts | 4 
 target/linux/lantiq/dts/ARV752DPW.dts | 4 
 target/linux/lantiq/dts/ARV752DPW22.dts   | 4 
 target/linux/lantiq/dts/BTHOMEHUBV2B.dts  | 4 
 target/linux/lantiq/dts/BTHOMEHUBV3A.dts  | 4 
 target/linux/lantiq/dts/BTHOMEHUBV5A.dts  | 4 
 target/linux/lantiq/dts/DGN1000B.dts  | 2 --
 target/linux/lantiq/dts/EASY50712.dts | 4 
 target/linux/lantiq/dts/EASY50810.dts | 4 
 target/linux/lantiq/dts/EASY80920.dtsi| 4 
 target/linux/lantiq/dts/FRITZ7320.dts | 4 
 target/linux/lantiq/dts/FRITZ7360SL.dts   | 4 
 target/linux/lantiq/dts/GIGASX76X.dts | 4 
 target/linux/lantiq/dts/H201L.dts | 4 
 target/linux/lantiq/dts/P2601HNFX.dts | 4 
 target/linux/lantiq/dts/P2812HNUFX.dtsi   | 4 
 target/linux/lantiq/dts/TDW89X0.dtsi  | 4 
 target/linux/lantiq/dts/VG3503J.dts   | 4 
 target/linux/lantiq/dts/VGV7510KW22.dtsi  | 2 +-
 target/linux/lantiq/dts/VGV7519.dtsi  | 2 +-
 target/linux/lantiq/dts/VR200v.dts| 4 
 target/linux/lantiq/dts/WBMR.dts  | 4 
 target/linux/lantiq/dts/WBMR300.dts   | 4 
 target/linux/lantiq/dts/danube.dtsi   | 1 -
 34 files changed, 2 insertions(+), 125 deletions(-)

diff --git a/target/linux/lantiq/dts/ACMP252.dts 
b/target/linux/lantiq/dts/ACMP252.dts
index cb1ec75..50c011a 100644
--- a/target/linux/lantiq/dts/ACMP252.dts
+++ b/target/linux/lantiq/dts/ACMP252.dts
@@ -5,10 +5,6 @@
 / {
model = "ACMP252 - AudioCodes MediaPack MP-252";
 
-   chosen {
-   bootargs = "init=/etc/preinit";
-   };
-
memory@0 {
reg = <0x0 0x400>;
};
diff --git a/target/linux/lantiq/dts/ARV4510PW.dts 
b/target/linux/lantiq/dts/ARV4510PW.dts
index 3f10d66..5850767 100644
--- a/target/linux/lantiq/dts/ARV4510PW.dts
+++ b/target/linux/lantiq/dts/ARV4510PW.dts
@@ -7,10 +7,6 @@
 / {
model = "ARV4510PW - Wippies, Elisa";
 
-   chosen {
-   bootargs = "init=/etc/preinit";
-   };
-
aliases {
led-boot = &power;
led-failsafe = &power2;
diff --git a/target/linux/lantiq/dts/ARV4518PWR01.dtsi 
b/target/linux/lantiq/dts/ARV4518PWR01.dtsi
index 6e92bf3..c527147 100644
--- a/target/linux/lantiq/dts/ARV4518PWR01.dtsi
+++ b/target/linux/lantiq/dts/ARV4518PWR01.dtsi
@@ -3,10 +3,6 @@
 #include 
 
 / {
-   chosen {
-   bootargs = "init=/etc/preinit";
-   };
-
aliases {
led-boot = &power;
led-failsafe = &power;
diff --git a/target/linux/lantiq/dts/ARV4519PW.dts 
b/target/linux/lantiq/dts/ARV4519PW.dts
index 77a3f32..fe0f9a7 100644
--- a/target/linux/lantiq/dts/ARV4519PW.dts
+++ b/target/linux/lantiq/dts/ARV4519PW.dts
@@ -7,10 +7,6 @@
 / {
model = "ARV4519PW - Vodafone Netfaster IAD 2, Pirelli P.RG A4201G";
 
-   chosen {
-   bootargs = "init=/etc/preinit";
-   };
-
aliases {
led-boot = &power_green;
led-failsafe = &power_red;
diff --git a/target/linux/lantiq/dts/ARV4520PW.dts 
b/target/linux/lantiq/dts/ARV4520PW.dts
index 4fa8082..2ad3a8a 100644
--- a/target/linux/lantiq/dts/ARV4520PW.dts
+++ b/target/linux/lantiq/dts/ARV4520PW.dts
@@ -7,10 +7,6 @@
 / {
model = "ARV4520PW - Easybox 800, WAV-281";
 
-   chosen {
-   bootargs = "init=/etc/preinit";
-   };
-
aliases {
led-boot = &power_blue;
led-failsafe = &power_red;
diff --git a/target/linux/lantiq/dts/ARV452CQW.dts 
b/target/linux/lantiq/dts/ARV452CQW.dts
index f2b8457..8d47b3b 100644
--- a/target/linux/lantiq/dts/ARV452CQW.dts
+++ b/target/linux/lantiq/dts/ARV452CQW.dts
@@ -7,10 +7,6 @@
 / {
model = "ARV452CQW - Arcor 801";
 
-   chosen {
-   bootargs = "init=/etc/preinit";
-   };
-
aliases {
led-boot = &power_blue;
led-failsafe = &power_red;
diff --git a/target/linux/lantiq/dts/ARV7510PW22.dts 
b/target/linux/lantiq/dts/ARV7510P

[LEDE-DEV] [PATCH 0/2] lantiq: get rid of /chosen/bootargs where possible

2016-12-11 Thread Martin Blumenstingl 
This series removes the bootargs from all devicetree files where
possible. There are two parameters which are converted to standard
devicetree properties:
- the console parameter is now provided by using /chosen/stdout-path
  along with an /aliases/serialN node
- the init kernel parameter is removed completely since it's the
  default in LEDE and no other target provides it

There are only 5 occurrences of bootargs left:
- VGV7510KW22 and VGV7519 use it to provide the VPE (required for vmmc)
  memory -> mid-term this should probably be replaced by reserved
  memory nodes: [0]
- FRITZ3370 needs investigating if we can rename the partition to "ubi"
  (depends on whether there's a rootfs UBI volume inside or not)
- EASY80920NAND needs investigation similar to FRITZ3370
- DGN3500 passes only "root=" - if this is bogus then it should be
  removed with a followup


[0] 
https://www.kernel.org/doc/Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt

Martin Blumenstingl (2):
  lantiq: specify console using stdout-path instead of cmdline argument
  lantiq: remove "init" kernel command line parameter from bootargs

 target/linux/lantiq/dts/ACMP252.dts   |  4 
 target/linux/lantiq/dts/ARV4510PW.dts |  4 
 target/linux/lantiq/dts/ARV4518PWR01.dtsi |  4 
 target/linux/lantiq/dts/ARV4519PW.dts |  4 
 target/linux/lantiq/dts/ARV4520PW.dts |  4 
 target/linux/lantiq/dts/ARV452CQW.dts |  4 
 target/linux/lantiq/dts/ARV7510PW22.dts   |  4 
 target/linux/lantiq/dts/ARV7518PW.dts |  4 
 target/linux/lantiq/dts/ARV7519PW.dts |  4 
 target/linux/lantiq/dts/ARV7519RW22.dts   |  4 
 target/linux/lantiq/dts/ARV7525PW.dts |  4 
 target/linux/lantiq/dts/ARV752DPW.dts |  4 
 target/linux/lantiq/dts/ARV752DPW22.dts   |  4 
 target/linux/lantiq/dts/BTHOMEHUBV2B.dts  |  4 
 target/linux/lantiq/dts/BTHOMEHUBV3A.dts  |  4 
 target/linux/lantiq/dts/BTHOMEHUBV5A.dts  |  4 
 target/linux/lantiq/dts/DGN1000B.dts  |  2 --
 target/linux/lantiq/dts/DGN3500.dtsi  |  2 +-
 target/linux/lantiq/dts/EASY50712.dts |  4 
 target/linux/lantiq/dts/EASY50810.dts |  4 
 target/linux/lantiq/dts/EASY80920.dtsi|  4 
 target/linux/lantiq/dts/FRITZ3370.dts |  2 +-
 target/linux/lantiq/dts/FRITZ7320.dts |  4 
 target/linux/lantiq/dts/FRITZ7360SL.dts   |  4 
 target/linux/lantiq/dts/GIGASX76X.dts |  4 
 target/linux/lantiq/dts/H201L.dts |  4 
 target/linux/lantiq/dts/P2601HNFX.dts |  4 
 target/linux/lantiq/dts/P2812HNUFX.dtsi   |  4 
 target/linux/lantiq/dts/TDW89X0.dtsi  |  4 
 target/linux/lantiq/dts/VG3503J.dts   |  4 
 target/linux/lantiq/dts/VGV7510KW22.dtsi  |  2 +-
 target/linux/lantiq/dts/VGV7519.dtsi  |  2 +-
 target/linux/lantiq/dts/VR200v.dts|  4 
 target/linux/lantiq/dts/WBMR.dts  |  4 
 target/linux/lantiq/dts/WBMR300.dts   |  4 
 target/linux/lantiq/dts/amazonse.dtsi | 10 +-
 target/linux/lantiq/dts/ar9.dtsi  |  8 
 target/linux/lantiq/dts/danube.dtsi   |  6 +-
 target/linux/lantiq/dts/falcon.dtsi   |  4 
 target/linux/lantiq/dts/vr9.dtsi  |  8 
 40 files changed, 38 insertions(+), 128 deletions(-)

-- 
2.10.2


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] uqmi: Add support for specifying profile index

2016-12-11 Thread Matti Laakso 
On 12/09/2016 04:35 PM, Nikolay Ledovskikh wrote:
> Tested your patch. It's working, but only after startup.
>
> When you disconnect modem from usb we have old cids saved.
> Then we connect modems back, modems won't bring up automatically
> (and I suppose they souldn't). And when we try to bring interface up we are
> falling into situation with locked up uqmi:
> 4912 root  1000 Suqmi -s -d /dev/cdc-wdm0 --set-client-id wds
> 2 --stop-network 0x --autoconnect
> 4980 root  1000 Suqmi -s -d /dev/cdc-wdm0 --get-pin-status
> 5020 root  1000 Suqmi -s -d /dev/cdc-wdm1 --set-client-id wds
> 2 --stop-network 0x --autoconnect
> 5090 root   992 Suqmi -s -d /dev/cdc-wdm1 --get-pin-status
> If we now kill all this uqmi processes, we then bring interfaces up :(
> Maybe it's all because of saved cids?
>
> Other case, when only modem's usb data lines are disconnected, without
> loosing power. This case we don't have locked up uqmi and manual 'ifup $iface'
> works. Saved cids released successfully.

Indeed, if one disconnects power from the modem, the interface somehow
stays up and the cid's stay in memory. Then when one tries to stop the
network with an unallocated cid after the modem again has power, uqmi
hangs. I think disconnecting the modem should tear down the interface as
well, but I'm not sure how to achieve that.

>
> 2016-12-09 15:02 GMT+03:00 Felix Fietkau :
>> On 2016-12-03 23:05, Matti Laakso wrote:
>>> Update uqmi to latest version, which brings about support for
>>> specifying a call profile index instead of APN. A specific index
>>> different from 1 must be used for some service provider and modem
>>> combinations.
>>>
>>> Also make autoconnect optional and default it to off due to it not
>>> working with statically configured IPv6.
>>>
>>> Signed-off-by: Matti Laakso 
>> I think autoconnect should default to on for IPv4, as long as we don't
>> have anything running on the host to replace it.
>>
>> If the autoconnect does not work with the device for some reason, you at
>> least notice it immediately (and realize you have to do some monitoring
>> of the connection).
>>
>> If autoconnect defaults to off and the device will simply stay
>> disconnected on the first network outage, that's a pretty bad default,
>> especially in cases where the device could just reconnect on its own.
>>
>> - Felix
>>
>> ___
>> 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

Re: [LEDE-DEV] [PATCH] comgt-ncm: Add support for specifying profile index

2016-12-11 Thread Matti Laakso 
On 12/11/2016 09:47 AM, John Crispin wrote:
> Hi Matti
>
> i noticed that you remove the ipv6 option/support and this is not
> mentioned in the commit message. could you elaborate on that one ?
>
>   John

Hi John,

It is mentioned in the commit message, although maybe a bit unclear. I
just sent a v2 with among other changes a slightly reworded commit
message. The point is that it is better (and common to mobile broadband
connections) to specify pdptype as ip, ipv6 or ipv4v6 rather than enable
or disable ipv6.

Matti

>
> On 06/12/2016 17:52, Matti Laakso wrote:
>> Add support for specifying a call profile index instead of APN. A
>> specific index different from 1 must be used for some service
>> provider and modem combinations.
>>
>> In addition, change the manufacturer detection to use the standard
>> AT+CGMI command, which produces more predictable output than ATI,
>> and remove the redundant ipv6 option, since it is more customary
>> to specify the PDP context type with mobile connections.
>>
>> Signed-off-by: Matti Laakso 
>> ---
>>  package/network/utils/comgt/Makefile   |  2 +-
>>  package/network/utils/comgt/files/getcardinfo.gcom |  2 +-
>>  package/network/utils/comgt/files/ncm.json | 26 -
>>  package/network/utils/comgt/files/ncm.sh   | 65 
>> ++
>>  4 files changed, 44 insertions(+), 51 deletions(-)
>>
>> diff --git a/package/network/utils/comgt/Makefile 
>> b/package/network/utils/comgt/Makefile
>> index 9d99d64..4b6e6ea 100644
>> --- a/package/network/utils/comgt/Makefile
>> +++ b/package/network/utils/comgt/Makefile
>> @@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
>>  
>>  PKG_NAME:=comgt
>>  PKG_VERSION:=0.32
>> -PKG_RELEASE:=27
>> +PKG_RELEASE:=28
>>  
>>  PKG_SOURCE:=$(PKG_NAME).$(PKG_VERSION).tgz
>>  PKG_SOURCE_URL:=@SF/comgt
>> diff --git a/package/network/utils/comgt/files/getcardinfo.gcom 
>> b/package/network/utils/comgt/files/getcardinfo.gcom
>> index 5c69a64..f91665f 100644
>> --- a/package/network/utils/comgt/files/getcardinfo.gcom
>> +++ b/package/network/utils/comgt/files/getcardinfo.gcom
>> @@ -6,7 +6,7 @@ opengt
>>   flash 0.1
>>  
>>  :start
>> - send "ATI^m"
>> + send "AT+CGMI^m"
>>   get 1 "" $s
>>   print $s
>>  
>> diff --git a/package/network/utils/comgt/files/ncm.json 
>> b/package/network/utils/comgt/files/ncm.json
>> index d1f8699..8f74e17 100644
>> --- a/package/network/utils/comgt/files/ncm.json
>> +++ b/package/network/utils/comgt/files/ncm.json
>> @@ -7,7 +7,7 @@
>>  "ATV1",
>>  "ATE1",
>>  "ATS0=0",
>> -"AT+CGDCONT=1,\\\"${pdptype}\\\",\\\"${apn}\\\""
>> +
>> "AT+CGDCONT=${profile},\\\"${pdptype}\\\"${apn:+,\\\"$apn\\\"}"
>>  ],
>>  "modes": {
>>  "preferlte": 
>> "AT^SYSCFGEX=\\\"030201\\\",3fff,2,4,7fff,,",
>> @@ -17,8 +17,8 @@
>>  "gsm": 
>> "AT^SYSCFGEX=\\\"01\\\",3fff,2,4,7fff,,",
>>  "auto": 
>> "AT^SYSCFGEX=\\\"00\\\",3fff,2,4,7fff,,"
>>  },
>> -"connect": 
>> "AT^NDISDUP=1,1,\\\"${apn}\\\"${username:+,\\\"$username\\\"}${password:+,\\\"$password\\\"}${auth:+,$auth}",
>> -"disconnect": "AT^NDISDUP=1,0"
>> +"connect": 
>> "AT^NDISDUP=${profile},1${apn:+,\\\"$apn\\\"}${username:+,\\\"$username\\\"}${password:+,\\\"$password\\\"}${auth:+,$auth}",
>> +"disconnect": "AT^NDISDUP=${profile},0"
>>  },
>>  "samsung": {
>>  "initialize": [
>> @@ -26,7 +26,7 @@
>>  "AT+CGREG=2",
>>  "AT+CFUN=5",
>>  "AT+MODESELECT=3",
>> -"AT+CGDCONT=1,\\\"${pdptype}\\\",\\\"${apn}\\\""
>> +
>> "AT+CGDCONT=${profile},\\\"${pdptype}\\\"${apn:+,\\\"$apn\\\"}"
>>  ],
>>  "modes": {
>>  "umts": "AT+CHANGEALLPATH=1"
>> @@ -34,11 +34,11 @@
>>  "connect": "AT+CGATT=1",
>>  "disconnect": "AT+CGATT=0"
>>  },
>> -"sierra wireless, incorporated": {
>> +"sierra": {
>>  "initialize": [
>>  "AT+CFUN=1",
>> -"AT+CGDCONT=1,\\\"${pdptype}\\\",\\\"${apn}\\\"",
>> -
>> "AT$QCPDPP=1${auth:+,$auth}${password:+,\\\"$password\\\"}${username:+,\\\"$username\\\"}"
>> +
>> "AT+CGDCONT=${profile},\\\"${pdptype}\\\"${apn:+,\\\"$apn\\\"}",
>> +
>> "AT$QCPDPP=${profile},${auth:-0}${password:+,\\\"$password\\\"}${username:+,\\\"$username\\\"}"
>>  ],
>>  "modes": {
>>  "preferlte": "AT!SELRAT=07",
>> @@ -48,20 +48,20 @@
>>  "gsm": "AT!SELRAT=02",
>>  "auto": "AT!SELRAT=00"
>>  },
>> -"connect": "AT!SCACT=1,1",
>> -"disconnect": "AT!SCACT=0,1"
>> +

[LEDE-DEV] [PATCH v2] comgt-ncm: Add support for specifying profile index

2016-12-11 Thread Matti Laakso 
Add support for specifying a call profile index instead of APN. A
specific index different from 1 must be used for some service
provider and modem combinations.

In addition, change the manufacturer detection to use the standard
AT+CGMI command, which produces more predictable output than ATI,
remove the redundant ipv6 option, since it is less ambiguous to
directly specify the PDP context type with mobile connections, and
fix missing device during teardown when using ncm through the wwan
proto.

Signed-off-by: Matti Laakso 
---

v2:
* Ignore echoed AT+CGMI
* Workaround +CGMI: prefix from some modems
* Fix missing device in teardown with wwan proto
* Store manufacturer string so it is not queried again during teardown

 package/network/utils/comgt/Makefile   |  2 +-
 package/network/utils/comgt/files/getcardinfo.gcom |  2 +-
 package/network/utils/comgt/files/ncm.json | 26 
 package/network/utils/comgt/files/ncm.sh   | 77 ++
 4 files changed, 51 insertions(+), 56 deletions(-)

diff --git a/package/network/utils/comgt/Makefile 
b/package/network/utils/comgt/Makefile
index 9d99d64..4b6e6ea 100644
--- a/package/network/utils/comgt/Makefile
+++ b/package/network/utils/comgt/Makefile
@@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
 
 PKG_NAME:=comgt
 PKG_VERSION:=0.32
-PKG_RELEASE:=27
+PKG_RELEASE:=28
 
 PKG_SOURCE:=$(PKG_NAME).$(PKG_VERSION).tgz
 PKG_SOURCE_URL:=@SF/comgt
diff --git a/package/network/utils/comgt/files/getcardinfo.gcom 
b/package/network/utils/comgt/files/getcardinfo.gcom
index 5c69a64..f91665f 100644
--- a/package/network/utils/comgt/files/getcardinfo.gcom
+++ b/package/network/utils/comgt/files/getcardinfo.gcom
@@ -6,7 +6,7 @@ opengt
  flash 0.1
 
 :start
- send "ATI^m"
+ send "AT+CGMI^m"
  get 1 "" $s
  print $s
 
diff --git a/package/network/utils/comgt/files/ncm.json 
b/package/network/utils/comgt/files/ncm.json
index d1f8699..8f74e17 100644
--- a/package/network/utils/comgt/files/ncm.json
+++ b/package/network/utils/comgt/files/ncm.json
@@ -7,7 +7,7 @@
"ATV1",
"ATE1",
"ATS0=0",
-   "AT+CGDCONT=1,\\\"${pdptype}\\\",\\\"${apn}\\\""
+   
"AT+CGDCONT=${profile},\\\"${pdptype}\\\"${apn:+,\\\"$apn\\\"}"
],
"modes": {
"preferlte": 
"AT^SYSCFGEX=\\\"030201\\\",3fff,2,4,7fff,,",
@@ -17,8 +17,8 @@
"gsm": 
"AT^SYSCFGEX=\\\"01\\\",3fff,2,4,7fff,,",
"auto": 
"AT^SYSCFGEX=\\\"00\\\",3fff,2,4,7fff,,"
},
-   "connect": 
"AT^NDISDUP=1,1,\\\"${apn}\\\"${username:+,\\\"$username\\\"}${password:+,\\\"$password\\\"}${auth:+,$auth}",
-   "disconnect": "AT^NDISDUP=1,0"
+   "connect": 
"AT^NDISDUP=${profile},1${apn:+,\\\"$apn\\\"}${username:+,\\\"$username\\\"}${password:+,\\\"$password\\\"}${auth:+,$auth}",
+   "disconnect": "AT^NDISDUP=${profile},0"
},
"samsung": {
"initialize": [
@@ -26,7 +26,7 @@
"AT+CGREG=2",
"AT+CFUN=5",
"AT+MODESELECT=3",
-   "AT+CGDCONT=1,\\\"${pdptype}\\\",\\\"${apn}\\\""
+   
"AT+CGDCONT=${profile},\\\"${pdptype}\\\"${apn:+,\\\"$apn\\\"}"
],
"modes": {
"umts": "AT+CHANGEALLPATH=1"
@@ -34,11 +34,11 @@
"connect": "AT+CGATT=1",
"disconnect": "AT+CGATT=0"
},
-   "sierra wireless, incorporated": {
+   "sierra": {
"initialize": [
"AT+CFUN=1",
-   "AT+CGDCONT=1,\\\"${pdptype}\\\",\\\"${apn}\\\"",
-   
"AT$QCPDPP=1${auth:+,$auth}${password:+,\\\"$password\\\"}${username:+,\\\"$username\\\"}"
+   
"AT+CGDCONT=${profile},\\\"${pdptype}\\\"${apn:+,\\\"$apn\\\"}",
+   
"AT$QCPDPP=${profile},${auth:-0}${password:+,\\\"$password\\\"}${username:+,\\\"$username\\\"}"
],
"modes": {
"preferlte": "AT!SELRAT=07",
@@ -48,20 +48,20 @@
"gsm": "AT!SELRAT=02",
"auto": "AT!SELRAT=00"
},
-   "connect": "AT!SCACT=1,1",
-   "disconnect": "AT!SCACT=0,1"
+   "connect": "AT!SCACT=1,${profile}",
+   "disconnect": "AT!SCACT=0,${profile}"
},
-   "sony ericsson": {
+   "sony": {
"initialize": [
"AT+CFUN=1",
-   "AT+CGDCONT=1,\\\"${pdptype}\\\",\\\"${apn}\\\"",
-   
"AT*EIAAUW=1,1,\\\"${username}\\\",\\\"${password}\\\",${auth:-00111}"
+   
"AT+CGDCONT=${profile},\\\"${pdptype}\\\"${apn:+,\\\"$apn\\\"}",
+

[LEDE-DEV] [PATCH v2] uqmi: Add support for specifying profile index

2016-12-11 Thread Matti Laakso 
Update uqmi to latest version, which brings about support for
specifying a call profile index instead of APN. A specific index
different from 1 must be used for some service provider and modem
combinations.

Also change option dhcp to dhcpv6, since IPv4 now always uses DHCP,
replace option ipv6 with pdptype, which is less ambiguous, and
make autoconnect optional and default it to off for IPv6 due to it
not working with statically configured IPv6.

Signed-off-by: Matti Laakso 
---

v2:
* Enable autoconnect by default for IPv4

 package/network/utils/uqmi/Makefile|   6 +-
 .../utils/uqmi/files/lib/netifd/proto/qmi.sh   | 169 +++--
 2 files changed, 93 insertions(+), 82 deletions(-)

diff --git a/package/network/utils/uqmi/Makefile 
b/package/network/utils/uqmi/Makefile
index 06d9ac2..2b832d4 100644
--- a/package/network/utils/uqmi/Makefile
+++ b/package/network/utils/uqmi/Makefile
@@ -1,15 +1,15 @@
 include $(TOPDIR)/rules.mk
 
 PKG_NAME:=uqmi
-PKG_VERSION:=2016-08-23
+PKG_VERSION:=2016-11-22
 PKG_RELEASE=$(PKG_SOURCE_VERSION)
 
 PKG_SOURCE_PROTO:=git
 PKG_SOURCE_URL=$(LEDE_GIT)/project/uqmi.git
 PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION)
-PKG_SOURCE_VERSION:=eb1dec7d0dc283a7f61aa574a443a0ab61f8793f
+PKG_SOURCE_VERSION:=d682e966615fc652da6e4e26b57aa3adfebeb2fe
 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION)-$(PKG_SOURCE_VERSION).tar.xz
-PKG_MIRROR_MD5SUM:=e6273e6aee6fce419e13f84439c240d48c32020fce7f07b2dc123ae32742382c
+PKG_MIRROR_MD5SUM:=a82c4682d07870d1bdf63e475afe1c1fffabf0954a49e0e67058dae0d4f6f71c
 PKG_MAINTAINER:=Matti Laakso 
 
 PKG_LICENSE:=GPL-2.0
diff --git a/package/network/utils/uqmi/files/lib/netifd/proto/qmi.sh 
b/package/network/utils/uqmi/files/lib/netifd/proto/qmi.sh
index 1235698..05b9242 100755
--- a/package/network/utils/uqmi/files/lib/netifd/proto/qmi.sh
+++ b/package/network/utils/uqmi/files/lib/netifd/proto/qmi.sh
@@ -15,24 +15,22 @@ proto_qmi_init_config() {
proto_config_add_string username
proto_config_add_string password
proto_config_add_string pincode
-   proto_config_add_string delay
+   proto_config_add_int delay
proto_config_add_string modes
-   proto_config_add_boolean ipv6
-   proto_config_add_boolean dhcp
+   proto_config_add_string pdptype
+   proto_config_add_int profile
+   proto_config_add_boolean dhcpv6
+   proto_config_add_boolean autoconnect
proto_config_add_defaults
 }
 
 proto_qmi_setup() {
local interface="$1"
 
-   local device apn auth username password pincode delay modes ipv6 dhcp 
$PROTO_DEFAULT_OPTIONS
-   local cid_4 pdh_4 cid_6 pdh_6 ipv4
-   local ip subnet gateway dns1 dns2 ip_6 ip_prefix_length gateway_6 
dns1_6 dns2_6
-   json_get_vars device apn auth username password pincode delay modes 
ipv6 dhcp $PROTO_DEFAULT_OPTIONS
-
-   ipv4=1
-
-   [ "$ipv6" = 1 ] || ipv6=""
+   local device apn auth username password pincode delay modes pdptype 
profile dhcpv6 autoconnect $PROTO_DEFAULT_OPTIONS
+   local cid_4 pdh_4 cid_6 pdh_6
+   local ip_6 ip_prefix_length gateway_6 dns1_6 dns2_6
+   json_get_vars device apn auth username password pincode delay modes 
pdptype profile dhcpv6 autoconnect $PROTO_DEFAULT_OPTIONS
 
[ "$metric" = "" ] && metric="0"
 
@@ -76,18 +74,6 @@ proto_qmi_setup() {
}
}
 
-   [ -n "$apn" ] || {
-   echo "No APN specified"
-   proto_notify_error "$interface" NO_APN
-   return 1
-   }
-
-   # try to clear previous autoconnect state
-   # do not reuse previous wds client id to prevent hangs caused by stale 
data
-   uqmi -s -d "$device" \
-   --stop-network 0x \
-   --autoconnect > /dev/null
-
uqmi -s -d "$device" --set-data-format 802.3
uqmi -s -d "$device" --wda-set-data-format 802.3
 
@@ -98,68 +84,96 @@ proto_qmi_setup() {
 
[ -n "$modes" ] && uqmi -s -d "$device" --set-network-modes "$modes"
 
-   echo "Starting network $apn"
+   echo "Starting network $interface"
 
-   cid_4=`uqmi -s -d "$device" --get-client-id wds`
-   [ $? -ne 0 ] && {
-   echo "Unable to obtain client ID"
-   proto_notify_error "$interface" NO_CID
-   return 1
-   }
+   pdptype=`echo "$pdptype" | awk '{print tolower($0)}'`
+   [ "$pdptype" = "ip" -o "$pdptype" = "ipv6" -o "$pdptype" = "ipv4v6" ] 
|| pdptype="ip"
+
+   if [ "$pdptype" = "ip" ]; then
+   [ -z "$autoconnect" ] && autoconnect=1
+   [ "$autoconnect" = 0 ] && autoconnect=""
+   else
+   [ "$autoconnect" = 1 ] || autoconnect=""
+   fi
+
+   [ "$pdptype" = "ip" -o "$pdptype" = "ipv4v6" ] && {
+   cid_4=`uqmi -s -d "$device" --get-client-id wds`
+   [ $? -ne 0 ] && {
+   echo "Unable to obtain client ID"
+   proto_notify_error "$interface" NO_C

Re: [LEDE-DEV] [PATCH v5 2/3] ipq806x: Add support for new device: tew827dru

2016-12-11 Thread Mathias Kresin 

05.12.2016 03:43, J Mo:

On 12/01/2016 11:18 PM, Mathias Kresin wrote:

02.12.2016 06:28, J Mo:

On 11/27/2016 02:29 AM, Mathias Kresin wrote:
Can you please clarify what of my previous reply it is that you don't
understand so that I can do a better job of explaining it?


The problem is quite simple, I don't get how the signature created by
Build/cameo-sig should look like. And the way the signature is created
looks way to complex to me.

Mentioning that it's a cameo signature does not help at all, as long
as you don't provide a link to some kind of specification how this
signature format should look like.

I expect to see a human readable explantation of what the code should
do. Hence I asked you back in the days:

> Do you want to add the signature to a 64 byte padded image or should
> the image + signature padded to a multiple of 64byte? Where does the
> 64 byte does come from? It doesn't seam to be related to the 128k
> blocksize of the flash

With the new image build code, we have a lot of helper for doing
padding without the need of a single line of custom code. But as long
as I don't understand how the resulting signature should look
like/should be padded, I can not point you to the correct helper for
the job.


My requirements are the same as the Image/Build/Cameo target in
target/linux/ar71xx/image/legacy.mk.

There are two devices in particular which require a similar signature
method: TEW-632BRP (CameoAP81) and TEW-823DRU (CameoAP135). Both are
already in LEDE.

The TEW-632BRP (CameoAP81) is an ancient device from 2004. I just
happened to have two of them, so I was vaguely familiar with this
requirement before I acquired my new device.

The TEW-823DRU (CameoAP135) is both very recent and architecturally
similar to the tew827dru. It's also based on the same upstream source
(QSDK).

The makefile portion that I wrote was intended to duplicate the same
image generation functionality so that it would be useful for future
devices. I looked at existing tools prior to making my own and didn't
find anything that would do what I needed.

The image needs to be byte-aligned with the signature inside. The 64 was
backwards compatible with the old default from the old makefiles, but it
works for this device too. The actual blocksize is not relevant to my
device because of it being a FIT image.


Still not the answer I expected, but I got it.

target/linux/ar71xx/image/legacy.mk is for boards using the old image 
build code (as indicated by the term legacy).


Board support patches creating images the old way or duplicating any 
legacy stuff will not be accepted any more.


Please find a way to do the padding using the pad* helpers in 
include/image-commands.mk. If patches still using the old image build 
code were accepted in the past, it was a mistake.



You are aware that tools/firmware-utils has a mkcameofw? Not sure if
it's the same format you need.


Not applicable here and I'm not sure why you would bring it up.


Well that one is obvious to me. You are talking about an cameo signature 
and I found a tool that creates a cameo firmware. But I even wrote that 
I'm not sure if mkcameofw is related to the cameo signature or used for 
something different.


Mathias

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH v3] ramips: build factory images for Buffalo WSR-1166DHP/WSR-1166DHP2

2016-12-11 Thread Mathias Kresin 
First of all, sorry for beeing late to the party and requesting changes 
to a V3.


11.12.2016 02:17, FUKAUMI Naoki:

diff --git a/target/linux/ramips/image/mt7621.mk 
b/target/linux/ramips/image/mt7621.mk
index 6d85511..23a79f5 100644
--- a/target/linux/ramips/image/mt7621.mk
+++ b/target/linux/ramips/image/mt7621.mk
@@ -192,8 +192,41 @@ define Device/wndr3700v5
 endef
 TARGET_DEVICES += wndr3700v5

+define Build/wsr-factory-image
+   $(STAGING_DIR_HOST)/bin/trx \
+   -M $(2) \
+   -m $(IMAGE_SIZE) \
+   -f $(1) \
+   -o $(1).trx
+   $(STAGING_DIR_HOST)/bin/buffalo-enc \
+   -l -m 'start' \
+   -p $(3) -v '0.00' \
+   -i $(1).trx -o $(1).trx.enc
+   $(STAGING_DIR_HOST)/bin/buffalo-tag \
+   -a MTK \
+   -b $(3) -p $(3) \
+   -l JP -r JP -r JP \
+   -s \
+   -v '0.00' -m '0.00' \
+   -w 1 \
+   -I $(1).trx.enc -o $(1).tag
+   $(STAGING_DIR_HOST)/bin/buffalo-enc \
+   -l -m 'start' \
+   -p '' -v '' \
+   -i $(1).tag -o $(1).tag.enc
+   $(STAGING_DIR_HOST)/bin/mkdhpimg \
+   $(1).tag.enc $(1).trx.enc \
+   $(call imgname,initramfs,$(4))-factory.bin
+endef
+
+define Build/wsr-1166-factory-images
+   $(call Build/wsr-factory-image,$@,0x746f435c,WSR-1166DHP,wsr-1166dhp)
+   $(call Build/wsr-factory-image,$@,0x1fc384dd,WSR-1166DHP2,wsr-1166dhp2)
+endef


This looks like the old image build code we just got rid of. Would you 
please add multiple factory images to "Device/wsr-1166" instead.


Have a look at the DGN3500 image build code in the lantiq target for an 
example.


Mathias

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH] Kernel: update kernel 4.4 to version 4.4.37

2016-12-11 Thread Stijn Segers 

Yep, I see that now... Shouldn't send stuff when I'm tired.

I sent in a new one for .36 -> .38.

Cheers

Stijn

Op za, 10 dec 2016 om 9:08 , schreef Koen Vandeputte 
:

Hi Stijn,

2 comments about this patch:
- The actual upgrade is missing (in file include/kernel-version.mk)
- .38 has been released

Regards,

Koen

On 2016-12-10 18:39, Stijn Segers wrote:
Bump to .37 for all platforms supported by 4.4. All patches 
refreshed.


Compile-tested on ar71xx, ramips/mt7621 and x86/64.

Run-tested on ar71xx and ramips/mt7621.

Signed-off-by: Stijn Segers 
---
  
...tend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch 
| 2 +-

  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch 
b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch

index 96f20a4..c58830a 100644
--- 
a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
+++ 
b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch

@@ -1,6 +1,6 @@
  --- a/drivers/pci/probe.c
  +++ b/drivers/pci/probe.c
-@@ -1938,7 +1938,8 @@ static void pcie_write_mrrs(struct pci_d
+@@ -1964,7 +1964,8 @@ static void pcie_write_mrrs(struct pci_d
   	/* In the "safe" case, do not configure the MRRS.  There appear 
to be

 * issues with setting MRRS to 0 on a number of devices.
 */



___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] Kernel: bump to 4.4.38

2016-12-11 Thread Stijn Segers 
This patch bumps 4.4 from .36 to .38 (and supersedes my incomplete patch
for .37). Compile-tested on ar71xx, ramips/mt7621 and x86/64.

Run-tested on ar71xx & ramips/mt7621.

Signed-off-by: Stijn Segers 
---
 include/kernel-version.mk  |  4 ++--
 .../patches-4.4/910-unaligned_access_hacks.patch   |  2 +-
 ...ER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch |  2 +-
 .../patches-4.4/630-packet_socket_type.patch   |  4 ++--
 .../patches-4.4/653-disable_netlink_trim.patch |  2 +-
 .../666-Add-support-for-MAP-E-FMRs-mesh-mode.patch | 22 +++---
 6 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index 0cde467..eeb8195 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -4,11 +4,11 @@ LINUX_RELEASE?=1
 
 LINUX_VERSION-3.18 = .43
 LINUX_VERSION-4.1 = .34
-LINUX_VERSION-4.4 = .36
+LINUX_VERSION-4.4 = .38
 
 LINUX_KERNEL_MD5SUM-3.18.43 = b1faeb4a2e1e70ffe061bdbb3452840a
 LINUX_KERNEL_MD5SUM-4.1.34 = fba99f0f4765ebf01033e69518740a3c
-LINUX_KERNEL_MD5SUM-4.4.36 = c23de77131c05a27e638026972ada85b
+LINUX_KERNEL_MD5SUM-4.4.38 = 
77ed9e650b65788a1f9f371ba87c2e50b5ba7624bc834ae38b036f7f592816a6
 
 ifdef KERNEL_PATCHVER
   LINUX_VERSION:=$(KERNEL_PATCHVER)$(strip $(LINUX_VERSION-$(KERNEL_PATCHVER)))
diff --git a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch 
b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
index fc006f0..21cad91 100644
--- a/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
+++ b/target/linux/ar71xx/patches-4.4/910-unaligned_access_hacks.patch
@@ -310,7 +310,7 @@
if (t->parms.flags & IP6_TNL_F_USE_ORIG_FWMARK)
 --- a/net/ipv6/ip6_tunnel.c
 +++ b/net/ipv6/ip6_tunnel.c
-@@ -1388,7 +1388,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str
+@@ -1397,7 +1397,7 @@ ip6ip6_tnl_xmit(struct sk_buff *skb, str
  
dsfield = ipv6_get_dsfield(ipv6h);
if (t->parms.flags & IP6_TNL_F_USE_ORIG_TCLASS)
diff --git 
a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
 
b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
index 96f20a4..c58830a 100644
--- 
a/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
+++ 
b/target/linux/cns3xxx/patches-4.4/130-Extend-PCIE_BUS_PEER2PEER-to-set-MRSS-128-to-fix-CNS3xxx-BM-DMA..patch
@@ -1,6 +1,6 @@
 --- a/drivers/pci/probe.c
 +++ b/drivers/pci/probe.c
-@@ -1938,7 +1938,8 @@ static void pcie_write_mrrs(struct pci_d
+@@ -1964,7 +1964,8 @@ static void pcie_write_mrrs(struct pci_d
/* In the "safe" case, do not configure the MRRS.  There appear to be
 * issues with setting MRRS to 0 on a number of devices.
 */
diff --git a/target/linux/generic/patches-4.4/630-packet_socket_type.patch 
b/target/linux/generic/patches-4.4/630-packet_socket_type.patch
index b14afdd..eb79b2d 100644
--- a/target/linux/generic/patches-4.4/630-packet_socket_type.patch
+++ b/target/linux/generic/patches-4.4/630-packet_socket_type.patch
@@ -91,7 +91,7 @@ Signed-off-by: Felix Fietkau 
  
if (sock->type == SOCK_PACKET)
po->prot_hook.func = packet_rcv_spkt;
-@@ -3707,6 +3710,16 @@ packet_setsockopt(struct socket *sock, i
+@@ -3713,6 +3716,16 @@ packet_setsockopt(struct socket *sock, i
po->xmit = val ? packet_direct_xmit : dev_queue_xmit;
return 0;
}
@@ -108,7 +108,7 @@ Signed-off-by: Felix Fietkau 
default:
return -ENOPROTOOPT;
}
-@@ -3759,6 +3772,13 @@ static int packet_getsockopt(struct sock
+@@ -3765,6 +3778,13 @@ static int packet_getsockopt(struct sock
case PACKET_VNET_HDR:
val = po->has_vnet_hdr;
break;
diff --git a/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch 
b/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
index 2f64696..073550c 100644
--- a/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
+++ b/target/linux/generic/patches-4.4/653-disable_netlink_trim.patch
@@ -1,6 +1,6 @@
 --- a/net/netlink/af_netlink.c
 +++ b/net/netlink/af_netlink.c
-@@ -1795,27 +1795,7 @@ void netlink_detachskb(struct sock *sk,
+@@ -1812,27 +1812,7 @@ void netlink_detachskb(struct sock *sk,
  
  static struct sk_buff *netlink_trim(struct sk_buff *skb, gfp_t allocation)
  {
diff --git 
a/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
 
b/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
index c4e1904..c86f4c7 100644
--- 
a/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
+++ 
b/target/linux/generic/patches-4.4/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch
@@ -296,7 +296,7 @@ Signed-off-by: Steven Barth 
  
__skb_tunnel_rx(skb, t->dev, t->net);
  
-@@ -1226,6

[LEDE-DEV] [PATCH] bcm53xx: disable CONFIG_FW_LOADER_USER_HELPER_FALLBACK

2016-12-11 Thread Rafał Miłecki 
From: Rafał Miłecki 

There are many targets using user space scripts to generate firmware but
bcm53xx doesn't need this, so let's disable that kernel option.

This lets us avoid some scary-looking kernel warnings like:
brcmfmac 0001:04:00.0: Falling back to user helper
firmware brcm!brcmfmac43602-pcie.txt: firmware_loading_store: map pages failed

Signed-off-by: Rafał Miłecki 
---
 target/linux/bcm53xx/config-4.4 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/target/linux/bcm53xx/config-4.4 b/target/linux/bcm53xx/config-4.4
index 7c210a3..e6e6e50 100644
--- a/target/linux/bcm53xx/config-4.4
+++ b/target/linux/bcm53xx/config-4.4
@@ -124,6 +124,7 @@ CONFIG_EDAC_SUPPORT=y
 CONFIG_FIXED_PHY=y
 CONFIG_FIX_EARLYCON_MEM=y
 CONFIG_FRAME_POINTER=y
+# CONFIG_FW_LOADER_USER_HELPER_FALLBACK is not set
 CONFIG_GENERIC_ALLOCATOR=y
 CONFIG_GENERIC_BUG=y
 CONFIG_GENERIC_CLOCKEVENTS=y
-- 
2.10.1


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH rpcd 1/2] cmake: Find libubox/blobmsg_json.h

2016-12-11 Thread John Crispin 


On 11/12/2016 09:12, John Crispin wrote:
> 
> 
> On 03/12/2016 18:34, Florian Fainelli wrote:
>> Add a CMake FIND_PATH and INCLUDE_DIRECTORIES searching for blobmsg_json.h.
>> Some external toolchains which do not include standard locations would fail 
>> to
>> find the header otherwise.
>>
>> Signed-off-by: Florian Fainelli 
>> ---
>>  CMakeLists.txt | 3 +++
>>  1 file changed, 3 insertions(+)
>>
>> diff --git a/CMakeLists.txt b/CMakeLists.txt
>> index 49aa4176fbc7..ceb472e94162 100644
>> --- a/CMakeLists.txt
>> +++ b/CMakeLists.txt
>> @@ -31,6 +31,9 @@ ENDIF()
>>  FIND_PATH(ubus_include_dir libubus.h)
>>  INCLUDE_DIRECTORIES(${ubus_include_dir})
>>  
>> +FIND_PATH(ubox_include_dir libubox/blobmsg_json.h)
>> +INCLUDE_DIRECTORIES(${ubox_include_dir})
>> +
>>  ADD_EXECUTABLE(rpcd main.c exec.c session.c uci.c plugin.c)
>>  TARGET_LINK_LIBRARIES(rpcd ubox ubus uci dl blobmsg_json ${json} ${crypt})
>>  
>>
> 
> 
> Hi,
> 
> this fails to apply, could you check/resend please ? patch 2/2 applied fine
> 
>   John
> 

my fault, was still on the old git tree.

John


> ___
> 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

Re: [LEDE-DEV] [PATCH] mediatek: enable support for vfpv4 and neon

2016-12-11 Thread John Crispin 


On 25/11/2016 20:57, Christian Lamparter wrote:
> While researching for the armvirt target, I looked at the
> existing arm platforms. It turns out that the mediatek target
> with its sole MT7623N/A chip is sold as a "highly integrated
> multimedia network router system-on-chip". To that end, it
> lists support for the "NEON multimedia processing engine with
> SIMDv2 / VFPv4 ISA support".
> 
> 
> 
> So this patch enables the CPU_SUBTYPE to use this information.
> This should have the nice side effect that LEDE's phase2 builders
> no longer need to built a separate "cortex-a7" target, so this
> should free up some resources.
> 
> Cc: John Crispin 
> Signed-off-by: Christian Lamparter 

sorry took me ages to build/boot an image. merged into my staging tree
just now

John

> ---
> I don't have any MT7623, so I can't say if this works or not.
> ---
>  target/linux/mediatek/Makefile | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/target/linux/mediatek/Makefile b/target/linux/mediatek/Makefile
> index 689ba31..e3eecd5 100644
> --- a/target/linux/mediatek/Makefile
> +++ b/target/linux/mediatek/Makefile
> @@ -7,6 +7,7 @@ BOARD:=mediatek
>  BOARDNAME:=MediaTek Ralink ARM
>  FEATURES:=squashfs nand ubifs
>  CPU_TYPE:=cortex-a7
> +CPU_SUBTYPE:=neon-vfpv4
>  MAINTAINER:=John Crispin 
>  
>  KERNEL_PATCHVER:=4.4
> 

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [PATCH rpcd 1/2] cmake: Find libubox/blobmsg_json.h

2016-12-11 Thread John Crispin 


On 03/12/2016 18:34, Florian Fainelli wrote:
> Add a CMake FIND_PATH and INCLUDE_DIRECTORIES searching for blobmsg_json.h.
> Some external toolchains which do not include standard locations would fail to
> find the header otherwise.
> 
> Signed-off-by: Florian Fainelli 
> ---
>  CMakeLists.txt | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/CMakeLists.txt b/CMakeLists.txt
> index 49aa4176fbc7..ceb472e94162 100644
> --- a/CMakeLists.txt
> +++ b/CMakeLists.txt
> @@ -31,6 +31,9 @@ ENDIF()
>  FIND_PATH(ubus_include_dir libubus.h)
>  INCLUDE_DIRECTORIES(${ubus_include_dir})
>  
> +FIND_PATH(ubox_include_dir libubox/blobmsg_json.h)
> +INCLUDE_DIRECTORIES(${ubox_include_dir})
> +
>  ADD_EXECUTABLE(rpcd main.c exec.c session.c uci.c plugin.c)
>  TARGET_LINK_LIBRARIES(rpcd ubox ubus uci dl blobmsg_json ${json} ${crypt})
>  
> 


Hi,

this fails to apply, could you check/resend please ? patch 2/2 applied fine

John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev