blems and/or going to openwrt sites/lists for help
with non-stock and potentially getting rough or at least short treatment
as a result).
I've probably overdone it, and some things, like replacing openwrt-linux
with lede-linux as GCC OS might cause unnecessarily complications; my
goal wa
From: Daniel Dickinson
Branding: Rename openwrt to lede where appropriate
(although probably some unnecessary changes were made due
to not looking all that closely and doing a relatively mindless
(but not automatic) search and replace).
Probably this commit is incomplete and also has some
, ~MS_SYNCHRONOUS },
--
1.9.1
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
From: Daniel Dickinson
vfat is a common filesystem which users may want to mount on an
OpenWrt/LEDE device, so support peforming filesystem checks
before mount for vfat.
Signed-off-by: Daniel Dickinson
---
block.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git
usr/sbin/e2fsck";
/* UBIFS does not need stuff like fsck */
if (!strncmp(pr->id->name, "ubifs", 5))
--
1.9.1
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
From: Daniel Dickinson
Some users will want to use OpenWrt/LEDE devices as NAS
devices and have full POSIX ACL and user_xattr support
(along with other possible use cases), therefore add
support to mount with POSIX ACLs and/or user XATTR
support.
Signed-off-by: Daniel Dickinson
---
block.c
: Add support for checking vfat filesystems
[PATCH 3/4] [RFC] fstools: block.c: Use instead of defining mount
flags
[PATCH 4/4] [RFC] fstools: block.c: Add ability to mount with ACL and XATTR
support
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
;
va_end(arg2);
- ustream_printf(cl->us, "%X\r\n", len);
+ ustream_printf(us, "%X\r\n", len);
if (len < sizeof(buf))
- ustream_write(cl->us, buf, len, true);
+ ustream_write(us, buf, len, true);
else
- ustream_vprintf(cl->us, format, arg);
- ustream_printf(cl->us, "\r\n", len);
+ ustream_vprintf(us, format, arg);
+ ustream_printf(us, "\r\n", len);
}
-void uh_chunk_printf(struct client *cl, const char *format, ...)
+void uh_ustream_chunk_printf(struct client *cl, struct ustream *us, const char
*format, ...)
{
va_list arg;
va_start(arg, format);
- uh_chunk_vprintf(cl, format, arg);
+ uh_ustream_chunk_vprintf(cl, us, format, arg);
va_end(arg);
}
-void uh_chunk_eof(struct client *cl)
+static void ustream_chunk_eof(struct client *cl, struct ustream *us)
{
if (!uh_use_chunked(cl))
return;
@@ -94,7 +94,31 @@ void uh_chunk_eof(struct client *cl)
if (cl->state == CLIENT_STATE_CLEANUP)
return;
- ustream_printf(cl->us, "0\r\n\r\n");
+ ustream_printf(us, "0\r\n\r\n");
+}
+
+void uh_chunk_write(struct client *cl, const void *data, int len)
+{
+ uh_ustream_chunk_write(cl, cl->us, data, len);
+}
+
+void uh_chunk_vprintf(struct client *cl, const char *format, va_list arg)
+{
+ uh_ustream_chunk_vprintf(cl, cl->us, format, arg);
+}
+
+void uh_chunk_printf(struct client *cl, const char *format, ...)
+{
+ va_list arg;
+
+ va_start(arg, format);
+ uh_ustream_chunk_printf(cl, cl->us, format, arg);
+ va_end(arg);
+}
+
+void uh_chunk_eof(struct client *cl)
+{
+ ustream_chunk_eof(cl, cl->us);
}
/* blen is the size of buf; slen is the length of src. The input-string need
--
1.9.1
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
uest)(struct client *cl, char *url, struct path_info
*pi);
};
--
1.9.1
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
From: Daniel Dickinson
v2: Fix mixup of dosfsck checking ext* and e2fsck checking vfat.
vfat is a common filesystem which users may want to mount on an
OpenWrt/LEDE device, so support peforming filesystem checks
before mount for vfat.
Signed-off-by: Daniel Dickinson
---
block.c | 12
[PATCH 1/2] block.c: Make static string a const char * instead char *
[PATCH 2/2] block.c: Add support for checking vfat filesystems
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
From: Daniel Dickinson
vfat is a common filesystem which users may want to mount on an
OpenWrt/LEDE device, so support peforming filesystem checks
before mount for vfat.
Signed-off-by: Daniel Dickinson
---
block.c | 16 +++-
1 file changed, 11 insertions(+), 5 deletions(-)
diff
usr/sbin/e2fsck";
/* UBIFS does not need stuff like fsck */
if (!strncmp(pr->id->name, "ubifs", 5))
--
1.9.1
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
From: Daniel Dickinson
Some users will want to use OpenWrt/LEDE devices as NAS
devices and have full POSIX ACL and user_xattr support
(along with other possible use cases), therefore add
support to mount with POSIX ACLs and/or user XATTR
support.
Signed-off-by: Daniel Dickinson
---
block.c
, ~MS_SYNCHRONOUS },
--
1.9.1
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Tested on ar71xx (Netgear WNDR3800) on ext4 with the right kernel support.
[PATCH 1/2] block.c: Use instead of defining mount flags
[PATCH 2/2] block.c: Add ability to mount with ACL and XATTR support
___
Lede-dev mailing list
Lede-dev
P-LINK TL-WR841N/ND v1.5
diff --git a/target/linux/ar71xx/mikrotik/config-default
b/target/linux/ar71xx/mikrotik/config-default
index 65bed3f..e17b166 100644
--- a/target/linux/ar71xx/mikrotik/config-default
+++ b/target/linux/ar71xx/mikrotik/config-default
@@ -98,6 +98,7 @@ CONFIG_ATH79_MACH_RBSXTLITE=y
# CONFIG_ATH79_MACH_TL_WR720N_V3 is not set
# CONFIG_ATH79_MACH_TL_WR741ND is not set
# CONFIG_ATH79_MACH_TL_WR741ND_V4 is not set
+# CONFIG_ATH79_MACH_TL_WR802N_V1 is not set
# CONFIG_ATH79_MACH_TL_WR841N_V1 is not set
# CONFIG_ATH79_MACH_TL_WR841N_V8 is not set
# CONFIG_ATH79_MACH_TL_WR841N_V9 is not set
--
2.9.3
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
(and freifunk) a couple of years (and try use LEDE
now), so it was a good style for us to payback the active community. And
IMHO better then collecting cash via patreon's "Klingelbeutel".
Our office is in Hamburg, but we want open a small office in Leipzig
this year (asap).
Is th
Hi Daniel,
as I already says: I think it was good way to payback the active
community. So we talking about the possibility for you to continue your
work on lede-project.org, but as an employer in our company.
I have a the moment not enough time to a detailed answer your mail, but
I can understand
that you talk directly rather than through the mailing list?
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
ES := kmod-mt7603 kmod-usb3 kmod-usb-ledtrig-usbport
wpad-mini
+ DEVICE_PACKAGES := \
+ kmod-mt7603 kmod-mt76x2 kmod-usb3 kmod-usb-ledtrig-usbport
kmod-mt76 \
+ wpad-mini
endef
TARGET_DEVICES += 11acnas
-- 2.1.4
--- End Message ---
__
ps://blog.andi95.de/>
PGP:0xB7E04818
___
openwrt-devel mailing list
openwrt-de...@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
--- End Message ---
___
Lede-dev
42, Philip Prindeville wrote:
On Nov 1, 2017, at 8:36 PM, Philip Prindeville
wrote:
Can someone else please try to reproduce this?
I’m using busybox’s wget on x86_64 hardware, and when I do a “wget” of 2 http:
URI’s, it mangles the second URI’s derived filename:
root@lede:/tmp/x# c
Downloa
nterested about porting LEDE on it. It looks like typical
MT7621A board which has PCIe slot instead of MT7603 & MT7612.
... or something much similar to Firefly FireWRT
(https://wikidevi.com/wiki/Firefly_FireWRT unfortunately, discontinued
due to its manufacturing cost)
I successfully p
board with 2 ethernet ports. I connect the WAN port to
another router and the LAN port to my laptop. During boot, my laptop
gets an IP address from the parent router, because it seems that kernel
is forwarding packets when lede has not started up completely.
When boot finished I should renew m
esterday many times with the same router,
which increases my confusion)
any pointer is much appreciated :)
ps: using lede
Reboot (17.01-SNAPSHOT, r3285-111cf1b)
built using SDK, so binaries are exactly the same as upstream
(thanks Daniel Golle for t
ngs i come across while using LEDE 17.01.0 on a
TL-WR842ND
a strange crash in wifi:
http://pastebin.com/THLMDT6C
WARNING: CPU: 0 PID: 22264 at
compat-wireless-2016-10-08/net/mac80211/sta_info.c:451 0x80e84f90
[mac80211@80e8+0x5f540]()
does that ring a bell for anyone?
or is just a harmle
tart" forcing a config change (new dns
> black list) and followed by the delayed procd trigger.
ok, but even in this case, at least one of the two processes should be
able to start it up, and not die both :P
>
> - Eric
--- End Message ---
___
This one I also have no clue about. It didn't even make it to the "realstart"
> part. So checking further what happened in between was causing that should be
> helpful
>
> Wed Mar 22 18:26:10 2017 user.notice root: guidebug dnsmasq init
> Wed
5:13, Koen Vandeputte wrote:
>
>
> On 2017-03-23 02:30, Gui Iribarren via Lede-dev 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, t
niel Golle wrote:
> Hi Pau,
>
> On Tue, Mar 28, 2017 at 09:28:22PM +0200, Pau wrote:
>> Hi.
>>
>> I am using the SDK and IB from LEDE 17.01.0 release (mips_24kc). I've
>> been using it successfully the last days until now. I did not change
>> anything but I
q realstart
>> cfg02411c wait 20
>> Wed Mar 22 18:26:08 2017 user.notice root: guidebug dnsmasq realstart
>> cfg02411c wait 18
>>
>> This one I also have no clue about. It didn't even make it to the
>> "realstart"
>> part. So checking further what happened in between was causing that should
>> be
>> helpful
>>
>> Wed Mar 22 18:26:10 2017 user.notice root: guidebug dnsmasq init
>> Wed Mar 22 18:26:10 2017 user.notice root: guidebug dnsmasq reload
>> Wed Mar 22 18:26:10 2017 user.notice root: guidebug dnsmasq startsrv ,
>>
>
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
XZ_DEC_ARM=y
CONFIG_XZ_DEC_BCJ=y
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
4 target,
why not also do the same to armvirt? After all, both are mostly virtual
targets and from what I can tell, it's just ARMv8 vs ARMv7
(or maybe can these be folded into one?)
Regards,
Christian
--- End Message ---
_______
Lede-dev mailing lis
hcd xhci-hcd.0.auto: Cannot set link state.
[ 31.357151] usb usb2-port1: cannot disable (err = -32)
Can you please check the usb port functionality on your board too?
- the board fails to reboot / restart.
The WPJ428 LEDE-Image will just freeze. The FB4040 and RT-AC58U doesn't
have no i
AM devices like the Asus RT-AC58U.
> > + local-mac-address = [00 00 00 00 00 00];
> > +- vlan_tag = <1 0x1f>;
> > ++ qcom,phy-mdio-addr = <4>;
> > ++ qcom,poll-requ
and IPQ806x AP148 Board:
> a. NAND boot
> b. ubi sysupgrade
>
> Signed-off-by: Ram Chandra Jangir
Thanks for posting this.
Chris Blake is currently in the process of adding the Cisco Meraki MR33.
<https://github.com/riptidewave93/LEDE-MR33>
The MR33 uses the IPQ4029 and has j
dent young-timers knows XMMS? Once upon a time this
was a household name (FOSS folks houses). Now I reckon those who use it
as a primary player do it for nostalgia.
Likewise, OpenWRT while more recognizable than LEDE, is not worth as
much as people here paint it, and will only remain relevant
d out.
Regards,
Christian
--- End Message ---
_______
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
ze: 2048, OOB
size: 64
[1.018135] 11 ofpart partitions found on MTD device qcom_nand.0
[1.025449] Creating 11 MTD partitions on "qcom_nand.0":
so, it's working now.
Regards,
Christian
--- End Message ---
___
Lede-dev mailing list
gt; [ 1.68] invalid GPIO -22
> [ 1.69] Modules linked in:
> [ 1.69] CPU: 3 PID: 1 Comm: swapper/0 Not tainted 4.4.61 #0
>
> seems not to find the i2c-pca and it's gpios, as these modules are not
> compile into the kernel.
> [ 10.46] kmodloader: loading kern
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,
Compile and run tested on ip
ac1 for LAN group,
> existing ipq806x boards are also following the same, and we would like to
> continue with the same convention. I do not see any reason to deviate this
> in ipq40xx based boards.
>
> I agree that ac58u nbg6617 and fritz4040 needs some changes, and Christian
amp; {
- local kern_ubivol="$(nand_find_volume $ubidev kernel)"
+ local kern_ubivol="$(nand_find_volume $ubidev $CI_KERNPART)"
tar xf $tar_file sysupgrade-$board_name/kernel -O | \
ubiupdatevol /dev/$kern_ubivol -s $kernel_length -
}
--
2.11.0
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
y does the package prosody is missing for the
following x86 targets?
packages-17.01/i386_geode
packages-17.01/i386_i486/
packages-17.01/i386_pentium
packages-17.01/i386_pentium4
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradea
y() is
+unable to detect the AR8035 PHY. As a result, the emac driver
+bails out early and the user left with no ethernet.
+
+In order to stay compatible with existing configurations, the driver
+tries the current reset approach at first. Only if the first attempt
+timed out, it does perform one mor
rt288x is completely missing from the 17.01.2 download pages
(ie. https://downloads.lede-project.org/releases/17.01.2/targets/ramips) it was
there for 17.01.1 BTW. Could someone please investigate the reason it's
missing and remedy it. The device page
(https://lede-project.org/toh/hw
mv88e6060 1902 0
I would like to have working ethernet on WRT300N. Or is it possible without
mv88e6060? I found in some Chinese forum that people got it working, but
no info how it was done.
Regards,
Nerijus
--- End Message ---
___
Lede-d
his driver is quite useless on their own. It
requires some assistance to properly detects switch IC either from
arch code via platform device data or via DTS.
Try to use OpenWRT/LEDE specific driver, which is used by ath25 and
ar7 platforms by enabling CONFIG_MVSWITCH_PHY option in the kernel.
to use mv88e6060.ko which
should use CONFIG_MVSWITCH_PHY or is CONFIG_MVSWITCH_PHY alone enough?
This driver uses VLAN tags to determine which port the frame should be
sent from. Try to create couple of VLAN sub-interfaces on eth0 with ID
1 and 2 and work with them.
I'll try.
And BTW d
AN tags to determine which port the frame should be
sent from. Try to create couple of VLAN sub-interfaces on eth0 with ID
1 and 2 and work with them.
I'll try.
Yes, use the latest version of LEDE, please, to avoid facing with
long-forgotten bugs.
Tried the latest LEDE. Now I see
8, Nerijus Baliūnas via Lede-dev rašė:
How do I configure vlan? Here I changed eth0 to eth0.1:
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.1.1'
opt
.
How do I add it? I added swconfig to target/linux/ixp4xx/Makefile:
DEFAULT_PACKAGES += ixp4xx-microcode fconfig swconfig
but still no swconfig in generated lede-ixp4xx-generic-squashfs.img.
Thanks,
Nerijus
--- End Message ---
___
Lede-dev mailing
ed in order to
> get the switch working? Because by default it is not installed.
>
>
> Yes, it is necessary with this switch driver to have swconfig installed,
> otherwise nothing would push CLEAN configurations to the mv88e6060 switch.
I added swconfig, but still no network with the above config.
Could you please give some hints if the above switch config is correct?
Regards,
Nerijus
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
7 21:31:01 +0300 Sergey Ryazanov
wrote:
> > Tried the latest LEDE. Now I see in the boot log:
> > [6.507617] NPE-B: firmware's license can be found in
> > /usr/share/doc/LICENSE.IPL
> > [6.515168] NPE-B: firmware functionality 0x2, revision 0x2:1
> > [
: MII read [3] -> 0x0
[1.003068] libphy: IXP4xx MII Bus: probed
[1.010033] eth0: MII PHY 32 on NPE-B
[1.014186] IXP4xx MII Bus #1: MII read [1] -> 0x7849
[ 1.014288] IXP4xx MII Bus #1: MII read [0] -> 0x1000
[1.014393] IXP4xx MII Bus #1: MII write [0] <- 0x1000, err = 0
[1.016811] eth1: MII PHY 1 on NPE-C
Regards,
Nerijus
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
+along with this program. If not, see <http://www.gnu.org/licenses/>.
+ */
+
+-#include
+ #include "dnsmasq.h"
+
+ #ifdef HAVE_SCRIPT
--
2.14.1
--- End Message ---
_______
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://l
rcepted,
corrupted, lost, destroyed, arrive late, incomplete or contain viruses. The
sender, therefore, does not accept liability for any errors or omissions in the
contents of the message.
--- End Message ---
_______
Lede-dev mailing list
Lede-dev
. I had some success with it
on the RT-AC58U. All I needed there was to add a custom
definition for the Winbond W25N01GV chip [0] and enable
CONFIG_MTD_SPINAND_MT29F=y
CONFIG_MTD_SPINAND_ONDIEECC=y
Maybe you too can get away with something similar to this?
Until linux-mtd _finally_ knows what they w
195 Mbps = 0.3949 ~ 40%
Regards,
Christian
--- End Message ---
_______
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
arget/linux/pistachio/patches-4.4/0001-mtd-nand-Introduce-SPI-NAND-framework.patch
commit message:
"5. mtd: spi-nand: Support common SPI NAND devices
This commit uses the recently introduced SPI NAND framework to support
Micron MT29F and Gigadevice GD5F serial NAND devices. These two fam
read [3] -> 0x602
> [0.998319] IXP4xx MII Bus #29: MII read [2] -> 0x0
> [0.998420] IXP4xx MII Bus #29: MII read [3] -> 0x602
> [1.21] IXP4xx MII Bus #30: MII read [2] -> 0x0
> [1.000120] IXP4xx MII Bus #30: MII read [3] -> 0x0
> [1.001588] IXP4xx MII Bus #31: MII read [2] -> 0x0
> [1.001687] IXP4xx MII Bus #31: MII read [3] -> 0x0
> [1.003068] libphy: IXP4xx MII Bus: probed
> [1.010033] eth0: MII PHY 32 on NPE-B
> [1.014186] IXP4xx MII Bus #1: MII read [1] -> 0x7849
> [1.014288] IXP4xx MII Bus #1: MII read [0] -> 0x1000
> [1.014393] IXP4xx MII Bus #1: MII write [0] <- 0x1000, err = 0
> [1.016811] eth1: MII PHY 1 on NPE-C
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
] 1c00.uartlite: ttyS1 at MMIO 0x1c00 (irq = 20,
> base_baud = 2500000) is a Palmchip BK-3103
> [0.680207] spi spi0.0: force spi mode3
>
> With swapped items in rt5350.dtsi
> [0.564356] gpio-export gpio_export: 3 gpio(s
; >}
> >
> > -if (ttl != 255)
> > -return;
> > -
> >if (debug > 1) {
> >char buf[256];
> >
> > @@ -310,9 +307,6 @@ read_socket6(struct uloop_fd *u, unsigned int events)
> >}
> > }
> >
cat */*/phy_id
0x8201
0x088e6060
0x01410c87
0x01410c87
0x01410c87
0x01410c87
0x0000
0x
0x
0x0602
0x0602
0x0602
0x0602
0x00000602
0x0602
0x
0x
Regards,
Nerijus
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
ned because PHY ID for eth0 is
> hardcoded inside WRT300Nv2 setup code.
>
> To check whether your board can act without dedicated driver for 88E6060:
> * revert any earlier modifications to LEDE if you do any
> * disable any drivers for 88E6060 (e.g. disable both
> CONFIG_NET_DS
0
RX bytes:92 (92.0 B) TX bytes:1551 (1.5 KiB)
Ping still does not answer.
Regards,
Nerijus
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
de
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[ 10.310754] mount_root: jffs2 not ready yet, using temporary tmpfs overlay
[ 10.359891] urandom-seed: Seed file not found (/etc/urandom.seed)
[ 10.492841] eth0: link down
Regards,
Nerijus
--- End Message --
ed:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:1551 (1.5 KiB)
Ping to neither 192.168.1.1 nor 192.168.0.10 does not answer.
Regards,
Nerijus
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
p again.
Regards,
Nerijus
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
urandom.seed
[ 10.553168] eth0: link down
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
gt; Check, please, memory information and list of loaded kernel modules:
> # cat /proc/meminfo
> # lsmod
root@LEDE:/# free
total used free sharedbuffers cached
Mem: 12232 11352880 40632 2420
-/+ buffers/ca
7 23:28:00 +0300 Sergey Ryazanov
wrote:
> > root@LEDE:/# cat /proc/meminfo
> > MemTotal: 12232 kB
> > MemFree: 996 kB
>
> Looks like this ^^^ is the cause of the "ifconfig up" failure. Your
> board really have not free RAM.
>
> As a qui
kB
# ifconfig eth0 down
# cat /proc/meminfo
MemTotal: 12232 kB
MemFree:2136 kB
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Nerijus
--- End Message ---
_______
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
y will be ready.
Thank you. Another question about wifi - there is no /etc/config/wireless
file, and even if I create it and reboot the device, wifi is not working
and there is no wlan0 interface. ath5k module is loaded.
Regards,
Nerijus
--- End Message ---
____
576 kB
Regards,
Nerijus
--- End Message ---
_______
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Yún uses packets.
Jay
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
(White Box/Lede 100% Compatible) wireless router supplier.
If anyone has any recommendation.
Must have:
Dual Band (2.4/5.8Ac)
At least 4 gigabit ports.
2 or more external antennas.
Case: ISP providing wireless for customers,bulk order.
--- E
;, \
> + g++ -dumpversion | grep -E
> '(4\.[8-9]|5\.[0-9]|6\.[0-9]|^7|7\.[0-9])', \
> g++48 --version | grep g++, \
> g++49 --version | grep g++, \
> g++5 --version | grep g++, \
> g++6 --version | grep g++, \
>
7;w':
return jshn_format(no_newline, indent);
case 'n':
diff --git a/sh/jshn.sh b/sh/jshn.sh
index bf76edb..0a146e1 100644
--- a/sh/jshn.sh
+++ b/sh/jshn.sh
@@ -174,6 +174,10 @@ json_load() {
eval "`jshn -r "$1"`"
}
+json_load_file() {
+ eval &q
ot;emr3k:".
Anyone any hints on what I might be missing?
Could it be that the way to generate a sysupgrade image has changed? Here's
what I'm using for emr3000 (and what works with 4.4):
https://github.com/bk138/source/blob/emr3000-wip/target/linux/ar71xx/image/senao.mk
Thanks in advance,
Christian
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
b 19 18:04
openwrt-toolchain-mpc85xx-p1020_gcc-5.5.0_musl.Linux-x86_64.tar.bz2
-rw-r--r-- 1 jeclark2006 jeclark2006 1108 Feb 19 18:04 sha256sums
John Clark.
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.inf
r expanding .config and _more_ local customizations applied as
> local customizations :)
>
> Cheers,
> Karl Palsson
>
>
> ___
> openwrt-devel mailing list
> openwrt-de...@lists.openwrt.org
> https://lists.openwrt.org/cgi
is is not what you want!
--- End Message ---
_______
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
8 at 02:24:57PM -0600, Philip Prindeville wrote:
> Collected errors:
> * check_data_file_clashes: Package bind-check wants to install file
> /home/philipp/lede/build_dir/target-x86_64_musl/root-x86/usr/sbin/named-checkconf
> But that file is already provided by
Number of Spatial Streams seen in mesh
beacons and in mesh data packet?
Thanks,
Ashok
--- End Message ---
_______
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
0211AC=y, sends mesh peering messages and creates peers
without AC support, causing firmware to get confused. After
recompiling supplicant with the correct flag, no more crashes were
observed in casual testing. I submitted a pull request to LEDE to,
hopefully, fix it in upstream.
Best regards,
re 11n only capable nodes in
> an 11s mesh?
>
>
>
> -adrian
--- End Message ---
_______
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
k that's the support for the RT-AC58U is now mostly complete.
I haven't heard any complains and there seem to be people using it.
Regards,
Christian
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
ee up some resources.
> >
> > Cc: John Crispin
> > Signed-off-by: Christian Lamparter
>
> sorry took me ages to build/boot an image. merged into my staging tree
> just now
Looks like this was silently dropped? Doesn't the CPU like NEON/VFPV4
or was the p
use 1.1.16 which unfortunately has the downside that
it's not getting updated automatically.
[0]
<https://github.com/chunkeey/LEDE-IPQ40XX/commit/4c487165ff074e2f3fe7116140d1d9cded95b018>
Regards,
Christian
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
at 5:17 PM, antonio rossi wrote:
> Hi everybody,
>
> i'll try to make this as short as possible despite the large amount of
> information needed to describe the issue:
>
> i am working on adding support to LEDE/OpenWRT for DIR-815 A1, it's a
> RT3662+RT3092 device with
y only AES-GCM)
> * ECDH key exchange for control channel
> * LZ4 compression support
it seems that there's a small compatibility problem for "older VPN
servers" with OpenVPN 2.4 and mbedTLS:
TLS-DHE-* ciphers don't seem to be supported anymore. I'm not sure if
that's
nt of
> >> information needed to describe the issue:
> >>
> >> i am working on adding support to LEDE/OpenWRT for DIR-815 A1, it's a
> >> RT3662+RT3092 device with an infamous IP175D switch IC.
> >> i managed to get everything working properly, save for
index.php?do=details&task_id=350
[1]
https://git.lede-project.org/?p=source.git;a=commitdiff;h=6b94234a6598b855573a6516494de8e7d755e944
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
te all daemons en mass to be run under runit.
>> We can try it with, say, ntpd first. If it goes well, we'd use it
>> for more and more things. If it goes badly, we drom it.
>>
>> Thoughts?
>
> Here's the thing: OpenWrt/LEDE is starting services via procd.
> This is a
n't
want bootloader's init arg")?
>> - reverting my patch and enabling CONFIG_MIPS_CMDLINE_DTB_EXTEND would
>> fix #2 and #3 while #1 is broken again
>> - not reverting my patch, enabling CONFIG_MIPS_CMDLINE_DTB_EXTEND and
>> adding a "black- o
xisting
soc_mt7620 code). The RT3883/3662 just lacks the internal switch otherwise
it looks to be the same.
Regards,
Christian
--- End Message ---
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
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 ---
This patch updates musl to 1.1.16
1 - 100 of 159 matches
Mail list logo
