Re: [LEDE-DEV] [RFC] kernel patches cleanup

2017-08-07 Thread Philip Prindeville 

> On Aug 7, 2017, at 3:48 PM, Rafał Miłecki  wrote:
> 
> On 7 August 2017 at 21:20, Philip Prindeville
>  wrote:
>>> On Jul 31, 2017, at 10:11 AM, John Crispin  wrote:
>>> 
>>> Hi,
>>> 
>>> I rebased my ages old kernel patch cleanup series. It can be found here [1].
>>> 
>>> the series annotates all patches and splits them up into 3 folders 
>>> backports/pending/hacks.
>> 
>> 
>> What’s the criteria for each?
>> 
>> And isn’t “hacks” kind of self-defeating?  If someone submits a PR that adds 
>> something to “hacks”, won’t the default position be, “since this is 
>> admittedly a hack, it’s not really needed and you should find a more 
>> compelling fix”?
> 
> Sometimes getting upstream-acceptable solution takes months (or
> years), so I'm OK accepting well-described and argumented "hacks”.


Fair enough.

-Philip


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

Re: [LEDE-DEV] Bind not building

2017-08-07 Thread Philip Prindeville 

> On Aug 7, 2017, at 6:37 PM, Matthias Schiffer 
>  wrote:
> 
> On 08/07/2017 06:14 PM, Philip Prindeville wrote:
>> I’m seeing the following when building bind:
>> 
>> OpenWrt-libtool: link: x86_64-openwrt-linux-musl-gcc -Os -pipe 
>> -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable 
>> -Wno-error=unused-result 
>> -iremap/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.10.5-P3:bind-9.10.5-P3
>>  -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z -Wl,now -Wl,-z -Wl,relro -znow 
>> -zrelro -o .libs/resolve .libs/resolve.o  
>> -L/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/usr/lib
>>  
>> -L/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/lib
>>  
>> -L/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib
>>  
>> -L/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib 
>> ../irs/.libs/libirs.so ../dns/.libs/libdns.so ../isccfg/.libs/libisccfg.so 
>> /home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.10.5-P3/lib/dns/.libs/libdns.so
>>  
>> /home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.10.5-P3/lib/isc/.libs/libisc.so
>>  -lcrypto ../isc/.libs/libisc.so -ldl 
>> ../dns/.libs/libdns.so: undefined reference to `ERR_remove_state'
>> ../dns/.libs/libdns.so: undefined reference to `CRYPTO_set_id_callback'
>> collect2: error: ld returned 1 exit status
>> Makefile:483: recipe for target 'resolve' failed
>> make[5]: *** [resolve] Error 1
>> 
>> anyone else seeing this?
>> 
>> I think a patch shouldn’t be too complicated, but I’m surprised that the 
>> buildbots didn’t catch this.
>> 
>> -Philip
> 
> Hmm, I wonder if the linker is picking up your host system libcrypto
> instead of the target build. Does your staging_dir/target-.../usr/lib have
> a libcrypto.so (that is a symlink to libcrypto.so.1.0.0)?


It does:

% ls -ltr staging_dir/target-x86_64_musl_powercode-bmu/usr/lib/libcrypto*
-rw-r--r-- 1 philipp philipp 5200098 Aug  7 13:35 
staging_dir/target-x86_64_musl_powercode-bmu/usr/lib/libcrypto.a
-r-xr-xr-x 1 philipp philipp 2162104 Aug  7 13:35 
staging_dir/target-x86_64_musl_powercode-bmu/usr/lib/libcrypto.so.1.0.0*
lrwxrwxrwx 1 philipp philipp  18 Aug  7 13:35 
staging_dir/target-x86_64_musl_powercode-bmu/usr/lib/libcrypto.so -> 
libcrypto.so.1.0.0*
%


And the configure happened as:

AR="x86_64-openwrt-linux-musl-gcc-ar" AS="x86_64-openwrt-linux-musl-gcc -c -Os 
-pipe -fno-caller-saves -fno-plt -fhonour-copts 
-Wno-error=unused-but-set-variable -Wno-error=unused-result 
-iremap/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.11.2:bind-9.11.2
 -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro" 
LD=x86_64-openwrt-linux-musl-ld NM="x86_64-openwrt-linux-musl-gcc-nm" 
CC="x86_64-openwrt-linux-musl-gcc" GCC="x86_64-openwrt-linux-musl-gcc" 
CXX="x86_64-openwrt-linux-musl-g++" 
RANLIB="x86_64-openwrt-linux-musl-gcc-ranlib" 
STRIP=x86_64-openwrt-linux-musl-strip OBJCOPY=x86_64-openwrt-linux-musl-objcopy 
OBJDUMP=x86_64-openwrt-linux-musl-objdump SIZE=x86_64-openwrt-linux-musl-size 
CFLAGS="-Os -pipe -fno-caller-saves -fno-plt -fhonour-copts 
-Wno-error=unused-but-set-variable -Wno-error=unused-result 
-iremap/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.11.2:bind-9.11.2
 -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro " CXXFLAGS="-Os 
