On 2013-09-04 7:37 PM, Luis R. Rodriguez wrote:
> On Thu, Aug 29, 2013 at 06:12:02PM +0200, Felix Fietkau wrote:
>> On 2013-08-28 10:30 PM, Luis R. Rodriguez wrote:
>> > From: "Luis R. Rodriguez"
>> >
>> > The mac80211.sh script uses readlink -f which requires
>> >
>> > CONFIG_BUSYBOX_CONFIG_REA
Added Asmax AR 1004g router
Signed-off-by: Adrian Feliks
--
--- a/arch/mips/bcm63xx/boards/board_bcm963xx.c
+++ b/arch/mips/bcm63xx/boards/board_bcm963xx.c
@@ -67,7 +67,6 @@
#define CT6373_SPI_GPIO_CLK6
This patch updates the lighttpd package to version 1.4.32
The makefile has been reworked and uses a macro for module creation
The config file has been updated to include module dependant configuration from
conf.d subdirectory
Signed-off-by: Gerald Matzka
diff --git a/net/lighttpd/Makefile b/ne
On 2013-09-05 8:15 PM, Luis R. Rodriguez wrote:
> Thanks, odd though I don't see that on the git tree [0], I see r37897
> and r37895 but not r37896. Is this in another tree perhaps?
>
> git://nbd.name/openwrt.git
That repo only contains changes from trunk. AA is here:
http://git.openwrt.org/?p=12.
On Thu, Sep 5, 2013 at 2:46 AM, Felix Fietkau wrote:
> On 2013-09-04 7:37 PM, Luis R. Rodriguez wrote:
>> On Thu, Aug 29, 2013 at 06:12:02PM +0200, Felix Fietkau wrote:
>>> On 2013-08-28 10:30 PM, Luis R. Rodriguez wrote:
>>> > From: "Luis R. Rodriguez"
>>> >
>>> > The mac80211.sh script uses rea
I've updated the Bitlbee package from version 1.0.1 to version 3.2 and added a new package for
libotr which is used by the optional CONFIG_BITLBEE_OTR setting for off-the-record encryption support.
I had originally compiled with openssl but had to move to gnutls for Jabber to successfully
negot
On 09/04/2013 03:24 PM, Helmut Schaa wrote:
> Hi Hauke,
>
> Booting a pretty decent x86 OpenWrt within KVM gives me a bunch of
> Symbol errors in b44:
>
> [2.291153] b44: Unknown symbol ssb_device_is_enabled (err 0)
> [2.294154] b44: Unknown symbol ssb_pcicore_dev_irqvecs_enable (err 0)
>
On 08/23/2013 12:47 AM, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> This enables usage of the ath10k driver on OpenWrt. Only 2.0 PCI hardware
> is supported. The ath10k firmware is currently only available
> through github so use that as its source for now.
>
> This goes build teste