Compile a kernel with debugging enabled, this is pretty much worthless
There are a lot of options under debugging in the config. I enabled all of
them, but the result hangs during boot.
Which one must be enabled?
Thx
K. Gy.
___
openwrt-devel mailing
On Mon, March 1, 2010 09:01, K�vesdi Gy�rgy wrote:
Compile a kernel with debugging enabled, this is pretty much worthless
There are a lot of options under debugging in the config. I enabled all of
them, but the result hangs during boot.
Which one must be enabled?
Most important is Compile the
OpenWrt 写道:
#6484: generic 2.6.33 preliminary support
-+--
Reporter: acoul alex at ozo.com | Owner: developers
Type: enhancement | Status: new
Priority: normal |
On Sun, 2010-02-28 at 11:30 +0100, Stijn Tintel wrote:
On 28-02-10 11:28, Stijn Tintel wrote:
This patch allows multiple listen ports to be configured for dropbear in
/etc/config/dropbear. It renames the 'Port' option to 'Ports', so this
will break existing configs.
What looks more useful
Just to be clear, it's not intended to be a selectable feature, it will
just be defined if CONFIG_NETFILTER is defined in the target kernel
config, like it is for the GPIO, PCI or USB features.
What do you mean by migrate to the DEVICE_TYPE ?
--
-{Nico}
Imre Kaloz wrote:
On Mon, 01 Mar 2010
On Mon, March 1, 2010 10:31, Bas Mevissen wrote:
On Sun, 2010-02-28 at 11:30 +0100, Stijn Tintel wrote:
On 28-02-10 11:28, Stijn Tintel wrote:
This patch allows multiple listen ports to be configured for dropbear
in
/etc/config/dropbear. It renames the 'Port' option to 'Ports', so this
On 01-03-10 14:12, m...@maddes.net wrote:
On Mon, March 1, 2010 10:31, Bas Mevissen wrote:
On Sun, 2010-02-28 at 11:30 +0100, Stijn Tintel wrote:
On 28-02-10 11:28, Stijn Tintel wrote:
This patch allows multiple listen ports to be configured for dropbear
in
sslh will not be added to the 8.09 packages branch. I will make it
into the next release.
Travis
On Fri, Feb 26, 2010 at 6:08 PM, Matthias Buecher / Germany
m...@maddes.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi OpenWrt team,
please add packages/net/sslh to
On Mon, 2010-03-01 at 15:22 +0100, Stijn Tintel wrote:
Since the above suggestion is OK for me, I'd suggest to just forget this
patch :-)
The patch itself is useful if someone wants to explore the possibilities
of dropbear. There is a difference between two instances and one
instance which
On 2010.03.01. 12:34:03 Nico n...@openwrt.org wrote:
Just to be clear, it's not intended to be a selectable feature, it will
just be defined if CONFIG_NETFILTER is defined in the target kernel
config, like it is for the GPIO, PCI or USB features.
What do you mean by migrate to the DEVICE_TYPE
patch attached
greets
Peter Wagner
diff --git a/package/openssl/Makefile b/package/openssl/Makefile
index 2d2a940..3b99c08 100644
--- a/package/openssl/Makefile
+++ b/package/openssl/Makefile
@@ -8,15 +8,15 @@
include $(TOPDIR)/rules.mk
PKG_NAME:=openssl
-PKG_VERSION:=0.9.8l
-PKG_RELEASE:=2
This patch series enables management frame protection (802.11w) in hostapd and
wpa_supplicant. Both programs implement IEEE Std 802.11w-2009 since version
0.7.0 (1),(2). According to (3), the only driver that currently supports
802.11w is ath9k.
I have tested this on two identical OpenWrt
When enabling MFP, hostapd will read assoc_sa_query_max_timeout and
assoc_sa_query_retry_timeout from it's config file. Make these options
configurable in /etc/config/wireless. To make it clear that these
options are 802.11w related, I named them ieee80211w_max_timeout and
ieee80211w_retry_timeout
Enable management frame protection in wpa_supplicant, and make it
configurable in /etc/config/wireless.
Signed-off-by: Stijn Tintel st...@linux-ipv6.be
---
package/hostapd/files/wpa_supplicant-full.config |2 +-
package/hostapd/files/wpa_supplicant.sh | 10 ++
2 files
Enable management frame protection in hostapd, and make it configurable
in /etc/config/wireless. Since ath9k is currently the only driver that
supports MFP, it will only be enabled when ath9k is enabled.
Signed-off-by: Stijn Tintel st...@linux-ipv6.be
---
package/hostapd/Makefile |3
Hello
From: j...@gmx.de
I couldn't find any code in svn r19920 dealing specifically with the AR7240
and the built-in switch.
Today in revision 19927 switch support for AG7240 has been committed. I'll try
that. Buildroot is running at the moment.
So I guess that the bootloader
Well, you could always look at some packages for exisiting kernel
modules for blueprints.
If you have some specific questions, you can ask them here or in
#openwrt on freenode.
But please try to figure out how to do this by yourself first, too
general questions will only get general and not very
Hello list,
finally the switch in the TP-Link TL-WR741N(D) (and probably other devices
based von AR7140) is not blocking broadcasts any more and thus allows to get an
IP via DHCP.
But my question is left to be answered. Does this bridge which is created over
the LAN-ports really mean that
Did you try to flash an ar71xx image? For example the fon one?
If the kernel at least starts to boot, I can do the rest. Otherwise,
I'm not so sure.
Bernhard
2010/3/1 jason duhamell ps2chi...@gmail.com:
Ok, I decided I will start the Job offer at 100 dollars and the board. dont
worry
On 2010.03.02. 04:52:23 Nico n...@openwrt.org wrote:
Well, using DEVICE_TYPE does not solve the issue, it will just prevent
netfilter modules from being embedded in the final images, but wont
prevent them from being built and that will just fail for those targets
that have CONFIG_NETFILTER not
On Tue, March 2, 2010 07:10, Imre Kaloz wrote:
On 2010.03.02. 04:52:23 Nico n...@openwrt.org wrote:
Well, using DEVICE_TYPE does not solve the issue, it will just prevent
netfilter modules from being embedded in the final images, but wont
prevent them from being built and that will just fail
21 matches
Mail list logo