-pipe -fno-caller-saves -fno-plt -fhonour-copts 
-Wno-error=unused-but-set-variable -Wno-error=unused-result 
-iremap/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.11.2:bind-9.11.2
 -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro " 
CPPFLAGS="-I/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/usr/include
 
-I/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/include
 
-I/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/include
 
-I/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/include/fortify
 
-I/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/include
 " 
LDFLAGS="-L/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/usr/lib
 -L/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/lib 
-L/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib
 -L/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib 
-znow -zrelro "  BUILD_CC="x86_64-openwrt-linux-musl-gcc"   ./configure 
--target=x86_64-openwrt-linux --host=x86_64-openwrt-linux 
--build=x86_64-pc-linux-gnu --program-prefix="" --program-suffix="" 
--prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin 
--libexecdir=/usr/lib --sysconfdir=/etc --datadir=/usr/share 
--localstatedir=/var --mandir=/usr/man --infodir=/usr/info --disable-nls  
--enable-shared

Re: [LEDE-DEV] [PATCH 00/13] sunxi: upgrade to kernel 4.9 and add A64 support

2017-08-07 Thread Lucian Cristian 

On 07.08.2017 19:47, Lucian Cristian wrote:

On 07.08.2017 19:43, Hauke Mehrtens wrote:

...



Hi Lucian,

The eMMC version needs an extra device tree file, could you please use
this one:
arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts

We should probably add two device one for the normal lime2 and one
lime2-emmc.

Hauke


Yes, I know, on 4.4 it worked with or without emmc dts, but since it 
wasn't merged I didn't made a patch for eMMC version, I'll return with 
output asap


Regards


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


So I made a test without the split and it worked, but on the same three 
with the split I didn't had an option for root partition size on 
menuconfig so I made a new git clone and I can confirm that is booting.


Something must have been broken in my branch!


Regards


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

Re: [LEDE-DEV] [RFC] kernel patches cleanup

2017-08-07 Thread Rafał Miłecki 
On 7 August 2017 at 21:20, Philip Prindeville
 wrote:
>> On Jul 31, 2017, at 10:11 AM, John Crispin  wrote:
>>
>> Hi,
>>
>> I rebased my ages old kernel patch cleanup series. It can be found here [1].
>>
>> the series annotates all patches and splits them up into 3 folders 
>> backports/pending/hacks.
>
>
> What’s the criteria for each?
>
> And isn’t “hacks” kind of self-defeating?  If someone submits a PR that adds 
> something to “hacks”, won’t the default position be, “since this is 
> admittedly a hack, it’s not really needed and you should find a more 
> compelling fix”?

Sometimes getting upstream-acceptable solution takes months (or
years), so I'm OK accepting well-described and argumented "hacks".

-- 
Rafał

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

Re: [LEDE-DEV] [RFC] kernel patches cleanup

2017-08-07 Thread Philip Prindeville 

> On Jul 31, 2017, at 10:11 AM, John Crispin  wrote:
> 
> Hi,
> 
> I rebased my ages old kernel patch cleanup series. It can be found here [1].
> 
> the series annotates all patches and splits them up into 3 folders 
> backports/pending/hacks.


What’s the criteria for each?

And isn’t “hacks” kind of self-defeating?  If someone submits a PR that adds 
something to “hacks”, won’t the default position be, “since this is admittedly 
a hack, it’s not really needed and you should find a more compelling fix”?

-Philip


> 
> I'd like to push this asap if there are no mayor issues as it will be a pain 
> to rebase once again
> 
>John
> 
> 
> [1] 
> https://git.lede-project.org/?p=lede/blogic/staging.git;a=shortlog;h=refs/heads/patches-cleanup
> 


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

Re: [LEDE-DEV] [PATCH] lantiq: fix missing otg_cap on danube platform

2017-08-07 Thread Hauke Mehrtens 


