Re: [OpenWrt-Devel] pivot_overlay doesn't work anymore
On 10 January 2015 at 12:54, Gianluca Anzolin gianl...@sottospazio.it wrote: I just tried to install the latest CC trunk (r43901) on my netgear wndr4300, a router with NAND flash on that uses UBIFS. I noticed that I cannot use an external /overlay anymore: while I can mount the usb drive on any mountpoint, the '/overlay' target in /etc/config/fstab is ignored and the rootfs is never switched to the new device. The funny fact is that on another different router this doesn't happen: that router however doesn't rely on UBIFS since it uses NOR flash. So I tried to revert the latest change relevant to fstools (git-svn-id: svn://svn.openwrt.org/openwrt/trunk@43868 3c298f89-4303-0410-b956-a3cf2f4a3e73) and pivot_overlay began to work again. I understand that commit is only an upgrade to the latest HEAD of fstools: before starting to bisect I thought someone working on the code could have an idea on what's really happening. I'll try to bisect this evening if needed. I guess I broke something, but I can't really say what and why. It works for me, but obviously there are mny different possible setups. You can see the list of fstools commits using following URL: http://nbd.name/gitweb.cgi?p=fstools.git;a=shortlog I'll need you to bisect them by changing PKG_SOURCE_VERSION in the package/system/fstools/Makefile What do we know so far: BAD 6a448a100c7ce8b8b85f262ba1258e54363da9cc ??? 1e4579556ca54bdf9ccb86933c64bc6094c04e9a ??? 0bc9aa72941d2e361e77b5ff7c4a742e1de98cc2 ??? a5076ad9c92895c54eb384b224e7af1a914f1fd9 ??? 9847f4e2769d0d808a846724f8dd74b83280fdd8 ??? 1a57eb9b7cc5e772d1090a23c51fdd4a01ec5df0 ??? 25a65a42bb0b2eb0b6c89b1803c703aadae8196b ??? 35056038c02a7cbd18b57a5f46a373d564c69693 GOOD 83cf8896a598fb9fc58da0a9bb4f137695f78853 So please open package/system/fstools/Makefile and change PKG_SOURCE_VERSION to something from the middle of above list. You can start e.g. from 9847f4e2769d0d808a846724f8dd74b83280fdd8. After you change PKG_SOURCE_VERSION to 9847f4e2769d0d808a846724f8dd74b83280fdd8, recompile OpenWrt, install it and try. Using above way, please find the first bad commit. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] JSON data interchange format for networks
Hi everybody, in the past 2months some people have been working on a simple idea, which would bring a lot of benefits to many peopleand that for some strange reason has not been implemented yet, probably because the effort is more human than technical, as many different people have to work together and come to agreements. But here's the idea: Immagine you could export adevice configuration in JSON format and reimport that somewhere else,like monitoring software, node database, or whatever you need. Something like this: https://github.com/interop-dev/json-for-networks/blob/master/examples/device-configuration.json Immagine you could extract monitoring data with a simple JSONthat has a similar structure to the device configuration, that would enable different software to play well with one another, instead of building silos that don't talk to each other. Something like this: https://github.com/interop-dev/json-for-networks/blob/master/examples/monitoring-data.json Immagine the olsr json info plugin, or the json output by batman, but instead of being all different,they shared a common structure, and differed only in the key/value pairs that are specific to their protocol. That would be easier to parse for who develops software to represent those topologies visually. Something like this: https://github.com/interop-dev/json-for-networks/blob/master/examples/network-routes.json Now, this is not some weird utopic idea. A similar thing has been done in the GIS field: *GeoJSON*. You can pass GeoJSON to any GIS library, written in any language, and it will understand what is that you are passing. You can visualize that GeoJSON on a map with leaflet or openlayers, you can useit to calculate distances and stuff on the server side, you can output on an HTTP API, or whatever. Here there's a very early draft of the spec: https://github.com/interop-dev/json-for-networks Before we start implementing it in softwares like node databases, monitoring systems and firmwares, we would love to have some feedback from you guys as everybody in our communities use OpenWRT. We would like to know if anyone else has been working on a similar idea and we would like to have constructive critical feedback and improve our early spec before starting to prototype. If anybody will be at Fosdem we can also discuss in person there. Cheers to all and hope to see many of you at the next battlemesh in Slovenia. Federico Capoano (aka Nemesis) Ninux.org ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [OFF] Can't join openwrt-users
Hello all, Sorry to post this here, but I really can't subscribe to the openwrt-users. I've tried with two different emails and I never receive the confirmation email (also checked spam). Anybody could help? cheers, bráulio -- Lute pela sua ideologia. Seja um com sua ideologia. Viva pela sua ideologia. Morra por sua ideologia P.R. Sarkar EITA - Educação, Informação e Tecnologias para Autogestão http://cirandas.net/brauliobo http://eita.org.br Paramapurusha é meu pai e Parama Prakriti é minha mãe. O universo é meu lar e todos nós somos cidadãos deste cosmo. Este universo é a imaginação da Mente Macrocósmica, e todas as entidades estão sendo criadas, preservadas e destruídas nas fases de extroversão e introversão do fluxo imaginativo cósmico. No âmbito pessoal, quando uma pessoa imagina algo em sua mente, naquele momento, essa pessoa é a única proprietária daquilo que ela imagina, e ninguém mais. Quando um ser humano criado mentalmente caminha por um milharal também imaginado, a pessoa imaginada não é a propriedade desse milharal, pois ele pertence ao indivíduo que o está imaginando. Este universo foi criado na imaginação de Brahma, a Entidade Suprema, por isso a propriedade deste universo é de Brahma, e não dos microcosmos que também foram criados pela imaginação de Brahma. Nenhuma propriedade deste mundo, mutável ou imutável, pertence a um indivíduo em particular; tudo é o patrimônio comum de todos. Restante do texto em http://cirandas.net/brauliobo/blog/a-problematica-de-hoje-em-dia ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Dual Wifi for OpenWRT
Hello! Does anyone know a hardware platform with 2 or more wifi interfaces which can both be used in the 2.4 GHz band? I just went thru the table of hardware looking for boards which have more than one wifi. Unfortunately all of the consumer APs tagged with 2WNIC seem to have 1 wifi for 2.4GHz and one for 5GHz. The few other boards which can support more than one wifi (RouterBoard, Complex, Gateworks) are miniPCI or mPCIe based and look like developer boards meaning one has to get the board, cards, casing separately and assemble it manually... Is there really no readily availabe HW with more than one wifi? I'm puzzled... Thanks for any pointers... bruno ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/7] kernel: add missing symbols for 3.18
Hi, On Sat, 10 Jan 2015, Daniel Golle wrote: Augmented by iptables modules, if they are enabled. oldconfig hangs and asks for them if *tables modules are not selected. Signed-off-by: Daniel Golle dan...@makrotopia.org --- target/linux/generic/config-3.18 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/target/linux/generic/config-3.18 b/target/linux/generic/config-3.18 index ce2ec5c..1927a18 100644 --- a/target/linux/generic/config-3.18 +++ b/target/linux/generic/config-3.18 @@ -2552,6 +2552,8 @@ CONFIG_NF_CONNTRACK_PROCFS=y # CONFIG_NF_CT_PROTO_UDPLITE is not set # CONFIG_NF_DEFRAG_IPV4 is not set # CONFIG_NF_LOG_ARP is not set +# CONFIG_NF_LOG_IPV4 is not set +# CONFIG_NF_REJECT_IPV4 is not set # CONFIG_NF_NAT is not set # CONFIG_NF_NAT_AMANDA is not set # CONFIG_NF_NAT_FTP is not set This one was added as part of r43912 already - thanks. Based on the first mvebu 3.18 build, further similar ones are expected. Regards, -w- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 3/7] uboot-sunxi: fix bananapro target
Hi, On Sat, 10 Jan 2015, Daniel Golle wrote: At least making sure stuff compiles before committing would be nice. Signed-off-by: Daniel Golle dan...@makrotopia.org --- package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff b/package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff index 1d2677c..23d0ebf 100644 --- a/package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff +++ b/package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff @@ -5,7 +5,7 @@ diff -ruN u-boot-2015.01-rc3.old/board/sunxi/Makefile u-boot-2015.01-rc3/board/s obj-$(CONFIG_TARGET_AUXTEK_T004) += dram_a10s_olinuxino_m.o obj-$(CONFIG_TARGET_BA10_TV_BOX) += dram_sun4i_384_1024_iow8.o obj-$(CONFIG_TARGET_BANANAPI) += dram_bananapi.o -+obj-$(CONFIG_TARGET_BANANAPI) += dram_bananapi.o ++obj-$(CONFIG_TARGET_BANANAPRO)+= dram_bananapi.o obj-$(CONFIG_TARGET_CUBIEBOARD)+= dram_cubieboard.o obj-$(CONFIG_TARGET_CUBIEBOARD2) += dram_cubieboard2.o obj-$(CONFIG_TARGET_CUBIETRUCK)+= dram_cubietruck.o This was missed during patch shuffling - thanks, applied in r43921. Regards, -w- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Dual Wifi for OpenWRT
As in to run on 2 different 2.4ghz channels, or to just provide 2 SSIDs? Most platforms can run multiple SSIDs, I personally have several Linksys WRT54GL and TPLink TL-WR1043ND (HW versions 1 and 2) devices that happily run 3 SSIDs (all in AP mode, all on the same channel). Aaron Z A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. — Robert Heinlein, Time Enough for Love On Sat, Jan 10, 2015 at 11:15 AM, Bruno Randolf b...@einfach.org wrote: Hello! Does anyone know a hardware platform with 2 or more wifi interfaces which can both be used in the 2.4 GHz band? I just went thru the table of hardware looking for boards which have more than one wifi. Unfortunately all of the consumer APs tagged with 2WNIC seem to have 1 wifi for 2.4GHz and one for 5GHz. The few other boards which can support more than one wifi (RouterBoard, Complex, Gateworks) are miniPCI or mPCIe based and look like developer boards meaning one has to get the board, cards, casing separately and assemble it manually... Is there really no readily availabe HW with more than one wifi? I'm puzzled... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Dual Wifi for OpenWRT
On Sat, 10 Jan 2015, Bruno Randolf wrote: On 01/10/2015 08:38 PM, David Lang wrote: I would not expect to find consumer hardware that had two radios on the 2.4GHz band, the problems that you would run into trying to keep the output of one radio from deafening the other (if not outright popping the receiver amps) would be significant (to say the least). It could be done, but it would take antenna setups that you just don't see mass produced to even get started. Right, that is a good explanation why no consumer HW with this feature exists. Even the enterprise grade hardware that has multiple radios tends to have problems with this. It takes having very directional antennas to try and keep as much of the signal away from the other radio to even start. Hmm... Yes antenna placement is important and difficult, but I know setups where this works quite well. E.g. using RouterStation Pro with 3 MiniPCI cards (ath5k/ath9k). What is it that you are trying to accomplish? For one part I'm trying to find alternatives to that RouterStationPro board which is EOL. But in the current case I actually want to have one or more radios in monitor mode (running horst, switching thru channels) and another one for connectivity (mesh). In this case the interference problems you mention don't exist, but I admit that this is not a very usual use-case... ;) In that case you re probably best off adding a USB wifi interface to a router. In terms of antennas, try going with high-gain omnidirectional antennas and position them directly above each other (omnidirectional antennas have a 'blind spot' directly above and below the antenna, so if you position them so that each is in the blind spot of the other you have the best chance of it working, and high gain antennas are going to have flatter patterns, making them more forgiving) David Lang ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 1/7] kernel: add missing symbols for 3.18
Augmented by iptables modules, if they are enabled. oldconfig hangs and asks for them if *tables modules are not selected. Signed-off-by: Daniel Golle dan...@makrotopia.org --- target/linux/generic/config-3.18 | 2 ++ 1 file changed, 2 insertions(+) diff --git a/target/linux/generic/config-3.18 b/target/linux/generic/config-3.18 index ce2ec5c..1927a18 100644 --- a/target/linux/generic/config-3.18 +++ b/target/linux/generic/config-3.18 @@ -2552,6 +2552,8 @@ CONFIG_NF_CONNTRACK_PROCFS=y # CONFIG_NF_CT_PROTO_UDPLITE is not set # CONFIG_NF_DEFRAG_IPV4 is not set # CONFIG_NF_LOG_ARP is not set +# CONFIG_NF_LOG_IPV4 is not set +# CONFIG_NF_REJECT_IPV4 is not set # CONFIG_NF_NAT is not set # CONFIG_NF_NAT_AMANDA is not set # CONFIG_NF_NAT_FTP is not set -- 2.2.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 7/7] sunxi: add support for Lamobo R1
Initial support for BananaPi-R1 aka Lamobo-R1.
Based on patchset form Wang Yi wangyi8...@gmail.com published on
https://github.com/Lamobo/Lamobo-R1-OpenWrt
Signed-off-by: Daniel Golle dan...@makrotopia.org
---
target/linux/sunxi/config-3.18 | 7 +
target/linux/sunxi/image/Makefile | 7 +-
.../patches-3.18/302-dt-sun7i-add-lamobo-r1.patch | 221 +
target/linux/sunxi/profiles/lamobo-r1.mk | 19 ++
4 files changed, 253 insertions(+), 1 deletion(-)
mode change 100644 = 100755 target/linux/sunxi/image/Makefile
create mode 100644
target/linux/sunxi/patches-3.18/302-dt-sun7i-add-lamobo-r1.patch
create mode 100644 target/linux/sunxi/profiles/lamobo-r1.mk
diff --git a/target/linux/sunxi/config-3.18 b/target/linux/sunxi/config-3.18
index 44b5d89..3dfe903 100644
--- a/target/linux/sunxi/config-3.18
+++ b/target/linux/sunxi/config-3.18
@@ -58,6 +58,11 @@ CONFIG_AUDIT=y
CONFIG_AUDIT_GENERIC=y
CONFIG_AUTO_ZRELADDR=y
CONFIG_AVERAGE=y
+CONFIG_B53=y
+# CONFIG_B53_MMAP_DRIVER is not set
+CONFIG_B53_PHY_DRIVER=y
+CONFIG_B53_PHY_FIXUP=y
+# CONFIG_B53_SRAB_DRIVER is not set
CONFIG_BINFMT_MISC=y
CONFIG_BLK_CGROUP=y
CONFIG_BLK_DEV_SD=y
@@ -305,6 +310,7 @@ CONFIG_MFD_SUN6I_PRCM=y
CONFIG_MIGHT_HAVE_CACHE_L2X0=y
CONFIG_MIGHT_HAVE_PCI=y
CONFIG_MIGRATION=y
+CONFIG_MII=y
CONFIG_MMC=y
CONFIG_MMC_BLOCK=y
# CONFIG_MMC_BLOCK_BOUNCE is not set
@@ -448,6 +454,7 @@ CONFIG_STRICT_DEVMEM=y
CONFIG_SUN4I_TIMER=y
CONFIG_SUN5I_HSTIMER=y
CONFIG_SUNXI_WATCHDOG=y
+CONFIG_SWCONFIG=y
CONFIG_SWIOTLB=y
CONFIG_SWP_EMULATE=y
CONFIG_SYSFS_SYSCALL=y
diff --git a/target/linux/sunxi/image/Makefile
b/target/linux/sunxi/image/Makefile
old mode 100644
new mode 100755
index 3fb41c1..81ec8d8
--- a/target/linux/sunxi/image/Makefile
+++ b/target/linux/sunxi/image/Makefile
@@ -24,7 +24,8 @@ BOARDS:= \
sun7i-a20-cubietruck \
sun7i-a20-olinuxino-lime \
sun7i-a20-olinuxino-micro \
- sun7i-a20-pcduino3
+ sun7i-a20-pcduino3 \
+ sun7i-a20-lamobo-r1
define Image/BuildKernel
mkimage -A arm -O linux -T kernel -C none \
@@ -88,6 +89,10 @@ define Image/Build/Profile/Bananapro
$(call Image/Build/SDCard,$(1),sun7i-a20-bananapro)
endef
+define Image/Build/Profile/Lamobo-R1
+ $(call Image/Build/SDCard,$(1),sun7i-a20-lamobo-r1)
+endef
+
define Image/Build/Profile/Cubieboard
$(call Image/Build/SDCard,$(1),sun4i-a10-cubieboard)
endef
diff --git a/target/linux/sunxi/patches-3.18/302-dt-sun7i-add-lamobo-r1.patch
b/target/linux/sunxi/patches-3.18/302-dt-sun7i-add-lamobo-r1.patch
new file mode 100644
index 000..e8288ca
--- /dev/null
+++ b/target/linux/sunxi/patches-3.18/302-dt-sun7i-add-lamobo-r1.patch
@@ -0,0 +1,221 @@
+--- a/arch/arm/boot/dts/Makefile
b/arch/arm/boot/dts/Makefile
+@@ -441,6 +441,7 @@ dtb-$(CONFIG_MACH_SUN7I) += \
+ sun7i-a20-cubietruck.dtb \
+ sun7i-a20-hummingbird.dtb \
+ sun7i-a20-i12-tvbox.dtb \
++ sun7i-a20-lamobo-r1.dtb \
+ sun7i-a20-olinuxino-lime.dtb \
+ sun7i-a20-olinuxino-micro.dtb \
+ sun7i-a20-pcduino3.dtb
+--- a/arch/arm/boot/dts/sun7i-a20-lamobo-r1.dts2015-01-09
12:02:32.479031636 +0100
b/arch/arm/boot/dts/sun7i-a20-lamobo-r1.dts2015-01-09
12:02:32.479031636 +0100
+@@ -0,0 +1,208 @@
++/*
++ * Copyright 2014 Zoltan HERPAI
++ * Zoltan HERPAI wigy...@uid0.hu
++ *
++ * The code contained herein is licensed under the GNU General Public
++ * License. You may obtain a copy of the GNU General Public License
++ * Version 2 or later at the following locations:
++ *
++ * http://www.opensource.org/licenses/gpl-license.html
++ * http://www.gnu.org/copyleft/gpl.html
++ */
++
++/dts-v1/;
++/include/ sun7i-a20.dtsi
++/include/ sunxi-common-regulators.dtsi
++#include dt-bindings/input/input.h
++
++/ {
++ model = Lamobo R1;
++ compatible = lamobo,lamobo-r1, allwinner,sun7i-a20;
++
++ aliases {
++ spi0 = spi1;
++ spi1 = spi2;
++ };
++
++ soc@01c0 {
++ spi1: spi@01c06000 {
++ pinctrl-names = default;
++ pinctrl-0 = spi1_pins_a;
++ status = okay;
++ };
++
++ spi2: spi@01c17000 {
++ pinctrl-names = default;
++ pinctrl-0 = spi2_pins_a;
++ status = okay;
++ };
++
++ mmc0: mmc@01c0f000 {
++ pinctrl-names = default, default;
++ pinctrl-0 = mmc0_pins_a;
++ pinctrl-1 = mmc0_cd_pin_lamobo;
++ cd-gpios = pio 7 10 0; /* PH10 */
++ status = okay;
++ };
++
++ usbphy: phy@01c13400 {
++ usb1_vbus-supply = reg_usb1_vbus;
++ usb2_vbus-supply = reg_usb2_vbus;
++ status = okay;
++ };
++
++
[OpenWrt-Devel] [PATCH 5/7] sunxi: merge upstream devicetree improvements for bananapro
merges DTS published on linux devicetree mailing list.
Signed-off-by: Daniel Golle dan...@makrotopia.org
---
.../sunxi/patches-3.18/301-add-bananapro.diff | 57 +++---
1 file changed, 49 insertions(+), 8 deletions(-)
diff --git a/target/linux/sunxi/patches-3.18/301-add-bananapro.diff
b/target/linux/sunxi/patches-3.18/301-add-bananapro.diff
index 2634240..a5d7154 100644
--- a/target/linux/sunxi/patches-3.18/301-add-bananapro.diff
+++ b/target/linux/sunxi/patches-3.18/301-add-bananapro.diff
@@ -12,27 +12,28 @@ diff -ruN old/arch/arm/boot/dts/Makefile
new/arch/arm/boot/dts/Makefile
diff -ruN old/arch/arm/boot/dts/sun7i-a20-bananapro.dts
new/arch/arm/boot/dts/sun7i-a20-bananapro.dts
--- old/arch/arm/boot/dts/sun7i-a20-bananapro.dts 1970-01-01
01:00:00.0 +0100
+++ new/arch/arm/boot/dts/sun7i-a20-bananapro.dts 2015-01-06
09:31:18.290582574 +0100
-@@ -0,0 +1,232 @@
+@@ -0,0 +1,273 @@
+/*
+ * Copyright 2014 Zoltan HERPAI wigy...@uid0.hu
++ * Copyright 2015 Hans de Goede hdegoede@xx
+ *
+ * This file is dual-licensed: you can use it either under the terms
+ * of the GPL or the X11 license, at your option. Note that this dual
+ * licensing only applies to this file, and not this project as a
+ * whole.
+ *
-+ * a) This library is free software; you can redistribute it and/or
++ * a) This file is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of the
+ * License, or (at your option) any later version.
+ *
-+ * This library is distributed in the hope that it will be useful,
++ * This file 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.
+ *
+ * You should have received a copy of the GNU General Public
-+ * License along with this library; if not, write to the Free
++ * License along with this file; if not, write to the Free
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
+ * MA 02110-1301 USA
+ *
@@ -132,6 +133,20 @@ diff -ruN old/arch/arm/boot/dts/sun7i-a20-bananapro.dts
new/arch/arm/boot/dts/su
+ };
+
+ pinctrl@01c20800 {
++ usb1_vbus_pin_bananapro: usb1_vbus_pin@0 {
++ allwinner,pins = PH0;
++ allwinner,function = gpio_out;
++ allwinner,drive = 0;
++ allwinner,pull = 0;
++ };
++
++ usb2_vbus_pin_bananapro: usb2_vbus_pin@0 {
++ allwinner,pins = PH1;
++ allwinner,function = gpio_out;
++ allwinner,drive = 0;
++ allwinner,pull = 0;
++ };
++
+ mmc0_cd_pin_bananapro: mmc0_cd_pin@0 {
+ allwinner,pins = PH10;
+ allwinner,function = gpio_in;
@@ -139,6 +154,13 @@ diff -ruN old/arch/arm/boot/dts/sun7i-a20-bananapro.dts
new/arch/arm/boot/dts/su
+ allwinner,pull = 1;
+ };
+
++ vmmc3_pin_bananapro: vmmc3_pin@0 {
++ allwinner,pins = PH22;
++ allwinner,function = gpio_out;
++ allwinner,drive = 0;
++ allwinner,pull = 0;
++ };
++
+ gmac_power_pin_bananapro: gmac_power_pin@0 {
+ allwinner,pins = PH23;
+ allwinner,function = gpio_out;
@@ -147,7 +169,7 @@ diff -ruN old/arch/arm/boot/dts/sun7i-a20-bananapro.dts
new/arch/arm/boot/dts/su
+ };
+
+ led_pins_bananapro: led_pins@0 {
-+ allwinner,pins = PH24;
++ allwinner,pins = PH24, PG2;
+ allwinner,function = gpio_out;
+ allwinner,drive = 0;
+ allwinner,pull = 0;
@@ -166,9 +188,9 @@ diff -ruN old/arch/arm/boot/dts/sun7i-a20-bananapro.dts
new/arch/arm/boot/dts/su
+ status = okay;
+ };
+
-+ uart3: serial@01c28c00 {
++ uart2: serial@01c28800 {
+ pinctrl-names = default;
-+ pinctrl-0 = uart3_pins_b;
++ pinctrl-0 = uart2_pins_a;
+ status = okay;
+ };
+
@@ -223,13 +245,21 @@ diff -ruN old/arch/arm/boot/dts/sun7i-a20-bananapro.dts
new/arch/arm/boot/dts/su
+
[OpenWrt-Devel] [PATCH 6/7] uboot-sunxi: add support for Lamobo R1
Seems to be identical with bananapi, however, sdcard image generation scripts currently depend on having u-boot named the same as the profile. Signed-off-by: Daniel Golle dan...@makrotopia.org --- package/boot/uboot-sunxi/Makefile | 5 +++ .../uboot-sunxi/patches/004-add-lamobo-r1.patch| 37 ++ 2 files changed, 42 insertions(+) create mode 100644 package/boot/uboot-sunxi/patches/004-add-lamobo-r1.patch diff --git a/package/boot/uboot-sunxi/Makefile b/package/boot/uboot-sunxi/Makefile index d61e4a3..6571088 100644 --- a/package/boot/uboot-sunxi/Makefile +++ b/package/boot/uboot-sunxi/Makefile @@ -86,6 +86,10 @@ define uboot/Linksprite_pcDuino3 TITLE:=U-Boot for Linksprite pcDuino3 endef +define uboot/Lamobo-R1 + TITLE:=U-Boot for Lamobo R1 +endef + UBOOTS:= \ A10-OLinuXino-Lime \ A13-OLinuXino \ @@ -101,6 +105,7 @@ UBOOTS:= \ OLIMEX-A13-SOM \ Linksprite_pcDuino \ Linksprite_pcDuino3 \ + Lamobo-R1 \ define Package/uboot/template define Package/uboot-sunxi-$(1) diff --git a/package/boot/uboot-sunxi/patches/004-add-lamobo-r1.patch b/package/boot/uboot-sunxi/patches/004-add-lamobo-r1.patch new file mode 100644 index 000..7f52cce --- /dev/null +++ b/package/boot/uboot-sunxi/patches/004-add-lamobo-r1.patch @@ -0,0 +1,37 @@ +Index: u-boot-2015.01-rc4/board/sunxi/Makefile +=== +--- u-boot-2015.01-rc4.orig/board/sunxi/Makefile u-boot-2015.01-rc4/board/sunxi/Makefile +@@ -23,6 +23,7 @@ obj-$(CONFIG_TARGET_AUXTEK_T004) += dram + obj-$(CONFIG_TARGET_BA10_TV_BOX) += dram_sun4i_384_1024_iow8.o + obj-$(CONFIG_TARGET_BANANAPI) += dram_bananapi.o + obj-$(CONFIG_TARGET_BANANAPRO)+= dram_bananapi.o ++obj-$(CONFIG_TARGET_LAMOBO_R1)+= dram_bananapi.o + obj-$(CONFIG_TARGET_CUBIEBOARD) += dram_cubieboard.o + obj-$(CONFIG_TARGET_CUBIEBOARD2) += dram_cubieboard2.o + obj-$(CONFIG_TARGET_CUBIETRUCK) += dram_cubietruck.o +Index: u-boot-2015.01-rc4/board/sunxi/gmac.c +=== +--- u-boot-2015.01-rc4.orig/board/sunxi/gmac.c u-boot-2015.01-rc4/board/sunxi/gmac.c +@@ -34,7 +34,7 @@ int sunxi_gmac_initialize(bd_t *bis) +* need to set bits 10-12 GTXDC GMAC Transmit Clock Delay Chain +* of the GMAC clk register to 3. +*/ +-#ifdef CONFIG_TARGET_BANANAPI ++#if defined(CONFIG_TARGET_BANANAPI) || defined(CONFIG_TARGET_LAMOBO_R1) + setbits_le32(ccm-gmac_clk_cfg, 0x3 10); + #endif + +Index: u-boot-2015.01-rc4/configs/Lamobo-R1_defconfig +=== +--- /dev/null u-boot-2015.01-rc4/configs/Lamobo-R1_defconfig +@@ -0,0 +1,7 @@ ++CONFIG_SPL=y ++CONFIG_SYS_EXTRA_OPTIONS=AXP209_POWER,SUNXI_GMAC,RGMII,MACPWR=SUNXI_GPH(23),AHCI,USB_EHCI ++CONFIG_FDTFILE=sun7i-a20-lamobo-r1.dtb +++S:CONFIG_ARM=y +++S:CONFIG_ARCH_SUNXI=y +++S:CONFIG_MACH_SUN7I=y +++S:CONFIG_TARGET_LAMOBO_R1=y -- 2.2.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Dual Wifi for OpenWRT
* Aaron Z aczlan+open...@gmail.com [10.01.2015 19:09]: Does anyone know a hardware platform with 2 or more wifi interfaces which can both be used in the 2.4 GHz band? We simply connect several AP's together (ethernet) and let do the mesh-routing-daemon OLSR the rest. bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Dual Wifi for OpenWRT
On 01/10/2015 08:38 PM, David Lang wrote: I would not expect to find consumer hardware that had two radios on the 2.4GHz band, the problems that you would run into trying to keep the output of one radio from deafening the other (if not outright popping the receiver amps) would be significant (to say the least). It could be done, but it would take antenna setups that you just don't see mass produced to even get started. Right, that is a good explanation why no consumer HW with this feature exists. Even the enterprise grade hardware that has multiple radios tends to have problems with this. It takes having very directional antennas to try and keep as much of the signal away from the other radio to even start. Hmm... Yes antenna placement is important and difficult, but I know setups where this works quite well. E.g. using RouterStation Pro with 3 MiniPCI cards (ath5k/ath9k). What is it that you are trying to accomplish? For one part I'm trying to find alternatives to that RouterStationPro board which is EOL. But in the current case I actually want to have one or more radios in monitor mode (running horst, switching thru channels) and another one for connectivity (mesh). In this case the interference problems you mention don't exist, but I admit that this is not a very usual use-case... ;) bruno ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Dual Wifi for OpenWRT
On Sat, 10 Jan 2015, Bruno Randolf wrote: Does anyone know a hardware platform with 2 or more wifi interfaces which can both be used in the 2.4 GHz band? I would not expect to find consumer hardware that had two radios on the 2.4GHz band, the problems that you would run into trying to keep the output of one radio from deafening the other (if not outright popping the receiver amps) would be significant (to say the least). It could be done, but it would take antenna setups that you just don't see mass produced to even get started. Even the enterprise grade hardware that has multiple radios tends to have problems with this. It takes having very directional antennas to try and keep as much of the signal away from the other radio to even start. What is it that you are trying to accomplish? David Lang ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 4/7] sunxi: fix DTS syntax in bananapro device tree
add missing semicolon Signed-off-by: Daniel Golle dan...@makrotopia.org --- target/linux/sunxi/patches-3.18/301-add-bananapro.diff | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/sunxi/patches-3.18/301-add-bananapro.diff b/target/linux/sunxi/patches-3.18/301-add-bananapro.diff index 47454e9..2634240 100644 --- a/target/linux/sunxi/patches-3.18/301-add-bananapro.diff +++ b/target/linux/sunxi/patches-3.18/301-add-bananapro.diff @@ -90,7 +90,7 @@ diff -ruN old/arch/arm/boot/dts/sun7i-a20-bananapro.dts new/arch/arm/boot/dts/su + #size-cells = 0; + + pinctrl-names = default; -+ pinctrl-0 = mmc3_pins_a ++ pinctrl-0 = mmc3_pins_a; + vmmc-supply = reg_vmmc3; + bus-width = 4; + non-removable; -- 2.2.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 3/7] uboot-sunxi: fix bananapro target
At least making sure stuff compiles before committing would be nice. Signed-off-by: Daniel Golle dan...@makrotopia.org --- package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff b/package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff index 1d2677c..23d0ebf 100644 --- a/package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff +++ b/package/boot/uboot-sunxi/patches/003-add-lemaker-bananapro.diff @@ -5,7 +5,7 @@ diff -ruN u-boot-2015.01-rc3.old/board/sunxi/Makefile u-boot-2015.01-rc3/board/s obj-$(CONFIG_TARGET_AUXTEK_T004) += dram_a10s_olinuxino_m.o obj-$(CONFIG_TARGET_BA10_TV_BOX) += dram_sun4i_384_1024_iow8.o obj-$(CONFIG_TARGET_BANANAPI) += dram_bananapi.o -+obj-$(CONFIG_TARGET_BANANAPI) += dram_bananapi.o ++obj-$(CONFIG_TARGET_BANANAPRO)+= dram_bananapi.o obj-$(CONFIG_TARGET_CUBIEBOARD) += dram_cubieboard.o obj-$(CONFIG_TARGET_CUBIEBOARD2) += dram_cubieboard2.o obj-$(CONFIG_TARGET_CUBIETRUCK) += dram_cubietruck.o -- 2.2.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 7/7] sunxi: add support for Lamobo R1
Hi, On Sat, 10 Jan 2015, Daniel Golle wrote: Initial support for BananaPi-R1 aka Lamobo-R1. Based on patchset form Wang Yi wangyi8...@gmail.com published on https://github.com/Lamobo/Lamobo-R1-OpenWrt Thanks for submitting this. Did you have a chance to verify the switch working? I have read various results around it. Regards, -w- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 5/7] sunxi: merge upstream devicetree improvements for bananapro
Hi, On Sat, 10 Jan 2015, Daniel Golle wrote: merges DTS published on linux devicetree mailing list. Thanks for this - didn't spot that Hans beat me with a few days on the file. Pushed in the published patch, and will patch in the brcmfmac-related stuff later. Thanks, -w- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
