This fixes system/system not properly loading due to themes being null.
Signed-off-by: Álvaro Fernández Rojas
---
v3: follow conventions as stated by rmilecki
v2: fix broken validation
diff --git a/luci2/htdocs/luci2/luci2.js b/luci2/htdocs/luci2/luci2.js
index 040f1e5..a2f10af 100644
--- a/luci
On 2014-11-21 21:10, Rafał Miłecki wrote:
> Signed-off-by: Rafał Miłecki
> ---
> V2: Don't touch ath9k as explained by Felix
Applied in r43339, thanks.
- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-
Signed-off-by: Rafał Miłecki
---
V2: Don't touch ath9k as explained by Felix
---
package/network/services/hostapd/Makefile | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/network/services/hostapd/Makefile
b/package/network/services/hostapd/Makefile
index d8b34
Quoting John Crispin :
Hi,
why the mt7610 requirement ? whr works well with a rt5592 as 5ghz and
the whr-1166 has mt7612 as 5ghz for which felix pushed the driver last
night. mt7610 is only used by the dir810 and there is no free driver for
that wifi chip.
so, to make sure i'm understanding
Quoting John Crispin :
Hi,
why the mt7610 requirement ? whr works well with a rt5592 as 5ghz and
the whr-1166 has mt7612 as 5ghz for which felix pushed the driver last
night. mt7610 is only used by the dir810 and there is no free driver for
that wifi chip.
ok, that might solve my problem, i
Hi,
why the mt7610 requirement ? whr works well with a rt5592 as 5ghz and
the whr-1166 has mt7612 as 5ghz for which felix pushed the driver last
night. mt7610 is only used by the dir810 and there is no free driver for
that wifi chip.
John
On 21/11/2014 14:27, Robert P. J. Day wrote:
>
Hello Rday,
you might check with the folks at asiarf.com. We buy and use several MT7620A and N routers from them. They all run CC
fine. Note that the DTS files for their eval boards are supported under the latest CC trunk. Also note that you may
need to modify the stock DTS files to support
On 2014-11-21 14:15, Rafał Miłecki wrote:
> Also drop ath9k dependency as it should use mac80211 anyway.
NACK for the included ath9k change, the config symbol is used to detect
the 802.11w capability. Simply removing it from PKG_CONFIG_DEPENDS
without touching the other place does not make sense.
P
[apologies for sending to both lists, i wanted to make sure i
caught everyone who might be interested; feel free to delete either
recipient when replying.]
following up on my earlier pleas for help with getting openwrt onto
*any* kind of mediatek-based router or eval board, i'm more tha
Also drop ath9k dependency as it should use mac80211 anyway.
Signed-off-by: Rafał Miłecki
---
Does this cleanup make a sense to you?
---
package/network/services/hostapd/Makefile | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/package/network/services/hostapd/Makefil
Hi Jaime,
On Nov 21, 2014, at 12:49 , Jaime T wrote:
> On 20 November 2014 20:49, Sebastian Moeller wrote:
>> Hi Jaime,
>> not an expert on adel modem errors, let alone lantiq, here is my attempt at
>> helping out:
>
> Hi Sebastien. Thank you for trying to help me - I appreciate it.
>
>>
Most TP-Link squashfs images are created using mktplinkfw -a 0x4
The "Rootfs data offset" in the header of those images is 0x0010. But
the rootfs actually starts at "Kernel data offset" + "Kernel data length".
As a result when extracting the rootfs with "mktplinkfw -x -i" the result
is broken.
On 20 November 2014 20:49, Sebastian Moeller wrote:
> Hi Jaime,
> not an expert on adel modem errors, let alone lantiq, here is my attempt at
> helping out:
Hi Sebastien. Thank you for trying to help me - I appreciate it.
> Maybe https://forum.openwrt.org/viewtopic.php?pid=222065 works
This adds support for the TP-LINK CPE210/220/510/520 (Pharos series). These
devices are very similar to the Ubiquiti NanoStations, but with better specs:
faster CPU, more RAM, 2x2 MIMO.
Signed-off-by: Matthias Schiffer
---
target/linux/ar71xx/base-files/etc/diag.sh | 3 +
.../ar71xx/ba
The new TP-LINK Pharos series uses a new bootloader, the "TP-LINK Safeloader".
It uses an advanced firmware image format, containing an image partition table
and a flash partition table (and image partitions are mapped to the
corresponding flash partitions). The exact image format is documented in
Hi,
this adds support for the new TP-LINK outdoor series CPE210/220/510/520
("Pharos"). I'm sending this as a RFC as there is a still a number of open
questions:
eth0 configuration
==
Looking at the log output of the stock firmware, it seems like the to ethernet
ports both have the
16 matches
Mail list logo
