Re: [OpenWrt-Devel] [PATCH 14/22] ARM: dts: add a devicetree for Raidsonic NAS IB-4220-B

2017-02-07 Thread Linus Walleij
On Sun, Feb 5, 2017 at 10:53 AM, Hans Ulli Kroll
 wrote:

> Hi Linus,
>
> please add right baudrate and partition scheme for NAS 4220
>
> Signed-off-by: Hans Ulli Kroll 

Thanks Hans! I folded this into the NAS 4220 device tree
and added your Signed-off-by to the patch.

Yours,
Linus Walleij
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] [PATCH 12/22 v3] ARM: dts: add top-level DT bindings for Cortina Gemini

2017-02-07 Thread Linus Walleij
This adds the top level SoC bindings for Cortina systems Gemini
platforms.

Cc: Janos Laube 
Cc: Paulius Zaleckas 
Cc: Hans Ulli Kroll 
Cc: Florian Fainelli 
Cc: devicet...@vger.kernel.org
Signed-off-by: Linus Walleij 
---
ChangeLog v2->v3:
- Fix soc bus node and references.
- Fix spelling of interrupt-controller
ChangeLog v1->v2:
- Rename required property "intcon" to "interrupt-controller"
- Elaborate a bit on the SoC origins
- Put the example DTS SoC nodes in a soc {} node
---
 Documentation/devicetree/bindings/arm/gemini.txt | 84 
 1 file changed, 84 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/arm/gemini.txt

diff --git a/Documentation/devicetree/bindings/arm/gemini.txt 
b/Documentation/devicetree/bindings/arm/gemini.txt
new file mode 100644
index ..c3e8430202ef
--- /dev/null
+++ b/Documentation/devicetree/bindings/arm/gemini.txt
@@ -0,0 +1,84 @@
+Cortina systems Gemini platforms
+
+The Gemini SoC is the project name for an ARMv4 FA525-based SoC originally
+produced by Storlink Semiconductor around 2005. The company was renamed
+later renamed Storm Semiconductor. The chip product name is Storlink SL3516.
+It was derived from earlier products from Storm named SL3316 (Centroid) and
+SL3512.
+
+Storm Semiconductor was acquired by Cortina Systems in 2008 and the SoC was
+produced and used for NAS and similar usecases. In 2014 Cortina Systems was
+in turn acquired by Inphi, who seem to have discontinued this product family.
+
+Required properties (in root node):
+   compatible = "cortina,gemini";
+
+Required nodes:
+
+- soc: the SoC should be represented by a simple bus encompassing all the
+  onchip devices, this is referred to as the soc bus node.
+
+- syscon: the soc bus node must have a system controller node pointing to the
+  global control registers, with the compatible string
+  "cortina,gemini-syscon", "syscon";
+
+- timer: the soc bus node must have a timer node pointing to the SoC timer
+  block, with the compatible string "cortina,gemini-timer"
+  See: clocksource/cortina,gemini-timer.txt
+
+- interrupt-controller: the sob bus node must have an interrupt controller
+  node pointing to the SoC interrupt controller block, with the compatible
+  string "cortina,gemini-interrupt-controller"
+  See interrupt-controller/cortina,gemini-interrupt-controller.txt
+
+Example:
+
+/ {
+   model = "Foo Gemini Machine";
+   compatible = "cortina,gemini";
+   #address-cells = <1>;
+   #size-cells = <1>;
+
+   memory {
+   device_type = "memory";
+   reg = <0x 0x800>;
+   };
+
+   soc {
+   #address-cells = <1>;
+   #size-cells = <1>;
+   ranges;
+   compatible = "simple-bus";
+   interrupt-parent = <>;
+
+   syscon: syscon@4000 {
+   compatible = "cortina,gemini-syscon", "syscon";
+   reg = <0x4000 0x1000>;
+   };
+
+   uart0: serial@4200 {
+   compatible = "ns16550a";
+   reg = <0x4200 0x100>;
+   clock-frequency = <4800>;
+   interrupts = <18 IRQ_TYPE_LEVEL_HIGH>;
+   reg-shift = <2>;
+   };
+
+   timer@4300 {
+   compatible = "cortina,gemini-timer";
+   reg = <0x4300 0x1000>;
+   interrupt-parent = <>;
+   interrupts = <14 IRQ_TYPE_EDGE_RISING>, /* Timer 1 */
+<15 IRQ_TYPE_EDGE_RISING>, /* Timer 2 */
+<16 IRQ_TYPE_EDGE_RISING>; /* Timer 3 */
+   syscon = <>;
+   };
+
+   intcon: interrupt-controller@4800 {
+   compatible = "cortina,gemini-interrupt-controller";
+   reg = <0x4800 0x1000>;
+   interrupt-controller;
+   #interrupt-cells = <2>;
+   };
+   };
+};
-- 
2.9.3
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] dnscrypt-proxy package missing in snapshot

