Re: [LEDE-DEV] [PATCH] mvebu: add support for WRT32X (venom)

michael.g...@lantisproject.com writes: > + { > + /* Spansion S34ML02G2 256MiB, OEM Layout */ > + partition@0 { > + label = "u-boot"; > + reg = <0x000 0x20>; /* 2MB */ > +

Re: [LEDE-DEV] Lack of DNS robustness for openwrt.org

John Crispin <j...@phrozen.org> writes: > On 06/05/18 22:44, Joerg Jaspert wrote: >> On 15029 March 1977, Bjørn Mork wrote: >> >>> 1) update the .org delegation to include *all* NS records for the >>> openwrt.org zone >> I added the soapstone o

Re: [LEDE-DEV] Lack of DNS robustness for openwrt.org

Jo-Philipp Wich writes: > Hi Joerg, John. > > I created an openwrt.org zone on Digital Ocean now so you could delegate > the name servers to ns1.digitalocean.com, ns2.digitalocean.com and > ns3.digitalocean.com, maybe with one of the SPI machines thrown into the > mix... Good! I

[LEDE-DEV] Lack of DNS robustness for openwrt.org

Hello, I apologize for bringing up this long-standing issue at a time where you all have need to other issues to take care of. But it's again become a real pressing issue, at least seen from the networks I have a presence in. The main problem is that there still hasn't been any update to the

Re: [LEDE-DEV] [PATCH] kernel: speed up mtdsplit_uimage for the most common use

Bjørn Mork <bj...@mork.no> writes: > This is achieved by registering in the reverse order. No, that is not true. Drop this. I tricked myself by disabling debugging while making changes. Stupid... The points for further work are valid though

[LEDE-DEV] [PATCH] kernel: speed up mtdsplit_uimage for the most common use

ns found on MTD device firmware [1.728233] 0x0040-0x005e : "kernel" [1.739291] 0x005e-0x0440 : "ubi" [1.750251] 0x0440-0x0450 : "Private" [1.761403] 0x0450-0x05500000 : "Log" [1.771983]

Re: [LEDE-DEV] [OpenWrt-Devel] [PATCH] mvebu: disable CPU_IDLE as a Mamba instability workaround

Felix Fietkau <n...@nbd.name> writes: > On 2018-03-19 10:51, Bjørn Mork wrote: >> A regression seriously affecting the Linksys WRT1900ACv1 (Mamba) was >> introduced some time between the OpenWrti/LEDE v4.4 and v4.9 kernels. >> The root cause has not yet been identi

[LEDE-DEV] [PATCH] mvebu: disable CPU_IDLE as a Mamba instability workaround

mba support. Link: https://forum.lede-project.org/t/wrt1900acv1-reboots-kernel-4-9/2025 Signed-off-by: Bjørn Mork <bj...@mork.no> --- target/linux/mvebu/config-4.14 | 4 1 file changed, 4 deletions(-) diff --git a/target/linux/mvebu/config-4.14 b/target/linux/mvebu/config-4.14 index 528

Re: [LEDE-DEV] [PATCH] usbutils: Update to version 009.

Great! Note that the OpenWrt usbreset utility has been included in this version of usbutils. usbreset is currently packaged separately with its source. Maybe consider merging the two source packages and start building usbreset as part of the usbutils package? Bjørn

Re: [LEDE-DEV] [PATCH] base-files: sysupgrade depends on sha256sum now

Matthias Schiffer writes: > We generally do no add dependencies for busybox applets that are enabled by > default - otherwise, we would also need to add dependencies for sed, awk, > grep, etc. When you change the busybox configuration, you are on your own, > and

[LEDE-DEV] [PATCH] base-files: sysupgrade depends on sha256sum now

commit 6ed389da85a9 ("base-files: sysupgrade: do not rely on opkg to list changed conffile") adds a call to sha256sum. Make sure it exists. Signed-off-by: Bjørn Mork <bj...@mork.no> --- You'll see this unless you select sha256sum: root@wrt1900ac-1:~# sysupgrade -b /tmp/foo

Re: [LEDE-DEV] [PATCH] prereq-mk: Change wget dependency to curl one.

Rosen Penev <ros...@gmail.com> writes: > On Sat, Mar 10, 2018 at 3:31 AM, Bjørn Mork <bj...@mork.no> wrote: >> Rosen Penev <ros...@gmail.com> writes: >> >>> curl is more common than GNU wget is. >> >> No. > Yes. How about throwing in an a

Re: [LEDE-DEV] [PATCH] prereq-mk: Change wget dependency to curl one.

Rosen Penev writes: > curl is more common than GNU wget is. No. > For example, Cygwin, Arch Linux, and my android phone all come with > curl by default whereas wget is missing. wget has priority "important" in Debian, while curl is "optional". I don't think it makes much

Re: [LEDE-DEV] [PATCH 0/3] uqmi: fix more dial-in issues

Bjørn Mork <bj...@mork.no> writes: > Backporting the raw-ip feature to v4.4 is simple. Just cherry-pick > > 81e0ce79f291 ("usbnet: allow mini-drivers to consume L2 headers") > 32f7adf633b9 ("net: qmi_wwan: support "raw IP" mode") > 6c730080e6

Re: [LEDE-DEV] [PATCH 0/3] uqmi: fix more dial-in issues

Koen Vandeputte writes: > On 07-02-18 22:14, Levente Kovacs wrote: >> On Wed, 7 Feb 2018 13:23:25 +0100 >> Koen Vandeputte wrote: >> Quectel EC25-A >> Does the EC25 work without any kernel patch? I was testing EC25 with 17.01.1,

Re: [LEDE-DEV] [PATCH 3/3] usbmode: remove devices with unsupported modes

Julian Labus <jul...@labus-online.de> writes: > On 12/22/2017 10:48 AM, Bjørn Mork wrote: >> Julian Labus <jul...@labus-online.de> writes: >> >>> diff --git a/package/utils/usbmode/Makefile b/package/utils/usbmode/Makefile >>> index 7f0195fdce..1b1e

Re: [LEDE-DEV] [PATCH 3/3] usbmode: remove devices with unsupported modes

Julian Labus writes: > diff --git a/package/utils/usbmode/Makefile b/package/utils/usbmode/Makefile > index 7f0195fdce..1b1ef147b6 100644 > --- a/package/utils/usbmode/Makefile > +++ b/package/utils/usbmode/Makefile > @@ -40,8 +40,13 @@ endef > define Build/Prepare >

[LEDE-DEV] [PATCH 3/3] support PantechMode

The behaviour of the usb_modeswitch "Pantech" mode depends on the option value, so we need to propagate this via the json config to the usbmode tool. Signed-off-by: Bjørn Mork <bj...@mork.no> --- convert-modeswitch.pl | 9 + switch.c | 16

[LEDE-DEV] [PATCH 0/3] usb-modeswitch: adding new modes supporting new config format

support, as it complicates stuff quite a bit for little gain AFAICS. But it's there if you want it. This is build tested only. I dont' own any of the affected modems. Bjørn Mork (3): fix support for Option modems support Quanta and Blackberry modes support PantechMode convert-modeswitch.pl

[LEDE-DEV] [PATCH 1/3] fix support for Option modems

USB_ModeSwitch version 2.3.0 introduced "OptionMode". Signed-off-by: Bjørn Mork <bj...@mork.no> --- convert-modeswitch.pl | 1 + switch.c | 16 2 files changed, 17 insertions(+) diff --git a/convert-modeswitch.pl b/convert-modeswitch.pl in

[LEDE-DEV] [PATCH 2/3] support Quanta and Blackberry modes

Quanta mode was introduced in usb_modeswitch 1.2.6 and Blackberry mode in usb_modeswitch 1.2.7 Signed-off-by: Bjørn Mork <bj...@mork.no> --- convert-modeswitch.pl | 2 ++ switch.c | 21 + 2 files changed, 23 insertions(+) diff --git a/convert-modeswitc

Re: [LEDE-DEV] [PATCH] uqmi: fix raw-ip mode for newer lte modems

Koen Vandeputte <koen.vandepu...@ncentric.com> writes: > On 2017-11-27 17:53, Bjørn Mork wrote: >> Koen Vandeputte <koen.vandepu...@ncentric.com> writes: >> >>> @@ -99,6 +99,13 @@ proto_qmi_setup() { >>> uqmi -s -d "$device" --s

Re: [LEDE-DEV] [PATCH] uqmi: fix raw-ip mode for newer lte modems

Koen Vandeputte writes: > @@ -99,6 +99,13 @@ proto_qmi_setup() { > > uqmi -s -d "$device" --set-data-format 802.3 > uqmi -s -d "$device" --wda-set-data-format 802.3 > + dataformat="$(uqmi -s -d "$device" --wda-get-data-format)" > + > + if [

Re: [LEDE-DEV] LEDE version numbers?

Matthias Schiffer writes: > Fixing our revision numbering to include the branch name to make this more > or less unambiguous is the intent of the two patches I linked. The commit > ID should still be included in this revision number (e.g. >

Re: [LEDE-DEV] [PATCH 1/3] Remove ttl==255 restriction for queries

Matthias May writes: > While unfortunate that the actual patch which got merged didn't have the > explanation why the patch was done, if you look > at the mailing list archive you will see that there was a thread discussing > this topic: >

Re: [LEDE-DEV] [PATCH 1/3] Remove ttl==255 restriction for queries

Note that security is the usual (only?) reason one would enforce TTL=255. Requiring TTL=255 is the same as guaranteeing that the packet source is in the same L2 domain. This prevents any direct remote attack. Please do not propose any patches removing such a restriction without at least

Re: [LEDE-DEV] [OpenWrt-Devel] Survey on the usage of OpenWrt/LEDE

Shelly Coen writes: > Hi Everyone, > > The prplWrt Working Group has compiled a survey on the subject of how > OpenWrt/LEDE is used. > > We would really appreciate if you could take some time to complete this short > survey to help give us a valuable oversight of

Re: [LEDE-DEV] [PATCH] scripts: getver.sh: use sha1 as base and drop r* format

Rafał Miłecki writes: > From: Rafał Miłecki > > Counting commits to determine revision number is a wrong idea when there > are branches in a project. This could generate the same revision for > different git commits, e.g.: > > For master branch: >

Re: [LEDE-DEV] [PATCH v2] dropbear: bump to 2017.75

Kevin Darbyshire-Bryant writes: > CVE-2018-9078 https://secure.ucc.asn.au/hg/dropbear/rev/c8114a48837c 2018? Early fix, I guess :-) Bjørn ___ Lede-dev mailing list Lede-dev@lists.infradead.org

Re: [LEDE-DEV] generic: add support for ZTE MF667[rndis] 19d2:1403

Ермошкин А.Ю. writes: > This patch adds support for the ZTE usb modem MF667 in rndis/network card > mode. > > generic/099-usb-cdc_ether-zte-update.patch > generic/774-net-usb-cdc_ether-quirks-for-zte-mf667.patch Any reason why the first patch isn't simply a backport

Re: [LEDE-DEV] Proper way to deal with "dual firmware" ar71xx devices

Mathias Kresin writes: > I had a similar problem with the dual image feature of brnboot in > lantiq. It resulted in the following two patches: > > https://git.lede-project.org/d7438ce3152e2e0dc1678dcb24ca050dbc2733c8 >

[LEDE-DEV] Policies for changes to LEDE stable branches, or LEDE patches in general?

Hello, I note that a recent commit to the lede-17.01 branch has added a few driver patches which have barely hit the mainline kernel: https://github.com/lede-project/source/commit/1ab41265c39354332630bcba0ec704abd2e790f0 This surprised me quite a bit. I would expect any such fixes to go the

Re: [LEDE-DEV] [PATCH 2/2] kernel: kmod-usb-net-pl: Add support for PL-27A1

Roman Spychała writes: > diff --git > a/target/linux/generic/patches-4.4/870-usb-plusb-Add-support-for-PL-27A1.patch > > b/target/linux/generic/patches-4.4/870-usb-plusb-Add-support-for-PL-27A1.patch > new file mode 100644 > index 00..794a861993 > --- /dev/null > +++ >

Re: [LEDE-DEV] Proper way to deal with "dual firmware" ar71xx devices

Alberto Bursi writes: > Can this "bs" partition be manipulated on installation or later? Yes. The only thing preventing that is the default "(ro)" in the LEDE images. But by using mtd-rw it can be manipulated. That's how I fixed my installation. I believe there

[LEDE-DEV] Proper way to deal with "dual firmware" ar71xx devices

Hello, Many devices make use of "dual firmware" configurations, splitting the available flash and allowing two complete and independent installations. This works fine for devices like the Linksys WRT1900AC etc, where the boot loader make sure the kernel command line "root=" parameter matches the

Re: [LEDE-DEV] [PATCH odhcpd] dhcpv6-ia: add option for dhcpv6 privacy address

Eric Luehrsen writes: > It appears many other severs and clients dont implement IA_TA. Its a lost > option. Sure. Very few want this feature. We must however assume that those who do want it will implement it. > It should not break "expectations" as this an central

Re: [LEDE-DEV] [PATCH odhcpd] dhcpv6-ia: add option for dhcpv6 privacy address

Eric Luehrsen writes: > IP6 SLAAC plus privacy is common. DHCPv6 should be able to provide > the same funciton. This way central IT can maintain integrity and > traceability. However, individual machines will not be easily > placed into a pattern over time by external

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Harald Welte <lafo...@gnumonks.org> writes: > On Sun, Jan 08, 2017 at 11:10:20PM +0100, Bjørn Mork wrote: >> Note that there is nothing Quectel here. This is a standard Qualcomm >> platform. The output above comes from the Sierra Wireless EM7455 >> originally delive

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Petr Štetiar <yn...@true.cz> writes: > Bjørn Mork <bj...@mork.no> [2017-01-08 23:10:20]: > >> The output above comes from the Sierra Wireless EM7455 originally delivered >> as part of my Lenovo X1 Carbon, running bog standard firmare. > > Oops. How did

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Petr Štetiar writes: > Adding laforge and zecke to the Cc loop. > > Matti Laakso [2017-01-08 14:39:34]: > > Hi, > >> I'm almost done with checking the connection state using a proto_run_command >> with a simple script running uqmi --get-data-status

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

Matti Laakso writes: > On 12.12.2016 08:52, Petr Štetiar wrote: >> Matti Laakso [2016-12-09 11:35:35]: >> >>> On 09.12.2016 11:27, Petr Štetiar wrote: I knew, that there's only one profile defined, operator has deleted all other

Re: [LEDE-DEV] enhanced 3G support

"Giuseppe Lippolis" writes: > Dear Bjørn, Matti, > >> I don't think it is relevant for you, though. You should continue your >> initial >> idea, creating a "proto" supporting the AT managed cdc_ether based >> modem. > > I add a pull request here: > >

Re: [LEDE-DEV] enhanced 3G support

"Giuseppe Lippolis" writes: > Dear Bjørn, > >> Nice. The "M-MBIM" is a bit confusing, though. This doesn't seem to have >> anything to do with MBIM? >> > I'm just recompiled an image with mbim, ncm support. > > But I don't know if it is the right driver. > If I send

Re: [LEDE-DEV] Fix for uqmi crash when using qmi-via-mbim (--mbim / -m)

Felix Fietkau writes: > On 2016-11-22 14:10, Mogens Lauridsen wrote: >> Seems like a better fix, but it doesn't work. uqmi hangs, so I suspect >> that EM7455 has misunderstood the command. I have removed/replaced the >> ustream_write(..,..,.., true) and after the changes below it

Re: [LEDE-DEV] Fix for uqmi crash when using qmi-via-mbim (--mbim / -m)

Felix Fietkau writes: > On 2016-11-22 12:47, Mogens Lauridsen wrote: >> Hi, >> >> I found a memory overwrite causing a crash when using uqmi and >> qmi-via-mbim such as: >> uqmi -m -d /dev/cdc-wdm0 --get-signal-info >> >> The problem is missing space for mbim header, which is

Re: [LEDE-DEV] ext4 / no space left on device / UML

Bastian Bittorf <b...@npl.de> writes: > * Bjørn Mork <bj...@mork.no> [11.11.2016 14:58]: >> > in fact there is enough space, but not useable. >> >> And "df -i" says? > > this seems not supported by the busybox applet, but > on the host

Re: [LEDE-DEV] ext4 / no space left on device / UML

Bastian Bittorf writes: > i'am using LEDE with target UML and rr2155 and has this problem: > > root@uml:/ df -h > FilesystemSize Used Available Use% Mounted on > /dev/root15.7M 12.3M 3.1M 80% / > tmpfs12.5M320.0K

Re: [LEDE-DEV] 3G support for dwr-512

Cezary Jackiewicz writes: > Dnia 2016-10-31, o godz. 19:17:38 > "Giuseppe Lippolis" napisał(a): > >> Hallo, >> I'm completing the support for the dlink dwr-512 adding the support for 3G. >> In order to enable the 3G modem the following step

Re: [LEDE-DEV] [PATCH 1/2] uqmi: add support for MBIM devices with QMI service

Felix Fietkau writes: > Applied with some cleanups and portability fixes. > I changed the code to use __packed and endian conversion from libubox. Thanks! Sorry about the sloppy implementation. I guess I expected it to come back with a "changes requested" instead of just fixed

[LEDE-DEV] [PATCH] uqmi: fix big endian bugs in MBIM code

All MBIM integer fields are 32bit little endian. So we need to convert then all on big endian systems. Fixes: e69bf24b00d8 ("uqmi: add support for MBIM devices with QMI service") Signed-off-by: Bjørn Mork <bj...@mork.no> --- mbim.c | 6 +++--- 1 file changed, 3 insertions

[LEDE-DEV] [PATCH 0/2] uqmi: "FCC Auth" and "QMI-in-MBIM" support

cation" support. There are no TLVs associated with this request, so it is pretty simple. Bjørn Mork (2): uqmi: add support for MBIM devices with QMI service dms: add "Set FCC Authentication" request CMakeLists.txt| 2 +- commands-dms.c| 8 ++

[LEDE-DEV] [PATCH 2/2] dms: add "Set FCC Authentication" request

thentication feature enabled: $ umbim -d /dev/cdc-wdm0 -n radio hwradiostate: on swradiostate: off $ uqmi -m -d /dev/cdc-wdm0 --fcc-auth $ umbim -d /dev/cdc-wdm0 -t 2 radio hwradiostate: on swradiostate: on Signed-off-by: Bjørn Mork <bj...@mork.no> --- commands-dms.c|

[LEDE-DEV] [PATCH 1/2] uqmi: add support for MBIM devices with QMI service

$ umbim -d /dev/cdc-wdm0 -t 2 caps devicetype: 0003 - remote cellularclass: 0001 voiceclass: 0001 - no-voice simclass: 0002 dataclass: 003C smscaps: 0003 controlcaps: 0001 maxsessions: 0008 deviceid: 0145820007xxxxx firmwareinfo: SWI9X30C_02.08.02.00 hardwareinfo: EM74

Re: [LEDE-DEV] Add info about git URLs in Lede Git Web

Alexey Brodkin writes: > Hello, > > I think it would be quite convenient to add info about URLs > that could be used for accessing Lede repos via git. > > In OpenWRT Git Web we had something like that: > --->8--- > URL  

Re: [LEDE-DEV] [OpenWrt-Devel] OpenWrt / LEDE

Zoltan HERPAI writes: >> On 05/24/2016 10:31 PM, Hauke Mehrtens wrote: >> >> This is my personal opinion and this was not somehow internally planned >> with other LEDE people. > > If I start a discussion about my employer-related topics along a beer > with a couple friends,

Re: [LEDE-DEV] [PATCH] scripts/download.pl: Use CDN for kernel downloads

Arjen de Korte writes: > Since GitHub apparently also uses Fastly as CDN provider, building on > a machine with IPv6 only connectivity is going to be difficult anyway. > Using both won't hurt, but if you're not able to connect to an IPv4 > server for the kernel sources,

Re: [LEDE-DEV] WRT1900ACS Testing

Dheeran Senthilvel writes: >> Its gonna take a while before either Linksys just releases a proper >> working drivers (or) just releases the code under GPL for upstream >> kernel-development (Just like what happened for raspberrypi). This is wrong. The mwlwifi driver is

Re: [LEDE-DEV] copyright questions

Hauke Mehrtens <ha...@hauke-m.de> writes: > On 05/09/2016 10:19 PM, Bjørn Mork wrote: > >> How do you ensure that they use the code only like you intended after you >> donated it? > This copyright notice is useless. The copyright will stay at the > individual author