Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1
Hi,
On Thu, 03 Jan 2013 11:57:56 +0100, Bastian Bittorf
wrote:
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=10'
like mentioned in this post:
https://lists.openwrt.org/pipermail/openwrt-devel/2012-August/016430.html
Now its much better, nearly no manual restarts are needed.
I like to discuss that these changes are a good idea for everybody
and should be standard for headless/embedded systems in production.
If you care about "patching away errors", developers ("serial attached")
can choose to not include it. also an init/rc-script after boot
can switch this behaviour off.
While we are at this point: 'panic_on_oom' is IMHO also a good choice.
I'm fine with the idea but not the way you did it, because if you're "serial
attached" this gets annoying quite fast. Although we could make this a config option
and do all kind of magic to set it based on that, I suggest swapping your idea: change
these through sysctl _after_ a successful boot-up.
Imre
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] how to get config option value on model ListValue!
hi all , The following is my dhcp config
config host
option name 'q'
option mac '64:31:50:93:f5:2c'
option ip '192.168.11.123'
config host
option name 'w'
option mac '64:31:50:93:f5:2c'
option ip '192.168.11.124'
how to get the value of the option name? Can i use foreach?
follow is my program
profile = s:option(ListValue, "profile", translate("Profile Selection"))
profile:value("", "")
profile.default = "Default"
profile:depends("apn", "1")
m.uci:foreach("dhcp", "host",
function (section)
--local ifc = option[".value"]
profile:value(ifc)
end
)
thanks all.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH][mac80211]b43: UPDATED fix for Linksys E1000 V1 GPIOs
UPDATE:
This patch INVALIDATES the first one I sent for this fix.
The other one made the LEDs behave properly, however the wireless did not work.
This one fixes it, the wireless work properly.
(It uses the value of the "leddc" nvram var, 0x, of the Linksys
E1000 v1; see https://forum.openwrt.org/viewtopic.php?pid=179199).
If you receive this email multiple times, I apologize.
--- a/drivers/net/wireless/b43/main.c
+++ b/drivers/net/wireless/b43/main.c
@@ -2722,6 +2722,10 @@
} else if (dev->dev->chip_id == 0x5354) {
/* Don't allow overtaking buttons GPIOs */
set &= 0x2; /* 0x2 is LED GPIO on BCM5354 */
+ } else if (dev->dev->chip_id == 47162) {
+ /* only use LED GPIO (gpio 0 on Linksys E1000 V1) */
+ set &= 0x1;
+ mask = 0x;
}
if (0 /* FIXME: conditional unknown */ ) {
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH][toolchain/uclibc] build: enable ld.so standalone (LDSO_STANDALONE_SUPPORT)
This patch enables the LDSO_STANDALONE_SUPPORT kconfig option of uClibc by default. This can be useful e.g. for faking chroot of a rootfs, for example, using proot (http://proot.me/ https://github.com/cedric-vincent/PRoot). Right now this can be done by hacking the makefiles (for example the way *this* patch does :-) ), however, it would be really awesome if the stock images come compiled with it enabled, that way people on e.g. android do not have to go through the compilation process. --- a/toolchain/uClibc/config-0.9.33.2/common +++ b/toolchain/uClibc/config-0.9.33.2/common @@ -39,7 +39,7 @@ LDSO_LDD_SUPPORT=y # LDSO_PRELOAD_ENV_SUPPORT is not set LDSO_RUNPATH=y # LDSO_SEARCH_INTERP_PATH is not set -# LDSO_STANDALONE_SUPPORT is not set +LDSO_STANDALONE_SUPPORT=y # LINUXTHREADS_NEW is not set # LINUXTHREADS_OLD is not set # UCLIBC_HAS_BACKTRACE is not set ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] mac80211: add dependency of PACKAGE_MAC80211_DEBUGFS
On 2012-12-24 3:46 PM, Stefan Hellermann wrote: > I wanted to use some statistics from /sys/kernel/debug/ieee80211, > so I enabled PACKAGE_MAC80211_DEBUGFS. But I could not use it, > because CONFIG_KERNEL_DEBUG_FS was not set and it's a little bit > hidden. After manually setting CONFIG_KERNEL_DEBUG_FS to y, > everything was fine. This patch automatically selects > CONFIG_KERNEL_DEBUG_FS if PACKAGE_MAC80211_DEBUGFS is set. > > Additionally, the help text says "Say N unless you know you need this.", > but it's set to default y. I removed the default y to be consistent > with the help text. It's better to remove this note from the help text (which was probably copied from the kernel's Kconfig). Keep the default at y, debugfs support is very useful for getting additional status information about the state of wireless. Also, please move the select to the 'config PACKAGE_MAC80211_DEBUGFS' symbol, so you can drop the 'if PACKAGE_MAC80211_DEBUGFS' part. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH][toolchain/uclibc] build: enable ld.so standalone (LDSO_STANDALONE_SUPPORT)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 How does it affect the size of the libc binaries? ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDm0OcACgkQdputYINPTPP7rwCeKCGZ7kQiIwpAz1B/9e+HZVRD P/gAn22kP80zz+SvtTkTEX9KMXB+LyrI =nX+R -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] how to get config option value on model ListValue!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
> how to get the value of the option name? Can i use foreach? follow
> is my program [...]
m.uci:foreach("dhcp", "host",
function(section)
profile:value(section['name'])
end)
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlDm0SIACgkQdputYINPTPN0agCcClFEhFOK5uAySaO0M1ZHXG7Q
+ocAoJzTAwd4MYx3v9BS4jJbxKX+ZkD6
=1UFC
-END PGP SIGNATURE-
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [packages] mosquitto: Upgrade MQTT tools to v1.1
From: Karl Palsson This is a bugfix and feature release. Full release notes at http://mosquitto.org/2012/12/version-1-1-released/ This also removes some unnecessary flags included by mistake in an earlier update. As before, I volunteer to maintain this package. Signed-off-by: Karl Palsson --- net/mosquitto/Makefile | 7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/net/mosquitto/Makefile b/net/mosquitto/Makefile index 627e992..de79165 100644 --- a/net/mosquitto/Makefile +++ b/net/mosquitto/Makefile @@ -9,19 +9,16 @@ include $(TOPDIR)/rules.mk PKG_NAME:=mosquitto -PKG_VERSION:=1.0.3 +PKG_VERSION:=1.1 PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=http://mosquitto.org/files/source/ -PKG_MD5SUM:=9c9e06c57fcca80d76068c53ad140186 - -PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-$(BUILD_VARIANT)/$(PKG_NAME)-$(PKG_VERSION) +PKG_MD5SUM:=ab51f64eb3f0041402073aa7865f3ec4 include $(INCLUDE_DIR)/package.mk MAKE_FLAGS+=WITH_MEMORY_TRACKING=no -TARGET_CFLAGS+=-ggdb3 define Package/$(PKG_NAME)/default SECTION:=net -- 1.7.11.7 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [packages] add PageKite C, and libev
From: Karl Palsson
Adds the PageKite C implementation and it's dependency, libev.
>From the package description:
PageKite is a system for running publicly visible servers (generally
web servers) on machines without a direct connection to the Internet,
such as mobile devices or computers behind restrictive firewalls.
PageKite works around NAT, firewalls and IP-address limitations by
using a combination of tunnels and reverse proxies.
This package provides an implementation of the PageKite Protocol in C,
optimized for high-performance or embedded applications.
Basic UCI support for HTTP and SSH servers is also included in this
package.
https://pagekite.net/wiki/Floss/LibPageKite/
Signed-off-by: Karl Palsson
---
libs/libev/Makefile| 59 +
net/pagekitec/Makefile | 60 ++
net/pagekitec/files/pagekitec.config | 1 +
net/pagekitec/files/pagekitec.init | 36 ++
net/pagekitec/files/pagekitec.uci-defaults | 25 +
5 files changed, 181 insertions(+)
create mode 100644 libs/libev/Makefile
create mode 100644 net/pagekitec/Makefile
create mode 100644 net/pagekitec/files/pagekitec.config
create mode 100755 net/pagekitec/files/pagekitec.init
create mode 100755 net/pagekitec/files/pagekitec.uci-defaults
diff --git a/libs/libev/Makefile b/libs/libev/Makefile
new file mode 100644
index 000..4607d9b
--- /dev/null
+++ b/libs/libev/Makefile
@@ -0,0 +1,59 @@
+#
+# Copyright (C) 2006-2010 OpenWrt.org
+#
+# This is free software, licensed under the GNU General Public License v2.
+# See /LICENSE for more information.
+#
+
+include $(TOPDIR)/rules.mk
+
+PKG_NAME:=libev
+PKG_VERSION:=4.11
+PKG_RELEASE:=1
+
+PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
+PKG_SOURCE_URL:=http://dist.schmorp.de/libev/Attic/
+PKG_MD5SUM:=cda69b858a1849dfe6ce17c930cf10cd
+
+PKG_FIXUP:=autoreconf
+PKG_INSTALL:=1
+PKG_BUILD_PARALLEL:=1
+
+include $(INCLUDE_DIR)/package.mk
+
+define Package/libev
+ SECTION:=libs
+ CATEGORY:=Libraries
+ TITLE:=Another event notification library
+ URL:=http://software.schmorp.de/pkg/libev.html
+ MAINTAINER:=Thomas Heil
+endef
+
+define Package/libev/description
+A full-featured and high-performance (see benchmark) event loop that is
loosely
+modelled after libevent, but without its limitations and bugs.
+It is used, among others, in the GNU Virtual Private Ethernet and rxvt-unicode
+packages, and in the Deliantra MORPG Server and Client.
+endef
+
+TARGET_CFLAGS += $(FPIC)
+
+CONFIGURE_ARGS += \
+ --enable-shared \
+ --enable-static \
+
+define Build/InstallDev
+ $(INSTALL_DIR) $(1)/usr/include
+ $(CP) $(PKG_INSTALL_DIR)/usr/include/* $(1)/usr/include
+ $(INSTALL_DIR) $(1)/usr/lib
+ $(CP) $(PKG_INSTALL_DIR)/usr/lib/libev.{la,a,so} $(1)/usr/lib
+ $(CP) $(PKG_INSTALL_DIR)/usr/lib/libev.so.4* $(1)/usr/lib
+endef
+
+define Package/libev/install
+ $(INSTALL_DIR) $(1)/usr/lib
+ $(CP) $(PKG_INSTALL_DIR)/usr/lib/libev.so.4* $(1)/usr/lib/
+endef
+
+$(eval $(call BuildPackage,libev))
+
diff --git a/net/pagekitec/Makefile b/net/pagekitec/Makefile
new file mode 100644
index 000..471d1f4
--- /dev/null
+++ b/net/pagekitec/Makefile
@@ -0,0 +1,60 @@
+#
+# Copyright (C) 2012 OpenWrt.org
+#
+# This is free software, licensed under the GNU General Public License v2.
+# See /LICENSE for more information.
+#
+
+include $(TOPDIR)/rules.mk
+
+PKG_NAME:=pagekitec
+PKG_REV:=e79bf00c4efd4e37e4941a054e1e6d8fbce5d00a
+PKG_VERSION:=121207C-$(PKG_REV)
+PKG_RELEASE:=1
+PKG_SOURCE_SUBDIR:=$(PKG_NAME)-$(PKG_VERSION)
+PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
+PKG_SOURCE_URL:=g...@github.com:pagekite/libpagekite.git
+PKG_SOURCE_PROTO:=git
+PKG_SOURCE_VERSION:=$(PKG_REV)
+
+include $(INCLUDE_DIR)/package.mk
+
+define Package/$(PKG_NAME)
+ SECTION:=net
+ CATEGORY:=Network
+ TITLE:=Make localhost servers publicly visible.
+ URL:=https://pagekite.net/wiki/Floss/LibPageKite/
+ DEPENDS:=+libopenssl +libpthread +libev
+endef
+
+define Package/$(PKG_NAME)/description
+PageKite is a system for running publicly visible servers (generally
+ web servers) on machines without a direct connection to the Internet,
+ such as mobile devices or computers behind restrictive firewalls.
+ PageKite works around NAT, firewalls and IP-address limitations by
+ using a combination of tunnels and reverse proxies.
+
+ This package provides an implementation of the PageKite Protocol in C,
+ optimized for high-performance or embedded applications.
+
+ Basic UCI support for HTTP and SSH servers is also included in this package.
+
+ https://pagekite.net/wiki/Floss/LibPageKite/
+endef
+
+define Package/$(PKG_NAME)/conffiles
+/etc/config/$(PKG_NAME)
+endef
+
+define Package/$(PKG_NAME)/install
+ $(INSTALL_DIR) $(1)/usr/bin
+ $(INSTALL_BIN) $(PKG_BUILD_DIR)/$(PKG_NAME) $(1)/usr/bin
+ $(INSTALL_DIR) $(1)/etc/init.d
+ $(INSTALL_BIN) .
Re: [OpenWrt-Devel] tune kernel commandline for headless/embedded systems / oops=panic panic=10 / panic_on_oom=1
* Imre Kaloz [04.01.2013 16:27]:
>
> I'm fine with the idea but not the way you did it, because if you're "serial
> attached" this gets annoying quite fast. Although we could make this a config
> option and do all kind of magic to set it based on that, I suggest swapping
> your idea: change these through sysctl _after_ a successful boot-up.
>
the problem is: most routers are "in production" and not "serial
attached" - so you have really a problem if a node ("rooftop" or "solar
powered") dies during boot. if you are a developer, you can simple build
your own image and disable this option, all other persons (>90%?) like to
have a running/selfrebooting router when the kernel is panic'ing or there
are serious problems.
with "gets annoying quite fast" i think you mean: during
developing/playing you cannot see the crash-dump, because the unit
is rebooting too fast? then we can simple use the kernel-commandline
argument "panic=30" which leaves 30 seconds before a reboot is
enforced.
also: reading the crashdump after reboot is possible since r32787:
http://intercity-vpn.de/crashlog/
bye, bastian
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
Hauke, I tested this patch today and just wanted to give some feedback. The patch applies cleanly and installs everything correctly, however it does not activate the swap on boot up. Executing '/etc/init.d/zram start' successfully starts. There is also a uci error when starting when the 'zram_size_mb' is not set. On 01/03/2013 03:17 PM, Hauke Mehrtens wrote: 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 and switch on: General setup: ---> [*] Support for paging of anonymous memory (swap) Device Drivers ---> Staging drivers ---> [*] Compressed RAM block device support which means: CONFIG_FRONTSWAP is not set CONFIG_SWAP=y CONFIG_HIBERNATION is not set CONFIG_MTD_SWAP is not set CONFIG_ZRAM=y CONFIG_ZRAM_DEBUG is not set CONFIG_ZSMALLOC=y CONFIG_LZO_COMPRESS=y CONFIG_LZO_DECOMPRESS=y also we use our own rc-file, so we can do /etc/init.d/zram start|stop https://github.com/bittorf/kalua/blob/master/openwrt-addons/etc/init.d/zram IMHO it should be a menuconfig-entry in "base-system", because it is fundamental for all 16mb routers. What i need for baking a Makefile is a hint for a package which a) activates some symbols in kernel-config b) enforces building and loading of a kmodule c) has an rc-file I'am new to Make, so please help 8-) Also i like to have feedback. For the motivation, the output of a WRT54G running 3.6.11: root@openwrt:~ free total used free shared buffers Mem: 1300411420 15840 696 -/+ buffers: 10724 2280 Swap: 6140 584 5556 bye, bastian [0] https://code.google.com/p/compcache/ Nice work Bastian. I would not add it as a global option, but as a module, so it could also be used by someone not building his own image, but using a prebuild image, with kernel 3.6.11 I had a problem building this as a module. The swap utils e.g. from busybox are also needed, this increases the busybox binary by 3.2K uncompressed. CONFIG_BUSYBOX_CONFIG_MKSWAP=y CONFIG_BUSYBOX_CONFIG_SWAPONOFF=y Attached is a patch adding zram as a module. The default image without zram should be 3.2K bigger (uncompressed) but there are no more influences to a image without zram support. Bastian could you test this and give feedback? Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] mac80211: add dependency of PACKAGE_MAC80211_DEBUGFS
mac80211: add dependency of PACKAGE_MAC80211_DEBUGFS I wanted to use some statistics from /sys/kernel/debug/ieee80211, so I enabled PACKAGE_MAC80211_DEBUGFS. But I could not use it, because CONFIG_KERNEL_DEBUG_FS was not set and it's a little bit hidden. After manually setting CONFIG_KERNEL_DEBUG_FS to y, everything was fine. This patch automatically selects CONFIG_KERNEL_DEBUG_FS if PACKAGE_MAC80211_DEBUGFS is set. Additionally, the help text says "Say N unless you know you need this.", but it's default y. This help text is copied verbatim from the kernel's Kconfig and not true for us. So remove this part of the help text Signed-off-by: Stefan Hellermann --- a/package/mac80211/Makefile +++ b/package/mac80211/Makefile @@ -84,13 +84,12 @@ define KernelPackage/mac80211/config config PACKAGE_MAC80211_DEBUGFS bool "Export mac80211 internals in DebugFS" + select KERNEL_DEBUG_FS default y help Select this to see extensive information about the internal state of mac80211 in debugfs. - Say N unless you know you need this. - config PACKAGE_MAC80211_MESH bool "Enable 802.11s mesh support" default y ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH variant a] mac80211: uncouple ATH_DEBUGFS from MAC80211_DEBUGFS
uncouple ATH_DEBUGFS from MAC80211_DEBUGFS MAC80211_DEBUGFS selects the atheros wireless debugfs options, but not the debugfs options from rt2x00-lib and b43. Make it consistent and add a ATH_DEBUGFS option. ATH_DEBUG needs ATH_DEBUGFS, so select it. When the new ATH_DEBUGFS is disabled and MAC80211_DEBUGFS is enabled, it saves about 25k on a compressed image here. Signed-off-by: Stefan Hellermann --- a/package/mac80211/Makefile +++ b/package/mac80211/Makefile @@ -35,6 +35,7 @@ PKG_CONFIG_DEPENDS:= \ $(patsubst %,CONFIG_PACKAGE_kmod-%,$(PKG_DRIVERS)) \ CONFIG_PACKAGE_MAC80211_DEBUGFS \ CONFIG_PACKAGE_MAC80211_MESH \ + CONFIG_PACKAGE_ATH_DEBUGFS \ CONFIG_PACKAGE_ATH_DEBUG \ CONFIG_PACKAGE_B43_DEBUG \ CONFIG_PACKAGE_B43_PIO \ @@ -220,7 +221,7 @@ define KernelPackage/rt2x00-lib/config config PACKAGE_RT2X00_LIB_DEBUGFS bool "Enable rt2x00 debugfs support" - depends PACKAGE_MAC80211_DEBUGFS + select PACKAGE_MAC80211_DEBUGFS help Enable creation of debugfs files for the rt2x00 drivers. These debugfs files support both reading and writing of the @@ -383,11 +384,22 @@ define KernelPackage/ath/config Select this option if you want the driver to respect the user's decision about regulatory settings. + config PACKAGE_ATH_DEBUGFS + bool "Atheros wireless debugfs support" + select PACKAGE_MAC80211_DEBUGFS + default y + help + Enable creation of debugfs files for the atheros wireless drivers. + These debugfs files support both reading and writing of the + most important register types of the atheros wireless hardware. + Additionally you can read extensive information and statistics. + It's used on Buffalo WZR-HP-AG300H to enable LED support. + config PACKAGE_ATH_DEBUG bool "Atheros wireless debugging" + select PACKAGE_ATH_DEBUGFS help Say Y, if you want to debug atheros wireless drivers. - Right now only ath9k makes use of this. endif endef @@ -1171,9 +1183,10 @@ BUILDFLAGS:= \ -DCONFIG_B43_HWRNG -DCONFIG_B43LEGACY_HWRNG \ $(if $(CONFIG_PCI),-DCONFIG_ATH9K_PCI) \ $(if $(CONFIG_TARGET_ar71xx),-DCONFIG_ATH9K_AHB) \ - $(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS), -DCONFIG_CFG80211_DEBUGFS -DCONFIG_MAC80211_DEBUGFS -DCONFIG_ATH9K_DEBUGFS -DCONFIG_CARL9170_DEBUGFS -DCONFIG_ATH9K_HTC_DEBUGFS -DCONFIG_ATH5K_DEBUG) \ + $(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS), -DCONFIG_CFG80211_DEBUGFS -DCONFIG_MAC80211_DEBUGFS) \ + $(if $(CONFIG_PACKAGE_ATH_DEBUGFS), -DCONFIG_ATH9K_DEBUGFS -DCONFIG_CARL9170_DEBUGFS -DCONFIG_ATH9K_HTC_DEBUGFS) \ $(if $(CONFIG_PACKAGE_MAC80211_MESH),-DCONFIG_MAC80211_MESH) \ - $(if $(CONFIG_PACKAGE_ATH_DEBUG),-DCONFIG_ATH_DEBUG -DCONFIG_ATH9K_PKTLOG) \ + $(if $(CONFIG_PACKAGE_ATH_DEBUG),-DCONFIG_ATH_DEBUG -DCONFIG_ATH9K_MAC_DEBUG -DCONFIG_ATH9K_PKTLOG -DCONFIG_ATH5K_DEBUG) \ -D__CONFIG_MAC80211_RC_DEFAULT=minstrel \ -DCONFIG_MAC80211_RC_MINSTREL_HT \ $(if $(CONFIG_ATH_USER_REGD),-DATH_USER_REGD=1) \ @@ -1239,17 +1252,18 @@ MAKE_OPTS:= \ CONFIG_ATH5K=$(if $(CONFIG_PACKAGE_kmod-ath5k),m) \ CONFIG_ATH5K_PCI=$(if $(CONFIG_TARGET_atheros),,y) \ CONFIG_ATH5K_AHB=$(if $(CONFIG_TARGET_atheros),y) \ - CONFIG_ATH5K_DEBUG=$(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),y) \ + CONFIG_ATH5K_DEBUG=$(if $(CONFIG_PACKAGE_ATH_DEBUG),y) \ CONFIG_ATH9K=$(if $(CONFIG_PACKAGE_kmod-ath9k),m) \ CONFIG_ATH9K_PCI=$(CONFIG_PCI) \ CONFIG_ATH9K_AHB=$(if $(CONFIG_TARGET_ar71xx),y) \ CONFIG_ATH9K_HTC=$(if $(CONFIG_PACKAGE_kmod-ath9k-htc),m) \ - CONFIG_ATH9K_HTC_DEBUGFS=$(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),y) \ + CONFIG_ATH9K_HTC_DEBUGFS=$(if $(CONFIG_PACKAGE_ATH_DEBUGFS),y) \ CONFIG_ATH9K_HW=$(if $(CONFIG_PACKAGE_kmod-ath9k-common),m) \ CONFIG_ATH9K_COMMON=$(if $(CONFIG_PACKAGE_kmod-ath9k-common),m) \ - CONFIG_ATH9K_DEBUGFS=$(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),y) \ + CONFIG_ATH9K_DEBUGFS=$(if $(CONFIG_PACKAGE_ATH_DEBUGFS),y) \ + CONFIG_ATH9K_MAC_DEBUG=$(if $(CONFIG_PACKAGE_ATH_DEBUG),y) \ CONFIG_CARL9170=$(if $(CONFIG_PACKAGE_kmod-carl9170),m) \ - CONFIG_CARL9170_DEBUGFS=$(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),y) \ + CONFIG_CARL9170_DEBUGFS=$(if $(CONFIG_PACKAGE_ATH_DEBUGFS),y) \ CONFIG_COMPAT_ZD1211RW=$(if $(CONFIG_PACKAGE_kmod-zd1211rw),m) \ CONFIG_P54_COMMON=$(if $(CONFIG_PACKAGE_kmod-p54-common),m) \ CONFIG_P54_PCI=$(if $(CONFIG_PACKAGE_kmod-p54-pci),m) \ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org htt
[OpenWrt-Devel] [PATCH variant b] mac80211: remove a few config options
remove a few config settings from mac80211 MAC80211_DEBUGFS selects the atheros wireless debugfs options, but not the debugfs options from rt2x00-lib and b43. Make it consistent and remove all driver_DEBUGFS option. ATH_DEBUG needs MAC80211_DEBUGFS, so select it. Signed-off-by: Stefan Hellermann --- a/package/mac80211/Makefile +++ b/package/mac80211/Makefile @@ -218,14 +218,6 @@ endef define KernelPackage/rt2x00-lib/config if PACKAGE_kmod-rt2x00-lib - config PACKAGE_RT2X00_LIB_DEBUGFS - bool "Enable rt2x00 debugfs support" - depends PACKAGE_MAC80211_DEBUGFS - help - Enable creation of debugfs files for the rt2x00 drivers. - These debugfs files support both reading and writing of the - most important register types of the rt2x00 hardware. - config PACKAGE_RT2X00_DEBUG bool "Enable rt2x00 debug output" help @@ -385,9 +377,9 @@ define KernelPackage/ath/config config PACKAGE_ATH_DEBUG bool "Atheros wireless debugging" + select PACKAGE_MAC80211_DEBUGFS help Say Y, if you want to debug atheros wireless drivers. - Right now only ath9k makes use of this. endif endef @@ -1171,9 +1163,9 @@ BUILDFLAGS:= \ -DCONFIG_B43_HWRNG -DCONFIG_B43LEGACY_HWRNG \ $(if $(CONFIG_PCI),-DCONFIG_ATH9K_PCI) \ $(if $(CONFIG_TARGET_ar71xx),-DCONFIG_ATH9K_AHB) \ - $(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS), -DCONFIG_CFG80211_DEBUGFS -DCONFIG_MAC80211_DEBUGFS -DCONFIG_ATH9K_DEBUGFS -DCONFIG_CARL9170_DEBUGFS -DCONFIG_ATH9K_HTC_DEBUGFS -DCONFIG_ATH5K_DEBUG) \ + $(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS), -DCONFIG_CFG80211_DEBUGFS -DCONFIG_MAC80211_DEBUGFS -DCONFIG_ATH9K_DEBUGFS -DCONFIG_CARL9170_DEBUGFS -DCONFIG_ATH9K_HTC_DEBUGFS -DCONFIG_RT2X00_LIB_DEBUGFS) \ $(if $(CONFIG_PACKAGE_MAC80211_MESH),-DCONFIG_MAC80211_MESH) \ - $(if $(CONFIG_PACKAGE_ATH_DEBUG),-DCONFIG_ATH_DEBUG -DCONFIG_ATH9K_PKTLOG) \ + $(if $(CONFIG_PACKAGE_ATH_DEBUG),-DCONFIG_ATH_DEBUG -DCONFIG_ATH9K_PKTLOG -DCONFIG_ATH9K_MAC_DEBUG -DCONFIG_ATH5K_DEBUG) \ -D__CONFIG_MAC80211_RC_DEFAULT=minstrel \ -DCONFIG_MAC80211_RC_MINSTREL_HT \ $(if $(CONFIG_ATH_USER_REGD),-DATH_USER_REGD=1) \ @@ -1185,7 +1177,6 @@ BUILDFLAGS:= \ $(if $(CONFIG_PACKAGE_B43_PHY_LCN),-DCONFIG_B43_PHY_LCN) \ -DCONFIG_B43_BCMA -DCONFIG_B43_BCMA_EXTRA \ -DCONFIG_B43_SSB \ - $(if $(CONFIG_PACKAGE_RT2X00_LIB_DEBUGFS),-DCONFIG_RT2X00_LIB_DEBUGFS) \ $(if $(CONFIG_PACKAGE_RT2X00_DEBUG),-DCONFIG_RT2X00_DEBUG) \ $(if $(NEED_RT2X00_LIB_HT),-DCONFIG_RT2X00_LIB_HT) \ $(if $(NEED_RT2X00_LIB_CRYPTO),-DCONFIG_RT2X00_LIB_CRYPTO) \ @@ -1239,7 +1230,7 @@ MAKE_OPTS:= \ CONFIG_ATH5K=$(if $(CONFIG_PACKAGE_kmod-ath5k),m) \ CONFIG_ATH5K_PCI=$(if $(CONFIG_TARGET_atheros),,y) \ CONFIG_ATH5K_AHB=$(if $(CONFIG_TARGET_atheros),y) \ - CONFIG_ATH5K_DEBUG=$(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),y) \ + CONFIG_ATH5K_DEBUG=$(if $(CONFIG_PACKAGE_ATH_DEBUG),y) \ CONFIG_ATH9K=$(if $(CONFIG_PACKAGE_kmod-ath9k),m) \ CONFIG_ATH9K_PCI=$(CONFIG_PCI) \ CONFIG_ATH9K_AHB=$(if $(CONFIG_TARGET_ar71xx),y) \ @@ -1248,6 +1239,7 @@ MAKE_OPTS:= \ CONFIG_ATH9K_HW=$(if $(CONFIG_PACKAGE_kmod-ath9k-common),m) \ CONFIG_ATH9K_COMMON=$(if $(CONFIG_PACKAGE_kmod-ath9k-common),m) \ CONFIG_ATH9K_DEBUGFS=$(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),y) \ + CONFIG_ATH9K_MAC_DEBUG=$(if $(CONFIG_PACKAGE_ATH_DEBUG),y) \ CONFIG_CARL9170=$(if $(CONFIG_PACKAGE_kmod-carl9170),m) \ CONFIG_CARL9170_DEBUGFS=$(if $(CONFIG_PACKAGE_MAC80211_DEBUGFS),y) \ CONFIG_COMPAT_ZD1211RW=$(if $(CONFIG_PACKAGE_kmod-zd1211rw),m) \ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
* Hauke Mehrtens [03.01.2013 21:30]: > I would not add it as a global option, but as a module, so it could also > be used by someone not building his own image, but using a prebuild > image, with kernel 3.6.11 I had a problem building this as a module. > > The swap utils e.g. from busybox are also needed, this increases the > busybox binary by 3.2K uncompressed. > CONFIG_BUSYBOX_CONFIG_MKSWAP=y > CONFIG_BUSYBOX_CONFIG_SWAPONOFF=y > > Attached is a patch adding zram as a module. The default image without > zram should be 3.2K bigger (uncompressed) but there are no more > influences to a image without zram support. Bastian could you test this > and give feedback? i compiled it for 2 different platforms (ar7xxx + brcm47xx) and it mostly works, these are my issues: - zram initfile is not enabled by default, there is some magic needed in the Makefile, e.g. '$(INSTALL_BIN) ./files/zram.init $(1)/etc/init.d/zram' - the minor "error during uci calls an unset var" is fixed: https://github.com/bittorf/kalua/blob/master/openwrt-addons/etc/init.d/zram diff: https://github.com/bittorf/kalua/commit/078b53388f08cf752b32e4606bf8c60ce7630847 - MKSWAP and SWAPONOFF has to be a dependency, the old package compcache does this via DEPENDS:=@BUSYBOX_CONFIG_SWAPONOFF @BUSYBOX_CONFIG_MKSWAP but: gogogo! it's working - we want it 8-) bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
On 2013-01-03 9:17 PM, Hauke Mehrtens wrote: > diff --git a/package/kernel/modules/other.mk b/package/kernel/modules/other.mk > index 2374d19..b3bf6fd 100644 > --- a/package/kernel/modules/other.mk > +++ b/package/kernel/modules/other.mk > @@ -729,3 +729,40 @@ define KernelPackage/ikconfig/description > endef > > $(eval $(call KernelPackage,ikconfig)) > + > +define KernelPackage/zsmalloc > + SUBMENU:=$(OTHER_MENU) > + TITLE:=ZSMALLOC > + DEPENDS:=@!LINUX_3_3 > + KCONFIG:=CONFIG_ZSMALLOC > + FILES:=$(LINUX_DIR)/drivers/staging/zsmalloc/zsmalloc.ko > + AUTOLOAD:=$(call AutoLoad,20,zsmalloc) > +endef > + > +define KernelPackage/zsmalloc/description > + Memory allocator for compressed pages > +endef > + > +$(eval $(call KernelPackage,zsmalloc)) > + > +define KernelPackage/zram > + SUBMENU:=$(OTHER_MENU) > + TITLE:=ZRAM > + DEPENDS:=+kmod-lib-lzo +kmod-zsmalloc > + KCONFIG:= \ > + CONFIG_ZRAM \ > + CONFIG_ZRAM_DEBUG=n > + FILES:=$(LINUX_DIR)/drivers/staging/zram/zram.ko > + AUTOLOAD:=$(call AutoLoad,25,zram) > +endef > + > +define KernelPackage/zram/description > + Compressed RAM block device support > +endef > + > +define KernelPackage/zram/install > + $(INSTALL_DIR) $(1)/etc/init.d > + $(INSTALL_BIN) ./files/zram $(1)/etc/init.d/zram > +endef > + > +$(eval $(call KernelPackage,zram)) Can you merge these two into one package? I don't think there's anything else using zsmalloc, so there's no need to add an extra package for it. The rest looks good to me. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] mac80211: add dependency of PACKAGE_MAC80211_DEBUGFS
On 2013-01-04 5:20 PM, Stefan Hellermann wrote: > mac80211: add dependency of PACKAGE_MAC80211_DEBUGFS > > I wanted to use some statistics from /sys/kernel/debug/ieee80211, > so I enabled PACKAGE_MAC80211_DEBUGFS. But I could not use it, > because CONFIG_KERNEL_DEBUG_FS was not set and it's a little bit > hidden. After manually setting CONFIG_KERNEL_DEBUG_FS to y, > everything was fine. This patch automatically selects > CONFIG_KERNEL_DEBUG_FS if PACKAGE_MAC80211_DEBUGFS is set. > > Additionally, the help text says "Say N unless you know you need this.", > but it's default y. This help text is copied verbatim from the > kernel's Kconfig and not true for us. So remove this part of the > help text > > Signed-off-by: Stefan Hellermann Applied in r35014, thanks. By the way, you don't need to repeat the subject in the message body, git-am includes the subject as the first line in the commit message. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [RFC][PATCH][v2] Asterisk 11 package
Hello everyone,
I've made newer version of Asterisk package. Previous version located at
http://patchwork.openwrt.org/patch/2898/ had some issues with crosscompiling
Asterisk's SIP stack PJSIP. Current version should not suffer from incorrectly
compiled PJSIP built inside the Asterisk.
I would really appreciate if anyone would love to review my latest patch that
brings the latest LTS Asterisk11 version to OpenWrt. Also I would appreciate if
anyone would love to test this package if it works on different platforms.
Thank you so much
Signed-off-by: Jiri Slachta
Index: feeds/packages/net/asterisk-11.x/patches/100-build_tools-iconv.patch
===
--- feeds/packages/net/asterisk-11.x/patches/100-build_tools-iconv.patch
(revision 0)
+++ feeds/packages/net/asterisk-11.x/patches/100-build_tools-iconv.patch
(revision 0)
@@ -0,0 +1,11 @@
+--- a/build_tools/menuselect-deps.in
b/build_tools/menuselect-deps.in
+@@ -18,7 +18,7 @@ GTK2=@PBX_GTK2@
+ H323=@PBX_H323@
+ HOARD=@PBX_HOARD@
+ ICAL=@PBX_ICAL@
+-ICONV=@PBX_ICONV@
++ICONV=0
+ IKSEMEL=@PBX_IKSEMEL@
+ IMAP_TK=@PBX_IMAP_TK@
+ IODBC=@PBX_IODBC@
Index: feeds/packages/net/asterisk-11.x/patches/500-nres.patch
===
--- feeds/packages/net/asterisk-11.x/patches/500-nres.patch (revision 0)
+++ feeds/packages/net/asterisk-11.x/patches/500-nres.patch (revision 0)
@@ -0,0 +1,11 @@
+--- a/configure
b/configure
+@@ -24044,7 +24044,7 @@
+ $as_echo "yes" >&6; }
+
+ cat >>confdefs.h <<\_ACEOF
+-#define HAVE_RES_NINIT 1
++//#define HAVE_RES_NINIT 1
+ _ACEOF
+
+ { $as_echo "$as_me:$LINENO: checking for library containing
res_9_ndestroy" >&5
Index:
feeds/packages/net/asterisk-11.x/patches/600-cross-compile-check-pjproject.patch
===
---
feeds/packages/net/asterisk-11.x/patches/600-cross-compile-check-pjproject.patch
(revision 0)
+++
feeds/packages/net/asterisk-11.x/patches/600-cross-compile-check-pjproject.patch
(revision 0)
@@ -0,0 +1,89 @@
+--- a/res/pjproject/aconfigure
b/res/pjproject/aconfigure
+@@ -2898,46 +2898,46 @@
+ ac_clean_files="$ac_clean_files conftest.out"
+ # Check that the compiler produces executables we can run. If not, either
+ # the compiler is broken, or we cross compile.
+-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are cross
compiling" >&5
+-$as_echo_n "checking whether we are cross compiling... " >&6; }
+-if test "$cross_compiling" != yes; then
+- { { ac_try="$ac_link"
+-case "(($ac_try" in
+- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
+- *) ac_try_echo=$ac_try;;
+-esac
+-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
+-$as_echo "$ac_try_echo"; } >&5
+- (eval "$ac_link") 2>&5
+- ac_status=$?
+- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
+- test $ac_status = 0; }
+- if { ac_try='./conftest$ac_cv_exeext'
+- { { case "(($ac_try" in
+- *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
+- *) ac_try_echo=$ac_try;;
+-esac
+-eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
+-$as_echo "$ac_try_echo"; } >&5
+- (eval "$ac_try") 2>&5
+- ac_status=$?
+- $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
+- test $ac_status = 0; }; }; then
+-cross_compiling=no
+- else
+-if test "$cross_compiling" = maybe; then
+- cross_compiling=yes
+-else
+- { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
+-$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
+-as_fn_error "cannot run C compiled programs.
+-If you meant to cross compile, use \`--host'.
+-See \`config.log' for more details." "$LINENO" 5; }
+-fi
+- fi
+-fi
+-{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
+-$as_echo "$cross_compiling" >&6; }
++#{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are cross
compiling" >&5
++#$as_echo_n "checking whether we are cross compiling... " >&6; }
++#if test "$cross_compiling" != yes; then
++# { { ac_try="$ac_link"
++#case "(($ac_try" in
++# *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
++# *) ac_try_echo=$ac_try;;
++#esac
++#eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
++#$as_echo "$ac_try_echo"; } >&5
++# (eval "$ac_link") 2>&5
++# ac_status=$?
++# $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
++# test $ac_status = 0; }
++# if { ac_try='./conftest$ac_cv_exeext'
++# { { case "(($ac_try" in
++# *\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
++# *) ac_try_echo=$ac_try;;
++#esac
++#eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
++#$as_echo "$ac_try_echo"; } >&5
++# (eval "$ac_try") 2>&5
++# ac_status=$?
++# $as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
++# test $ac_status = 0; }; }; then
++#cross_compiling=no
++# else
++#if test "$cross_compiling" = maybe; then
++# cross_compiling=yes
++#
[OpenWrt-Devel] [PATCH] Added default configurations for enabling wifi on omap4 by default
Hi Imre Kaloz, With default configurations omap4(Pandaboard) WIFI is not working and Ethernet is in lan group. So added default configuration files of a working router(pandaboard)to change eth0 to wan and added working wlan configs. Signed-off-by: dvrao Index: target/linux/omap4/base-files/etc/config/wireless === --- target/linux/omap4/base-files/etc/config/wireless(revision 0) +++ target/linux/omap4/base-files/etc/config/wireless(revision 0) @@ -0,0 +1,19 @@ + +config wifi-device 'radio0' +option type 'mac80211' +option channel '11' +option path 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' +list ht_capab 'GF' +list ht_capab 'SHORT-GI-20' +list ht_capab 'RX-STBC1' +option txpower '25' +option hwmode '11g' +option country '00' + +config wifi-iface +option device 'radio0' +option mode 'ap' +option ssid 'Panda' +option encryption 'none' +option network 'lan' + Property changes on: target/linux/omap4/base-files/etc/config/wireless ___ Added: svn:executable + * Index: target/linux/omap4/base-files/etc/config/network === --- target/linux/omap4/base-files/etc/config/network(revision 0) +++ target/linux/omap4/base-files/etc/config/network(revision 0) @@ -0,0 +1,19 @@ + +config interface 'loopback' +option ifname 'lo' +option proto 'static' +option ipaddr '127.0.0.1' +option netmask '255.0.0.0' + +config interface 'lan' +option type 'bridge' +option proto 'static' +option ipaddr '192.168.1.1' +option netmask '255.255.255.0' +option _orig_ifname 'eth0 radio0.network1' +option _orig_bridge 'true' + +config interface 'wan' +option proto 'dhcp' +option ifname 'eth0' + Property changes on: target/linux/omap4/base-files/etc/config/network ___ Added: svn:executable + * Index: target/linux/omap4/base-files/etc/config/luci === --- target/linux/omap4/base-files/etc/config/luci(revision 0) +++ target/linux/omap4/base-files/etc/config/luci(revision 0) @@ -0,0 +1,28 @@ + +config core 'main' +option lang 'auto' +option mediaurlbase '/luci-static/openwrt.org' +option resourcebase '/luci-static/resources' + +config extern 'flash_keep' +option uci '/etc/config/' +option dropbear '/etc/dropbear/' +option openvpn '/etc/openvpn/' +option passwd '/etc/passwd' +option opkg '/etc/opkg.conf' +option firewall '/etc/firewall.user' +option uploads '/lib/uci/upload/' + +config internal 'languages' +option en 'English' + +config internal 'sauth' +option sessionpath '/tmp/luci-sessions' +option sessiontime '3600' + +config internal 'ccache' +option enable '1' + +config internal 'themes' +option OpenWrt '/luci-static/openwrt.org' + Property changes on: target/linux/omap4/base-files/etc/config/luci ___ Added: svn:executable + * ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Added default configurations for enabling wifi on omap4 by default
On 2013-01-04 9:11 PM, dvrao wrote: > Hi Imre Kaloz, > > With default configurations omap4(Pandaboard) WIFI is not working and > Ethernet is in lan group. > So added default configuration files of a working router(pandaboard)to > change eth0 to wan and added working wlan configs. > > > Signed-off-by: dvrao > > Index: target/linux/omap4/base-files/etc/config/wireless > === > --- target/linux/omap4/base-files/etc/config/wireless(revision 0) > +++ target/linux/omap4/base-files/etc/config/wireless(revision 0) > @@ -0,0 +1,19 @@ > + > +config wifi-device 'radio0' > +option type 'mac80211' > +option channel '11' > +option path > 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' > +list ht_capab 'GF' > +list ht_capab 'SHORT-GI-20' > +list ht_capab 'RX-STBC1' > +option txpower '25' > +option hwmode '11g' > +option country '00' > + > +config wifi-iface > +option device 'radio0' > +option mode 'ap' > +option ssid 'Panda' > +option encryption 'none' > +option network 'lan' > + > The default configuration in OpenWrt intentionally does not enable unconfigured, unencrypted wifi by default, as it would expose access to LAN at a potentially inconvenient time. Please leave out /etc/config/wireless - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Added default configurations for enabling wifi on omap4 by default
On Saturday 05 January 2013 01:48 AM, Felix Fietkau wrote: On 2013-01-04 9:11 PM, dvrao wrote: Hi Imre Kaloz, With default configurations omap4(Pandaboard) WIFI is not working and Ethernet is in lan group. So added default configuration files of a working router(pandaboard)to change eth0 to wan and added working wlan configs. Signed-off-by: dvrao Index: target/linux/omap4/base-files/etc/config/wireless === --- target/linux/omap4/base-files/etc/config/wireless(revision 0) +++ target/linux/omap4/base-files/etc/config/wireless(revision 0) @@ -0,0 +1,19 @@ + +config wifi-device 'radio0' +option type 'mac80211' +option channel '11' +option path 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' +list ht_capab 'GF' +list ht_capab 'SHORT-GI-20' +list ht_capab 'RX-STBC1' +option txpower '25' +option hwmode '11g' +option country '00' + +config wifi-iface +option device 'radio0' +option mode 'ap' +option ssid 'Panda' +option encryption 'none' +option network 'lan' + The default configuration in OpenWrt intentionally does not enable unconfigured, unencrypted wifi by default, as it would expose access to LAN at a potentially inconvenient time. Please leave out /etc/config/wireless - Felix Hi Felix Fietkau, As Panda have one Ethernet(WAN mode) and one WIFI Module(LAN). To access the WEB UI of OpenWrt at least one LAN module must be enabled. As we have only WIFI module in LAN mode I enabled it by default to connect and configure initially (after we can enable security). Is there any way to connect and configure from WAN ? Thanks & Regards, dvrao. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Added default configurations for enabling wifi on omap4 by default
On 2013-01-04 9:37 PM, dvrao wrote: > On Saturday 05 January 2013 01:48 AM, Felix Fietkau wrote: >> On 2013-01-04 9:11 PM, dvrao wrote: >>> Hi Imre Kaloz, >>> >>> With default configurations omap4(Pandaboard) WIFI is not working and >>> Ethernet is in lan group. >>> So added default configuration files of a working router(pandaboard)to >>> change eth0 to wan and added working wlan configs. >>> >>> >>> Signed-off-by: dvrao >>> >>> Index: target/linux/omap4/base-files/etc/config/wireless >>> === >>> --- target/linux/omap4/base-files/etc/config/wireless(revision 0) >>> +++ target/linux/omap4/base-files/etc/config/wireless(revision 0) >>> @@ -0,0 +1,19 @@ >>> + >>> +config wifi-device 'radio0' >>> +option type 'mac80211' >>> +option channel '11' >>> +option path >>> 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' >>> +list ht_capab 'GF' >>> +list ht_capab 'SHORT-GI-20' >>> +list ht_capab 'RX-STBC1' >>> +option txpower '25' >>> +option hwmode '11g' >>> +option country '00' >>> + >>> +config wifi-iface >>> +option device 'radio0' >>> +option mode 'ap' >>> +option ssid 'Panda' >>> +option encryption 'none' >>> +option network 'lan' >>> + >>> >> The default configuration in OpenWrt intentionally does not enable >> unconfigured, unencrypted wifi by default, as it would expose access to >> LAN at a potentially inconvenient time. >> Please leave out /etc/config/wireless >> >> - Felix >> > Hi Felix Fietkau, > > As Panda have one Ethernet(WAN mode) and one WIFI Module(LAN). > To access the WEB UI of OpenWrt at least one LAN module must be enabled. > As we have only WIFI module in LAN mode I enabled it by default to > connect and configure initially (after we can enable security). > > Is there any way to connect and configure from WAN ? Maybe you should just leave Ethernet connected to the LAN. Let the user reconfigure it for WAN if necessary. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
Hi. On 4 January 2013 18:25, Bastian Bittorf wrote: > - MKSWAP and SWAPONOFF has to be a dependency, the old package compcache > does this via > > DEPENDS:=@BUSYBOX_CONFIG_SWAPONOFF @BUSYBOX_CONFIG_MKSWAP > I think better dependency would be: define KernelPackage/zram/config select BUSYBOX_CONFIG_MKSWAP if !PACKAGE_swap-utils select BUSYBOX_CONFIG_SWAPONOFF if !PACKAGE_swap-utils endef btw. @devs - is there an openwrt "DEPENDS:=" equivalent for "select if " ? Greets. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Added default configurations for enabling wifi on omap4 by default
On Saturday 05 January 2013 02:19 AM, Felix Fietkau wrote: On 2013-01-04 9:37 PM, dvrao wrote: On Saturday 05 January 2013 01:48 AM, Felix Fietkau wrote: On 2013-01-04 9:11 PM, dvrao wrote: Hi Imre Kaloz, With default configurations omap4(Pandaboard) WIFI is not working and Ethernet is in lan group. So added default configuration files of a working router(pandaboard)to change eth0 to wan and added working wlan configs. Signed-off-by: dvrao Index: target/linux/omap4/base-files/etc/config/wireless === --- target/linux/omap4/base-files/etc/config/wireless(revision 0) +++ target/linux/omap4/base-files/etc/config/wireless(revision 0) @@ -0,0 +1,19 @@ + +config wifi-device 'radio0' +option type 'mac80211' +option channel '11' +option path 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' +list ht_capab 'GF' +list ht_capab 'SHORT-GI-20' +list ht_capab 'RX-STBC1' +option txpower '25' +option hwmode '11g' +option country '00' + +config wifi-iface +option device 'radio0' +option mode 'ap' +option ssid 'Panda' +option encryption 'none' +option network 'lan' + The default configuration in OpenWrt intentionally does not enable unconfigured, unencrypted wifi by default, as it would expose access to LAN at a potentially inconvenient time. Please leave out /etc/config/wireless - Felix Hi Felix Fietkau, As Panda have one Ethernet(WAN mode) and one WIFI Module(LAN). To access the WEB UI of OpenWrt at least one LAN module must be enabled. As we have only WIFI module in LAN mode I enabled it by default to connect and configure initially (after we can enable security). Is there any way to connect and configure from WAN ? Maybe you should just leave Ethernet connected to the LAN. Let the user reconfigure it for WAN if necessary. - Felix Hi Felix Fietkau, Thanks for your support I have updated the patch. Please check. Signed-off-by: dvrao Index: target/linux/omap4/base-files/etc/config/network === --- target/linux/omap4/base-files/etc/config/network(revision 0) +++ target/linux/omap4/base-files/etc/config/network(revision 0) @@ -0,0 +1,19 @@ + +config interface 'loopback' +option ifname 'lo' +option proto 'static' +option ipaddr '127.0.0.1' +option netmask '255.0.0.0' + +config interface 'lan' +option ifname 'eth0' +option type 'bridge' +option proto 'static' +option ipaddr '192.168.1.1' +option netmask '255.255.255.0' +option _orig_ifname 'eth0 radio0.network1' +option _orig_bridge 'true' + +config interface 'wan' +option proto 'dhcp' + Property changes on: target/linux/omap4/base-files/etc/config/network ___ Added: svn:executable + * Index: target/linux/omap4/base-files/etc/config/luci === --- target/linux/omap4/base-files/etc/config/luci(revision 0) +++ target/linux/omap4/base-files/etc/config/luci(revision 0) @@ -0,0 +1,28 @@ + +config core 'main' +option lang 'auto' +option mediaurlbase '/luci-static/openwrt.org' +option resourcebase '/luci-static/resources' + +config extern 'flash_keep' +option uci '/etc/config/' +option dropbear '/etc/dropbear/' +option openvpn '/etc/openvpn/' +option passwd '/etc/passwd' +option opkg '/etc/opkg.conf' +option firewall '/etc/firewall.user' +option uploads '/lib/uci/upload/' + +config internal 'languages' +option en 'English' + +config internal 'sauth' +option sessionpath '/tmp/luci-sessions' +option sessiontime '3600' + +config internal 'ccache' +option enable '1' + +config internal 'themes' +option OpenWrt '/luci-static/openwrt.org' + Property changes on: target/linux/omap4/base-files/etc/config/luci ___ Added: svn:executable + * Index: target/linux/omap4/base-files/etc/config/wireless === --- target/linux/omap4/base-files/etc/config/wireless(revision 0) +++ target/linux/omap4/base-files/etc/config/wireless(revision 0) @@ -0,0 +1,20 @@ + +config wifi-device 'radio0' +option type 'mac80211' +option channel '11' +option path 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' +list ht_capab 'GF' +list ht_capab 'SHORT-GI-20' +list ht_capab 'RX-STBC1' +option txpower '25' +option hwmode '11g' +option country '00' + +config wifi-iface +option device 'radio0' +option mode 'ap' +option ssid 'Panda' +option encryption 'none' +option network 'lan' +option disabled '1' + Property changes on: target/linux/omap4/base-files/etc/config/wireless
Re: [OpenWrt-Devel] [PATCH] Added default configurations for enabling wifi on omap4 by default
Hi dvrao, Generally in OpenWrt wireless is not configured automatically even with a default disable config. wifi detect is run to determine info about the wlan interface and set default parameters, but left disabled. It shouldn't be on the filesystem. Regards, Daniel On Fri, Jan 4, 2013 at 4:04 PM, dvrao wrote: > On Saturday 05 January 2013 02:19 AM, Felix Fietkau wrote: > >> On 2013-01-04 9:37 PM, dvrao wrote: >> >>> On Saturday 05 January 2013 01:48 AM, Felix Fietkau wrote: >>> On 2013-01-04 9:11 PM, dvrao wrote: > Hi Imre Kaloz, > > With default configurations omap4(Pandaboard) WIFI is not working and > Ethernet is in lan group. > So added default configuration files of a working router(pandaboard)to > change eth0 to wan and added working wlan configs. > > > Signed-off-by: dvrao > > Index: target/linux/omap4/base-files/**etc/config/wireless > ==**==** > === > --- target/linux/omap4/base-files/**etc/config/wireless(revision > 0) > +++ target/linux/omap4/base-files/**etc/config/wireless(revision > 0) > @@ -0,0 +1,19 @@ > + > +config wifi-device 'radio0' > +option type 'mac80211' > +option channel '11' > +option path > 'platform/omap/omap_hsmmc.4/**mmc_host/mmc1/mmc1:0001/mmc1:** > 0001:2/wl12xx' > +list ht_capab 'GF' > +list ht_capab 'SHORT-GI-20' > +list ht_capab 'RX-STBC1' > +option txpower '25' > +option hwmode '11g' > +option country '00' > + > +config wifi-iface > +option device 'radio0' > +option mode 'ap' > +option ssid 'Panda' > +option encryption 'none' > +option network 'lan' > + > > The default configuration in OpenWrt intentionally does not enable unconfigured, unencrypted wifi by default, as it would expose access to LAN at a potentially inconvenient time. Please leave out /etc/config/wireless - Felix Hi Felix Fietkau, >>> >>> As Panda have one Ethernet(WAN mode) and one WIFI Module(LAN). >>> To access the WEB UI of OpenWrt at least one LAN module must be enabled. >>> As we have only WIFI module in LAN mode I enabled it by default to >>> connect and configure initially (after we can enable security). >>> >>> Is there any way to connect and configure from WAN ? >>> >> Maybe you should just leave Ethernet connected to the LAN. Let the user >> reconfigure it for WAN if necessary. >> >> - Felix >> >> Hi Felix Fietkau, > > Thanks for your support I have updated the patch. Please check. > > Signed-off-by: dvrao > > > Index: target/linux/omap4/base-files/**etc/config/network > ==**==**=== > --- target/linux/omap4/base-files/**etc/config/network(revision 0) > +++ target/linux/omap4/base-files/**etc/config/network(revision 0) > > @@ -0,0 +1,19 @@ > + > +config interface 'loopback' > +option ifname 'lo' > +option proto 'static' > +option ipaddr '127.0.0.1' > +option netmask '255.0.0.0' > + > +config interface 'lan' > +option ifname 'eth0' > > +option type 'bridge' > +option proto 'static' > +option ipaddr '192.168.1.1' > +option netmask '255.255.255.0' > +option _orig_ifname 'eth0 radio0.network1' > +option _orig_bridge 'true' > + > +config interface 'wan' > +option proto 'dhcp' > + > > Property changes on: target/linux/omap4/base-files/**etc/config/network > __**__**___ > Added: svn:executable >+ * > > Index: target/linux/omap4/base-files/**etc/config/luci > ==**==**=== > --- target/linux/omap4/base-files/**etc/config/luci(revision 0) > +++ target/linux/omap4/base-files/**etc/config/luci(revision 0) > @@ -0,0 +1,28 @@ > + > +config core 'main' > +option lang 'auto' > +option mediaurlbase '/luci-static/openwrt.org' > +option resourcebase '/luci-static/resources' > + > +config extern 'flash_keep' > +option uci '/etc/config/' > +option dropbear '/etc/dropbear/' > +option openvpn '/etc/openvpn/' > +option passwd '/etc/passwd' > +option opkg '/etc/opkg.conf' > +option firewall '/etc/firewall.user' > +option uploads '/lib/uci/upload/' > + > +config internal 'languages' > +option en 'English' > + > +config internal 'sauth' > +option sessionpath '/tmp/luci-sessions' > +option sessiontime '3600' > + > +config internal 'ccache' > +option enable '1' > + > +config internal 'themes' > +option OpenWrt '/luci-static/openwrt.org' > + > > Property changes on: target/linux/omap4/base-files/**etc/config/luci > __**__**___ > Added: svn:executable >+ * > > Index: target/linux/omap4/base-files/**etc/config/wireless > =
Re: [OpenWrt-Devel] [PATCH] Added default configurations for enabling wifi on omap4 by default
On 2013-01-04 10:04 PM, dvrao wrote: > On Saturday 05 January 2013 02:19 AM, Felix Fietkau wrote: >> On 2013-01-04 9:37 PM, dvrao wrote: >>> On Saturday 05 January 2013 01:48 AM, Felix Fietkau wrote: On 2013-01-04 9:11 PM, dvrao wrote: > Hi Imre Kaloz, > > With default configurations omap4(Pandaboard) WIFI is not working and > Ethernet is in lan group. > So added default configuration files of a working router(pandaboard)to > change eth0 to wan and added working wlan configs. > > > Signed-off-by: dvrao > > Index: target/linux/omap4/base-files/etc/config/wireless > === > --- target/linux/omap4/base-files/etc/config/wireless(revision 0) > +++ target/linux/omap4/base-files/etc/config/wireless(revision 0) > @@ -0,0 +1,19 @@ > + > +config wifi-device 'radio0' > +option type 'mac80211' > +option channel '11' > +option path > 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' > +list ht_capab 'GF' > +list ht_capab 'SHORT-GI-20' > +list ht_capab 'RX-STBC1' > +option txpower '25' > +option hwmode '11g' > +option country '00' > + > +config wifi-iface > +option device 'radio0' > +option mode 'ap' > +option ssid 'Panda' > +option encryption 'none' > +option network 'lan' > + > The default configuration in OpenWrt intentionally does not enable unconfigured, unencrypted wifi by default, as it would expose access to LAN at a potentially inconvenient time. Please leave out /etc/config/wireless - Felix >>> Hi Felix Fietkau, >>> >>> As Panda have one Ethernet(WAN mode) and one WIFI Module(LAN). >>> To access the WEB UI of OpenWrt at least one LAN module must be enabled. >>> As we have only WIFI module in LAN mode I enabled it by default to >>> connect and configure initially (after we can enable security). >>> >>> Is there any way to connect and configure from WAN ? >> Maybe you should just leave Ethernet connected to the LAN. Let the user >> reconfigure it for WAN if necessary. >> >> - Felix >> > Hi Felix Fietkau, > > Thanks for your support I have updated the patch. Please check. > > Signed-off-by: dvrao You have way too many generic config files in there. A target isn't supposed to contain a luci config or the wireless config (generated at first boot). Also, if ethernet by default already comes up with ethernet configured to LAN, why add a new config file? - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
On 4 January 2013 21:52, Damian Kaczkowski wrote: > On 4 January 2013 18:25, Bastian Bittorf wrote: > >> - MKSWAP and SWAPONOFF has to be a dependency, the old package compcache >> does this via >> >> DEPENDS:=@BUSYBOX_CONFIG_SWAPONOFF @BUSYBOX_CONFIG_MKSWAP >> > > I think better dependency would be: > > define KernelPackage/zram/config > select BUSYBOX_CONFIG_MKSWAP if !PACKAGE_swap-utils > select BUSYBOX_CONFIG_SWAPONOFF if !PACKAGE_swap-utils > endef > btw. Do we really need dependency for mkswap / swaponoff ? You can use any fs on zram disk not only swap (also your init script already checks for mkswap and swapon bins (but not swapoff btw.)). Maybe better would be what hauke proposed? - just set CONFIG_BUSYBOX_CONFIG_MKSWAP=y, CONFIG_BUSYBOX_CONFIG_SWAPONOFF=y as default config. Then also some other packages might benefit from this, eg. block-mount ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
On 13-01-04 04:23 PM, Damian Kaczkowski wrote: On 4 January 2013 21:52, Damian Kaczkowski wrote: On 4 January 2013 18:25, Bastian Bittorf wrote: - MKSWAP and SWAPONOFF has to be a dependency, the old package compcache does this via DEPENDS:=@BUSYBOX_CONFIG_SWAPONOFF @BUSYBOX_CONFIG_MKSWAP I think better dependency would be: define KernelPackage/zram/config select BUSYBOX_CONFIG_MKSWAP if !PACKAGE_swap-utils select BUSYBOX_CONFIG_SWAPONOFF if !PACKAGE_swap-utils endef btw. Do we really need dependency for mkswap / swaponoff ? You can use any fs on zram disk not only swap (also your init script already checks for mkswap and swapon bins (but not swapoff btw.)). Maybe better would be what hauke proposed? - just set CONFIG_BUSYBOX_CONFIG_MKSWAP=y, CONFIG_BUSYBOX_CONFIG_SWAPONOFF=y as default config. Then also some other packages might benefit from this, eg. block-mount Actually swaponoff and mkswap were ditched by default due to size (block-mount is an optional package). Also depends that change busybox configuration are considered bad and it was an error to have them before (it creates incompatible bb builds depending on what packages are built). Better only have the util-linux dependency (if it's even needed). -- Daniel Dickinson PowerCloud Systems, Palo Alto, CA Senior Firmware Engineer (In Canada: Senior Firmware Analyst) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Added default configurations for enabling wifi on omap4 by default
On Saturday 05 January 2013 02:49 AM, Felix Fietkau wrote: On 2013-01-04 10:04 PM, dvrao wrote: On Saturday 05 January 2013 02:19 AM, Felix Fietkau wrote: On 2013-01-04 9:37 PM, dvrao wrote: On Saturday 05 January 2013 01:48 AM, Felix Fietkau wrote: On 2013-01-04 9:11 PM, dvrao wrote: Hi Imre Kaloz, With default configurations omap4(Pandaboard) WIFI is not working and Ethernet is in lan group. So added default configuration files of a working router(pandaboard)to change eth0 to wan and added working wlan configs. Signed-off-by: dvrao Index: target/linux/omap4/base-files/etc/config/wireless === --- target/linux/omap4/base-files/etc/config/wireless(revision 0) +++ target/linux/omap4/base-files/etc/config/wireless(revision 0) @@ -0,0 +1,19 @@ + +config wifi-device 'radio0' +option type 'mac80211' +option channel '11' +option path 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' +list ht_capab 'GF' +list ht_capab 'SHORT-GI-20' +list ht_capab 'RX-STBC1' +option txpower '25' +option hwmode '11g' +option country '00' + +config wifi-iface +option device 'radio0' +option mode 'ap' +option ssid 'Panda' +option encryption 'none' +option network 'lan' + The default configuration in OpenWrt intentionally does not enable unconfigured, unencrypted wifi by default, as it would expose access to LAN at a potentially inconvenient time. Please leave out /etc/config/wireless - Felix Hi Felix Fietkau, As Panda have one Ethernet(WAN mode) and one WIFI Module(LAN). To access the WEB UI of OpenWrt at least one LAN module must be enabled. As we have only WIFI module in LAN mode I enabled it by default to connect and configure initially (after we can enable security). Is there any way to connect and configure from WAN ? Maybe you should just leave Ethernet connected to the LAN. Let the user reconfigure it for WAN if necessary. - Felix Hi Felix Fietkau, Thanks for your support I have updated the patch. Please check. Signed-off-by: dvrao You have way too many generic config files in there. A target isn't supposed to contain a luci config or the wireless config (generated at first boot). Also, if ethernet by default already comes up with ethernet configured to LAN, why add a new config file? - Felix Hi Felix Fietkau,Daniel, I have removed luci config file in the updated patch below. major concern of this patch is * By default create WAN group (instead of creating manually). * default generated wireless config is not working for OMAP4 TIWI-BLE module, after small change of the hwmod it is working. because of that I added wireless config (disabled mode). Please find the updated patch. Signed-off-by: dvrao Index: target/linux/omap4/base-files/etc/config/network === --- target/linux/omap4/base-files/etc/config/network(revision 0) +++ target/linux/omap4/base-files/etc/config/network(revision 0) @@ -0,0 +1,19 @@ + +config interface 'loopback' + option ifname 'lo' + option proto 'static' + option ipaddr '127.0.0.1' + option netmask '255.0.0.0' + +config interface 'lan' + option ifname 'eth0' + option type 'bridge' + option proto 'static' + option ipaddr '192.168.1.1' + option netmask '255.255.255.0' + option _orig_ifname 'eth0 radio0.network1' + option _orig_bridge 'true' + +config interface 'wan' + option proto 'dhcp' + Property changes on: target/linux/omap4/base-files/etc/config/network ___ Added: svn:executable + * Index: target/linux/omap4/base-files/etc/config/wireless === --- target/linux/omap4/base-files/etc/config/wireless (revision 0) +++ target/linux/omap4/base-files/etc/config/wireless (revision 0) @@ -0,0 +1,19 @@ + +config wifi-device 'radio0' + option type 'mac80211' + option channel '11' + option path 'platform/omap/omap_hsmmc.4/mmc_host/mmc1/mmc1:0001/mmc1:0001:2/wl12xx' + list ht_capab 'GF' + list ht_capab 'SHORT-GI-20' + list ht_capab 'RX-STBC1' + option txpower '25' + option hwmode '11g' + option country '00' + +config wifi-iface + option device 'radio0' + option network 'lan' + option mode 'ap' + option ssid 'OpenWrt' + option encryption 'none' + option disabled '1' ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
> I think better dependency would be: > > define KernelPackage/zram/config > select BUSYBOX_CONFIG_MKSWAP if !PACKAGE_swap-utils > select BUSYBOX_CONFIG_SWAPONOFF if !PACKAGE_swap-utils > endef > > > btw. > @devs - is there an openwrt "DEPENDS:=" equivalent for "select if > " ? > Yes there is: DEPENDS:=+@!PACKAGE_swap-utils:BUSYBOX_CONFIG_MKSWAP I tried something like this yesterday and added it to http://wiki.openwrt.org/doc/devel/dependencies Cheers, Stefan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
On 4 January 2013 23:46, Stefan Hellermann wrote: > > I think better dependency would be: > > > > define KernelPackage/zram/config > > select BUSYBOX_CONFIG_MKSWAP if !PACKAGE_swap-utils > > select BUSYBOX_CONFIG_SWAPONOFF if !PACKAGE_swap-utils > > endef > > > > > > btw. > > @devs - is there an openwrt "DEPENDS:=" equivalent for "select > if > > " ? > > > > Yes there is: > DEPENDS:=+@!PACKAGE_swap-utils:BUSYBOX_CONFIG_MKSWAP > Nice. Thanks for the hint Stefan! I wanted to use such "DEPENDS" type instead of "define (...)/config" block but unfortunately after converting "Kconfig selects" to equivalent "openwrt DEPENDS:", eg: *DEPENDS:=+@!PACKAGE_swap-utils:BUSYBOX_CONFIG_MKSWAP +@!PACKAGE_swap-utils:BUSYBOX_CONFIG_SWAPONOFF* I got this in opkg control file: *Package: kmod-zram Version: 3.6.11-1 Depends: kernel (=3.6.11-1-479d5850a6a04abbd6713ee6c4ef65ac), kmod-lib-lzo, kmod-zsmalloc, **BUSYBOX_CONFIG_MKSWAP, **BUSYBOX_CONFIG_SWAPONOFF, * This doesn't look good, does it? So I tried to reverse this dependency to allow people using buildroot to have the possibility to optimize their builds and be able to select busybox applets instead of swap-utils package, and also leaving other people using prebuild images the possibility to install this kmod package through opkg with appropriate dependencies. Unfortunately with this: *DEPENDS:=+@!BUSYBOX_CONFIG_MKSWAP:PACKAGE_swap-utils +@!BUSYBOX_CONFIG_SWAPONOFF:PACKAGE_swap-utils* I got this in opkg control file: *Package: kmod-zram Version: 3.6.11-1 Depends: kernel (=3.6.11-1-479d5850a6a04abbd6713ee6c4ef65ac), kmod-lib-lzo, kmod-zsmalloc, PACKAGE_swap-utils, PACKAGE_swap-utils * Which still doesn't look good. @devs: Is there any chance for patch to opkg system so it generates proper "Depends:" in such situations? I mean "swap-utils" instead of " PACKAGE_swap-utils" This would be useful I think. What do you think? btw. shouldn't we move init script to some seperate userspace package and put the dependencies there? zram doesn't need swap-utils ... what if one want to use it for some other stuff. I know that init script is not much for a seperate package... but... is it a good idea to put some init script in kernel module package? btw2. This also doesn't work: *DEPENDS:=+@!BUSYBOX_CONFIG_MKSWAP:swap-utils +@!BUSYBOX_CONFIG_SWAPONOFF:swap-utils* ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
> I wanted to use such "DEPENDS" type instead of "define (...)/config" block > but unfortunately after converting "Kconfig selects" to equivalent "openwrt > DEPENDS:", eg: > > DEPENDS:=+@!PACKAGE_swap-utils:BUSYBOX_CONFIG_MKSWAP > +@!PACKAGE_swap-utils:BUSYBOX_CONFIG_SWAPONOFF > > I got this in opkg control file: > > Package: kmod-zram > Version: 3.6.11-1 > Depends: kernel (=3.6.11-1-479d5850a6a04abbd6713ee6c4ef65ac), kmod-lib-lzo, > kmod-zsmalloc, BUSYBOX_CONFIG_MKSWAP, BUSYBOX_CONFIG_SWAPONOFF, > > This doesn't look good, does it? So I tried to reverse this dependency to > allow people using buildroot to have the possibility to optimize their > builds and be able to select busybox applets instead of swap-utils package, > and also leaving other people using prebuild images the possibility to > install this kmod package through opkg with appropriate dependencies. > > Unfortunately with this: > > DEPENDS:=+@!BUSYBOX_CONFIG_MKSWAP:PACKAGE_swap-utils > +@!BUSYBOX_CONFIG_SWAPONOFF:PACKAGE_swap-utils > > I got this in opkg control file: > > Package: kmod-zram > Version: 3.6.11-1 > Depends: kernel (=3.6.11-1-479d5850a6a04abbd6713ee6c4ef65ac), kmod-lib-lzo, > kmod-zsmalloc, PACKAGE_swap-utils, PACKAGE_swap-utils > > Which still doesn't look good. > > @devs: Is there any chance for patch to opkg system so it generates proper > "Depends:" in such situations? I mean "swap-utils" instead of " > PACKAGE_swap-utils" This would be useful I think. What do you think? That's easy: DEPENDS:=+!BUSYBOX_CONFIG_MKSWAP:swap-utils the @ is only needed if you want to select a symbol. I have never watched into a opkg control file, otherwise I would have seen that busybox depends will not work. For compiling you own image it's fine. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
On 5 January 2013 01:37, Stefan Hellermann wrote: > That's easy: > DEPENDS:=+!BUSYBOX_CONFIG_MKSWAP:swap-utils > > the @ is only needed if you want to select a symbol. I have never > watched into a opkg control file, otherwise I would have seen that > busybox depends will not work. For compiling you own image it's fine. > Unfortunately this doesn't work. Menuconfig does not see the symbol "swap-utils" which is expected behavior. * Symbol: PACKAGE_kmod-zram [=n] x Prompt: kmod-zram Compressed RAM block device x Defined at tmp/.config-package.in:7970 x Location: x -> Kernel modules x -> Other modules x Selects: swap-utils && PACKAGE_kmod-lib-lzo [=y] && swap-utils && PACKAGE_kmod-zsmalloc [=n] * It won't select PACKAGE_swap-utils if BUSYBOX_CONFIG_MKSWAP is *not* set (because it tries to select swap-utils symbol which is nonexistent). Thus leaving package with broken dependencies. I think this has to be workaround/pached on buildroot first so it allows DEPENDS like above and generates proper opkg control files in such situations. Eg: a) It should strip the "PACKAGE_" portion from opkg control file in such case: *DEPENDS:=+!BUSYBOX_CONFIG_MKSWAP:PACKAGE_swap-utils* b) but also It should strip the whole symbol in case it is not a package symbol, eg: *DEPENDS:=+!PACKAGE_swap-utils*:*BUSYBOX_CONFIG_MKSWAP * Then it should work ok I think. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
On 5 January 2013 02:36, Damian Kaczkowski wrote: > I think this has to be workaround/pached on buildroot first so it allows > DEPENDS like above and generates proper opkg control files in such > situations. Eg: > > a) It should strip the "PACKAGE_" portion from opkg control file in such > case: > > *DEPENDS:=+!BUSYBOX_CONFIG_MKSWAP:PACKAGE_swap-utils* > > b) but also It should strip the whole symbol in case it is not a package > symbol, eg: > > *DEPENDS:=+!PACKAGE_swap-utils*:*BUSYBOX_CONFIG_MKSWAP > * > c) or just append "PACKAGE_" to appropriate parts of generated "tmp/. config-package.in" file when used such DEPENDS: *DEPENDS:=+!BUSYBOX_CONFIG_MKSWAP:swap-utils* ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] cns3xxx: fix inverted gpio line config
The logic for setting pin direction was inverted Signed-off-by: Tim Harvey --- .../cns3xxx/files/arch/arm/mach-cns3xxx/gpio.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/target/linux/cns3xxx/files/arch/arm/mach-cns3xxx/gpio.c b/target/linux/cns3xxx/files/arch/arm/mach-cns3xxx/gpio.c index 8fccbbf..4f5d500 100644 --- a/target/linux/cns3xxx/files/arch/arm/mach-cns3xxx/gpio.c +++ b/target/linux/cns3xxx/files/arch/arm/mach-cns3xxx/gpio.c @@ -59,9 +59,9 @@ __set_direction(struct cns3xxx_gpio_chip *cchip, unsigned pin, int input) reg = __raw_readl(cchip->base + GPIO_DIR); if (input) - reg |= 1 << pin; + reg &= ~(1 << pin); else - reg &= !(1 << pin); + reg |= (1 << pin); __raw_writel(reg, cchip->base + GPIO_DIR); } -- 1.7.5.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
> On 5 January 2013 01:37, Stefan Hellermann wrote: >> >> That's easy: >> DEPENDS:=+!BUSYBOX_CONFIG_MKSWAP:swap-utils >> > > Unfortunately this doesn't work. Menuconfig does not see the symbol > "swap-utils" which is expected behavior. > > Symbol: PACKAGE_kmod-zram [=n] > x Prompt: kmod-zram Compressed RAM > block device > x Defined at tmp/.config-package.in:7970 > x Location: > x -> Kernel modules > x -> Other modules > x Selects: swap-utils && PACKAGE_kmod-lib-lzo [=y] && swap-utils && > PACKAGE_kmod-zsmalloc [=n] > > It won't select PACKAGE_swap-utils if BUSYBOX_CONFIG_MKSWAP is not set > (because it tries to select swap-utils symbol which is nonexistent). Thus > leaving package with broken dependencies. > Hmm, here it works! I double checked it! A package with DEPENDS:= +!BUSYBOX_CONFIG_HOSTNAME:net-tools-hostname I compiled it with BUSYBOX_CONFIG_HOSTNAME=y and the resulting opkg does not depend on net-tools-hostname Then I removed BUSYBOX_CONFIG_HOSTNAME and compiled the package again, now it depends on net-tools-hostname and it is even build before my own package. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] cns3xxx: clean up PCI bus topology
This makes the PCI bus topology more standard for devices behind a bridge
Signed-off-by: Tim Harvey
---
.../patches-3.3/066-pcie_bus_topology.patch| 27
1 files changed, 27 insertions(+), 0 deletions(-)
create mode 100644 target/linux/cns3xxx/patches-3.3/066-pcie_bus_topology.patch
diff --git a/target/linux/cns3xxx/patches-3.3/066-pcie_bus_topology.patch
b/target/linux/cns3xxx/patches-3.3/066-pcie_bus_topology.patch
new file mode 100644
index 000..269a0fb
--- /dev/null
+++ b/target/linux/cns3xxx/patches-3.3/066-pcie_bus_topology.patch
@@ -0,0 +1,27 @@
+--- a/arch/arm/mach-cns3xxx/pcie.c
b/arch/arm/mach-cns3xxx/pcie.c
+@@ -79,9 +79,11 @@ static void __iomem *cns3xxx_pci_cfg_bas
+* the first device on the same bus as the CNS PCI bridge.
+*/
+ if (busno == 0) {
+- if (slot > 1)
++ if (slot > 0)
+ return NULL;
+ type = slot;
++ } else if (busno == 1) {
++ type = CNS3XXX_CFG0_TYPE;
+ } else {
+ type = CNS3XXX_CFG1_TYPE;
+ }
+@@ -428,8 +430,9 @@ static void __init cns3xxx_pcie_hw_init(
+ if (!cnspci->linked)
+ return;
+
+- /* Set Device Max_Read_Request_Size to 128 byte */
+- devfn = PCI_DEVFN(1, 0);
++ /* Configure Root Complex: Set Device Max_Read_Request_Size to 128 byte
*/
++ bus.number = 1;
++ devfn = PCI_DEVFN(0, 0);
+ pos = pci_bus_find_capability(&bus, devfn, PCI_CAP_ID_EXP);
+ pci_bus_read_config_word(&bus, devfn, pos + PCI_EXP_DEVCTL, &dc);
+ dc &= ~(0x3 << 12); /* Clear Device Control Register [14:12] */
--
1.7.5.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
On 5 January 2013 02:59, Stefan Hellermann wrote: > Hmm, here it works! I double checked it! > A package with DEPENDS:= +!BUSYBOX_CONFIG_HOSTNAME:net-tools-hostname > > I compiled it with BUSYBOX_CONFIG_HOSTNAME=y and the resulting opkg > does not depend on net-tools-hostname > Then I removed BUSYBOX_CONFIG_HOSTNAME and compiled the package again, > now it depends on net-tools-hostname and it is even build before my > own package. > My bad! You are right Stephan. I apologizes. I have overlooked missing "@" in your DEPENDS ... been testing with "+@!" ... -.- Time to sleep. Sorry all and thank you again Stefan. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] compcache / ramzswap / zram / frontswap
> My bad! You are right Stephan. I apologizes. I have overlooked missing "@" > in your DEPENDS ... been testing with "+@!" ... -.- Time to sleep. Sorry all > and thank you again Stefan. When doing funky DEPENDS always think of poor opkg which has to install a package later. It cannot add a applet to busybox... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] D-Link DIR-600/601(Rev.A1) - Not preserving configurations
I have a few dir 601 A1 and built some images from attitude adjustment URL: svn://svn.openwrt.org/openwrt/branches/attitude_adjustment Repository Root: svn://svn.openwrt.org/openwrt Repository UUID: 3c298f89-4303-0410-b956-a3cf2f4a3e73 Revision: 35014 Node Kind: directory Schedule: normal Last Changed Author: nbd Last Changed Rev: 35003 Last Changed Date: 2013-01-03 15:03:14 -0500 (Thu, 03 Jan 2013) http://wiki.openwrt.org/toh/d-link/dir-600#supported.versions1 I now found out that all opkg packages installed or any configurations done are lost once the router reboots and the system reverts to the default build settings. Is this caused by the lack of jffs2 ? If so... it can be added to the wiki page as still not working. Are there any patches to solve this in trunk ? I also found another problem when set wireless to act as a wds server. It seems that "mode wds" does not work. The SSID does not even shows up on scan and some errors are outputted such as: radio0 (cfg033579): Invalid mode, ignored. Can anyone confirm these reports ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] D-Link DIR-600/601(Rev.A1) - Not preserving configurations
I use dir 601 a1 with no problem. Maybe the problem is the size check and you have too big an image to create a jffs2 partition. Regards, Daniel On 13-01-04 10:40 PM, HeXiLeD wrote: I have a few dir 601 A1 and built some images from attitude adjustment URL: svn://svn.openwrt.org/openwrt/branches/attitude_adjustment Repository Root: svn://svn.openwrt.org/openwrt Repository UUID: 3c298f89-4303-0410-b956-a3cf2f4a3e73 Revision: 35014 Node Kind: directory Schedule: normal Last Changed Author: nbd Last Changed Rev: 35003 Last Changed Date: 2013-01-03 15:03:14 -0500 (Thu, 03 Jan 2013) http://wiki.openwrt.org/toh/d-link/dir-600#supported.versions1 I now found out that all opkg packages installed or any configurations done are lost once the router reboots and the system reverts to the default build settings. Is this caused by the lack of jffs2 ? If so... it can be added to the wiki page as still not working. Are there any patches to solve this in trunk ? I also found another problem when set wireless to act as a wds server. It seems that "mode wds" does not work. The SSID does not even shows up on scan and some errors are outputted such as: radio0 (cfg033579): Invalid mode, ignored. Can anyone confirm these reports ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Daniel Dickinson PowerCloud Systems, Palo Alto, CA Senior Firmware Engineer (In Canada: Senior Firmware Analyst) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
