On Mon, 2 Mar 2020 at 10:21, Enrico Mioso wrote:
>
> Hi! I flashed OpenWRt master (commit
> 4349d4c6823bfe09caabbdd3c9a65198addc76d6) on this device. All seems to work
> fine, but I sawthis in the dmesg.
>
> should I worry about my flash chip?
> thank you guys!!
>
> Enrico
This could be a
Sorry for the third mail... note: on 4.19.71 this problem did not happen.
On Mon, 2 Mar 2020, Enrico Mioso wrote:
Date: Mon, 2 Mar 2020 03:44:38
From: Enrico Mioso
To: openwrt-devel@lists.openwrt.org
Cc: Neil Brown
Subject: Re: jffs2: Erase at 0x01ab failed immediately: errno -22 on
Ok guys, the error rpeats itself, and jffs2 seems to get corrupted. And even
erasing the mtd6 device fails at some point.
Even the F2FS filesystem on the internal SSD does corrupt. This remembers me
the issue I was having when using the GnuBee PC 1 some time ago.
any help would be really
Hi! I flashed OpenWRt master (commit 4349d4c6823bfe09caabbdd3c9a65198addc76d6)
on this device. All seems to work fine, but I sawthis in the dmesg.
should I worry about my flash chip?
thank you guys!!
Enrico
config.buildinfo:
CONFIG_TARGET_ramips=y
CONFIG_TARGET_ramips_mt7621=y
On 01.03.20 02:34, Petr Štetiar wrote:
Paul Spooren [2020-02-29 16:48:50]:
FYI:
$ grep JSON .config
CONFIG_JSON_OVERVIEW_IMAGE_INFO=y
$ cat bin/targets/imx6/generic/profiles.json
{}
This problem occurs also fox x86, the problem is that the image function
is not properly called.
On 01.03.20 02:29, Moritz Warning wrote:
Hi Paul,
as I see it, there are now two JSON options:
- creates the single JSON files in the $(KDIR)/tmp folder
- create a per target overview JSON that contains nearly all data of the single
JSON files
This is the way I implemented it now :)
Branch: refs/heads/master
Home: https://github.com/sdwalker/sdwalker.github.io
Commit: d19be5bc910acc190f3a19d30fc210efc9876a7f
https://github.com/sdwalker/sdwalker.github.io/commit/d19be5bc910acc190f3a19d30fc210efc9876a7f
Author: Stephen Walker
Date: 2020-03-01 (Sun, 01 Mar
Hello Magnus
On 3/1/20 1:08 PM, Magnus Kroken wrote:
> Signed-off-by: Magnus Kroken
> ---
> According to e-mail about pushing kernel 5.4 support to master, 5.4 was added
> as testing
> kernel for supported targets. For mpc85xx, 5.4 was set as its default
> kernel. (This technically also applies
Hi again, Petr.
A domingo, 1/03/2020, 13:47, Petr Štetiar escreveu:
> Rui Salvaterra [2020-03-01 13:39:37]:
>
> > Ah, silly me, you're absolutely right. This is just half the patch, and
> > it's perfectly fine the way it is, so I'm not enabling anything new, just
> > exposing the existing
Rui Salvaterra [2020-03-01 13:39:37]:
> Ah, silly me, you're absolutely right. This is just half the patch, and
> it's perfectly fine the way it is, so I'm not enabling anything new, just
> exposing the existing kconfig. Please ignore my previous email.
Well, I've re-read it again.
Your commit
Ah, silly me, you're absolutely right. This is just half the patch, and
it's perfectly fine the way it is, so I'm not enabling anything new, just
exposing the existing kconfig. Please ignore my previous email.
Thanks,
Rui
A domingo, 1/03/2020, 13:34, Rui Salvaterra
escreveu:
> Hi, Petr!
Hi, Petr! Writing from my phone, pardon the terseness (and HTML crap).
A domingo, 1/03/2020, 13:06, Petr Štetiar escreveu:
> Rui Salvaterra [2020-01-27 18:19:46]:
>
> why is this RFC, are there any gotchas?
>
This has only been thoroughly tested on AR9003 and AR9002 hardware. I just
received
Rui Salvaterra [2020-01-27 18:19:46]:
Hi,
> The ath9k driver is able to leverage the PHY ADC in order to provide a
> generic hardware random number generator to the kernel, filling up the
> entropy pool as required. Expose this feature in the build system and
> remove the old entropy patch,
ad...@kryma.net [2020-02-19 02:39:23]:
Hi,
...
> + partition@2 {
> + compatible = "denx,uimage";
> + label = "firmware";
> + reg = <0x02 0x7c>;
> + };
> +
> +
Paul Spooren [2020-02-29 16:48:50]:
FYI:
$ grep JSON .config
CONFIG_JSON_OVERVIEW_IMAGE_INFO=y
$ cat bin/targets/imx6/generic/profiles.json
{}
> diff --git a/config/Config-build.in b/config/Config-build.in
> index 6a6fb2882c..57428399ab 100644
> --- a/config/Config-build.in
> +++
Hi Paul,
as I see it, there are now two JSON options:
- creates the single JSON files in the $(KDIR)/tmp folder
- create a per target overview JSON that contains nearly all data of the single
JSON files
Questions:
- Why not only have one JSON menu option that create the one per target JSON
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
---
Hauke Mehrtens [2020-03-01 13:12:29]:
> This removed the kernel 4.14 support for multiple targets which were
> early switched to kernel 4.19. This should reduce the maintenance
> efforts especially after or when we add kernel 5.4 support for these
> targets. Some of these targets do not even
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
---
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
---
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
---
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
---
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
---
This removed the kernel 4.14 support for multiple targets which were
early switched to kernel 4.19. This should reduce the maintenance
efforts especially after or when we add kernel 5.4 support for these
targets. Some of these targets do not even compile against 4.14 any
more.
Hauke Mehrtens
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
---
This target was switched to kernel 4.19 more than 6 months ago in commit
f342ffd300da ("treewide: kernel: bump some targets to 4.19") and now
with kernel 5.4 support being added it gets harder to support kernel
4.14 in addition to kernel 4.19 and 5.4.
Signed-off-by: Hauke Mehrtens
---
This removed the kernel 4.14 support for multiple targets which were
early switched to kernel 4.19. This should reduce the maintenance
efforts especially after or when we add kernel 5.4 support for these
targets. Some of these targets do not even compile against 4.14 any
more.
Hauke Mehrtens
Signed-off-by: Magnus Kroken
---
According to e-mail about pushing kernel 5.4 support to master, 5.4 was added
as testing
kernel for supported targets. For mpc85xx, 5.4 was set as its default
kernel. (This technically also applies to ipq807x, but master has no
support for it on any prior
Hi,
> --- a/target/linux/imx6/base-files/etc/board.d/02_network
> +++ b/target/linux/imx6/base-files/etc/board.d/02_network
> @@ -13,7 +13,11 @@ case "$board" in
> cubox-i |\
> *gw51xx |\
> *gw52xx |\
> -*gw5904)
> +*gw5904 |\
> +*gw5907 |\
> +*gw5910 |\
> +*gw5912 |\
> +*gw5913)
Is there any
Tim Harvey [2020-02-28 11:33:30]:
Hi Tim,
> - backport dts patches from 5.6:
> ARM: dts: imx: Add GW5912 board support
> ARM: dts: imx: Add GW5913 board support
> ARM: dts: imx: Add GW5910 board support
> ARM: dts: imx: Add GW5907 board support
> - add support for board names in lib/imx6.sh
> -
There is something strange going on in the buildbot. It doesn't seem to like
the current codebase.
Lots of core packages fail currently e.g. for mips_24kc (=ath79). The core
packages is so intertwined that I can't even figure out which is the actual
culprit.
31 matches
Mail list logo