On 08/04/2017 08:45 PM, Daniel wrote:
> Not sure about your question. I'm just re-adding the deleted code in
> the last commit on the affected kernel patch:
> 
> https://github.com/lede-project/source/commit/f036956e1f6a38bfc4e678adf404f3a717ceaed8#diff-0928a7bd0f08843e69824f86d7a82782L35
> 
> I assume the only one important parameter here is " .otg_cap
>  = 2, "
> Which is causing the danube boards don't initialize the USB port correctly.
> 
> Related bug 
> https://bugs.lede-project.org/index.php?do=details_id=351=11[0]=
> As Mohammed Berdai commented in the last post the ARV7518PW doesn't
> detect anything on the usb port. Not sure if all danube boards are
> affected. The patch solves the problem.

Hi,

I will take care about this problem.

Danube supports host only mode and device only mode, are there any
boards with USB configured in device only mode out there and did it ever
worked with LEDE?

Hauke

> 
> Regards.
> 
> 2017-08-04 18:41 GMT+02:00 Hauke Mehrtens :
>>
>>
>>
>> On 07/29/2017 02:54 PM, Daniel Gonzalez Cabanelas wrote:
>>> USB doesn't work in some danube boards because otg_cap
>>> is missing since previous changes made on the USB-dwc2
>>> lantiq driver. Fix it.
>>>
>>> Tested on the ARV7518PW router.
>>>
>>> Signed-off-by: Daniel Gonzalez Cabanelas 
>>> ---
>>>  ...ke-the-lantiq-settings-match-vendor-drive.patch | 78 
>>> +++---
>>>  ...ke-the-lantiq-settings-match-vendor-drive.patch | 41 ++--
>>>  2 files changed, 90 insertions(+), 29 deletions(-)
>>>
>>> diff --git 
>>> a/target/linux/lantiq/patches-4.4/0061-USB-DWC2-make-the-lantiq-settings-match-vendor-drive.patch
>>>  
>>> b/target/linux/lantiq/patches-4.4/0061-USB-DWC2-make-the-lantiq-settings-match-vendor-drive.patch
>>> index 1eda4cc..d92e7b1 100644
>>> --- 
>>> a/target/linux/lantiq/patches-4.4/0061-USB-DWC2-make-the-lantiq-settings-match-vendor-drive.patch
>>> +++ 
>>> b/target/linux/lantiq/patches-4.4/0061-USB-DWC2-make-the-lantiq-settings-match-vendor-drive.patch
>>> @@ -23,16 +23,46 @@ Signed-off-by: Hauke Mehrtens 
>>>
>>>  --- a/drivers/usb/dwc2/platform.c
>>>  +++ b/drivers/usb/dwc2/platform.c
>>> -@@ -116,7 +116,7 @@ static const struct dwc2_core_params par
>>> +@@ -116,7 +116,37 @@ static const struct dwc2_core_params par
>>>   .hibernation= -1,
>>>   };
>>>
>>>  -static const struct dwc2_core_params params_ltq = {
>>> ++static const struct dwc2_core_params params_danube = {
>>> ++.otg_cap= 2,/* non-HNP/non-SRP */
>>> ++.otg_ver= -1,
>>> ++.dma_enable = -1,
>>> ++.dma_desc_enable= -1,
>>> ++.speed  = -1,
>>> ++.enable_dynamic_fifo= -1,
>>> ++.en_multiple_tx_fifo= -1,
>>> ++.host_rx_fifo_size  = -1,
>>> ++.host_nperio_tx_fifo_size   = -1,
>>> ++.host_perio_tx_fifo_size= -1,
>>> ++.max_transfer_size  = -1,
>>> ++.max_packet_count   = -1,
>>> ++.host_channels  = -1,
>>> ++.phy_type   = -1,
>>> ++.phy_utmi_width = -1,
>>> ++.phy_ulpi_ddr   = -1,
>>> ++.phy_ulpi_ext_vbus  = -1,
>>> ++.i2c_enable = -1,
>>> ++.ulpi_fs_ls = -1,
>>> ++.host_support_fs_ls_low_power   = -1,
>>> ++.host_ls_low_power_phy_clk  = -1,
>>> ++.ts_dline   = -1,
>>> ++.reload_ctl = -1,
>>> ++.ahbcfg = -1,
>>> ++.uframe_sched   = -1,
>>> ++.external_id_pin_ctl= -1,
>>> ++.hibernation= -1,
>>> ++};
>>> ++
>>>  +static const struct dwc2_core_params params_ase = {
>>>   .otg_cap= 2,/* non-HNP/non-SRP */
>>>   .otg_ver= -1,
>>>   .dma_enable = -1,
>>> -@@ -127,8 +127,8 @@ static const struct dwc2_core_params par
>>> +@@ -127,8 +157,38 @@ static const struct dwc2_core_params par
>>>   .host_rx_fifo_size  = 288,  /* 288 DWORDs */
>>>   .host_nperio_tx_fifo_size   = 128,  /* 128 DWORDs */
>>>   .host_perio_tx_fifo_size= 96,   /* 96 DWORDs */
>>> @@ -40,15 +70,17 @@ Signed-off-by: Hauke Mehrtens 
>>>  -.max_packet_count   = 511,
>>>  +.max_transfer_size  = -1,
>>>  +.max_packet_count   = -1,
>>> - .host_channels  = -1,
>>> - .phy_type   = -1,
>>> - .phy_utmi_width = -1,
>>> -@@ -140,8 +140,37 @@ static const struct dwc2_core_params par
>>> - .host_ls_low_power_phy_clk  = -1,
>>> - .ts_dline   = -1,
>>> - .reload_ctl = -1,
>>> --

Re: [LEDE-DEV] wifi and wan ipv6 connectivity

2017-08-07 Thread Hans Dedecker 
On Sat, Aug 5, 2017 at 8:57 AM, e9hack  wrote:
> Hi,
>
> executing of command wifi disables ipv6 connectivity on wan interface. The 
> wan interface is pppoe-wan. To get ipv6
> connectivity again, I've to execute manually
>
> ubus call network add_dynamic '{ "name": "wan_6", "ifname": "@wan", "proto": 
> "dhcpv6", "zone": "wan" }'
>
> what is usually done by /lib/netifd/ppp6-up.
>
> How can I avoid this?
This is certainly not intended behavior as there's no direct link
between wireless and dynamic interfaces in netifd.

Can you elaborate a bit more giving the complete picture of the
network config  and how the issue is triggered ?

Hans
>
> Regards,
> Hartmut
>
> ___
> 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 00/13] sunxi: upgrade to kernel 4.9 and add A64 support

