On Wed, 2017-02-15 at 14:03 -0800, Russell Senior wrote:
>
> I just tried r3499 (master branch), and it works too,
Nice. Do you want to reinstate the default configuration for it, which
was removed in commit 9e0759ea2? See how I've just done it for Geos.
Wha
t is in /tmp/sysinfo/board_name?
You
This is needed to use the nflog interface with tcpdump
Signed-off-by: Martin Schiller
---
package/libs/libpcap/Config.in | 5 +
package/libs/libpcap/Makefile | 7 +--
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/package/libs/libpcap/Config.in b/package/libs/libpcap/Co
I am experimenting with UEFI boot for LEDE x86_64 image.
Currently, lede-x86_64-vmlinuz boots fine on UEFI - both on MBR and GPT
disk, by chainloading via grub or directly launching the kernel via EFI
shell.
There is no support in the kernel for EFI framebuffer, so a serial
interface is needed to
Signed-off-by: David Woodhouse
---
package/firmware/linux-firmware/ti.mk | 13 +
1 file changed, 13 insertions(+)
diff --git a/package/firmware/linux-firmware/ti.mk
b/package/firmware/linux-firmware/ti.mk
index a1e12fc..ba1baa9 100644
--- a/package/firmware/linux-firmware/ti.mk
+++
Update mt76 Makefile to latest github revision.
Signed-off-by: L. D. Pinney
---
package/kernel/mt76/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/kernel/mt76/Makefile b/package/kernel/mt76/Makefile
index 5e7761093c..658a3191b1 100644
--- a/package/ker
On 2017-02-16 12:04, L. D. Pinney wrote:
> Update mt76 Makefile to latest github revision.
>
> Signed-off-by: L. D. Pinney
NACK. 17.01 doesn't have the necessary changes to ramips .dts files, and
I see no good reason to update mt76 in the branch now.
- Felix
Without the updated Makefile I have this error :
make[3]: Entering directory '/data/LEDE-17.01/package/kernel/mt76'
. /data/LEDE-17.01/include/shell.sh; xzcat
/data/LEDE-17.01/dl/mt76-2017-01-31-3c8caafc.tar.xz | tar -C
/data/LEDE-17.01/build_dir/target-mipsel_24kc_musl-1.1.16/linux-ramips_mt7628/
On 2017-02-16 12:21, L. D. Pinney wrote:
> Without the updated Makefile I have this error :
>
> make[3]: Entering directory '/data/LEDE-17.01/package/kernel/mt76'
> . /data/LEDE-17.01/include/shell.sh; xzcat
> /data/LEDE-17.01/dl/mt76-2017-01-31-3c8caafc.tar.xz | tar -C
> /data/LEDE-17.01/build_di
On Thu, Feb 16, 2017 at 5:27 AM, Felix Fietkau wrote:
> On 2017-02-16 12:21, L. D. Pinney wrote:
>> Without the updated Makefile I have this error :
>>
>> make[3]: Entering directory '/data/LEDE-17.01/package/kernel/mt76'
>> . /data/LEDE-17.01/include/shell.sh; xzcat
>> /data/LEDE-17.01/dl/mt76-20
Whoops, still missed the lede-dev list...
yousong
-- Forwarded message --
From: Yousong Zhou
Date: 16 February 2017 at 21:52
Subject: Re: [LEDE-DEV] Makefile question
To: Philip Prindeville
Cc: David Lang , Felix Fietkau
On 16 February 2017 at 09:38, Philip P
Hi Felix,
Hi Tim,
commit "imx6: move to Linux 4.9 kernel" introduces some regression on
wlan level.
When starting wpa_supplicant to initiate an IBSS link, the handshake fails.
Inspecting it reveals that no data packets are transceived (both TX & RX).
Beacon frames seem to come in, as scannin
Hi list,
I just pushed an experimental commit to my staging tree which updates
opkg to an improved custom LEDE fork [1] which attempts to minimize the
memory usage requirements to make opkg usable on low memory devices again.
Some preliminary testing on virtual and physical x86/64 targets showed
Mathias,
I have just come across a weird side effect of the following change.
With the patch applied it is no longer possible to communicate via the
red Ethernet between 2 BT Home Hub 5, but communications are fine
between a HH5 and any other device (??).
diff --git a/target/linux/lantiq/dts
The feeds script sets value of TOPDIR in a way that is inconsistent
with how toplevel Makefile sets it. The inconsistency manifests when I
use a "build directory" with symlinks to LEDE source (see below).
When make is invoked in such a directory, make's TOPDIR variable is
set to that directory, wh
14 matches
Mail list logo
