Hi,
this is more like my todo list shared with 蝈蝈 (Guo), but I hope, that I
could get some inputs from others as well. I'm aware about following issues
with ath79 on ar9342 so far, and I don't know how to fix some of them
properly. BTW, everything described bellow works fine on ar71xx using 4.14
This adds a hotplug function to (re-)start inittab entries with askfirst or
respawn.
At the moment the devices used with these actions must be present during boot
otherwise such lines are skipped.
However, this prevents having inittab entries with consoles for e.g. USB gadget
devices which only
This is a trial to make it more obvious what the historically
grown code is actually doing.
Signed-off-by: Michael Heimpold
---
v2: use Jo-Philipp Wich's proposal
inittab.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/inittab.c b/inittab.c
index 4b9..c9e6c13
This series extends procd to allow starting consoles for devices which
are not present during boot or after kernel module loading. This is
for example the case when a USB gadget serial device is created with
configfs. Here the kernel module is loaded but the tty device only
appears after gadget is
Signed-off-by: Michael Heimpold
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index 9d80a74..eaf1ef4 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,6 +2,7 @@ procd
askfirst
udevtrigger
init
+upgraded/upgraded
.*
Makefile
CMakeCache.txt
--
Signed-off-by: Michael Heimpold
---
inittab.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/inittab.c b/inittab.c
index b8552e9..18023f5 100644
--- a/inittab.c
+++ b/inittab.c
@@ -123,6 +123,11 @@ static void child_exit(struct uloop_process *proc, int ret)
DEBUG(4, "pid:%d,
Signed-off-by: Michael Heimpold
---
initd/init.c| 2 +-
initd/preinit.c | 6 +++---
initd/zram.c| 4 ++--
plug/coldplug.c | 3 ++-
plug/hotplug.c | 14 +++---
upgraded/upgraded.c | 2 +-
6 files changed, 16 insertions(+), 15 deletions(-)
diff --git
Usually respawn(), askfirst(), askconsole() and rcrespawn() are run only
one time to start a worker child for the given inittab entry.
In case we want to allow calling these functions several times, we need
to ensure that we do not start multiple workers at the same time for the
same inittab
In case we want to process an inittab item multiple times (e.g. in case
of hotplugging) we must not shift the arguments for askfirst multiple
times. So check whether we already did it.
Signed-off-by: Michael Heimpold
---
inittab.c | 18 --
1 file changed, 12 insertions(+), 6
I have found that my ath9k-based WiFi card is malfunctioning with recent
OpenWrt master builds. I build things myself, but my configuration
(both the build configuration and /etc/config/wireless and so on) has
not changed other than doing a "git pull" to get the latest source from
Daniel Golle [2019-01-01 17:56:25]:
Hi,
> On Sun, Dec 30, 2018 at 11:26:58AM +0100, Petr Štetiar wrote:
> > Daniel Golle [2018-12-29 06:51:32]:
> >
> > > config KERNEL_AIO
> > > config KERNEL_FHANDLE
> > > config KERNEL_FANOTIFY
> > > + default y if !SMALL_FLASH
> >
> > What about
On Tue, Jan 1, 2019 at 9:44 AM Hauke Mehrtens wrote:
>
> On 12/18/18 12:46 PM, Hauke Mehrtens wrote:
> > On 12/17/18 1:54 AM, Dave Taht wrote:
> >>
> >> A pretty deep look at home MIPS and arm routers, and a surprising bug in
> >> Linux/MIPS - by mudge and co:
> >>
> >>
Hi Christian,
On 01.01.2019 18:23, Christian Lamparter wrote:
On Tuesday, January 1, 2019 1:03:22 PM CET Christoph Krapp via openwrt-devel
wrote:
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate
01/01/2019 18:23, Christian Lamparter:
The "Device/glinet_ar750s" change to "Device/glinet_gl-ar750s" will likely
break sysupgrade from existing "glinet_ar750s" images. This is because the
now deprecated glinet_ar750s identifier was not added to the
SUPPORTED_DEVICES variable. Other than that,
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 ---
> I had this problem (DMARC
Hardware
CPU: Qualcomm Atheros QCA9558
RAM: 128M DDR2
FLASH: 16MiB
ETH: 1x Atheros AR8035 (PoE in)
WiFi2: QCA9558 2T2R
WiFi5: QCA9880 2T2R
BTN: 1x Reset
LED: 1x LED blue
1x LED red
BEEP: 1x GPIO attached piezo beeper
UART: 3.3V GND TX RX (115200-N-8) (3.3V is square
Hardware
CPU: Qualcomm Atheros QCA9558
RAM: 128M DDR2
FLASH: 16MiB
ETH: 1x Atheros AR8035 (PoE in)
WiFi2: QCA9558 3T3R
WiFi5: QCA9880 3T3R
BTN: 1x Reset
LED: 1x LED blue
1x LED red
BEEP: 1x GPIO attached piezo beeper
UART: 3.3V GND TX RX (115200-N-8) (3.3V is square
On 12/18/18 12:46 PM, Hauke Mehrtens wrote:
On 12/17/18 1:54 AM, Dave Taht wrote:
A pretty deep look at home MIPS and arm routers, and a surprising bug in
Linux/MIPS - by mudge and co:
https://cyber-itl.org/2018/12/07/a-look-at-home-routers-and-linux-mips.html
I have no idea if current
On Tuesday, January 1, 2019 1:03:22 PM CET Christoph Krapp via openwrt-devel
wrote:
> 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
>
This patch adds the boot-part feature which enables the brcm2708
target move from the custom boot partition size config option to
the generic CONFIG_TARGET_KERNEL_PARTSIZE.
Note:
For people using custom images: Just like with
CONFIG_TARGET_ROOTFS_PARTSIZE changing the value
can cause sysupgrade
Initially this patch was introduced as a quick fix following
the removal of 936-ath10k_skip_otp_check.patch which caused
multiple ath10k pcie devices in various ipq806x and ar71xx/ath79
targets to malfunction.
Thankfully, the affected devices have been updated to utilize
the pre-caldata method.
Christian Lamparter [2018-12-31 17:41:34]:
> I hope you know what you are up against because unless you also do the changes
> upstream this will happen again and again. :\ / :)
My plan is to first wait for comments here, see if it gets merged eventualy
and then start poking upstream. I still
Hi!
On Sun, Dec 30, 2018 at 11:26:58AM +0100, Petr Štetiar wrote:
> Daniel Golle [2018-12-29 06:51:32]:
>
> > config KERNEL_AIO
> > config KERNEL_FHANDLE
> > config KERNEL_FANOTIFY
> > + default y if !SMALL_FLASH
>
> What about `FEATURES += nas` to make it clear and don't abuse
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 ---
As the official device name is
24 matches
Mail list logo