2017-08-07 Thread Lucian Cristian 

On 07.08.2017 19:43, Hauke Mehrtens wrote:


On 08/07/2017 06:13 PM, Lucian Cristian wrote:

On 07.08.2017 18:55, Hauke Mehrtens wrote:

On 08/06/2017 08:16 PM, Lucian Cristian wrote:

On 04.08.2017 00:37, Hauke Mehrtens wrote:

This upgrades the target to kernel 4.9 and also adds support for the
Allwinner A64 SoC. This was only tested on the pine64+ and I do not own
any older Allwinner SoC.

Could someone please test this on an older 32 bit Allwinner SoC and
report back some results.

Hauke Mehrtens (13):
 kernel: add some config options
 sunix: add support for kernel 4.9
 include: u-boot.mk: remove LEDE HOSTCPPFLAGS from u-boot
HOSTCPPFLAGS
 uboot-sunxi: update to version 2017.07
 uboot-sunxi: do not depend on dtc being install on host
 uboot-sunxi: revert the usage of binman
 sunxi: fix build of rtc package when module not available
 sunxi: split into cortex A8 and A7 subtarget
 arm-trusted-firmware-sunxi: add new package
 uboot-sunxi: build A64 SoC and pine64 U-Boot
 sunxi: Backport patches needed for A64
 sunxi: Backport patches from kernel 4.11 for A64
 sunxi: Add A64 support with cortex53 subtarget

...

On LIME2 I get the attached boot log


Regards

Hi Lucian,

Thanks you for testing. Could you send me your patch you applied to add
LIME2 please.

It looks like executing the init binary failed, could you try to only
apply my patches till "sunxi: fix build of rtc package when module not
available" please, I assume the subtarget split is somehow not working.

Hauke

I just added to the image/cortex-a7.mk, and no more dts patching like on
4.4

define Device/sun7i-a20-olinuxino-lime2
   DEVICE_TITLE:=Olimex A20-OLinuXino-LIME2
   DEVICE_PACKAGES:=kmod-ata-core kmod-ata-sunxi kmod-rtc-sunxi kmod-usb-hid
   SUPPORTED_DEVICES:=olimex,a20-olinuxino-lime2
   SUNXI_DTS:=sun7i-a20-olinuxino-lime2
endef

TARGET_DEVICES += sun7i-a20-olinuxino-lime2


and for uboot patch from here

https://github.com/lucize/source/commit/325304c62dd8f6ef1b82b94873397c31226a6f88#diff-1ab1035312dfd60272886d810ef44e7f


I actually own an eMMC version, tried that too, but is the same, for
eMMC uboot needs this

https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-sunxi/add-lime2-emmc.patch


I'll try without the split

Regards


Hi Lucian,

The eMMC version needs an extra device tree file, could you please use
this one:
arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts

We should probably add two device one for the normal lime2 and one
lime2-emmc.

Hauke


