[OpenWrt-Devel] lantiq voip foo
Hi, with the vdsl now working as well as the adsl i would also like to try to bring the voip/asterisk support up to scratch. i am a n00b at asterisk and have never used the can_lantiq driver. any volunteers for this ? any one successfully used chan_lantiq ? ideally we could make a sample config file that will allow users to simply setup the voip of the usual suspects such as sipgate, ekiga, bt, dt, kpn ... Having an easy way to set this up would make units such as the a803 or the 7519 much more attractive. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] lantiq voip foo
I have only two ARV4518pw but they are enough to make tests, and in a spanish forum surely there will be a lot of people very pleased to help you. First of all i need to learn a bit of asterisk with AA in order to help you better. Thanks in advance: Pepe 2014-04-10 9:23 GMT+02:00, John Crispin : > Hi, > > with the vdsl now working as well as the adsl i would also like to try > to bring the voip/asterisk support up to scratch. > > i am a n00b at asterisk and have never used the can_lantiq driver. > > any volunteers for this ? > > any one successfully used chan_lantiq ? > > ideally we could make a sample config file that will allow users to > simply setup the voip of the usual suspects such as sipgate, ekiga, > bt, dt, kpn ... > > Having an easy way to set this up would make units such as the a803 or > the 7519 much more attractive. > > > John > ___ > 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 1/4] [ramips] Add wmac clock for rt2880
Signed-off-by: Roman Yeryomin
---
.../patches-3.10/0218-rt2880-add-wmac-clock.patch | 21 +
1 file changed, 21 insertions(+)
create mode 100644
target/linux/ramips/patches-3.10/0218-rt2880-add-wmac-clock.patch
diff --git a/target/linux/ramips/patches-3.10/0218-rt2880-add-wmac-clock.patch
b/target/linux/ramips/patches-3.10/0218-rt2880-add-wmac-clock.patch
new file mode 100644
index 000..20b186b
--- /dev/null
+++ b/target/linux/ramips/patches-3.10/0218-rt2880-add-wmac-clock.patch
@@ -0,0 +1,21 @@
+Index: linux-3.10.34/arch/mips/ralink/rt288x.c
+===
+--- linux-3.10.34.orig/arch/mips/ralink/rt288x.c
linux-3.10.34/arch/mips/ralink/rt288x.c
+@@ -52,7 +52,7 @@ static void rt288x_wdt_reset(void)
+
+ void __init ralink_clk_init(void)
+ {
+- unsigned long cpu_rate;
++ unsigned long cpu_rate, wmac_rate = 4000;
+ u32 t = rt_sysc_r32(SYSC_REG_SYSTEM_CONFIG);
+ t = ((t >> SYSTEM_CONFIG_CPUCLK_SHIFT) & SYSTEM_CONFIG_CPUCLK_MASK);
+
+@@ -78,6 +78,7 @@ void __init ralink_clk_init(void)
+ ralink_clk_add("300500.uart", cpu_rate / 2);
+ ralink_clk_add("300c00.uartlite", cpu_rate / 2);
+ ralink_clk_add("40.ethernet", cpu_rate / 2);
++ ralink_clk_add("48.wmac", wmac_rate);
+ }
+
+ void __init ralink_of_remap(void)
--
1.8.3.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 3/4] [ramips] rt2880 DT fixes
* add pinctrl
* fix ethernet port
* make wifi available by default
Signed-off-by: Roman Yeryomin
---
target/linux/ramips/dts/rt2880.dtsi | 38 +++--
1 file changed, 36 insertions(+), 2 deletions(-)
diff --git a/target/linux/ramips/dts/rt2880.dtsi
b/target/linux/ramips/dts/rt2880.dtsi
index b513148..646cb6a 100644
--- a/target/linux/ramips/dts/rt2880.dtsi
+++ b/target/linux/ramips/dts/rt2880.dtsi
@@ -121,15 +121,51 @@
};
};
+ pinctrl {
+ compatible = "ralink,rt2880-pinmux";
+
+ pinctrl-names = "default";
+ pinctrl-0 = <&state_default>;
+
+ state_default: pinctrl0 {
+ sdram {
+ ralink,group = "sdram";
+ ralink,function = "sdram";
+ };
+ };
+
+ spi_pins: spi {
+ spi {
+ ralink,group = "spi";
+ ralink,function = "spi";
+ };
+ };
+
+ uartlite_pins: uartlite {
+ uart {
+ ralink,group = "uartlite";
+ ralink,function = "uartlite";
+ };
+ };
+ };
+
ethernet@40 {
compatible = "ralink,rt2880-eth";
reg = <0x0040 1>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+
interrupt-parent = <&cpuintc>;
interrupts = <5>;
status = "disabled";
+ port@0 {
+ compatible = "ralink,rt2880-port", "ralink,eth-port";
+ reg = <0>;
+ };
+
mdio-bus {
#address-cells = <1>;
#size-cells = <0>;
@@ -146,8 +182,6 @@
interrupts = <6>;
ralink,eeprom = "soc_wmac.eeprom";
-
- status = "disabled";
};
};
--
1.8.3.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/4] [ramips] Fix pinmux-rt2880
The last arg to FUNC() is count, not last pin.
Signed-off-by: Roman Yeryomin
---
target/linux/ramips/patches-3.10/0217-pinmux-rt2880.patch | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/target/linux/ramips/patches-3.10/0217-pinmux-rt2880.patch
b/target/linux/ramips/patches-3.10/0217-pinmux-rt2880.patch
index 3cadce7..6821da1 100644
--- a/target/linux/ramips/patches-3.10/0217-pinmux-rt2880.patch
+++ b/target/linux/ramips/patches-3.10/0217-pinmux-rt2880.patch
@@ -46,12 +46,12 @@
- .gpio_last = 71,
- }, {0}
+static struct rt2880_pmx_func i2c_func[] = { FUNC("i2c", 0, 1, 2) };
-+static struct rt2880_pmx_func spi_func[] = { FUNC("spi", 0, 3, 6) };
-+static struct rt2880_pmx_func uartlite_func[] = { FUNC("uartlite", 0, 7, 14)
};
-+static struct rt2880_pmx_func jtag_func[] = { FUNC("jtag", 0, 17, 21) };
-+static struct rt2880_pmx_func mdio_func[] = { FUNC("mdio", 0, 22, 23) };
-+static struct rt2880_pmx_func sdram_func[] = { FUNC("sdram", 0, 24, 39) };
-+static struct rt2880_pmx_func pci_func[] = { FUNC("pci", 0, 40, 71) };
++static struct rt2880_pmx_func spi_func[] = { FUNC("spi", 0, 3, 4) };
++static struct rt2880_pmx_func uartlite_func[] = { FUNC("uartlite", 0, 7, 8) };
++static struct rt2880_pmx_func jtag_func[] = { FUNC("jtag", 0, 17, 5) };
++static struct rt2880_pmx_func mdio_func[] = { FUNC("mdio", 0, 22, 2) };
++static struct rt2880_pmx_func sdram_func[] = { FUNC("sdram", 0, 24, 16) };
++static struct rt2880_pmx_func pci_func[] = { FUNC("pci", 0, 40, 32) };
+
+static struct rt2880_pmx_group rt2880_pinmux_data_act[] = {
+GRP("i2c", i2c_func, 1, RT2880_GPIO_MODE_I2C),
--
1.8.3.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 4/4] [ramips] Fix Asus rt-n15 board support
* gpio leds and buttons
* ethernet
Signed-off-by: Roman Yeryomin
---
target/linux/ramips/dts/RT-N15.dts | 26 ++
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/target/linux/ramips/dts/RT-N15.dts
b/target/linux/ramips/dts/RT-N15.dts
index 77e640f..8936520 100644
--- a/target/linux/ramips/dts/RT-N15.dts
+++ b/target/linux/ramips/dts/RT-N15.dts
@@ -9,18 +9,20 @@
model = "Asus RT-N15";
palmbus@30 {
- sysc@0 {
- ralink,pinmux = "uartlite";
- ralink,gpiomux = "i2c";
- ralink,uartmux = "gpio";
- ralink,wdtmux = <1>;
- };
-
gpio0: gpio@600 {
status = "okay";
};
};
+ pinctrl {
+ state_default: pinctrl0 {
+ gpio {
+ ralink,group = "i2c", "uartlite", "mdio";
+ ralink,function = "gpio";
+ };
+ };
+ };
+
cfi@1f00 {
compatible = "cfi-flash";
reg = <0x1f00 0x80>;
@@ -46,7 +48,7 @@
read-only;
};
partition@5 {
- label = "linux";
+ label = "firmware";
reg = <0x5 0x3b>;
};
};
@@ -58,6 +60,14 @@
port@0 {
ralink,fixed-link = <1000 1 1 1>;
};
+
+ mdio-bus {
+ status = "okay";
+ phy0: ethernet-phy@0 {
+ phy-mode = "mii";
+ reg = <0>;
+ };
+ };
};
rtl8366s {
--
1.8.3.2
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [ramips] Don't try to generate whr-g300n image if it's going to be more than 4M
And this one too. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] OpenSSL: update to 1.0.1g
On April 8, 2014 at 3:57:57 AM, Michel Stempin (michel.stem...@wanadoo.fr) wrote: > Le 08/04/2014 08:37, Steven Barth a écrit : > > Applied, thanks. Will probably take care of AA later today. > > Does it mean that ther ewill be a new AA binary release, or just the sources > will be updated? And will it have to be a new whole-image release or is there any way of shipping upgraded packages? Right at the current moment, OpenWrt AA has a version-numbering problem. A natural name for a hot-fix release for openssl would be 12.09.1, but there is already something else planned to be called "12.09.1" and I believe some users flashing AA-head over 12.09 would require network reconfiguration. It would be *really* *nice* if there was a "no reconfiguration required" hotfix for openssl. We could build an official patch package. For most router users, libssl.so is in squashfs, though. An upgraded libssl will eat a second 300k on ar71xx, and the 300k is from the uncompressed user storage area. How close to the edge of running out of space are people running AA? I started looked at using ELF hackery to get around creating a full copy. *If* you think patching tls1_process_heartbeat and dtls1_process_heartbeat is sufficient--and that is a significant "if"--it's possible to place a stub libssl.so on the /overlay filesystem which satisfies most of its symbol dependencies by DT_NEEDing /rom/usr/lib/libssl.so. For better or worse, /rom/usr/lib/libssl.so is linked -Bsymbolic. This means that users of tls1_process_heartbeat internal to the library do not go through the symbol table; they branch directly to the function. So it is not enough to just fix the symbol resolution. We need to include patched versions of all the internal callers...and then all *their* internal callers. It looks like we'd have to include a copy of at least ssl3_read_bytes, since that does a local "bal" call to tls1_process_heartbeat. But then what about callers of ssl3_read_bytes? It doesn't look like there are any direct calls. Then ssl3_read_bytes is only called via function pointer. So where does that pointer come from? The pointers appear to be in the writable .data section, where we could patch them at shim load time. That's good. Unfortunately, at the C source file level those references are specified in static-visibility data, such as several in t1_meth.o. So I don't know if there is any way of writing a shim in (relatively) pure C; there would have to be architecture-specific offset-based word patching, and I don't know if it's worth it for OpenWrt. There are more space-efficient ways of patching libssl via an /overlay shim on top of a /rom libssl. On MIPS, the single text page with a reference to tls1_process_heartbeat could have write-protection turned off and the opcode overwritten. But that becomes very architecture-specific, or somebody has to write a portable SVR4 ELF .text patcher system. Let us hope we do not have to be patching like that very often. If it makes anybody feel better, vendors of other network devices should be discussing something like this decision now too. Most vendors don't have to worry about user programs or a proliferation of ROM images, but some do... -- Jay Strong authentication just proves which chump is in front of the keyboard. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] target rb532 / routerboard
On 9 April 2014 15:55, Bastian Bittorf wrote: > * Imre Kaloz [09.04.2014 14:53]: >> Because no one tested it since the kernel has been upgraded, and we don't >> have a board to do anymore ;) > > ok, will do some more tests and send a patch with re-enables it. > (board will run in our testnet) > I would even use it if it really works... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] OpenSSL: update to 1.0.1g - heartbleed bug
Heartbleed - libopenssl AA binary feed update we updated the AA release. the files libopenssl_1.0.1e-1_*.ipk have been replaced with libopenssl_1.0.1g-1_*.ipk and the Packages index was updated. If you use openssl on your unit you need to run : # opkg update # opkg upgrade libopenssl In order to ensure that all affected services are using the updated OpenSSL library it is recommended to reboot the device after applying the upgrade. To find out more about the bug go to - http://heartbleed.com/ Note that default OpenWrt installations are not vulnerable to the particular bug, neither the builtin SSH server nor the optional LuCI SSL support rely on OpenSSL for cryptography. The OpenSSL library is not installed within the stock images available on the download server. This is not a lightweight bug. Please take it serious and check your unit. OpenWrt Developers ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] target rb532 / routerboard
2014-04-10 13:39 GMT-07:00 Roman Yeryomin : > On 9 April 2014 15:55, Bastian Bittorf wrote: >> * Imre Kaloz [09.04.2014 14:53]: >>> Because no one tested it since the kernel has been upgraded, and we don't >>> have a board to do anymore ;) >> >> ok, will do some more tests and send a patch with re-enables it. >> (board will run in our testnet) >> > > I would even use it if it really works... What exactly does that mean? If you have access to HW, please do test and submit patches against it. Thanks! -- Florian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] target rb532 / routerboard
On 11 April 2014 00:19, Florian Fainelli wrote: > 2014-04-10 13:39 GMT-07:00 Roman Yeryomin : >> On 9 April 2014 15:55, Bastian Bittorf wrote: >>> * Imre Kaloz [09.04.2014 14:53]: Because no one tested it since the kernel has been upgraded, and we don't have a board to do anymore ;) >>> >>> ok, will do some more tests and send a patch with re-enables it. >>> (board will run in our testnet) >>> >> >> I would even use it if it really works... > > What exactly does that mean? If you have access to HW, please do test > and submit patches against it. Thanks! > Bastian said he will. I can help testing for sure. I can try what we have now a bit later but not sure I will have time to fix it right now if it's broken. Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] SNIProxy in Openwrt
Hi, I am trying to compile SNI Proxy in OpenWRT, https://github.com/dlundquist/sniproxy I have successfully done this before for ar71xx platform but I am trying to now do it with ramips. My notes from the first time aren't up to scratch so I am not sure if a) changes to the SNIproxy code are effecting this or b) I have forgotten what I did. I think this would be a good little package to have available anyway so I am looking for assistance to get this compiled and rolled into the feeds system. SNIProxy is great for countries like Australia to get Netflix and other services and could be of benefit in the embedded space. It seems to run quite well on my ar71xx chipset. So here are my current problems limiting me from getting this done. 1: This package uses autoconf and I was struggling to produce a Makefile that works so I am now just attempting to cross compile it using the toolchain. Need help to build Makefile 2: Seems to require libev4. I cannot see if this package is available for OpenWRT, I tried to cross compile it manually but I am getting an error "opcode not supported on this processor: mips1" The ar71xx is mips but maybe it does support opcode. I will test recompiling for ar71xx later today and see if I have the same problems. 3: When I get to the next step there are some rpl_malloc propblems that can be fixed through the code quiet easily but I will have to work this out again. I would be interested for any feedback and assistance in getting this happening. cheers pjfrase ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] OpenSSL: update to 1.0.1g - heartbleed bug
Hi John (& co), Thanks a bucket for this :-) Pete. On 11/04/14 06:45, John Crispin wrote: Heartbleed - libopenssl AA binary feed update we updated the AA release. the files libopenssl_1.0.1e-1_*.ipk have been replaced with libopenssl_1.0.1g-1_*.ipk and the Packages index was updated. If you use openssl on your unit you need to run : # opkg update # opkg upgrade libopenssl In order to ensure that all affected services are using the updated OpenSSL library it is recommended to reboot the device after applying the upgrade. To find out more about the bug go to - http://heartbleed.com/ Note that default OpenWrt installations are not vulnerable to the particular bug, neither the builtin SSH server nor the optional LuCI SSL support rely on OpenSSL for cryptography. The OpenSSL library is not installed within the stock images available on the download server. This is not a lightweight bug. Please take it serious and check your unit. OpenWrt Developers ___ 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
