[LEDE-DEV] kernel: add test MTD driver package
Allows to test MTD driver using RAM Signed-off-by: Hans Dedecker --- package/kernel/linux/modules/other.mk | 16 1 file changed, 16 insertions(+) diff --git a/package/kernel/linux/modules/other.mk b/package/kernel/linux/modules/other.mk index 973e4f3..3e22909 100644 --- a/package/kernel/linux/modules/other.mk +++ b/package/kernel/linux/modules/other.mk @@ -619,6 +619,22 @@ endef $(eval $(call KernelPackage,mtdoops)) +define KernelPackage/mtdram + SUBMENU:=$(OTHER_MENU) + TITLE:=Test MTD driver using RAM + KCONFIG:=CONFIG_MTD_MTDRAM \ +CONFIG_MTDRAM_TOTAL_SIZE=4096 \ +CONFIG_MTDRAM_ERASE_SIZE=128 + FILES:=$(LINUX_DIR)/drivers/mtd/devices/mtdram.ko +endef + +define KernelPackage/mtdram/description + Test MTD driver using RAM +endef + +$(eval $(call KernelPackage,mtdram)) + + define KernelPackage/serial-8250 SUBMENU:=$(OTHER_MENU) TITLE:=8250 UARTs -- 1.9.1 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] build: disable BUILD_PATENTED by default
> On 25 Jan 2018, at 02:42, Yousong Zhou wrote: > > Signed-off-by: Yousong Zhou > --- > config/Config-build.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/config/Config-build.in b/config/Config-build.in > index f9987fc..7ec7653 100644 > --- a/config/Config-build.in > +++ b/config/Config-build.in > @@ -41,7 +41,7 @@ menu "Global build settings" > default n > > config BUILD_PATENTED > - default y > + default n > bool "Compile with support for patented functionality" > help > When this option is disabled, software which provides > patented functionality > -- > 1.8.3.1 > > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev The commit messages lacks a “Why we need this change”. Cheers, Kevin D-B 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A signature.asc Description: Message signed with OpenPGP ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] build: disable BUILD_PATENTED by default
On 25 January 2018 at 19:30, Kevin Darbyshire-Bryant wrote: > > >> On 25 Jan 2018, at 02:42, Yousong Zhou wrote: >> >> Signed-off-by: Yousong Zhou >> --- >> config/Config-build.in | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/config/Config-build.in b/config/Config-build.in >> index f9987fc..7ec7653 100644 >> --- a/config/Config-build.in >> +++ b/config/Config-build.in >> @@ -41,7 +41,7 @@ menu "Global build settings" >> default n >> >> config BUILD_PATENTED >> - default y >> + default n >> bool "Compile with support for patented functionality" >> help >> When this option is disabled, software which provides >> patented functionality >> -- >> 1.8.3.1 >> >> >> ___ >> Lede-dev mailing list >> Lede-dev@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/lede-dev > > The commit messages lacks a “Why we need this change”. > > > Cheers, > > Kevin D-B Sorry, I thought the reason was very very apparent and the patch was posted here mainly to serve as a prior notification to mitigate possible surprise... That said, the reason behind the change is that I think we are not supposed to promote usage of and redistribute binaries of patented code/technologies, for legal considerations I only vaguely "groked". This seems to be the established practice with ffmpeg, flashplayer, video card drivers, etc. with other linux distributions Turning off BUILD_PATENTED by default is the first safe step. yousong ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] build: disable BUILD_PATENTED by default
> On 25 Jan 2018, at 12:58, Yousong Zhou wrote: > > On 25 January 2018 at 19:30, Kevin Darbyshire-Bryant > wrote: >> >> >>> On 25 Jan 2018, at 02:42, Yousong Zhou wrote: >>> >>> Signed-off-by: Yousong Zhou >>> --- >>> config/Config-build.in | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/config/Config-build.in b/config/Config-build.in >>> index f9987fc..7ec7653 100644 >>> --- a/config/Config-build.in >>> +++ b/config/Config-build.in >>> @@ -41,7 +41,7 @@ menu "Global build settings" >>> default n >>> >>> config BUILD_PATENTED >>> - default y >>> + default n >>> bool "Compile with support for patented functionality" >>> help >>>When this option is disabled, software which provides >>> patented functionality >>> -- >>> 1.8.3.1 >>> >>> >>> ___ >>> Lede-dev mailing list >>> Lede-dev@lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/lede-dev >> >> The commit messages lacks a “Why we need this change”. >> >> >> Cheers, >> >> Kevin D-B > > Sorry, I thought the reason was very very apparent and the patch was > posted here mainly to serve as a prior notification to mitigate > possible surprise... > > That said, the reason behind the change is that I think we are not > supposed to promote usage of and redistribute binaries of patented > code/technologies, for legal considerations I only vaguely "groked". > This seems to be the established practice with ffmpeg, flashplayer, > video card drivers, etc. with other linux distributions > > Turning off BUILD_PATENTED by default is the first safe step. And that ^^ is what should be in the commit message, ‘cos I didn’t know. We’ll be a to see what the commit did, and why we chose to do it. Wunderbar :-) Cheers, Kevin D-B 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A signature.asc Description: Message signed with OpenPGP ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] kernel: add test MTD driver package
On 01/25/2018 02:46 AM, Hans Dedecker wrote: > Allows to test MTD driver using RAM There appears to be a desire to get rid of those in-kernel MTD tests and move exclusively towards user-space based MTD tests: http://lists.infradead.org/pipermail/linux-mtd/2018-January/078636.html even if the objective is to run from RAM, you could still achieve that by using an initramfs + user-space MTD tests, would that work? -- Florian ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH v1] wireguard: bump to 20180118
Bump to latest wireguard release snapshot: 9a93a3d version: bump snapshot 7bc0579 contrib: keygen-html: update curve25519 implementation ffc13a3 tools: import new curve25519 implementations 0ae7356 curve25519: wire up new impls and remove donna f90e36b curve25519: resolve symbol clash between fe types 505bc05 curve25519: import 64-bit hacl-star implementation 8c02050 curve25519: import 32-bit fiat-crypto implementation 96157fd curve25519: modularize implementation 4830fc7 poly1305: remove indirect calls bfd1a5e tools: plug memleak in config error path 09bf49b external-tests: add python implementation b4d5801 wg-quick: ifnames have max len of 15 6fcd86c socket: check for null socket before fishing out sport ddb8270 global: year bump 399d766 receive: treat packet checking as irrelevant for timers No patch refresh required. Compile-tested-for: ar71xx Run-tested-on: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant --- package/network/services/wireguard/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package/network/services/wireguard/Makefile b/package/network/services/wireguard/Makefile index 0cb17e9cc1..0cc850be29 100644 --- a/package/network/services/wireguard/Makefile +++ b/package/network/services/wireguard/Makefile @@ -11,12 +11,12 @@ include $(INCLUDE_DIR)/kernel.mk PKG_NAME:=wireguard -PKG_VERSION:=0.0.20171221 +PKG_VERSION:=0.0.20180118 PKG_RELEASE:=1 PKG_SOURCE:=WireGuard-$(PKG_VERSION).tar.xz PKG_SOURCE_URL:=https://git.zx2c4.com/WireGuard/snapshot/ -PKG_HASH:=2b97697e9b271ba8836a04120a287b824648124f21d5309170ec51c1f86ac5ed +PKG_HASH:=463f3b402deb66b7ceac8df2d50944f32683933356455d6c1c7453926db3a8a3 PKG_LICENSE:=GPL-2.0 Apache-2.0 PKG_LICENSE_FILES:=COPYING -- 2.14.3 (Apple Git-98) ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] [PATCH uclient] uclient-fetch: use package name pattern in message for missing SSL library
When faced with this error message, I did not directly know what
package(s) to install. I first grepped the package list for packages
named libustream-ssl... found nothing, and finally realized, that here
only the library name was mentioned.
But when we mention the certificate packages, why not also directly
mention the SSL/TLS packages with a pattern. That will save one step
next time when stumbling here - at least for me ;-)
Signed-off-by: Michael Heimpold
---
uclient-fetch.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/uclient-fetch.c b/uclient-fetch.c
index 2e553a0..6961d94 100644
--- a/uclient-fetch.c
+++ b/uclient-fetch.c
@@ -494,7 +494,7 @@ static int no_ssl(const char *progname)
{
fprintf(stderr,
"%s: SSL support not available, please install one of the "
- "libustream-ssl-* libraries as well as the ca-bundle and "
+ "libustream-.*[ssl|tls] packages as well as the ca-bundle and "
"ca-certificates packages.\n",
progname);
--
2.7.4
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] procd mount wrong amount fo ram!
https://forum.lede-project.org/t/no-space-left-in-tmp/11000/14 Here you can find details about problem i find. In short. My setup have zram-swap and procd set to mount /tmp with zram... This result in /tmp mounted with zram with only 11 mb of my 512 (even after i remove swap script...) If someone can explain me why... i think this is a bug and this broke sysupgrade, as it needs to upload the image in tmp, a 14 mb image to a 11 mb dir... Also sysupgrade from luci should detect that the upload was not complete and not say that the image provided is not valid... ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH 1/2] procd/base-files: move init.d locking to rc.common
On 2018-01-18 10:30, John Crispin wrote:
On 18/01/18 09:14, John Crispin wrote:
rather than using flock for procd enabled services we add locking to
the
rc.common code.
Signed-off-by: John Crispin
---
package/base-files/files/etc/rc.common | 6 ++
package/system/procd/files/procd.sh| 15 ---
2 files changed, 6 insertions(+), 15 deletions(-)
diff --git a/package/base-files/files/etc/rc.common
b/package/base-files/files/etc/rc.common
index 3e237170b4..180ee83acd 100755
--- a/package/base-files/files/etc/rc.common
+++ b/package/base-files/files/etc/rc.common
@@ -148,4 +148,10 @@ ${INIT_TRACE:+set -x}
ALL_COMMANDS="start stop reload restart boot shutdown enable
disable enabled depends ${EXTRA_COMMANDS}"
list_contains ALL_COMMANDS "$action" || action=help
+
+local basescript=$(readlink "$initscript")
+local service_name="$(basename ${basescript:-$initscript})"
+
+lock -w /var/lock/init.d_${service_name}.lock
the -w is wrong here and needs to be removed
Hi John,
the lock command here is OpenWrt custom patch, implementing flock (in a
different way).
Maybe we can use busybox flock and migrate all other scripts to flock?
Can it do something what flock cannot?
I have done this already in one of my branches but didn't do testing so
didn't submit.
Regards,
Roman
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
[LEDE-DEV] Debugging steps for FS#1246 - Ubnt Nanostation Loco M2 - WDS link drops out after a few hours
I opened a ticket in late Dec but haven't heard anything. Does anyone have any suggestions on where to go next to troubleshoot this issue? My wife is getting very tired of the internet randomly dropping out on our WDS link. Ticket: https://bugs.openwrt.org/index.php?do=details&task_id=1246 Cliffs: I have a pair of Nanostation Loco M2 access points setup as a wireless bridge over a ~1300 foot (~400M) line of sight link. One is setup as a WDS AP and the other is setup as a WDS Client, after a few hours (4-12 hours?) the link drops out but still says that is connected (if I go to status it shows the other AP as connected but I cannot ping or do anything else across the link). If I restart the wireless service on the client device, the connection comes right back and all is well for a 4-12 hours. I have had LEDE 17.01.3, 17.0.4 and OpenWrt SNAPSHOT r5499-575178e / LuCI Master (git-17.343.27587-8e6b1a6) and now OpenWrt SNAPSHOT r5902-9c2ac19b03 / LuCI Master (git-18.021.64448-4dddecf) installed at both ends with the same results. Anyone have any suggestions on where to look next to figure out why this is happening? Thanks Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] build: disable BUILD_PATENTED by default
On Thu, Jan 25, 2018 at 5:03 AM, Kevin Darbyshire-Bryant wrote: > > >> On 25 Jan 2018, at 12:58, Yousong Zhou wrote: >> >> On 25 January 2018 at 19:30, Kevin Darbyshire-Bryant >> wrote: >>> >>> On 25 Jan 2018, at 02:42, Yousong Zhou wrote: Signed-off-by: Yousong Zhou --- config/Config-build.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/Config-build.in b/config/Config-build.in index f9987fc..7ec7653 100644 --- a/config/Config-build.in +++ b/config/Config-build.in @@ -41,7 +41,7 @@ menu "Global build settings" default n config BUILD_PATENTED - default y + default n bool "Compile with support for patented functionality" help When this option is disabled, software which provides patented functionality -- 1.8.3.1 ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev >>> >>> The commit messages lacks a “Why we need this change”. >>> >>> >>> Cheers, >>> >>> Kevin D-B >> >> Sorry, I thought the reason was very very apparent and the patch was >> posted here mainly to serve as a prior notification to mitigate >> possible surprise... >> >> That said, the reason behind the change is that I think we are not >> supposed to promote usage of and redistribute binaries of patented >> code/technologies, for legal considerations I only vaguely "groked". >> This seems to be the established practice with ffmpeg, flashplayer, >> video card drivers, etc. with other linux distributions >> >> Turning off BUILD_PATENTED by default is the first safe step. > The second step of course would be to remove stuff like mp2 and mp3 from the purview of BUILD_PATENTED as mp[23] patents have both expired. > And that ^^ is what should be in the commit message, ‘cos I didn’t know. > We’ll be a to see what the commit did, and why we chose to do it. Wunderbar > :-) > > > > Cheers, > > Kevin D-B > > 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A > > > ___ > 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] build: disable BUILD_PATENTED by default
On 26 January 2018 at 10:23, Rosen Penev wrote: > On Thu, Jan 25, 2018 at 5:03 AM, Kevin Darbyshire-Bryant > wrote: >> >> >>> On 25 Jan 2018, at 12:58, Yousong Zhou wrote: >>> >>> On 25 January 2018 at 19:30, Kevin Darbyshire-Bryant >>> wrote: > On 25 Jan 2018, at 02:42, Yousong Zhou wrote: > > Signed-off-by: Yousong Zhou > --- > config/Config-build.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/config/Config-build.in b/config/Config-build.in > index f9987fc..7ec7653 100644 > --- a/config/Config-build.in > +++ b/config/Config-build.in > @@ -41,7 +41,7 @@ menu "Global build settings" > default n > > config BUILD_PATENTED > - default y > + default n > bool "Compile with support for patented functionality" > help >When this option is disabled, software which provides > patented functionality > -- > 1.8.3.1 > > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev The commit messages lacks a “Why we need this change”. Cheers, Kevin D-B >>> >>> Sorry, I thought the reason was very very apparent and the patch was >>> posted here mainly to serve as a prior notification to mitigate >>> possible surprise... >>> >>> That said, the reason behind the change is that I think we are not >>> supposed to promote usage of and redistribute binaries of patented >>> code/technologies, for legal considerations I only vaguely "groked". >>> This seems to be the established practice with ffmpeg, flashplayer, >>> video card drivers, etc. with other linux distributions >>> >>> Turning off BUILD_PATENTED by default is the first safe step. >> > The second step of course would be to remove stuff like mp2 and mp3 > from the purview of BUILD_PATENTED as mp[23] patents have both > expired. Yesterday I checked, the mp3lame or names like that did not have the tag. Feel free to open a pull request if it's not the case. yousong ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] procd mount wrong amount fo ram!
Hi, On Friday 26 January 2018 04:18 AM, Ansuel Smith wrote: https://forum.lede-project.org/t/no-space-left-in-tmp/11000/14 Here you can find details about problem i find. In short. My setup have zram-swap and procd set to mount /tmp with zram... This result in /tmp mounted with zram with only 11 mb of my 512 (even after i remove swap script...) If someone can explain me why... i think this is a bug and this broke sysupgrade, as it needs to upload the image in tmp, a 14 mb image to a 11 mb dir... Also sysupgrade from luci should detect that the upload was not complete and not say that the image provided is not valid... I did this while compiling images and left with just around same amount of /tmp even when I had 2 GB of RAM on board. Once I disabled the option "procd uses RAM to mount /tmp" and only enabled the "ZRAM Swap", it was back to normal. I am not sure why it creates such a small zram device for /tmp when swap device is around 50% of RAM. Regards, Nishant ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
