Eneas U de Queiroz wrote at Thu Apr 9 17:39:17 PDT 2020:
> This was reported to me here:
>
https://github.com/openwrt/openwrt/commit/dcf3e63a35d05e7e5103819c0f17195bfafe9baa#commitcomment-38390450
> The update to kconfig-v5.6 broke TARGET_MULTI_PROFILE because it would not
accept bool TARGET_DEV
Hi Li Zhang,
thank you very much for the contribution! Please stick to the device
tree naming schema of `manufacture,model` when adding devices to
OpenWrt. In this case the device should be called `glinet,gl-vm1000`
instead of just `gl-mv1000`.
For the device profile (inline commented below), ple
This patch adds supports for GL-MV1000.
Specification:
- SOC: Marvell Armada 88F3720 (1GHz)
- Flash: 16MB
- RAM: 1GB DDR4
- Ethernet: 3x GE (1 WAN + 2 LAN)
- EMMC: 8GB EMMC
- MicroSD: 1x microSD slot
- USB: 1x USB 2.0 port;1x USB 3.0 port(typ
In FS#2738 we can see that patch first introduced in
e8ebcff ("ramips: add a explicit reset to dwc2")
breaks USB functionality since 18.06. Thus, this patch should be removed.
Removed:
- 0032-USB-dwc2-add-device_reset.patch
Fixes: FS#2738
Fixes: FS#2964
Signed-off-by: Alexey Dobrovolsky
---
No
Le ven. 10 avr. 2020 à 17:09, Etienne Champetier
a écrit :
>
> Hi Michael,
>
> Le ven. 10 avr. 2020 à 16:48, W. Michael Petullo a écrit :
> >
> > Has anyone tried to build a Java compiler package for OpenWrt? I am
> > investigating doing this. I see the lang/jamvm JVM, but no compiler
> > akin to
Hi Michael,
Le ven. 10 avr. 2020 à 16:48, W. Michael Petullo a écrit :
>
> Has anyone tried to build a Java compiler package for OpenWrt? I am
> investigating doing this. I see the lang/jamvm JVM, but no compiler
> akin to devel/gcc or lang/golang. I have packaged a number of things,
> but I susp
Has anyone tried to build a Java compiler package for OpenWrt? I am
investigating doing this. I see the lang/jamvm JVM, but no compiler
akin to devel/gcc or lang/golang. I have packaged a number of things,
but I suspect this will be a bit more of a challenge. Hence my question
here.
Thank you!
--
Andre Valentin writes:
> Am 07.04.20 um 17:49 schrieb Bjørn Mork:
>> Just remembered an issue on my todo list: There have been some MTU
>> handling changes in the kernel networking API. This affected the
>> qmi_wwan QMAP handling. I am not sure about the current status. Will
>> have to dig a b
With forum help from @123serge123 the trendnet:internet:green gpio was
enabled and added to a *dts and 01_leds. It is highly likely that this
change will work for the D-Link DIR-810L. Both the Trendnet and the
D-Link use a Cameo based board with the same cpu, spi flash and ram
chips. They hav
Am Dienstag, 7. April 2020, 16:22:37 CEST schrieb Hannu Nyman:
> I do not think that there is a nice clean solution, as I do not remember
> seeing a solution of different packages for iniramfs, factory and sysupgrade
> images.
>
> I would approach that with a two-step build process, using two .con
Hi Andre,
On Fri, Apr 10, 2020 at 2:29 PM Andre Valentin wrote:
>
[snip]
> > Does these changes makes the job for you?
Attached new patch. This hopefully works.
> No, it does not work. Again I get this:
> root@OpenWrt:/# cat /proc/interrupts
>CPU0 CPU1 CPU2 CPU3
>
Hi Sergio
Am 10.04.20 um 13:36 schrieb Sergio Paracuellos:
>> cat /proc/interrupts new:
>>CPU0 CPU1 CPU2 CPU3
>> 8: 75188 75268 75341 75246 MIPS GIC Local 1 timer
>> 9: 24413 0 0 0 MIPS GIC 63 IPI call
>>
On Fri, Apr 10, 2020 at 1:36 PM Sergio Paracuellos
wrote:
>
> Hi André,
>
> On Fri, Apr 10, 2020 at 11:36 AM Andre Valentin wrote:
> >
> > Hi Sergio,
> >
> > the device has an onboard LTE modem. Tonight I noticed that the originial
> > pci driver
> > must have changed some additional GPIO pins.
Hi André,
On Fri, Apr 10, 2020 at 11:36 AM Andre Valentin wrote:
>
> Hi Sergio,
>
> the device has an onboard LTE modem. Tonight I noticed that the originial pci
> driver
> must have changed some additional GPIO pins.
> After more testing, I found the GPIO and the LTE device now operates again.
Hi , Paul
Sorry, I misread the mail contact.
Our watchdog uses two GPIO to control, one is to use pulse to switch the
watchdog, one GPIO is used to feed the dog, specifically the external
single-chip to feed the dog, now the external single-chip cannot detect the
level change of GPIO I now
Hi , MartinOur
Watchdog uses two GPIO to control, one is to use pulse to switch the
watchdog, one GPIO is used to feed the dog, specifically the external
single-chip to feed the dog, now the external single-chip cannot detect the
level change of GPIO I now suspect that the wdt-gpio delay
Hi,
On Fri, Apr 10, 2020 at 06:55:59PM +0800, guilin.wang wrote:
> but found that the dog could not be fed successfully.
Why exactly?
> Our external microcontroller feeds the dog. The cpu just gives the
> microcontroller a trigger signal, but I tested that the
> microcontroller cannot detect the
Hi ,Martin
Thank your for your suggest, I initially followed this method, but found
that the dog could not be fed successfully. Our external microcontroller feeds
the dog. The cpu just gives the microcontroller a trigger signal, but I tested
that the microcontroller cannot detect the level ch
This patch was previously send to the Kernel, however as it also changes
labels and the DTS filename existing devices could break.
The internal Linksys codename `rango` is renamed to `wrt3200acm`, it's
common model name. This way the build code base becomes more readable as
developers don't need t
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi Andreas,
On Sat, Mar 28, 2020
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi,
On Fri, Apr 10, 2020 at 11:47
Now that the x86 target uses the new image generation code we can also
attach metadata to the created images.
As currently the `SUPPORTED_DEVICES` list is empty, no JSON metadata is
attached, however the signing happens in the same step.
This results in signature verification for x86 images.
Sig
Signed-off-by: guilin.w...@gl-inet.com
---
package/kernel/om-watchdog/Makefile | 2 +-
package/kernel/om-watchdog/files/om-watchdog | 40 +++
package/kernel/om-watchdog/files/om-watchdog.init | 2 ++
3 files changed, 37 insertions(+), 7 deletions(-)
diff
Hi Sergio,
the device has an onboard LTE modem. Tonight I noticed that the originial pci
driver
must have changed some additional GPIO pins.
After more testing, I found the GPIO and the LTE device now operates again.
But after more testing, I found out that the wifi chip does not fully
initiali
Hi!
Am 07.04.20 um 17:49 schrieb Bjørn Mork:
> Just remembered an issue on my todo list: There have been some MTU
> handling changes in the kernel networking API. This affected the
> qmi_wwan QMAP handling. I am not sure about the current status. Will
> have to dig a bit more. But this might b
25 matches
Mail list logo