2017-02-07 Thread Mangesh Bhamre
Hi Alex,

Snapshot don't have any reference of 'dnscrypt-proxy'. It is supported in
CC 15.05.1 and I am able to add 'dnscrypt-proxy' in list of packages to
include while building with CC Image-builder.

I scanned through all snapshot image-builder and no reference there. I run
following command to build - same works fine for CC 15.05.1

make image PROFILE=Default PACKAGES="-wpad-mini wpad luci curl
ca-certificates dnscrypt-proxy" FILES=/home/mangesh/files

Surely no typo there.

Regards,
Mangesh


On Tue, Feb 7, 2017 at 10:23 PM, Alexandru Ardelean 
wrote:

> Do you have a Package/dnscrypt-proxy/install rule ?
> Are you calling the BuildPackage rule ?
>
> Do you have Package/dnscrypt-proxy/description rule ?
>
> And check for typos if above stuff is checked.
>
> Thanks
> Alex
>
>
> On Tue, 7 Feb 2017 at 18:21, Mangesh Bhamre 
> wrote:
>
>> Hello OpenWRT team,
>>
>> I wish to bundle dnscrypt-proxy package using latest snapshot
>> Image-builder. I get below errors. Please recommend a fix or address it in
>> snapshot.
>>
>> Collected errors:
>>  * opkg_install_cmd: Cannot install package dnscrypt-proxy.
>> Makefile:146: recipe for target 'package_install' failed
>>
>> Regards,
>> Mangesh
>> ___
>> 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] dnscrypt-proxy package missing in snapshot

2017-02-07 Thread Alexandru Ardelean
Do you have a Package/dnscrypt-proxy/install rule ?
Are you calling the BuildPackage rule ?

Do you have Package/dnscrypt-proxy/description rule ?

And check for typos if above stuff is checked.

Thanks
Alex


On Tue, 7 Feb 2017 at 18:21, Mangesh Bhamre  wrote:

> Hello OpenWRT team,
>
> I wish to bundle dnscrypt-proxy package using latest snapshot
> Image-builder. I get below errors. Please recommend a fix or address it in
> snapshot.
>
> Collected errors:
>  * opkg_install_cmd: Cannot install package dnscrypt-proxy.
> Makefile:146: recipe for target 'package_install' failed
>
> Regards,
> Mangesh
> ___
> 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] dnscrypt-proxy package missing in snapshot

2017-02-07 Thread Mangesh Bhamre
Hello OpenWRT team,

I wish to bundle dnscrypt-proxy package using latest snapshot
Image-builder. I get below errors. Please recommend a fix or address it in
snapshot.

Collected errors:
 * opkg_install_cmd: Cannot install package dnscrypt-proxy.
Makefile:146: recipe for target 'package_install' failed

Regards,
Mangesh
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #20685: Weak Wi-Fi signal E1700 (MT7620A)

2017-02-07 Thread Tom Psyborg
Hi

Can anyone get a reference driver for MT7612E ?

On 7 February 2017 at 14:22, Qier LU  wrote:

