- "Karthik Venkateswaran" <[EMAIL PROTECTED]> ha scritto:
> A simple solution is to use $(CXX) instead of $(CC) in MGEN source
> Makefile.
Sorry for the very simple question, but how do I tell kamikaze to use g++
in the package Makefile. The mgen makefile already spacifies g++ but it is
ig
Hi,
After a quick look at your issue, seems like the linking problem is
because you are using i386-linux-uclibc-gcc instead of
i386-linux-uclibc-g++.
make[5]: Leaving directory
`/home/wing/wing-bot-r12098/kamikaze-wrap/build_dir/i386/mgen-4.2b6/protolib/unix'
i386-linux-uclibc-gcc -g -g -DPROT
Johannes Berg schrieb:
>> Call Trace:[][]
>
> My magic crystal ball says that this is not inside p54 at all, and
> indeed a problem in your kernel patches. :P
An amazingly advanced crystal ball you have ;)
So, a final update: ASUS WL-500gP (v1) running with OpenWRT patches and
a prism54 mini-pc
I've just downloaded the latest svn trunk...and etrax target cannot be
compiled anymore...
Can someone test?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
I have a mipsel device (ASUS WL-500gP; it runs a 2.6.25.9 OpenWRT kernel) with
a prism54 mini-pci card:
00:02.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism
Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
Subsystem: Intersil Corporation Unknown device
Hi,
I'm trying to build mgen (http://cs.itd.nrl.navy.mil/work/mgen/) for kamikaze.
Hoever
after launching the build I get the following errors:
make[5]: Leaving directory
`/home/wing/wing-bot-r12098/kamikaze-wrap/build_dir/i386/mgen-4.2b6/protolib/unix'
i386-linux-uclibc-gcc -g -g -DPROTO_DEBUG
Il giorno mar, 05/08/2008 alle 18.47 +0200, Felix Fietkau ha scritto:
> The WDS thing is fixable in madwifi. I will eventually add compatibility
> for Broadcom WDS when I find the time.
Thanks a lot. Remember me to buy you a beer (or mail you a spare router,
the beer might get warm while shipping
This patch adds wpa_supplicant calls for EAP TLS, TTLS, PEAP to
madwifi configuration script.
Defined options correspond to wpa_supplicant options :
Common options :
* eap
* identity
* ca_cert
* pairwise
* group
TLS specific options :
* client_cert
* private_key
* private_key_passwd
TTLS and PE
Dirk Nehring wrote:
> Hi,
>
> the SLUB allocator is included in the official kernel since 2.6.22,
> smaller footprint, better performance and the standard allocator in
> "make defconfig". We should safely switch to this one.
Added in r12138
- Felix
___
Alberto Botti wrote:
> Il giorno mar, 05/08/2008 alle 15.52 +0200, Felix Fietkau ha scritto:
>> It doesn't work between Broadcom and Atheros yet. But if you use only
>> Atheros devices, then WPA-PSK will work. I've tested both WPA and WPA2.
>
> Thanks. Is it a specific limitation of the Broadcom h
In client mode, this avoid to associate to an AP with different ssid.
Signed-off-by: Frédéric Moulins <[EMAIL PROTECTED]>
diff --git a/package/madwifi/files/lib/wifi/madwifi.sh
b/package/madwifi/files/lib/wifi/madwifi.sh
index 9d08e1f..e996a2c 100755
--- a/package/madwifi/files/lib/wifi/madwifi.
Il giorno mar, 05/08/2008 alle 15.52 +0200, Felix Fietkau ha scritto:
> It doesn't work between Broadcom and Atheros yet. But if you use only
> Atheros devices, then WPA-PSK will work. I've tested both WPA and WPA2.
Thanks. Is it a specific limitation of the Broadcom hardware (or its
crappy binary
Alberto Botti wrote:
> Il giorno mar, 05/08/2008 alle 09.19 +0200, Felix Fietkau ha scritto:
>
>> If you're talking about madwifi, then simply put up an AP on the side
>> that talks to multiple WDS peers.
>> On the other side, simply add a regular sta interface.
>> Make sure that you grab the late
> > It allows to configure kernel modules parameters from uci config
> > files.
>
> Interesting. But is it really good to have a separate config file for
> each module? This can lead to collisions (if a module has the same
> name as a different config file); also, a set of config files without
Hi,
the SLUB allocator is included in the official kernel since 2.6.22,
smaller footprint, better performance and the standard allocator in
"make defconfig". We should safely switch to this one.
Dirk
Index: target/linux/generic-2.6/config-2.6.26
==
Il giorno mar, 05/08/2008 alle 09.19 +0200, Felix Fietkau ha scritto:
> If you're talking about madwifi, then simply put up an AP on the side
> that talks to multiple WDS peers.
> On the other side, simply add a regular sta interface.
> Make sure that you grab the latest trunk (some more fixes jus
Thanks.
It works fine. This new way of configuring WDS is really great
congratulations for the great works guys.
Bye
R.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
HI
2008/8/4, Claudio <[EMAIL PROTECTED]>:
> 2008/8/4, Hinko Kocevar <[EMAIL PROTECTED]>:
>> MichelinoK wrote:
>>> "Hinko Kocevar" <[EMAIL PROTECTED]> ha scritto nel messaggio
>>> news:[EMAIL PROTECTED]
MichelinoK wrote:
> Is there a way to have a more verbose "boot" (to see where it hangs
[EMAIL PROTECTED] wrote:
> Hi,
>
> as far as I've understood there have been changes in the wds area.
> Which is the proper way to setup wds now? For example how should I
> translate the following config:
If you're talking about madwifi, then simply put up an AP on the side
that talks to multiple
Hi,
as far as I've understood there have been changes in the wds area.
Which is the proper way to setup wds now? For example how should I
translate the following config:
config wifi-iface
option device "wifi0"
option network "lan"
option mode"ap"
o
20 matches
Mail list logo
