date:20161211

[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 = 
led-failsafe = 
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 = 
led-failsafe = 
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 = _green;
led-failsafe = _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 = _blue;
led-failsafe = _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 = _blue;
led-failsafe = _red;
diff --git a/target/linux/lantiq/dts/ARV7510PW22.dts 
b/target/linux/lantiq/dts/ARV7510PW22.dts
index

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",
>> -

[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"
+

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

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

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

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

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

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

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

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

7 matches

Site Navigation

Mail list logo

Footer information