Yes, I know, on 4.4 it worked with or without emmc dts, but since it 
wasn't merged I didn't made a patch for eMMC version, I'll return with 
output asap


Regards


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

Re: [LEDE-DEV] [PATCH 00/13] sunxi: upgrade to kernel 4.9 and add A64 support

2017-08-07 Thread Hauke Mehrtens 


On 08/07/2017 06:13 PM, Lucian Cristian wrote:
> On 07.08.2017 18:55, Hauke Mehrtens wrote:
>>
>> On 08/06/2017 08:16 PM, Lucian Cristian wrote:
>>> On 04.08.2017 00:37, Hauke Mehrtens wrote:
 This upgrades the target to kernel 4.9 and also adds support for the
 Allwinner A64 SoC. This was only tested on the pine64+ and I do not own
 any older Allwinner SoC.

 Could someone please test this on an older 32 bit Allwinner SoC and
 report back some results.

 Hauke Mehrtens (13):
 kernel: add some config options
 sunix: add support for kernel 4.9
 include: u-boot.mk: remove LEDE HOSTCPPFLAGS from u-boot
 HOSTCPPFLAGS
 uboot-sunxi: update to version 2017.07
 uboot-sunxi: do not depend on dtc being install on host
 uboot-sunxi: revert the usage of binman
 sunxi: fix build of rtc package when module not available
 sunxi: split into cortex A8 and A7 subtarget
 arm-trusted-firmware-sunxi: add new package
 uboot-sunxi: build A64 SoC and pine64 U-Boot
 sunxi: Backport patches needed for A64
 sunxi: Backport patches from kernel 4.11 for A64
 sunxi: Add A64 support with cortex53 subtarget

 ...
>>> On LIME2 I get the attached boot log
>>>
>>>
>>> Regards
>> Hi Lucian,
>>
>> Thanks you for testing. Could you send me your patch you applied to add
>> LIME2 please.
>>
>> It looks like executing the init binary failed, could you try to only
>> apply my patches till "sunxi: fix build of rtc package when module not
>> available" please, I assume the subtarget split is somehow not working.
>>
>> Hauke
> 
> I just added to the image/cortex-a7.mk, and no more dts patching like on
> 4.4
> 
> define Device/sun7i-a20-olinuxino-lime2
>   DEVICE_TITLE:=Olimex A20-OLinuXino-LIME2
>   DEVICE_PACKAGES:=kmod-ata-core kmod-ata-sunxi kmod-rtc-sunxi kmod-usb-hid
>   SUPPORTED_DEVICES:=olimex,a20-olinuxino-lime2
>   SUNXI_DTS:=sun7i-a20-olinuxino-lime2
> endef
> 
> TARGET_DEVICES += sun7i-a20-olinuxino-lime2
> 
> 
> and for uboot patch from here
> 
> https://github.com/lucize/source/commit/325304c62dd8f6ef1b82b94873397c31226a6f88#diff-1ab1035312dfd60272886d810ef44e7f
> 
> 
> I actually own an eMMC version, tried that too, but is the same, for
> eMMC uboot needs this
> 
> https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-sunxi/add-lime2-emmc.patch
> 
> 
> I'll try without the split
> 
> Regards
> 

Hi Lucian,

The eMMC version needs an extra device tree file, could you please use
this one:
arch/arm/boot/dts/sun7i-a20-olinuxino-lime2-emmc.dts

We should probably add two device one for the normal lime2 and one
lime2-emmc.

Hauke

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

[LEDE-DEV] Bind not building

2017-08-07 Thread Philip Prindeville 
I’m seeing the following when building bind:

OpenWrt-libtool: link: x86_64-openwrt-linux-musl-gcc -Os -pipe 
-fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable 
-Wno-error=unused-result 
-iremap/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.10.5-P3:bind-9.10.5-P3
 -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z -Wl,now -Wl,-z -Wl,relro -znow 
-zrelro -o .libs/resolve .libs/resolve.o  
-L/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/usr/lib
 -L/home/philipp/bertram/lede/staging_dir/target-x86_64_musl_powercode-bmu/lib 
-L/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/usr/lib
 -L/home/philipp/bertram/lede/staging_dir/toolchain-x86_64_gcc-5.4.0_musl/lib 
../irs/.libs/libirs.so ../dns/.libs/libdns.so ../isccfg/.libs/libisccfg.so 
/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.10.5-P3/lib/dns/.libs/libdns.so
 
/home/philipp/bertram/lede/build_dir/target-x86_64_musl_powercode-bmu/bind-9.10.5-P3/lib/isc/.libs/libisc.so
 -lcrypto ../isc/.libs/libisc.so -ldl 
../dns/.libs/libdns.so: undefined reference to `ERR_remove_state'
../dns/.libs/libdns.so: undefined reference to `CRYPTO_set_id_callback'
collect2: error: ld returned 1 exit status
Makefile:483: recipe for target 'resolve' failed
make[5]: *** [resolve] Error 1

anyone else seeing this?

I think a patch shouldn’t be too complicated, but I’m surprised that the 
buildbots didn’t catch this.

-Philip


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

Re: [LEDE-DEV] [PATCH 00/13] sunxi: upgrade to kernel 4.9 and add A64 support

2017-08-07 Thread Lucian Cristian 

On 07.08.2017 18:55, Hauke Mehrtens wrote:


On 08/06/2017 08:16 PM, Lucian Cristian wrote:

On 04.08.2017 00:37, Hauke Mehrtens wrote:

This upgrades the target to kernel 4.9 and also adds support for the
Allwinner A64 SoC. This was only tested on the pine64+ and I do not own
any older Allwinner SoC.

Could someone please test this on an older 32 bit Allwinner SoC and
report back some results.

Hauke Mehrtens (13):
kernel: add some config options
sunix: add support for kernel 4.9
include: u-boot.mk: remove LEDE HOSTCPPFLAGS from u-boot HOSTCPPFLAGS
uboot-sunxi: update to version 2017.07
uboot-sunxi: do not depend on dtc being install on host
uboot-sunxi: revert the usage of binman
sunxi: fix build of rtc package when module not available
sunxi: split into cortex A8 and A7 subtarget
arm-trusted-firmware-sunxi: add new package
uboot-sunxi: build A64 SoC and pine64 U-Boot
sunxi: Backport patches needed for A64
sunxi: Backport patches from kernel 4.11 for A64
sunxi: Add A64 support with cortex53 subtarget

...

On LIME2 I get the attached boot log


Regards

Hi Lucian,

Thanks you for testing. Could you send me your patch you applied to add
LIME2 please.

It looks like executing the init binary failed, could you try to only
apply my patches till "sunxi: fix build of rtc package when module not
available" please, I assume the subtarget split is somehow not working.

Hauke


I just added to the image/cortex-a7.mk, and no more dts patching like on 4.4

define Device/sun7i-a20-olinuxino-lime2
  DEVICE_TITLE:=Olimex A20-OLinuXino-LIME2
  DEVICE_PACKAGES:=kmod-ata-core kmod-ata-sunxi kmod-rtc-sunxi kmod-usb-hid
  SUPPORTED_DEVICES:=olimex,a20-olinuxino-lime2
  SUNXI_DTS:=sun7i-a20-olinuxino-lime2
endef

TARGET_DEVICES += sun7i-a20-olinuxino-lime2


and for uboot patch from here

https://github.com/lucize/source/commit/325304c62dd8f6ef1b82b94873397c31226a6f88#diff-1ab1035312dfd60272886d810ef44e7f

I actually own an eMMC version, tried that too, but is the same, for 
eMMC uboot needs this


https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-sunxi/add-lime2-emmc.patch

I'll try without the split

Regards


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

[LEDE-DEV] [PATCH] kernel: update kernel 4.4 to version 4.4.80

2017-08-07 Thread Kevin Darbyshire-Bryant 
refresh patches
minor rework 704-phy-no-genphy-soft-reset.patch which was partially
accepted upstream.

Signed-off-by: Kevin Darbyshire-Bryant 
---
 include/kernel-version.mk|  4 ++--
 .../680-NET-skip-GRO-for-foreign-MAC-addresses.patch | 10 +-
 .../generic/pending-4.4/701-phy_extension.patch  |  2 +-
 .../pending-4.4/704-phy-no-genphy-soft-reset.patch   | 20 +---
 .../710-phy-add-mdio_register_board_info.patch   |  2 +-
 .../linux/generic/pending-4.4/721-phy_packets.patch  |  2 +-
 ...128-phy-export-phy_speed_to_str-for-phylink.patch |  2 +-
 7 files changed, 12 insertions(+), 30 deletions(-)

diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index ca2cb8f..31b1d12 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -3,11 +3,11 @@
 LINUX_RELEASE?=1
 
 LINUX_VERSION-3.18 = .43
-LINUX_VERSION-4.4 = .79
+LINUX_VERSION-4.4 = .80
 LINUX_VERSION-4.9 = .40
 
 LINUX_KERNEL_HASH-3.18.43 = 
