On Wednesday, December 19, 2018 12:26:18 AM CET David Bauer wrote:
> Hello Christian,
>
> On 19.12.18 00:14, Christian Lamparter wrote:
> > I had no luck with a loaned EX6150v2 and this patch. I tried to sysupgrade
> > from the current -snapshot to a newly compiled image with the patch applied.
>
On Monday, December 17, 2018 11:08:00 PM CET Marius Genheimer wrote:
> SoC: Qualcomm IPQ4019 (Dakota) 717 MHz, 4 cores
> RAM: 256 MiB (Nanya NT5CC128M16IP-DI)
> FLASH: 128 MiB (Macronix NAND)
> WiFi0: Qualcomm IPQ4019 b/g/n 2x2
> WiFi1: Qualcomm IPQ4019 a/n/ac 2x2
> WiFi2: Qualcomm Atheros QCA9
Hello Christian,
On 19.12.18 00:14, Christian Lamparter wrote:
> I had no luck with a loaned EX6150v2 and this patch. I tried to sysupgrade
> from the current -snapshot to a newly compiled image with the patch applied.
> But sadly, the device didn't boot (power led stayed orange). I had to
> init
On Tuesday, December 18, 2018 2:27:20 AM CET David Bauer wrote:
> The NETGEAR EX61x0v2 does only validate the DNI header, neither it needs
> the kernel to be a specific size nor a fake filesystem header to be
> present.
>
> This has been tested using the NETGEAR Web-UI and the pushbutton TFTP
> re
CONFIG_COMPAT_BRK disables the heap randomization which is only needed
for very old and ancient user space applications, I am not aware that we
run any of these, just deactivate this option for these targets to allow
heap randomization.
Signed-off-by: Hauke Mehrtens
---
target/linux/at91/config-
Going back to my ancient cerowrt box, the stack space is actively being
relocated on this version, but marked executable...
7f8d4000-7f8f5000 rwxp 00:00 0 [stack]
7fff7000-7fff8000 r-xp 00:00 0 [vdso]
but there doesn't appear to be a vfp area on this ancient
Cutting this down a bit
>> Do the common MIPS CPUs support non executable stacks at all?
?
>> cpu_has_rixi is set to 0 for the ath79 SoCs for example, for lantiq some
Should this show up in /proc/cpuinfo? Or where?
>> automatic detection is done, but I haven't checked the result.
> ramips ha
On Tue, Dec 18, 2018 at 6:41 AM Hauke Mehrtens wrote:
>
> On 12/18/18 11:02 AM, Andre Heider wrote:
> > On 18/12/2018 01:44, Rosen Penev wrote:
> >> On Mon, Dec 17, 2018 at 4:34 PM Rosen Penev wrote:
> >>>
> >>> On Mon, Dec 17, 2018 at 3:40 PM Dave Taht wrote:
>
> John Crispin writes:
On Tue, Dec 18, 2018 at 2:35 AM Kevin 'ldir' Darbyshire-Bryant
wrote:
>
> Signed-off-by: Kevin Darbyshire-Bryant
> ---
>
> This patch, in a variety of forms, has been around since beginning 2016
> as e756c2bb07, ending up in present form 0aa6c7df60 (kernel 4.4.13 bump)
> and carried forward ever
Hauke Mehrtens writes:
> 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 open
On 12/18/18 11:02 AM, Andre Heider wrote:
> On 18/12/2018 01:44, Rosen Penev wrote:
>> On Mon, Dec 17, 2018 at 4:34 PM Rosen Penev wrote:
>>>
>>> On Mon, Dec 17, 2018 at 3:40 PM Dave Taht wrote:
John Crispin writes:
> On 17/12/2018 23:18, Dave Taht wrote:
>> Rosen Penev w
I'm doing some quick run time tests in QEMU, where I'm always greeted
with a bunch of quite useless error messages, so it would be nice if we
could relax them little bit and developers could always enable them if
needed anyway.
$ dmesg | grep -c 'gpio-nct5104d: Unsupported device 0x'
246
Interface triggers are installed by the dropbear init script in case an
interface is configured for a given dropbear uci section.
As dropbear is started after network the interface trigger event can be
missed during a small window; this is especially the case if lan is
specified as interface.
Fix t
On Tue, 18 Dec 2018 at 14:16, Hans Dedecker wrote:
>
> Interface triggers are installed by the dropbear init script in case an
> interface is configured for a given dropbear uci section.
> As dropbear is started after network the interface trigger event can be
> missed during a small window; this
Hi Hans,
> [...]
> +boot()
> +{
> + BOOT=1
> + start "@"
Typo here, should likely be "$@".
Otherwise Acked-by.
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://
Interface triggers are installed by the dropbear init script in case an
interface is configured for a given dropbear uci section.
As dropbear is started after network the interface trigger event can be
missed during a small window; this is especially the case if lan is
specified as interface.
Fix t
- it appears (at least from OS X verison 10.10, Yosemite) that the
big and little endian defintions have changed.
the older
#include
#include
reference yielded the following warning:
#define __bswap_16(x) NXSwapShort(x)
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 openwrt, or what prior releases... are
Signed-off-by: Kevin Darbyshire-Bryant
---
This patch, in a variety of forms, has been around since beginning 2016
as e756c2bb07, ending up in present form 0aa6c7df60 (kernel 4.4.13 bump)
and carried forward ever since.
There have been a number of MIPS kernel memory handling changes since,
inclu
It seems, that since Linux 4.18-rc1 rtc-ds1307 depends on hwmon-core.
commit 6b583a64fd1e019fd01626b46892ebf2361951c5
Author: Heiner Kallweit
Date: Wed Sep 27 22:41:26 2017 +0200
rtc: ds1307: simplify hwmon config
We don't have to define an extra config symbol, IS_REACHABLE does
kmod-w1 depends on kmod-hwmon-core since Linux 4.14
Signed-off-by: Petr Štetiar
---
Changes since v1:
* as Bjørn suggested, I've changed the kernel version selection as used in
31abe083311e ("kernel: Add missing dependency to kmod-regmap") to make it
more future proof
package/kernel/l
On 18/12/2018 01:44, Rosen Penev wrote:
On Mon, Dec 17, 2018 at 4:34 PM Rosen Penev wrote:
On Mon, Dec 17, 2018 at 3:40 PM Dave Taht wrote:
John Crispin writes:
On 17/12/2018 23:18, Dave Taht wrote:
Rosen Penev writes:
On Sun, Dec 16, 2018 at 4:54 PM Dave Taht wrote:
A pretty deep
Bjørn Mork [2018-12-18 09:53:36]:
> The futureproof(?) way to do this appears to be
>
> DEPENDS:=+!(LINUX_3_18||LINUX_4_9):kmod-hwmon-core
Yes, better. It's harder to read, but the commit message should make the
intention clear.
> See for example commit 31abe083311e ("kernel: Add missing dep
Petr Štetiar writes:
> It seems, that since Linux 4.18-rc1 rtc-ds1307 depends on hwmon-core.
>
> commit 6b583a64fd1e019fd01626b46892ebf2361951c5
> Author: Heiner Kallweit
> Date: Wed Sep 27 22:41:26 2017 +0200
>
> rtc: ds1307: simplify hwmon config
>
> We don't have to define an ext
Petr Štetiar writes:
> kmod-w1 depends on kmod-hwmon-core since Linux 4.14
>
> Signed-off-by: Petr Štetiar
> ---
> package/kernel/linux/modules/w1.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/kernel/linux/modules/w1.mk
> b/package/kernel/linux/modules/w1.
25 matches
Mail list logo
