Hi,
Thanks for writing to us about OpenWrt. I think you misunderstand the right
place to ask your questions. Please accept our advice for a good way to
proceed. Here is how I understand your request:
1) You are looking to modify the base OpenWrt release. This seems to be an
interesting set of
Starting with version 1.1.15, musl supports powerpc64.
There are no known users of powerpc64 yet.
This is effectively a revert of 0de93311e1575ab6f8e9e90b5023b6fb2cedcf1f
Signed-off-by: Rosen Penev
---
v2: Add missing entries
toolchain/Config.in | 6 ++
1 file changed, 2 insertions(+), 4
This fixes compilation with -Werror=implicit-function-declaration.
Signed-off-by: Rosen Penev
---
package/network/utils/linux-atm/Makefile | 2 +-
.../linux-atm/patches/700-musl-include.patch | 30 +++
2 files changed, 31 insertions(+), 1 deletion(-)
create mode 100644
Fixes compilation with -Werror=implicit-function-declaration.
Patch submitted upstream: https://github.com/paulusmack/ppp/pull/124
Signed-off-by: Rosen Penev
---
package/network/services/ppp/Makefile | 2 +-
.../services/ppp/patches/700-musl.patch | 22 +++
2
Patch is an upstream backport.
Fixes compilation when -Werror=implicit-function-declaration is passed.
Signed-off-by: Rosen Penev
---
package/utils/util-linux/Makefile | 2 +-
.../util-linux/patches/010-stdlib.h.patch | 26 +++
2 files changed, 27
Starting with version 1.1.15, musl supports powerpc64.
There are no known users of powerpc64 yet.
Signed-off-by: Rosen Penev
---
toolchain/Config.in | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/toolchain/Config.in b/toolchain/Config.in
index 95087b7078..9ca711e29a
Hi
I would like to ask openwrt team to add some special features that i need.
I will use crowd funding to collect the money!
1-I need full control over Lantiq xDsl firmware using both GUI and CLI.
2-I want to override Line Config enforced by DSLAM/DLM, [SNR, Power,
Interleaving, G.INP,
Hi Daniel,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Daniel Danzberger
> Sent: Dienstag, 16. Juli 2019 12:31
> To: openwrt-devel@lists.openwrt.org
> Cc: Daniel Danzberger
> Subject: [OpenWrt-Devel] [PATCH] ramips: mt7621:
The flash layout on the Storlink reference design for Gemini
is using 2 MB flash for the kernel, and it also insists on
overwriting the partition table with default values on every
boot. The same is true for the SQ201. This poses a problem
on recent OpenWrt firmware as the base zImage is bigger
This package just contains a small Gemini-only assembler
bootstrap loop to copy the kernel from the two fragments
(previously zImage at 0x0160 and initramdisk at 0x0080)
into one big zImage of up to 8 MB at 0x0040.
It will be built on demand from the Gemini image Makefile.
The SL93512r and the NAS4220B have Redboot partition
tables (rely on these) and need to boot from mtdblock3.
Add two patches from upstream to fix this.
Signed-off-by: Linus Walleij
---
...-Switch-to-redboot-partition-parsing.patch | 104 ++
Upstream patch fixing the errors in the device tree.
Signed-off-by: Linus Walleij
---
...-gemini-Fix-up-confused-pin-settings.patch | 54 +++
1 file changed, 54 insertions(+)
create mode 100644
It was reported in FS#2385, that Carambola2 doesn't currently have
working watchdog so fix it by adding watchdog node.
Ref: FS#2385
Signed-off-by: Petr Štetiar
---
target/linux/ath79/dts/ar9330.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git
From: Rafał Miłecki
1) nand_do_upgrade() is always called by a target code
2) nand_do_upgrade() starts with calling platform_nand_pre_upgrade()
It means there is no need for the platform_nand_pre_upgrade() callback
at all. All code that was present there could bo moved & simplly called
by a
From: Rafał Miłecki
No target uses it anymore. All code from that callback was moved into
the platform_do_upgrade().
Signed-off-by: Rafał Miłecki
---
package/base-files/Makefile | 2 +-
package/base-files/files/lib/upgrade/nand.sh | 4
2 files changed, 1 insertion(+), 5
Etienne Champetier [2019-07-16 21:17:43]:
Hi,
> Saw that you applied it to master, I just tested the patch on 19.07, works
> fine
> Do you want me to send the patch again, or can you just cherry-pick it ?
> (git cherry-pick 2a7519e29d6cbbe1eb73623ef35add0ef596fb5f)
git cherry-pick -x
From: Rafał Miłecki
1) RAMFS_COPY_BIN and RAMFS_COPY_DATA can be defined at top of the file
like it's done for all other targets.
2) fw_printenv.lock can be created one step later in the
platform_do_upgrade(). It seems to be working well on many other
targets.
Signed-off-by: Rafał
17 matches
Mail list logo
