Hi all,
I am trying to run openwrt on rk3328, but the kernel hanged when booting,
below is the log.Any hints will be appreciated.
below is the boot log:
U-Boot 2020.01 (Apr 07 2020 - 11:55:14 +)
Model: Radxa Rockpi E
DRAM: 1022 MiB
PMIC: RK8050 (on=0x40, off=0x01)
MMC: rksdmmc@ff500
Hi!
First of all: Please don't top-post like this on mailing lists :)
On Sun, May 3, 2020 at 10:40 AM Philip Prindeville
wrote:
>
> I’m not convinced that would be necessary, or that this proposal would create
> any new circumstances.
>
> An example is that certain architectures are supported b
I’m not convinced that would be necessary, or that this proposal would create
any new circumstances.
An example is that certain architectures are supported by MUSL and others by
uClibc, or eglibc, etc. That in turn means that some functionality is
available and others not, because not all pack
I'm concerned about introducing a global configuration symbol that
changes the behavior of any individual package--right now, large- and
small-format devices share the same package feeds, and there's no
provision in opkg for package variant flags.
This suggests that we'd need to host a feed for sk
Wherever we can find common ground, I’m willing to go.
I’ve worked on various projects that used OpenWRT in some atypical scenarios
(positioning radios, traffic shapers, home security hubs, etc). I think it
gets used for a broader base of development than most people realize. There’s
a LOT do
I think we’re both agreeing that there’s a time/place for “largish” platforms
to have their own allowances called out, aren’t we?
We can explicitly call out either the constrained or the seemingly limitless…
either way is fine.
The benefit of calling out the constrained is that they’re hopefull
I like that even better.
OpenWrt has traditionally focused on embedded systems such as routers and the
like. So these should be the default as you say.
Then if I want to run OpenWrt on a larger machine, I can add the fat so to
speak.
On May 2, 2020 11:48:03 PM UTC, m...@adrianschmutzler.de wro
Hi,
just a single thought on this:
For me, this quickly raised the question: What's normal and what's exceptional?
Your proposal assumes that "huge" devices are normal (default), and skinny
devices are the exception which has to be "marked".
Why not the other way around? For standard, just kee
I like “CONSTRAINED” as well.
We could even have:
CONFIG_CONSTRAINED_MEM
and:
CONFIG_CONSTRAINED_DISK
and if either is set, then it sets CONFIG_CONSTRAINED as well.
> On May 2, 2020, at 4:09 PM, Lucas Ramage wrote:
>
> Excellent idea!
>
> But perhaps we could use either CONFIG_CONSTRAINED
Excellent idea!
But perhaps we could use either CONFIG_CONSTRAINED, or CONFIG_DEVICE_THIN
instead?
Regards,
On May 2, 2020 9:54:16 PM UTC, Philip Prindeville
wrote:
>Hi all,
>
>We sometimes get into debates about whether certain functionality
>should be allowed and oftentimes the gating facto
Hi all,
We sometimes get into debates about whether certain functionality should be
allowed and oftentimes the gating factor is “will this fit in a skinny
platform” (i.e. something highly constrained, like 32MB of DRAM)? I suppose
there’s a similar argument about what a “small footprint” machi
Hi all,
We sometimes get into debates about whether certain functionality should be
allowed and oftentimes the gating factor is “will this fit in a skinny
platform” (i.e. something highly constrained, like 32MB of DRAM)? I suppose
there’s a similar argument about what a “small footprint” machi
Hi,
I've installed the latest OpenWRT trunk version. Everything
seems to be fine except the port numbering:
~# cat /sys/kernel/debug/gpio
gpiochip2: GPIOs 416-447, parent: platform/1600.gpio,
1600.gpio-bank2:
gpiochip1: GPIOs 448-479, parent: platform/1600.gpio,
1600.gpio-ban
- Release notes:
https://curl.haxx.se/changes.html#7_70_0
- Refreshed patch
Signed-off-by: Josef Schlehofer
---
package/network/utils/curl/Makefile| 4 ++--
.../utils/curl/patches/200-no_docs_tests.patch | 14 +++---
2 files changed, 9 insertions(+), 9 deletions(-)
On 02.05.2020 14:46, b.l.huang wrote:
Hi all,
Hi all, I am trying to run openwrt on rk3328, but the kernel hanged
when booting, below is the log.
Any hints will be appreciated.
U-Boot 2020.01 (Apr 07 2020 - 11:55:14 +) Model: Radxa Rockpi E
DRAM: 1022 MiB PMIC: RK8050 (on=0x40, off=0x00)
From: Rafał Miłecki
Use this method even if UBIFS extroot support is enabled. This is needed
on x86 systems (using F2FS for overlay) as they may still come with F2FS
enabled.
Ref: https://bugs.openwrt.org/index.php?do=details&task_id=2231
Signed-off-by: Rafał Miłecki
---
block.c | 26 +
Hi all,
Hi all, I am trying to run openwrt on rk3328, but the kernel
hanged when booting, below is the log.
Any hints will be appreciated.
U-Boot 2020.01 (Apr 07 2020 - 11:55:14 +) Model: Radxa Rockpi E DRAM: 1022
MiB PMIC: RK8050 (on=0x40, off=0x00) MMC: rksdmmc@ff50: 1,
rksd
17 matches
Mail list logo
