Changing the subject from the previous thread as it turned out to not have to
do with sysupgrade at all.
What I can tell is this, having added some tracing to fstools.
We get to the call to system() in rootdisk_volume_init():
Hello Sergey,
On 01.09.2017 06:16, ad...@yapic.net wrote:
From: Sergey Sergeev
Changes the platform to use the Chipidea driver instead of the
generic USB host driver which has support for both host and
device modes (selected on boot) for QCA953x based boards.
It was tested
On Sun, 10 Sep 2017, Zoltan HERPAI wrote:
The A8-based devices don't boot (A10/A13), waiting on me to come up with a
fix.
-w-
On Sun, 10 Sep 2017, Lucian CRISTIAN wrote:
Is something that blocks these patch sets to go in trunk ?
It looks like that CONFIG_ARM_LPAE is the culprit for these
On Sat, Sep 9, 2017 at 1:20 PM, JORDI PALET MARTINEZ
wrote:
> Ah even better, I thought 17.01.2 was not including the right CLAT (NAT46)
> stuff.
>
> So, I will try that then:
>
>
The A8-based devices don't boot (A10/A13), waiting on me to come up with a
fix.
-w-
On Sun, 10 Sep 2017, Lucian CRISTIAN wrote:
Is something that blocks these patch sets to go in trunk ?
Regards
Lucian
___
Lede-dev mailing list
ok. I'll be waiting until the framework merged into the upstream kernel.
2017-09-10 13:25 GMT+08:00 Felix Fietkau :
> On 2017-09-06 18:24, Weijie Gao wrote:
>> Yes, I have to admit operations of GigaDevice's chips are the same.
>> All the chips have the same read/write/erase
Is something that blocks these patch sets to go in trunk ?
Regards
Lucian
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
The ZBT WE1026-5G
(http://www.zbtlink.com/products/router/WE1026-5G.html) is the follow-up
to the ZBT WE1026 and is based on MT7620. For the previous WE1026, the
ZBT WE826 image could be used. However, as the name implies, the -5G
comes equipped with a 5GHz wifi radio. As the WE826 only has a
On Sat, Sep 9, 2017 at 10:51 PM, Baptiste Jonglez
wrote:
> On 09-09-17, Baptiste Jonglez wrote:
>> On 05-09-17, Alexandru Ardelean wrote:
>> > The `proto_add_dynamic_defaults()` seems to be called mostly
>> > in the context of LTE/3G modems (via wwan, qmi, etc) setup.