1236e8123a6ce537d5029232560966feed054ae31776fe8481dd7d18cdd5492c
-LINUX_KERNEL_HASH-4.4.79 = 
0dbda3b51e11957fdb96c46844a823a212d46d6db680d77422ddea1a65bebca8
+LINUX_KERNEL_HASH-4.4.80 = 
34f849d5d837d0b2b75c14bc692c275da0784c0a96b72ab847f12e9dc83c40c3
 LINUX_KERNEL_HASH-4.9.40 = 
025767f3652a656c7b5ed2949aef205f88a5acfd70ae3fe77710ad37f1662d9b
 
 ifdef KERNEL_PATCHVER
diff --git 
a/target/linux/generic/pending-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
 
b/target/linux/generic/pending-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
index 0c58710..0616eaa 100644
--- 
a/target/linux/generic/pending-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
+++ 
b/target/linux/generic/pending-4.4/680-NET-skip-GRO-for-foreign-MAC-addresses.patch
@@ -17,7 +17,7 @@ Signed-off-by: Felix Fietkau 
 
 --- a/net/core/dev.c
 +++ b/net/core/dev.c
-@@ -4249,6 +4249,9 @@ static enum gro_result dev_gro_receive(s
+@@ -4256,6 +4256,9 @@ static enum gro_result dev_gro_receive(s
enum gro_result ret;
int grow;
  
@@ -27,7 +27,7 @@ Signed-off-by: Felix Fietkau 
if (!(skb->dev->features & NETIF_F_GRO))
goto normal;
  
-@@ -5415,6 +5418,48 @@ static void __netdev_adjacent_dev_unlink
+@@ -5422,6 +5425,48 @@ static void __netdev_adjacent_dev_unlink
   _dev->adj_list.lower);
  }
  
@@ -76,7 +76,7 @@ Signed-off-by: Felix Fietkau 
  static int __netdev_upper_dev_link(struct net_device *dev,
   struct net_device *upper_dev, bool master,
   void *private)