> Hi Daniel,
>
> Thank you for your support!
>
> Here is Xiaomi mini using LEDE r2244
>
> root@lede:~# cat /proc/cpuinfo
> system type: MediaTek MT7620A ver:2 eco:6
> machine: Xiaomi MiWiFi Mini
> processor: 0
> cpu model: MIPS 24KEc V5.0
> BogoMIPS: 385.84
> wait instruction: yes
> microsecond timers: yes
> tlb_entries: 32
> extra interrupt vector: yes
> hardware watchpoint: yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc,
> 0x0ffb, 0x0ffb]
> isa: mips1 mips2 mips32r1 mips32r2
> ASEs implemented: mips16 dsp
> shadow register sets: 1
> kscratch registers: 0
> package: 0
> core: 0
> VCED exceptions: not available
> VCEI exceptions: not available
>
> root@lede:~# cat /proc/mtd
> dev:size   erasesize  name
> mtd0: 0003 1000 "u-boot"
> mtd1: 0001 1000 "u-boot-env"
> mtd2: 0001 1000 "factory"
> mtd3: 00f8 1000 "firmware"
> mtd4: 0013f660 1000 "kernel"
> mtd5: 00e409a0 1000 "rootfs"
> mtd6: 00c46000 1000 "rootfs_data"
> mtd7: 0001 1000 "crash"
> mtd8: 0001 1000 "reserved"
> mtd9: 0001 1000 "Bdata"
> root@lede:~# free
>  total   used   free sharedbuffers cached
> Mem:125744  34240  91504680   1900  11196
> -/+ buffers/cache:  21144 104600
> Swap:0  0  0
>
> On Tue, Feb 7, 2017 at 8:37 PM, Sam Charania 
> wrote:
>
>> E1700 using https://downloads.lede-project.org/releases/17.01.0-rc1/
>> targets/ramips/mt7620/lede-17.01.0-rc1-r3042-ec095b5-ramips-
>> mt7620-e1700-squashfs-factory.bin
>>
>> root@lede:~# cat /proc/cpuinfo
>> system type : MediaTek MT7620A ver:2 eco:6
>> machine : Linksys E1700
>> processor : 0
>> cpu model : MIPS 24KEc V5.0
>> BogoMIPS : 385.84
>> wait instruction : yes
>> microsecond timers : yes
>> tlb_entries : 32
>> extra interrupt vector : yes
>> hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc,
>> 0x0ffb, 0x0ffb]
>> isa : mips1 mips2 mips32r1 mips32r2
>> ASEs implemented : mips16 dsp
>> shadow register sets : 1
>> kscratch registers : 0
>> package : 0
>> core : 0
>> VCED exceptions : not available
>> VCEI exceptions : not available
>>
>>
>>
>>
>> root@lede:~# cat /proc/mtd
>> dev:size   erasesize  name
>> mtd0: 0003 1000 "u-boot"
>> mtd1: 0001 1000 "config"
>> mtd2: 0001 1000 "factory"
>> mtd3: 007b 1000 "firmware"
>> mtd4: 001281bd 1000 "kernel"
>> mtd5: 00687e43 1000 "rootfs"
>> mtd6: 00451000 1000 "rootfs_data"
>>
>> root@lede:~# free -m
>>  total   used   free sharedbuffers cached
>> Mem: 61112  21536  39576712   2200   7616
>> -/+ buffers/cache:  11720  49392
>> Swap:0  0  0
>> root@lede:~#
>>
>> Also note:
>>
>> [image: Inline image 1]
>>
>>
>> On Tue, Feb 7, 2017 at 11:23 AM, Daniel Golle 
>> wrote:
>>
>>> Hi Toan,
>>>
>>> I received some more funding on the kickstarter campaign which will
>>> allow me to add support for the external PA and external LNA stuff
>>> which will bring our GPL'ed driver to the same level of hardware
>>> support of the vendor's driver.
>>> In order to do that it'd be great if you can provide some help:
>>> Please flash your router to OpenWrt or LEDE and enter a console via
>>> SSH. Then see which flash partition holds the wifi eeprom:
>>> cat /proc/mtd
>>> There is supposed to be a 'factory' partition, e.g. /dev/mtd2 or
>>> something like that. Dump that partition to /tmp
>>> dd if=/dev/mtd2 of=/tmp/factory.bin
>>> Then logout and copy that file to your workstation:
>>> scp root@192.168.1.1:/tmp/factory.bin .
>>> (assuming the router has the IP 192.168.1.1)
>>> Then send that file (factory.bin) to me via email, so I can analyze
>>> it and see how we can auto-detect those features present on your
>>> device.
>>>
>>> I know this is some effort (flashing OpenWrt/LEDE and then reverting
>>> to the factory firmware, loosing your configuration on the way and all
>>> that) but I would be a great help and most likely improve the bad wifi
>>> signal situation on OpenWrt/LEDE within the next days.
>>>
>>>
>>> Cheers
>>>
>>>
>>> Daniel
>>>
>>>
>>> On Sun, Feb 05, 2017 at 02:19:10PM -0500, Toan Pham wrote:
>>> > Hi,
>>> >
>>> > I tested OpenWrt trunk version on the E1700 five months ago.  At that
>>> time,
>>> > openwrt (or the vendor) claimed that all of all ethernet ports are
>>> gibabit
>>> > ports (ref.  https://wiki.openwrt.org/toh/hwdata/linksys/linksys_e1700
>>> )
>>> > However, All four ports showed up as 100Mb, not Gbps ports, on Chaos
>>> Calmer
>>> > build.  Please let me know if you're experiencing the same thing, if
>>> so,
>>> > 

