On Wed, Apr 18, 2012 at 07:22:33AM +0200, jbem...@zonnet.nl wrote:
> Many architectures already have the patches for the various kernel
> versions ( e.g. patches-3.0, patches-3.1, patches-3.3 ). This is why I
> all I had to do was change the kernel version from 3.0.18 to 3.3.2 for
> my brcm63
Many architectures already have the patches for the various kernel
versions ( e.g. patches-3.0, patches-3.1, patches-3.3 ). This is why I
all I had to do was change the kernel version from 3.0.18 to 3.3.2 for
my brcm63xx target (I first did 3.3.1, but then found that 3.3.2 was
the latest)
The
On Tue, Apr 17, 2012 at 09:50:56PM +0900, 马进 wrote:
> Hi all,
>
> Where could I find the configuration file for wireless based on ath9k
> driver?
> I want to know how to configure the beacon time, beacon time interval and
> so on.
> Is it hostapd.conf?
Add your needed options in /etc/config/wirel
> Regarding the problem of users playing with config options and not
> mentioning it, part of the solution could be to require users to submit
> their .config files when reporting issues. In such a case, having the
> kernel version in there too would actually be better than relying on
> use
We don't allow the targets to be out of sync anyway — for example, if
our 3.3.x kernel is 3.3.2, then no target is allowed to be on 3.3.1.
So don't allow them to set it at all. That way we don't keep ending up
with targets out of sync, when we update and forget to change them all.
If we want to d
See ftp://space.mit.edu/pub/davis/slang/v2.2/changes.txt for changes
Signed-Off-By: Jeroen van Bemmel
Index: feeds/packages/libs/slang2/Makefile
===
--- feeds/packages/libs/slang2/Makefile(revision 31337)
+++ feeds/packages/lib
On Tue, Apr 17, 2012 at 10:51:47PM +0200, Emmanuel Deloget wrote:
>
>
>
>
>
>
> No specific reason. That's just the default eglibc setting and some
> ticket seems to show that there are other issu
No specific reason. That's just the default eglibc setting and some ticket seems to show that there are other issues with 2.13 (but then I did not read them very carefully).Envoyé depuis un mobile Samsung Original message Subject: Re: [OpenWrt-Devel] eglibc 2.12 fails to build Fr
Hey Emmanuel,
I levelled up all versions of eglibc to it's latest revisions of its
respective branches ( https://dev.openwrt.org/changeset/31300 ) and
therewith I guess broke eglibc version 2.12 which I'd like to purge out
anyway. Is there any reason for you to stay on 2.12 instead of 2.13?
If it
Hello,
I´m getting the following warnings during build:
WARNING: arch/arm/mach-ixp4xx/built-in.o(.text+0x624): Section mismatch
in reference from the function at24_setup() to the (unknown reference)
.init.data:(unknown)
The function at24_setup() references
the (unknown reference) __initdata (u
Hello,
(working on trunk...)
It seems (to me; I can be wrong) that patch 100-do-not-use-implicit-rules.patch
for eglibc-2.12 is not needed, as this version already contains it.
Can someone confirm this before I send a patch / open a ticket?
Best regards,
-- Emmanuel Deloget
__
Hi all,
Where could I find the configuration file for wireless based on ath9k
driver?
I want to know how to configure the beacon time, beacon time interval and
so on.
Is it hostapd.conf?
Thank you.
Regards,
Jin
___
openwrt-devel mailing list
openwrt-dev
On 2 April 2012 11:46, Viktar Palstsiuk wrote:
> Signed-off-by: Viktar Palstsiuk
> ---
> net/igmpproxy/Makefile | 8 +++---
> net/igmpproxy/files/igmpproxy.conf | 43
> --
> net/igmpproxy/files/igmpproxy.config | 11
> net/igmpprox
Hi Hannu,
Le 04/15/12 12:26, Hannu Nyman a écrit :
During the long pause in buildbot snapshots last month I got interested
in the snapshot builds.
I noticed that some of the platforms are being built daily although they
have not completed the build process successfully for 1-2 years, in some
ca
14 matches
Mail list logo
