Second patch in getting Wt working on openwrt.
---
libs/wt/Makefile | 164 ++
1 files changed, 164 insertions(+), 0 deletions(-)
create mode 100644 libs/wt/Makefile
diff --git a/libs/wt/Makefile b/libs/wt/Makefile
new file mode 100644
index 0
Hi,
The intent of these 2 patches is to get Wt running on openwrt. (It's a c++ web
framework).
It worked out really well for the application I wrote, although it requires
a bit of space when built as shared libraries. (Of course, static builds and
aggressive linking can reduce the size for a sp
Travis Kemen wrote:
> On Wed, Oct 14, 2009 at 9:54 PM, Wade Berrier <mailto:wberr...@gmail.com>> wrote:
>
> I've tested r17527 on the 8.09 branch and it works great.
>
> Could it be backported to the 8.09 branch?
>
> Thanks,
>
> Wade
&
I've tested r17527 on the 8.09 branch and it works great.
Could it be backported to the 8.09 branch?
Thanks,
Wade
Wade Berrier wrote:
> Hi,
>
> I was wondering if ticket 2781 (and thus r17527) could be backported
> to the 8.09 branch?
>
> I noticed there are a lot
Hi,
I was wondering if ticket 2781 (and thus r17527) could be backported
to the 8.09 branch?
I noticed there are a lot of differences between trunk and branch for
some of the files that are modified. Is backporting feasible? The
patch appeared to apply cleaning, and I'll try it out a little lat
Hi,
I noticed that dnsmasq is listening on wan port 53. (I inadvertently
found this out by accidentally disabling my firewall... thanks xMff).
This was a side effect of r11062 and ticket 3406:
https://dev.openwrt.org/ticket/3406
https://dev.openwrt.org/changeset/10958
I think that a better fix
Hi,
Turns out that disabling madwifi compression fixed the issue.
Could someone backport 16642 from trunk to the 8.09 branch? This makes
MADWIFI_COMPRESSION optional (defaulting to no).
Wade
Wade Berrier wrote:
> Hello,
>
> I built an image from revision 17579 from
> svn://svn
Hello,
I built an image from revision 17579 from
svn://svn.openwrt.org/openwrt/branches/8.09 for an airlink 101 ar430w.
I can connect wirelessly, but when I try to max out the wireless
throughput, my connection dies, and I get this from dmesg:
NETDEV WATCHDOG: wifi0: transmit timed out
-
