On Thu, 2012-12-13 at 19:55 +0100, Hauke Mehrtens wrote:
> On 12/11/2012 05:56 AM, Nathan Hintz wrote:
> > I noticed these changes when reviewing the 2011 Broadcom SDK. I haven't
> > noticed any obvious changes in behavior with them applied; but thought I
> > should at least pass them on.
> >
> >
On Mon, 31 Dec 2012 19:38:38 +0400, Paul Fertser wrote:
> Can you please explain why wget without keep-alive works but with
> default doesn't? Why shouldn't wget work with the same user:pass@
> syntax? In fact i tried both 2 and 4 on my desktop with old wget
> version 1.12 and both 2 and 4 work the
On Mon, 31 Dec 2012 15:04:58 +0100, Bastian Bittorf wrote:
> this is only correct in the short run.
> maybe OpenWrt will switch to toybox later.
We should deal with that if and when it happens.
> i understand the examples and the problem.
> it is possible to configure busybox wget to behave like
2013/1/3 Rafał Miłecki :
> 2013/1/3 Rafał Miłecki :
>> 2012/12/29 Hauke Mehrtens :
>>> On 12/28/2012 01:05 AM, Rafał Miłecki wrote:
I don't use compat-wireless package in my builds and I wish to just
use default kernel's drivers. So I did:
> make kernel_menuconfig
and enabled MAC
On 12/31/2012 05:07 PM, Bastian Bittorf wrote:
> since 2 years we are using zram[0] in our production
> networks and we love it. i like to kick out the package
> compcache which is very outdated and just use the mainline
> implementation. at the moment we are manually go into
> kernel_menuconfig an
2013/1/3 Rafał Miłecki :
> 2012/12/29 Hauke Mehrtens :
>> On 12/28/2012 01:05 AM, Rafał Miłecki wrote:
>>> I don't use compat-wireless package in my builds and I wish to just
>>> use default kernel's drivers. So I did:
make kernel_menuconfig
>>> and enabled MAC80211 and wireless drivers.
>>>
>
2012/12/29 Hauke Mehrtens :
> On 12/28/2012 01:05 AM, Rafał Miłecki wrote:
>> I don't use compat-wireless package in my builds and I wish to just
>> use default kernel's drivers. So I did:
>>> make kernel_menuconfig
>> and enabled MAC80211 and wireless drivers.
>>
>> Unfortunately it seems that mod
On 01/03/2013 06:41 AM, Nathan Hintz wrote:
> On Wed, 2013-01-02 at 19:12 -0800, Nathan Hintz wrote:
>> On Wed, 2013-01-02 at 19:22 +0100, Hauke Mehrtens wrote:
>>> On 12/19/2012 05:09 AM, Nathan Hintz wrote:
The existing IRQ logic incorrectly indicates cores that have no IRQ
assignment a
Bastian,
I currently use these settings on all of my devices as well. Perhaps
the simplest way to apply these values without having to modify each
target/sub-target is to put a patch under
'target/linux/generic/patches-*' for the kernel that sets these values
to defaults within the kernel.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm not sure if this patch makes much sense. The /proc/net/wireless
file is part of the legacy wext api which is scheduled for removal
soon, also the signal and noise values in ap mode are mostly
meaningless, if set at all.
~ Jow
-BEGIN PGP S
Hello Jack,
did you send this patch also to the mini_snmpd developers to have this
patch in the next releases ?
thanks
Saverio Proto
2012/12/21 Jack Bates :
> Support monitoring wireless signal and noise with SNMP. This is based on
> the demo example distributed with Mini SNMP Daemon. Here is
Hello Manuel,
I will test your patch as soon as possible.
thanks
Saverio
2012/12/22 Manuel Munz :
> The initscript for tinc writes a temporary config into /tmp/tinc. In the
> prepare_net function it appends flags and params from the uci config to
> the temporary tinc.conf for each net. These v
Hello,
Is there anyone has perl-mysql packages to openwrt backfire? or if it is
not exist any suggestion how to create one?
Thanks,
miki
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwr
This patch fixes a problem with wrong GPIOs being changed when the
wlan is on, which disables the wired network ports until the right
GPIO is turned back off. (see
https://lists.openwrt.org/pipermail/openwrt-devel/2012-December/018113.html).
The patch makes it only use the correct GPIO pin.
NOTE:
oops=panic panic=10 / panic_on_oom=1
Reply-To:
X-Editor: vi http://ex-vi.sourceforge.net/
In our production networks we had issues that some device needed
a manual restart, because there where hanging/panic/oopsing during
boot-time.
We added to the kernel-commandline the args: 'oops=panic panic=
Are you using trunk or AA ?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
16 matches
Mail list logo
