Hi Christian,
On Wed, Jun 5, 2019 at 10:23 PM Christian Lamparter wrote:
> @Kristian Evensen, can you please check if the following patch would also
> resolve the issues you have been experiencing?
>
> I had to attach the patch as a file since gmail's webmail interface now seems
> to
> eat all t
On 6/5/19 1:54 PM, Petr Štetiar wrote:
Jeff Kletsky [2019-06-05 13:17:05]:
Hi,
I'll put aside, that it's 4.19 (we should still focus on 4.14), can you please
explain in more detail, why we would need all this bacported patches?
* macronix: Fix ECC Status Read
I can understand this one.
Jeff Kletsky [2019-06-05 13:17:06]:
> Backport upstream support for GigaDevice GD5F1GQ4UFxxG SPI NAND
>
> * Add support for GigaDevice GD5F1GQ4UFxxG
> * Add support for two-byte device IDs
> * Define macros for page-read ops with three-byte addresses
What devices currently in the tree need (
Jeff Kletsky [2019-06-05 13:17:05]:
Hi,
I'll put aside, that it's 4.19 (we should still focus on 4.14), can you please
explain in more detail, why we would need all this bacported patches?
> * macronix: Fix ECC Status Read
I can understand this one.
> * winbond: Add support for W25N01GV
Th
On Tue, Jun 4, 2019 at 3:05 PM Petr Štetiar wrote:
>
> Commit afc056d7dc83 ("gpio-button-hotplug: support interrupt
> properties") changed the gpio-keys interrupt handling logic in a way,
> that it always misses first event, which causes issues with rc.button
> scripts, so this patch restores the
From: Jeff Kletsky
Backport upstream support for GigaDevice GD5F1GQ4UFxxG SPI NAND
* Add support for GigaDevice GD5F1GQ4UFxxG
* Add support for two-byte device IDs
* Define macros for page-read ops with three-byte addresses
Upstream patches refreshed against 4.19.47
Run-tested-on: ath79/nan
From: Jeff Kletsky
Several SPI NAND chips were added between 4.19 and 5.1
including GigaDevice, Toshiba, and Winbond.
A fix to Macronix chips' ECC was also included.
* Add support for GigaDevice GD5F1GQ4UExxG
* Add support for all Toshiba Memory products
* macronix: Fix ECC Status Read
* add
From: Jeff Kletsky
This patch series brings in various chips supported by the upstream
SPI-NAND framework after 4.19 and through linux/next at this time.
There are significant changes to the driver in 5.x that add new
features that have not been backported as they are relatively invasive
and/or
Through LuCI, stopping / disabling rngd, as I am also testing the urngd
change. Did not happen on an image generated yesterday.
On 2019-06-05 1:16 p.m., Jo-Philipp Wich wrote:
Hi,
Something has started zeroing out /etc/rc.local contents, maybe:
https://git.openwrt.org/?p=project/luci.git;a=c
Hi,
> Does it zero out itself or when using LuCI? The commit above will
> touch rc.local when LuCI is not used.
This should have been: "will *not* touch rc.local when LuCI is not used"
~ Jo
signature.asc
Description: OpenPGP digital signature
___
op
Hi,
> Something has started zeroing out /etc/rc.local contents, maybe:
>
> https://git.openwrt.org/?p=project/luci.git;a=commit;h=1c09ee5e42550d6339bffa58d4cba3461948e19c
Does it zero out itself or when using LuCI? The commit above will
touch rc.local when LuCI is not used.
~ Jo
signature.as
Something has started zeroing out /etc/rc.local contents, maybe:
https://git.openwrt.org/?p=project/luci.git;a=commit;h=1c09ee5e42550d6339bffa58d4cba3461948e19c
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/m
Use generic wording.
Signed-off-by: Karl Palsson
---
v2: fixed typo
toolchain/Config.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/toolchain/Config.in b/toolchain/Config.in
index 82dddbc209..95087b7078 100644
--- a/toolchain/Config.in
+++ b/toolchain/Config.in
@@ -4
Karl Pálsson writes:
> + If enabled, the buildrood will compile using the native
> toolchain for your
That's the Danish version of the buildroot?
Bjørn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openw
On 05/06/2019 19:10, Karl Pálsson wrote:
Use generic wording.
Signed-off-by: Karl Palsson
---
toolchain/Config.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/toolchain/Config.in b/toolchain/Config.in
index 82dddbc209..e76e62e34f 100644
--- a/toolchain/Config.in
+
Use generic wording.
Signed-off-by: Karl Palsson
---
toolchain/Config.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/toolchain/Config.in b/toolchain/Config.in
index 82dddbc209..e76e62e34f 100644
--- a/toolchain/Config.in
+++ b/toolchain/Config.in
@@ -42,7 +42,7 @@ men
On 05/06/2019 18:42, Karl Palsson wrote:
John Crispin wrote:
The requirement for being able to add custom src toolchains to
the build system has been brought forward by the members of the
prpl foundation. This patch tries to address this requirement
by allowing a ned folder to be loaded into
John Crispin wrote:
> The requirement for being able to add custom src toolchains to
> the build system has been brought forward by the members of the
> prpl foundation. This patch tries to address this requirement
> by allowing a ned folder to be loaded into the tree call
> toolchain_custom. The
This patch should not be merged and is just an example of how the previous
custom toolchain patch can be used.
Signed-off-by: John Crispin
---
toolchain_custom/Config.in| 16 ++
toolchain_custom/binutils/Makefile.var| 10 +
.../patches/300-001_ld_makefile_patch.patc
The requirement for being able to add custom src toolchains to the build
system has been brought forward by the members of the prpl foundation.
This patch tries to address this requirement by allowing a ned folder to be
loaded into the tree call toolchain_custom. The subfolders contained within
hav
On Wed, 5 Jun 2019 at 16:32, Tomasz Maciej Nowak wrote:
>
> Supports EIP97 and EIP197 found on Armada 37xx, 7k and 8k SoCs.
> Unfortunately firmware for EIP197 is not easily obtainable, therefore
> to not cause lot of user requests directed at OpenWrt, package it as
> module with explanation where
W dniu 05.06.2019 o 16:31, Tomasz Maciej Nowak pisze:
> From: Marko Ratkaj
>
> Cc: Vladimir Vid
> Signed-off-by: Marko Ratkaj
> [added sfp related patches from Russell King]
> Signed-off-by: Marek Behún
> [rebase; rework patches; separate and cleanup kernel configs;
> add espessobin dts; adjus
Supports EIP97 and EIP197 found on Armada 37xx, 7k and 8k SoCs.
Unfortunately firmware for EIP197 is not easily obtainable, therefore
to not cause lot of user requests directed at OpenWrt, package it as
module with explanation where to obtain the firmware.
Cc: Marek Behún
Signed-off-by: Tomasz Ma
On Wed, 5 Jun 2019 at 15:28, John Crispin wrote:
>
>
> On 05/06/2019 15:26, Jonas Gorski wrote:
> > On Wed, 5 Jun 2019 at 15:16, John Crispin wrote:
> >>
> >> On 05/06/2019 15:11, Jonas Gorski wrote:
> >>> On Wed, 5 Jun 2019 at 14:58, John Crispin wrote:
> On 05/06/2019 14:54, Jonas Gorski
John Crispin writes:
> On 05/06/2019 14:19, Bjørn Mork wrote:
>> The src-include method allows recursive inclusion of feeds.conf snippets.
>>
>> This can for example be used for adding static local feeds to
>> feeds.conf.default without ever having to update the local feeds.conf:
>>
>> src-inclu
On 05/06/2019 15:26, Jonas Gorski wrote:
On Wed, 5 Jun 2019 at 15:16, John Crispin wrote:
On 05/06/2019 15:11, Jonas Gorski wrote:
On Wed, 5 Jun 2019 at 14:58, John Crispin wrote:
On 05/06/2019 14:54, Jonas Gorski wrote:
Hi,
On Wed, 5 Jun 2019 at 14:33, John Crispin wrote:
On 05/06/201
On Wed, 5 Jun 2019 at 15:16, John Crispin wrote:
>
>
> On 05/06/2019 15:11, Jonas Gorski wrote:
> > On Wed, 5 Jun 2019 at 14:58, John Crispin wrote:
> >>
> >> On 05/06/2019 14:54, Jonas Gorski wrote:
> >>> Hi,
> >>>
> >>> On Wed, 5 Jun 2019 at 14:33, John Crispin wrote:
> On 05/06/2019 13:3
On 05/06/2019 15:11, Jonas Gorski wrote:
On Wed, 5 Jun 2019 at 14:58, John Crispin wrote:
On 05/06/2019 14:54, Jonas Gorski wrote:
Hi,
On Wed, 5 Jun 2019 at 14:33, John Crispin wrote:
On 05/06/2019 13:35, Karl Palsson wrote:
John Crispin wrote:
On 05/06/2019 12:17, Karl Palsson wrote:
On Wed, 5 Jun 2019 at 14:58, John Crispin wrote:
>
>
> On 05/06/2019 14:54, Jonas Gorski wrote:
> > Hi,
> >
> > On Wed, 5 Jun 2019 at 14:33, John Crispin wrote:
> >>
> >> On 05/06/2019 13:35, Karl Palsson wrote:
> >>> John Crispin wrote:
> On 05/06/2019 12:17, Karl Palsson wrote:
> > Jo
On 05/06/2019 14:54, Jonas Gorski wrote:
Hi,
On Wed, 5 Jun 2019 at 14:33, John Crispin wrote:
On 05/06/2019 13:35, Karl Palsson wrote:
John Crispin wrote:
On 05/06/2019 12:17, Karl Palsson wrote:
John Crispin wrote:
This can be used inside build setups for easy feeds.conf
generation.
Hi,
On Wed, 5 Jun 2019 at 14:33, John Crispin wrote:
>
>
> On 05/06/2019 13:35, Karl Palsson wrote:
> > John Crispin wrote:
> >> On 05/06/2019 12:17, Karl Palsson wrote:
> >>> John Crispin wrote:
> This can be used inside build setups for easy feeds.conf
> generation.
> >>> Could you
On 05/06/2019 13:35, Karl Palsson wrote:
John Crispin wrote:
On 05/06/2019 12:17, Karl Palsson wrote:
John Crispin wrote:
This can be used inside build setups for easy feeds.conf
generation.
Could you give us an example of how this is actually easy, or
what sort of functionality this is p
On 05/06/2019 14:19, Bjørn Mork wrote:
The src-include method allows recursive inclusion of feeds.conf snippets.
This can for example be used for adding static local feeds to
feeds.conf.default without ever having to update the local feeds.conf:
src-include defaults feeds.conf.default
src-
The src-include method allows recursive inclusion of feeds.conf snippets.
This can for example be used for adding static local feeds to
feeds.conf.default without ever having to update the local feeds.conf:
src-include defaults feeds.conf.default
src-link custom /usr/local/src/lede/custom
Sign
A little late into this discussion, but something like the attached
patch would suite my personal usage patterns much better. I don't
really need to update or change my local additions to feeds.conf at all.
I just want to add them to the defaults for whatever version I am
currently building.
Anot
John Crispin wrote:
>
> On 05/06/2019 12:17, Karl Palsson wrote:
> > John Crispin wrote:
> >> This can be used inside build setups for easy feeds.conf
> >> generation.
> >
> > Could you give us an example of how this is actually easy, or
> > what sort of functionality this is providing beyond "
John Crispin [2019-06-05 12:30:57]:
> On 05/06/2019 12:17, Karl Palsson wrote:
> > It seems like a lot of perl for a narrow usecase.
It seems like a good starting point, but it makes me wonder who is going to
touch this afterwards due to the Perl :-)
> This was brought up as a missing feature b
On 05/06/19 07:22, John Braley wrote:
Also tested on an EFI only Asrock J5005-ITX. Builds, writes and boots
fine. However since it is not from 18.06 dev and is built from LEDE
you really cant do anything else with as luci wont install via opkg.
If the commits can be pulled into openwrt-dev, I
On 05/06/2019 12:17, Karl Palsson wrote:
John Crispin wrote:
This can be used inside build setups for easy feeds.conf
generation.
Could you give us an example of how this is actually easy, or
what sort of functionality this is providing beyond "cat
feeds.conf.default feeds.conf.extra > feed
John Crispin wrote:
> This allows managing several different folder for varying env
> profiles.
This is neat, very cool! Thanks for this, I hadn't even thought
it could be done so simply.
Cheers,
Karl Palsson
OpenPGP-digital-signature.html
Description: OpenPGP Digital Signature
__
John Crispin wrote:
> This can be used inside build setups for easy feeds.conf
> generation.
Could you give us an example of how this is actually easy, or
what sort of functionality this is providing beyond "cat
feeds.conf.default feeds.conf.extra > feeds.conf"
It seems like a lot of perl for
In commit d2e18dae2892 ("kirkwood: cleanup image build code") the image
build code was refactored, setting KERNEL_IN_UBI=0 which doesn't work as
the KERNEL_IN_UBI needs to be unset in order to make it working as
intended, which leads to factory images with two kernels in them:
binwalk --keep-goin
42 matches
Mail list logo
