[OpenWrt-Devel] [PATCH] ca-certificates: update to version 20150426
update to version 20150426 Signed-off-by: Christian Schoenebeck --- package/system/ca-certificates/Makefile | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/package/system/ca-certificates/Makefile b/package/system/ca-certificates/Makefile index 0bf3f25..9c50fef 100644 --- a/package/system/ca-certificates/Makefile +++ b/package/system/ca-certificates/Makefile @@ -1,5 +1,5 @@ -# -# Copyright (C) 2006 OpenWrt.org +# +# Copyright (C) 2006-2015 OpenWrt.org # # This is free software, licensed under the GNU General Public License v2. # See /LICENSE for more information. @@ -7,11 +7,11 @@ include $(TOPDIR)/rules.mk PKG_NAME:=ca-certificates -PKG_VERSION:=20141019 +PKG_VERSION:=20150426 PKG_SOURCE:=$(PKG_NAME)_$(PKG_VERSION).tar.xz PKG_SOURCE_URL:=http://ftp.debian.org/debian/pool/main/c/ca-certificates -PKG_MD5SUM:=f619282081c8bfc65ea64c37fa5285ed +PKG_MD5SUM:=717455f13fb31fd014a11a468ea3895d PKG_INSTALL:=1 -- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] ipq806x: move stmmac support in the kernel binary
Ethernet GMAC is built-in the SoC, so there is no need to enable it as a module. We'll just assume we need it. That's what is done for other platform where this driver is used so it'll make things more consistent. Signed-off-by: Mathieu Olivari --- target/linux/ipq806x/Makefile| 2 +- target/linux/ipq806x/config-3.18 | 10 -- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/target/linux/ipq806x/Makefile b/target/linux/ipq806x/Makefile index da841a6..b6ddfe2 100644 --- a/target/linux/ipq806x/Makefile +++ b/target/linux/ipq806x/Makefile @@ -15,7 +15,7 @@ KERNELNAME:=zImage Image dtbs include $(INCLUDE_DIR)/target.mk DEFAULT_PACKAGES += \ - kmod-leds-gpio kmod-gpio-button-hotplug kmod-stmmac swconfig \ + kmod-leds-gpio kmod-gpio-button-hotplug swconfig \ kmod-ata-core kmod-ata-ahci kmod-ata-ahci-platform diff --git a/target/linux/ipq806x/config-3.18 b/target/linux/ipq806x/config-3.18 index 396c6e3..4d3b884 100644 --- a/target/linux/ipq806x/config-3.18 +++ b/target/linux/ipq806x/config-3.18 @@ -121,6 +121,7 @@ CONFIG_DMA_ENGINE=y CONFIG_DMA_OF=y CONFIG_DMA_VIRTUAL_CHANNELS=y CONFIG_DTC=y +CONFIG_DWMAC_IPQ806X=y # CONFIG_DW_DMAC_CORE is not set # CONFIG_DW_DMAC_PCI is not set CONFIG_DYNAMIC_DEBUG=y @@ -212,7 +213,6 @@ CONFIG_I2C_CHARDEV=y CONFIG_I2C_COMPAT=y CONFIG_I2C_HELPER_AUTO=y CONFIG_I2C_QUP=y -# CONFIG_IEEE802154 is not set CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y CONFIG_INITRAMFS_SOURCE="" @@ -243,7 +243,6 @@ CONFIG_MFD_SYSCON=y CONFIG_MIGHT_HAVE_CACHE_L2X0=y CONFIG_MIGHT_HAVE_PCI=y CONFIG_MIGRATION=y -# CONFIG_MMC_SDHCI_MSM is not set CONFIG_MODULES_USE_ELF_REL=y CONFIG_MSM_GCC_8660=y CONFIG_MSM_GCC_8960=y @@ -261,6 +260,7 @@ CONFIG_MUTEX_SPIN_ON_OWNER=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEON=y CONFIG_NET_FLOW_LIMIT=y +CONFIG_NET_PTP_CLASSIFY=y CONFIG_NET_VENDOR_WIZNET=y CONFIG_NO_BOOTMEM=y CONFIG_NO_HZ=y @@ -319,12 +319,14 @@ CONFIG_POWER_RESET=y CONFIG_POWER_RESET_MSM=y # CONFIG_POWER_RESET_SYSCON is not set CONFIG_POWER_SUPPLY=y +CONFIG_PPS=y CONFIG_PREEMPT=y CONFIG_PREEMPT_COUNT=y # CONFIG_PREEMPT_NONE is not set CONFIG_PREEMPT_RCU=y CONFIG_PRINTK_TIME=y CONFIG_PROC_PAGE_MONITOR=y +CONFIG_PTP_1588_CLOCK=y CONFIG_QCOM_BAM_DMA=y CONFIG_QCOM_GSBI=y CONFIG_QCOM_HFPLL=y @@ -366,6 +368,10 @@ CONFIG_SPI_MASTER=y CONFIG_SPI_QUP=y CONFIG_SPMI=y CONFIG_SPMI_MSM_PMIC_ARB=y +# CONFIG_STMMAC_DA is not set +CONFIG_STMMAC_DEBUG_FS=y +CONFIG_STMMAC_ETH=y +CONFIG_STMMAC_PLATFORM=y CONFIG_STOP_MACHINE=y # CONFIG_STRIP_ASM_SYMS is not set CONFIG_SUSPEND=y -- 2.1.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/2] kernel: remove stmmac kernel package
We just moved the stmmac support in the kernel for ipq806x. Therefore, nobody needs this driver so we'll just get rid of it. Signed-off-by: Mathieu Olivari --- package/kernel/linux/modules/netdevices.mk | 21 - 1 file changed, 21 deletions(-) diff --git a/package/kernel/linux/modules/netdevices.mk b/package/kernel/linux/modules/netdevices.mk index 62fd949..9dd18f3 100644 --- a/package/kernel/linux/modules/netdevices.mk +++ b/package/kernel/linux/modules/netdevices.mk @@ -811,27 +811,6 @@ endef $(eval $(call KernelPackage,vmxnet3)) -define KernelPackage/stmmac - SUBMENU:=$(NETWORK_DEVICES_MENU) - TITLE:=STMicro 10/100/1000 Ethernet driver - DEPENDS:=+kmod-mii +kmod-ptp - KCONFIG:=CONFIG_NET_VENDOR_STMICRO=y \ - CONFIG_STMMAC_ETH \ - CONFIG_STMMAC_PLATFORM=y \ - CONFIG_STMMAC_DEBUG_FS=y \ - CONFIG_STMMAC_DA=y \ - CONFIG_DWMAC_IPQ806X=y - FILES:=$(LINUX_DIR)/drivers/net/ethernet/stmicro/stmmac/stmmac.ko - AUTOLOAD:=$(call AutoLoad,50,stmmac.ko) -endef - -define KernelPackage/stmmac/description - Kernel module for STMicroelectronics 10/100/1000 Ethernet driver -endef - -$(eval $(call KernelPackage,stmmac)) - - define KernelPackage/spi-ks8995 SUBMENU:=$(NETWORK_DEVICES_MENU) TITLE:=Micrel/Kendin KS8995 Ethernet switch control -- 2.1.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Suggestions anyone - EasyBox 904 xDSL (Lantiq xrx200)
On Sat, May 30, 2015 at 1:58 AM, Arnold Schulz wrote: > I don't know. According to console output PCI seems to be recognized, for > PCIe there are error messages ("pcie_rc_initialize link up failed!"). > The lspci command shows nothing. Can you see the physical wifi chip on your board? If you google the part number then you'll probably know whether it's PCI or PCIe. Looking at this config (I'm hoping that this is the correct device) suggests that it's a PCIe is at least enabled: [0] Please note that OpenWrt svn r45717 and r45718 contain bugfixes for PCIe! > This leads to the assumption, that USB is connected via PCI. But lspci shows > nothing, while USB seems to work. lsusb shows two busses and I could mount a > vfat USB stick. Sorry, I have no idea how USB is connected internally. > Here I had made many tests and I think I tried all or allmost all > combinations of >reg = ; // X = 0, *1, *2, 3, 4, 5 used in > other profiles >phy-handle = <&phyY>; // Y = *0, 1, 5, *11, 12, *13, 14 *=most use > in other profiles > > Console msgs told about successfull attachment only for values &phy11 or > &phy13, > but then networking via ethernet did not work any longer. I had the same behavior when I mixed up the assignment of a phy to the ethernet-port or when I used an incorrect "reg" config at the ethernet-port. > BTW: Which phy-mode (gmii, rgmii or even mii) to use in 'phy-mode = "..."' > lines? > Is this also a variable I should play with? Yes, have a look at the network driver: [1] If you have gbit ethernet then you should probably use gmii or rgmii (depending on the port -> see the source-code). As a general note: You can find most pinmux/GPIO settings in the original source code: [2] Sometimes you need to do some basic calulations (for example interrupts are +8 in the OpenWrt kernel). I also suggest to get a copy of Draytek's vigor 2760 GPL sources [3] as they are shipping the most complete kernel source that I have seen so far. Using both sources together with the original kernel config helps you finding the correct values. Regards, Martin [0] https://github.com/uwehermann/easybox-904-xdsl-firmware/blob/master/target/linux/ltqcpe/platform_vr9/config-2.6.32#L134 [1] https://github.com/openwrt-mirror/openwrt/blob/master/target/linux/lantiq/patches-3.18/0025-NET-MIPS-lantiq-adds-xrx200-net.patch#L1532 [2] https://github.com/uwehermann/easybox-904-xdsl-firmware/tree/master/projects/904dsl/linux/linux-2.6.32.32/arch/mips [3] http://gplsource.draytek.com/Vigor2760/v2760_v1212_GPL_release.tar.bz2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Suggestions anyone - EasyBox 904 xDSL (Lantiq xrx200)
Hi Martin, On Fri, May 29, 2015 at 5:50 PM, Arnold Schulz wrote: My current questions center on the .dts settings: 1. How to access WLAN hardware Do you know if wifi is connected via PCI or PCIe? You then need to configure the corresponding pins in the pinmux section. Of course you also need to set up the bus in the dts. I don't know. According to console output PCI seems to be recognized, for PCIe there are error messages ("pcie_rc_initialize link up failed!"). The lspci command shows nothing. Console output from a dts trial is here: http://arny.tjps.eu/OpenWrt/EasyBox904xDSL/devel/v0.1-console.log which corresponds to my dts file in http://arny.tjps.eu/OpenWrt/EasyBox904xDSL/devel/v0.1-EasyBox904xDSL.patch BTW, console output from orig. firmware is here: http://arny.tjps.eu/OpenWrt/EasyBox904xDSL/oem-firmware-info/ (concatenate bootlog-part1-console.txt and bootlog-part2-netlog.txt) There I find only the following PCI or PCIe related messages: [0.346000] === ifx_gpio_register (10,PCI) === kernel init [0.354000] === ifx_gpio_register (11,PCIE) === kernel init [ 121.742000] setUsbPciInfo() cpu_to_usb_addr_shift[5]:0x, usb_to_cpu_addr_shift[5]:0x [ 121.751000] usb_pci_probe() Found Synopsis OTG-1, baseAddr:0xbe101000, IRQ:54 [ 121.758000] setUsbPciInfo() cpu_to_usb_addr_shift[6]:0x, usb_to_cpu_addr_shift[6]:0x [ 121.767000] usb_pci_probe() Found Synopsis OTG-2, baseAddr:0xbe106000, IRQ:48 [ 121.774000] usb_hcd_init() probe PCI function:2 !! This leads to the assumption, that USB is connected via PCI. But lspci shows nothing, while USB seems to work. lsusb shows two busses and I could mount a vfat USB stick. I played around with pinmux settings, inspired by looking at other dtsi and dts files, but could not recognize any effects. If you suggest changes of the dts file, I will try them and report the results. 2. Recommended settings for this phy-thingy There are no "recommended" settings. Let's start at the top: vr9_phy11g_a2x.bin -> used if you have 1gbit ports, otherwise you need to load vr9_phy22f_a2x.bin. I understand. The EasyBox 904 xDSL has 1Gb Ethernet, so vr9_phy11g_a2x.bin is the right one. Have you already figured out which phys are connected (your dts states that you get a reply on 0x11 and 0x13 (those are *probably* LAN 3 and 4). There should be two more, possible addresses are: 0x0, 0x1, 0x5 and 0x14. Here I had made many tests and I think I tried all or allmost all combinations of reg = ; // X = 0, *1, *2, 3, 4, 5 used in other profiles phy-handle = <&phyY>; // Y = *0, 1, 5, *11, 12, *13, 14 *=most use in other profiles Console msgs told about successfull attachment only for values &phy11 or &phy13, but then networking via ethernet did not work any longer. BTW: Which phy-mode (gmii, rgmii or even mii) to use in 'phy-mode = "..."' lines? Is this also a variable I should play with? If the LEDs are directly connected (the other option is they are connected via STP) then it's pretty easy to find their GPIOs by taking the script from [0] and modifying it a bit. Same for the buttons, only that you configure the GPIOs in "in" (input) mode and read the value instead of writing it. [0] http://wiki.openwrt.org/doc/hardware/port.gpio I keep these good hints in mind for later. Cheers, Arnold ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] How to track IO usage of internal flash mtd partitions?
Awesome news Sergey, will this patch be applied to latest trunk anytime soon so that I can test it? Can you just briefly explain how will it be possible to track erase block count once this patch is applied? Regards, Valent. On 20 May 2015 at 08:38, Sergey Zakharchenko wrote: > Hello Valent, > > 2015-05-19 15:52 GMT+03:00 you wrote: >> Is there maybe something that I have missed or there is no tool for >> reading IO usage of mtd partitions? > > Without kernel support for this, it's not possible. However, yo're > (possibly) in luck, as we use the following patch in new DLI power > controllers to do what you probably want to do: > > http://sources.digital-loggers.com/patches/openwrt-aa-r42647/mtd_erasecount.patch > > It's supposed to work with OpenWrt AA (kernel 3.3). It's distributed > together with the firmware sources, so consider it's under GPL. > > Keep in mind that few care about the write count, it's usually the > erase count that matters. > > Best regards, > > -- > DoubleF ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 3/6] kernel: add stmmac as a new kernel package
Yeah; that's what I was thinking actually. I'll post a patch today. -Original Message- From: Felix Fietkau [mailto:n...@openwrt.org] Sent: Friday, May 29, 2015 1:35 PM To: Mathieu Olivari; blo...@openwrt.org; ka...@openwrt.org Cc: openwrt-devel@lists.openwrt.org Subject: Re: [PATCH 3/6] kernel: add stmmac as a new kernel package On 2015-05-26 23:27, Mathieu Olivari wrote: > Signed-off-by: Mathieu Olivari How about simply enabling stmmac in the target kernel config? - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 3/6] kernel: add stmmac as a new kernel package
On 2015-05-26 23:27, Mathieu Olivari wrote: > Signed-off-by: Mathieu Olivari How about simply enabling stmmac in the target kernel config? - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] zram-swap: set a high priority for the swap
Sorry, this is the good one. I sent the wrong patch in my previous email. 2015-05-29 22:00 GMT+02:00 Juan Orti Alcaine : > The zram swap must be activated with a higher priority than > disk-based swap, so it is used before any other. > This patch activates the zram-based swap with a priority of 100. > > --- > v2: > Fallback to no priority when swapon doesn't support it. > > Signed-off-by: Juan Orti Alcaine > --- > package/system/zram-swap/files/zram.init | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/package/system/zram-swap/files/zram.init > b/package/system/zram-swap/files/zram.init > index 23de915..44f75dd 100644 > --- a/package/system/zram-swap/files/zram.init > +++ b/package/system/zram-swap/files/zram.init > @@ -100,7 +100,7 @@ start() > zram_reset "$zram_dev" "enforcing defaults" > echo $(( $zram_size * 1024 * 1024 )) >"/sys/block/$( basename > $zram_dev )/disksize" > mkswap "$zram_dev" > - swapon "$zram_dev" > + swapon -p 100 "$zram_dev" || swapon "$zram_dev" > } done > } > > -- > 2.4.1 > -- Juan Orti https://miceliux.com GPG key: https://miceliux.com/pub/pubkey.asc GPG fingerprint: 61F0 8272 6882 BCA6 3A35 88F6 B630 4B72 DEEB D08B ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] zram-swap: set a high priority for the swap
The zram swap must be activated with a higher priority than disk-based swap, so it is used before any other. This patch activates the zram-based swap with a priority of 100. --- v2: Fallback to no priority when swapon doesn't support it. Signed-off-by: Juan Orti Alcaine --- package/system/zram-swap/files/zram.init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/system/zram-swap/files/zram.init b/package/system/zram-swap/files/zram.init index 23de915..44f75dd 100644 --- a/package/system/zram-swap/files/zram.init +++ b/package/system/zram-swap/files/zram.init @@ -100,7 +100,7 @@ start() zram_reset "$zram_dev" "enforcing defaults" echo $(( $zram_size * 1024 * 1024 )) >"/sys/block/$( basename $zram_dev )/disksize" mkswap "$zram_dev" - swapon "$zram_dev" + swapon -p 100 "$zram_dev" || swapon "$zram_dev" } done } -- 2.4.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v2] zram-swap: set a high priority for the swap
The zram swap must be activated with a higher priority than disk-based swap, so it is used before any other. This patch activates the zram-based swap with a priority of 100. --- v2: Fallback to no priority when swapon doesn't support it. Signed-off-by: Juan Orti Alcaine --- package/system/zram-swap/files/zram.init | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/system/zram-swap/files/zram.init b/package/system/zram-swap/files/zram.init index 23de915..b26ee0d 100644 --- a/package/system/zram-swap/files/zram.init +++ b/package/system/zram-swap/files/zram.init @@ -100,7 +100,7 @@ start() zram_reset "$zram_dev" "enforcing defaults" echo $(( $zram_size * 1024 * 1024 )) >"/sys/block/$( basename $zram_dev )/disksize" mkswap "$zram_dev" - swapon "$zram_dev" + swapon -p 100 "$zram_dev" } done } -- 2.4.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v4] [kernel] upstream fix: mount overlayfs r/o if workdir cannot be created
On 29/05/2015 18:43, Christian Mehlis wrote: > Am 29.05.2015 um 15:38 schrieb Thomas Huehn: >> This is the case e.g. if JFFS2 partition is full. >> >> see: >> https://www.mail-archive.com/linux-unionfs@vger.kernel.org/msg00246.html >> (a small error in a logmessage was changed and reported upstream) >> >> runtime tested on ar71xx with kernel 3.18.11 and r45772 >> this paritially fixes #19564 > > this patch is superfluous because it's already merged... > > http://git.openwrt.org/?p=openwrt.git;a=commitdiff;h=f521e44327cab409ba0e4557ba491ef8243cb23e > > unfortunatley in the wrong folder and not for 4.0 i am working on the fix just now > Best > Christian > ___ > 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] [PATCH 3/6] kernel: add stmmac as a new kernel package
Please note that the sunxi and oxnas targets already use stmmac. However, in your patch the selected config symbols do not apply to stmmac in general but are specific to the hardware you are using. Please either make the module depend on the target platforms it is meant to be used on or fix it so it actually covers the generic case. On Tue, May 26, 2015 at 02:27:54PM -0700, Mathieu Olivari wrote: > Signed-off-by: Mathieu Olivari > --- > package/kernel/linux/modules/netdevices.mk | 21 + > 1 file changed, 21 insertions(+) > > diff --git a/package/kernel/linux/modules/netdevices.mk > b/package/kernel/linux/modules/netdevices.mk > index 9dd18f3..62fd949 100644 > --- a/package/kernel/linux/modules/netdevices.mk > +++ b/package/kernel/linux/modules/netdevices.mk > @@ -811,6 +811,27 @@ endef > $(eval $(call KernelPackage,vmxnet3)) > > > +define KernelPackage/stmmac > + SUBMENU:=$(NETWORK_DEVICES_MENU) > + TITLE:=STMicro 10/100/1000 Ethernet driver > + DEPENDS:=+kmod-mii +kmod-ptp > + KCONFIG:=CONFIG_NET_VENDOR_STMICRO=y \ > + CONFIG_STMMAC_ETH \ > + CONFIG_STMMAC_PLATFORM=y \ > + CONFIG_STMMAC_DEBUG_FS=y \ > + CONFIG_STMMAC_DA=y \ > + CONFIG_DWMAC_IPQ806X=y > + FILES:=$(LINUX_DIR)/drivers/net/ethernet/stmicro/stmmac/stmmac.ko > + AUTOLOAD:=$(call AutoLoad,50,stmmac.ko) > +endef > + > +define KernelPackage/stmmac/description > + Kernel module for STMicroelectronics 10/100/1000 Ethernet driver > +endef > + > +$(eval $(call KernelPackage,stmmac)) > + > + > define KernelPackage/spi-ks8995 >SUBMENU:=$(NETWORK_DEVICES_MENU) >TITLE:=Micrel/Kendin KS8995 Ethernet switch control > -- > 2.1.4 > ___ > 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] Suggestions anyone - EasyBox 904 xDSL (Lantiq xrx200)
Hi Arnold, On Fri, May 29, 2015 at 5:50 PM, Arnold Schulz wrote: > My current questions center on the .dts settings: > 1. How to access WLAN hardware Do you know if wifi is connected via PCI or PCIe? You then need to configure the corresponding pins in the pinmux section. Of course you also need to set up the bus in the dts. > 2. Recommended settings for this phy-thingy There are no "recommended" settings. Let's start at the top: vr9_phy11g_a2x.bin -> used if you have 1gbit ports, otherwise you need to load vr9_phy22f_a2x.bin. Have you already figured out which phys are connected (your dts states that you get a reply on 0x11 and 0x13 (those are *probably* LAN 3 and 4). There should be two more, possible addresses are: 0x0, 0x1, 0x5 and 0x14. If the LEDs are directly connected (the other option is they are connected via STP) then it's pretty easy to find their GPIOs by taking the script from [0] and modifying it a bit. Same for the buttons, only that you configure the GPIOs in "in" (input) mode and read the value instead of writing it. Regards, Martin [0] http://wiki.openwrt.org/doc/hardware/port.gpio ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v4] [kernel] upstream fix: mount overlayfs r/o if workdir cannot be created
* Christian Mehlis [29.05.2015 19:00]: > this patch is superfluous because it's already merged... Thomas is right, i send it only for ar71xx, but it should be in the generic 3.18-patchfolder. I'am already compiling some other platforms and test it. if ok, i will send v5 which will revert the old and place the patch in generic... bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v4] [kernel] upstream fix: mount overlayfs r/o if workdir cannot be created
Am 29.05.2015 um 15:38 schrieb Thomas Huehn: This is the case e.g. if JFFS2 partition is full. see: https://www.mail-archive.com/linux-unionfs@vger.kernel.org/msg00246.html (a small error in a logmessage was changed and reported upstream) runtime tested on ar71xx with kernel 3.18.11 and r45772 this paritially fixes #19564 this patch is superfluous because it's already merged... http://git.openwrt.org/?p=openwrt.git;a=commitdiff;h=f521e44327cab409ba0e4557ba491ef8243cb23e Best Christian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Suggestions anyone - EasyBox 904 xDSL (Lantiq xrx200)
I am trying to port OpenWrt to the EasyBox 904xDSL. As I got the impression that OpenWrt developers rely mainly on this mailing list, I humbly dare to point to this location, where there are more infos and links to details like a patch for OpenWrt trunk: https://forum.openwrt.org/viewtopic.php?id=57649 My current questions center on the .dts settings: 1. How to access WLAN hardware 2. Recommended settings for this phy-thingy Thanks in advance for feedback, Arnold ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] kernel: bluetooth: Add dependency to kmod-crypto-ecb
Add dependency of kmod-crypto-ecb to kmod-bluetooth to avoid the kernel warning "Bluetooth: Unable to create crypto context". Signed-off-by: Bruno Randolf --- package/kernel/linux/modules/other.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/kernel/linux/modules/other.mk b/package/kernel/linux/modules/other.mk index 082c74a..955c140 100644 --- a/package/kernel/linux/modules/other.mk +++ b/package/kernel/linux/modules/other.mk @@ -28,7 +28,7 @@ $(eval $(call KernelPackage,6lowpan)) define KernelPackage/bluetooth SUBMENU:=$(OTHER_MENU) TITLE:=Bluetooth support - DEPENDS:=@USB_SUPPORT +kmod-usb-core +kmod-crypto-hash +kmod-lib-crc16 +kmod-hid + DEPENDS:=@USB_SUPPORT +kmod-usb-core +kmod-crypto-hash +kmod-crypto-ecb +kmod-lib-crc16 +kmod-hid KCONFIG:= \ CONFIG_BLUEZ \ CONFIG_BLUEZ_L2CAP \ -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v4] [kernel] upstream fix: mount overlayfs r/o if workdir cannot be created
On 29 May 2015 at 15:38, Thomas Huehn wrote: > +Index: linux-3.18.14/fs/overlayfs/copy_up.c > +=== > +--- linux-3.18.14.orig/fs/overlayfs/copy_up.c 2015-05-20 17:04:50.0 > +0200 > linux-3.18.14/fs/overlayfs/copy_up.c 2015-05-29 13:58:51.281147554 > +0200 > +@@ -300,6 +300,9 @@ Your patch seems to be wrongly formatted, please see http://wiki.openwrt.org/doc/devel/patches (and setup your ~/.quiltrc) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH/RFC] bluez: Add bluez-daemon package
Move bluetoothd and related programs and files from bluez-utils into bluez-daemon package. The main motivation for this is to remove the dependency to DBus from bluez-utils. The utilities like "hcitool" are useful without it. Also add kmod-bluetooth dependency to bluez-utils, as the utils don't make much sense without bluetooth support in the kernel. Signed-off-by: Bruno Randolf --- Please let me know, if this is OK, I'll send a pull request --- utils/bluez/Makefile | 39 +-- 1 file changed, 33 insertions(+), 6 deletions(-) diff --git a/utils/bluez/Makefile b/utils/bluez/Makefile index 4865698..ebc1646 100644 --- a/utils/bluez/Makefile +++ b/utils/bluez/Makefile @@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=bluez PKG_VERSION:=5.30 -PKG_RELEASE:=1 +PKG_RELEASE:=2 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz PKG_SOURCE_URL:=http://www.kernel.org/pub/linux/bluetooth/ @@ -47,7 +47,7 @@ $(call Package/bluez/Default) SECTION:=libs CATEGORY:=Libraries TITLE+= library - DEPENDS:=+libpthread + DEPENDS:=+libpthread +kmod-bluetooth endef define Package/bluez-utils @@ -55,10 +55,18 @@ $(call Package/bluez/Default) SECTION:=utils CATEGORY:=Utilities TITLE+= utilities - DEPENDS:=+bluez-libs +libpthread +librt +dbus +glib2 +libical +libncurses +libreadline $(INTL_DEPENDS) $(ICONV_DEPENDS) + DEPENDS:=+bluez-libs +libpthread +librt +glib2 +libncurses +libreadline $(INTL_DEPENDS) $(ICONV_DEPENDS) endef -define Package/bluez-utils/conffiles +define Package/bluez-daemon +$(call Package/bluez/Default) + SECTION:=utils + CATEGORY:=Utilities + TITLE+= daemon + DEPENDS:=+bluez-libs +bluez-utils +dbus +libical $(INTL_DEPENDS) $(ICONV_DEPENDS) +endef + +define Package/bluez-daemon/conffiles /etc/bluetooth/main.conf /etc/bluetooth/network.conf /etc/bluetooth/input.conf @@ -109,10 +117,28 @@ endef define Package/bluez-utils/install $(INSTALL_DIR) $(1)/usr/bin - $(CP) $(PKG_INSTALL_DIR)/usr/bin/* $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/bccmd $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/bluemoon $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/btmon $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/ciptool $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/hciattach $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/hciconfig $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/hcidump $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/hcitool $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/hex2hcd $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/l2ping $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/l2test $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/rctest $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/rfcomm $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/sdptool $(1)/usr/bin/ + $(INSTALL_BIN) $(PKG_BUILD_DIR)/attrib/gatttool $(1)/usr/bin/ +endef + +define Package/bluez-daemon/install + $(INSTALL_DIR) $(1)/usr/bin $(CP) $(PKG_INSTALL_DIR)/usr/lib/bluetooth/bluetoothd $(1)/usr/bin/ + $(CP) $(PKG_INSTALL_DIR)/usr/bin/bluetoothctl $(1)/usr/bin/ $(CP) $(PKG_INSTALL_DIR)/usr/lib/bluetooth/obexd $(1)/usr/bin/ - $(INSTALL_BIN) $(PKG_BUILD_DIR)/attrib/gatttool $(1)/usr/bin/ $(INSTALL_DIR) $(1)/etc/config $(INSTALL_DATA) ./files/bluetooth.config $(1)/etc/config/bluetooth $(INSTALL_DIR) $(1)/etc/dbus-1/system.d/ @@ -129,3 +155,4 @@ endef $(eval $(call BuildPackage,bluez-examples)) $(eval $(call BuildPackage,bluez-libs)) $(eval $(call BuildPackage,bluez-utils)) +$(eval $(call BuildPackage,bluez-daemon)) -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH v4] [kernel] upstream fix: mount overlayfs r/o if workdir cannot be created
This is the case e.g. if JFFS2 partition is full. see: https://www.mail-archive.com/linux-unionfs@vger.kernel.org/msg00246.html (a small error in a logmessage was changed and reported upstream) runtime tested on ar71xx with kernel 3.18.11 and r45772 this paritially fixes #19564 Signed-off-by: Thomas Huehn Signed-off-by: Bastian Bittorf --- ...-overlayfs-fallback-to-readonly-when-full.patch | 73 ++ 1 file changed, 73 insertions(+) create mode 100644 target/linux/generic/patches-3.18/912-overlayfs-fallback-to-readonly-when-full.patch diff --git a/target/linux/generic/patches-3.18/912-overlayfs-fallback-to-readonly-when-full.patch b/target/linux/generic/patches-3.18/912-overlayfs-fallback-to-readonly-when-full.patch new file mode 100644 index 000..9e5fad4 --- /dev/null +++ b/target/linux/generic/patches-3.18/912-overlayfs-fallback-to-readonly-when-full.patch @@ -0,0 +1,73 @@ +Index: linux-3.18.14/fs/overlayfs/copy_up.c +=== +--- linux-3.18.14.orig/fs/overlayfs/copy_up.c 2015-05-20 17:04:50.0 +0200 linux-3.18.14/fs/overlayfs/copy_up.c 2015-05-29 13:58:51.281147554 +0200 +@@ -300,6 +300,9 @@ + struct cred *override_cred; + char *link = NULL; + ++ if (WARN_ON(!workdir)) ++ return -EROFS; ++ + ovl_path_upper(parent, &parentpath); + upperdir = parentpath.dentry; + +Index: linux-3.18.14/fs/overlayfs/dir.c +=== +--- linux-3.18.14.orig/fs/overlayfs/dir.c 2015-05-20 17:04:50.0 +0200 linux-3.18.14/fs/overlayfs/dir.c 2015-05-29 14:00:55.727646504 +0200 +@@ -222,6 +222,9 @@ + struct kstat stat; + int err; + ++ if (WARN_ON(!workdir)) ++ return ERR_PTR(-EROFS); ++ + err = ovl_lock_rename_workdir(workdir, upperdir); + if (err) + goto out; +@@ -322,6 +325,9 @@ + struct dentry *newdentry; + int err; + ++ if (WARN_ON(!workdir)) ++ return -EROFS; ++ + err = ovl_lock_rename_workdir(workdir, upperdir); + if (err) + goto out; +@@ -506,6 +512,9 @@ + struct dentry *opaquedir = NULL; + int err; + ++ if (WARN_ON(!workdir)) ++ return -EROFS; ++ + if (is_dir) { + opaquedir = ovl_check_empty_and_clear(dentry); + err = PTR_ERR(opaquedir); +Index: linux-3.18.14/fs/overlayfs/super.c +=== +--- linux-3.18.14.orig/fs/overlayfs/super.c2015-05-20 17:04:50.0 +0200 linux-3.18.14/fs/overlayfs/super.c 2015-05-29 14:05:45.901472157 +0200 +@@ -740,9 +740,17 @@ + ufs->workdir = ovl_workdir_create(ufs->upper_mnt, workpath.dentry); + err = PTR_ERR(ufs->workdir); + if (IS_ERR(ufs->workdir)) { +- pr_err("overlayfs: failed to create directory %s/%s\n", +- ufs->config.workdir, OVL_WORKDIR_NAME); +- goto out_put_lower_mnt; ++ if (err == -ENOSPC || err == -EROFS) { ++ pr_warning("overlayfs: failed to create work directory" ++ " (%s), mounting read-only\n", ++ err == ENOSPC ? "ENOSPC" : "EROFS"); ++ sb->s_flags |= MS_RDONLY; ++ ufs->workdir = NULL; ++ } else { ++ pr_err("overlayfs: failed to create directory %s/%s\n", ++ ufs->config.workdir, OVL_WORKDIR_NAME); ++ goto out_put_lower_mnt; ++ } + } + + /* -- 2.4.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] menuconfig: unselect usign / build without opkg
while working on a minimal image, i tried to build without usign. is it possible to let it depend on opkg? can i send a patch for this? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel