Re: [OpenWrt-Devel] [PATCH] openssl: version bump
On 06/06/2014 01:00, Florian Fainelli wrote: On Jun 5, 2014 2:54 PM, joerg jungermann j...@borkum.net mailto:j...@borkum.net wrote: today appeared another serious vulnerability in openssl. More info is here http://ccsinjection.lepidum.co.jp. Users are advised to update to openssl 1.0.1h. Thank you for your patch, it was committed in r41026 and 41027. Will there be a backport to AA 12.09? There has been one just applied in r41027 i'll kick the release-builder once i've had breakfast best regards -- Joerg Jungermann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org mailto:openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hotplug / micro-optimization
On 5 Jun 2014 04:19, Bastian Bittorf bitt...@bluebottle.com wrote: i have a router here with 400 vlan-interfaces. i'am still not happy, that an hotplug-event triggers a lot of unneccesary action. I wasn't paying attention but what services are you complaining about? On my router things like dnsmasq, the firewall, miniupnpd, and QoS run /etc/init.d/whatever enabled as the first line of code. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] openssl: version bump
Hi, On Thu, Jun 05, 2014 at 11:54:40PM +0200, joerg jungermann wrote: today appeared another serious vulnerability in openssl. More info is here http://ccsinjection.lepidum.co.jp. Users are advised to update to openssl 1.0.1h. Thank you for your patch, it was committed in r41026 and 41027. Will there be a backport to AA 12.09? Seconded - that would be very welcome (because OpenVPN is vulnerable to CVE-2014-0224). gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de pgpKjTwnFL2Wa.pgp Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] hotplug / micro-optimization
On 2014-06-05 10:31, Bastian Bittorf wrote: i have a router here with 400 vlan-interfaces. i'am still not happy, that an hotplug-event triggers a lot of unneccesary action. i see at least 3 possibilities reduce the load: (beside the upcoming procd-interface job) 1) each script implements something like: #!/bin/sh /etc/init.d/$daemon enabled || exit 0 case $ACTION in ifup) ... ;; esac the part '/etc/init.d/$daemon enabled' is expensive, so we can instead call: . /etc/rc.common /etc/init.d/$daemon enabled || return 0 this saves _some_ cycles (2 seconds here for 400 hotplug-scripts, not much) 2) simply dont call a script when the corresponding daemon is not enabled. i'am not sure, if each hotplug-script has a coressponding /etc/init.d/$daemon script, if so - so would be fine (and easy to do) 3) during bootup or '/etc/init.d/$daemon enable' we build a directory for enabled scripts. while we are at it, we can e.g. call 'ifup'/$ACTION if the daemon supports/implements it, otherwise ignore what will be the best approach? bye, bastian The best approach will be: none of the above. We're going to use the procd 'trigger' support (added in r41008) to avoid having to throw in hotplug scripts for every service. When a service is started from the init script, it adds a network event trigger, meaning it will be called by procd when netifd sends an interface event. For this trigger we can add a time delay, which will aggregate events. Once that is implemented correctly, 400 ifup events in rapid succession will lead to only one series of init script calls instead of 400. With that approach, such micro-optimizations become unnecessary. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Broken b43 package, a bit uncommon dependency
So it appears my patch broke b43 on non-Broadcom targets. Package kmod-b43 is missing dependencies for the following libraries: bcma.ko ssb.ko make[3]: *** [/home/zajec/openwrt/openwrt.git/bin/ar71xx/packages/kmod-b43_3.10.36+2014-05-22-1_ar71xx.ipk] Error 1 My problem is that I can't specify detailed package dependency for kmod-b43, because it depends on package config. 1) If user selects PACKAGE_B43_BUSES_BCMA_AND_SSB b43 depends on bcma and ssb 2) If user selects PACKAGE_B43_BUSES_BCMA b43 depends on bcma 3) If user selects PACKAGE_B43_BUSES_SSB b43 depends on ssb All above configs are defined for KernelPackage/b43/config. Of course I take care of dependency, for example: select PACKAGE_kmod-bcma if !TARGET_brcm47xx , but this doesn't make OpenWrt happy. Any idea how to fix this? -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211: b43: rework package dependency
This fixes: Package kmod-b43 is missing dependencies for the following libraries: bcma.ko ssb.ko on non-Broadcom targets. Signed-off-by: Rafał Miłecki zaj...@gmail.com --- package/kernel/mac80211/Makefile | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index 5654ada..e27b6c5 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -1071,7 +1071,12 @@ define KernelPackage/b43 KCONFIG:= \ CONFIG_HW_RANDOM=y # Depend on PCI_SUPPORT to make sure we can select kmod-bcma or kmod-ssb - DEPENDS+= +kmod-mac80211 +!(TARGET_brcm47xx||TARGET_brcm63xx):PCI_SUPPORT + DEPENDS+=+kmod-mac80211 \ + +!(TARGET_brcm47xx||TARGET_brcm63xx):PCI_SUPPORT \ + +(!(TARGET_brcm47xx||TARGET_brcm63xx)PACKAGE_B43_BUSES_BCMA_AND_SSB):kmod-bcma \ + +(!(TARGET_brcm47xx||TARGET_brcm63xx)PACKAGE_B43_BUSES_BCMA_AND_SSB):kmod-ssb \ + +(!(TARGET_brcm47xx||TARGET_brcm63xx)PACKAGE_B43_BUSES_BCMA):kmod-bcma \ + +(!(TARGET_brcm47xx||TARGET_brcm63xx)PACKAGE_B43_BUSES_SSB):kmod-ssb FILES:=$(PKG_BUILD_DIR)/drivers/net/wireless/b43/b43.ko AUTOLOAD:=$(call AutoProbe,b43) MENU:=1 @@ -1187,16 +1192,12 @@ define KernelPackage/b43/config config PACKAGE_B43_BUSES_BCMA_AND_SSB bool BCMA and SSB - select PACKAGE_kmod-bcma if !TARGET_brcm47xx - select PACKAGE_kmod-ssb if !(TARGET_brcm47xx || TARGET_brcm63xx) config PACKAGE_B43_BUSES_BCMA bool BCMA only - select PACKAGE_kmod-bcma if !TARGET_brcm47xx config PACKAGE_B43_BUSES_SSB bool SSB only - select PACKAGE_kmod-ssb if !(TARGET_brcm47xx || TARGET_brcm63xx) endchoice -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] mac80211: b43: rework package dependency
On Fri, Jun 6, 2014 at 12:50 PM, Rafał Miłecki zaj...@gmail.com wrote: This fixes: Package kmod-b43 is missing dependencies for the following libraries: bcma.ko ssb.ko on non-Broadcom targets. Signed-off-by: Rafał Miłecki zaj...@gmail.com --- package/kernel/mac80211/Makefile | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index 5654ada..e27b6c5 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -1071,7 +1071,12 @@ define KernelPackage/b43 KCONFIG:= \ CONFIG_HW_RANDOM=y # Depend on PCI_SUPPORT to make sure we can select kmod-bcma or kmod-ssb - DEPENDS+= +kmod-mac80211 +!(TARGET_brcm47xx||TARGET_brcm63xx):PCI_SUPPORT + DEPENDS+=+kmod-mac80211 \ + +!(TARGET_brcm47xx||TARGET_brcm63xx):PCI_SUPPORT \ + +(!(TARGET_brcm47xx||TARGET_brcm63xx)PACKAGE_B43_BUSES_BCMA_AND_SSB):kmod-bcma \ brcm63xx does not have bcma built-in, so the dependency is still required there. + +(!(TARGET_brcm47xx||TARGET_brcm63xx)PACKAGE_B43_BUSES_BCMA_AND_SSB):kmod-ssb \ + +(!(TARGET_brcm47xx||TARGET_brcm63xx)PACKAGE_B43_BUSES_BCMA):kmod-bcma \ Same here. + +(!(TARGET_brcm47xx||TARGET_brcm63xx)PACKAGE_B43_BUSES_SSB):kmod-ssb Since we now support building empty ipks for modules built into the kernel, I wonder if we shouldn't just drop the ! dependency of bcma/ssb to bcm47xx/bcm63xx. Then the dependencies could be written much simpler as +(PACKAGE_B43_BUSES_BCMA_AND_SSB||PACKAGE_B43_BUSES_SSB):kmod-ssb \ +(PACKAGE_B43_BUSES_BCMA||PACKAGE_B43_BUSES_BCMA):kmod-bcma Regards Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] mac80211: b43: rework package dependency
On 6 June 2014 13:25, Jonas Gorski j...@openwrt.org wrote: Since we now support building empty ipks for modules built into the kernel, I wonder if we shouldn't just drop the ! dependency of bcma/ssb to bcm47xx/bcm63xx. We definitely need to rethink think... with my patch I got: tmp/.config-package.in:9597:error: recursive dependency detected! tmp/.config-package.in:9597: choice choice contains symbol PACKAGE_kmod-b43 tmp/.config-package.in:9470: symbol PACKAGE_kmod-b43 depends on PACKAGE_B43_BUSES_SSB tmp/.config-package.in:9609: symbol PACKAGE_B43_BUSES_SSB is part of choice choice (didn't notice it earlier :/ ) -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Patch: usb-modeswitch-data update url/version
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Package/utils/usbmode is referring to a file that no longer exists. I've updated the filename and md5sum to the latest version. Signed-off-by: Mark Janssen m...@sig-io.nl - --- package/utils/usbmode/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package/utils/usbmode/Makefile b/package/utils/usbmode/Makefile index 36459a6..c2a54a8 100644 - --- a/package/utils/usbmode/Makefile +++ b/package/utils/usbmode/Makefile @@ -16,7 +16,7 @@ PKG_LICENSE_FILES:= PKG_MAINTAINER:=Felix Fietkau n...@openwrt.org - -PKG_DATA_VERSION:=20131113 +PKG_DATA_VERSION:=20140529 PKG_DATA_URL:=http://www.draisberghof.de/usb_modeswitch PKG_DATA_PATH:=usb-modeswitch-data-$(PKG_DATA_VERSION) PKG_DATA_FILENAME:=$(PKG_DATA_PATH).tar.bz2 @@ -27,7 +27,7 @@ include $(INCLUDE_DIR)/cmake.mk define Download/data FILE:=$(PKG_DATA_FILENAME) URL:=$(PKG_DATA_URL) - - MD5SUM:=7b5ac1226b360ddc366c286e62b3c3a4 + MD5SUM:=dff94177781298aaf0b3c2a3c3dea6b2 endef $(eval $(call Download,data)) - -- Mark Janssen -- Sig-I/O Automatisering m...@sig-io.nl http://sig-io.nl Phone: +31-6-5886.7992 Linux/Unix System Administration, DevOps, Ansible, Networking -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJTkeZsAAoJENhnTY/E9pvSIEcP/1kvrFkbTc7QPnkvuZbKaq2w X5tTRUL61WgFH7ecz1lSlO4wzj4NgA6jMiAIbieOjvjvWgCzWfI1bqyEiWDcuLcK 8ICeL+Ky2IjQi+C+z+T4YlZ3khXxFjuEhZf/+rv2BGsc6tEcFBDvPU6E1vwOT1eT Rs0Whox/X3XbJR1rtJpKxrqOz2EjMCGMlbH8S+ZsDEwk3L0Viqkjnb72g+zyIM2a 7q4dOtA/++itirxi7md/jJm4pyY7A5jWVJrqUcG3Y1hCuUGDTEXXzU8zCduxtqhm 6OunTSE9O0CwbnfcsmGZr7Qx1osCGg+wb40XWpqYIaNvA6cqlrrGVevPWyzvhEhX 2fWXxQos0iMtyqn2G8r0p1aJ6V5tUhmCt8iVe7zhjCaeMr2A7POQZLwJhOcUq1Mn EvxyuES8QLxjvcmdFxecPTpd4taGyYVJ0eTtsWzPwBKhKPefLlYag6MJXGIv8ngd ugzXuBevLEV8WMo5zENeGhWdURKbiPVlKToARG/v/6Lvj/kGxXoEbrkv+Jrn8m5Q WpznxAgurltjAn1Gfj7DQiAwml6oXy0t/wU6M3Fft4c2q689XRuN8w2s1PGVbFD0 mXnFj2BQR1w17+oNopo+/vpewoTJ8DMwKlqY6Dz0T1avDsPZ1tvYHkFucadvIwDD f7Y+uuMQt1CDtwzzFnnv =6CBJ -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Problem compiling kernel 3.3.8 in AA
Hello, I am trying to compile my trunk version of Attitude Adjustment with some USB features enabled for allowing the connection of Atheros USB dongles to a tplink WDR4300ND. However, I am facing always the same problem, the firmware creation process is always stopped at the same point, which can be seen below. I don't know the reason, Just after that I am ask to set again what looks like the kernel configuration, but I am not prompted any error, as far as I can see. I have just tried to compile the kernel, and I was given back the same state... May anyone enligthen me a bit? Thanks in advance, regards! ... make[4]: Entering directory `/home/j/openwrt/attitudeAdjustment/build_dir/linux-ar71xx_generic/linux-3.3.8' HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig * * Restart config... * * * GCOV-based kernel profiling * Enable gcov-based kernel profiling (GCOV_KERNEL) [N/y/?] (NEW) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] mac80211: b43: fix B43_USE_SSB dependency
Signed-off-by: Rafał Miłecki zaj...@gmail.com --- package/kernel/mac80211/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index 19f8c3b..d316958 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -1085,7 +1085,7 @@ define KernelPackage/b43/config config PACKAGE_B43_USE_SSB select PACKAGE_kmod-ssb tristate - depends on !TARGET_brcm47xx + depends on !TARGET_brcm47xx !TARGET_brcm63xx default PACKAGE_kmod-b43 if PACKAGE_B43_BUSES_BCMA_AND_SSB default PACKAGE_kmod-b43 if PACKAGE_B43_BUSES_SSB -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] brcm47xx: mips74k: disable BCM47XX_SSB
Save 8 376 B of LZMA compressed kernel size. Signed-off-by: Rafał Miłecki zaj...@gmail.com --- target/linux/brcm47xx/mips74k/config-default | 1 + 1 file changed, 1 insertion(+) create mode 100644 target/linux/brcm47xx/mips74k/config-default diff --git a/target/linux/brcm47xx/mips74k/config-default b/target/linux/brcm47xx/mips74k/config-default new file mode 100644 index 000..702cf58 --- /dev/null +++ b/target/linux/brcm47xx/mips74k/config-default @@ -0,0 +1 @@ +# CONFIG_BCM47XX_SSB is not set -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [RFH][PATCH] brcm47xx: mips74k: drop CONFIG_SSB for kernel config
This allows using ssb.ko and saving some space (and memory if unused). --- I need some help with this patch. Unfortunately this results in: ERROR: pcibios_enable_device [drivers/ssb/ssb.ko] undefined! ERROR: register_pci_controller [drivers/ssb/ssb.ko] undefined! It seems to be caused because compiling driver_pcicore.c with hostmode support. For some reason CONFIG_SSB_PCICORE_HOSTMODE had to be enabled. grep 'SSB_' build_dir/target-*/linux-brcm47xx_mips74k/linux-*/.config | sort CONFIG_SSB_B43_PCI_BRIDGE=y CONFIG_SSB_BLOCKIO=y CONFIG_SSB_DRIVER_EXTIF=y CONFIG_SSB_DRIVER_GIGE=y CONFIG_SSB_DRIVER_GPIO=y CONFIG_SSB_DRIVER_MIPS=y CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y CONFIG_SSB_EMBEDDED=y CONFIG_SSB_PCICORE_HOSTMODE=y CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y CONFIG_SSB_POSSIBLE=y CONFIG_SSB_SERIAL=y CONFIG_SSB_SFLASH=y CONFIG_SSB_SILENT=y CONFIG_SSB_SPROM=y According to the KernelPackage/ssb this should not happen. It sets: SSB_DRIVER_MIPS=n As the result SSB_PCICORE_HOSTMODE was also selected. --- package/kernel/linux/modules/other.mk| 2 +- package/kernel/mac80211/Makefile | 2 +- target/linux/brcm47xx/mips74k/config-default | 1 + 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/package/kernel/linux/modules/other.mk b/package/kernel/linux/modules/other.mk index 8f68bd8..ffcd0a5 100644 --- a/package/kernel/linux/modules/other.mk +++ b/package/kernel/linux/modules/other.mk @@ -374,7 +374,7 @@ $(eval $(call KernelPackage,softdog)) define KernelPackage/ssb SUBMENU:=$(OTHER_MENU) TITLE:=Silicon Sonics Backplane glue code - DEPENDS:=@PCI_SUPPORT @!TARGET_brcm47xx @!TARGET_brcm63xx + DEPENDS:=@PCI_SUPPORT @!TARGET_brcm47xx_generic @!TARGET_brcm63xx KCONFIG:=\ CONFIG_SSB \ CONFIG_SSB_B43_PCI_BRIDGE=y \ diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index d316958..3b05c19 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -1085,7 +1085,7 @@ define KernelPackage/b43/config config PACKAGE_B43_USE_SSB select PACKAGE_kmod-ssb tristate - depends on !TARGET_brcm47xx !TARGET_brcm63xx + depends on !TARGET_brcm47xx_generic !TARGET_brcm63xx default PACKAGE_kmod-b43 if PACKAGE_B43_BUSES_BCMA_AND_SSB default PACKAGE_kmod-b43 if PACKAGE_B43_BUSES_SSB diff --git a/target/linux/brcm47xx/mips74k/config-default b/target/linux/brcm47xx/mips74k/config-default index 702cf58..f42fd04 100644 --- a/target/linux/brcm47xx/mips74k/config-default +++ b/target/linux/brcm47xx/mips74k/config-default @@ -1 +1,2 @@ # CONFIG_BCM47XX_SSB is not set +# CONFIG_SSB is not set -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [Patch][BCM63XX] Select HW_RANDOM_BCM63XX only in the SoCs that support it.
Select HW_RANDOM_BCM63XX only in the SoCs that support it. Only BCM6368, BCM6362 and BCM63268 have a hardware random numbers generator, so, if none of these are selected, don't compile a driver that has no effect. Tested with BCM6358 and BCM6328 successfully. Signed off by: José Vázquez Fernández ppvazquez...@gmail.com diff -urN a/drivers/char/hw_random/Kconfig b/drivers/char/hw_random/Kconfig --- a/drivers/char/hw_random/Kconfig 2014-06-06 12:21:38.677781666 +0200 +++ b/drivers/char/hw_random/Kconfig 2014-06-05 20:58:11.0 +0200 @@ -75,7 +75,7 @@ config HW_RANDOM_BCM63XX tristate Broadcom BCM63xx Random Number Generator support - depends on HW_RANDOM BCM63XX + depends on HW_RANDOM (BCM63XX_CPU_6362 || BCM63XX_CPU_6368 || BCM63XX_CPU_63268) default HW_RANDOM ---help--- This driver provides kernel-side support for the Random Number ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Patch][BCM63XX] Select HW_RANDOM_BCM63XX only in the SoCs that support it.
2014-06-06 12:46 GMT-07:00 José Vázquez Fernández ppvazquez...@gmail.com: Select HW_RANDOM_BCM63XX only in the SoCs that support it. Only BCM6368, BCM6362 and BCM63268 have a hardware random numbers generator, so, if none of these are selected, don't compile a driver that has no effect. Tested with BCM6358 and BCM6328 successfully. How about a Kconfig symbol such as BCM63XX_HAS_HWRANDOM that gets selected by only the SoCs that support it? Hopefully in the future, this list should grow rather than shrink. Signed off by: José Vázquez Fernández ppvazquez...@gmail.com ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Patch][BCM63XX] Select HW_RANDOM_BCM63XX only in the SoCs that support it.
On Fri, Jun 6, 2014 at 9:52 PM, Florian Fainelli flor...@openwrt.org wrote: 2014-06-06 12:46 GMT-07:00 José Vázquez Fernández ppvazquez...@gmail.com: Select HW_RANDOM_BCM63XX only in the SoCs that support it. Only BCM6368, BCM6362 and BCM63268 have a hardware random numbers generator, so, if none of these are selected, don't compile a driver that has no effect. Tested with BCM6358 and BCM6328 successfully. How about a Kconfig symbol such as BCM63XX_HAS_HWRANDOM that gets selected by only the SoCs that support it? Hopefully in the future, this list should grow rather than shrink. I think if you do the effort of disabling specific SoC support, then it isn't too much asked to also manually de-select the rng driver. Also I think that we should go the other way and allow compilation of it for !BCM63XX if COMPILE_TEST is enabled, to allow better build test coverage. And finally, these kind of patches should go to linux-mips. Regards Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFH][PATCH] brcm47xx: mips74k: drop CONFIG_SSB for kernel config
On 06/06/2014 09:25 PM, Rafał Miłecki wrote: This allows using ssb.ko and saving some space (and memory if unused). --- I need some help with this patch. Unfortunately this results in: ERROR: pcibios_enable_device [drivers/ssb/ssb.ko] undefined! ERROR: register_pci_controller [drivers/ssb/ssb.ko] undefined! It seems to be caused because compiling driver_pcicore.c with hostmode support. For some reason CONFIG_SSB_PCICORE_HOSTMODE had to be enabled. grep 'SSB_' build_dir/target-*/linux-brcm47xx_mips74k/linux-*/.config | sort CONFIG_SSB_B43_PCI_BRIDGE=y CONFIG_SSB_BLOCKIO=y CONFIG_SSB_DRIVER_EXTIF=y CONFIG_SSB_DRIVER_GIGE=y CONFIG_SSB_DRIVER_GPIO=y CONFIG_SSB_DRIVER_MIPS=y CONFIG_SSB_DRIVER_PCICORE_POSSIBLE=y CONFIG_SSB_DRIVER_PCICORE=y CONFIG_SSB_EMBEDDED=y CONFIG_SSB_PCICORE_HOSTMODE=y CONFIG_SSB_PCIHOST_POSSIBLE=y CONFIG_SSB_PCIHOST=y CONFIG_SSB_POSSIBLE=y CONFIG_SSB_SERIAL=y CONFIG_SSB_SFLASH=y CONFIG_SSB_SILENT=y CONFIG_SSB_SPROM=y According to the KernelPackage/ssb this should not happen. It sets: SSB_DRIVER_MIPS=n As the result SSB_PCICORE_HOSTMODE was also selected. --- package/kernel/linux/modules/other.mk| 2 +- package/kernel/mac80211/Makefile | 2 +- target/linux/brcm47xx/mips74k/config-default | 1 + 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/package/kernel/linux/modules/other.mk b/package/kernel/linux/modules/other.mk index 8f68bd8..ffcd0a5 100644 --- a/package/kernel/linux/modules/other.mk +++ b/package/kernel/linux/modules/other.mk @@ -374,7 +374,7 @@ $(eval $(call KernelPackage,softdog)) define KernelPackage/ssb SUBMENU:=$(OTHER_MENU) TITLE:=Silicon Sonics Backplane glue code - DEPENDS:=@PCI_SUPPORT @!TARGET_brcm47xx @!TARGET_brcm63xx + DEPENDS:=@PCI_SUPPORT @!TARGET_brcm47xx_generic @!TARGET_brcm63xx KCONFIG:=\ CONFIG_SSB \ CONFIG_SSB_B43_PCI_BRIDGE=y \ diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index d316958..3b05c19 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -1085,7 +1085,7 @@ define KernelPackage/b43/config config PACKAGE_B43_USE_SSB select PACKAGE_kmod-ssb tristate - depends on !TARGET_brcm47xx !TARGET_brcm63xx + depends on !TARGET_brcm47xx_generic !TARGET_brcm63xx default PACKAGE_kmod-b43 if PACKAGE_B43_BUSES_BCMA_AND_SSB default PACKAGE_kmod-b43 if PACKAGE_B43_BUSES_SSB diff --git a/target/linux/brcm47xx/mips74k/config-default b/target/linux/brcm47xx/mips74k/config-default index 702cf58..f42fd04 100644 --- a/target/linux/brcm47xx/mips74k/config-default +++ b/target/linux/brcm47xx/mips74k/config-default @@ -1 +1,2 @@ # CONFIG_BCM47XX_SSB is not set +# CONFIG_SSB is not set Please try to add # CONFIG_SSB_PCICORE_HOSTMODE not set Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [Patch][BCM63XX] Select HW_RANDOM_BCM63XX only in the SoCs that support it.
2014-06-06 22:00 GMT+02:00, Jonas Gorski j...@openwrt.org: On Fri, Jun 6, 2014 at 9:52 PM, Florian Fainelli flor...@openwrt.org wrote: 2014-06-06 12:46 GMT-07:00 José Vázquez Fernández ppvazquez...@gmail.com: Select HW_RANDOM_BCM63XX only in the SoCs that support it. Only BCM6368, BCM6362 and BCM63268 have a hardware random numbers generator, so, if none of these are selected, don't compile a driver that has no effect. Tested with BCM6358 and BCM6328 successfully. How about a Kconfig symbol such as BCM63XX_HAS_HWRANDOM that gets selected by only the SoCs that support it? Hopefully in the future, this list should grow rather than shrink. I think if you do the effort of disabling specific SoC support, then it isn't too much asked to also manually de-select the rng driver. If you deselect HW_RANDOM, when compiling the kernel sends an error, which is the reason of the patch. Also I think that we should go the other way and allow compilation of it for !BCM63XX if COMPILE_TEST is enabled, to allow better build test coverage. Do you mean something like this? http://lists.linaro.org/pipermail/linaro-kernel/2013-July/005078.html And finally, these kind of patches should go to linux-mips. Regards Jonas Are you sure about linux-mips? It scares me a bit. Would not be better publish a patch here and Florian, Kevin Cernekee or you send it with the adequate and professional description? Regards: Pepe ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] procd: Fix USB cellular modems
Without this patch, /etc/hotplug.d/tty/30-3g won't be called when you insert or remove a USB-serial cellular modem. (see Ticket #14117) Signed-off-by: Matthew Reeve mre...@tenxnetworks.com --- package/system/procd/files/hotplug.json 2014-05-27 22:34:33.175634831 + +++ package/system/procd/files/hotplug.json 2014-06-06 20:47:13.736795246 + @@ -13,7 +13,7 @@ [ null, full, ptmx, zero ], ], [ regex, DEVNAME, - [ ^gpio, ^hvc, ^tty ], + [ ^gpio, ^hvc ], ], ], [ @@ -76,10 +76,10 @@ ], [ if, [ and, - [ eq, SUBSYSTEM, - [ tty, usb-serial ] - ], - [ regex, DEVNAME, ^ttyUSB ], + [ eq, SUBSYSTEM, usb-serial ], + [ regex, DEVNAME, + [ ^ttyUSB, ^ttyACM ] + ], ], [ exec, /sbin/hotplug-call, tty ] ], ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH V2] brcm47xx: mips74k: optimize kernel config
This saves abount 15 kB of compressed kernel size. Signed-off-by: Rafał Miłecki zaj...@gmail.com --- This patch replaces brcm47xx: mips74k: disable BCM47XX_SSB --- target/linux/brcm47xx/mips74k/config-default | 10 ++ 1 file changed, 10 insertions(+) create mode 100644 target/linux/brcm47xx/mips74k/config-default diff --git a/target/linux/brcm47xx/mips74k/config-default b/target/linux/brcm47xx/mips74k/config-default new file mode 100644 index 000..a29b477 --- /dev/null +++ b/target/linux/brcm47xx/mips74k/config-default @@ -0,0 +1,10 @@ +# CONFIG_ADM6996_PHY is not set +# CONFIG_BCM47XX_SSB is not set +# CONFIG_FIXED_PHY is not set +# CONFIG_SSB_DRIVER_EXTIF is not set +# CONFIG_SSB_DRIVER_GIGE is not set +# CONFIG_SSB_DRIVER_MIPS is not set +# CONFIG_SSB_EMBEDDED is not set +# CONFIG_SSB_PCICORE_HOSTMODE is not set +# CONFIG_SSB_SERIAL is not set +# CONFIG_SSB_SFLASH is not set -- 1.8.4.5 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] mempool support question for building software
I'm trying to build a new version of clamav for the brcm2708 platform and have some questions about the new build dependencies for the latest version of clamav 98.3. 98.1 built OK and didn't use openssl. The configure portion of the build is asking about mempool support. output snip checking for sysctlbyname... no configure: ** mempool support disabled (mmap not available or not usable) .. mempool.h is found in the -I$(BUILD_DIR)/linux-3.10.36/mm directory. I've included the directory path in the Target_cpplfags, like below. Is this the right way to do this? As the make file will obviously be out of date soon as a new kernel version is used. TARGET_CPPFLAGS += \ -I$(STAGING_DIR)/usr/include \ -I$(STAGING_DIR)/usr/include/openssl \ -I$(STAGING_DIR)/usr/include/crypto \ -I$(STAGING_DIR)/usr/include/libxml2 \ -I$(STAGING_DIR)/usr/lib \ -I$(TOOLCHAIN_DIR)/include \ -I$(BUILD_DIR)/linux-3.10.36/mm \ Thanks for the advice in advance. Cheers Derek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] mempool support question for building software
2014-06-06 15:35 GMT-07:00 Derek Werthmuller thewerth...@gmail.com: I'm trying to build a new version of clamav for the brcm2708 platform and have some questions about the new build dependencies for the latest version of clamav 98.3. 98.1 built OK and didn't use openssl. The configure portion of the build is asking about mempool support. output snip checking for sysctlbyname... no configure: ** mempool support disabled (mmap not available or not usable) .. mempool.h is found in the -I$(BUILD_DIR)/linux-3.10.36/mm directory. I've included the directory path in the Target_cpplfags, like below. Is this the right way to do this? This is not the right way to do this, you should not include Linux kernel headers directly that have not been voluntarily exported. The kernel exports some header files for use by user-programs from its include/uapi/ directory. Those kernel headers are staged by the toolchain build process in staging_dir/toolchain-*/usr/include/linux. mempool.h does not appear to be in the headers exported for uapi, so I am not sure this is referring to the same mempool.h header file, it could be either some external library, or some internal header that does not get properly included. As the make file will obviously be out of date soon as a new kernel version is used. TARGET_CPPFLAGS += \ -I$(STAGING_DIR)/usr/include \ -I$(STAGING_DIR)/usr/include/openssl \ -I$(STAGING_DIR)/usr/include/crypto \ -I$(STAGING_DIR)/usr/include/libxml2 \ -I$(STAGING_DIR)/usr/lib \ -I$(TOOLCHAIN_DIR)/include \ -I$(BUILD_DIR)/linux-3.10.36/mm \ Thanks for the advice in advance. Cheers Derek ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] How to use PAM with Busybox Login tools.
I’ve been going the rounds of how to enable PAM for the busy box login tools. At first glance it seems it is supported in the ‘menuconfig’ set of options. However, upon performing the ‘make’ operation, the build fails as ‘libpam’ is not in the LDLIBS list, nor is it any path that the Makefile for Busybox uses to look for libraries. There are some trouble reports, all of which are closed, none of which seem to reflect the current ‘menuconfig’ options. So, the question is, does anyone use PAM with OpenWRT. Alternatively, how does one require the ‘built in’ Busybox crypto functions to use SHA512 for password hashing, rather than the simplistic MD5 that seems to be the default. John Clark. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
