Re: [OpenWrt-Devel] [PATCH 1/2] ralink: add FireWRT power button
On 22/03/2015 00:31, Rafał Miłecki wrote: > On 21 March 2015 at 23:18, John Crispin wrote: >> >> >> On 21/03/2015 23:15, Rafał Miłecki wrote: >>> On 21 March 2015 at 06:06, wengbj wrote: Signed-off-by: wengbj --- target/linux/ramips/dts/FIREWRT.dts |5 + 1 file changed, 5 insertions(+) diff --git a/target/linux/ramips/dts/FIREWRT.dts b/target/linux/ramips/dts/FIREWRT.dts index 54f0e55..2b018e6 100644 --- a/target/linux/ramips/dts/FIREWRT.dts +++ b/target/linux/ramips/dts/FIREWRT.dts @@ -103,6 +103,11 @@ gpios = <&gpio0 18 1>; linux,code = <0x211>; }; + power { + label = "power"; + gpios = <&gpio0 23 1>; + linux,code = <116>; + }; >>> >>> Could you break this bad habit and use KEY_* instead of magic numbers? >>> Like a KEY_POWER. >>> >> >> sure but this is out of scope of this patch and needs to be done >> globally for all dts files in the ralink target. > > I don't mean changing any existing entry, just the one that was > suggested to be added. > > I think it's OK to add it in a correct & nice form? > i think that is incosistent to the rest of the code. people add code based on what is there. expecting them to magically know what you wish is not consistent tot waht is there. therefore the change needs to be made globally for all targets and not just for one. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] ptrace and pselect
Hi all, I installed `mosquitto` via `opkg` on BarrierBreaker, and I am getting: root@WEIO:~# mosquitto_pub -h test.mosquitto.org -t temp/random -m 40 mosquitto_pub: can't resolve symbol 'pselect' Then I wnated to see what's happening, and I installed `strace`, but I am getting: root@WEIO:~# strace mosquitto_pub -h test.mosquitto.org -t temp/random -m 40 strace: can't resolve symbol 'ptrace' in lib 'strace'. strace: test_ptrace_setoptions_for_all: unexpected exit status 1 root@WEIO:~# Any ideas? BR, Drasko ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Multiple OpenWrt devices collectively managed?
On 21 March 2015 at 15:49, Janne Cederberg wrote: > Greetings all! > Been searching around and found for example OpenWISP but thought I'd > ask the list as well: is there some opensource management software for > OpenWrt that could control a set of multiple OpenWrt AP's on the same > SSID; so basically controlling their channels based on channel use and > actively avoiding crowded/DOS'sed channels for example? > > Best regards, Janne Cederberg Hi Janne, what you are asking for is quite custom piece of software so there is not any open source project with functionality that you ask for. But it is not too difficult to build something like that, try building it yourself and share it with others, or hire somebody to do it for you. Cheers, Valent. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] ralink: add FireWRT power button
On 21 March 2015 at 23:18, John Crispin wrote: > > > On 21/03/2015 23:15, Rafał Miłecki wrote: >> On 21 March 2015 at 06:06, wengbj wrote: >>> Signed-off-by: wengbj >>> --- >>> target/linux/ramips/dts/FIREWRT.dts |5 + >>> 1 file changed, 5 insertions(+) >>> >>> diff --git a/target/linux/ramips/dts/FIREWRT.dts >>> b/target/linux/ramips/dts/FIREWRT.dts >>> index 54f0e55..2b018e6 100644 >>> --- a/target/linux/ramips/dts/FIREWRT.dts >>> +++ b/target/linux/ramips/dts/FIREWRT.dts >>> @@ -103,6 +103,11 @@ >>> gpios = <&gpio0 18 1>; >>> linux,code = <0x211>; >>> }; >>> + power { >>> + label = "power"; >>> + gpios = <&gpio0 23 1>; >>> + linux,code = <116>; >>> + }; >> >> Could you break this bad habit and use KEY_* instead of magic numbers? >> Like a KEY_POWER. >> > > sure but this is out of scope of this patch and needs to be done > globally for all dts files in the ralink target. I don't mean changing any existing entry, just the one that was suggested to be added. I think it's OK to add it in a correct & nice form? -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] ralink: add FireWRT power button
On 21/03/2015 23:15, Rafał Miłecki wrote: > On 21 March 2015 at 06:06, wengbj wrote: >> Signed-off-by: wengbj >> --- >> target/linux/ramips/dts/FIREWRT.dts |5 + >> 1 file changed, 5 insertions(+) >> >> diff --git a/target/linux/ramips/dts/FIREWRT.dts >> b/target/linux/ramips/dts/FIREWRT.dts >> index 54f0e55..2b018e6 100644 >> --- a/target/linux/ramips/dts/FIREWRT.dts >> +++ b/target/linux/ramips/dts/FIREWRT.dts >> @@ -103,6 +103,11 @@ >> gpios = <&gpio0 18 1>; >> linux,code = <0x211>; >> }; >> + power { >> + label = "power"; >> + gpios = <&gpio0 23 1>; >> + linux,code = <116>; >> + }; > > Could you break this bad habit and use KEY_* instead of magic numbers? > Like a KEY_POWER. > sure but this is out of scope of this patch and needs to be done globally for all dts files in the ralink target. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/2] ralink: add FireWRT power button
On 21 March 2015 at 06:06, wengbj wrote: > Signed-off-by: wengbj > --- > target/linux/ramips/dts/FIREWRT.dts |5 + > 1 file changed, 5 insertions(+) > > diff --git a/target/linux/ramips/dts/FIREWRT.dts > b/target/linux/ramips/dts/FIREWRT.dts > index 54f0e55..2b018e6 100644 > --- a/target/linux/ramips/dts/FIREWRT.dts > +++ b/target/linux/ramips/dts/FIREWRT.dts > @@ -103,6 +103,11 @@ > gpios = <&gpio0 18 1>; > linux,code = <0x211>; > }; > + power { > + label = "power"; > + gpios = <&gpio0 23 1>; > + linux,code = <116>; > + }; Could you break this bad habit and use KEY_* instead of magic numbers? Like a KEY_POWER. -- Rafał ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ar71xx: add support for the UniFi AP Outdoor Plus
2015-03-21 12:16 GMT+03:00 Stefan Rompf : > -The RF filter is controlled by the GPIO pins on the AR928x wifi chip via some > kind of serial protocol. > -The functions responsible for the filter are ath_hal_hsr_init(), called once > on initialisation, ath_hal_hsr_disable() and ath_hal_hsr_enable() on channel > change. There is an ath_hal_hsr_get_lock_status() that does not seem to be > used. > -There seems to be no filter tuning after it has been setup on channel change. > Wow, impressive. > Reverse engineering this unreadable MIPS assembly mess will take some time... > anyone willing to help? What kind of help do you need? > Does it make sense to open a ticket to track the issue > or is this mailing list ok? > -- Sergey ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 2/2] ralink: MT7621 add i2c controller driver on linux kernel 3.18
Hi, please see comments inline. also please the checkpatch.pl script on this patch before sending a V2 John On 21/03/2015 06:06, wengbj wrote: > ralink i2c driver is not working on MT7621 platform. Porting a new drivers > from MTK's source code. > > Signed-off-by: wengbj > --- > .../0111-i2c-MIPS-add-mt7621-I2C-driver.patch | 390 > > 1 file changed, 390 insertions(+) > create mode 100755 > target/linux/ramips/patches-3.18/0111-i2c-MIPS-add-mt7621-I2C-driver.patch > > diff --git > a/target/linux/ramips/patches-3.18/0111-i2c-MIPS-add-mt7621-I2C-driver.patch > b/target/linux/ramips/patches-3.18/0111-i2c-MIPS-add-mt7621-I2C-driver.patch > new file mode 100755 > index 000..ec897ee > --- /dev/null > +++ > b/target/linux/ramips/patches-3.18/0111-i2c-MIPS-add-mt7621-I2C-driver.patch > @@ -0,0 +1,390 @@ > +Index: linux-3.18.9/drivers/i2c/busses/Kconfig > +=== > +--- linux-3.18.9.orig/drivers/i2c/busses/Kconfig 2015-03-21 > 11:47:27.387652879 +0800 > linux-3.18.9/drivers/i2c/busses/Kconfig 2015-03-21 11:47:27.587652870 > +0800 > +@@ -714,6 +714,10 @@ > + tristate "Ralink I2C Controller" > + select OF_I2C > + > ++config I2C_MT7621 > ++tristate "Mt7621 I2C Controller" > ++select OF_I2C > ++ > + config HAVE_S3C2410_I2C > + bool > + help > +Index: linux-3.18.9/drivers/i2c/busses/Makefile > +=== > +--- linux-3.18.9.orig/drivers/i2c/busses/Makefile2015-03-21 > 11:47:27.387652879 +0800 > linux-3.18.9/drivers/i2c/busses/Makefile 2015-03-21 11:47:27.587652870 > +0800 > +@@ -67,6 +67,7 @@ > + obj-$(CONFIG_I2C_PXA) += i2c-pxa.o > + obj-$(CONFIG_I2C_PXA_PCI) += i2c-pxa-pci.o > + obj-$(CONFIG_I2C_RALINK)+= i2c-ralink.o > ++obj-$(CONFIG_I2C_MT7621)+= i2c-mt7621.o > + obj-$(CONFIG_I2C_QUP) += i2c-qup.o > + obj-$(CONFIG_I2C_RIIC) += i2c-riic.o > + obj-$(CONFIG_I2C_RK3X) += i2c-rk3x.o > +Index: linux-3.18.9/drivers/i2c/busses/i2c-mt7621.c > +=== > +--- /dev/null1970-01-01 00:00:00.0 + > linux-3.18.9/drivers/i2c/busses/i2c-mt7621.c 2015-03-21 > 11:48:58.883648615 +0800 > +@@ -0,0 +1,358 @@ > ++/* > ++ * drivers/i2c/busses/i2c-mt7621.c > ++ * > ++ * Copyright (C) 2013 Steven Liu > ++ * > ++ * Improve driver for i2cdetect from i2c-tools to detect i2c devices on the > bus. > ++ * (C) 2014 Sittisak > ++ * > ++ * This software is licensed under the terms of the GNU General Public > ++ * License version 2, as published by the Free Software Foundation, and > ++ * may be copied, distributed, and modified under those terms. > ++ * > ++ * 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 > ++#include > ++#include > ++#include > ++#include > ++#include > ++#include > ++#include > ++#include > ++#include > ++#include > ++#include > ++ > ++#include > ++ > ++#define REG_CONFIG_REG 0x00 > ++#define REG_CLKDIV_REG 0x04 > ++#define REG_DEVADDR_REG 0x08 > ++#define REG_ADDR_REG 0x0C > ++#define REG_DATAOUT_REG 0x10 > ++#define REG_DATAIN_REG 0x14 > ++#define REG_STATUS_REG 0x18 > ++#define REG_STARTXFR_REG 0x1C > ++#define REG_BYTECNT_REG 0x20 > ++#define REG_SM0_IS_AUTOMODE 0x28 > ++#define REG_SM0CTL0 0x40 > ++ > ++ > ++#define I2C_STARTERR 0x10 > ++#define I2C_ACKERR 0x08 > ++#define I2C_DATARDY 0x04 > ++#define I2C_SDOEMPTY 0x02 > ++#define I2C_BUSY 0x01 > ++ > ++/* I2C_CFG register bit field */ > ++#define I2C_CFG_ADDRLEN_8(7<<5) /* 8 bits */ > ++#define I2C_CFG_DEVADLEN_7 (6<<2) > ++#define I2C_CFG_ADDRDIS (1<<1) > ++#define I2C_CFG_DEVADDIS (1<<0) please use the BIT() macro instead of x< ++ > ++#define I2C_CFG_DEFAULT (I2C_CFG_ADDRLEN_8 | \ > ++I2C_CFG_DEVADLEN_7 | \ > ++I2C_CFG_ADDRDIS) > ++ > ++#define I2C_RETRY0x1000 > ++ > ++#define CLKDIV_VALUE 333 > ++#define i2c_busy_loop(CLKDIV_VALUE*30) > ++ > ++#define READ_CMD 0x01 > ++#define WRITE_CMD0x00 > ++#define READ_BLOCK 16 > ++ > ++#define I2C
Re: [OpenWrt-Devel] [PATCH 1/2] ralink: add FireWRT power button
Hi On 21/03/2015 06:06, wengbj wrote: > Signed-off-by: wengbj > --- > target/linux/ramips/dts/FIREWRT.dts |5 + > 1 file changed, 5 insertions(+) > > diff --git a/target/linux/ramips/dts/FIREWRT.dts > b/target/linux/ramips/dts/FIREWRT.dts > index 54f0e55..2b018e6 100644 > --- a/target/linux/ramips/dts/FIREWRT.dts > +++ b/target/linux/ramips/dts/FIREWRT.dts > @@ -103,6 +103,11 @@ > gpios = <&gpio0 18 1>; > linux,code = <0x211>; > }; > + power { > + label = "power"; > + gpios = <&gpio0 23 1>; > + linux,code = <116>; > + }; what kind of power button is this ? does the board have a gpio to toggle the supply voltage ? if so please consider also adding a "gpio-poweroff" node. John > }; > > pinctrl { > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Why OpenWrt sucks?
On 10 March 2015 at 21:26, Gergely Kiss wrote: > Hi Valent, > > first of all, I strongly disagree with people claiming that OpenWrt sucks > because it doesn't. For me it rather looks like a well-maintained, rapidly > improving project with a great number of actively supported hardware and > quite a few people contributing to > Do you think OpenWrt sucks? Then stop complaining and do something to make > it better. It's that simple. > > Cheers, > Gergely Hi Gergely, thanks for your reply and for your contribution to OpenWrt. But I have to ask - have you read my message apart from headline? If you have read it you will see that I'm defending OpenWrt and I definitely don't think it sucks! I contribute to it everyday, but not (yet) as a developer but as advanced user, forum and wiki contributor and have organized multiple workshops all accross Croatia, Serbia and Macedonia to get people to use OpenWrt. Cheers, Valent. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Interesting OpenWrt and Atheros job listing
Hi, just stumbled upon this interesting job listing that is appropriate for people on this list: https://www.elance.com/j/outdoor-wireless-open-wrt-atheros-development/69183838/?backurl=aHR0cHM6Ly93d3cuZWxhbmNlLmNvbS9yL2pvYnMvcS1vcGVud3J0Lw== Hope somebody of you guys gets this and also that we get open source TDMA support, that would be awesome! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Multiple OpenWrt devices collectively managed?
Greetings all! Been searching around and found for example OpenWISP but thought I'd ask the list as well: is there some opensource management software for OpenWrt that could control a set of multiple OpenWrt AP's on the same SSID; so basically controlling their channels based on channel use and actively avoiding crowded/DOS'sed channels for example? Best regards, Janne Cederberg ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OpenWrt-Commits] r44899 - trunk/package/network/config/netifd
The culprit is the last netifd changes: I have built r44915 otherwise updated, but with the last two commits removed from netifd, and ipv6 routing works again. So, the breakage is due to netifd. * after "add prelocal table to manipulate locally destinated"/3eea8576d48d9b20cc1c6b46f54c7345a39d13aa ipv6 still works * after "add missing argument for ipv4 routes"/2fb3d0e9205e2a4cea38062caefd7251f562866d there are no ipv6 routes for the 6in4 tunnel. It seems to me that a seventh parameter "table" might be needed for proto_add_ipv6_route in 6in4, but I didn't figure out how to change the 6in4 tunnel script. I tried ading an empty table parameter to three calls to proto_add_ipv6_route, but that didn't work. On 20.3.2015 22:15, Arjen de Korte wrote: I'm running trunk on a Netgear WNDR4300. On this router, a Hurricane Electric tunnel is configured to provide IPv6 access for the LAN. All was fine until this morning. Bisecting leads to the below commit to break IPv6 routing (IPv4 was still fine). Could it be that 6in4 needs to be modified after this commit? Citeren openwrt-comm...@openwrt.org: Author: cyrus Date: 2015-03-20 08:50:45 +0100 (Fri, 20 Mar 2015) New Revision: 44899 Modified: trunk/package/network/config/netifd/Makefile Log: netifd: device update fixes, improvements in policy routing ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ar71xx: add support for the UniFi AP Outdoor Plus
Hi Sergey, > You should be a wizard to reveal hw protocol without touching hw :) I cannot say 'Mischief managed!' by now, but it's slowly making progress ;-) > Unlikely that iwconfig changes something directly, I would bet on the > driver. Indeed. So far -The RF filter is controlled by the GPIO pins on the AR928x wifi chip via some kind of serial protocol. -The functions responsible for the filter are ath_hal_hsr_init(), called once on initialisation, ath_hal_hsr_disable() and ath_hal_hsr_enable() on channel change. There is an ath_hal_hsr_get_lock_status() that does not seem to be used. -There seems to be no filter tuning after it has been setup on channel change. Reverse engineering this unreadable MIPS assembly mess will take some time... anyone willing to help? Does it make sense to open a ticket to track the issue or is this mailing list ok? Stefan ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] directory completeness problems
> "John" == John Crispin writes: John> On 10/12/2014 01:37, Russell Senior wrote: >> I am also wondering whether or not OpenWrt should be using ubifs >> (like for the generic NAND subtarget) for the Mikrotik subtarget. >> >> Thoughts? John> yes, i have a mikrotik board on my desk already for this purpose. Ping. Current trunk is kernel panic'ing on this (mikrotik rb493g) hardware: http://pastebin.com/xX8vVGkY Getting off yaffs might help? I'm suffering a different ipv6 kernel panic (a few times a day) on the r43530 image I'm using now, which has been fixed, but the pastebin panic and the yaffs bug is impeding my updates. Any progress? -- Russell Senior, President russ...@personaltelco.net ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel