[LEDE-DEV] Cubietruck / WiFi:brcmfmac / SDIO / firmware

[Bastian Bittorf]

with recent trunk r2116 i cannot get WiFi working.
First it only seems the SDIO-support must be activated
CONFIG_BRCMFMAC_SDIO=y (which is not!) but even with this i see:

root@lede:~ :) dmesg | grep -i brcm
[   11.319793] brcmfmac mmc1:0001:1: Direct firmware load for 
brcm/brcmfmac43362-sdio.bin failed with error -2
[   11.329540] brcmfmac mmc1:0001:1: Falling back to user helper
[   11.345082] firmware brcm!brcmfmac43362-sdio.bin: firmware_loading_store: 
map pages failed
[   12.390780] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 
0x50
[   13.400836] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 
0x50
[   13.430723] usbcore: registered new interface driver brcmfmac

any hints about that? was it already working and is now broken,
or was it never possible to use the WiFi for this board?

bye, bastian

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

Re: [LEDE-DEV] QCA Dakota support

[Matthew McClintock]

On Mon, Nov 7, 2016 at 3:49 PM, Christian Mehlis  wrote:
> Dakota kernel support done by QCA is public here:
> https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?h=release/collard_cc_cs=2e6acfb58dceee5baf746a9ed37a8efbad8a7626

For a little bit cleaner tree's take a look here:

https://source.codeaurora.org/quic/qsdk/mmcclint-qca/
https://chromium-review.googlesource.com/#/q/status:merged+project:chromiumos/third_party/kernel+branch:chromeos-3.18

-M

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

Re: [LEDE-DEV] extend support from Ubiquiti EdgeRouter X (UBNT-ERX) --> UBNT-ERX-SFP

[Peter Trollope]

Thanks Sven
It's working perfectly for what I need. You had a couple of typos in
the wiki which I've changed and added some more for clarity. Thanks
heaps for sharing this.
Regards
Peter



On Tue, Nov 8, 2016 at 7:11 AM, Sven Roederer  wrote:
> Am Montag, 31. Oktober 2016, 09:49:49 CET schrieb Peter Trollope:
>> Hi
>> Have you made any progress on getting the POE working? These are a
>> great little router with heaps of grunt and it's a shame the POE
>> function doesn't work.
>>
>
> Hi Peter,
>
> I made it work by using the "i2c-gpio" driver only. Still no progress on using
> the native i2c-controller of the SoC.
> All my findings are noted in the OpenWrt-Wiki page of the EdgeRouter-X.
>
> Sven
>
>
> ___
> 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] How do you develop (compile) LEDE efficiently?

[Ted Hess]

-Original Message- 
From: Weedy

Sent: Monday, November 07, 2016 3:03 PM
To: Rafał Miłecki
Cc: LEDE Development List
Subject: Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

On Sun, Nov 6, 2016 at 3:24 PM, Rafał Miłecki  wrote:

I'm looking for a new notebook, but I can't find anything with i7 quad
core + AMD GPU. I may need to buy something with i7-6500U or i7-7500U
which may be too slow for compiling LEDE.



Dell Precisions they will compile for days and never overheat. You can
get AMD or Nvidia GPUs


+1 for Dell Precision laptops - My M4300 (retired) and more recently my M4800 are quite fast for doing full builds. M4800 
w/Quad-core i7 4910MQ @2.9GHz;3.9Ghz turbo + nVidia K1100M / Intel HD graphics w/ 16GB RAM and 2x500G SSD (Raid 1). I think the 
newest series is Precision 15.


/ted


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

Re: [LEDE-DEV] QCA Dakota support

[Christian Mehlis]

Hi Again,

I received multiple private mails in the last days, please always 
include this mailing list on reply!


Current situation from my perspective:
Dakota kernel support done by QCA is public here: 
https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?h=release/collard_cc_cs=2e6acfb58dceee5baf746a9ed37a8efbad8a7626


This branch contains all code and drivers to build a Linux kernel for 
Dakota CPUs.
But this kernel tree is based on 3.14 and has more that 2400 commits on 
top. Including kernel updates, other HW support and so on.


-> someone needs to find the relevant parts (device drivers?) and 
extract and rebase them to 4.4 (current LEDE ipq Linux kernel version).
---> I have no idea how to do that in a way that we can extract the 
newest bits, but not lose relevant parts at the same time, input/advice 
from others needed!


With that kernel support we can build LEDE build targets, I started here 
https://github.com/lede-project/source/compare/master...mehlis:ipq40xx 
but this is more or less a copy on ipq806x with dk01 and dk04 dts files, 
no real support.


Feedback and ideas are welcome!

Christian

Reminder: I'm doing this in my spare time :)


Am 2016-10-31 22:38, schrieb Christian Mehlis:

Hi,

is there someone working on QCA Dakota support for lede?

Linux 4.4 already has support for the dakota ref board:
arch/arm/boot/dts/qcom-ipq4019-ap.dk01.1-c1.dts

I received a Compex WPJ428 board containing QSDK (which is in fact
openwrt based) and I want to make lede work on it.
Unfortunately there is no support for DK01 QCA refboard in lede, I
think WPJ428 is almost the same.

Regards,
Christian


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

Re: [LEDE-DEV] extend support from Ubiquiti EdgeRouter X (UBNT-ERX) --> UBNT-ERX-SFP

[Sven Roederer]

Am Montag, 31. Oktober 2016, 09:49:49 CET schrieb Peter Trollope:
> Hi
> Have you made any progress on getting the POE working? These are a
> great little router with heaps of grunt and it's a shame the POE
> function doesn't work.
> 

Hi Peter,

I made it work by using the "i2c-gpio" driver only. Still no progress on using 
the native i2c-controller of the SoC.
All my findings are noted in the OpenWrt-Wiki page of the EdgeRouter-X.

Sven


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

[LEDE-DEV] [PATCH] net-snmp: add package snmp-mibs

[Sven Roederer]

this installs the default MIBS-files under /usr/share/snmp/mibs

Signed-off-by: Sven Roederer 
---
 net/net-snmp/Makefile | 23 ---
 1 file changed, 20 insertions(+), 3 deletions(-)

diff --git a/net/net-snmp/Makefile b/net/net-snmp/Makefile
index ddd2da4..6661bcb 100644
--- a/net/net-snmp/Makefile
+++ b/net/net-snmp/Makefile
@@ -1,5 +1,5 @@
 #
-# Copyright (C) 2006-2015 OpenWrt.org
+# Copyright (C) 2006-2016 OpenWrt.org
 #
 # This is free software, licensed under the GNU General Public License v2.
 # See /LICENSE for more information.
@@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
 
 PKG_NAME:=net-snmp
 PKG_VERSION:=5.4.4
-PKG_RELEASE:=2
+PKG_RELEASE:=3
 
 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
 PKG_SOURCE_URL:=@SF/net-snmp
@@ -88,6 +88,18 @@ $(call Package/net-snmp/Default/description)
 endef
 
 
+define Package/snmp-mibs
+$(call Package/net-snmp/Default)
+  TITLE:=Open source SNMP implementation (MIB-files)
+endef
+
+define Package/snmp-mibs/description
+$(call Package/net-snmp/Default/description)
+ .
+ This package contains SNMP MIB-Files.
+endef
+
+
 SNMP_MIB_MODULES_INCLUDED = \
host/hr_device \
host/hr_disk \
@@ -165,7 +177,6 @@ CONFIGURE_ARGS += \
--enable-applications \
--disable-debugging \
--disable-manuals \
-   --disable-mibs \
--disable-scripts \
--with-out-mib-modules="$(SNMP_MIB_MODULES_EXCLUDED)" \
--with-mib-modules="$(SNMP_MIB_MODULES_INCLUDED)" \
@@ -251,7 +262,13 @@ define Package/snmp-utils/install
$(INSTALL_BIN) 
$(PKG_INSTALL_DIR)/usr/bin/snmp{get,set,status,test,trap,walk} $(1)/usr/bin/
 endef
 
+define Package/snmp-mibs/install
+   $(INSTALL_DIR) $(1)/usr/share/snmp/mibs
+   $(INSTALL_DATA) $(PKG_INSTALL_DIR)/usr/share/snmp/mibs/* 
$(1)/usr/share/snmp/mibs/
+endef
+
 $(eval $(call BuildPackage,libnetsnmp))
 $(eval $(call BuildPackage,snmp-utils))
 $(eval $(call BuildPackage,snmpd))
 $(eval $(call BuildPackage,snmpd-static))
+$(eval $(call BuildPackage,snmp-mibs))
-- 
2.1.4


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

Re: [LEDE-DEV] o2 box 6431 / VGV7510KW22 - SIP with FXS/TAE Ports | owsip or alternative ?

[Eddi De Pieri]

I've just prepared a temporary repository to test asterisk_channel for
ast11 and ast13.

Actually I haven't tried to build yet on ast11 but it builds for ast13

https://github.com/openwrt-vgv7519/asterisk_channel_lantiq

Please give it a try

PS: many thanks to Gilles Mazoyer for his work on bcm63xx from which i
copied some portions of conditionals and makefile

regards

Eddi

On Mon, Oct 31, 2016 at 9:47 PM, Hauke Mehrtens  wrote:
> Thanks for the link.
>
> I will look into the differences between the versions  and try to adapt
> that for the lantiq driver.
>
> Hauke
>
> On 10/29/2016 12:37 PM, Eddi De Pieri wrote:
>> As already said... in lede is missing the patch I've added to bb to support 
>> vmmc
>>
>> On Fri, Oct 28, 2016 at 11:24 PM, Eddi De Pieri  wrote:
>>> Give a look at
>>> https://github.com/pgid69/bcm63xx-phone/tree/master/bcm63xx-ast-chan
>>>
>>> they have the same source for both 1.8 1.11 and 1.13, it seems that it
>>> does change just the makefile... maybe it can be applied to lantiq
>>> asterisk-tapi
>>>
>>> Regards
>>>
>>> On Mon, Oct 3, 2016 at 1:56 AM, Hauke Mehrtens  wrote:
 On 09/23/2016 09:02 PM, Daniel Golle wrote:
> On Fri, Sep 23, 2016 at 08:14:24PM +0200, Dennis Schneck wrote:
>>
>>
>>
>> Hello,
>> i use the o2 box 6431 / VGV7510KW22 with LEDE r1640.
>> Like to use my SIP Accout with the 3x FXS Ports (Analog Phone / TAE 
>> Ports)
>>
>> I read about owsip but can not find a package.
>> Is there a simular package for lede ?
>
> No. owsip disappeared a while ago, asterisk-chan-lantiq was dropped
> with asterisk-1.8.x being moved to packages-abandoned, but it may
> possible to still build it. If you want to give asterisk-1.8.x with
> chan-lantiq a shot, I'd be happy to assist and maybe even forward-
> port things to asterisk-13.x -- on this box having plenty of RAM
> and flash, this might actually be a quite nice option.

 Hi Daniel,

 I looked into it and was unable to find any documentation on how to
 write a asterisk channel driver. Do you know some documentation or
 should I look into the code of the other channel drivers? My plan was to
 port the lantiq channel driver to asterisk 1.13.x.

 Hauke


 ___
 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] How do you develop (compile) LEDE efficiently?

[Weedy]

On Sun, Nov 6, 2016 at 3:24 PM, Rafał Miłecki  wrote:
> I'm looking for a new notebook, but I can't find anything with i7 quad
> core + AMD GPU. I may need to buy something with i7-6500U or i7-7500U
> which may be too slow for compiling LEDE.


Dell Precisions they will compile for days and never overheat. You can
get AMD or Nvidia GPUs

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

Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

[Tino Reichardt]

* Tino Reichardt  wrote:
> * Rafał Miłecki  wrote:
> > Hey,
> > 
> > So far I was always using my notebook for the development. My
> > requirements were Intel i7 quad core + AMD GPU. I was using some
> > Samsung but it's GPU has died and I can't replace it (stupid
> > 216-0811000 chipset).
> > 
> > I'm looking for a new notebook, but I can't find anything with i7 quad
> > core + AMD GPU. I may need to buy something with i7-6500U or i7-7500U
> > which may be too slow for compiling LEDE.

Hui, I just see you wanted to have an AMD GPU...
What about an "Ati Radeon HD 7700M (1GB)" ?

This one has i7-3720QM, 16GB RAM, ...
http://www.lapstore.de/a.php/shop/lapstore/lang/x/a/22741/kw/Dell-Precision-M4700
also about 750€


-- 
Best regards, TR

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

Re: [LEDE-DEV] [RFC] ADSL Modem Allnet All0333CJ Rev.C / Amazon-SE SoC

[Mathias Kresin]

07.11.2016 19:02, Tino Reichardt:

Now I have to check, how to start the init...

Is there currently any golden way, how the init should be done on these
devices, with very small flash memory?

I also modify the .config, to fit the drivers of the allnet ;)


In menuconfig => "Target Images" you can select the ramdisk option.

This will create kernel + initramfs. The resulting binary can be loaded 
with tftpboot and should boot to a prompt without relying on 
flash/filesystem support.


But not sure how far you already got. I guess the best would be to 
publish your git tree somewhere so that one can point you to the missing 
parts.


Mathias

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

Re: [LEDE-DEV] [RFC] ADSL Modem Allnet All0333CJ Rev.C / Amazon-SE SoC

[Tino Reichardt]

* Tino Reichardt  wrote:
> * Mathias Kresin  wrote:
> > 2016-11-06 20:47 GMT+01:00 Tino Reichardt :
> > > The main thing is, the kernel stops very early, I have turned on every
> > > debug option, but have not much info :(
> > >
> > > [0.00] Linux version 4.4.30 (mcmilk@lap-00488) (gcc version 5.4.0 
> > > (LEDE GCC 5.4.0 r2084) ) #0 Sat Nov 5 20:54:43 2016
> > > [0.00] SOC_ID_AMAZON_SE_* done!
> > > [0.00] SoC: Amazon_SE rev 1.3
> > > [0.00] bootconsole [early0] enabled
> > > [0.00] CPU0 revision is: 0001906c (MIPS 4KEc)
> > > [0.00] MIPS: machine is ALL0333CJ - Allnet ALL0333CJ DSL Modem
> > > [0.00] Determined physical RAM map:
> > > [0.00]  memory: 00518000 @ 2000 (usable)
> > > [0.00]  memory: 00136000 @ 0051a000 (usable after init)
> > > [0.00] Wasting 64 bytes for tracking 2 unused pages
> > >
> > > Has someone an idea?
> >
> > I guess I found the commit mentioned by john which removed the AMAZON
> > SE support [0] from the lantiq target. The obvious question that comes
> > in mind when having a look at this commit: Do you have enabled
> > CONFIG_SOC_AMAZON_SE in your kernel config? Not sure if it really
> > makes a difference since the config option seams to be only used by
> > target/linux/lantiq/patches-4.4/0008-MIPS-lantiq-backport-old-timer-code.patch
> > and not in the kernel at all.
> 
> Yes, CONFIG_SOC_AMAZON_SE=y is in my .config settings.
> I am trying now with cmdline settings like " ... mem=16M"
> 
> I will give feedback when done, I am also reading the patchset and try
> to get into this mips specific settings... what is when called, and so
> one...


Hui, giving mem=16M to the cmdline looks cool:


Bytes transferred = 2621444 (280004 hex)
AMAZON_SE # bootm 0x8050
Checking Images Integrity ...
  Kernel: OK
  Rootfs: OK
## Booting image at 8050 ...
   Image Name:   MIPS LEDE Linux-4.4.30
   Created:  2016-11-05  20:54:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:1227403 Bytes =  1.2 MB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[0.00] Linux version 4.4.30 (mcmilk@lap-00488) (gcc version 5.4.0 (LEDE 
GCC 5.4.0 r2084) ) #0 Sat Nov 5 20:54:43 2016
[0.00] SoC: Amazon_SE rev 1.3
[0.00] bootconsole [early0] enabled
[0.00] CPU0 revision is: 0001906c (MIPS 4KEc)
[0.00] MIPS: machine is ALL0333CJ - Allnet ALL0333CJ DSL Modem
[0.00] Determined physical RAM map:
[0.00]  memory: 003b1000 @ 2000 (usable)
[0.00]  memory: 0012d000 @ 003b3000 (usable after init)
[0.00] User-defined physical RAM map:
[0.00]  memory: 0100 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone ranges:
[0.00]   Normal   [mem 0x-0x00ff]
[0.00] Movable zone start for each node
[0.00] Early memory node ranges
[0.00]   node   0: [mem 0x-0x00ff]
[0.00] Initmem setup node 0 [mem 0x-0x00ff]
[0.00] Built 1 zonelists in Zone order, mobility grouping off.  Total 
pages: 4064
[0.00] Kernel command line: console=ttyLTQ0,115200 
ethaddr=00:0F:C9:11:95:7B mem=16M panic=1 
[0.00] PID hash table entries: 64 (order: -4, 256 bytes)
[0.00] Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.00] Memory: 10964K/16384K available (2997K kernel code, 138K rwdata, 
636K rodata, 1204K init, 206K bss, 5420K reserved, 0K cma-reserved)
[0.00] NR_IRQS:256
[0.00] CPU Clock: 266MHz
[0.00] clocksource: MIPS: mask: 0x max_cycles: 0x, 
max_idle_ns: 14334453388 ns
[0.42] sched_clock: 32 bits at 133MHz, resolution 7ns, wraps every 
16106127356ns
[0.008020] Calibrating delay loop... 264.70 BogoMIPS (lpj=529408)
[0.046985] pid_max: default: 32768 minimum: 301
[0.051956] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.058602] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.089118] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
[0.098998] pinctrl core: initialized pinctrl subsystem
[0.107817] NET: Registered protocol family 16
[0.121973] cpuidle: using governor ladder
[0.126083] cpuidle: using governor menu
[0.142542] pinctrl-xway 1e100b10.pinmux: Init done
[0.150353] dma-xway 1e104100.dma: Init done - hw rev: 4, ports: 3, 
channels: 10
[0.242163] clocksource: Switched to clocksource MIPS
[0.254495] NET: Registered protocol family 2
[0.261784] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[

[LEDE-DEV] Update on prpl Funding for OpenWrt/LEDE Projects

[Eric Schultz]

I wanted to let everyone know that prpl will be accepting proposals for
OpenWrt/LEDE project funding on a rolling basis. We want to fund your
projects to improve or add features to OpenWrt/LEDE. If you want your
project funded or you're interested in learning more, please
visit https://prpl.works/2016/09/26/openwrt-funding-round-two/ or
contact myself. Also, if you're having trouble with your proposal,
please let me know, I'm happy to help.

Thanks,

Eric

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

Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

[Tino Reichardt]

* Rafał Miłecki  wrote:
> Hey,
> 
> So far I was always using my notebook for the development. My
> requirements were Intel i7 quad core + AMD GPU. I was using some
> Samsung but it's GPU has died and I can't replace it (stupid
> 216-0811000 chipset).
> 
> I'm looking for a new notebook, but I can't find anything with i7 quad
> core + AMD GPU. I may need to buy something with i7-6500U or i7-7500U
> which may be too slow for compiling LEDE.

I like the 2 Years old "used" laptops, selled by lapstore... maybe this
one would fit your needs, for "small" money:
http://www.lapstore.de/a.php/shop/lapstore/lang/x/a/20124/kw/Lenovo-ThinkPad-W530-2447-GW3-2463-A24

Intel Core i7-3720QM (4x 2,6 GHz / 8 MB Cache / 45W TDP)
16GB RAM (4x 4GB, max possible is 32GB)
15,6" TFT LED Display with ThinkLight for working in the dark ;)
1920 x 1080 Pixel (FHD)
1x 180GB SSD in it (space for 2x 2,5" HDD)
8xDVD+/-RW Dual Double Layer
Intel HD4000 CPU graphics, for progging
NVIDIA Quadro K1000M (2048 MB), for other things (linux driver works very well)
(incl. Windows 7 Prof. license)
= 750€

> How do you develop LEDE? Do you work on some powerful machine, or do
> you compile it remotely somehow? If you do it remotely, do you mount
> remote filesystem? I need a very good access to the build_dir for my
> needs.

I am using an Dell Latitude with i7-3632QM (4C/8T), make -j6 V=s works
fine... and the Samsung SSD with 1TB is fast + big... backup is done
every X weeks to a local Server via rsync.


-- 
Best regards, TR

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

Re: [LEDE-DEV] [RFC] ADSL Modem Allnet All0333CJ Rev.C / Amazon-SE SoC

[Tino Reichardt]

* Mathias Kresin  wrote:
> 2016-11-06 20:47 GMT+01:00 Tino Reichardt :
> > The main thing is, the kernel stops very early, I have turned on every
> > debug option, but have not much info :(
> >
> > [0.00] Linux version 4.4.30 (mcmilk@lap-00488) (gcc version 5.4.0 
> > (LEDE GCC 5.4.0 r2084) ) #0 Sat Nov 5 20:54:43 2016
> > [0.00] SOC_ID_AMAZON_SE_* done!
> > [0.00] SoC: Amazon_SE rev 1.3
> > [0.00] bootconsole [early0] enabled
> > [0.00] CPU0 revision is: 0001906c (MIPS 4KEc)
> > [0.00] MIPS: machine is ALL0333CJ - Allnet ALL0333CJ DSL Modem
> > [0.00] Determined physical RAM map:
> > [0.00]  memory: 00518000 @ 2000 (usable)
> > [0.00]  memory: 00136000 @ 0051a000 (usable after init)
> > [0.00] Wasting 64 bytes for tracking 2 unused pages
> >
> > Has someone an idea?
>
> I guess I found the commit mentioned by john which removed the AMAZON
> SE support [0] from the lantiq target. The obvious question that comes
> in mind when having a look at this commit: Do you have enabled
> CONFIG_SOC_AMAZON_SE in your kernel config? Not sure if it really
> makes a difference since the config option seams to be only used by
> target/linux/lantiq/patches-4.4/0008-MIPS-lantiq-backport-old-timer-code.patch
> and not in the kernel at all.

Yes, CONFIG_SOC_AMAZON_SE=y is in my .config settings.
I am trying now with cmdline settings like " ... mem=16M"

I will give feedback when done, I am also reading the patchset and try
to get into this mips specific settings... what is when called, and so
one...

> You might want to give the parent of the mentioned commit a try, to
> make sure that it worked at least back in the days.

I tried directly multiple images from the 12.09 release for amazon-se...
they all do not boot on my system, on one I got some output:

It was this one: openwrt-lantiq-ase-NONE-jffs2-256k

boot.log:


AMAZON_SE # bootm 0x8050
Checking Images Integrity ...
  Kernel: OK
  Rootfs: OK
## Booting image at 8050 ...
   Image Name:   MIPS OpenWrt Linux-3.3.8
   Created:  2013-03-23  13:11:17 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:972129 Bytes = 949.3 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

[0.00] Linux version 3.3.8 (blogic@Debian-60-squeeze-64-minimal) (gcc 
version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #1 Sat Mar 23 
13:11:07 UTC 2013
[0.00] SoC: Amazon_SE rev 1.3
[0.00] bootconsole [early0] enabled
[0.00] CPU revision is: 0001906c (MIPS 4KEc)
[0.00] Determined physical RAM map:
[0.00]  memory: 0100 @  (usable)
[0.00] Initrd not found or empty - disabling initrd
[0.00] Zone PFN ranges:
[0.00]   Normal   0x -> 0x1000
[0.00] Movable zone start PFN for each node
[0.00] Early memory PFN ranges
[0.00] 0: 0x -> 0x1000
[0.00] Built 1 zonelists in Zone order, mobility grouping off.  Total 
pages: 4064
[0.00] Kernel command line:
[0.00] PID hash table entries: 64 (order: -4, 256 bytes)
[0.00] Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.00] Primary instruction cache 8kB, VIPT, 4-way, linesize 16 bytes.
[0.00] Primary data cache 8kB, 2-way, VIPT, no aliases, linesize 16 
bytes
[0.00] Memory: 13132k/16384k available (2316k kernel code, 3252k 
reserved, 366k data, 164k init, 0k highmem)
[0.00] NR_IRQS:256
[0.00] CPU Clock: 266MHz
[0.00] Calibrating delay loop... 264.70 BogoMIPS (lpj=529408)
[0.036000] pid_max: default: 32768 minimum: 301
[0.04] Mount-cache hash table entries: 512
[0.056000] NET: Registered protocol family 16
[0.068000] gpiochip_add: registered GPIOs 0 to 15 on device: ltq_gpio
[0.072000] gpiochip_add: registered GPIOs 16 to 31 on device: ltq_gpio
[0.076000] MIPS: machine is Generic Lantiq based board
[0.104000] bio: create slab  at 0
[0.116000] Switching to clocksource MIPS
[0.132000] NET: Registered protocol family 2
[0.136000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.144000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[0.152000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[0.156000] TCP: Hash tables configured (established 512 bind 512)
[0.164000] TCP reno registered
[0.168000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[0.172000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[0.18] NET: Registered protocol family 1
[0.184000] gptu: totally 6 16-bit timers/counters
[0.192000] gptu: misc_register on minor 63
[0.196000] gptu: succeeded to request irq 126
[ 

[LEDE-DEV] [PATCH 2/2] iperf3: update to version 3.1.4

[Christian Lamparter]

"This release fixes a few minor bugs, including a
(non-security-impacting) buffer overflow fix ported
from upstream cjson."


Signed-off-by: Christian Lamparter 
---
 package/network/utils/iperf3/Makefile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/network/utils/iperf3/Makefile 
b/package/network/utils/iperf3/Makefile
index d68ac2b..5283842 100644
--- a/package/network/utils/iperf3/Makefile
+++ b/package/network/utils/iperf3/Makefile
@@ -8,12 +8,12 @@
 include $(TOPDIR)/rules.mk
 
 PKG_NAME:=iperf
-PKG_VERSION:=3.1.3
+PKG_VERSION:=3.1.4
 PKG_RELEASE:=1
 
 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
 PKG_SOURCE_URL:=http://downloads.es.net/pub/iperf
-PKG_MD5SUM:=3fb849c24a2370af60687cf673b67bc7
+PKG_MD5SUM:=db61d70ac62003ebe0bf15496bd8c4b3c4b728578a44d0a1a88fcf8afc0e8f76
 
 PKG_MAINTAINER:=Felix Fietkau 
 PKG_LICENSE:=BSD-3-Clause
-- 
2.10.2


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

[LEDE-DEV] [PATCH 1/2] apm821xx: redo WAN green and yellow LEDs

[Christian Lamparter]

Because the WAN port is handled by the internal AR8327N switch, the
device should use swconfig_leds trigger to handle the link activity
of the WAN LED. This has the added bonus that the WAN LED will now
go dark if there's no ethernet cable connected to the WAN port.

Signed-off-by: Christian Lamparter 
---
 target/linux/apm821xx/base-files/etc/board.d/01_leds | 3 ++-
 target/linux/apm821xx/nand/config-default| 2 ++
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/target/linux/apm821xx/base-files/etc/board.d/01_leds 
b/target/linux/apm821xx/base-files/etc/board.d/01_leds
index 76edbd1..b34f5fe 100755
--- a/target/linux/apm821xx/base-files/etc/board.d/01_leds
+++ b/target/linux/apm821xx/base-files/etc/board.d/01_leds
@@ -29,7 +29,8 @@ mbl)
 
 wndr4700)
ucidef_set_led_ide "sata" "SATA" "wndr4700:green:hd"
-   ucidef_set_led_netdev "wan" "WAN (green)" "wndr4700:green:wan" "eth0.2"
+   ucidef_set_led_switch "wan_green" "WAN (green)" "wndr4700:green:wan" 
"switch0" "0x20"
+   ucidef_set_led_netdev "wan_yellow" "WAN (yellow)" "wndr4700:yellow:wan" 
"eth0.2" "tx rx"
ucidef_set_led_usbport "usb3" "USB3" "wndr4700:blue:usb" "usb2-port1" 
"usb2-port2" "usb3-port1" "usb3-port2"
ucidef_set_led_wlan "wlan2g" "WLAN2G" "wndr4700:blue:wlan" "phy0tpt"
ucidef_set_led_wlan "wlan5g" "WLAN5G" "wndr4700:blue:wlan" "phy1tpt"
diff --git a/target/linux/apm821xx/nand/config-default 
b/target/linux/apm821xx/nand/config-default
index d6328fd..d17c2c9 100644
--- a/target/linux/apm821xx/nand/config-default
+++ b/target/linux/apm821xx/nand/config-default
@@ -39,4 +39,6 @@ CONFIG_UBIFS_FS=y
 # CONFIG_UBIFS_FS_ADVANCED_COMPR is not set
 CONFIG_SENSORS_LM90=y
 CONFIG_SENSORS_TC654=y
+CONFIG_SWCONFIG=y
+CONFIG_SWCONFIG_LEDS=y
 CONFIG_WNDR4700=y
-- 
2.10.2


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

Re: [LEDE-DEV] [RFC] ADSL Modem Allnet All0333CJ Rev.C / Amazon-SE SoC

[Mathias Kresin]

2016-11-06 20:47 GMT+01:00 Tino Reichardt :
> The main thing is, the kernel stops very early, I have turned on every
> debug option, but have not much info :(
>
> [0.00] Linux version 4.4.30 (mcmilk@lap-00488) (gcc version 5.4.0 
> (LEDE GCC 5.4.0 r2084) ) #0 Sat Nov 5 20:54:43 2016
> [0.00] SOC_ID_AMAZON_SE_* done!
> [0.00] SoC: Amazon_SE rev 1.3
> [0.00] bootconsole [early0] enabled
> [0.00] CPU0 revision is: 0001906c (MIPS 4KEc)
> [0.00] MIPS: machine is ALL0333CJ - Allnet ALL0333CJ DSL Modem
> [0.00] Determined physical RAM map:
> [0.00]  memory: 00518000 @ 2000 (usable)
> [0.00]  memory: 00136000 @ 0051a000 (usable after init)
> [0.00] Wasting 64 bytes for tracking 2 unused pages
>
> Has someone an idea?

I guess I found the commit mentioned by john which removed the AMAZON
SE support [0] from the lantiq target. The obvious question that comes
in mind when having a look at this commit: Do you have enabled
CONFIG_SOC_AMAZON_SE in your kernel config? Not sure if it really
makes a difference since the config option seams to be only used by
target/linux/lantiq/patches-4.4/0008-MIPS-lantiq-backport-old-timer-code.patch
and not in the kernel at all.

You might want to give the parent of the mentioned commit a try, to
make sure that it worked at least back in the days.

The last bootlog if found which doesn't hang while/after setting up
memory is from 2012 [1]. According to the kernel version it has to be
around the time OpenWrt 12.09 Attitude Adjustment was released.

Mathias

[0] https://git.lede-project.org/c821836
[1] https://forum.openwrt.org/viewtopic.php?pid=178271#p178271

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

Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

[Bas Mevissen]

On 06/11/16 21:24, Rafał Miłecki wrote:


How do you develop LEDE? Do you work on some powerful machine, or do
you compile it remotely somehow? If you do it remotely, do you mount
remote filesystem? I need a very good access to the build_dir for my
needs.



I' using a Centos 7 installed virtual private server with SSD storage. 
I'm using a Mate desktop on it, which I access with X2Go over the 
internet. Files with sshfs most of the time. Nightly backup of most 
important files to my NAS at home. I'm using a hosted Git repository to 
share my work with my customer.


This all works really well. Even the compile performance is very high.

Cheers,

--
Bas.

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

Re: [LEDE-DEV] [PATCH] kernel/mtd: Add support for Macronix mx25u25635f, used in Archer C2600 v1.1

[Rafał Miłecki]

On 31 May 2016 at 10:04, A. Benz  wrote:
> On 05/31/16 04:56, Rafał Miłecki wrote:
>>
>> On 30 May 2016 at 11:52, Ash Benz  wrote:
>>>
>>> Signed-off-by: Ash Benz 
>>> ---
>>>  .../475-mtd-spi-nor-add-macronix-mx25u25635f.patch | 10
>>> ++
>>>  1 file changed, 10 insertions(+)
>>>  create mode 100644
>>> target/linux/generic/patches-3.18/475-mtd-spi-nor-add-macronix-mx25u25635f.patch
>>>
>>> diff --git
>>> a/target/linux/generic/patches-3.18/475-mtd-spi-nor-add-macronix-mx25u25635f.patch
>>> b/target/linux/generic/patches-3.18/475-mtd-spi-nor-add-macronix-mx25u25635f.patch
>>> new file mode 100644
>>> index 000..72c0832
>>> --- /dev/null
>>> +++
>>> b/target/linux/generic/patches-3.18/475-mtd-spi-nor-add-macronix-mx25u25635f.patch
>>> @@ -0,0 +1,10 @@
>>> +--- a/drivers/mtd/spi-nor/spi-nor.c
>>>  b/drivers/mtd/spi-nor/spi-nor.c
>>> +@@ -532,6 +532,7 @@ static const struct spi_device_id spi_no
>>> +   { "mx25l12805d", INFO(0xc22018, 0, 64 * 1024, 256, 0) },
>>> +   { "mx25l12855e", INFO(0xc22618, 0, 64 * 1024, 256, 0) },
>>> +   { "mx25l25635e", INFO(0xc22019, 0, 64 * 1024, 512, 0) },
>>> ++  { "mx25u25635f", INFO(0xc22539, 0, 64 * 1024, 512, 0) },
>>> +   { "mx25l25655e", INFO(0xc22619, 0, 64 * 1024, 512, 0) },
>>> +   { "mx66l51235l", INFO(0xc2201a, 0, 64 * 1024, 1024,
>>> SPI_NOR_QUAD_READ) },
>>> +   { "mx66l1g55g",  INFO(0xc2261b, 0, 64 * 1024, 2048,
>>> SPI_NOR_QUAD_READ) },
>>
>>
>> This patch is so trivial there is no reason not to upstream it. Please
>> send it to the l2-mtd ML. I should've said it earlier, but I missed
>> it.
>>
> Hi Rafał,
>
> Will do. Thanks.

I can't find your patch sent upstream. Did I miss is?

-- 
Rafał

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

Re: [LEDE-DEV] [PATCH netifd] device: extend interface.macaddr option to refer to another interface

[Guenther Kelleter]

Please see below

> -Original Message-
> From: Felix Fietkau [mailto:n...@nbd.name]
> Sent: Friday, November 4, 2016 3:09 PM
> To: Guenther Kelleter ; lede-
> d...@lists.infradead.org
> Subject: Re: [LEDE-DEV] [PATCH netifd] device: extend interface.macaddr
> option to refer to another interface
> 
> On 2016-11-03 13:49, Günther Kelleter wrote:
> > e.g. option macaddr "@eth0" tells netifd to use the MAC of interface eth0.
> > Use case: set MAC address of a bridge interface to a specific interface's
> > MAC regardless of bridge/interface initialization order.
> >
> > Signed-off-by: Günther Kelleter 
> > ---
> >  device.c | 16 +++-
> >  1 file changed, 15 insertions(+), 1 deletion(-)
> >
> > diff --git a/device.c b/device.c
> > index 82596e4..c63ddc7 100644
> > --- a/device.c
> > +++ b/device.c
> > @@ -256,7 +256,21 @@ device_init_settings(struct device *dev, struct
> blob_attr **tb)
> > }
> >
> > if ((cur = tb[DEV_ATTR_MACADDR])) {
> > -   ea = ether_aton(blobmsg_data(cur));
> > +   const char *data = blobmsg_data(cur);
> > +   struct device_settings ds = {0};
> > +   if (data[0] == '@') {
> > +   struct device dev = {0};
> > +   strncpy(dev.ifname, data + 1, sizeof dev.ifname);
> > +   dev.ifname[sizeof dev.ifname - 1] = '\0';
> > +   system_if_get_settings(, );
> > +   if (ds.flags & DEV_OPT_MACADDR) {
> > +   ea = (struct ether_addr *)ds.macaddr;
> > +   } else {
> > +   ea = NULL;
> > +   }
> > +   } else {
> > +   ea = ether_aton(blobmsg_data(cur));
> > +   }
> I think this is somewhat quirky. Depending on the time when this device
> is brought up, it could either get an original device mac address, or
> one that has been modified via UCI. This is also not taken into account
> on reload.
> 
> What's your use case for this?

The original issue we had was that depending on the initialization order of the 
interfaces in the bridge, the bridge got different IP addresses from DHCP.
If e.g. bridge consists of eth0 and eth1, the resulting MAC address of the 
bridge was non-deterministically either eth0's or eth1's MAC address, depending 
on some (to me) unknown varying initialization order of the eth interfaces. 
That resulted in different DHCP address assignments.
The extension fixes this so the bridge always gets the same MAC (which is in 
our case original device MAC addr. Set by the machine init or a boot time 
fixup).
Using an explicit MAC address in the bridge configuration is not an option for 
us, since we want to use the same network configuration on different devices 
(sysupgrade backup -> restore to another device).

Günther

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

Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

[David Woodhouse]

On Mon, 2016-11-07 at 01:58 -0800, Russell Senior wrote:
> > > > > > "Rafał" == Rafał Miłecki  writes:
> 
> Rafał> On 7 November 2016 at 00:40, Russell Senior 
>  wrote:
> > 
> > > 
> > > I have a 16-core build box which I connect to over ssh.  I use scp to
> > > move images to devices.  I have a testbed with ethernet connections
> > > to the build box and serial consoles on most if not all of them.
> 
> Rafał> But what about development with modifying files in build_dir?
> Rafał> That's the most tricky part for me.
> 
> I ssh into the build machine and use whatever my favorite editor of the
> moment is (vi or emancs) and modify files.  I don't understand the
> problem.
> 
> I've even been known to load emacs with X11 over a dialup connection
> with ssh X forwarding (20 years ago).  It took a while to start up, but
> was generally pretty responsive once started.  In an environment with
> flakey network, that could be painful.  GNU screen and
> persistent/reconnectable screen sessions on the build machine can help
> smooth things out.

This is what tramp-mode is for.

emacs /buildhost:/home/dwmw2/git/lede/...

-- 
dwmw2

smime.p7s
Description: S/MIME cryptographic signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

[Rafał Miłecki]

On 7 November 2016 at 10:58, Russell Senior  wrote:
>> "Rafał" == Rafał Miłecki  writes:
>
> Rafał> On 7 November 2016 at 00:40, Russell Senior 
>  wrote:
>>> I have a 16-core build box which I connect to over ssh.  I use scp to
>>> move images to devices.  I have a testbed with ethernet connections
>>> to the build box and serial consoles on most if not all of them.
>
> Rafał> But what about development with modifying files in build_dir?
> Rafał> That's the most tricky part for me.
>
> I ssh into the build machine and use whatever my favorite editor of the
> moment is (vi or emancs) and modify files.  I don't understand the
> problem.

I'm just not geeky enough to use vi/emacs, anyway, thanks for answer.

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

Re: [LEDE-DEV] TDW8970 Slow Wireless Performance when using VDSL2

[Sebastian Moeller]

Hi All,


> On Nov 6, 2016, at 11:47, Kevin Darbyshire-Bryant 
>  wrote:
> 
> 
> 
> On 06/11/16 10:12, Xander Shelley wrote:
>> Hi there,
>> 
>> I've installed LEDE Nov5 snapshot onto my TP-Link TD-W8970 router to use
>> with a UK fibre ISP (Plus.net)
>> 
>> Out of the box most things work great.
>> 
>> If I connect via Ethernet to the router from my xubuntu T410 laptop, and
>> run a speed test using (speedtest.net) I get close to line speed (31Mb/s
>> Line Speed, measured speed 29MB/s) which is great.
> 
> VDSL2 overheads would account for the drop there.

Assuming TCP/IPV4 goodput measurements the best you can expect on a 
VDSL2 line is:
sync bandwidth * coding factor * per packet overhead factor
with coding factot: 64/65
payload factor: variable depending on encapsulation, typically PPPoE with MTU 
1500 and VLAN

PPPoE: 2 Byte PPP + 6 Byte PPPoE
VLAN: 4 Byte VLAN
VDSL2 (IEEE 802.3-2012 61.3 relevant fuer VDSL2):  1 Byte Start of Frame (S), 1 
Byte End of Frame (Ck), 2 Byte TC-CRC (PTM-FCS), = 4 Byte
COMMON ethernet: 4 Byte Frame Check Sequence (FCS) + 6 (dest MAC) + 6 (src MAC) 
+ 2 (ethertype) = 18 byte
Sum: 8 + 4 + 4 + 18 = 34 Bytes
effective MTU 1500 - PPPoE - PPP = 1500 - 8 = 1492 Bytes
payload factor: (1492 - 20 - 20) / (1492 + 8 + 4 + 4 + 18) = 0.951507208388
PPPoE goodput: 31 * (1492/1526) * (64/65) = 29.8430083678
IPv4 goodput: 31 * ((1492 -20)/1526) * (64/65) = 29.4429680411
TCP/IPv4 goodput: 31 * ((1492 - 20 - 20)/1526) * (64/65) = 29.0429277145
TCP/IPv4 goodput (assuming MTU 1508 baby jumbo frames): 31 * ((1500 - 20 - 
20)/1534) * (64/65) = 29.0506468759
So 29 out of 31 is to be expected…

About the wifi problem, I would try to test against a local machine connected 
to the wired LAN ports of the router to reduce the internet introduced 
variability…

Best Regards
Sebastian



> 
>> 
>> However, when I switch over to using wifi, this measured speed drops to
>> 12-16MB/s
>> 
>> Looking at the LuCI interface it shows that my laptop is connected
>> around 113MB/s which  is as expected.
>> 
>> Am I doing anything incorrectly/missed a step in my setup?
> 
> I can't offer any magic bullet.  Wifi is notoriously variable in terms of 
> bandwidth and I have to say my 2.4Ghz is slower (similar to your measurement) 
> than 5Ghz even though rates would suggest plenty of spare capacity.
> 
> It's worth proving the router isn't running out of CPU though...a top during 
> wired/wireless tests would be helpful.
> 
> Kevin
> 
> ___
> 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] How do you develop (compile) LEDE efficiently?

[Yousong Zhou]

On 7 November 2016 at 04:24, Rafał Miłecki  wrote:
> Hey,
>
> So far I was always using my notebook for the development. My
> requirements were Intel i7 quad core + AMD GPU. I was using some
> Samsung but it's GPU has died and I can't replace it (stupid
> 216-0811000 chipset).
>
> I'm looking for a new notebook, but I can't find anything with i7 quad
> core + AMD GPU. I may need to buy something with i7-6500U or i7-7500U
> which may be too slow for compiling LEDE.
>
> How do you develop LEDE? Do you work on some powerful machine, or do
> you compile it remotely somehow? If you do it remotely, do you mount
> remote filesystem? I need a very good access to the build_dir for my
> needs.
>

Most of my development work happens on remote kvm machines with ssh
and tmux.  The best thing about this is that there is no heat and
noise from fans spining mad.

Since most changes are device agnostic, I use qemu vm to do run-test
[1].  It's quite handy and I do not often need to touch actual
hardware these days...

I use sshfs to transfer files to local machines, only occasionally
when the work has to be done on real devices.  I prefer sshfs for the
same reason as for pppossh: it's already there and no extra work to
configure each remote host.

 [1] https://gist.github.com/yousong/8d94c6823a2a6f0f79fd

yousong

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

Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

[Russell Senior]

> "Rafał" == Rafał Miłecki  writes:

Rafał> On 7 November 2016 at 00:40, Russell Senior  
wrote:
>> I have a 16-core build box which I connect to over ssh.  I use scp to
>> move images to devices.  I have a testbed with ethernet connections
>> to the build box and serial consoles on most if not all of them.

Rafał> But what about development with modifying files in build_dir?
Rafał> That's the most tricky part for me.

I ssh into the build machine and use whatever my favorite editor of the
moment is (vi or emancs) and modify files.  I don't understand the
problem.

I've even been known to load emacs with X11 over a dialup connection
with ssh X forwarding (20 years ago).  It took a while to start up, but
was generally pretty responsive once started.  In an environment with
flakey network, that could be painful.  GNU screen and
persistent/reconnectable screen sessions on the build machine can help
smooth things out.


-- 
Russell Senior, President
russ...@personaltelco.net

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

Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

[Baptiste Jonglez]

On Mon, Nov 07, 2016 at 09:51:31AM +0100, Rafał Miłecki wrote:
> >> But what about development with modifying files in build_dir? That's
> >> the most tricky part for me.
> >
> > What do you mean exactly?
> 
> Like working with quilt to modify software (kernel/packages) in the build_dir.

I see, I think I would do that directly on the server then.

> > I use the GCC compile farm to develop/compile, since the hardware there is
> > much faster than my laptop (and has more disk space).  I generally mount
> > the remote server locally using sshfs to get access to the generated
> > images and packages.  When I need to edit things in the development tree,
> > I do it directly on the server.
> 
> It sounds like sshfs being too slow for you? That's what bothers me. I
> think I'll just need to experiment with nfs and sshfs a bit and see if
> that will be fast enough for me or not.

It's not so much a matter of sshfs being slow than being unreliable.  If
you (or the server) lose network connectivity or change IP address while
you're working over sshfs, it's a bit inconvenient.  Sshfs uses fuse, so
initially it will just block I/O if the server is not reachable.  But if
the issue lasts for too long, from my experience the mountpoint will
either block I/O forever, return I/O errors or get unmounted.

Of course, on a local network, you're less likely to encounter issues.

Baptiste


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

Re: [LEDE-DEV] How do you develop (compile) LEDE efficiently?

[Baptiste Jonglez]

On Mon, Nov 07, 2016 at 06:23:49AM +0100, Rafał Miłecki wrote:
> On 7 November 2016 at 00:40, Russell Senior  wrote:
> > I have a 16-core build box which I connect to over ssh.  I use scp to
> > move images to devices.  I have a testbed with ethernet connections to
> > the build box and serial consoles on most if not all of them.
> 
> But what about development with modifying files in build_dir? That's
> the most tricky part for me.

What do you mean exactly?

I use the GCC compile farm to develop/compile, since the hardware there is
much faster than my laptop (and has more disk space).  I generally mount
the remote server locally using sshfs to get access to the generated
images and packages.  When I need to edit things in the development tree,
I do it directly on the server.


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