I did not try to think through if this would be the correct thing to do for
all packages, but the basic change seems reasonable. Having the uci-defaults
run postponed to the reboot is annoying in some cases.
However, your patch seems to break the basic characteristics of an
uci-defaults script
Packages may install scripts into /etc/uci-defaults to be executed once
after installation, usually at the first boot of the target. This works
fine if the package was installed onto the rootfs during build or using
the ImageBuilder.
If the package is installed using opkg during run-time uci-defaul
Packages may install scripts into /etc/uci-defaults to be executed once
after installation, usually at the first boot of the target. This works
fine if the package was installed to the rootfs during build or using
the ImageBuilder.
If the package is installed using opkg during run-time uci-defaults
Packages may install scripts into /etc/uci-defaults to be executed once
after installation, usually at the first boot of the target. This works
fine if the package was installed to the rootfs during build or using
the ImageBuilder.
If the package is installed using opkg during run-time uci-defaults
On 27/04/2016 22:09, Mathias Kresin wrote:
> The VGV7510KW22 has the leds for LAN1-3 connected to pin1 of the phys
> and the led for LAN4 connect to pin0 of the phy. This results with the
> current configuration in a fast flashing LAN4 led as soon as a network
> cable is connected. Something simi
Signed-off-by: Mathias Kresin
---
.../patches-4.4/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/target/linux/lantiq/patches-4.4/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch
b/target/linux/lantiq/patches-4.4/002
The VGV7510KW22 has the leds for LAN1-3 connected to pin1 of the phys
and the led for LAN4 connect to pin0 of the phy. This results with the
current configuration in a fast flashing LAN4 led as soon as a network
cable is connected. Something similar was reported on the forum[1] for
the VGV7519 as w
The VGV7510KW22 has the leds for LAN1-3 connected to pin1 of the phys
and the led for LAN4 connect to pin0 of the phy. This results with the
current configuration in a fast flashing LAN4 led as soon as a network
cable is connected. Something similar was reported in the forum[1] for
the VGV7519 as w
Signed-off-by: Mathias Kresin
---
.../patches-4.4/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
a/target/linux/lantiq/patches-4.4/0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch
b/target/linux/lantiq/patches-4.4/002
OpenWRT has own support for the memory-mapped fast SPI flash read on ath79.
With mainline kernel 4.6/4.7 more elegant generic support for this feature
was added upstream consisting of these commits:
556351f14e74 "spi: introduce accelerated read support for spi flash devices"
08922f644878 "mtd: dev
This is another issue with musl and kernel headers colliding.
However this one cannot seem to be fixed with header guards
as my last 2 patches for mpc85xx.
Patch 1: http://patchwork.ozlabs.org/patch/614830/
Patch 2: http://patchwork.ozlabs.org/patch/615669/
It seems that doing a bit inclusion bla
The header guard is the same as in:
linux/arch/powerpc/include/uapi/asm/errno.h
I've sent another patch for this issue, but reconsidered on it.
Patch is here: http://patchwork.ozlabs.org/patch/614830/
The issue is a collision on the EDEADLOCK define between
musl's and the kernel's when buildin
From: Dan Bugnar
Change the log buffer size and copy the messages.
Signed-off-by: Dan Bugnar
---
log/syslog.c | 37 +++--
log/syslog.h | 2 +-
2 files changed, 16 insertions(+), 23 deletions(-)
diff --git a/log/syslog.c b/log/syslog.c
index e8b6774..d6cb868 10
From: Dan Bugnar
Add logd link to uci library, to read the system config file and get the buffer
size.
Remove the -S option support and use just the option from the config file.
Signed-off-by: Dan Bugnar
---
CMakeLists.txt | 2 +-
log/logd.c | 58 +
Found the solution ! Need to add uart1 in dts and set the clock
Le 27 avr. 2016 09:24, "Baptiste Clenet" a écrit :
> Hi,
>
> I want to run an UART communication between the mt7688 and another
> board, console uses UART0 but I want to configure UART1 to be able to
> send data on it. Currently, if
Signed-off-by: Hans Dedecker
---
package/network/services/ppp/Makefile | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/package/network/services/ppp/Makefile
b/package/network/services/ppp/Makefile
index e0acf59..23c1e93 100644
--- a/package/network/servic
A dropbear instance having an interface config won't start if the interface is
down as no
IP address is available.
Adding interface triggers for each configured interface executing the dropbear
reload script
will start the dropbear instance when the interface is up.
Signed-off-by: Hans Dedecker
Conntrack support reads the connection track mark associated with
incoming DNS queries and sets the same mark value on the upstream
forwarded DNS query. This can be usefull to track traffic generated
by dnsmasq to associate it with the clients who generate the queries,
usefull for bandwidth accouti
Add support for the command line utility nstat displaying network statistics
Signed-off-by: Hans Dedecker
---
package/network/utils/iproute2/Makefile | 11 +++
1 file changed, 11 insertions(+)
diff --git a/package/network/utils/iproute2/Makefile
b/package/network/utils/iproute2/Makefil
Utmp support tracks who is currenlty logged in by logging info to the file
/var/run/utmp (supported by busybox)
Putuline support will use the utmp structure to write to the utmp file
Signed-off-by: Hans Dedecker
---
package/network/services/dropbear/Config.in | 15 +++
package/netwo
Make sending a DHCP release configurable when the client exits allowing to
clean up
IP/mac state info in intermediate devices.
Signed-off-by: Hans Dedecker
---
v1 -> v2 : Make sending DHCP release configurable via uci
package/network/config/netifd/files/lib/netifd/proto/dhcp.sh | 8 +---
Hi,
I want to run an UART communication between the mt7688 and another
board, console uses UART0 but I want to configure UART1 to be able to
send data on it. Currently, if I send something on /dev/ttyS1, I get:
write to fd 4 failed: I/O error
or
ash: write error: I/O error
root@OpenWrt:/# stty -F
22 matches
Mail list logo
