Am Sonntag, 18. Oktober 2020, 18:59:19 CET schrieb Sven Roederer:
> > > fail ---
> > > root@gib-mir-einen-namen:~# cat /lib/upgrade/freifunk-berlin_freeup-
> > > ram.sh
> > > ffberlin_freeup_ram() {
> > >
> > >
Am Sonntag, 22. November 2020, 18:07:05 CET schrieb Hannu Nyman:
> Adrian Schmutzler wrote at Fri Oct 16 19:15:38 EDT 2020:
> > Fortunately, and I don't fully understand why, we were able to drive this
>
> to effectively zero by simply running
>
> > echo 3 > /proc/sys/vm/drop_caches
> > direct
fixes "file no found" error on stripped down images, caused by prod.sh:43.
Signed-off-by: Sven Roederer
---
package/system/procd/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/system/procd/Makefile b/package/system/procd/Makefile
index
Am Dienstag, 24. November 2020, 07:39:48 CET schrieb Hannu Nyman:
> Flush kernel memory caches during sysupgrade in order
> to mitigate the impact from memory consumption spikes
> in low-RAM devices.
>
> This may help to prevent sysupgrade causing a reboot
> before the actual flashing starts.
>
>
Currently 8MB flash / 32MB RAM devices are fully supported in OpenWrt, as they
work quite well for basic usage (including full LuCI).
On some projects with advanced features (e.g. Freifunk) the lack of RAM turns
them into unstable devices. Mostly caused by several OOM problems per day.
This serie
From: adminuser
---
target/linux/ath79/tiny/config-default | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ath79/tiny/config-default
b/target/linux/ath79/tiny/config-default
index 5dcdf30af4..f686d284f6 100644
--- a/target/linux/ath79/tiny/config-default
+++ b/target/linux/ath7
From: adminuser
this includes:
* CONFIG_AIO
* CONFIG_HAVE_IDE
* CONFIG_NVMEM
* CONFIG_DEBUG_FS
* CONFIG_DEBUG_KERNEL
* CONFIG_HAVE_DEBUG_KMEMLEAK
* CONFIG_HAVE_DEBUG_STACKOVERFLOW
* CONFIG_ISDN
* CONFIG_SND_DRIVERS
* CONFIG_STAGING
* CONFIG_HAVE_KVM
* CONFIG_VIRTIO_MENU
---
target/linux/ath79/ti
WR1043v1; WR842v1/v2; WR710
Signed-off-by: Sven Roederer
---
target/linux/ath79/image/Makefile | 1 +
target/linux/ath79/image/common-tp-link.mk| 2 +
target/linux/ath79/image/tiny-tp-link.mk | 66 +
target/linux/ath79/image/tiny-ubnt.mk | 132
From: adminuser
---
target/linux/ath79/image/tiny-tp-link.mk | 4
target/linux/ath79/image/tiny-ubnt.mk| 2 --
target/linux/ath79/image/tiny.mk | 1 -
target/linux/ath79/tiny/config-default | 5 +++--
4 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/target/linux/
on this low-end hardware it's nearly impossible to add external drives, so
there seems no need for this partition-type.
this will safe some kernel-size
---
target/linux/ath79/tiny/config-default | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/ath79/tiny/config-default
b/target/li
Am Sonntag, 6. Dezember 2020, 13:59:52 CET schrieb Adrian Schmutzler:
> > -Original Message-
> > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> > On Behalf Of Sven Roederer
> > Sent: Sonntag, 6. Dezember 2020 02:07
> > To: openwrt-devel
Am Sonntag, 6. Dezember 2020, 11:03:56 CET schrieb Baptiste Jonglez:
> Hi,
>
> On 06-12-20, Sven Roederer wrote:
> > Currently 8MB flash / 32MB RAM devices are fully supported in OpenWrt, as
> > they work quite well for basic usage (including full LuCI).
> > On
Am Sonntag, 6. Dezember 2020, 14:05:15 CET schrieb Adrian Schmutzler:
>
> Apart from that, I don't see disabling basic features like USB on a device
> with USB ports as an option for pure OpenWrt.
>
Disabling USB was just a pragmatic solution, as without SCSI-support,
partition-handling and USB
Am Freitag, 2. Oktober 2020, 21:34:30 CET schrieb Sven Roederer:
> Am Sonntag, 19. April 2020, 11:32:03 CEST schrieb Bjørn Mork:
> > Sven Roederer writes:
> > > I was just building a master-branch for x86-generic and got following
> > > error:
> > >
> >
Am Mittwoch, 30. Dezember 2020, 05:23:41 CET schrieb Paul Spooren:
> Multiple prereq checks are only required within the build system but not
> for the ImageBuilder. These checks are excluded by using ifndef IB.
>
> This commit merges the three ifndef IB blocks together.
Happy new year to all.
W
Am Donnerstag, 31. Dezember 2020, 20:35:47 CET schrieb Paul Spooren:
>
> Merged and backported.
>
I think 4f3806364011aa3aef26fcab2e7b71837a777bcc needs to be backported too,
to make it work.
Sven
___
openwrt-devel mailing list
openwrt-devel@lis
Hi,
based on the recent changes to the tools required when using the imagebuilder,
I wonder If there are more tools that can be excluded for this case.
Candidates I see here are:
* patch
* unzip
* bzip2
* Perl 5.x (including Data::Dumper, Thread::Queue)
* Python
* Git
* rsync
This list is just g
Hi,
based on Pauls recent idea "rules: add findrev function from LuCI" of reusing
some LuCI-code, I'd like to point to a github-PR with a related suggestion:
https://github.com/openwrt/luci/pull/2637
As noted in the PR-message, it splits the current luci.mk file into two files.
One for common
When saving the list of installed pkgs, also store the status of the
system services. The list is created in the etc/backup folder also
and formated as:
/etc/init.d/ {enable|disable}
This way it can be sourced after sysupgrade, to restore the previous
state.
Signed-off-by: Sven Roederer
Am Samstag, 9. Januar 2021, 12:28:31 CET schrieb Stijn Segers:
> > @@ -228,6 +229,7 @@ do_save_conffiles() {
> >
> > if [ "$SAVE_INSTALLED_PKGS" -eq 1 ]; then
> > echo "${INSTALLED_PACKAGES}" >> "$CONFFILES"
> > + echo "${SERVICE_STATUS}" >> "$CONFFILES"
> > mkdir -p "$ETCBACKUP_DIR"
Am Sonntag, 10. Januar 2021, 09:47:27 CET schrieb Andre Heider:
> > Same. I would personally like this as default sysupgrade procedure, as
> > that's what makes most sense imho.
> > If I have disabled a service it makes sense that after a firmware
> > upgrade it remains disabled.
>
> Seconded.
>
as:
/etc/init.d/ {enable|disable}
When upgrading with an generic image all system services are enabled by
default which is usually not expected and can cause trouble.
The default behavior can be flipped with the "-s" option of sysupgrade.
Signed-off-by: Sven Roederer
---
This v2 in
Am Montag, 11. Januar 2021, 03:59:51 CET schrieb Alberto Bursi:
> On 10/01/21 22:40, Sven Roederer wrote:
> > Am Sonntag, 10. Januar 2021, 09:47:27 CET schrieb Andre Heider:
> >>> Same. I would personally like this as default sysupgrade procedure, as
> >>>
Am Dienstag, 12. Januar 2021, 19:56:54 CET schrieb Hannu Nyman:
> Martin Schiller kirjoitti 12.1.2021 klo 9.25:
> > On 2021-01-11 23:07, Sven Roederer wrote:
> >> Restore the status of the system-services after sysupgrade.
> >> Create a file with the status of all known
Am Dienstag, 12. Januar 2021, 13:01:45 CET schrieb Adrian Schmutzler:
> > Hello,
> > You don't have to run such complicated script. Just restore /etc/rc.d/
> > directory after upgrade.
>
> Well, that depends on how we want to deal with new services. If I upgrade
> from 19.07.5 to master, I'd expec
Ben,
seems to me, that at least "firmware-5-ct-full-community-12.bin-lede.013" is
still not recovered. File is there, but contains only 0x00.
This seems to cause my fresh build of 19.07.5 to fail.
+ curl -f --connect-timeout 20 --retry 5 --location --insecure https://
www.candelatech.com/downlo
Happy easter all and thanks for branching 21.02.
Holidays and lockdown give me some time to keep-up with OpenWrt. During this I
found that 21.02 is still missing the kernel-CONFIG for RTC_DRV_JZ4740
Can someone cherry-pick 55ed4bf6d7bf80b705d015c3b73f772db485ba9c into 21.02 to
fix?
Best Sven
ion denied
Makefile:116: recipe for target '_call_image' failed
make[2]: *** [_call_image] Error 1
Makefile:241: recipe for target 'image' failed
make[1]: *** [image] Error 2
Signed-off-by: Sven Roederer
---
target/imagebuilder/Makefile | 2 ++
1 file changed, 2 insertions(+)
di
Hi,
since some days my master builds failing for ath79-generic. I was able to
narrow it to running "mkmylofw for compex_wpj344-16m".
The tool runs till the drive is full, currently my "compex_wpj344-16m-
squashfs-cpximg-6a08.bin.new" is 161GB and growing ...
Has anyone else seen this?
I'll check
Philip,
I already read about deprecating ipsec tool someyears ago and started to use
swanctl. I hacked some scripts together on one of my nodes to not use ipsec-
cli. (Sadly I stopped at some point, without making it useable outside of my
"lab" to pubish / share.)
By the time I became a fan of s
Hi Rafał,
thanks for picking this up soo quickly.
Am Dienstag, 13. April 2021, 14:02:10 CEST schrieb Rafał Miłecki:
> > The original code comes from Florian from the 2007 commit 7b564bfdcbef
> > ("Fix potential unligned access with MyLoader based devices, thanks
> > Juhos")
> >
> > https://git.o
Am Sonntag, 21. Februar 2021, 20:13:40 CEST schrieb Petr Štetiar:
Hi,
>
> > I have submitted two PR's to remove the freifunk feed from master and
> > openwrt-21.02.
>
> thank you for the heads up, I'm just wondering why we should left
> openwrt-19.07[1] behind?
>
> 1. https://git.openwrt.org/2a
Hi,
Am Dienstag, 16. Februar 2021, 17:17:17 CEST schrieb Petr Štetiar:
>
> > The meson build system bumped their python requirement to 3.6 for the
> > 0.57.0 release. This patch ensures that OpenWrt can update meson while
> > still relying on the host python.
>
> Current buildbot images are bas
Am Samstag, 17. April 2021, 16:45:01 CEST schrieb Sven Roederer:
> On my Ubuntu 16.04 based build-system I also have build-failures for meson
> using Python3.5.
Correction: it's a 18.04 LTS ...
Sven
___
openwrt-devel mailing list
op
The hardware of the v3 is identical to the v2.
Based-on-patch-by: nbd (b9d5ee8)
- Backport to CC
- add TPL-WR1043v3 to list of supported boards in config-menu
- was tested for all 3 boards by freifunk-community Berlin
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile
Hi,
you are right regarding the old-style vs. new-style. I have seen this, but
forgot about. I'll fix this with a new patch.
The Kconfig-stuff is indeed only cosmetic, but as is will not break anything I
think it's ok. There might be no general rule if all models should be listed
or just some
.patch
- also update Kconfig for this board
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 3 ++-
target/linux/ar71xx/patches-3.18/610-MIPS-ath79-openwrt-machines.patch | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a
potential to break other projects.
- based on
https://github.com/freifunk-gluon/gluon/blob/master/patches/openwrt/0037-ar71xx-add-support-for-TP-Link-TL-WR1043ND-v3.patch
- also update Kconfig for this board
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile
Am Tuesday 09 February 2016, 14:53:30 schrieb John Crispin:
> NAK, please use the new image building infra for trunk and the old one
> for the CC backport
>
I already sent an updated version of this patch on "08 Feb 2016 15:28:17
+0100" ("[OpenWrt-Devel] [PATCH v2] [CC] ar71xx: backport support
Hi,
Am Tuesday 09 February 2016, 14:53:30 schrieben Sie:
> > The hardware of the v3 is identical to the v2.
> >
> > - adds support via old-style-definition. So less code is changed and there
> > is less potential to break other projects
> NAK, please use the new image building infra for trunk and
These patches change the image-name of some TPlink-routers.
Esp. for the TPlink WR841N + WR841ND some users are confused by the fact
that some images have "nd"-names and others "n"-names only.
In addition this also corrects a missed "D" on WA701 and a "-" fo
- it seems there was never a 701N-model build
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index 0ef972a..1bd4559 100644
--- a
- insert missing "-" between model and version
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index 1bd4559..cb11104 10
ffix in IRC with jow and Borromini
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index a770041..0ef972a 100644
--- a
- it seems there was never a 701N-model build
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index 0ef972a..1bd4559 100644
--- a
- insert missing "-" to separate model and version
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index 1bd4559..cb11
r
WA730RE.
v2: fixes the subject-prefix as per blogic
Sven Roederer (3):
[ar71xx] matchup of TPlink WR841N(D)-names
- some of these models have a "N"-suffix, others have (ND)-suffix,
but the boards are the same
- only difference is the detachable antenna on "D"-
ffix in IRC with jow and Borromini
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index a770041..0ef972a 100644
--- a
Am Wednesday 17 February 2016, 07:49:37 schrieb John Crispin:
> this patch seems incomplete. after applying it there are still lots of
> images with n(d) behind them.
One one side, there are many models around which are "N" or "ND" exclusively.
So some of these suffixes are correct. One teh othe
Hi,
Am Tuesday 09 February 2016, 14:53:30 schrieben Sie:
> > The hardware of the v3 is identical to the v2.
> >
> > - adds support via old-style-definition. So less code is changed and there
> > is less potential to break other projects
> NAK, please use the new image building infra for trunk and
Am Thursday 25 February 2016, 09:07:22 schrieben Sie:
>
> i still dont like the fact that this is only addressing some routers and
> not all. i am also pretty sure that the wiki was not updated as per my
> request to the last series.
>
I added a note on the page of the WR-841, informing on the p
Am Thursday 25 February 2016, 09:07:22 schrieb John Crispin:
> i am also pretty sure that the wiki was not updated as per my
> request to the last series.
Hi, I'm back now after some hardware outage ...
Thanks for applying the patches; I just finished updating the Wiki.
What are the chances to
;a=commit;h=783756e3096a417565d58d78e082a29db10738d4'
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index
;a=commit;h=783756e3096a417565d58d78e082a29db10738d4'
Signed-off-by: Sven Roederer
---
target/linux/ar71xx/image/Makefile | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/target/linux/ar71xx/image/Makefile
b/target/linux/ar71xx/image/Makefile
index
Am Friday 11 March 2016, 00:20:15 schrieb Sven Roederer:
> This patch changes the image-name of some TPlink-routers.
> Esp. for the TPlink WR841N + WR841ND some users are confused by the fact
> that some images have "nd"-names and others "n"-names only.
> In additio
Hi,
for me it helped to go this way, to bring a NSM5 (xm) one member of our
Freifunk-community bricked :
- UBoot was "1.1.4.2-s956 (Jun 10 2015 - 10:54:50)" and did not accept
snapshot-images
- downgrading UBoot to "1.1.4.2-s594 (Dec 5 2012 - 15:23:07)" by flashing
original xm5.5 image
- on ub
Am Monday 25 April 2016, 09:06:38 schrieb John Crispin:
> On 25/04/2016 08:54, Bastian Bittorf wrote:
> > * John Crispin [25.04.2016 07:39]:
> >>> The changed image name breaks compatibility for derived projects and
> >>> that's something which should only happen if there is a really good
> >>> re
- this covers the WT3020-routers
- so this target can be even used in Imagebuilder
Signed-off-by: Sven Roederer
---
target/linux/ramips/mt7620/profiles/nexx.mk | 17 +
1 file changed, 17 insertions(+)
create mode 100644 target/linux/ramips/mt7620/profiles/nexx.mk
diff --git a
- update mtd-utils to 1.5.2 (git a494d30ab1ae40cb7665680cadf5af3ca3830a73)
- remove patches that came upstream
- fixes build from scratch as of broken patches
Signed-off-by: Sven Roederer
---
diff --git a/tools/mtd-utils/Makefile b/tools/mtd-utils/Makefile
index b4c9c66..660f06d 100644
--- a
- update mtd-utils to 1.5.2 (git a494d30ab1ae40cb7665680cadf5af3ca3830a73)
- remove patches that went upstream
- fixes build from scratch as of broken patches
just had a crash-course to git send-email
Signed-off-by: Sven Roederer
---
tools/mtd-utils/Makefile
Am Sonntag, 15. November 2015, 22:59:48 schrieben Sie:
>
> Why are you using some random commit and not the commit of the 1.5.2 tag?
>
it was the most recent commit this moment and the messages seems to give only
improvements
> When I build it I get this warning, can you fix it?
>
got also th
The luci and freifunk feed having a common Makefile included by the
individual packages. Currently a change to this file will be ignored
when running "scripts/feeds update".
Add a check for a Makefile "feed.mk" in the root of a feed and include
this to the dependencies.
The luci and freifunk feed having a common Makefile included by the
individual packages. Currently a change to this file will be ignored
when running "scripts/feeds update".
When we are updating for a feed, add a dependency for all .mk files
in the root of it.
Signed-off-by: Sve
Am Freitag, 8. März 2019, 07:28:21 CET schrieb Jo-Philipp Wich:
> Hi,
>
> tbh I don't really like the approach of arbitrarily defining "feed.mk"
> to be a change source. Can we extend this to take all toplevel *.mk
> files into consideration? I think this falls more in line with what
> people woul
Am Mittwoch, 26. Juni 2019, 12:02:23 CEST schrieb Luochongjun:
> This patch supports gl-ar750, which was previously supported by ar71xx.
>
> Specification:
> - SOC: QCA9531 (650MHz)
> - Flash: 16 MiB (W25Q128FVSG)
> - RAM: 128 MiB DDR2
> - Ethernet: 10/100: 2xLAN + 10/100: 1xWAN
> - Wireless: 2.4G
me time for our freifunk-firmware already.
Sven
Am Samstag, 9. März 2019, 15:00:15 CEST schrieb Sven Roederer:
> The luci and freifunk feed having a common Makefile included by the
> individual packages. Currently a change to this file will be ignored
> when running "scripts/feeds up
uot;, "zip ", zipfsname, rootfs.file_name);
int ret = system(zipper);
Check that the zip command is installed on the host.
Signed-off-by: Sven Roederer
---
include/prereq-build.mk | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/prereq-build.mk b/include/prereq-build
Am Donnerstag, 11. Oktober 2018, 19:34:35 CEST schrieb Sven Roederer:
> tools/firmware-utils/src/mksercommfw.c depends on the zip-tool to generate
> the firmwareimage.
Thinking of this again, I wonder if it would be the proper way to build the
zip-tool as y host-command like we do for tar
Hi all,
I had some time to look into this and had a test on my board.
Am Sonntag, 28. Oktober 2018, 10:29:40 CET schrieb Thibaut:
> Forwarding a successful test report for the RFT patch here:
> https://patchwork.ozlabs.org/patch/953454/
>
After rebasing the code onto the current master, it work
id read from unit and txoffset from datasheet
Signed-off-by: Sven Roederer
---
This patch directly applies to the git-repo of iwinfo
hardware.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/hardware.txt b/hardware.txt
index 4cac0a1..81b31cf 100644
--- a/hardware.txt
+++ b
PACKAGE: net/net-snmp
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
this installs the default MIBS-files under /usr/share/snmp/mibs
backport of http://patchwork.ozlabs.org/patch/688978/
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
Am Montag, 31. Oktober 2016, 09:10:17 CET schrieb Stijn Tintel:
> On 30-10-16 19:18, Sven Roederer wrote:
> > PACKAGE: net/net-snmp
> > this installs the default MIBS-files under /usr/share/snmp/mibs
>
> Please send a PR on Github: https://github.com/openwrt/packages
>
Am Samstag, 31. Dezember 2016, 16:12:21 CET schrieb Philip Prindeville:
> Hi.
>
> I wanted to be able to script building images completely.
> Is there an equivalent way to generate the kernel config by seeding it with
> minimum state?
>
> I don’t want to save the complete .config because tha
Update the link to the current section in the documentaion wiki.
This fixes https://github.com/openwrt/packages/issues/6282
Signed-off-by: Sven Roederer
---
package/base-files/files/etc/banner.failsafe | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/package/base-files
Am Dienstag, 12. Juni 2018, 22:48:39 CEST schrieb Sven Roederer:
> Update the link to the current section in the documentaion wiki.
> This fixes https://github.com/openwrt/packages/issues/6282
>
This was merged into master with 2314c2c6f295b7b4aa5a261d19fa6ca16210f42c.
Can you cherry-
Am Sonntag, 24. Juni 2018, 22:36:42 CEST schrieb Hans Dedecker:
>
> Cherry-picked to both 18.06 and 17.01
>
> Hans
>
Thanks
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/listinfo/openwrt-devel
Hi,
since long time our buildbot hat problems creating images for ar71xx-mikrotik
with openwrt-master. I'm not sure anymore when it started after branching
17.01, as I did not look for this target for long.
By default we are using the following config-options:
CONFIG_VERSIONOPT=y
CONFIG_VERSION
Hi,
it's a bit off-topic, but probably someone can share the correct uboot-env of
a Turris-Omnia 2G.
Mine is not bootingafter somehow damaging the settings.
A simple printenv would be great.
Thanks Sven
___
openwrt-devel mailing list
openwrt-devel@l
, 1. Juli 2018, 23:20:12 CEST schrieb Sven Roederer:
> Hi,
>
> since long time our buildbot hat problems creating images for
> ar71xx-mikrotik with openwrt-master. I'm not sure anymore when it started
> after branching 17.01, as I did not look for this target for long.
Am Samstag, 19. Oktober 2019, 16:45:40 CEST schrieb Baptiste Jonglez:
> Thanks Philipp, I didn't know Freifunk Berlin had its own firmware
> generation utility! Looking at it, it seems a bit heavyweight (it builds
> OpenWrt from scratch instead of using the ImageBuilder) but it's probably
> necess
Hi all,
based on Jo Blockers I created a GtiHub-PR [1] which should work as an
comprehensive list for easy review.
Based on a short check of the replies, there are only 3 blockers open. The
RPCd memleak seems to in good progress to get solved.
Thanks to all making this great project
Sven
1 -
Hi,
can you cherry-pick the following two commits to openwrt-19-07 branch:
* 853e4dd3062df7cb5704b15d6af6730e3194b571 (ipqx0xx: add Generic subtarget)
* 40e3f660c1c0f400092cce09feb8c13bec97caeb (uboot-fritz4040: build with
ipq40xx "generic" subtarget)
We use this since some time in our freifunk
The "append-uboot" macro is looking for the file
"$(STAGING_DIR_IMAGE)/uboot-fritz4040.bin"
which is provided by the u-boot-fritz4040 package. If this is not build, image
creation
will fail with "file not found".
Signed-off-by: Sven Roederer
---
target/linux/ip
switch
- Button: 1x reset button
- LED: 3x LEDS (white)
Flash instruction:
Support for sysupgrade directive upgrades, as well as luci upgrades.
Signed-off-by: Luochongjun
(cherry picked from commit 921675a2d148330a7ec44f10ea4d583b8d7b5a44)
[backported to 19.07]
Signed-off-by: Sven Roederer
Adrian,
it's just that I've this patch around for some time, as I use this device on
19.07. So just sharing this patch ...
Sven
Am Freitag, 13. Dezember 2019, 21:21:14 CET schrieb Adrian Schmutzler:
> Hi Sven,
>
> so, the primary question remains unanswered: Why should exactly this device
> be
Am Freitag, 13. Dezember 2019, 21:07:23 CET schrieb Paul Fertser:
> Hello,
>
> On Fri, Dec 13, 2019 at 08:50:46PM +0100, Sven Roederer wrote:
> > .../ath79/base-files/etc/board.d/02_network | 5 +
> > .../etc/hotplug.d/firmware/11-ath10k-caldata | 1 +
> > .../
Paul,
Am Samstag, 14. Dezember 2019, 00:10:28 CET schrieb Paul Fertser:
> Also, if you're going to improve the patch, I've noticed you have no
> DTS designations for how the LEDs are to be used (aliases for led-boot
> etc) and no label_mac assignment. Not sure if that's important.
As the router i
Also use xz compression, as we do for sdk and imagebuilder.
Signed-off-by: Sven Roederer
---
target/toolchain/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/target/toolchain/Makefile b/target/toolchain/Makefile
index c3ba70db04..cf34a89e04 100644
--- a/target
e passed into the archives via
.config
for the imagebuilder and via Config.in and Config.build for the sdk.
The expected behavior is that after unpacking sdk and imagebuilder act like
these
settings have the default, using intree folders. So unset or filter out the
build-
time settings.
Signed-off-by:
ives via
.config file.
The expected behavior is that after unpacking the imagebuilder acts like
these settings have their defaults, using intree folders. So unset the
build-time settings.
Signed-off-by: Sven Roederer
---
target/imagebuilder/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff -
Using the BINARY_FOLDER or DOWNLOAD_FOLDER options make them escape from the
build-system to the system the archives run later.
As the build-time path will usually not work on the other system, restore the
intree defaults.
___
openwrt-devel mailing l
e previous commit for the
imagebuilder.
Signed-off-by: Sven Roederer
---
target/sdk/Makefile | 1 +
target/sdk/convert-config.pl | 8 +++-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/target/sdk/Makefile b/target/sdk/Makefile
index 0606621192..5330d14955 100644
--
Hi,
I've seen this once, but just was able to double check ...
Using a freshly installed OpenWrt 21.02 fails to install a package that has
been downloaded manually. I had seen this initially when using my own image
where a package was missing. To fix I copied over with scp and wanted to
instal
Am Donnerstag, 29. April 2021, 01:54:34 CEST schrieb Sven Roederer:
>
> Using a freshly installed OpenWrt 21.02 fails to install a package that has
> been downloaded manually. I had seen this initially when using my own image
> where a package was missing. To fix I copied over with sc
Adrian,
Am Sonntag, 25. April 2021, 21:09:40 CEST schrieb Adrian Schmutzler:
> Hi,
>
> > -Original Message-
> > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> > On Behalf Of Sven Roederer
> > Sent: Samstag, 24. April 20
Hi,
there are reports about unstable ethernet-links for TPLink EAP2x5 devices in
the forum [1].
I can confirm that cherry-picking fbbad9a9a629b388626b477e6cd692c160f63fb3 to
21.02 fixes it. Can somebody cherry-pick?
Best Sven
1 -
https://forum.openwrt.org/t/eap225-v1-lan-port-link-speed-100m
Am Freitag, 30. April 2021, 14:23:12 CEST schrieb Hannu Nyman:
> Sven Roederer kirjoitti 30.4.2021 klo 1.44:
> > Am Donnerstag, 29. April 2021, 01:54:34 CEST schrieb Sven Roederer:
> >> Using a freshly installed OpenWrt 21.02 fails to install a package that
> >> has
&g
Am Freitag, 30. April 2021, 04:49:09 CEST schrieb Alex Henrie:
> I haven't gotten a serial cable hooked up yet, but I tried with
> another AD7200 router that is running stock firmware version 1.0.10
> and was not able to upload OpenWrt to it either. Its web interface
> gives the error "Invalid file
Am Samstag, 1. Mai 2021, 15:14:35 CEST schrieb Hannu Nyman:
> Sven Roederer kirjoitti 30.4.2021 klo 22.43:
> > ...
> > Digging further I found installing online pulled librt in. Restarting from
> > scratch ...
> > Downloading librt and wall via wget and running `opkg
1 - 100 of 155 matches
Mail list logo