-@@ -5486,6 +5531,7 @@ static int __netdev_upper_dev_link(struc
+@@ -5493,6 +5538,7 @@ static int __netdev_upper_dev_link(struc
goto rollback_lower_mesh;
}
  
@@ -84,7 +84,7 @@ Signed-off-by: Felix Fietkau 
call_netdevice_notifiers_info(NETDEV_CHANGEUPPER, dev,
  _info.info);
return 0;
-@@ -5612,6 +5658,7 @@ void netdev_upper_dev_unlink(struct net_
+@@ -5619,6 +5665,7 @@ void netdev_upper_dev_unlink(struct net_
list_for_each_entry(i, _dev->all_adj_list.upper, list)
__netdev_adjacent_dev_unlink(dev, i->dev, i->ref_nr);
  
@@ -92,7 +92,7 @@ Signed-off-by: Felix Fietkau 
call_netdevice_notifiers_info(NETDEV_CHANGEUPPER, dev,
  _info.info);
  }
-@@ -6152,6 +6199,7 @@ int dev_set_mac_address(struct net_devic
+@@ -6159,6 +6206,7 @@ int dev_set_mac_address(struct net_devic
if (err)
return err;
dev->addr_assign_type = NET_ADDR_SET;
diff --git a/target/linux/generic/pending-4.4/701-phy_extension.patch 
b/target/linux/generic/pending-4.4/701-phy_extension.patch
index 6cb3fdf..a1c48b7 100644
--- a/target/linux/generic/pending-4.4/701-phy_extension.patch
+++ b/target/linux/generic/pending-4.4/701-phy_extension.patch
@@ -53,7 +53,7 @@
   * @phydev: the phy_device struct
 --- a/include/linux/phy.h
 +++ b/include/linux/phy.h
-@@ -796,6 +796,7 @@ void phy_start_machine(struct phy_device
+@@ -800,6 +800,7 @@ void phy_start_machine(struct phy_device
  void phy_stop_machine(struct phy_device *phydev);
  int phy_ethtool_sset(struct phy_device *phydev, struct ethtool_cmd *cmd);
  int phy_ethtool_gset(struct phy_device *phydev, struct ethtool_cmd *cmd);
diff --git 
a/target/linux/generic/pending-4.4/704-phy-no-genphy-soft-reset.patch 
b/target/linux/generic/pending-4.4/704-phy-no-genphy-soft-reset.patch
index d876187..0d89b4b 100644
--- a/target/linux/generic/pending-4.4/704-phy-no-genphy-soft-reset.patch
+++ b/target/linux/generic/pending-4.4/704-phy-no-genphy-soft-reset.patch
@@ -1,29 +1,11 @@
 --- a/drivers/net/phy/phy_device.c
 +++ b/drivers/net/phy/phy_device.c
-@@ -1213,7 +1213,7 @@ int genphy_config_init(struct phy_device
-   return 0;
- }
- 
--static int gen10g_soft_reset(struct

[LEDE-DEV] [PATCH] base-files: don't setup network in preinit if failsafe is disabled

2017-08-07 Thread Rafał Miłecki 
From: Rafał Miłecki 

With failsafe disabled there is no point in early network setup. We
don't send announcement over UDP and there is no way to ssh to the
device.

Signed-off-by: Rafał Miłecki 
---
 package/base-files/files/lib/preinit/10_indicate_preinit | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/package/base-files/files/lib/preinit/10_indicate_preinit 
b/package/base-files/files/lib/preinit/10_indicate_preinit
index 666f9aa860..5442a749b1 100644
--- a/package/base-files/files/lib/preinit/10_indicate_preinit
+++ b/package/base-files/files/lib/preinit/10_indicate_preinit
@@ -99,6 +99,8 @@ preinit_config_board() {
 }
 
 preinit_ip() {
+   [ "$pi_preinit_no_failsafe" = "y" ] && return
+
# if the preinit interface isn't specified and ifname is set in
# preinit.arch use that interface
if [ -z "$pi_ifname" ]; then
@@ -110,6 +112,8 @@ preinit_ip() {
elif [ -d "/etc/board.d/" ]; then
preinit_config_board
fi
+
+   preinit_net_echo "Doing Lede Preinit\n"
 }
 
 preinit_ip_deconfig() {
@@ -144,7 +148,6 @@ preinit_net_echo() {
 }
 
 pi_indicate_preinit() {
-   preinit_net_echo "Doing Lede Preinit\n"
set_state preinit
 }
 
-- 
2.11.0


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

Re: [LEDE-DEV] b43 support for AC chipsets like BCM4360 and BCM4352?

2017-08-07 Thread Rafał Miłecki 
On 7 August 2017 at 08:25, Baptiste Jonglez  wrote:
> On Mon, Jul 31, 2017 at 06:31:43PM -0700, ros...@gmail.com wrote:
>> Based on kernel activity, this driver is not under active development.
>>
>> And yes, avoid.
>
> Ok, I was hoping to get an answer from Rafał or Hauke.
>
> But you seem to be right about the development activity!

There isn't any behind the scenes development going on I'm aware of.

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

[LEDE-DEV] [PATCH] base-files: drop unused preinit_echo function

2017-08-07 Thread Rafał Miłecki 
From: Rafał Miłecki 

It isn't used for years since 99_10_run_init has been dropped.

Signed-off-by: Rafał Miłecki 
---
 package/base-files/files/lib/preinit/10_indicate_preinit | 5 -
 1 file changed, 5 deletions(-)

diff --git a/package/base-files/files/lib/preinit/10_indicate_preinit 
b/package/base-files/files/lib/preinit/10_indicate_preinit
index 43bd04d444..666f9aa860 100644
--- a/package/base-files/files/lib/preinit/10_indicate_preinit
+++ b/package/base-files/files/lib/preinit/10_indicate_preinit
@@ -143,11 +143,6 @@ preinit_net_echo() {
}
 }
 
-preinit_echo() {
-   preinit_net_echo $1
-   echo $1
-}
-
 pi_indicate_preinit() {
preinit_net_echo "Doing Lede Preinit\n"
set_state preinit
-- 
2.11.0


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

Re: [LEDE-DEV] b43 support for AC chipsets like BCM4360 and BCM4352?

2017-08-07 Thread Baptiste Jonglez 
On Mon, Jul 31, 2017 at 06:31:43PM -0700, ros...@gmail.com wrote:
> Based on kernel activity, this driver is not under active development.
> 
> And yes, avoid.

Ok, I was hoping to get an answer from Rafał or Hauke.

But you seem to be right about the development activity!

Thanks,
Baptiste

> On Tue, 2017-08-01 at 00:42 +0200, Baptiste Jonglez wrote:
> > Hi,
> > 
> > As far as I can tell, the b43 driver does not support AC chipsets
> > like
> > BCM4352, BCM4360, BCM4366.  Support for these is marked BROKEN
> > upstream.
> > 
> > This means that a few devices supported by LEDE actually have no
> > wireless,
> > for instance Archer C9 v1, ASUS RT-AC68U, maybe others.  Also, quite
> > a lot
> > of dual-band devices lack 5 GHz support, because BCM4360 seems to be
> > quite
> > popular as a second wireless chipset.
> > 
> > Is there any news regarding AC support in b43, and more generally
> > b43-related activity, or should we just avoid these devices?
> > 
> > Thanks,
> > Baptiste


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