Re: [OpenWrt-Devel] [PATCH 3/6] bcm53xx: update sprom from nvram to handle rev 11
On Thu, 2015-04-02 at 10:22 +0200, Rafał Miłecki wrote:
Hi Ian,
On 10 March 2015 at 04:30, Ian Kent ra...@themaw.net wrote:
Add new sprom revision 11 variables to the nvram - sprom reader.
Signed-off-by: Ian Kent ra...@themaw.net
There are few problems with bcm53xx's SPROM and I've few comments to your
patch.
As I expected, ;)
bcm53xx's SPROM driver is modified version of mainline
arch/mips/bcm74xx/sprom.c. It already differs a bit, but we can still
see the differences and try to mainline them. By adding more changes
to it we'll get lost and upsteaming changes will become more complex.
Yes, that's not good.
Other than that, current way of handling revisions is quite messy, I
guess you noticed it by yourself. I started reworking, see:
http://patchwork.linux-mips.org/patch/9659/
Again, my change if for upstream driver.
I've noticed a couple of changes you've submitted.
I must admit they are interesting but not what I would have come up
with. I guess it's my lack of experience with the code, but that'll come
in time.
Also your changes to struct ssb_sprom may get complex to maintain, I
believe you should try to upstream them.
Sure, we needed a place to start and something to work with.
At least the patch captures the names that need to be catered for and
should at least save a bit of leg work.
So my idea to resolve this situation is to:
1) sync bcm53xx SPROM driver with mainline one, let it differ only
with DT specific code
2) keep submitting SPROM changes to the mainline driver and just
backport them to bcm53xx
3) clear bcm47xx's sprom.c and work on moving it to the
drivers/firmware/broadcom/
OK, just to clarify, your recommending the canonical source is the
current bcm47xx and the goal is to make that generic and move it to a
common location in the source tree.
So I should familiarize myself with that source too.
I'm really happy you worked on SPROM rev 11 properties, it would be
great to get them as a patch for the bcm47xx's driver.
LOL, I need to start somewhere, thanks.
++ entry_count = ARRAY_SIZE(gains_info-rxgains5gmelnagaina);
++ for (j = 0; j entry_count; j++) {
++ snprintf(postfix, sizeof(postfix), %i, j);
++ snprintf(tmp, sizeof(tmp), %i:%s, i,
rxgains5gmelnagaina);
++ nvram_read_u8(fill, postfix, tmp,
++gains_info-rxgains5gmelnagaina[j],
0);
++ }
You shouldn't let unexpected NVRAM content crash your driver. Don't
trust the entry_count, verify it with your array size.
Umm ... don't have my patch handy and don't quite follow.
Since I set the array size in the sprom structure I've assumed I could
use it.
I'll check since I suspect I've used local working storage and perhaps
your saying I shouldn't trust the structure. So yes, I should check
entry_count in case something has changed in the sprom structure.
I'll need to check what happens if a value isn't present, IIRC the last
parameter was used in that case, setting the gains_info entry to NULL.
Ian
___
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] bcm53xx: update sprom from nvram to handle rev 11
Hi Ian,
On 10 March 2015 at 04:30, Ian Kent ra...@themaw.net wrote:
Add new sprom revision 11 variables to the nvram - sprom reader.
Signed-off-by: Ian Kent ra...@themaw.net
There are few problems with bcm53xx's SPROM and I've few comments to your patch.
bcm53xx's SPROM driver is modified version of mainline
arch/mips/bcm74xx/sprom.c. It already differs a bit, but we can still
see the differences and try to mainline them. By adding more changes
to it we'll get lost and upsteaming changes will become more complex.
Other than that, current way of handling revisions is quite messy, I
guess you noticed it by yourself. I started reworking, see:
http://patchwork.linux-mips.org/patch/9659/
Again, my change if for upstream driver.
Also your changes to struct ssb_sprom may get complex to maintain, I
believe you should try to upstream them.
So my idea to resolve this situation is to:
1) sync bcm53xx SPROM driver with mainline one, let it differ only
with DT specific code
2) keep submitting SPROM changes to the mainline driver and just
backport them to bcm53xx
3) clear bcm47xx's sprom.c and work on moving it to the
drivers/firmware/broadcom/
I'm really happy you worked on SPROM rev 11 properties, it would be
great to get them as a patch for the bcm47xx's driver.
++ entry_count = ARRAY_SIZE(gains_info-rxgains5gmelnagaina);
++ for (j = 0; j entry_count; j++) {
++ snprintf(postfix, sizeof(postfix), %i, j);
++ snprintf(tmp, sizeof(tmp), %i:%s, i,
rxgains5gmelnagaina);
++ nvram_read_u8(fill, postfix, tmp,
++gains_info-rxgains5gmelnagaina[j], 0);
++ }
You shouldn't let unexpected NVRAM content crash your driver. Don't
trust the entry_count, verify it with your array size.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 4/6] bcm53xx: increase nvram allocation size to 64k
On Thu, 2015-04-02 at 09:45 +0200, Rafał Miłecki wrote: On 10 March 2015 at 04:30, Ian Kent ra...@themaw.net wrote: The R8000 nvram is larger than 32k, increase nvram allocation to 64k to accomadate. I handled this by sending nvram.c patch for mainline: http://patchwork.linux-mips.org/patch/9651/ And backporting all changes to bcm53xx: https://dev.openwrt.org/changeset/45204/ OK, help me out with this patch. I thought it was necessary to calculate a from starting offset based on mtd size and nvram size since the code assumes the nvram partition might not start at 0 whereas in the patch it looks like a 0 starting offset is assumed? When I was working on this area of code, IIRC, the from offset was actually not 0. Ian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 4/6] bcm53xx: increase nvram allocation size to 64k
On 10 March 2015 at 04:30, Ian Kent ra...@themaw.net wrote: The R8000 nvram is larger than 32k, increase nvram allocation to 64k to accomadate. I handled this by sending nvram.c patch for mainline: http://patchwork.linux-mips.org/patch/9651/ And backporting all changes to bcm53xx: https://dev.openwrt.org/changeset/45204/ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Translating LuCI? (https://luci.subsignal.org/pootle/ down)
Greetings! TL;DR: Anyone able to write a short description on LuCI translation process and tools needed? LONGER EXPLANATION: I'm hoping to create a Finnish translation for the LuCI interface. However I can't find the instructions for the translation process as https://luci.subsignal.org/pootle/ has been down (502 Bad Gateway on Nginx) for several days. 1) Anyone involved with the https://luci.subsignal.org/pootle/ site to be able to aid in getting back up-n-running? 2) As an alternative to #1, is someone on the list able to describe the translation process? I'm suspected the translations to be use GNU Gettext based on the translation file extension .lmo (which I guessed to means LuCI mo) but when I renamed one of them to .mo and tried msgunfmt filename.mo it got the response that the file is not in GNU .mo format. I then took a look at the file in a hex editor and noticed it seems to contain HTML with nullbyte delimiters or something in that fashion. Anyone able help? Thank you in advance, Janne Cederberg Helsinki, Finland ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] kernel: add uinput module
This module is needed for bluetooth audio playback with pulseaudio 6 and bluez5. a working guide can be found in the wiki: http://wiki.openwrt.org/wiki/bluetooth.audio (additional packages/modifications are required and submitted to github feeds) tested with: Android mobile (Sony Xperia M) as audio source TI omap BeagleBoard as audio sink Signed-off-by: Dirk Neukirchen dirkneukirc...@web.de --- package/kernel/linux/modules/input.mk | 18 ++ 1 file changed, 18 insertions(+) diff --git a/package/kernel/linux/modules/input.mk b/package/kernel/linux/modules/input.mk index b44136b..86ff33c 100644 --- a/package/kernel/linux/modules/input.mk +++ b/package/kernel/linux/modules/input.mk @@ -205,3 +205,21 @@ define KernelPackage/keyboard-imx/description endef $(eval $(call KernelPackage,keyboard-imx)) + + +define KernelPackage/input-uinput + SUBMENU:=$(INPUT_MODULES_MENU) + TITLE:=user input module + DEPENDS:=+kmod-input-core + KCONFIG:= \ + CONFIG_INPUT_MISC=y \ + CONFIG_INPUT_UINPUT + FILES:=$(LINUX_DIR)/drivers/input/misc/uinput.ko + AUTOLOAD:=$(call AutoProbe,uinput) +endef + +define KernelPackage/input-uinput/description + user input modules needed for bluez +endef + +$(eval $(call KernelPackage,input-uinput)) -- 2.3.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 5/6] ipq806x: add platform usb support
This change adds DWC3 QCOM USB phys and TCSR drivers. These are cherry-picked from the following LKML threads: *dwc3 qcom: https://lkml.org/lkml/2014/9/12/599 *tcsr: https://lkml.org/lkml/2015/2/9/579 We're also adding an additional patch to add the corresponding dev nodes in the IPQ806x and AP148 dts files. Signed-off-by: Mathieu Olivari math...@codeaurora.org --- ...b-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch | 511 + ...1-ARM-qcom-add-USB-nodes-to-ipq806x-ap148.patch | 125 + ...qcom-gsbi-Add-support-for-ADM-CRCI-muxing.patch | 258 +++ .../103-ARM-DT-ipq8064-Add-TCSR-support.patch | 65 +++ .../patches-3.18/700-add-gmac-dts-suport.patch | 21 +- 5 files changed, 969 insertions(+), 11 deletions(-) create mode 100644 target/linux/ipq806x/patches-3.18/100-usb-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch create mode 100644 target/linux/ipq806x/patches-3.18/101-ARM-qcom-add-USB-nodes-to-ipq806x-ap148.patch create mode 100644 target/linux/ipq806x/patches-3.18/102-soc-qcom-gsbi-Add-support-for-ADM-CRCI-muxing.patch create mode 100644 target/linux/ipq806x/patches-3.18/103-ARM-DT-ipq8064-Add-TCSR-support.patch diff --git a/target/linux/ipq806x/patches-3.18/100-usb-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch b/target/linux/ipq806x/patches-3.18/100-usb-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch new file mode 100644 index 000..25803b8 --- /dev/null +++ b/target/linux/ipq806x/patches-3.18/100-usb-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch @@ -0,0 +1,511 @@ +--- a/drivers/phy/Kconfig b/drivers/phy/Kconfig +@@ -256,4 +256,15 @@ config PHY_STIH41X_USB + Enable this to support the USB transceiver that is part of + STMicroelectronics STiH41x SoC series. + ++config PHY_QCOM_DWC3 ++ tristate QCOM DWC3 USB PHY support ++ depends on ARCH_QCOM ++ depends on HAS_IOMEM ++ depends on OF ++ select GENERIC_PHY ++ help ++This option enables support for the Synopsis PHYs present inside the ++Qualcomm USB3.0 DWC3 controller. This driver supports both HS and SS ++PHY controllers. ++ + endmenu +--- a/drivers/phy/Makefile b/drivers/phy/Makefile +@@ -31,3 +31,4 @@ obj-$(CONFIG_PHY_ST_SPEAR1340_MIPHY) += + obj-$(CONFIG_PHY_XGENE) += phy-xgene.o + obj-$(CONFIG_PHY_STIH407_USB) += phy-stih407-usb.o + obj-$(CONFIG_PHY_STIH41X_USB) += phy-stih41x-usb.o ++obj-$(CONFIG_PHY_QCOM_DWC3) += phy-qcom-dwc3.o +--- /dev/null b/drivers/phy/phy-qcom-dwc3.c +@@ -0,0 +1,483 @@ ++/* Copyright (c) 2013-2014, Code Aurora Forum. All rights reserved. ++ * ++ * This program is free software; you can redistribute it and/or modify ++ * it under the terms of the GNU General Public License version 2 and ++ * only version 2 as published by the Free Software Foundation. ++ * ++ * This program is distributed in the hope that it will be useful, ++ * but WITHOUT ANY WARRANTY; without even the implied warranty of ++ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ++ * GNU General Public License for more details. ++ */ ++ ++#include linux/clk.h ++#include linux/err.h ++#include linux/io.h ++#include linux/module.h ++#include linux/of.h ++#include linux/phy/phy.h ++#include linux/platform_device.h ++#include linux/delay.h ++ ++/** ++ * USB QSCRATCH Hardware registers ++ */ ++#define QSCRATCH_GENERAL_CFG (0x08) ++#define HSUSB_PHY_CTRL_REG(0x10) ++ ++/* PHY_CTRL_REG */ ++#define HSUSB_CTRL_DMSEHV_CLAMP BIT(24) ++#define HSUSB_CTRL_USB2_SUSPEND BIT(23) ++#define HSUSB_CTRL_UTMI_CLK_ENBIT(21) ++#define HSUSB_CTRL_UTMI_OTG_VBUS_VALID BIT(20) ++#define HSUSB_CTRL_USE_CLKCOREBIT(18) ++#define HSUSB_CTRL_DPSEHV_CLAMP BIT(17) ++#define HSUSB_CTRL_COMMONONN BIT(11) ++#define HSUSB_CTRL_ID_HV_CLAMPBIT(9) ++#define HSUSB_CTRL_OTGSESSVLD_CLAMP BIT(8) ++#define HSUSB_CTRL_CLAMP_EN BIT(7) ++#define HSUSB_CTRL_RETENABLEN BIT(1) ++#define HSUSB_CTRL_PORBIT(0) ++ ++/* QSCRATCH_GENERAL_CFG */ ++#define HSUSB_GCFG_XHCI_REV BIT(2) ++ ++/** ++ * USB QSCRATCH Hardware registers ++ */ ++#define SSUSB_PHY_CTRL_REG(0x00) ++#define SSUSB_PHY_PARAM_CTRL_1(0x04) ++#define SSUSB_PHY_PARAM_CTRL_2(0x08) ++#define CR_PROTOCOL_DATA_IN_REG (0x0c) ++#define CR_PROTOCOL_DATA_OUT_REG (0x10) ++#define CR_PROTOCOL_CAP_ADDR_REG (0x14) ++#define CR_PROTOCOL_CAP_DATA_REG (0x18) ++#define CR_PROTOCOL_READ_REG (0x1c) ++#define CR_PROTOCOL_WRITE_REG (0x20) ++ ++/* PHY_CTRL_REG */ ++#define SSUSB_CTRL_REF_USE_PADBIT(28) ++#define SSUSB_CTRL_TEST_POWERDOWN BIT(27) ++#define SSUSB_CTRL_LANE0_PWR_PRESENT BIT(24)
[OpenWrt-Devel] [PATCH 0/6] Add USB support to ipq806x target
This patch set adds USB support to ipq806x. There are 3 main code areas which we modify: *target/linux/generic/config-*: add missing option which show-up when enabling USB on this target *target/linux/ipq806x: add patches update configs accordingly *package/kernel/linux/modules/usb.mk: add 3 packages for dwc3, dwc3-qcom and the corresponding PHYs Patches only concern 3.18 for now. 4.0 patches will come later as they get updated posted on LKML. Mathieu Olivari (6): ipq806x: clean-up kernel config file linux: Add missing config options to generic configs ipq806x: enable usb support kernel: add package for dwc3 dwc3-qcom drivers ipq806x: add platform usb support ipq806x: enable usb3 packages in default profile package/kernel/linux/modules/usb.mk| 53 +++ target/linux/generic/config-3.14 | 5 + target/linux/generic/config-3.18 | 12 + target/linux/generic/config-4.0| 12 + target/linux/ipq806x/Makefile | 2 +- target/linux/ipq806x/config-3.18 | 2 +- target/linux/ipq806x/config-4.0| 5 +- ...b-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch | 511 + ...1-ARM-qcom-add-USB-nodes-to-ipq806x-ap148.patch | 125 + ...qcom-gsbi-Add-support-for-ADM-CRCI-muxing.patch | 258 +++ .../103-ARM-DT-ipq8064-Add-TCSR-support.patch | 65 +++ .../patches-3.18/700-add-gmac-dts-suport.patch | 21 +- target/linux/ipq806x/profiles/default.mk | 3 +- 13 files changed, 1056 insertions(+), 18 deletions(-) create mode 100644 target/linux/ipq806x/patches-3.18/100-usb-phy-Add-Qualcomm-DWC3-HS-SS-PHY-drivers.patch create mode 100644 target/linux/ipq806x/patches-3.18/101-ARM-qcom-add-USB-nodes-to-ipq806x-ap148.patch create mode 100644 target/linux/ipq806x/patches-3.18/102-soc-qcom-gsbi-Add-support-for-ADM-CRCI-muxing.patch create mode 100644 target/linux/ipq806x/patches-3.18/103-ARM-DT-ipq8064-Add-TCSR-support.patch -- 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 1/6] ipq806x: clean-up kernel config file
Options that used to be in target config have been added to the generic config file, so remove them. Signed-off-by: Mathieu Olivari math...@codeaurora.org --- target/linux/ipq806x/config-3.18 | 1 - target/linux/ipq806x/config-4.0 | 4 2 files changed, 5 deletions(-) diff --git a/target/linux/ipq806x/config-3.18 b/target/linux/ipq806x/config-3.18 index 43b4950..b2f5571 100644 --- a/target/linux/ipq806x/config-3.18 +++ b/target/linux/ipq806x/config-3.18 @@ -212,7 +212,6 @@ CONFIG_MDIO_GPIO=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 diff --git a/target/linux/ipq806x/config-4.0 b/target/linux/ipq806x/config-4.0 index 5ce4644..8504c96 100644 --- a/target/linux/ipq806x/config-4.0 +++ b/target/linux/ipq806x/config-4.0 @@ -51,7 +51,6 @@ CONFIG_ARM_UNWIND=y CONFIG_ARM_VIRT_EXT=y CONFIG_AUTO_ZRELADDR=y # CONFIG_BATTERY_GAUGE_LTC2941 is not set -CONFIG_BCMA_DRIVER_PCI=y # CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0 CONFIG_BOUNCE=y @@ -220,15 +219,12 @@ CONFIG_LZO_DECOMPRESS=y CONFIG_MDIO_BITBANG=y CONFIG_MDIO_BOARDINFO=y CONFIG_MDIO_GPIO=y -# CONFIG_MFD_DA9150 is not set # CONFIG_MFD_QCOM_RPM is not set -# CONFIG_MFD_RT5033 is not set # CONFIG_MFD_SPMI_PMIC is not set CONFIG_MIGHT_HAVE_CACHE_L2X0=y CONFIG_MIGHT_HAVE_PCI=y CONFIG_MIGRATION=y CONFIG_MODULES_USE_ELF_REL=y -# CONFIG_MPLS is not set CONFIG_MSM_GCC_8660=y CONFIG_MSM_GCC_8960=y CONFIG_MSM_GCC_8974=y -- 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 2/6] linux: Add missing config options to generic configs
These missing options have been noticed while enabling the following configuration options on ipq806x, but they're available in the standard kernel: *ARCH_QCOM *CONFIG_USB_SUPPORT *CONFIG_USB_DWC3 *CONFIG_MFD_SYSCON Signed-off-by: Mathieu Olivari math...@codeaurora.org --- target/linux/generic/config-3.14 | 5 + target/linux/generic/config-3.18 | 12 target/linux/generic/config-4.0 | 12 3 files changed, 29 insertions(+) diff --git a/target/linux/generic/config-3.14 b/target/linux/generic/config-3.14 index 846ea1e..735c3e9 100644 --- a/target/linux/generic/config-3.14 +++ b/target/linux/generic/config-3.14 @@ -2860,6 +2860,7 @@ CONFIG_RCU_FANOUT_LEAF=16 # CONFIG_REGULATOR is not set # CONFIG_REGULATOR_ACT8865 is not set # CONFIG_REGULATOR_AD5398 is not set +# CONFIG_REGULATOR_ANATOP is not set # CONFIG_REGULATOR_BQ24022 is not set # CONFIG_REGULATOR_DA9210 is not set # CONFIG_REGULATOR_FAN53555 is not set @@ -3787,6 +3788,9 @@ CONFIG_USB_DEVICEFS=y # CONFIG_USB_DUMMY_HCD is not set # CONFIG_USB_DWC2 is not set # CONFIG_USB_DWC3 is not set +# CONFIG_USB_DWC3_EXYNOS is not set +# CONFIG_USB_DWC3_PCI is not set +# CONFIG_USB_DWC3_KEYSTONE is not set # CONFIG_USB_DWC_OTG_LPM is not set # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_EG20T is not set @@ -3910,6 +3914,7 @@ CONFIG_USB_GADGET_VBUS_DRAW=2 # CONFIG_USB_MIDI_GADGET is not set # CONFIG_USB_MON is not set # CONFIG_USB_MOUSE is not set +# CONFIG_USB_MSM_OTG is not set # CONFIG_USB_MUSB_HDRC is not set # CONFIG_USB_MV_U3D is not set # CONFIG_USB_MV_UDC is not set diff --git a/target/linux/generic/config-3.18 b/target/linux/generic/config-3.18 index e4df694..7c05594 100644 --- a/target/linux/generic/config-3.18 +++ b/target/linux/generic/config-3.18 @@ -925,6 +925,7 @@ CONFIG_DQL=y # CONFIG_DVB_TUNER_DIB0090 is not set # CONFIG_DW_DMAC is not set # CONFIG_DW_WATCHDOG is not set +# CONFIG_DWC3_HOST_USB3_LPM_ENABLE is not set # CONFIG_DX_SEP is not set # CONFIG_DYNAMIC_DEBUG is not set # CONFIG_E100 is not set @@ -1171,6 +1172,7 @@ CONFIG_GENERIC_TIME=y # CONFIG_GPIO_SCH is not set # CONFIG_GPIO_SCH311X is not set # CONFIG_GPIO_SX150X is not set +# CONFIG_GPIO_SYSCON is not set # CONFIG_GPIO_SYSFS is not set # CONFIG_GPIO_TS5500 is not set # CONFIG_GPIO_VX855 is not set @@ -1822,6 +1824,7 @@ CONFIG_LEDS_GPIO_PLATFORM=y # CONFIG_LEDS_PCA9685 is not set # CONFIG_LEDS_PWM is not set # CONFIG_LEDS_RENESAS_TPU is not set +# CONFIG_LEDS_SYSCON is not set # CONFIG_LEDS_TCA6507 is not set CONFIG_LEDS_TRIGGERS=y # CONFIG_LEDS_TRIGGER_BACKLIGHT is not set @@ -2836,6 +2839,7 @@ CONFIG_PCI_SYSCALL=y # CONFIG_PHYS_ADDR_T_64BIT is not set # CONFIG_PHY_EXYNOS_DP_VIDEO is not set # CONFIG_PHY_EXYNOS_MIPI_VIDEO is not set +# CONFIG_PHY_QCOM_DWC3 is not set # CONFIG_PHY_SAMSUNG_USB2 is not set # CONFIG_PID_IN_CONTEXTIDR is not set # CONFIG_PID_NS is not set @@ -2869,6 +2873,7 @@ CONFIG_PINMUX=y # CONFIG_POWER_AVS is not set # CONFIG_POWER_RESET is not set # CONFIG_POWER_RESET_RESTART is not set +# CONFIG_POWER_RESET_VERSATILE is not set # CONFIG_POWER_SUPPLY is not set # CONFIG_POWER_SUPPLY_DEBUG is not set # CONFIG_PPC4xx_GPIO is not set @@ -2994,6 +2999,7 @@ CONFIG_RCU_FANOUT_LEAF=16 # CONFIG_REGULATOR is not set # CONFIG_REGULATOR_ACT8865 is not set # CONFIG_REGULATOR_AD5398 is not set +# CONFIG_REGULATOR_ANATOP is not set # CONFIG_REGULATOR_BQ24022 is not set # CONFIG_REGULATOR_DA9210 is not set # CONFIG_REGULATOR_DA9211 is not set @@ -4053,11 +4059,16 @@ CONFIG_USB_DEVICEFS=y # CONFIG_USB_DWC2_HOST is not set # CONFIG_USB_DWC2_PERIPHERAL is not set # CONFIG_USB_DWC3 is not set +# CONFIG_USB_DWC3_EXYNOS is not set +# CONFIG_USB_DWC3_QCOM is not set +# CONFIG_USB_DWC3_PCI is not set +# CONFIG_USB_DWC3_KEYSTONE is not set # CONFIG_USB_DWC_OTG_LPM is not set # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_EG20T is not set # CONFIG_USB_EHCI_HCD_AT91 is not set # CONFIG_USB_EHCI_HCD_PPC_OF is not set +# CONFIG_USB_EHCI_MSM is not set # CONFIG_USB_EHCI_MV is not set CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y @@ -4181,6 +4192,7 @@ CONFIG_USB_GADGET_VBUS_DRAW=2 # CONFIG_USB_MIDI_GADGET is not set # CONFIG_USB_MON is not set # CONFIG_USB_MOUSE is not set +# CONFIG_USB_MSM_OTG is not set # CONFIG_USB_MUSB_HDRC is not set # CONFIG_USB_MV_U3D is not set # CONFIG_USB_MV_UDC is not set diff --git a/target/linux/generic/config-4.0 b/target/linux/generic/config-4.0 index 1f4d624..5e92d39 100644 --- a/target/linux/generic/config-4.0 +++ b/target/linux/generic/config-4.0 @@ -943,6 +943,7 @@ CONFIG_DQL=y # CONFIG_DVB_TUNER_DIB0090 is not set # CONFIG_DW_DMAC is not set # CONFIG_DW_WATCHDOG is not set +# CONFIG_DWC3_HOST_USB3_LPM_ENABLE is not set # CONFIG_DX_SEP is not set # CONFIG_DYNAMIC_DEBUG is not set # CONFIG_E100 is not set @@ -1191,6 +1192,7 @@ CONFIG_GENERIC_TIME=y # CONFIG_GPIO_SCH is not set # CONFIG_GPIO_SCH311X is not set #
[OpenWrt-Devel] [PATCH 4/6] kernel: add package for dwc3 usb driver used on ipq806x
Signed-off-by: Mathieu Olivari math...@codeaurora.org --- package/kernel/linux/modules/usb.mk | 53 + 1 file changed, 53 insertions(+) diff --git a/package/kernel/linux/modules/usb.mk b/package/kernel/linux/modules/usb.mk index 4950ab8..09251fa 100644 --- a/package/kernel/linux/modules/usb.mk +++ b/package/kernel/linux/modules/usb.mk @@ -146,6 +146,23 @@ endef $(eval $(call KernelPackage,usb-phy-am335x)) +define KernelPackage/usb-phy-qcom-dwc3 + TITLE:=DWC3 USB QCOM PHY driver + DEPENDS:=@TARGET_ipq806x + KCONFIG:= CONFIG_PHY_QCOM_DWC3 + FILES:= $(LINUX_DIR)/drivers/phy/phy-qcom-dwc3.ko + AUTOLOAD:=$(call AutoLoad,45,phy-qcom-dwc3,1) + $(call AddDepends/usb) +endef + +define KernelPackage/usb-phy-qcom-dwc3/description + This driver provides support for the integrated DesignWare + USB3 IP Core within the QCOM SoCs. +endef + +$(eval $(call KernelPackage,usb-phy-qcom-dwc3)) + + define KernelPackage/usb-phy-omap-usb2 TITLE:=Support for OMAP2 USB PHY KCONFIG:= \ @@ -493,6 +510,42 @@ endef $(eval $(call KernelPackage,usb2-oxnas)) +define KernelPackage/usb-dwc3-qcom + TITLE:=DWC3 USB QCOM controller driver + DEPENDS:=@TARGET_ipq806x +kmod-usb-dwc3 +kmod-usb-phy-dwc3-qcom + KCONFIG:= CONFIG_USB_DWC3_QCOM + FILES:= $(LINUX_DIR)/drivers/usb/dwc3/dwc3-qcom.ko + AUTOLOAD:=$(call AutoLoad,53,dwc3-qcom,1) + $(call AddDepends/usb) +endef + +define KernelPackage/usb-dwc3-qcom/description + This driver provides support for the integrated DesignWare + USB3 IP Core within the QCOM SoCs. +endef + +$(eval $(call KernelPackage,usb-dwc3-qcom)) + + +define KernelPackage/usb-dwc3 + TITLE:=DWC3 USB controller driver + KCONFIG:= \ + CONFIG_USB_DWC3 \ + CONFIG_USB_DWC3_DEBUG=n \ + CONFIG_USB_DWC3_VERBOSE=n + FILES:= $(LINUX_DIR)/drivers/usb/dwc3/dwc3.ko + AUTOLOAD:=$(call AutoLoad,54,dwc3,1) + $(call AddDepends/usb) +endef + +define KernelPackage/usb-dwc3/description + This driver provides support for the Dual Role SuperSpeed + USB Controller based on the Synopsys DesignWare USB3 IP Core +endef + +$(eval $(call KernelPackage,usb-dwc3)) + + define KernelPackage/usb-acm TITLE:=Support for modems/isdn controllers KCONFIG:=CONFIG_USB_ACM -- 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 6/6] ipq806x: enable usb3 packages in default profile
Default profile already enables usb2 so we'll do the same for usb3 now that we have support for it. Signed-off-by: Mathieu Olivari math...@codeaurora.org --- target/linux/ipq806x/profiles/default.mk | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/target/linux/ipq806x/profiles/default.mk b/target/linux/ipq806x/profiles/default.mk index ded0164..00e1611 100644 --- a/target/linux/ipq806x/profiles/default.mk +++ b/target/linux/ipq806x/profiles/default.mk @@ -9,7 +9,8 @@ define Profile/Default NAME:=Default Profile (minimum package set) PACKAGES:= \ - kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-ledtrig-usbdev + kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-ledtrig-usbdev \ + kmod-usb3 kmod-usb-dwc3-qcom endef define Profile/Default/Description -- 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] e2fsprogs broken on ARM...
On 30 March 2015 at 23:55, Roman Yeryomin leroi.li...@gmail.com wrote: On 30 March 2015 at 22:21, John Crispin blo...@openwrt.org wrote: On 30/03/2015 21:02, John Szakmeister wrote: Commit 988e3615e52b2cd9b9e07f4bbbd76494f7e0cb24 broke building e2fsprogs on an ARM platform. It looks like that in version 1.42.10 the decision was made to drop locally defined versions of both sync_file_range() and fallocate() because they were broken on 32-bit platforms, and there was some issue on the MIPS32 platform too (see 58229aaf85d435469e901c974f31ead6d9124166 is the e2fsprogs git repo). They decided to let the C library handle it, but unfortunately, uClibc really isn't up to it at the moment. It might be possible to backport the work done to make sync_file_range() on the mainline uClibc, but it might beyond my capability at the moment (I don't have a way to test other platforms right now)--though I can try, if you'd like me to. Or, should we just patch out the building of e4defrag for the time being? We don't currently package it. Thanks! -John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel fix in the making, will be pushed tomorrow ... I suppose the subj, this ticket https://dev.openwrt.org/ticket/19336 and this error are also related Making all in libtransmission make[5]: Entering directory '/tmp/roman/build_dir.mt7620/target-mipsel_24kec+dsp_uClibc-0.9.33.2/transmission-2.84/libtransmission' CC fdlimit.o In file included from fdlimit.c:39:0: /home/roman/dev/openwrt/build/mt7620/staging_dir/toolchain-mipsel_24kec+dsp_gcc-4.8-linaro_uClibc-0.9.33.2/include/fcntl.h:256:12: error: conflicting types for 'fallocate64' extern int fallocate64 (int __fd, int __mode, __off64_t __offset, __off64_t __len); ^ fdlimit.c:28:14: note: previous declaration of 'fallocate64' was here extern int fallocate64 (int fd, int mode, uint64_t offset, uint64_t len); ^ Makefile:1121: recipe for target 'fdlimit.o' failed make[5]: *** [fdlimit.o] Error 1 make[5]: Leaving directory '/tmp/roman/build_dir.mt7620/target-mipsel_24kec+dsp_uClibc-0.9.33.2/transmission-2.84/libtransmission' https://dev.openwrt.org/changeset/45249 fixes sync_file_range transmission patch sent by separate email Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] swconfig: set pvid to the same value as vid for untagged ports?
On 31 March 2015 at 00:10, Roman Yeryomin leroi.li...@gmail.com wrote: I was little bit surprised it's not so currently. Although I understand that, potentially, there are use cases when you want port pvid to be different from it's untagged vlan id, but usually one wants port ingress traffic to fall into the same vlan as it's untagged egress traffic. Even more, current luci interface ignores 'switch_port' section of /etc/config/network making it impossible to change pvid from web ui. Also if one creates a new vlan most likely he will need a new interface (e.g. eth0.10 for vlan 10). This is not obvious for a regular user. I think it would be much better if netifd (or whoever does it) would at least set pvid to vid value for untagged ports in same vlan group. I can try doing it myself if somebody can give me the pointers to where the changes should go. Did I overlook something? Are there other/better options? Anybody? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Question about conflict between ubus_invoke and uloop_run
HI !
I am Kevin and learning the ubus code and got something that is confusing me
very much in the code.
My question is regarding code in ubus_invoke - ubus_complete_request,
I can see that there are lots of uloop related code in ubus_complete_request
if (!registered) {
uloop_init();
ubus_add_uloop(ctx);
}
while (!req-status_msg) {
bool cancelled = uloop_cancelled;
uloop_cancelled = false;
if (req_timeout) {
timeout = time_end -
get_time_msec();
if (timeout = 0) {
ubus_set_req_status(req, UBUS_STATUS_TIMEOUT);
break;
}
}
ubus_poll_data(ctx, (unsigned int) timeout);
uloop_cancelled = cancelled;
}
My question is why is uloop involved here? uloop could be working in another
thread and also listen on the same socket.
I idea that, before the ubus_invoke sends the request messge, it should disable
the uloop for the current socket, so that code in uloop_run will not receive
anything from the same socket.
Because after calling ubus_add_uloop(ctx), the uloop_run could also be
receiving the response data
And this function could cause the uloop_run to quit the while loop.
How should I understand the logic here?
And How should I do if I want to call ubus_invoke as a client and use uloop_run
as a server at the same process?
Thanks very much!
Best regards
Kevin
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] transmission: fallocate64 was bacported to uClibc
Signed-off-by: Roman Yeryomin ro...@advem.lv --- .../patches/010-remove-fallocate64-definition.patch| 14 ++ .../patches/010_libtransmission_fallocate64_eglibc.patch | 12 2 files changed, 14 insertions(+), 12 deletions(-) create mode 100644 net/transmission/patches/010-remove-fallocate64-definition.patch delete mode 100644 net/transmission/patches/010_libtransmission_fallocate64_eglibc.patch diff --git a/net/transmission/patches/010-remove-fallocate64-definition.patch b/net/transmission/patches/010-remove-fallocate64-definition.patch new file mode 100644 index 000..869e64b --- /dev/null +++ b/net/transmission/patches/010-remove-fallocate64-definition.patch @@ -0,0 +1,14 @@ +--- a/libtransmission/fdlimit.c2015-04-03 03:41:10.936535751 +0300 b/libtransmission/fdlimit.c2015-04-03 03:41:20.272536044 +0300 +@@ -22,11 +22,6 @@ + #include fcntl.h + #endif + +-#ifdef HAVE_FALLOCATE64 +- /* FIXME can't find the right #include voodoo to pick up the declaration.. */ +- extern int fallocate64 (int fd, int mode, uint64_t offset, uint64_t len); +-#endif +- + #ifdef HAVE_XFS_XFS_H + #include xfs/xfs.h + #endif diff --git a/net/transmission/patches/010_libtransmission_fallocate64_eglibc.patch b/net/transmission/patches/010_libtransmission_fallocate64_eglibc.patch deleted file mode 100644 index d4f82fc..000 --- a/net/transmission/patches/010_libtransmission_fallocate64_eglibc.patch +++ /dev/null @@ -1,12 +0,0 @@ a/libtransmission/fdlimit.c2014-07-01 20:08:59.0 +0300 -+++ b/libtransmission/fdlimit.c2014-07-13 13:30:17.0 +0300 -@@ -22,7 +22,8 @@ - #include fcntl.h - #endif - --#ifdef HAVE_FALLOCATE64 -+/* no need to define fallocate64 in glibc/eglibc case */ -+#if defined(__UCLIBC__) (HAVE_FALLOCATE64) - /* FIXME can't find the right #include voodoo to pick up the declaration.. */ - extern int fallocate64 (int fd, int mode, uint64_t offset, uint64_t len); - #endif -- 2.1.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 3/6] ipq806x: enable usb support
This change doesn't make USB functional but it does make it selectable from a configuration perspective. Signed-off-by: Mathieu Olivari math...@codeaurora.org --- target/linux/ipq806x/config-3.18 | 1 + target/linux/ipq806x/config-4.0 | 1 + 2 files changed, 2 insertions(+) diff --git a/target/linux/ipq806x/config-3.18 b/target/linux/ipq806x/config-3.18 index b2f5571..e0535d3 100644 --- a/target/linux/ipq806x/config-3.18 +++ b/target/linux/ipq806x/config-3.18 @@ -351,6 +351,7 @@ CONFIG_UEVENT_HELPER_PATH= CONFIG_UID16=y CONFIG_UNCOMPRESS_INCLUDE=debug/uncompress.h CONFIG_UNINLINE_SPIN_UNLOCK=y +CONFIG_USB_SUPPORT=y CONFIG_USE_OF=y CONFIG_VECTORS_BASE=0x # CONFIG_VFIO is not set diff --git a/target/linux/ipq806x/config-4.0 b/target/linux/ipq806x/config-4.0 index 8504c96..4d56106 100644 --- a/target/linux/ipq806x/config-4.0 +++ b/target/linux/ipq806x/config-4.0 @@ -365,6 +365,7 @@ CONFIG_UEVENT_HELPER_PATH= CONFIG_UID16=y CONFIG_UNCOMPRESS_INCLUDE=debug/uncompress.h CONFIG_UNINLINE_SPIN_UNLOCK=y +CONFIG_USB_SUPPORT=y CONFIG_USE_OF=y CONFIG_VECTORS_BASE=0x CONFIG_VFP=y -- 1.9.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] kernel: add garmin_gps module
OpenWrt on sailboats requested: https://forum.openwrt.org/viewtopic.php?id=56586 Signed-off-by: Dirk Neukirchen dirkneukirc...@web.de --- package/kernel/linux/modules/usb.mk | 15 +++ 1 file changed, 15 insertions(+) diff --git a/package/kernel/linux/modules/usb.mk b/package/kernel/linux/modules/usb.mk index e3d7165..fc47568 100644 --- a/package/kernel/linux/modules/usb.mk +++ b/package/kernel/linux/modules/usb.mk @@ -631,6 +631,21 @@ endef $(eval $(call KernelPackage,usb-serial-ftdi)) +define KernelPackage/usb-serial-garmin + TITLE:=Support for Garmin GPS devices + KCONFIG:=CONFIG_USB_SERIAL_GARMIN + FILES:=$(LINUX_DIR)/drivers/usb/serial/garmin_gps.ko + AUTOLOAD:=$(call AutoProbe,garmin_gps) + $(call AddDepends/usb-serial) +endef + +define KernelPackage/usb-serial-garmin/description + Should work with most Garmin GPS devices which have a native USB port. +endef + +$(eval $(call KernelPackage,usb-serial-garmin)) + + define KernelPackage/usb-serial-ti-usb TITLE:=Support for TI USB 3410/5052 KCONFIG:=CONFIG_USB_SERIAL_TI -- 2.3.4 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 4/6] bcm53xx: increase nvram allocation size to 64k
On Thu, 2015-04-02 at 17:47 +0800, Ian Kent wrote: On Thu, 2015-04-02 at 09:45 +0200, Rafał Miłecki wrote: On 10 March 2015 at 04:30, Ian Kent ra...@themaw.net wrote: The R8000 nvram is larger than 32k, increase nvram allocation to 64k to accomadate. I handled this by sending nvram.c patch for mainline: http://patchwork.linux-mips.org/patch/9651/ And backporting all changes to bcm53xx: https://dev.openwrt.org/changeset/45204/ OK, help me out with this patch. I thought it was necessary to calculate a from starting offset based on mtd size and nvram size since the code assumes the nvram partition might not start at 0 whereas in the patch it looks like a 0 starting offset is assumed? When I was working on this area of code, IIRC, the from offset was actually not 0. Mmm .. so that's probably wrong since ... mtd = get_mtd_device_nm(nvram); Should get us the start of the nvram partition at offset 0. Ian ___ 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] bcm53xx: update sprom from nvram to handle rev 11
On 2 April 2015 at 11:03, Ian Kent ra...@themaw.net wrote:
On Thu, 2015-04-02 at 10:22 +0200, Rafał Miłecki wrote:
Other than that, current way of handling revisions is quite messy, I
guess you noticed it by yourself. I started reworking, see:
http://patchwork.linux-mips.org/patch/9659/
Again, my change if for upstream driver.
I've noticed a couple of changes you've submitted.
I must admit they are interesting but not what I would have come up
with. I guess it's my lack of experience with the code, but that'll come
in time.
That's expected. When you look at driver for the first time, it's hard
to have a nice idea for redesigning it. Unless it's a real crap :P
So my idea to resolve this situation is to:
1) sync bcm53xx SPROM driver with mainline one, let it differ only
with DT specific code
2) keep submitting SPROM changes to the mainline driver and just
backport them to bcm53xx
3) clear bcm47xx's sprom.c and work on moving it to the
drivers/firmware/broadcom/
OK, just to clarify, your recommending the canonical source is the
current bcm47xx and the goal is to make that generic and move it to a
common location in the source tree.
So I should familiarize myself with that source too.
You got me correct.. This is the same trick I did with bcm53xx NVRAM
driver. Some time ago it was also quite different from the bcm47xx
one. So I modified bcm47xx nvram.c (by sending upstream patches) to
make is usable by bcm53xx and then backported it to bcm53xx. Now the
drivers are identical according to my knowledge.
Few minutes ago I've updated bcm53xx SPROM driver to be based on bcm47xx's one:
https://dev.openwrt.org/changeset/45230/
so we are already doing pretty well with unifying them.
You can now work with bcm53xx's variation of SPROM driver and easily
port changes to the bcm47xx's sprom.c
++ entry_count = ARRAY_SIZE(gains_info-rxgains5gmelnagaina);
++ for (j = 0; j entry_count; j++) {
++ snprintf(postfix, sizeof(postfix), %i, j);
++ snprintf(tmp, sizeof(tmp), %i:%s, i,
rxgains5gmelnagaina);
++ nvram_read_u8(fill, postfix, tmp,
++gains_info-rxgains5gmelnagaina[j],
0);
++ }
You shouldn't let unexpected NVRAM content crash your driver. Don't
trust the entry_count, verify it with your array size.
Umm ... don't have my patch handy and don't quite follow.
Just ignore my silly comment, my brain got some memory corruption :|
--
Rafał
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 4/6] bcm53xx: increase nvram allocation size to 64k
On 2 April 2015 at 11:57, Ian Kent ra...@themaw.net wrote: On Thu, 2015-04-02 at 17:47 +0800, Ian Kent wrote: On Thu, 2015-04-02 at 09:45 +0200, Rafał Miłecki wrote: On 10 March 2015 at 04:30, Ian Kent ra...@themaw.net wrote: The R8000 nvram is larger than 32k, increase nvram allocation to 64k to accomadate. I handled this by sending nvram.c patch for mainline: http://patchwork.linux-mips.org/patch/9651/ And backporting all changes to bcm53xx: https://dev.openwrt.org/changeset/45204/ OK, help me out with this patch. I thought it was necessary to calculate a from starting offset based on mtd size and nvram size since the code assumes the nvram partition might not start at 0 whereas in the patch it looks like a 0 starting offset is assumed? When I was working on this area of code, IIRC, the from offset was actually not 0. Mmm .. so that's probably wrong since ... mtd = get_mtd_device_nm(nvram); Should get us the start of the nvram partition at offset 0. That's right, if something doesn't work for you, let me know. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] kernel: add usb-serial-simple module
replaces kmod-usb-serial-motorola-phone it's found only in Kernel 3.12 This module handles many simple USB serial devices like Motorola Phones, GPS reveivers in Kernels above 3.14 Signed-off-by: Dirk Neukirchen dirkneukirc...@web.de --- package/kernel/linux/modules/usb.mk | 28 1 file changed, 28 insertions(+) diff --git a/package/kernel/linux/modules/usb.mk b/package/kernel/linux/modules/usb.mk index 7a63829..38516f4 100644 --- a/package/kernel/linux/modules/usb.mk +++ b/package/kernel/linux/modules/usb.mk @@ -615,6 +615,34 @@ endef $(eval $(call KernelPackage,usb-serial-ftdi)) +define KernelPackage/usb-serial-simple + TITLE:=USB Serial Simple (Motorola phone) + KCONFIG:=CONFIG_USB_SERIAL_SIMPLE + FILES:=$(LINUX_DIR)/drivers/usb/serial/usb-serial-simple.ko + AUTOLOAD:=$(call AutoProbe,usb-serial-simple) + $(call AddDepends/usb-serial) +endef + +define KernelPackage/usb-serial-simple/description + Kernel support for very simple devices. + +Specifically, it supports: + - Suunto ANT+ USB device. + - Medtronic CareLink USB device (3.18) + - Fundamental Software dongle. + - Google USB serial devices (3.19) + - HP4x calculators + - a number of Motorola phones + - Novatel Wireless GPS receivers (3.18) + - Siemens USB/MPI adapter. + - ViVOtech ViVOpay USB device. + - Infineon Modem Flashloader USB interface + - ZIO Motherboard USB serial interface +endef + +$(eval $(call KernelPackage,usb-serial-simple)) + + define KernelPackage/usb-serial-ti-usb TITLE:=Support for TI USB 3410/5052 KCONFIG:=CONFIG_USB_SERIAL_TI -- 2.3.4 ___ 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] bcm53xx: update sprom from nvram to handle rev 11
On 10 March 2015 at 04:30, Ian Kent ra...@themaw.net wrote:
+@@ -93,6 +113,9 @@ struct ssb_sprom {
+ u16 boardflags2_lo; /* Board flags (bits 32-47) */
+ u16 boardflags2_hi; /* Board flags (bits 48-63) */
+ /* TODO store board flags in a single u64 */
++ /* spromrev 11 */
++ u16 boardflags3_lo; /* Board flags (bits 64-79) */
++ u16 boardflags3_hi; /* Board flags (bits 80-95) */
Please, please, use u32 boardflags3. We already suffer from split
boardflags(1) and boardflags2 too much ;)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] kernel: watchdog modules should be loaded on boot
Otherwise procd cannot initialize the watchdog since the module will be loaded later. Tested with booke_wdt. Signed-off-by: Helmut Schaa helmut.sc...@googlemail.com --- package/kernel/linux/modules/other.mk | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/package/kernel/linux/modules/other.mk b/package/kernel/linux/modules/other.mk index 20964f5..36d3ef9 100644 --- a/package/kernel/linux/modules/other.mk +++ b/package/kernel/linux/modules/other.mk @@ -468,7 +468,7 @@ define KernelPackage/wdt-omap DEPENDS:=@(TARGET_omap24xx||TARGET_omap35xx) KCONFIG:=CONFIG_OMAP_WATCHDOG FILES:=$(LINUX_DIR)/drivers/$(WATCHDOG_DIR)/omap_wdt.ko - AUTOLOAD:=$(call AutoLoad,50,omap_wdt.ko) + AUTOLOAD:=$(call AutoLoad,50,omap_wdt.ko,1) endef define KernelPackage/wdt-omap/description @@ -484,7 +484,7 @@ define KernelPackage/wdt-orion DEPENDS:=@TARGET_orion||TARGET_kirkwood||TARGET_mvebu KCONFIG:=CONFIG_ORION_WATCHDOG FILES:=$(LINUX_DIR)/drivers/$(WATCHDOG_DIR)/orion_wdt.ko - AUTOLOAD:=$(call AutoLoad,50,orion_wdt) + AUTOLOAD:=$(call AutoLoad,50,orion_wdt,1) endef define KernelPackage/wdt-orion/description @@ -500,7 +500,7 @@ define KernelPackage/booke-wdt DEPENDS:=@(TARGET_mpc85xx||TARGET_ppc40x||TARGET_ppc44x) KCONFIG:=CONFIG_BOOKE_WDT FILES:=$(LINUX_DIR)/drivers/$(WATCHDOG_DIR)/booke_wdt.ko - AUTOLOAD:=$(call AutoLoad,50,booke_wdt) + AUTOLOAD:=$(call AutoLoad,50,booke_wdt,1) endef define KernelPackage/booke-wdt/description -- 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] question about target/linux/mxs/patches-3.xx/120-dt-add-i2c.patch
On 02.04.2015 16:21, Harald Geyer wrote: Hi! It seems 120-dt-add-i2c.patch was first added to the git repository with commit bf323c768d5393a43a3fc74c5059c114f8fac4c0 mxs: initial 3.13 support As of today the mainline kernel still lacks the äquivalent functionality. I'd like to get this little devicetree snippet upstream, but I couldn't track down the copyright/authorship of that code. Who is the author and what is the reason that this has not been submitted upstream yet? TIA, Harald ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel NOT involved in any of the pieces/subsystem/kernel but I like to google so simply search with this: MX23_PAD_SSP1_DATA1__I2C_SCL leads to this mail: http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/142483.html ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] question about target/linux/mxs/patches-3.xx/120-dt-add-i2c.patch
Hi! It seems 120-dt-add-i2c.patch was first added to the git repository with commit bf323c768d5393a43a3fc74c5059c114f8fac4c0 mxs: initial 3.13 support As of today the mainline kernel still lacks the äquivalent functionality. I'd like to get this little devicetree snippet upstream, but I couldn't track down the copyright/authorship of that code. Who is the author and what is the reason that this has not been submitted upstream yet? TIA, Harald ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/2] mvebu: backport cpuidle improvements
Upstream commits 43b68879de27b1993518687fbc6013da80cdcbfe
and ce6031c89a35cffd5a5992b08377b77f49a004b9 improve the
cpuidle driver on Armada XP. The latter commit improves
performance at the slight expense of power consumption.
Signed-off-by: Claudio Leite lei...@staticky.com
---
...uidle-mvebu-Fix-the-CPU-PM-notifier-usage.patch | 38 +
...bu-Update-cpuidle-thresholds-for-Armada-X.patch | 66 ++
2 files changed, 104 insertions(+)
create mode 100644
target/linux/mvebu/patches-3.18/060-cpuidle-mvebu-Fix-the-CPU-PM-notifier-usage.patch
create mode 100644
target/linux/mvebu/patches-3.18/061-cpuidle-mvebu-Update-cpuidle-thresholds-for-Armada-X.patch
diff --git
a/target/linux/mvebu/patches-3.18/060-cpuidle-mvebu-Fix-the-CPU-PM-notifier-usage.patch
b/target/linux/mvebu/patches-3.18/060-cpuidle-mvebu-Fix-the-CPU-PM-notifier-usage.patch
new file mode 100644
index 000..afd6617
--- /dev/null
+++
b/target/linux/mvebu/patches-3.18/060-cpuidle-mvebu-Fix-the-CPU-PM-notifier-usage.patch
@@ -0,0 +1,38 @@
+From 43b68879de27b1993518687fbc6013da80cdcbfe Mon Sep 17 00:00:00 2001
+From: Gregory CLEMENT gregory.clem...@free-electrons.com
+Date: Thu, 26 Feb 2015 18:20:48 +0100
+Subject: [PATCH] cpuidle: mvebu: Fix the CPU PM notifier usage
+
+As stated in kernel/cpu_pm.c, Platform is responsible for ensuring
+that cpu_pm_enter is not called twice on the same CPU before
+cpu_pm_exit is called.. In the current code in case of failure when
+calling mvebu_v7_cpu_suspend, the function cpu_pm_exit() is never
+called whereas cpu_pm_enter() was called just before.
+
+This patch moves the cpu_pm_exit() in order to balance the
+cpu_pm_enter() calls.
+
+Cc: sta...@vger.kernel.org
+Reported-by: Fulvio Benini f...@libero.it
+Signed-off-by: Gregory CLEMENT gregory.clem...@free-electrons.com
+Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
+---
+ drivers/cpuidle/cpuidle-mvebu-v7.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/drivers/cpuidle/cpuidle-mvebu-v7.c
b/drivers/cpuidle/cpuidle-mvebu-v7.c
+@@ -37,11 +37,11 @@ static int mvebu_v7_enter_idle(struct cp
+ deepidle = true;
+
+ ret = mvebu_v7_cpu_suspend(deepidle);
++ cpu_pm_exit();
++
+ if (ret)
+ return ret;
+
+- cpu_pm_exit();
+-
+ return index;
+ }
+
diff --git
a/target/linux/mvebu/patches-3.18/061-cpuidle-mvebu-Update-cpuidle-thresholds-for-Armada-X.patch
b/target/linux/mvebu/patches-3.18/061-cpuidle-mvebu-Update-cpuidle-thresholds-for-Armada-X.patch
new file mode 100644
index 000..bc0f1a6
--- /dev/null
+++
b/target/linux/mvebu/patches-3.18/061-cpuidle-mvebu-Update-cpuidle-thresholds-for-Armada-X.patch
@@ -0,0 +1,66 @@
+From ce6031c89a35cffd5a5992b08377b77f49a004b9 Mon Sep 17 00:00:00 2001
+From: Sebastien Rannou m...@sbrk.org
+Date: Fri, 13 Feb 2015 15:55:03 +0100
+Subject: [PATCH] cpuidle: mvebu: Update cpuidle thresholds for Armada XP SOCs
+
+Originally, the thresholds used in the cpuidle driver for Armada SOCs
+were temporarily chosen, leaving room for improvements.
+
+This commit updates the thresholds for the Armada XP SOCs with values
+that positively impact performances:
+
+without patch with patch vendor kernel
+ - iperf localhost (gbit/sec) ~3.7 ~6.4 ~5.4
+ - ioping tmpfs (iops) ~163k ~206k~179k
+ - ioping tmpfs (mib/s) ~636 ~805 ~699
+
+The idle power consumption is negatively impacted (proportionally less
+than the performance gain), and we are still performing better than
+the vendor kernel here:
+
+without patch with patch vendor kernel
+ - power consumption idle (W) ~2.4~3.2~4.4
+ - power consumption busy (W) ~8.6~8.3~8.6
+
+There is still room for improvement regarding the value of these
+thresholds, they were chosen to mimic the vendor kernel.
+
+This patch only impacts Armada XP SOCs and was tested on Online Labs
+C1 boards. A similar approach can be taken to improve the performances
+of the Armada 370 and Armada 38x SOCs.
+
+Thanks a lot to Thomas Petazzoni, Gregory Clement and Willy Tarreau
+for the discussions and tips around this topic.
+
+Signed-off-by: Sebastien Rannou m...@sbrk.org
+Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
+Acked-by: Gregory CLEMENT gregory.clem...@free-electrons.com
+---
+ drivers/cpuidle/cpuidle-mvebu-v7.c | 8
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+--- a/drivers/cpuidle/cpuidle-mvebu-v7.c
b/drivers/cpuidle/cpuidle-mvebu-v7.c
+@@ -50,18 +50,18 @@ static struct cpuidle_driver armadaxp_id
+ .states[0] = ARM_CPUIDLE_WFI_STATE,
+ .states[1] = {
+ .enter = mvebu_v7_enter_idle,
+- .exit_latency = 10,
++ .exit_latency = 100,
+ .power_usage=
[OpenWrt-Devel] [PATCH 2/2] mvebu: refresh patch
Signed-off-by: Claudio Leite lei...@staticky.com --- .../206-mvebu_wrt1900ac_use_pwm-fan_rather_than_gpio-fan.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/mvebu/patches-3.18/206-mvebu_wrt1900ac_use_pwm-fan_rather_than_gpio-fan.patch b/target/linux/mvebu/patches-3.18/206-mvebu_wrt1900ac_use_pwm-fan_rather_than_gpio-fan.patch index 8af5eba..3c6e7d2 100644 --- a/target/linux/mvebu/patches-3.18/206-mvebu_wrt1900ac_use_pwm-fan_rather_than_gpio-fan.patch +++ b/target/linux/mvebu/patches-3.18/206-mvebu_wrt1900ac_use_pwm-fan_rather_than_gpio-fan.patch @@ -9,7 +9,7 @@ Signed-off-by: Andrew Lunn and...@lunn.ch --- a/arch/arm/boot/dts/armada-xp-mamba.dts +++ b/arch/arm/boot/dts/armada-xp-mamba.dts -@@ -302,13 +302,11 @@ +@@ -390,13 +390,11 @@ }; }; -- 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] Translating LuCI? (https://luci.subsignal.org/pootle/ down)
Hey Christian! Thank you for the info, helps a lot! I'm familiar with Poedit and po/mo files so will be a breeze :) Thanks again! -Janne On Apr 2, 2015 8:03 PM, Christian Schoenebeck christian.schoeneb...@gmail.com wrote: Hi Janne, from my knowledge pottle is down since LuCI moved to GitHub. inside luci/modules/[package] and luci/applications/[application] on source tree you should find a po directory where translations are stored. Inside there is a templates/[file].pot This is the catalog (master) the translation based on. There are also directorys for every translated language. In there are stored the final .po files. This .po files are translated/compiled into the needed .lmo files during compilation of LuCI. There are a lot of tools on the web handling .pot and .po files. I personally use poedit on my Xubuntu. To publish the final .po file use the standard contribution methods and guidelines of LuCI project on GitHub at https://github.com/openwrt/luci Does this help ? Christian Am 02.04.2015 um 10:28 schrieb Janne Cederberg: Greetings! TL;DR: Anyone able to write a short description on LuCI translation process and tools needed? LONGER EXPLANATION: I'm hoping to create a Finnish translation for the LuCI interface. However I can't find the instructions for the translation process as https://luci.subsignal.org/pootle/ has been down (502 Bad Gateway on Nginx) for several days. 1) Anyone involved with the https://luci.subsignal.org/pootle/ site to be able to aid in getting back up-n-running? 2) As an alternative to #1, is someone on the list able to describe the translation process? I'm suspected the translations to be use GNU Gettext based on the translation file extension .lmo (which I guessed to means LuCI mo) but when I renamed one of them to .mo and tried msgunfmt filename.mo it got the response that the file is not in GNU .mo format. I then took a look at the file in a hex editor and noticed it seems to contain HTML with nullbyte delimiters or something in that fashion. Anyone able help? Thank you in advance, Janne Cederberg Helsinki, Finland ___ 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] Translating LuCI? (https://luci.subsignal.org/pootle/ down)
Hi Janne, from my knowledge pottle is down since LuCI moved to GitHub. inside luci/modules/[package] and luci/applications/[application] on source tree you should find a po directory where translations are stored. Inside there is a templates/[file].pot This is the catalog (master) the translation based on. There are also directorys for every translated language. In there are stored the final .po files. This .po files are translated/compiled into the needed .lmo files during compilation of LuCI. There are a lot of tools on the web handling .pot and .po files. I personally use poedit on my Xubuntu. To publish the final .po file use the standard contribution methods and guidelines of LuCI project on GitHub at https://github.com/openwrt/luci Does this help ? Christian Am 02.04.2015 um 10:28 schrieb Janne Cederberg: Greetings! TL;DR: Anyone able to write a short description on LuCI translation process and tools needed? LONGER EXPLANATION: I'm hoping to create a Finnish translation for the LuCI interface. However I can't find the instructions for the translation process as https://luci.subsignal.org/pootle/ has been down (502 Bad Gateway on Nginx) for several days. 1) Anyone involved with the https://luci.subsignal.org/pootle/ site to be able to aid in getting back up-n-running? 2) As an alternative to #1, is someone on the list able to describe the translation process? I'm suspected the translations to be use GNU Gettext based on the translation file extension .lmo (which I guessed to means LuCI mo) but when I renamed one of them to .mo and tried msgunfmt filename.mo it got the response that the file is not in GNU .mo format. I then took a look at the file in a hex editor and noticed it seems to contain HTML with nullbyte delimiters or something in that fashion. Anyone able help? Thank you in advance, Janne Cederberg Helsinki, Finland ___ 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
[OpenWrt-Devel] [PATCH] samba36: add smb.conf.template to conffiles
User might have modified/extended template direct or by LuCI application. So do not overwrite on update/upgrade. Signed-off-by: Christian Schoenebeck christian.schoeneb...@gmail.com --- package/network/services/samba36/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/package/network/services/samba36/Makefile b/package/network/services/samba36/Makefile index d440495..b39f484 100644 --- a/package/network/services/samba36/Makefile +++ b/package/network/services/samba36/Makefile @@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=samba PKG_VERSION:=3.6.25 -PKG_RELEASE:=2 +PKG_RELEASE:=3 PKG_SOURCE_URL:=http://ftp.samba.org/pub/samba \ http://ftp.samba.org/pub/samba/stable @@ -125,6 +125,7 @@ MAKE_FLAGS += DYNEXP= PICFLAG= MODULES= define Package/samba36-server/conffiles /etc/config/samba +/etc/samba/smb.conf.template endef define Package/samba36-server/install -- 2.1.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