Re: [OpenWrt-Devel] [OpenWrt-Tickets] [OpenWrt] #20685: Weak Wi-Fi signal E1700 (MT7620A)

2017-02-07 Thread Daniel Golle
Hi Toan,

I received some more funding on the kickstarter campaign which will
allow me to add support for the external PA and external LNA stuff
which will bring our GPL'ed driver to the same level of hardware
support of the vendor's driver.
In order to do that it'd be great if you can provide some help:
Please flash your router to OpenWrt or LEDE and enter a console via
SSH. Then see which flash partition holds the wifi eeprom:
cat /proc/mtd
There is supposed to be a 'factory' partition, e.g. /dev/mtd2 or
something like that. Dump that partition to /tmp
dd if=/dev/mtd2 of=/tmp/factory.bin
Then logout and copy that file to your workstation:
scp root@192.168.1.1:/tmp/factory.bin .
(assuming the router has the IP 192.168.1.1)
Then send that file (factory.bin) to me via email, so I can analyze
it and see how we can auto-detect those features present on your
device.

I know this is some effort (flashing OpenWrt/LEDE and then reverting
to the factory firmware, loosing your configuration on the way and all
that) but I would be a great help and most likely improve the bad wifi
signal situation on OpenWrt/LEDE within the next days.


Cheers


Daniel


On Sun, Feb 05, 2017 at 02:19:10PM -0500, Toan Pham wrote:
> Hi,
> 
> I tested OpenWrt trunk version on the E1700 five months ago.  At that time,
> openwrt (or the vendor) claimed that all of all ethernet ports are gibabit
> ports (ref.  https://wiki.openwrt.org/toh/hwdata/linksys/linksys_e1700)
> However, All four ports showed up as 100Mb, not Gbps ports, on Chaos Calmer
> build.  Please let me know if you're experiencing the same thing, if so,
> should we update Openwrt product spec webpage to reflect the actual link
> speed?
> 
> I also found wifi on the e1700 hardware unbearable.  That's why I had to
> revert back to OEM firmware.
> 
> 
> 
> TP
> 
> On Sun, Feb 5, 2017 at 10:24 AM, Daniel Golle  wrote:
> 
> > Hi Sam,
> >
> > If this didn't get any better with on recent LEDE builds after commit
> > https://git.lede-project.org/?p=source.git;a=commit;h=
> > b367eef21dccbc5115778001955847ac3af47db8
> > it's most likely the issue is due to missing external PA init in the
> > rt2x00 driver. I'm currently fixing the most of the obvious problems
> > with rt2x00 on MT7620, but there are too many to get this done within
> > a weekend and a kickstarter bounty of EUR 200. External PA currently
> > isn't on the list of things I give priority to because none of the
> > boards I've seen are using this feature. Please retry with the current
> > LEDE build, if that doesn't fix the issue, let me know.
> >
> > I'll fix external PA if you are willing to help testing on the device
> > you own and obviously I'd appreciate if you throw something into my
> > hat for that tedious work on a not-very-well designed wifi chip and
> > a driver which has grown beyond reasonable size...
> >
> > https://www.kickstarter.com/projects/1327597961/better-
> > support-for-mt7620a-n-in-openwrt-lede/
> >
> >
> > Cheers
> >
> >
> > Daniel
> >
> > On Sun, Feb 05, 2017 at 03:07:02PM +, Sam Charania wrote:
> > > Hi,
> > >
> > > Did this ever get resolved?
> > >
> > > I would like to help resolve it so please advise ASAP.
> > >
> > > Thanks,
> > > Sam
> >
> > > ___
> > > 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 mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Wshaper package dependencies fail with snapshot image-builder

2017-02-07 Thread Dave Taht
wshaper was just retired in favor of sqm-scripts and qos-scripts.

See

https://www.bufferbloat.net/projects/cerowrt/wiki/Wondershaper_Must_Die/

for why.


On Tue, Feb 7, 2017 at 1:14 AM, Mangesh Bhamre  wrote:
> Hello OpenWRT team,
>
> I am trying to build ramips/7620 router firmware with wshaper and
> luci-app-wshaper package.  Build fails due to dependency error.
>
> --
>  * satisfy_dependencies_for: Cannot satisfy the following dependencies for
> luci-app-wshaper:
>  * wshaper *
>  * opkg_install_cmd: Cannot install package wshaper.
> Makefile:146: recipe for target 'package_install' failed
> -
>
> Please provide a fix.
>
>
> Regards,
> Mangesh Bhamre
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>



-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel