Re: [OpenWrt-Devel] [PATCH] openssl: version bump
On 06/06/2014 01:00, Florian Fainelli wrote: On Jun 5, 2014 2:54 PM, joerg jungermann j...@borkum.net mailto:j...@borkum.net wrote: today appeared another serious vulnerability in openssl. More info is here http://ccsinjection.lepidum.co.jp. Users are advised to update to openssl 1.0.1h. Thank you for your patch, it was committed in r41026 and 41027. Will there be a backport to AA 12.09? There has been one just applied in r41027 i'll kick the release-builder once i've had breakfast best regards -- Joerg Jungermann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org mailto: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] changeset 40948 breaks loading ath9k calibration data from EEPROM
On 14/06/2014 13:29, Ben Mulvihill wrote: Hi, Since changeset 40948, calibration data is no longer correctly loaded from EEPROM on the BTHOMEHUBV2B. I've been trying to make sense of the various changes to 0010-MIPS-lantiq-wifi-and-ethernet-eeprom-handling.patch and it looks to me as though merging José's recent patch for the ARV4518PW has left us with an old version of the ath9k EEPROM loading code, without the succession of changes made last year culminating in patch #4417 from Daniel Gimpelevitch. I should imagine therefore that the DGN3500 is broken as well as the BTHOMEHUBV2B. Ben ok, i will look into it and merge the version we had previous to the 3.10 rebase John u ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] changeset 40948 breaks loading ath9k calibration data from EEPROM
On 14/06/2014 23:08, José Vázquez wrote: The main problem with the wifi in the Lantiq target are the ARV boards: a lot of people, John included, spent a lot of time an still there are some problems, as you see. bollocks .. i never spent any time on that code. i don't even have the boards so i cannot test which is why its most likely why its broken. if people had spend that much time on the code it would be woring and not ugly and broken. as for the patches you sent, they were not merged because they are a big pile of copy pasta churn that adds lots of redunancy and duplication. it would make the code even uglier than it is now. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: RT-N56U support fixes and factory image creation
Hi Mikko,
On 11/06/2014 17:01, Mikko Hissa wrote:
@@ -0,0 +1,28 @@ +--- a/drivers/mtd/mtdpart.c 2014-04-27
10:09:21.566294160 +0300 b/drivers/mtd/mtdpart.c 2014-06-09
11:27:48.952211672 +0300 +@@ -793,8 +793,11 @@ + { + struct { +
__be32 magic; +- __be32 pad[2]; ++ __be32 pad0[2];
+ __be32
size; ++ __be32 pad1[4]; ++ __be32 name[7]; ++
__be32
kern_size; + } hdr; +size_t len; + +@@ -804,7 +807,11 @@ + if
(len != sizeof(hdr) || hdr.magic != cpu_to_be32(UBOOT_MAGIC)) +
return; + +- len = be32_to_cpu(hdr.size) + 0x40; ++ if
(hdr.kern_size != 0 hdr.name[0] == 0) ++ len =
be32_to_cpu(hdr.kern_size); ++else ++ len =
be32_to_cpu(hdr.size)
+ 0x40; ++ + __mtd_add_partition(master, rootfs, part-offset +
len, +part-mtd.size - len, false); + }
This bit look weird. the kern_size field certainly is not part of the
standard uimage header can we be sure that this field will always be 0
for none rt-n56u units ?
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Howto force mips64
On 17/06/2014 11:24, Martin Fäcknitz wrote: uclibc's mips64 support is broken, so you have to use glibc. gcc-4.8 doesn't work for me (invalid TLS related code), therefore use gcc-4.6. Hi, yes, utterly broken :) i have been talking to the guys at imgtec about this and there are people working on this matter. i would expect it to take a few months though until this is all fixed and has treacled down to openwrt. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Howto force mips64
Hi Martin,
you win the medal as contributor of the day ... i have been fighting
with octeon on and off for almost a month. i just dumped my own series
of patches which tried to fix up uclibc and simple did what you wrote
in the mail and i have a functional image for octeon :)
i just tested this on an esr-lite which seems to work without your
kernel patches. what board are you running on ?
John
On 17/06/2014 11:24, Martin Fäcknitz wrote:
force mips64 support is quite simple: set
CPU_CFLAGS_octeon=-march=octeon -mabi=64
inside target/linux/octeon/Makefile and replace the same line in
include/target.mk. Finally you have to add the following patch:
diff --git
a/target/linux/octeon/patches-3.10/-cn61xx_support.patch
b/target/linux/octeon/patches-3.10/-cn61xx_support.patch new
file mode 100644 index 000..18d2f3d --- /dev/null +++
b/target/linux/octeon/patches-3.10/-cn61xx_support.patch @@
-0,0 +1,47 @@ +Index:
b/arch/mips/cavium-octeon/executive/cvmx-helper-board.c
+===
+--- a/arch/mips/cavium-octeon/executive/cvmx-helper-board.c2014-05-06
15:24:06.0 +0200
b/arch/mips/cavium-octeon/executive/cvmx-helper-board.c 2014-05-06
15:25:14.0 +0200 +@@ -75,6 +75,8 @@ + int
cvmx_helper_board_get_mii_address(int ipd_port) + { + switch
(cvmx_sysinfo_get()-board_type) { ++ case 20003: ++ return -1; +
case CVMX_BOARD_TYPE_SIM: + /* Simulator doesn't have MII */ +
return -1; +Index:
b/arch/mips/cavium-octeon/executive/cvmx-helper.c
+===
+--- a/arch/mips/cavium-octeon/executive/cvmx-helper.c 2014-01-25
17:27:55.0 +0100
b/arch/mips/cavium-octeon/executive/cvmx-helper.c 2014-05-06
15:25:47.0 +0200 +@@ -83,7 +83,7 @@ + */ + int
cvmx_helper_get_number_of_interfaces(void) + { +- if
(OCTEON_IS_MODEL(OCTEON_CN56XX) || OCTEON_IS_MODEL(OCTEON_CN52XX))
++if (OCTEON_IS_MODEL(OCTEON_CN56XX) ||
OCTEON_IS_MODEL(OCTEON_CN52XX) || OCTEON_IS_MODEL(OCTEON_CN61XX)) +
return 4; + else + return 3; +@@ -121,7 +121,8 @@ + + if
(interface == 3) { + if (OCTEON_IS_MODEL(OCTEON_CN56XX) +-
|| OCTEON_IS_MODEL(OCTEON_CN52XX)) ++ ||
OCTEON_IS_MODEL(OCTEON_CN52XX) ++ ||
OCTEON_IS_MODEL(OCTEON_CN6XXX)) + return
CVMX_HELPER_INTERFACE_MODE_LOOP; +else + return
CVMX_HELPER_INTERFACE_MODE_DISABLED; +@@ -152,7 +153,9 @@ + +
mode.u64 = cvmx_read_csr(CVMX_GMXX_INF_MODE(interface)); + +- if
(OCTEON_IS_MODEL(OCTEON_CN56XX) || OCTEON_IS_MODEL(OCTEON_CN52XX))
{ ++ if (OCTEON_IS_MODEL(OCTEON_CN61XX)) { ++return
CVMX_HELPER_INTERFACE_MODE_SGMII; ++ } else if
(OCTEON_IS_MODEL(OCTEON_CN56XX) || OCTEON_IS_MODEL(OCTEON_CN52XX))
{ + switch (mode.cn56xx.mode) { + case 0: +
return
CVMX_HELPER_INTERFACE_MODE_DISABLED;
uclibc's mips64 support is broken, so you have to use glibc.
gcc-4.8 doesn't work for me (invalid TLS related code), therefore
use gcc-4.6.
greets
On 16.06.2014 23:26, Edison Figueira Junior wrote:
hello, I can be a beta test if you want :-)
Enviada do meu iPhone
Em 04/06/2014, às 10:05, John Crispin j...@phrozen.org
escreveu:
octeon is currently only partially working. we will push a fix
to trunk in the next few days. experimental patch is currently
in testing. please be patient for a few dyas
On 04/06/2014 14:36, Edison Figueira Junior wrote: Howto
force to use mips64 for target octeon?
___
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
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Add terminfo file in ncurses
On 12/06/2014 20:26, Jonathan Bennett wrote: Ran into a problem with my Fedora Linux machine, SSHing into an Openwrt router. Fedora sets terminfo to xterm-256color, but ncurses doesn't include that file in the firmware. This causes a few unintended problems, namely nano fails to launch. Attached patch adds xterm-256color to the files installed by ncurses. Signed-off-by: Jonathan Bennett jbscienc...@gmail.com mailto:jbscienc...@gmail.com Hi, patchwork picked up a patch with broken whitespaces -- http://patchwork.openwrt.org/patch/5644/ can you resend the patch using git send-email this will make sure that we receive valid patch. John diff --git a/package/libs/ncurses/Makefile b/package/libs/ncurses/Makefile index 62ffdfb..26b7bf5 100644 --- a/package/libs/ncurses/Makefile +++ b/package/libs/ncurses/Makefile @@ -101,7 +101,7 @@ ifneq ($(HOST_OS),FreeBSD) mv dir (echo -ne \xdir); \ done \ ) -for file in a/ansi d/dumb l/linux r/rxvt r/rxvt-unicode s/screen v/vt100 v/vt102 x/xterm x/xterm-color; do \ +for file in a/ansi d/dumb l/linux r/rxvt r/rxvt-unicode s/screen v/vt100 v/vt102 x/xterm x/xterm-color x/xterm-256color; do \ $(INSTALL_DIR) $(1)/usr/share/terminfo/`dirname file`; \ $(CP) $(PKG_INSTALL_DIR)/usr/share/terminfo/file \ $(1)/usr/share/terminfo/file; \ ___ 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] [PATCH v3] ar71xx: Add support for MikroTik RouterBOARD SXT Lite
Hi,
this patch is generated against the wrong root directory making git
am fail. i had to use patch -p0 to manually apply it. Please make
sure to send a valid patch the next time.
John
On 11/06/2014 23:05, Matthew Reeve wrote:
This patch adds support for the MikroTik RouterBOARD SXT Lite.
The new RB911L series is also supported as a result.
v2 of this patch fixes the wmac offset to match what is on the
sticker. v3 refreshes the patch against r41148 and defines the
power led as the status led in diag.sh
Signed-off-by: Matthew Reeve mre...@tenxnetworks.com
---
target/linux/ar71xx/patches-3.10/712-MIPS-ath79-add-RBSXTLite-support.patch
2014-05-12 18:49:06.902842033 + +++
target/linux/ar71xx/patches-3.10/712-MIPS-ath79-add-RBSXTLite-support.patch
2014-05-21 20:34:52.209118569 + @@ -0,0 +1,38 @@ +---
a/arch/mips/ath79/Kconfig 2014-05-21 20:25:24.801106234 +
b/arch/mips/ath79/Kconfig 2014-05-21 20:28:20.489109814 + +@@
-442,6 +442,14 @@ config ATH79_MACH_RB2011 + select
ATH79_ROUTERBOOT +select RLE_DECOMPRESS + ++config
ATH79_MACH_RBSXTLITE ++ bool MikroTik RouterBOARD SXT Lite ++
select SOC_AR934x ++ select ATH79_DEV_ETH ++ select ATH79_DEV_NFC
++select ATH79_DEV_WMAC ++select ATH79_ROUTERBOOT ++ + config
ATH79_MACH_WNDAP360 + bool NETGEAR WNDAP360 board support +
select SOC_AR71XX +--- a/arch/mips/ath79/machtypes.h 2014-05-21
20:25:24.801106234 + b/arch/mips/ath79/machtypes.h
2014-05-21 20:30:04.829111865 + +@@ -91,6 +91,8 @@ enum
ath79_mach_type { + ATH79_MACH_RB_2011G,/* Mikrotik RouterBOARD
2011UAS-2HnD */ + ATH79_MACH_RB_2011L,/* Mikrotik RouterBOARD
2011L */ +ATH79_MACH_RB_2011US, /* Mikrotik RouterBOARD 2011UAS
*/ ++ ATH79_MACH_RB_SXTLITE2ND, /* Mikrotik RouterBOARD SXT Lite
2nD */ ++ ATH79_MACH_RB_SXTLITE5ND, /* Mikrotik RouterBOARD SXT
Lite 5nD */ + ATH79_MACH_RW2458N, /* Redwave RW2458N */ +
ATH79_MACH_TEW_632BRP,/* TRENDnet TEW-632BRP */ +
ATH79_MACH_TEW_673GRU,/* TRENDnet TEW-673GRU */ +---
a/arch/mips/ath79/Makefile2014-05-21 20:25:24.801106234 +
b/arch/mips/ath79/Makefile 2014-05-21 20:31:37.169113830 +
+@@ -83,6 +83,7 @@ obj-$(CONFIG_ATH79_MACH_RB750) += mach- +
obj-$(CONFIG_ATH79_MACH_RB91X)+= mach-rb91x.o +
obj-$(CONFIG_ATH79_MACH_RB95X)+= mach-rb95x.o +
obj-$(CONFIG_ATH79_MACH_RB2011) += mach-rb2011.o
++obj-$(CONFIG_ATH79_MACH_RBSXTLITE) += mach-rbsxtlite.o +
obj-$(CONFIG_ATH79_MACH_RW2458N) += mach-rw2458n.o +
obj-$(CONFIG_ATH79_MACH_TEW_632BRP) += mach-tew-632brp.o +
obj-$(CONFIG_ATH79_MACH_TEW_673GRU) += mach-tew-673gru.o ---
target/linux/ar71xx/files/arch/mips/ath79/mach-rbsxtlite.c
2014-05-12 18:49:06.902842033 + +++
target/linux/ar71xx/files/arch/mips/ath79/mach-rbsxtlite.c
2014-05-21 19:50:48.073064837 + @@ -0,0 +1,238 @@ +/* + *
MikroTik RouterBOARD SXT Lite support + * + * Copyright (C) 2012
Stijn Tintel st...@linux-ipv6.be + * Copyright (C) 2012 Gabor
Juhos juh...@openwrt.org + * Copyright (C) 2013 Vyacheslav
Adamanov adama...@gmail.com + * + * This program is free
software; you can redistribute it and/or modify it + * under the
terms of the GNU General Public License version 2 as published + *
by the Free Software Foundation. + */ + +#define pr_fmt(fmt)
sxtlite: fmt + +#include linux/phy.h +#include linux/delay.h
+#include linux/platform_device.h +#include
linux/ath9k_platform.h +#include linux/mtd/mtd.h +#include
linux/mtd/nand.h +#include linux/mtd/partitions.h +#include
linux/spi/spi.h +#include linux/spi/flash.h +#include
linux/rle.h +#include linux/routerboot.h +#include
linux/gpio.h + +#include asm/mach-ath79/ath79.h +#include
asm/mach-ath79/ar71xx_regs.h +#include common.h +#include
dev-ap9x-pci.h +#include dev-gpio-buttons.h +#include
dev-leds-gpio.h +#include dev-eth.h +#include dev-m25p80.h
+#include dev-nfc.h +#include dev-wmac.h +#include dev-usb.h
+#include machtypes.h +#include routerboot.h +#include
linux/ar8216_platform.h + +#define SXTLITE_GPIO_NAND_NCE 14
+#define SXTLITE_GPIO_LED_USER 3 +#define SXTLITE_GPIO_LED_1 13
+#define SXTLITE_GPIO_LED_2 12 +#define SXTLITE_GPIO_LED_3 4
+#define SXTLITE_GPIO_LED_4 21 +#define SXTLITE_GPIO_LED_5 18
+#define SXTLITE_GPIO_LED_POWER 11 + +#define SXTLITE_GPIO_BUZZER
19 + +#define SXTLITE_GPIO_BTN_RESET 15 + +#define
SXTLITE_KEYS_POLL_INTERVAL 20 +#define
SXTLITE_KEYS_DEBOUNCE_INTERVAL (3 * SXTLITE_KEYS_POLL_INTERVAL) +
+static struct mtd_partition rbsxtlite_nand_partitions[] = { +{ +
.name = booter, + .offset = 0, + .size = (256 * 1024),
+
.mask_flags = MTD_WRITEABLE, +}, +{ + .name =
kernel, +
.offset = (256 * 1024), +
Re: [OpenWrt-Devel] [PATCH] lantiq: make loading pci fixup data from cal_data work again
On 17/06/2014 19:06, Ben Mulvihill wrote:
Changeset 40948 restored an older (and uglier!) version of the code
for reading the athxk calibration partition on lantiq xway boards.
As a result pci fixups stored in this partition are no longer
applied, breaking wireless on the BTHOMEHUBV2B and (I imagine) on
the DGN3500. This is a minimal patch to restore this functionality
for ath9k without reverting any of the other changes in changeset
40948.
Note for John Crispin: I guess you won't want to apply this patch
if you are planning to check changeset 40948 anyway yourself. I
produced it for my own use and thought I might as well send it in
in case it was any use to anyone.
Ben Mulvihill
thanks for looking into this. looks like you picked up the missing
pieces. i am building a test image just now with this patch applied on
top of trunk. i managed to find a dgn3500 last night and will pick it
up in an hour. if this work, i will simply merge your patch and hope
that all boards are now working. once BB is out the door i will rework
this code and make it aligned with the eep loading code used on
ralink/mtk.
John
--- a/arch/mips/lantiq/xway/ath_eep.c 2014-06-16 12:10:10.413893209
+0200 +++ b/arch/mips/lantiq/xway/ath_eep.c 2014-06-16
12:10:26.366264625 +0200 @@ -35,6 +35,7 @@ static int
ath9k_pci_plat_dev_init(struc return 0; }
+static int ath9k_eep_load; int __init of_ath9k_eeprom_probe(struct
platform_device *pdev) { struct device_node *np =
pdev-dev.of_node, *mtd_np; @@ -117,6 +118,13 @@ int __init
of_ath9k_eeprom_probe(struct ltq_pci_ath_fixup(pci_slot,
ath9k_pdata.eeprom_data);
dev_info(pdev-dev, pci slot: %u\n, pci_slot); +
if (ath9k_eep_load) { +struct pci_dev *d =
NULL; +while ((d =
pci_get_device(PCI_VENDOR_ID_ATHEROS, +
PCI_ANY_ID, d)) != NULL) +
pci_fixup_device(pci_fixup_early, d); +} + }
dev_info(pdev-dev, loaded ath9k eeprom\n); @@ -139,9 +147,22 @@
static struct platform_driver ath9k_eepr
static int __init of_ath9k_eeprom_init(void) { - return
platform_driver_probe(ath9k_eeprom_driver,
of_ath9k_eeprom_probe); +int ret =
platform_driver_probe(ath9k_eeprom_driver,
of_ath9k_eeprom_probe); + +if (ret) +
ath9k_eep_load = 1; + +return ret; +} + +static int __init
of_ath9k_eeprom_init_late(void) +{ +if (!ath9k_eep_load) +
return 0; +return
platform_driver_probe(ath9k_eeprom_driver,
of_ath9k_eeprom_probe); } -arch_initcall(of_ath9k_eeprom_init);
+late_initcall(of_ath9k_eeprom_init_late);
+subsys_initcall(of_ath9k_eeprom_init);
static int ath5k_pci_plat_dev_init(struct pci_dev *dev)
___ 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] [PATCH v3] lantiq: make zlib compression on ubifs the default for BTHOMEHUBV2B
On 20/06/2014 08:26, Ben Mulvihill wrote: On Fri, 2014-06-20 at 07:51 +0200, Ben Mulvihill wrote: On Thu, 2014-06-19 at 23:09 +0200, Ben Mulvihill wrote: Nand flash on the Home Hub 2B is 32M, so it makes sense at least for this board to use some sort of compression on ubifs. Of course anyone building trunk for themselves can choose whatever they want, but with a release coming up, I think compression should be the default in pre-built images. However, I have a question. Does it make sense for compression by default to be enabled/disabled on a board by board basis, or should it be the same for all lantiq targets, or perhaps all targets full stop? Thanks, Ben P.S. Sorry, missed the sign-off from the first one. Hi Ben, i had a look at this problem aswell and i think we should globally enable compression by default. i will ping felix about this and see what he has to say. John P.P.S. I'm not doing very well this time. Trying to do things in a hurry. v3 is the right one. Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com --- --- a/config/Config-images.in 2014-06-19 22:44:40.962240035 +0200 +++ b/config/Config-images.in 2014-06-19 19:48:15.508299173 +0200 @@ -158,6 +158,7 @@ menu Target Images choice prompt compression + default TARGET_UBIFS_COMPRESSION_ZLIB if TARGET_lantiq_xway_BTHOMEHUBV2B default TARGET_UBIFS_COMPRESSION_NONE depends on TARGET_ROOTFS_UBIFS help ___ 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] [PATCH 1/5] Fix stack overflow bug of uloop lua binding.
On 20/06/2014 13:31, xf...@credosemi.com wrote:
The static variable `state` in `lua/uloop.c` should be clean after
every callback.
Signed-off-by: Xiongfei(Alex) Guo xf...@credosemi.com ---
Hi,
just had a quick browse over the patches. looks good, the only nipick
i have is this
+static int ul_cancel(lua_State *L)
+{
+ uloop_end();
+ return 1;
+}
can we rename is to ul_end() and then also fix up {cancel,
ul_cancel} to use end instead of cancel. that way the apis have the
same names in lua and c. apart from that thanks for the patches, i
will give them a try later on and then merge them into the git.
John
lua/uloop.c | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/lua/uloop.c b/lua/uloop.c index 51f53c2..5922e04
100644 --- a/lua/uloop.c +++ b/lua/uloop.c @@ -43,6 +43,7 @@ static
void ul_timer_cb(struct uloop_timeout *t)
lua_getglobal(state, __uloop_cb); lua_rawgeti(state, -1,
tout-r); + lua_remove(state, -2); lua_call(state, 0, 0); }
@@ -133,6 +134,7 @@ static void ul_process_cb(struct uloop_process
*p, int ret) lua_getglobal(state, __uloop_cb); lua_rawgeti(state,
-1, proc-r); luaL_unref(state, -2, proc-r); + lua_remove(state,
-2); lua_pushinteger(state, ret 8); lua_call(state, 1, 0); }
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] ubinize autoresize flag for overlay partition on lantiq
no reason, send a patch please On 22/06/2014 10:12, Ben Mulvihill wrote: Hi, Is there any reason why the autoresize flag is not currently enabled for the rootfs_data partition in ubinize-overlay.cfg on lantiq? I have tried it and it seems to work fine. Thanks, Ben ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.
On 23/06/2014 20:22, Paul Blazejowski wrote: Hello list, Have found bug in the ubifs component when mounting images on wndr3700v4/4300 routers. This happens in trunk builds after r41130 but does not happen before r41118. Please take a look at bug https://dev.openwrt.org/ticket/16803 i have filed on this issue. Unfortunately i do not have any fixes for this but i am willing to test patches and debug in hopes of getting this fixed. On a side note, sysupgrade image for wndr4300 does work from the web interface on my 3700v4 router but the wndr3700v4 image does not. Guess one bugat a time ;-). cheerios, -paulb Hi, do you know how to build your own image and could you test a patch if i send one ? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.
On 24/06/2014 10:55, Adam Kuklycz wrote: Guys if you need a guinea pig for testing the WNDR4300’s I am happy to assist. Since introducing the sysupgrade features, upon a router reboot all settings are restored to factory defaults. ok, i'll look into it today. i think daniel already pushed a fix for this int the fstools tree. i'll give him a call in a sec to ask. as for 3700, we need to apply the same fixups to tit as we did to 4300. i'll look into this aswell. Also, is this mail list a channel that reaches most or all developers? yes ___ 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] [PATCH] Update MT7530 switch driver.
Hi,
On 21/06/2014 17:10, xf...@credosemi.com wrote:
From: Xiongfei Guo xf...@credosemi.com
- Support set VLAN ID of each vlan. - Support untag feature. -
Replace register address with C MACRO. - There are 8 ports for
MT7530 actually.
Signed-off-by: Xiongfei Guo xf...@credosemi.com
on which boards did you test this ? i want to give it a quick try on
the eval kit today before merging the patch. i have so far not seen
any boards in the wild with this switch
John
--- ...8-NET-MIPS-add-ralink-SoC-ethernet-driver.patch | 268
++--- 1 file changed, 186 insertions(+), 82
deletions(-)
diff --git
a/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
b/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
index 75f78bf..c8ec17c 100644
---
a/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
+++
b/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
@@ -2814,7 +2814,7 @@ Signed-off-by: John Crispin
blo...@openwrt.org +#endif --- /dev/null +++
b/drivers/net/ethernet/ralink/mt7530.c -@@ -0,0 +1,467 @@ +@@ -0,0
+1,571 @@ +/* + * This program is free software; you can
redistribute it and/or + * modify it under the terms of the GNU
General Public License @@ -2851,25 +2851,45 @@ Signed-off-by: John
Crispin blo...@openwrt.org +#include mt7530.h + +#define
MT7530_CPU_PORT 6 -+#define MT7530_NUM_PORTS7 ++#define
MT7530_NUM_PORTS 8 +#define MT7530_NUM_VLANS 16 -+#define
MT7530_NUM_VIDS 16 ++#define MT7530_MAX_VID 4095
++#define
MT7530_MIN_VID0 + -+#define REG_ESW_VLAN_VTCR 0x90 -+#define
REG_ESW_VLAN_VAWD10x94 -+#define REG_ESW_VLAN_VAWD2 0x98 ++/*
registers */ ++#define REG_ESW_VLAN_VTCR 0x90 ++#define
REG_ESW_VLAN_VAWD10x94 ++#define REG_ESW_VLAN_VAWD2
0x98
++#define REG_ESW_VLAN_VTIM(x)(0x100 + 4 * ((x) / 2)) ++ ++#define
REG_ESW_VLAN_VAWD1_IVL_MACBIT(30) ++#define
REG_ESW_VLAN_VAWD1_VTAG_ENBIT(28) ++#define
REG_ESW_VLAN_VAWD1_VALID BIT(0) ++ ++/* vlan egress mode */ ++enum
{ ++ ETAG_CTRL_UNTAG = 0, ++ ETAG_CTRL_TAG = 2, ++ ETAG_CTRL_SWAP =
1, ++ ETAG_CTRL_STACK = 3, ++}; + ++#define REG_ESW_PORT_PCR(x)
(0x2004 | ((x) 8)) ++#define REG_ESW_PORT_PVC(x) (0x2010 | ((x)
8)) ++#define REG_ESW_PORT_PPBV1(x)(0x2014 | ((x) 8)) +enum
{ + /* Global attributes. */ + MT7530_ATTR_ENABLE_VLAN, +}; +
-+struct mt7530_port { ++struct mt7530_port_entry { + u16 pvid;
+}; + -+struct mt7530_vlan { -+ u8 ports; ++struct
mt7530_vlan_entry { ++u16 vid; ++ u8 member; ++ u8
etags; +}; +
+struct mt7530_priv { @@ -2878,23 +2898,29 @@ Signed-off-by: John
Crispin blo...@openwrt.org +struct switch_dev swdev; + +
bool
global_vlan_enable; -+struct mt7530_vlan
vlans[MT7530_NUM_VLANS];
-+struct mt7530_port ports[MT7530_NUM_PORTS]; ++ struct
mt7530_vlan_entry vlan_entries[MT7530_NUM_VLANS]; ++ struct
mt7530_port_entry port_entries[MT7530_NUM_PORTS]; +}; + +struct
mt7530_mapping { +char*name; -+ u8 pvids[6]; -+u8
vlans[8]; ++
u16 pvids[MT7530_NUM_PORTS]; ++ u8 members[MT7530_NUM_VLANS]; ++
u8
etags[MT7530_NUM_VLANS]; ++ u16 vids[MT7530_NUM_VLANS]; +}
mt7530_defaults[] = { + { + .name = w, -+
.pvids = { 1, 1,
1, 1, 2, 1 }, -+ .vlans = { 0, 0x6f, 0x50 }, ++ .pvids
= { 1, 1,
1, 1, 2, 1, 1 }, ++ .members = { 0x6f, 0x50 }, ++ .etags
= {
0x40, 0x40 }, ++ .vids = { 1, 2 }, + }, { + .name =
w, -+
.pvids = { 2, 1, 1, 1, 1, 1 }, -+ .vlans = { 0, 0x7e, 0x41 }, ++
.pvids = { 2, 1, 1, 1, 1, 1, 1 }, ++ .members = { 0x7e, 0x41 }, ++
.etags = { 0x40, 0x40 }, ++ .vids = { 1, 2 }, + }, +}; + @@
-2921,10 +2947,14 @@ Signed-off-by: John Crispin
blo...@openwrt.org + + mt7530-global_vlan_enable = 1; + -+for
(i = 0; i 6; i++) -+mt7530-ports[i].pvid = map-pvids[i];
-+
for (i = 0; i 8; i++) -+mt7530-vlans[i].ports =
map-vlans[i]; ++ for (i = 0; i MT7530_NUM_PORTS; i++) ++
mt7530-port_entries[i].pvid = map-pvids[i]; ++ ++ for (i = 0; i
MT7530_NUM_VLANS; i++) { ++ mt7530-vlan_entries[i].member =
map-members[i]; ++ mt7530-vlan_entries[i].etags =
map-etags[i]; ++ mt7530-vlan_entries[i].vid = map-vids[i]; ++
} +} + +static int @@ -2932,8 +2962,8 @@ Signed-off-by: John
Crispin blo...@openwrt.org +{ + struct mt7530_priv *priv =
container_of(dev, struct mt7530_priv, swdev); + -+
memset(priv-ports, 0, sizeof(priv-ports)); -+ memset(priv-vlans,
0, sizeof(priv-vlans)); ++ memset(priv-port_entries, 0
Re: [OpenWrt-Devel] [PATCH v2 1/3] ar71xx: add kernel support for the EnGenius ESR900
Hi,
On 22/06/2014 22:20, Forest Crossman wrote:
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/nvram.c
b/target/linux/ar71xx/files/arch/mips/ath79/nvram.c index
43911b8..41c3542 100644 ---
a/target/linux/ar71xx/files/arch/mips/ath79/nvram.c +++
b/target/linux/ar71xx/files/arch/mips/ath79/nvram.c @@ -16,6
+16,21 @@
#include nvram.h
+char *ath79_nvram_sanitize_mac(char *input) +{ + int i,j; + char
*output=input; + for (i = 0, j = 0; istrlen(input); i++,j++) + {
+ if (input[i]!='\') + output[j]=input[i]; +
else + j--; + }
+ output[j]=0; + return output; +} + char
*ath79_nvram_find_var(const char *name, const char *buf, unsigned
buf_len) { unsigned len = strlen(name);
this loop is a bit weird. ca you tell us in what way the mac is broken
on your board ?
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Update MT7530 switch driver.
On 24/06/2014 15:54, Xiongfei(Alex) GUO wrote:
hi,
I'm test it on Mercury MW305R with a modified dts file for
RT-N14U. Maybe I can give a dts patch for this board later.
Actually, MT7530 is the ethernet switch inside the MTK MT7620A/N.
So you can try it with any MT7620 based board.
it is also the ip core inside the external chip and its inside the
mt7621. that is why i ask, testing on mt7620 only is not enough we need
to test a few more boards.
DTS file patches are welcome ...
thanks for the info i hope to look at this the next 2 days
John
Xiongfei Guo Credo Semi.
On Tue, Jun 24, 2014 at 8:54 PM, John Crispin j...@phrozen.org
mailto:j...@phrozen.org wrote:
Hi,
On 21/06/2014 17:10, xf...@credosemi.com
mailto:xf...@credosemi.com wrote:
From: Xiongfei Guo xf...@credosemi.com
mailto:xf...@credosemi.com
- Support set VLAN ID of each vlan. - Support untag feature. -
Replace register address with C MACRO. - There are 8 ports for
MT7530 actually.
Signed-off-by: Xiongfei Guo xf...@credosemi.com
mailto:xf...@credosemi.com
on which boards did you test this ? i want to give it a quick try
on the eval kit today before merging the patch. i have so far not
seen any boards in the wild with this switch
John
--- ...8-NET-MIPS-add-ralink-SoC-ethernet-driver.patch | 268
++--- 1 file changed, 186 insertions(+), 82
deletions(-)
diff --git
a/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
b/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
index 75f78bf..c8ec17c 100644
---
a/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
+++
b/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
@@ -2814,7 +2814,7 @@ Signed-off-by: John Crispin
blo...@openwrt.org mailto:blo...@openwrt.org +#endif ---
/dev/null +++
b/drivers/net/ethernet/ralink/mt7530.c -@@ -0,0 +1,467 @@ +@@
-0,0 +1,571 @@ +/* + * This program is free software; you can
redistribute it and/or + * modify it under the terms of the GNU
General Public License @@ -2851,25 +2851,45 @@ Signed-off-by:
John Crispin blo...@openwrt.org mailto:blo...@openwrt.org
+#include
mt7530.h + +#define
MT7530_CPU_PORT 6 -+#define MT7530_NUM_PORTS7
++#define
MT7530_NUM_PORTS 8 +#define MT7530_NUM_VLANS 16
-+#define MT7530_NUM_VIDS 16 ++#define
MT7530_MAX_VID
4095 ++#define
MT7530_MIN_VID0 + -+#define REG_ESW_VLAN_VTCR
0x90
-+#define
REG_ESW_VLAN_VAWD10x94 -+#define REG_ESW_VLAN_VAWD2
0x98
++/*
registers */ ++#define REG_ESW_VLAN_VTCR 0x90
++#define REG_ESW_VLAN_VAWD10x94 ++#define
REG_ESW_VLAN_VAWD2
0x98
++#define REG_ESW_VLAN_VTIM(x)(0x100 + 4 * ((x) / 2)) ++
++#define
REG_ESW_VLAN_VAWD1_IVL_MACBIT(30) ++#define
REG_ESW_VLAN_VAWD1_VTAG_ENBIT(28) ++#define
REG_ESW_VLAN_VAWD1_VALID BIT(0) ++ ++/* vlan egress mode */
++enum
{ ++ ETAG_CTRL_UNTAG = 0, ++ ETAG_CTRL_TAG = 2, ++
ETAG_CTRL_SWAP =
1, ++ ETAG_CTRL_STACK = 3, ++}; + ++#define REG_ESW_PORT_PCR(x)
(0x2004 | ((x) 8)) ++#define REG_ESW_PORT_PVC(x) (0x2010 |
((x) 8)) ++#define REG_ESW_PORT_PPBV1(x)(0x2014 | ((x)
8)) +enum
{ + /* Global attributes. */ + MT7530_ATTR_ENABLE_VLAN,
+}; + -+struct mt7530_port { ++struct mt7530_port_entry { + u16
pvid; +}; + -+struct mt7530_vlan { -+ u8 ports;
++struct mt7530_vlan_entry { ++u16 vid; ++ u8
member; ++
u8 etags; +}; +
+struct mt7530_priv { @@ -2878,23 +2898,29 @@ Signed-off-by:
John Crispin blo...@openwrt.org mailto:blo...@openwrt.org +
struct switch_dev swdev; + + bool
global_vlan_enable; -+struct mt7530_vlan
vlans[MT7530_NUM_VLANS];
-+struct mt7530_port ports[MT7530_NUM_PORTS]; ++
struct mt7530_vlan_entry vlan_entries[MT7530_NUM_VLANS]; ++
struct mt7530_port_entry port_entries[MT7530_NUM_PORTS]; +};
+ +struct mt7530_mapping { +char*name; -+ u8
pvids[6]; -+
u8 vlans[8]; ++
u16 pvids[MT7530_NUM_PORTS]; ++ u8
members[MT7530_NUM_VLANS]; ++ u8
etags[MT7530_NUM_VLANS]; ++ u16 vids[MT7530_NUM_VLANS]; +}
mt7530_defaults[] = { + { + .name = w,
-+
.pvids = { 1, 1,
1, 1, 2, 1 }, -+ .vlans = { 0, 0x6f, 0x50 }, ++
.pvids = { 1, 1,
1, 1, 2, 1, 1 }, ++ .members = { 0x6f, 0x50 }, ++
.etags = {
0x40, 0x40 }, ++ .vids = { 1, 2 }, + }, { +
.name = w, -+
.pvids = { 2, 1, 1, 1, 1, 1 }, -+ .vlans = { 0,
0x7e,
0x41 }, ++
.pvids = { 2, 1, 1, 1, 1, 1, 1 }, ++ .members = { 0x7e,
0x41 }, ++
.etags = { 0x40, 0x40 }, ++ .vids = { 1, 2 }, + },
+}; + @@
-2921,10 +2947,14 @@ Signed-off-by: John Crispin
blo...@openwrt.org mailto:blo...@openwrt.org + +
mt7530-global_vlan_enable
Re: [OpenWrt-Devel] [PATCH] Update MT7530 switch driver.
Hi, thanks for the patch, i just tested it on the external switch and it works there as well (but you already knew that i guess :-) ). i added the patch to my local queue and will push later on today. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.
Hi, On 23/06/2014 20:22, Paul Blazejowski wrote: Hello list, Have found bug in the ubifs component when mounting images on wndr3700v4/4300 routers. This happens in trunk builds after r41130 but does not happen before r41118. Please take a look at bug https://dev.openwrt.org/ticket/16803 i have filed on this issue. Unfortunately i do not have any fixes for this but i am willing to test patches and debug in hopes of getting this fixed. looking at that log it looks like you flashed different to me :) do you perhaps use the recovery method ? i am currently using an initramfs which i boot and then i sysupgrade from there. because of this i dont see the 0xdeadc0de that you see as it is only in the ubi file -- echo -ne '\xde\xad\xc0\xde' $(KDIR_TMP)/jffs2.eof $(call ubinize,ubinize-$(9).ini,$(KDIR_TMP),$(KDIR_TMP)/$(2)-root.ubi,128KiB,2048,-E 5) however to test further i need to know how you flashed :) John On a side note, sysupgrade image for wndr4300 does work from the web interface on my 3700v4 router but the wndr3700v4 image does not. Guess one bugat a time ;-). cheerios, -paulb ___ 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] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.
On 24/06/2014 22:25, Paul Blazejowski wrote: Hi again, thanks for the tftp fix, flushing just became so much faster and easier. Tested trunk r41336 after your jffs2 fix and the image boots fine, restored my configuration changes, rebooted the router and all changes are saved now. I will post the working dmesg to the ticket at https://dev.openwrt.org/ticket/16840 but it is safe to say that you can close it ;-) now. Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this is next on the list... i tested 4300 and it works. you need to use the *-ubi-sysupgrade.tar file. Thank you, -paul On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote: On 24/06/2014 19:05, Paul Blazejowski wrote: John, Yes i use the reset with pin and from there i tftp the original firmware from netgear after that i go to the gui and upload the open-wrt image because the router will not accept the wndr3700v4 image (there's a cosmetic fix for that, i created a patch that someone from the forums has sent months ago to this list but it was never accepted...) https://dev.openwrt.org/ticket/16840 With that patch tftp'ing the openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need to flash the original firmware. If there's another method that can be used to flash the image(s) please let me know i would want to try any alternative ways of flashing and could learn a thing or two in the process as well ;-) Thank you, -paul Hi, i just pushed the V vs v fix and another fix that removes the jffs2 magic. i think this might have been the cause of the problems. please retry with current trunk and let me know if the problem is gone or still there 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 mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.
On 24/06/2014 22:43, Paul Blazejowski wrote: i get The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform. from web interface. this is what i have: -rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58 bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar should i push it from shell using sysupgrade script? it will work from shell, i will look into why it fails via webui. thanks! On Tue, 2014-06-24 at 22:32 +0200, John Crispin wrote: On 24/06/2014 22:25, Paul Blazejowski wrote: Hi again, thanks for the tftp fix, flushing just became so much faster and easier. Tested trunk r41336 after your jffs2 fix and the image boots fine, restored my configuration changes, rebooted the router and all changes are saved now. I will post the working dmesg to the ticket at https://dev.openwrt.org/ticket/16840 but it is safe to say that you can close it ;-) now. Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this is next on the list... i tested 4300 and it works. you need to use the *-ubi-sysupgrade.tar file. Thank you, -paul On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote: On 24/06/2014 19:05, Paul Blazejowski wrote: John, Yes i use the reset with pin and from there i tftp the original firmware from netgear after that i go to the gui and upload the open-wrt image because the router will not accept the wndr3700v4 image (there's a cosmetic fix for that, i created a patch that someone from the forums has sent months ago to this list but it was never accepted...) https://dev.openwrt.org/ticket/16840 With that patch tftp'ing the openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need to flash the original firmware. If there's another method that can be used to flash the image(s) please let me know i would want to try any alternative ways of flashing and could learn a thing or two in the process as well ;-) Thank you, -paul Hi, i just pushed the V vs v fix and another fix that removes the jffs2 magic. i think this might have been the cause of the problems. please retry with current trunk and let me know if the problem is gone or still there 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 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] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.
Hi, can someone with a 3700v4 run cat /tmp/sysinfo/* on a 3700 ? the sysupgrade fails because the board id is not added yet in the upgrade script. however i fail to figure out what id it gets from the ar71xx.sh script John On 25/06/2014 06:27, Adam Kuklycz wrote: Hi all, I've flashed my Netgear WNDR4300 with trunk r41336 and have run a series of tests. Everything looks great! I can restore backed up settings, I can configure it from scratch too should I desire. Sysupgrade works fine on my WNDR4300 via the web UI. Paul if you're still having issues with this on your WNDR3700v4 it may be specific to that model; I do not have one of these to test on unfortunately. But sysupgrade on the WNDR4300 works and works well. All settings are kept when sysupgrading too. If it helps Paul out I can email him my config file, write me directly for it; that should eliminate any mistakes that have been overlooked. Easy to do. Will run the router for a few hours on the test bench and do some traffic through it, should that play nice then it's problems resolved on my end :) Cheers Adam On 25/06/14 13:14, Paul Blazejowski wrote: Adam, what do you know? hehehe when one sleeps another fixes things ;-) so far so good, my router has been up for few hours without problems... there's still issue with the sysupgrade image that John is already aware of ... and may have a fix for us to test ... one fix at a time they say. glad we made much progress today! thank you all! On Wed, 2014-06-25 at 00:07 +, Adam Kuklycz wrote: Geez, it must be true that you should only sleep when you're dead...damn Aussie time zones... I'll test with latest trunk as well will confirm. But looks promising! -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Paul Blazejowski Sent: Wednesday, 25 June 2014 6:27 AM To: John Crispin Cc: openwrt-devel@lists.openwrt.org Subject: Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300. sorry i meant https://dev.openwrt.org/ticket/16803 the previous one is closed for good ;-) On Tue, 2014-06-24 at 16:25 -0400, Paul Blazejowski wrote: Hi again, thanks for the tftp fix, flushing just became so much faster and easier. Tested trunk r41336 after your jffs2 fix and the image boots fine, restored my configuration changes, rebooted the router and all changes are saved now. I will post the working dmesg to the ticket at https://dev.openwrt.org/ticket/16840 but it is safe to say that you can close it ;-) now. Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this is next on the list... Thank you, -paul On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote: On 24/06/2014 19:05, Paul Blazejowski wrote: John, Yes i use the reset with pin and from there i tftp the original firmware from netgear after that i go to the gui and upload the open-wrt image because the router will not accept the wndr3700v4 image (there's a cosmetic fix for that, i created a patch that someone from the forums has sent months ago to this list but it was never accepted...) https://dev.openwrt.org/ticket/16840 With that patch tftp'ing the openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need to flash the original firmware. If there's another method that can be used to flash the image(s) please let me know i would want to try any alternative ways of flashing and could learn a thing or two in the process as well ;-) Thank you, -paul Hi, i just pushed the V vs v fix and another fix that removes the jffs2 magic. i think this might have been the cause of the problems. please retry with current trunk and let me know if the problem is gone or still there 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 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] [PATCH 2/2] busybox: use ntp enabled config option
On 26/06/2014 14:31, Bastian Bittorf wrote: * Luka Perkov l...@openwrt.org [26.06.2014 14:24]: +[ $enabled = 0 ] return This can also be 'true' or 'false' or 'disabled'. I see, that other packages are also doing it like this, but i remeber there was an uci-thingy() doing that, wasn't it? bye, bastian config_get_bool ... however there is not equivalent for the validate api so far. ___ 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] Resend patch to fix Support For Aztech GR7000
Hi,
i will postpone this patch till after BB. we will at that point fix up
the eep handling properly and merge/share the patches between ralink
and lantiq.
do you know if all the boards have the same eep in the filesystem or do
they differ between units ?
John
On 27/06/2014 19:05, Alpha Sparc wrote:
Move the Ralink EEPROM node into the PCI node to remove wmac
failed to load eeprom property message
---
a/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
+++ b/target/linux/lantiq/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom
@@ -41,6 +41,9 @@ case $FIRMWARE in ARV7525PW)
rt2x00_eeprom_extract board_config 1040 512 0 ;; +GR7000) +
rt2x00_eeprom_extract board_config 0 512 0 +;; *)
rt2x00_eeprom_die board $board is not supported yet ;;
--- a/target/linux/lantiq/base-files/etc/uci-defaults/02_network
+++ b/target/linux/lantiq/base-files/etc/uci-defaults/02_network @@
-128,8 +128,12 @@ DGN3500*) ;;
GR7000) -ucidef_set_interface_wan eth0 -uci set
network.lan.ifname='' +lan_mac=$(mtd_get_mac_ascii uboot_env
ethaddr) +wan_mac=$(macaddr_add $lan_mac 3) +
ucidef_set_interfaces_lan_wan eth0.1 eth0.2 +
ucidef_add_switch switch0 1 1 +ucidef_add_switch_vlan
switch0 1 0t 1 2 3 4 +ucidef_add_switch_vlan switch0
2 0t 5 ;;
H201L) @@ -167,13 +171,23 @@ BTHOMEHUBV2B) ;; esac
-[ -z $(ls /lib/modules/`uname -r`/ltq_atm*) ] || set_atm_wan
$vpi $vci $encaps $payload +board=$(lantiq_board_id) +
+case $board in
-if [ -n $(grep system type.*: VR9 /proc/cpuinfo) ]; then -
set_vdsl_modem $annex /lib/firmware/vdsl.bin av ptm -else -
set_adsl_modem $annex /lib/firmware/adsl.bin -fi +GR7000) +
;; + +*) +[ -z $(ls /lib/modules/`uname -r`/ltq_atm*) ] ||
set_atm_wan $vpi $vci $encaps $payload + +if [ -n
$(grep system type.*: VR9 /proc/cpuinfo) ]; then +
set_vdsl_modem $annex /lib/firmware/vdsl.bin av ptm +
else +set_adsl_modem $annex /lib/firmware/adsl.bin +
fi +;; +esac
[ -n $lan_mac ] ucidef_set_interface_macaddr lan $lan_mac [ -n
$wan_mac ] ucidef_set_interface_macaddr wan $wan_mac
---
a/target/linux/lantiq/base-files/etc/uci-defaults/03_wireless-wps
+++
b/target/linux/lantiq/base-files/etc/uci-defaults/03_wireless-wps
@@ -8,7 +8,7 @@ set_wps() {
board=$(lantiq_board_id) case $board in -WBMR) +WBMR|GR7000)
config_load wireless config_foreach set_wps wifi-iface uci commit
wireless
--- a/target/linux/lantiq/xway/profiles/aztech.mk +++
b/target/linux/lantiq/xway/profiles/aztech.mk @@ -2,6 +2,7 @@
define Profile/GR7000 NAME:=Aztech GR7000 PACKAGES:= \
kmod-ltq-deu-ar9 kmod-ltq-hcd-ar9 \ +kmod-rt2800-pci wpad \
swconfig endef $(eval $(call Profile,GR7000))
--- a/target/linux/lantiq/dts/GR7000.dts +++
b/target/linux/lantiq/dts/GR7000.dts @@ -3,7 +3,7 @@ /include/
ar9.dtsi
/ { -model = GR7000 - Aztech GR7000; +model = Aztech
GR7000;
chosen { bootargs = console=ttyLTQ0,115200 init=/etc/preinit; @@
-18,7 +18,7 @@ nor-boot@0 { compatible = lantiq,nor; bank-width =
2; -reg = 0 0x0 0x200; +reg
= 0 0x0 0x80; #address-cells = 1; #size-cells = 1;
@@ -29,16 +29,24 @@ };
partition@2 { -label = uboot_env; -
reg = 0x2 0x1; +label = firmware; +
reg = 0x2 0x7b; +}; + +
partition@7e { +label = board_config; +
reg = 0x7e 0x1; read-only; };
-partition@3 { -label =
firmware; -reg = 0x3 0x7d; +
partition@7f { +label = uboot_env; +
reg = 0x7f 0x1; +read-only; }; + };
+ };
gpio: pinmux@E100B10 { @@ -70,12 +78,25 @@ }; };
+etop@E18 { +phy-mode = rgmii; +
}; + ifxhcd@E101000 { status = okay; +gpios = gpio
5 0 +gpio 14 0; +lantiq,portmask =
0x3; };
pci@E105400 { status = okay; + +ralink_eep { +
compatible = ralink,eeprom; +ralink,eeprom =
RT2860.eeprom; +}; + };
stp: stp@E100BB0 { ___
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] [PATCH v4] ar71xx: Add support for MikroTik RouterBOARD SXT Lite
On 26/06/2014 21:47, Matthew Reeve wrote:
This patch adds support for the MikroTik RouterBOARD SXT Lite.
The new RB911L series is also supported as a result.
v2 of this patch fixes the wmac offset to match what is on the
sticker. v3 refreshes the patch against r41148 and defines the
power led as the status led in diag.sh v4 refreshes the patch
against r41353 and fixes the patch path issue to make git am work
correctly
Signed-off-by: Matthew Reeve mre...@tenxnetworks.com
Hi,
while trying to merge this i noticed that this router board is not
part of the mikrotik profile. why is this so ? looking at the platform
code, you do register a nand driver so the generic profile seems incorrect
John
---
trunk/target/linux/ar71xx/patches-3.10/713-MIPS-ath79-add-RBSXTLite-support.patch
2014-05-12 18:49:06.902842033 + +++
trunk/target/linux/ar71xx/patches-3.10/713-MIPS-ath79-add-RBSXTLite-support.patch
2014-05-21 20:34:52.209118569 + @@ -0,0 +1,38 @@ +---
a/arch/mips/ath79/Kconfig 2014-05-21 20:25:24.801106234 +
b/arch/mips/ath79/Kconfig 2014-05-21 20:28:20.489109814 + +@@
-462,6 +462,14 @@ config ATH79_MACH_RB2011 + select
ATH79_ROUTERBOOT +select RLE_DECOMPRESS + ++config
ATH79_MACH_RBSXTLITE ++ bool MikroTik RouterBOARD SXT Lite ++
select SOC_AR934x ++ select ATH79_DEV_ETH ++ select ATH79_DEV_NFC
++select ATH79_DEV_WMAC ++select ATH79_ROUTERBOOT ++ + config
ATH79_MACH_WNDAP360 + bool NETGEAR WNDAP360 board support +
select SOC_AR71XX +--- a/arch/mips/ath79/machtypes.h 2014-05-21
20:25:24.801106234 + b/arch/mips/ath79/machtypes.h
2014-05-21 20:30:04.829111865 + +@@ -93,6 +93,8 @@ enum
ath79_mach_type { + ATH79_MACH_RB_2011G,/* Mikrotik RouterBOARD
2011UAS-2HnD */ + ATH79_MACH_RB_2011L,/* Mikrotik RouterBOARD
2011L */ +ATH79_MACH_RB_2011US, /* Mikrotik RouterBOARD 2011UAS
*/ ++ ATH79_MACH_RB_SXTLITE2ND, /* Mikrotik RouterBOARD SXT Lite
2nD */ ++ ATH79_MACH_RB_SXTLITE5ND, /* Mikrotik RouterBOARD SXT
Lite 5nD */ + ATH79_MACH_RW2458N, /* Redwave RW2458N */ +
ATH79_MACH_TEW_632BRP,/* TRENDnet TEW-632BRP */ +
ATH79_MACH_TEW_673GRU,/* TRENDnet TEW-673GRU */ +---
a/arch/mips/ath79/Makefile2014-05-21 20:25:24.801106234 +
b/arch/mips/ath79/Makefile2014-05-21 20:31:37.169113830 + +@@
-85,6 +85,7 @@ obj-$(CONFIG_ATH79_MACH_RB750) += mach- +
obj-$(CONFIG_ATH79_MACH_RB91X)+= mach-rb91x.o +
obj-$(CONFIG_ATH79_MACH_RB95X)+= mach-rb95x.o +
obj-$(CONFIG_ATH79_MACH_RB2011) += mach-rb2011.o
++obj-$(CONFIG_ATH79_MACH_RBSXTLITE) += mach-rbsxtlite.o +
obj-$(CONFIG_ATH79_MACH_RW2458N) += mach-rw2458n.o +
obj-$(CONFIG_ATH79_MACH_TEW_632BRP) += mach-tew-632brp.o +
obj-$(CONFIG_ATH79_MACH_TEW_673GRU) += mach-tew-673gru.o ---
trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-rbsxtlite.c
2014-05-12 18:49:06.902842033 + +++
trunk/target/linux/ar71xx/files/arch/mips/ath79/mach-rbsxtlite.c
2014-05-21 19:50:48.073064837 + @@ -0,0 +1,238 @@ +/* + *
MikroTik RouterBOARD SXT Lite support + * + * Copyright (C) 2012
Stijn Tintel st...@linux-ipv6.be + * Copyright (C) 2012 Gabor
Juhos juh...@openwrt.org + * Copyright (C) 2013 Vyacheslav
Adamanov adama...@gmail.com + * + * This program is free
software; you can redistribute it and/or modify it + * under the
terms of the GNU General Public License version 2 as published + *
by the Free Software Foundation. + */ + +#define pr_fmt(fmt)
sxtlite: fmt + +#include linux/phy.h +#include
linux/delay.h +#include linux/platform_device.h +#include
linux/ath9k_platform.h +#include linux/mtd/mtd.h +#include
linux/mtd/nand.h +#include linux/mtd/partitions.h +#include
linux/spi/spi.h +#include linux/spi/flash.h +#include
linux/rle.h +#include linux/routerboot.h +#include
linux/gpio.h + +#include asm/mach-ath79/ath79.h +#include
asm/mach-ath79/ar71xx_regs.h +#include common.h +#include
dev-ap9x-pci.h +#include dev-gpio-buttons.h +#include
dev-leds-gpio.h +#include dev-eth.h +#include dev-m25p80.h
+#include dev-nfc.h +#include dev-wmac.h +#include dev-usb.h
+#include machtypes.h +#include routerboot.h +#include
linux/ar8216_platform.h + +#define SXTLITE_GPIO_NAND_NCE 14
+#define SXTLITE_GPIO_LED_USER 3 +#define SXTLITE_GPIO_LED_1 13
+#define SXTLITE_GPIO_LED_2 12 +#define SXTLITE_GPIO_LED_3 4
+#define SXTLITE_GPIO_LED_4 21 +#define SXTLITE_GPIO_LED_5 18
+#define SXTLITE_GPIO_LED_POWER 11 + +#define SXTLITE_GPIO_BUZZER
19 + +#define SXTLITE_GPIO_BTN_RESET 15 + +#define
SXTLITE_KEYS_POLL_INTERVAL 20 +#define
SXTLITE_KEYS_DEBOUNCE_INTERVAL (3 * SXTLITE_KEYS_POLL_INTERVAL) +
+static struct mtd_partition rbsxtlite_nand_partitions[] = { +{ +
.name = booter, + .offset = 0, + .size = (256 * 1024),
+
Re: [OpenWrt-Devel] [PATCH 1/3] [ubox] validate: fix indentation
Hi,
blogic@debian:/openwrt/ubox$ git am 5748
Applying: validate: fix indentation
blogic@debian:/openwrt/ubox$ git am 5749
Applying: validate: fix indentation
error: patch failed: validate/validate.c:882
error: validate/validate.c: patch does not apply
Patch failed at 0001 validate: fix indentation
When you have resolved this problem run git am --resolved.
If you would prefer to skip this patch, instead run git am --skip.
To restore the original branch and stop patching run git am --abort.
blogic@debian:/openwrt/ubox$ git am --abort
blogic@debian:/openwrt/ubox$ patch -p1 5749
patching file validate/validate.c
Reversed (or previously applied) patch detected! Assume -R? [n] n
Apply anyway? [n] y
Hunk #1 FAILED at 882.
1 out of 1 hunk FAILED -- saving rejects to file validate/validate.c.rej
blogic@debian:/openwrt/ubox$
On 27/06/2014 11:09, Luka Perkov wrote:
Signed-off-by: Luka Perkov l...@openwrt.org ---
validate/validate.c | 88
++--- 1 file
changed, 44 insertions(+), 44 deletions(-)
diff --git a/validate/validate.c b/validate/validate.c index
150c08d..f550e76 100644 --- a/validate/validate.c +++
b/validate/validate.c @@ -882,50 +882,50 @@ dt_type_uci(struct
dt_state *s, int nargs)
static struct dt_fun dt_types[] = { - { or,
DT_INVALID,
dt_type_or}, -{ and,
DT_INVALID, dt_type_and }, -{
not,DT_INVALID, dt_type_not
}, -{ neg,DT_INVALID,
dt_type_neg }, -{ list,
DT_INVALID, dt_type_list}, -{
min,DT_NUMBER, dt_type_min
}, -{ max,DT_NUMBER,
dt_type_max }, -{ range,
DT_NUMBER, dt_type_range }, -{
minlength, DT_STRING, dt_type_minlen }, -
{ maxlength,
DT_STRING,dt_type_maxlen }, -{ rangelength,
DT_STRING,
dt_type_rangelen }, -{ integer,DT_NUMBER,
dt_type_int }, -
{ uinteger, DT_NUMBER, dt_type_uint}, -
{ float,
DT_NUMBER,dt_type_float }, -{ ufloat,
DT_NUMBER,
dt_type_ufloat}, -{ bool,
DT_BOOL,dt_type_bool}, -{
string, DT_STRING, dt_type_string
}, -{ hexstring,
DT_STRING,dt_type_hexstring }, -{ ip4addr,
DT_STRING,
dt_type_ip4addr }, -{ ip6addr,DT_STRING,
dt_type_ip6addr
}, - { ipaddr, DT_STRING, dt_type_ipaddr
}, -{ cidr4,
DT_STRING,dt_type_cidr4 }, -{ cidr6,
DT_STRING,
dt_type_cidr6 }, -{ cidr, DT_STRING,
dt_type_cidr}, -{
netmask4, DT_STRING, dt_type_netmask4}, -
{ netmask6,
DT_STRING,dt_type_netmask6}, -{ ipmask4,
DT_STRING,
dt_type_ipmask4 }, -{ ipmask6,DT_STRING,
dt_type_ipmask6
}, - { ipmask, DT_STRING, dt_type_ipmask
}, -{ port,
DT_NUMBER,dt_type_port}, -{ portrange,
DT_STRING,
dt_type_portrange }, -{ macaddr,DT_STRING,
dt_type_macaddr
}, - { uciname,DT_STRING, dt_type_uciname
}, -{ wpakey,
DT_STRING,dt_type_wpakey }, -{ wepkey,
DT_STRING,
dt_type_wepkey}, -{ hostname, DT_STRING,
dt_type_hostname
}, - { host, DT_STRING, dt_type_host
}, -{ network,
DT_STRING,dt_type_network }, -{ phonedigit,
DT_STRING,
dt_type_phonedigit}, -{ directory, DT_STRING,
dt_type_directory }, -{ device, DT_STRING,
dt_type_device
}, - { file, DT_STRING, dt_type_file
}, -{ regex,
DT_STRING,dt_type_regex }, -{ uci,
DT_STRING, dt_type_uci
}, + { or, DT_INVALID, dt_type_or }, +
{ and,DT_INVALID,
dt_type_and }, +{ not,DT_INVALID,
dt_type_not }, +{ neg,
DT_INVALID, dt_type_neg }, +{ list,
Re: [OpenWrt-Devel] [Patch] Support for BMP085 pressure sensor
Hi, comments inline On 29/06/2014 10:13, Sergey Korolew wrote: Hello ! Bosch Sensortec is one of most popular pressure sensors for building home weather stations, its cheap and easy to use. I decided to add two packages for each bus type because device usually have only one barometer and we does no need to waste firmware space for unused bus. Tested on trunk, ar71xx (ML2030) with kernel 3.10, i2c only (due absent of spi version), but I added patch files for all current kernels. === --- a/target/linux/generic/patches-3.6/263-bmp085_dynamic.patch 1970-01-01 04:00:00.0 +0400 +++ b/target/linux/generic/patches-3.6/263-bmp085_dynamic.patch 2014-06-08 14:42:38.0 +0400 @@ -0,0 +1,11 @@ +--- a/drivers/misc/Kconfig2014-04-03 23:01:22.0 +0400 b/drivers/misc/Kconfig2014-06-08 14:40:09.129048438 +0400 +@@ -453,7 +453,7 @@ + still useful. + + config BMP085 +-bool ++ tristate BMP085 digital pressure sensor generic support + depends on SYSFS + i just had a look at the kernel Kconfig and it seems weird that the actual driver is bool while the busses are tristate. i would like to not carry your patches in trunk for future releases, so could please send this upstream aswell ? --- a/package/kernel/linux/modules/other.mk 2014-05-30 13:53:34.0 +0400 +++ b/package/kernel/linux/modules/other.mk 2014-06-08 16:47:48.315028290 +0400 @@ -698,6 +698,43 @@ $(eval $(call KernelPackage,regmap)) +define KernelPackage/bmp085-i2c + SUBMENU:=$(OTHER_MENU) + TITLE:=BMP085 digital pressure sensor on I2C + KCONFIG:=CONFIG_BMP085_I2C \ + CONFIG_BMP085 + DEPENDS:=+kmod-regmap + FILES:= \ + $(LINUX_DIR)/drivers/misc/bmp085-i2c.ko \ + $(LINUX_DIR)/drivers/misc/bmp085.ko + AUTOLOAD:=$(call AutoLoad,55,bmp085 bmp085-i2c) +endef please make bmp085.ko an extra package. it does not need the AUTOLOAD line. and for the i2c and spi package use AutoProbe instead of AutoLoad, that will tell kmodloader to figure out itself, that bmp085.ko needs to be loaded. John + +define KernelPackage/bmp085-i2c/description + Kernel module for BOSCH Sensortec pressure sensor on I2C +endef + +$(eval $(call KernelPackage,bmp085-i2c)) + +define KernelPackage/bmp085-spi + SUBMENU:=$(OTHER_MENU) + TITLE:=BMP085 digital pressure sensor on SPI + KCONFIG:=CONFIG_BMP085_SPI \ +CONFIG_BMP085 + DEPENDS:=+kmod-regmap + FILES:= \ + $(LINUX_DIR)/drivers/misc/bmp085-spi.ko \ + $(LINUX_DIR)/drivers/misc/bmp085.ko + AUTOLOAD:=$(call AutoLoad,55,bmp085 bmp085-spi) +endef + +define KernelPackage/bmp085-spi/description + Kernel module for BOSCH Sensortec pressure sensor on SPI +endef + +$(eval $(call KernelPackage,bmp085-spi)) + + define KernelPackage/ikconfig SUBMENU:=$(OTHER_MENU) TITLE:=Kernel configuration via /proc/config.gz === ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Resend patch to fix Support For Aztech GR7000
On 28/06/2014 15:49, Alpha Sparc wrote: I notice that support for lantiq mips34kc is also rather flaky, router somethings hangs and reboots abruptly... Is it possible to port the 34kc patches from TP-Link TD-W8970 SDK to OpenWRT? Is there a licensing issue. They have neatly place all their custom patches in a folder, porting should be doable. where inside the GPL tarball can i find the patches ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/3] [ubox] validate: fix indentation
On 29/06/2014 12:38, Jonas Gorski wrote: On Sun, Jun 29, 2014 at 8:58 AM, John Crispin j...@phrozen.org wrote: Hi, blogic@debian:/openwrt/ubox$ git am 5748 Applying: validate: fix indentation blogic@debian:/openwrt/ubox$ git am 5749 Applying: validate: fix indentation They have both the same subject, so you quite likely downloaded the same patch twice. Assuming the numbers are the patchwork patch ids, 5749 should be validate: add valid bool types enabled/disabled error: patch failed: validate/validate.c:882 error: validate/validate.c: patch does not apply Patch failed at 0001 validate: fix indentation When you have resolved this problem run git am --resolved. If you would prefer to skip this patch, instead run git am --skip. To restore the original branch and stop patching run git am --abort. blogic@debian:/openwrt/ubox$ git am --abort blogic@debian:/openwrt/ubox$ patch -p1 5749 patching file validate/validate.c Reversed (or previously applied) patch detected! Assume -R? [n] n Apply anyway? [n] y Hunk #1 FAILED at 882. 1 out of 1 hunk FAILED -- saving rejects to file validate/validate.c.rej Which would also perfectly explain this. let me check the bash_history ... and indeed i fat fingered this while doing copy pasta :) Jonas ___ 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] [Patch][Resend] Support for BMP085 pressure sensor
Hi, patchwork seems to not have picked up this patch. http://patchwork.openwrt.org/project/openwrt/list/ i can only see the previous version John On 29/06/2014 20:11, Sergey Korolew wrote: Hello ! Here is the v2 of the patch, with suggestions from John Crispin. Three packages (one main and two for i2c/spi) selected using submenu. Kernel patch separated from other.mk part, possibly we will have it included in linux kernel. === --- a/package/kernel/linux/modules/other.mk2014-06-29 15:21:39.359850523 +0400 +++ b/package/kernel/linux/modules/other.mk2014-06-29 15:17:27.0 +0400 @@ -698,6 +698,54 @@ $(eval $(call KernelPackage,regmap)) + +define KernelPackage/bmp085 + SUBMENU:=$(OTHER_MENU) + TITLE:=BMP085 digital pressure sensor + KCONFIG:=CONFIG_BMP085 + DEPENDS:=+kmod-regmap + FILES:= \ + $(LINUX_DIR)/drivers/misc/bmp085.ko +endef + +define KernelPackage/bmp085/description + Kernel module for BOSCH Sensortec pressure sensor generic support +endef + +$(eval $(call KernelPackage,bmp085)) + +define KernelPackage/bmp085-i2c + SUBMENU:=$(OTHER_MENU) + TITLE:=BMP085 sensor on I2C bus + KCONFIG:=CONFIG_BMP085_I2C + FILES:= \ + $(LINUX_DIR)/drivers/misc/bmp085-i2c.ko + DEPENDS:=kmod-bmp085 + AUTOLOAD:=$(call AutoProbe,bmp085-i2c) +endef + +define KernelPackage/bmp085-i2c/description + Kernel module for BOSCH Sensortec pressure sensor on I2C bus +endef + +$(eval $(call KernelPackage,bmp085-i2c)) + +define KernelPackage/bmp085-spi + SUBMENU:=$(OTHER_MENU) + TITLE:=BMP085 sensor on SPI bus + KCONFIG:=CONFIG_BMP085_SPI + FILES:= \ + $(LINUX_DIR)/drivers/misc/bmp085-spi.ko + DEPENDS:=kmod-bmp085 + AUTOLOAD:=$(call AutoProbe,bmp085-spi) +endef + +define KernelPackage/bmp085-spi/description + Kernel module for BOSCH Sensortec pressure sensor on SPI bus +endef + +$(eval $(call KernelPackage,bmp085-spi)) + define KernelPackage/ikconfig SUBMENU:=$(OTHER_MENU) TITLE:=Kernel configuration via /proc/config.gz === Kernel part, adapted for OpenWRT, if someone want to compile now. Actually its only replace bool with tristate. === --- a/target/linux/generic/patches-3.6/263-bmp085_dynamic.patch 1970-01-01 04:00:00.0 +0400 +++ b/target/linux/generic/patches-3.6/263-bmp085_dynamic.patch 2014-06-08 14:42:38.0 +0400 @@ -0,0 +1,11 @@ +--- a/drivers/misc/Kconfig2014-04-03 23:01:22.0 +0400 b/drivers/misc/Kconfig2014-06-08 14:40:09.129048438 +0400 +@@ -453,7 +453,7 @@ + still useful. + + config BMP085 +- bool ++ tristate BMP085 digital pressure sensor generic support + depends on SYSFS + + config BMP085_I2C --- a/target/linux/generic/patches-3.8/263-bmp085_dynamic.patch 1970-01-01 04:00:00.0 +0400 +++ b/target/linux/generic/patches-3.8/263-bmp085_dynamic.patch 2014-06-08 14:42:38.0 +0400 @@ -0,0 +1,11 @@ +--- a/drivers/misc/Kconfig2014-04-03 23:01:22.0 +0400 b/drivers/misc/Kconfig2014-06-08 14:40:09.129048438 +0400 +@@ -443,7 +443,7 @@ + still useful. + + config BMP085 +- bool ++ tristate BMP085 digital pressure sensor generic support + depends on SYSFS + + config BMP085_I2C --- a/target/linux/generic/patches-3.9/263-bmp085_dynamic.patch 1970-01-01 04:00:00.0 +0400 +++ b/target/linux/generic/patches-3.9/263-bmp085_dynamic.patch 2014-06-08 14:42:38.0 +0400 @@ -0,0 +1,11 @@ +--- a/drivers/misc/Kconfig2014-04-03 23:01:22.0 +0400 b/drivers/misc/Kconfig2014-06-08 14:40:09.129048438 +0400 +@@ -443,7 +443,7 @@ + still useful. + + config BMP085 +- bool ++ tristate BMP085 digital pressure sensor generic support + depends on SYSFS + + config BMP085_I2C --- a/target/linux/generic/patches-3.10/263-bmp085_dynamic.patch 1970-01-01 04:00:00.0 +0400 +++ b/target/linux/generic/patches-3.10/263-bmp085_dynamic.patch 2014-06-08 14:42:38.0 +0400 @@ -0,0 +1,11 @@ +--- a/drivers/misc/Kconfig2014-04-03 23:01:22.0 +0400 b/drivers/misc/Kconfig2014-06-08 14:40:09.129048438 +0400 +@@ -451,7 +451,7 @@ + still useful. + + config BMP085 +- bool ++ tristate BMP085 digital pressure sensor generic support + depends on SYSFS + + config BMP085_I2C --- a/target/linux/generic/patches-3.12/263-bmp085_dynamic.patch 1970-01-01 04:00:00.0 +0400 +++ b/target/linux/generic/patches-3.12/263-bmp085_dynamic.patch 2014-06-08 14:42:38.0 +0400 @@ -0,0 +1,11 @@ +--- a/drivers/misc/Kconfig2014-04-03 23:01:22.0 +0400 b/drivers/misc/Kconfig2014-06-08 14:40:09.129048438 +0400 +@@ -451,7 +451,7 @@ + still useful. + + config BMP085 +- bool ++ tristate BMP085 digital pressure sensor generic support
Re: [OpenWrt-Devel] [Patch][Resend] Support for BMP085 pressure sensor
On 30/06/2014 12:00, Jonas Gorski wrote: On Mon, Jun 30, 2014 at 10:01 AM, John Crispin j...@phrozen.org wrote: Hi, patchwork seems to not have picked up this patch. http://patchwork.openwrt.org/project/openwrt/list/ i can only see the previous version The patch is line broken, that's why patchwork doesn't see it. Also it is missing a Signed-off-by. Jonas imagine the time we would save if people started using git send-email :) and indeed it is line broken, did not spot it last night although i did go looking for breakage :) Sergey can you send the patch with git send-email please ? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] DGN3500 (all known variants) factory and sysupgrade image building support
On 30/06/2014 12:07, Marco Antonio Mauro wrote: On Wed, Apr 23, 2014 at 8:10 PM, John Crispin j...@phrozen.org wrote: looking at the patch, this was not the tool that depended on some compression lib. i will have a look in the morning to figure out why i did not merge it already :) sorry for the delay Bump! a74c1bb5ca2cf9156ac8cf1d3a91cc6759c4d7ad ??? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] DGN3500 (all known variants) factory and sysupgrade image building support
On 30/06/2014 12:32, Marco Antonio Mauro wrote: On Mon, Jun 30, 2014 at 12:12 PM, John Crispin j...@phrozen.org wrote: a74c1bb5ca2cf9156ac8cf1d3a91cc6759c4d7ad I missed that, I'm sorry! Thanks again! :) you got me worried there for a moment :) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/4] [WEIO] Adding WeIO profile
Hi, please resend with the patches inline, it is not possible to comment when they are attached. also, my first impression is that the patches are really messy and the commit text only partially matches what is inside the patches. 1/4 seems to have a pile of unrelated white space fixes. 1/4 adds a file only for 2/4 and 3/4 to fix it 4/4 adds code with incorrect indenting this is all not bad and we can fix it, however for that to be possible you need to send the patches inline. using git send-email is the best way to do so. last but not least, this is a carambola2 carrier board, with a lpc uC on it ? is this the uC that had a usb device stack in firmware ? John On 30/06/2014 13:59, Drasko DRASKOVIC wrote: This patch adds WeIO board profile. WeIO is the new AR9331 MIPS based board for Internet of Things. Project web-site is: http://we-io.net/ ___ 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] [PATCH 1/4] [WEIO] Adding WeIO profile
Hi, i would prefer it to be all in 1 patch with no unrelated whitespace fixes. that makes it less work to merge and its self contained. if there was more code then splitting it up might make sense, however its only a few lines that get patched ok, so it is the same uC as on the UBER ... i saw a photo of that a while ago. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH - for comment only] lantiq: use UbinizeImage instead lantiq-specific ubinize.cfg files
On 30/06/2014 13:40, Ben Mulvihill wrote: Hello Daniel and John, Could you have a look at this patch, and let me know if this is the best approach? I have defined new make targets for lantiq called Image/BuildNAND/squashfs and Image/BuildNAND/ubifs, making use of the UbinizeImage machanism. For the moment, I only enable them for the BTHOMEHUBV2B, because that is the only lantiq board I have to test, but I don't see any reason why they couldn't be used for the EASY80920NAND and the P2812HNUFX too. As far as I can see, that only leaves one more lantiq nand board, the FRITZ3370, which has a dedicated make target. Once that has been modified as well the make targets Image/Build/ubifs and Image/Build/ubi can be removed from target/linux/lantiq/image/Makefile. Thanks, Ben in general there are no guidelines to this stuff. every target maintainer sort of has his own pattern for the image/Makefile. some patterns have proven to be good and get reused etc etc. that being said, i know felix is planning to globally rework the image generation in owrt and unify it between all targets. so, if your patch works and causes no regression i am happy to take it. it looks good and i think i would have come up with a similar patch John Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com --- --- a/target/linux/lantiq/image/Makefile 2014-06-30 11:49:59.562213352 +0200 +++ b/target/linux/lantiq/image/Makefile2014-06-30 11:54:07.211979129 +0200 @@ -82,6 +82,14 @@ define Image/Build/squashfs $(if $(3),$(call MkBrnImage,$(3),$(4), $(BIN_DIR)/$(IMG_PREFIX)-$(2)-$(3)-brnImage,$(2),$(1),$(5))) endef +define Image/BuildNAND/squashfs + +ifneq ($($(PROFILE)_UBI_OPTS),) + $(call prepare_generic_squashfs,$(KDIR)/root.$(1)) + $(call Image/Build/UbinizeImage,$(PROFILE),,squashfs, $($(PROFILE)_UBI_OPTS)) +endif +endef + DGN3500_SKERNEL=0x5 DGN3500_SKERNEL_DECIMAL=327680 define Image/BuildDGN3500/squashfs @@ -185,6 +193,17 @@ ifneq ($($(PROFILE)_UBI_OPTS),) endif endef + +define Image/BuildNAND/ubifs + +ifneq ($($(PROFILE)_UBIFS_OPTS),) +ifneq ($($(PROFILE)_UBI_OPTS),) + $(call Image/Build/UbinizeImage,$(PROFILE),,ubifs, $($(PROFILE)_UBI_OPTS)) +endif +endif +endef + + define Image/InstallKernel/Template ifneq ($(CONFIG_TARGET_ROOTFS_INCLUDE_KERNEL),) @@ -293,7 +312,7 @@ ifeq ($(CONFIG_TARGET_lantiq_xway),y) # Danube Image/BuildKernel/Profile/BTHOMEHUBV2B=$(call Image/BuildKernel/Template,BTHOMEHUBV2B) -Image/Build/Profile/BTHOMEHUBV2B=$(call Image/Build/$(1), $(1),BTHOMEHUBV2B) +Image/Build/Profile/BTHOMEHUBV2B=$(call Image/BuildNAND/$(1), $(1),BTHOMEHUBV2B) Image/BuildKernel/Profile/EASY50712=$(call Image/BuildKernel/Template,EASY50712) Image/Build/Profile/EASY50712=$(call Image/Build/$(1),$(1),EASY50712) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 1/4] [WEIO] Adding WeIO profile
thanks, i will have a look tonight or in the morning John On 30/06/2014 17:47, Drasko DRASKOVIC wrote: Hi all, signed-off squashed commit that introduces WeIO board support is sent to the list in a new thread. Best regards, Drasko On Mon, Jun 30, 2014 at 3:34 PM, Jonas Gorski j...@openwrt.org wrote: On Mon, Jun 30, 2014 at 2:26 PM, John Crispin j...@phrozen.org wrote: Hi, i would prefer it to be all in 1 patch with no unrelated whitespace fixes. that makes it less work to merge and its self contained. if there was more code then splitting it up might make sense, however its only a few lines that get patched Also Signed-off-by please. See https://dev.openwrt.org/wiki/SubmittingPatches for details. Jonas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] mt7620 wifi
On 30/06/2014 18:50, Roman Yeryomin wrote: So... I've tried the old tree with suggested fix and ended up rebasing my patches to trunk, adding all the fixes and cleaning them up. Attaching the patches for now. John, Helmut, what do you think, can we apply them to the trunk (I will send them properly then)? Unfortunately I don't have any other socs which identify themselves as RT5390 to test if this patch brakes anything for it. i think this is the same is inside the 5390 pci chip ? i have one of those, will verify tomorrow. please tell me which patches to test/merge .. this is really good news, thanks a lot to everyone involved. Also it appeared that ethernet is broken for mt7620n (didn't test other ramips targets) on trunk. Apparently after this (not sure how it's possible): https://dev.openwrt.org/changeset/41331 As `swconfig list' tells: Found: switch0 - mt7530 huh ... i tested it on 2 boards before the merge, will verify ... what board are you testing on ? John Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC] mt7620 wifi
i think this is the same is inside the 5390 pci chip ? i have one of those, will verify tomorrow. Would be good! we will figure it out, otherwise we ask the rt2x00 people for help please tell me which patches to test/merge .. this is really good news, thanks a lot to everyone involved. Basically all I've attached, it's just they are not in the form to git apply them. I can prepare those too if you want. no worries i will ive it a shot in a sec and apply it manually thanks, John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH - for comment only] lantiq: use UbinizeImage instead lantiq-specific ubinize.cfg files
On 30/06/2014 20:32, Ben Mulvihill wrote: Great. Unless Daniel has any objections, I'll re-submit it properly ( - Patchwork didn't pick this one up). It didn't break the BTHOMEHUBV2B, but it would be good if someone could test it on the other boards too. The one thing that is still missing is sysupgrade support. Ben i have not spoken with daniel but i am sure he is fine with this patch is the kernel located on the same nand .. i recall that the unit had a nor flash aswell. look at the patch i added for the wndr4300 to make sysupgrade work. the homehub should work the same way i believe https://dev.openwrt.org/changeset/41131/ On Mon, 2014-06-30 at 14:43 +0200, John Crispin wrote: On 30/06/2014 13:40, Ben Mulvihill wrote: Hello Daniel and John, Could you have a look at this patch, and let me know if this is the best approach? I have defined new make targets for lantiq called Image/BuildNAND/squashfs and Image/BuildNAND/ubifs, making use of the UbinizeImage machanism. For the moment, I only enable them for the BTHOMEHUBV2B, because that is the only lantiq board I have to test, but I don't see any reason why they couldn't be used for the EASY80920NAND and the P2812HNUFX too. As far as I can see, that only leaves one more lantiq nand board, the FRITZ3370, which has a dedicated make target. Once that has been modified as well the make targets Image/Build/ubifs and Image/Build/ubi can be removed from target/linux/lantiq/image/Makefile. Thanks, Ben in general there are no guidelines to this stuff. every target maintainer sort of has his own pattern for the image/Makefile. some patterns have proven to be good and get reused etc etc. that being said, i know felix is planning to globally rework the image generation in owrt and unify it between all targets. so, if your patch works and causes no regression i am happy to take it. it looks good and i think i would have come up with a similar patch John Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com --- --- a/target/linux/lantiq/image/Makefile2014-06-30 11:49:59.562213352 +0200 +++ b/target/linux/lantiq/image/Makefile2014-06-30 11:54:07.211979129 +0200 @@ -82,6 +82,14 @@ define Image/Build/squashfs $(if $(3),$(call MkBrnImage,$(3),$(4), $(BIN_DIR)/$(IMG_PREFIX)-$(2)-$(3)-brnImage,$(2),$(1),$(5))) endef +define Image/BuildNAND/squashfs + +ifneq ($($(PROFILE)_UBI_OPTS),) + $(call prepare_generic_squashfs,$(KDIR)/root.$(1)) + $(call Image/Build/UbinizeImage,$(PROFILE),,squashfs, $($(PROFILE)_UBI_OPTS)) +endif +endef + DGN3500_SKERNEL=0x5 DGN3500_SKERNEL_DECIMAL=327680 define Image/BuildDGN3500/squashfs @@ -185,6 +193,17 @@ ifneq ($($(PROFILE)_UBI_OPTS),) endif endef + +define Image/BuildNAND/ubifs + +ifneq ($($(PROFILE)_UBIFS_OPTS),) +ifneq ($($(PROFILE)_UBI_OPTS),) + $(call Image/Build/UbinizeImage,$(PROFILE),,ubifs, $($(PROFILE)_UBI_OPTS)) +endif +endif +endef + + define Image/InstallKernel/Template ifneq ($(CONFIG_TARGET_ROOTFS_INCLUDE_KERNEL),) @@ -293,7 +312,7 @@ ifeq ($(CONFIG_TARGET_lantiq_xway),y) # Danube Image/BuildKernel/Profile/BTHOMEHUBV2B=$(call Image/BuildKernel/Template,BTHOMEHUBV2B) -Image/Build/Profile/BTHOMEHUBV2B=$(call Image/Build/$(1), $(1),BTHOMEHUBV2B) +Image/Build/Profile/BTHOMEHUBV2B=$(call Image/BuildNAND/$(1), $(1),BTHOMEHUBV2B) Image/BuildKernel/Profile/EASY50712=$(call Image/BuildKernel/Template,EASY50712) Image/Build/Profile/EASY50712=$(call Image/Build/$(1),$(1),EASY50712) ___ 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] [PATCH - for comment only] lantiq: use UbinizeImage instead lantiq-specific ubinize.cfg files
i renamed the api after r41131, so make sure to use the correct one. https://dev.openwrt.org/browser/trunk/target/linux/ar71xx/base-files/lib/upgrade/platform.sh?rev=41222#L308 On 30/06/2014 20:40, John Crispin wrote: On 30/06/2014 20:32, Ben Mulvihill wrote: Great. Unless Daniel has any objections, I'll re-submit it properly ( - Patchwork didn't pick this one up). It didn't break the BTHOMEHUBV2B, but it would be good if someone could test it on the other boards too. The one thing that is still missing is sysupgrade support. Ben i have not spoken with daniel but i am sure he is fine with this patch is the kernel located on the same nand .. i recall that the unit had a nor flash aswell. look at the patch i added for the wndr4300 to make sysupgrade work. the homehub should work the same way i believe https://dev.openwrt.org/changeset/41131/ On Mon, 2014-06-30 at 14:43 +0200, John Crispin wrote: On 30/06/2014 13:40, Ben Mulvihill wrote: Hello Daniel and John, Could you have a look at this patch, and let me know if this is the best approach? I have defined new make targets for lantiq called Image/BuildNAND/squashfs and Image/BuildNAND/ubifs, making use of the UbinizeImage machanism. For the moment, I only enable them for the BTHOMEHUBV2B, because that is the only lantiq board I have to test, but I don't see any reason why they couldn't be used for the EASY80920NAND and the P2812HNUFX too. As far as I can see, that only leaves one more lantiq nand board, the FRITZ3370, which has a dedicated make target. Once that has been modified as well the make targets Image/Build/ubifs and Image/Build/ubi can be removed from target/linux/lantiq/image/Makefile. Thanks, Ben in general there are no guidelines to this stuff. every target maintainer sort of has his own pattern for the image/Makefile. some patterns have proven to be good and get reused etc etc. that being said, i know felix is planning to globally rework the image generation in owrt and unify it between all targets. so, if your patch works and causes no regression i am happy to take it. it looks good and i think i would have come up with a similar patch John Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com --- --- a/target/linux/lantiq/image/Makefile 2014-06-30 11:49:59.562213352 +0200 +++ b/target/linux/lantiq/image/Makefile 2014-06-30 11:54:07.211979129 +0200 @@ -82,6 +82,14 @@ define Image/Build/squashfs $(if $(3),$(call MkBrnImage,$(3),$(4), $(BIN_DIR)/$(IMG_PREFIX)-$(2)-$(3)-brnImage,$(2),$(1),$(5))) endef +define Image/BuildNAND/squashfs + +ifneq ($($(PROFILE)_UBI_OPTS),) +$(call prepare_generic_squashfs,$(KDIR)/root.$(1)) + $(call Image/Build/UbinizeImage,$(PROFILE),,squashfs, $($(PROFILE)_UBI_OPTS)) +endif +endef + DGN3500_SKERNEL=0x5 DGN3500_SKERNEL_DECIMAL=327680 define Image/BuildDGN3500/squashfs @@ -185,6 +193,17 @@ ifneq ($($(PROFILE)_UBI_OPTS),) endif endef + +define Image/BuildNAND/ubifs + +ifneq ($($(PROFILE)_UBIFS_OPTS),) +ifneq ($($(PROFILE)_UBI_OPTS),) + $(call Image/Build/UbinizeImage,$(PROFILE),,ubifs, $($(PROFILE)_UBI_OPTS)) +endif +endif +endef + + define Image/InstallKernel/Template ifneq ($(CONFIG_TARGET_ROOTFS_INCLUDE_KERNEL),) @@ -293,7 +312,7 @@ ifeq ($(CONFIG_TARGET_lantiq_xway),y) # Danube Image/BuildKernel/Profile/BTHOMEHUBV2B=$(call Image/BuildKernel/Template,BTHOMEHUBV2B) -Image/Build/Profile/BTHOMEHUBV2B=$(call Image/Build/$(1), $(1),BTHOMEHUBV2B) +Image/Build/Profile/BTHOMEHUBV2B=$(call Image/BuildNAND/$(1), $(1),BTHOMEHUBV2B) Image/BuildKernel/Profile/EASY50712=$(call Image/BuildKernel/Template,EASY50712) Image/Build/Profile/EASY50712=$(call Image/Build/$(1),$(1),EASY50712) ___ 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] [Lantiq][RFC] Add cpu-feature-overrides.h and disable PCIe and multithreading in Danube
NAK, xway is a unified kernel target and we wont change that upstream. i am fine with the cpu override bit but i wont take the KConfig part, sorry, John On 01/07/2014 02:37, José Vázquez Fernández wrote: This draft adds cpu-feature-overrides.h using the FALCON one as base. Due to the different cores used in ASE and Danube the Kconfig was modified to disable some options that are present in the AR9 and VR9 SoCs, like multithreading, mt ASE and some others. According with UGW all the Lantiq SoCs supported in OpenWRT have CPU_MIPSR2_IRQ_VI but it was not tested nor added. FALCON sets cpu_has_vint and cpu_has_veic to 1, but here were left undefined because i have no idea if the XWAY family have and/or support they. Due to only dcdc driver only has effect with the VR9 the Makefile was modified to include it only when SOC_XWAY is selected. As a side effect the kernel size is 30KB smaller. This patch, as is, works fine with a Danube based router, but, as i have said, is only a draft that, if it has interest, must be improved. José Vázquez diff -urN a/arch/mips/include/asm/mach-lantiq/xway/cpu-feature-overrides.h b/arch/mips/include/asm/mach-lantiq/xway/cpu-feature-overrides.h --- a/arch/mips/include/asm/mach-lantiq/xway/cpu-feature-overrides.h 1970-01-01 01:00:00.0 +0100 +++ b/arch/mips/include/asm/mach-lantiq/xway/cpu-feature-overrides.h 2014-07-01 01:34:41.980432797 +0200 @@ -0,0 +1,67 @@ +/* + * Lantiq XWAY specific CPU feature overrides + * + * This file was derived from: include/asm-mips/cpu-features.h + *Copyright (C) 2003, 2004 Ralf Baechle + *Copyright (C) 2004 Maciej W. Rozycki + * + * This program is free software; you can redistribute it and/or modify it + * under the terms of the GNU General Public License version 2 as published + * by the Free Software Foundation. + * + */ +#ifndef __ASM_MACH_XWAY_CPU_FEATURE_OVERRIDES_H +#define __ASM_MACH_XWAY_CPU_FEATURE_OVERRIDES_H + +#define cpu_has_tlb 1 +#define cpu_has_4kex1 +#define cpu_has_3k_cache0 +#define cpu_has_4k_cache1 +#define cpu_has_tx39_cache0 +#define cpu_has_sb1_cache0 +#define cpu_has_fpu0 +#define cpu_has_32fpr0 +#define cpu_has_counter1 +#define cpu_has_watch1 +#define cpu_has_divec1 + +#define cpu_has_prefetch1 +#define cpu_has_ejtag1 +#define cpu_has_llsc1 + +#if defined(CONFIG_SOC_AMAZON_SE) +#define cpu_has_mips160 +#endif + +#define cpu_has_mdmx0 +#define cpu_has_mips3d 0 +#define cpu_has_smartmips0 +#define cpu_has_vz0 + +#define cpu_has_mips32r11 +#define cpu_has_mips32r21 +#define cpu_has_mips64r10 +#define cpu_has_mips64r20 + +#if defined(CONFIG_SOC_AMAZON_SE) +#define cpu_has_dsp0 +#endif + +#define cpu_has_dsp20 + +#if defined(CONFIG_SOC_AMAZON_SE) || defined(CONFIG_SOC_DANUBE) +#define cpu_has_mipsmt0 +#endif + +//#define cpu_has_vint ? /* MIPSR2 vectored interrupts */ +//#define cpu_has_veic? /* MIPSR2 external interrupt controller mode */ + +#define cpu_has_64bits0 +#define cpu_has_64bit_zero_reg0 +#define cpu_has_64bit_gp_regs0 +#define cpu_has_64bit_addresses0 + +#define cpu_dcache_line_size() 32 +#define cpu_icache_line_size()32 + +#endif /* __ASM_MACH_XWAY_CPU_FEATURE_OVERRIDES_H */ diff -urN a/arch/mips/Kconfig b/arch/mips/Kconfig --- a/arch/mips/Kconfig 2014-07-01 01:11:21.0 +0200 +++ b/arch/mips/Kconfig 2014-06-30 23:59:30.0 +0200 @@ -241,7 +241,6 @@ select SYS_HAS_CPU_MIPS32_R2 select SYS_SUPPORTS_BIG_ENDIAN select SYS_SUPPORTS_32BIT_KERNEL -select SYS_SUPPORTS_MULTITHREADING select SYS_HAS_EARLY_PRINTK select ARCH_REQUIRE_GPIOLIB select SWAP_IO_SPACE diff -urN a/arch/mips/lantiq/Kconfig b/arch/mips/lantiq/Kconfig --- a/arch/mips/lantiq/Kconfig 2014-07-01 01:11:23.0 +0200 +++ b/arch/mips/lantiq/Kconfig 2014-07-01 01:17:23.592775282 +0200 @@ -11,14 +11,21 @@ default SOC_XWAY config SOC_AMAZON_SE -bool Amazon SE +bool XWAY Amazon SE select SOC_TYPE_XWAY +config SOC_DANUBE +bool XWAY Danube +select SOC_TYPE_XWAY +select HW_HAS_PCI +select ARCH_SUPPORTS_MSI + config SOC_XWAY -bool XWAY +bool XWAY Danube, AR9 and VR9 select SOC_TYPE_XWAY select HW_HAS_PCI select ARCH_SUPPORTS_MSI +select SYS_SUPPORTS_MULTITHREADING config SOC_FALCON bool FALCON @@ -31,12 +38,12 @@ config DT_EASY50712 bool Easy50712 -depends on SOC_XWAY + depends on SOC_XWAY || SOC_DANUBE endchoice config PCI_LANTIQ bool PCI Support -depends on SOC_XWAY PCI +depends on (SOC_XWAY || SOC_DANUBE) PCI config PCIE_LANTIQ bool PCIE Support diff -urN a/arch/mips/lantiq/xway/Makefile b/arch/mips/lantiq/xway/Makefile --- a/arch/mips/lantiq/xway/Makefile2014-07-01 01:11:23.0 +0200 +++ b/arch/mips/lantiq/xway/Makefile 2014-07-01
Re: [OpenWrt-Devel] [RFC] mt7620 wifi
Hi, i have the whr-300hp2 on my desk now and will fix the switch and merge the wifi fixes now. John On 01/07/2014 09:41, Kazuki Shimada wrote: Hi, Roman. Do your patches have any chance to make wireless on mt7620a device to work? If so, I'll try it on my buffalo whr-300hp2. Thanks in advance. Kazuki Shimada (2014/07/01 2:36), Roman Yeryomin wrote: On 30 June 2014 20:30, John Crispin j...@phrozen.org wrote: i think this is the same is inside the 5390 pci chip ? i have one of those, will verify tomorrow. Would be good! we will figure it out, otherwise we ask the rt2x00 people for help please tell me which patches to test/merge .. this is really good news, thanks a lot to everyone involved. Basically all I've attached, it's just they are not in the form to git apply them. I can prepare those too if you want. no worries i will ive it a shot in a sec and apply it manually I've sent the series just now... Regards, Roman ___ 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] [PATCH 1/1] [WEIO] Initial support for WeIO board
Hi,
comments inline
From c01a10928d2f27f89ff712896c948f549827acbe Mon Sep 17 00:00:00
2001 From: Drasko DRASKOVIC drasko.drasko...@gmail.com Date: Sun,
9 Feb 2014 03:46:43 +0100 Subject: [PATCH 1/2] weio: adding WeIO
profile for OpenWrt
More changes on WeIO profile
Corrected board name detection in /tmp/sysinfo/board_name
weio: leds - enable STA and AP leds for WeIO board
mach-weio: led names to correspond to convention.
weio: buttons - added WeIO button support
button: Soft reset button moved to GPIO23
weio: i2c - add I2C functionality to WeIO kernel Signed-off-by:
Drasko DRASKOVIC drasko.drasko...@gmail.com ---
.../ar71xx/base-files/etc/uci-defaults/01_leds | 6 +
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 +
.../ar71xx/base-files/lib/upgrade/platform.sh | 3 +-
target/linux/ar71xx/config-3.10| 1 +
.../linux/ar71xx/files/arch/mips/ath79/mach-weio.c | 163
+ target/linux/ar71xx/generic/profiles/weio.mk
| 17 +++ target/linux/ar71xx/image/Makefile | 2
+ .../610-MIPS-ath79-openwrt-machines.patch | 81
+- 8 files changed, 240 insertions(+), 36 deletions(-)
create mode 100644
target/linux/ar71xx/files/arch/mips/ath79/mach-weio.c create mode
100644 target/linux/ar71xx/generic/profiles/weio.mk
diff --git
a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds index
fe5ff93..f0c2178 100755 ---
a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds +++
b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds @@ -57,6
+57,12 @@ carambola2) ucidef_set_led_wlan wlan WLAN
carambola2:green:wlan phy0tpt ;;
+weio) + ucidef_set_led_netdev lan LAN weio:orange:eth0
eth0 + ucidef_set_led_netdev wan WAN weio:orange:eth1
eth1 + ucidef_set_led_wlan wlan WLAN weio:green:wlan
phy0tpt + ;; + db120) ucidef_set_led_usbdev usb USB
db120:green:usb 1-1 ;; diff --git
a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh index
4656ac2..a9c0c99 100755 ---
a/target/linux/ar71xx/base-files/lib/ar71xx.sh +++
b/target/linux/ar71xx/base-files/lib/ar71xx.sh @@ -679,6 +679,9 @@
ar71xx_board_detect() { 8devices Carambola2*) name=carambola2
;; + WeIO*) + name=weio + ;; *Sitecom WLR-8100)
name=wlr8100 ;; diff --git
a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh index
8af9580..5308cf6 100755 ---
a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh +++
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh @@ -178,7
+178,8 @@ platform_check_image() { nbg460n_550n_550nh | \ unifi |
\ unifi-outdoor | \ - carambola2 ) + carambola2 | \ +weio ) [
$magic != 2705 ] { echo Invalid image type. return 1 diff
--git a/target/linux/ar71xx/config-3.10
b/target/linux/ar71xx/config-3.10 index 1346c3f..36576a2 100644 ---
a/target/linux/ar71xx/config-3.10 +++
b/target/linux/ar71xx/config-3.10 @@ -100,6 +100,7 @@
CONFIG_ATH79_MACH_TL_WR841N_V9=y CONFIG_ATH79_MACH_TL_WR941ND=y
CONFIG_ATH79_MACH_UBNT=y CONFIG_ATH79_MACH_UBNT_XM=y
+CONFIG_ATH79_MACH_WEIO=y CONFIG_ATH79_MACH_WHR_HP_G300N=y
CONFIG_ATH79_MACH_WLAE_AG300N=y CONFIG_ATH79_MACH_WLR8100=y diff
--git a/target/linux/ar71xx/files/arch/mips/ath79/mach-weio.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-weio.c new file
mode 100644 index 000..51534aa --- /dev/null +++
b/target/linux/ar71xx/files/arch/mips/ath79/mach-weio.c @@ -0,0
+1,163 @@ +/** + * WEIO Web Of Things Platform + * + * Copyright
(C) 2013 Drasko DRASKOVIC and Uros PETREVSKI + * All rights
reserved + * + * ## ## ### + *
## ## ## #### ## ## + * ## ## ## ##
## ## ## + * ## ## ## #### ## ## +
* ## ## ## #### ## ## + *
## ## ## #### ## ## + * ### ###
### + * + * Web Of Things
Platform + * + * This file is part of WEIO + * WEIO 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 3 of the License, or + *
(at your option) any later version.
linux is gpl 2 only
+ * + * WEIO 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 program. If not, see http://www.gnu.org/licenses/. +
* + * Authors : + * Drasko DRASKOVIC drasko.drasko...@gmail.com +
* Uros PETREVSKI u...@nodesign.net + */ + +#include
asm/mach-ath79/ath79.h +#include asm/mach-ath79/ar71xx_regs.h
+#include
Re: [OpenWrt-Devel] [RFC] mt7620 wifi
Hi, please make a patch that will default vid == vlan nr. this way we have a sane default hat user can override with higher vid if needed. Thanks John On 01/07/2014 08:57, Xiongfei(Alex) GUO wrote: hi, Roman, simply try these commands in OpenWrt, then the ethernet will start to work. uci set network.@switch_vlan[0].vid=1 uci set network.@switch_vlan[1].vid=2 uci commit /etc/init.d/network restart BTW, I'm not sure my test is right, that I can see the wireless driver start, but I cannot find any WIFI with SSID==OpenWrt. hi, John, the problem here is, in old driver for mt7530, vid is always equal to vlan number. but in new driver vid must be set explicitly. in most applications, user don't need to care about the difference between vid and vlan. my solution for mt7530 driver is, when swconfig apply, if vid == 0, then let vid = vlan (so vid==0 is valid). if you think it is ok, i can send a patch about this. Regards!~ Xiongfei (Alex) Guo Credo Semi. On Tue, Jul 1, 2014 at 7:37 AM, Roman Yeryomin leroi.li...@gmail.com wrote: On 1 July 2014 01:54, xf...@credosemi.com xf...@credosemi.com wrote: can you just show the output of swconfig dev switch0 show ? Also it appeared that ethernet is broken for mt7620n (didn't test other ramips targets) on trunk. Apparently after this (not sure how it's possible): https://dev.openwrt.org/changeset/41331 As `swconfig list' tells: Found: switch0 - mt7530 I don't have the board in hands right now but the other thing I've noticed that VID for both 1 and 2 vlans was 0. And setting it to correct values didn't have any effect. Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 0/4] add support for mt7620 wifi
On 30/06/2014 19:34, Roman Yeryomin wrote: This adds support for mt7620 SoC. Tested with Asus RT-N14U only. Thanks to everybody who participated in this effort. Epecially Miko Hissa and Сергей Василюгин. Roman Yeryomin (4): [mac80211] add support for mt7620 [mac80211] enable driver compilation for mt7620 [ramips] enable wmac clock for mt7620 [ramips] add wmac to mt7620 device tree package/kernel/mac80211/Makefile |2 +- ...910-00-rt2x00-enable-rt2800soc-for-mt7620.patch | 20 + .../patches/910-01-add-support-for-mt7620.patch| 1198 target/linux/ramips/dts/mt7620n.dtsi | 10 + .../patches-3.10/0401-mt7620n-add-wmac-clock.patch | 27 + 5 files changed, 1256 insertions(+), 1 deletion(-) create mode 100644 package/kernel/mac80211/patches/910-00-rt2x00-enable-rt2800soc-for-mt7620.patch create mode 100644 package/kernel/mac80211/patches/910-01-add-support-for-mt7620.patch create mode 100644 target/linux/ramips/patches-3.10/0401-mt7620n-add-wmac-clock.patch Hi, confirmed working and pushed to trunk. tested on mt7620a/n. i tested on 2 eval kits and 4 buffalo routers. for me all have functional ethernet even without the vid patch. nonetheless we should make the vid = vlan nr thing explicit and default i have a recollection, that the eep layout is different on mt7620 and i don't see that code being patched. so we need to look into that i am also missing the lna/pna fixes, we should add those as well, similar to how rt3352 does it. those nitpicks set aside, we have working wifi on mt7620x !!! :) thanks again to all involved, i think we will have the final cleanups in trunk soon, now that we have packet flow. John PS: just tested whr-1166 and get this, telling me the eeprom code needs a bit more love. i can still assoc though and am sending this mail via the whr-1166 [ 26.43] WARNING: at /openwrt/trunk/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7620a/compat-wireless-2014-05-22/drivers/net/wireless/rt2x00/rt2800lib.c:408 rt2800_vco_calibration+0x2d8/0x3d4 [rt2800lib]() [ 26.47] phy0: invalid EEPROM word 208 [ 26.48] Modules linked in: rt2800soc rt2800pci rt2800mmio ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: set default vid of each vlan, so it won't need be set explicitly.
Great,
Roman can you test / confirm that this fixes the problem on rt-n14 ? i
don't have that unit myself so i cannot test.
John
On 01/07/2014 12:54, xf...@credosemi.com wrote:
Signed-off-by: Xiongfei Guo xf...@credosemi.com ---
...8-NET-MIPS-add-ralink-SoC-ethernet-driver.patch | 24
++ 1 file changed, 16 insertions(+), 8
deletions(-)
diff --git
a/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
b/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
index c5d6623..6eb624f 100644
---
a/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
+++
b/target/linux/ramips/patches-3.10/0118-NET-MIPS-add-ralink-SoC-ethernet-driver.patch
@@ -2814,7 +2814,7 @@ Signed-off-by: John Crispin
blo...@openwrt.org +#endif --- /dev/null +++
b/drivers/net/ethernet/ralink/mt7530.c -@@ -0,0 +1,571 @@ +@@ -0,0
+1,579 @@ +/* + * This program is free software; you can
redistribute it and/or + * modify it under the terms of the GNU
General Public License @@ -2912,15 +2912,15 @@ Signed-off-by: John
Crispin blo...@openwrt.org +{ + .name = w, +
.pvids = {
1, 1, 1, 1, 2, 1, 1 }, -+ .members = { 0x6f, 0x50 }, -+
.etags =
{ 0x40, 0x40 }, -+.vids = { 1, 2 }, ++.members = { 0,
0x6f,
0x50 }, ++.etags = { 0, 0x40, 0x40 }, ++ .vids = { 0, 1,
2 }, +
}, { +.name = w, + .pvids = { 2, 1, 1, 1,
1, 1, 1 }, -+
.members = { 0x7e, 0x41 }, -+ .etags = { 0x40, 0x40 }, -+
.vids =
{ 1, 2 }, ++ .members = { 0, 0x7e, 0x41 }, ++.etags
= { 0, 0x40,
0x40 }, ++.vids = { 0, 1, 2 }, + }, +}; + @@ -2961,10 +2961,18 @@
Signed-off-by: John Crispin blo...@openwrt.org
+mt7530_reset_switch(struct switch_dev *dev) +{ + struct
mt7530_priv *priv = container_of(dev, struct mt7530_priv, swdev);
++int i; + + memset(priv-port_entries, 0,
sizeof(priv-port_entries)); +memset(priv-vlan_entries, 0,
sizeof(priv-vlan_entries)); + ++ /* set default vid of each vlan
to the same number of vlan, so the vid ++ * won't need be set
explicitly. ++ */ ++ for (i = 0; i MT7530_NUM_VLANS; i++) { ++
priv-vlan_entries[i].vid = i; ++ } ++ + return 0; +} + @@ -3158,7
+3166,7 @@ Signed-off-by: John Crispin blo...@openwrt.org + vid =
(u16)val-value.i; + +if (vlan 0 || vlan = MT7530_NUM_VLANS) -+
return -EINVAL; ++return -EINVAL; + + if (vid
MT7530_MIN_VID ||
vid MT7530_MAX_VID) + return -EINVAL;
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [LANTIQ] Enable LANTIQ_PHY and LANTIQ_XRX200 only in XRX200 subtarget.
ah , i rejected the wrong one in patchwork, will fix it up in a sec thanks for reporting this On 01/07/2014 13:40, José Vázquez wrote: 2014-06-30 21:46 GMT+02:00, José Vázquez Fernández ppvazquez...@gmail.com: Enable LANTIQ_PHY and LANTIQ_XRX200 only in XRX200 subtarget. These drivers are not needed for ASE, Danube and AR9. As side effect PHY11G and PHY22F firmwares are not included in the kernel image, which saves 64 KB. Why was it rejected? Pepe ___ 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] [PATCH] ar71xx: add support for EnGenius ESR1750
Hi,
2 comments inline
On 01/07/2014 13:44, Jon Suphammer wrote:
Signed-off-by: Jon Suphammer j...@suphammer.net ---
target/linux/ar71xx/base-files/etc/diag.sh | 3 +
.../ar71xx/base-files/etc/uci-defaults/02_network | 14 ++
target/linux/ar71xx/base-files/lib/ar71xx.sh | 3 +
.../ar71xx/base-files/lib/upgrade/platform.sh | 1 +
target/linux/ar71xx/config-3.10| 3 +-
.../ar71xx/files/arch/mips/ath79/mach-esr1750.c| 216
+
target/linux/ar71xx/generic/profiles/engenius.mk | 16 ++
target/linux/ar71xx/image/Makefile | 2 +
.../713-MIPS-ath79-add-ESR1750-support.patch | 45 + 9
files changed, 302 insertions(+), 1 deletion(-) create mode 100644
target/linux/ar71xx/files/arch/mips/ath79/mach-esr1750.c create
mode 100644 target/linux/ar71xx/generic/profiles/engenius.mk create
mode 100644
target/linux/ar71xx/patches-3.10/713-MIPS-ath79-add-ESR1750-support.patch
diff --git a/target/linux/ar71xx/base-files/etc/diag.sh
b/target/linux/ar71xx/base-files/etc/diag.sh index 687cddf..3a9de0b
100755 --- a/target/linux/ar71xx/base-files/etc/diag.sh +++
b/target/linux/ar71xx/base-files/etc/diag.sh @@ -69,6 +69,9 @@
get_status_led() { el-m150) status_led=EasyLink:green:system ;; +
esr1750) +status_led=esr1750:red:status + ;;
hiwifi-hc6361)
status_led=hiwifi:blue:system ;; diff --git
a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network index
99c0268..166b10c 100755 ---
a/target/linux/ar71xx/base-files/etc/uci-defaults/02_network +++
b/target/linux/ar71xx/base-files/etc/uci-defaults/02_network @@
-30,6 +30,20 @@ wlr8100) ucidef_add_switch_vlan switch0 2 0t
1 ;;
+esr1750) + ucidef_set_interfaces_lan_wan eth0.1 eth0.2 +
ucidef_add_switch switch0 1 1 + ucidef_add_switch_vlan
switch0 1 0t 2 3 4 5 + ucidef_add_switch_vlan switch0 2
0t 1 + part=$(find_mtd_part u-boot-env) + mac=$(strings $part |
sed -n 's/^'ethaddr'=//p' |sed 's/\//g') +
mac_lan=$(macaddr_canonicalize $mac) +[ -n $mac_lan ]
ucidef_set_interface_macaddr lan $mac_lan +
mac_wan=$(mtd_get_mac_ascii u-boot-env wanaddr) + [ -n $mac_wan ]
ucidef_set_interface_macaddr wan $mac_wan +
mac_wifi2=$(macaddr_add $mac_lan 1) + ;; +
package/kernel/uboot-env/ can solve this problem for you i believe
ap136-010) ucidef_set_interfaces_lan_wan eth0 eth1
ucidef_add_switch switch0 1 1 diff --git
a/target/linux/ar71xx/base-files/lib/ar71xx.sh
b/target/linux/ar71xx/base-files/lib/ar71xx.sh index
4656ac2..954fc9d 100755 ---
a/target/linux/ar71xx/base-files/lib/ar71xx.sh +++
b/target/linux/ar71xx/base-files/lib/ar71xx.sh @@ -319,6 +319,9 @@
ar71xx_board_detect() { *EL-MINI) name=el-mini ;; + *EnGenius
ESR1750) + name=esr1750 +;; *JA76PF)
name=ja76pf ;; diff
--git a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh index
8af9580..70f7fc2 100755 ---
a/target/linux/ar71xx/base-files/lib/upgrade/platform.sh +++
b/target/linux/ar71xx/base-files/lib/upgrade/platform.sh @@ -151,6
+151,7 @@ platform_check_image() { dir-825-c1 | \ dir-835-a1 | \
dragino2 | \ +esr1750 | \ ew-dorin | \ ew-dorin-router | \
hiwifi-hc6361 | \ diff --git a/target/linux/ar71xx/config-3.10
b/target/linux/ar71xx/config-3.10 index 1346c3f..3080c9f 100644 ---
a/target/linux/ar71xx/config-3.10 +++
b/target/linux/ar71xx/config-3.10 @@ -49,10 +49,11 @@
CONFIG_ATH79_MACH_DRAGINO2=y CONFIG_ATH79_MACH_EAP7660D=y
CONFIG_ATH79_MACH_EL_M150=y CONFIG_ATH79_MACH_EL_MINI=y
+CONFIG_ATH79_MACH_ESR1750=y CONFIG_ATH79_MACH_EW_DORIN=y
CONFIG_ATH79_MACH_GS_OOLITE=y -CONFIG_ATH79_MACH_HORNET_UB=y
CONFIG_ATH79_MACH_HIWIFI_HC6361=y +CONFIG_ATH79_MACH_HORNET_UB=y
CONFIG_ATH79_MACH_JA76PF=y CONFIG_ATH79_MACH_JWAP003=y
CONFIG_ATH79_MACH_MR600=y diff --git
a/target/linux/ar71xx/files/arch/mips/ath79/mach-esr1750.c
b/target/linux/ar71xx/files/arch/mips/ath79/mach-esr1750.c new file
mode 100644 index 000..6488d70 --- /dev/null +++
b/target/linux/ar71xx/files/arch/mips/ath79/mach-esr1750.c @@ -0,0
+1,216 @@ +/* + * EnGenius ESR1750 board support + * + * Based on
the Qualcomm Atheros AP135/AP136 reference board support code + *
Copyright (c) 2012 Qualcomm Atheros + * Copyright (c) 2012-2013
Gabor Juhos juh...@openwrt.org + * Copyright (c) 2014 Jon
Suphammer j...@suphammer.net + * + * Permission to use, copy,
modify, and/or distribute this software for any + * purpose with or
without fee is hereby granted, provided that the above + *
copyright notice and this permission notice appear in all copies. +
* + * THE SOFTWARE IS PROVIDED AS IS AND THE AUTHOR DISCLAIMS ALL
WARRANTIES + * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
WARRANTIES OF + * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
THE AUTHOR BE LIABLE FOR + * ANY
Re: [OpenWrt-Devel] [PATCH] [LANTIQ] Enable LANTIQ_PHY and LANTIQ_XRX200 only in XRX200 subtarget.
On 01/07/2014 13:40, José Vázquez wrote: 2014-06-30 21:46 GMT+02:00, José Vázquez Fernández ppvazquez...@gmail.com: Enable LANTIQ_PHY and LANTIQ_XRX200 only in XRX200 subtarget. These drivers are not needed for ASE, Danube and AR9. As side effect PHY11G and PHY22F firmwares are not included in the kernel image, which saves 64 KB. Why was it rejected? Pepe the patch did not apply. neither with git am nor with patch. i fixed this up manually. please check your patches before sending them. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: set default vid of each vlan, so it won't need be set explicitly.
On 01/07/2014 16:11, Roman Yeryomin wrote: On 1 July 2014 13:57, John Crispin j...@phrozen.org wrote: Great, Roman can you test / confirm that this fixes the problem on rt-n14 ? i don't have that unit myself so i cannot test. Yes, it fixes the default configuration. But I still don't understand why I cannot change neither vid not member ports: root@OpenWrt:/# swconfig dev switch0 vlan 1 show VLAN 1: vid: 1 ports: 1 2 3 4 6t root@OpenWrt:/# swconfig dev switch0 vlan 1 set ports '3 4 6t' root@OpenWrt:/# swconfig dev switch0 vlan 1 show VLAN 1: vid: 1 ports: 1 2 3 4 6t So is it broken or what? Although I didn't check earlier versions it seems broken to me... sounds broken, added to my todo list ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] Get wifi firmware for WRTnode
Thanks, applied in r41452 John On 01/07/2014 20:15, Cezary Jackiewicz wrote: After r41444 wifi working on WRTnode. Tested. Signed-off-by: Cezary Jackiewicz cezary.jackiew...@gmail.com --- Index: target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom === --- target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom (wersja 41450) +++ target/linux/ramips/base-files/etc/hotplug.d/firmware/10-rt2x00-eeprom (kopia robocza) @@ -119,6 +119,7 @@ wnce2001 | \ wr512-3gn | \ wr6202 | \ + wrtnode | \ mzk-w300nh2 | \ ur-326n4g | \ ur-336un | \ ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH - for comment only] lantiq: use UbinizeImage instead lantiq-specific ubinize.cfg files
On 01/07/2014 22:12, Ben Mulvihill wrote: Hello again, I have just tried sysupgradeNAND on the BTHOMEHUBV2B, and it fails with the following error: cat: can't open '/tmp/sysinfo/board_name': No such file or directory Unlocking kernel ... Writing from stdin to kernel ... [ ]tar: sysupgrade-/kernel: not found in archive Procd relies on /tmp/sysinfo/board_name being present, but I don't have a /tmp/sysinfo directory at all. Should I have? If so, should I add code to lib/functions/lantiq.sh to generate /tmp/sysinfo/board_name using lantiq_board_id() ? And if so, what do I hook it to to make sure it gets executed? Thanks, Ben ermm yes ... it should work the same as on imx6, ramips, ar71xx ... you can either do this tonight or i can do it in the morning. which ever you prefer :) On Mon, 2014-06-30 at 20:44 +0200, John Crispin wrote: i renamed the api after r41131, so make sure to use the correct one. https://dev.openwrt.org/browser/trunk/target/linux/ar71xx/base-files/lib/upgrade/platform.sh?rev=41222#L308 On 30/06/2014 20:40, John Crispin wrote: On 30/06/2014 20:32, Ben Mulvihill wrote: Great. Unless Daniel has any objections, I'll re-submit it properly ( - Patchwork didn't pick this one up). It didn't break the BTHOMEHUBV2B, but it would be good if someone could test it on the other boards too. The one thing that is still missing is sysupgrade support. Ben i have not spoken with daniel but i am sure he is fine with this patch is the kernel located on the same nand .. i recall that the unit had a nor flash aswell. look at the patch i added for the wndr4300 to make sysupgrade work. the homehub should work the same way i believe https://dev.openwrt.org/changeset/41131/ On Mon, 2014-06-30 at 14:43 +0200, John Crispin wrote: On 30/06/2014 13:40, Ben Mulvihill wrote: Hello Daniel and John, Could you have a look at this patch, and let me know if this is the best approach? I have defined new make targets for lantiq called Image/BuildNAND/squashfs and Image/BuildNAND/ubifs, making use of the UbinizeImage machanism. For the moment, I only enable them for the BTHOMEHUBV2B, because that is the only lantiq board I have to test, but I don't see any reason why they couldn't be used for the EASY80920NAND and the P2812HNUFX too. As far as I can see, that only leaves one more lantiq nand board, the FRITZ3370, which has a dedicated make target. Once that has been modified as well the make targets Image/Build/ubifs and Image/Build/ubi can be removed from target/linux/lantiq/image/Makefile. Thanks, Ben in general there are no guidelines to this stuff. every target maintainer sort of has his own pattern for the image/Makefile. some patterns have proven to be good and get reused etc etc. that being said, i know felix is planning to globally rework the image generation in owrt and unify it between all targets. so, if your patch works and causes no regression i am happy to take it. it looks good and i think i would have come up with a similar patch John Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com --- --- a/target/linux/lantiq/image/Makefile 2014-06-30 11:49:59.562213352 +0200 +++ b/target/linux/lantiq/image/Makefile 2014-06-30 11:54:07.211979129 +0200 @@ -82,6 +82,14 @@ define Image/Build/squashfs $(if $(3),$(call MkBrnImage,$(3),$(4), $(BIN_DIR)/$(IMG_PREFIX)-$(2)-$(3)-brnImage,$(2),$(1),$(5))) endef +define Image/BuildNAND/squashfs + +ifneq ($($(PROFILE)_UBI_OPTS),) + $(call prepare_generic_squashfs,$(KDIR)/root.$(1)) +$(call Image/Build/UbinizeImage,$(PROFILE),,squashfs, $($(PROFILE)_UBI_OPTS)) +endif +endef + DGN3500_SKERNEL=0x5 DGN3500_SKERNEL_DECIMAL=327680 define Image/BuildDGN3500/squashfs @@ -185,6 +193,17 @@ ifneq ($($(PROFILE)_UBI_OPTS),) endif endef + +define Image/BuildNAND/ubifs + +ifneq ($($(PROFILE)_UBIFS_OPTS),) +ifneq ($($(PROFILE)_UBI_OPTS),) + $(call Image/Build/UbinizeImage,$(PROFILE),,ubifs, $($(PROFILE)_UBI_OPTS)) +endif +endif +endef + + define Image/InstallKernel/Template ifneq ($(CONFIG_TARGET_ROOTFS_INCLUDE_KERNEL),) @@ -293,7 +312,7 @@ ifeq ($(CONFIG_TARGET_lantiq_xway),y) # Danube Image/BuildKernel/Profile/BTHOMEHUBV2B=$(call Image/BuildKernel/Template,BTHOMEHUBV2B) -Image/Build/Profile/BTHOMEHUBV2B=$(call Image/Build/$(1), $(1),BTHOMEHUBV2B) +Image/Build/Profile/BTHOMEHUBV2B=$(call Image/BuildNAND/$(1), $(1),BTHOMEHUBV2B) Image/BuildKernel/Profile/EASY50712=$(call Image/BuildKernel/Template,EASY50712) Image/Build/Profile/EASY50712=$(call Image/Build/$(1),$(1),EASY50712) ___ 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
Re: [OpenWrt-Devel] [PATCH - for comment only] lantiq: use UbinizeImage instead lantiq-specific ubinize.cfg files
On 02/07/2014 08:33, Ben Mulvihill wrote: On Tue, 2014-07-01 at 22:17 +0200, John Crispin wrote: On 01/07/2014 22:12, Ben Mulvihill wrote: Hello again, I have just tried sysupgradeNAND on the BTHOMEHUBV2B, and it fails with the following error: cat: can't open '/tmp/sysinfo/board_name': No such file or directory Unlocking kernel ... Writing from stdin to kernel ... [ ]tar: sysupgrade-/kernel: not found in archive Procd relies on /tmp/sysinfo/board_name being present, but I don't have a /tmp/sysinfo directory at all. Should I have? If so, should I add code to lib/functions/lantiq.sh to generate /tmp/sysinfo/board_name using lantiq_board_id() ? And if so, what do I hook it to to make sure it gets executed? Thanks, Ben ermm yes ... it should work the same as on imx6, ramips, ar71xx ... you can either do this tonight or i can do it in the morning. which ever you prefer :) Just did a quick test and the mechanism seems simple enough. But I'm afraid my day job and other commitments will keep me busy now until the weekend. I guess it depends whether you feel like taking time from the 101 other things you are working on simultaneously ;-) I'll send the UbinizeImage patch anyway now, with an extra line to generate the SysupgradeNAND tar files. One unfortunate thing: lantiq has lantiq_board_id and lantiq_board_name, whereas the other architectures all have x_board_name and x_model, and for sysupgrade to work /temp/sysinfo/board_name will have to contain the value of lantiq_board_id, not, as would seem logical, lantiq_board_name. Confusing! YES ! :) i already have staged patches locally that unify this pattern over all targets and add a /lib/board.sh with a unified api naming etc. i am just holding it back til BB is done. scared to break stuff in the last days of the release :) i'll fix up lantiq so your problem is gone during the day 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
Re: [OpenWrt-Devel] [PATCH] ramips: add missing rt3352 usb profile
On 02/07/2014 16:46, michael lee wrote: From: michael igv...@gmail.com Signed-off-by: michael igv...@gmail.com Thanks, applied in r41475 and r41476 John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] lantiq: UbinizeImage instead of lantiq-specific ubinize.cfg files
On 02/07/2014 08:37, Ben Mulvihill wrote: New make target in lantiq to use UbinizeImage and SysupgradeNand. Only enabled for BTHOMEHUBV2B for the moment but should be useable for other lantiq nand boards. Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com --- Thanks, applied in r41474 .. and i pushed the /tmp/sysinfo/* patch in r41472 please let me know if it still blows up or works. ___ 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 / PCI issues
applied in r41505 On 04/07/2014 00:24, Roman Yeryomin wrote: On 16 April 2014 11:17, Bastian Bittorf bitt...@bluebottle.com wrote: * Roman Yeryomin leroi.li...@gmail.com [16.04.2014 09:34]: Also pci seems to be broken as neither miniPCI slots nor VIA ethernet ports are not working: I've tested this and it works fine: https://patchwork.linux-mips.org/patch/6940/ Gabor, any reason it's still not in trunk? Regards, Roman ___ 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] (CVE-2014-2338) authentication bypass vulnerability in strongSwan needs patching
i stopped bb-builder2 and pointed it at AA instead of BB. i will update strongswan, openssl and gnutls during the day. sorry for the delay, the old AA builders HDD died half way through the build 2 weeks ago and i was busy with BB and simply forgot. sorry for the delay On 06/07/2014 17:41, Noel Kuntze wrote: Hello Mirko, So fixes or new versions with fixes will only be backported, if there is a complete rebuilt scheduled for the release? Regards, Noel Kuntze GPG Key id: 0x63EC6658 Fingerprint: 23CA BB60 2146 05E7 7278 6592 3839 298F 63EC 6658 Am 06.07.2014 14:39, schrieb Mirko Parthey: Am Sonntag, 06.07.14, 00:00 +0200 schrieb Noel Kuntze: I am once again inquiring about this vulnerabity. The strongSwan version in the repository for the 12.09 version of OpenWRT is still not patched and Mr. Fietkau does not respond to any emails. I wrote him one on 2014-06-08 and one on 2014-07-02. Please update the packages. Lots of people are running vulnerable StrongSwan versions on publicly reachable OpenWRT routers. Felix Fietkau updated the strongSwan package in the 12.09 SVN branch (r40518, 2014-04-15) shortly after updating it in trunk. However, it appears that the release branch is not rebuilt automatically, so the binary packages are outdated. For OpenSSL, packages have been rebuilt manually, but that seems to be the exception. There has been mention on this mailing list of a Barrier Breaker release being worked on, but I have no information if there will be another release of Attitude Adjustment, which would then also come with updated packages from the 12.09 branch. Regards, Mirko ___ 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] Help with SysupgradeNAND
On 09/07/2014 08:42, Ben Mulvihill wrote: Hello Daniel, I have got SysupgradeNAND working on the BTHOMEHUBV2B with an all-ubifs rootfs, with a patch which I'll submit in another email, once I've recompiled with the latest trunk and made sure that everything is working, but in the meantime I have a question: am I right in thinking that the only type of overlay supported is squashfs + ubifs, not squashfs + jffs2 ? ubifs is jffs3 essentially, a jffs2 with nand awareness added ... correct me if i am wrong ... Thanks, Ben ___ 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] Help with SysupgradeNAND
On 09/07/2014 09:14, Andre Valentin wrote: Hi! I also noticed after upgrading that routers with jffs2 in ubi (rootfs_data) are not supported anymore. The jffs2 is not mounted after an upgrade, resulting in loss of configuration. I had to clear rootfs_data to be able to mount it again as ubifs. That's okay if you know it! i think using squash+ubifs is a better option as we dont need to use the gluebi layer anymore. this makes the whole setup a lot nice i think. that is why jffs2 support for nand is gone. however i am open to hear use cases for why jffs2 support should be added for nand. I noticed a second issue. hostapd (running in some kind of dfs loop) was not killed by sysupgrade nand. That resulted in breaking the upgrade. System rebooted with old image. I personnaly added a check in sysupgrade if it runs below upgraded and if that's true, I kill _all_ processes. If interested I could publish the patch. please send a patch A third point is the upgrade itself. I the rootfs image grows, and rootfs_data has all the remaining space aligned, it will not work because rootfs cannot grow. Perhaps rootfs_data should always be recreated in the update process. If interested I could also supply a patch. please send a patch John Kind regards, André On 09.07.2014 09:02, John Crispin wrote: On 09/07/2014 08:42, Ben Mulvihill wrote: Hello Daniel, I have got SysupgradeNAND working on the BTHOMEHUBV2B with an all-ubifs rootfs, with a patch which I'll submit in another email, once I've recompiled with the latest trunk and made sure that everything is working, but in the meantime I have a question: am I right in thinking that the only type of overlay supported is squashfs + ubifs, not squashfs + jffs2 ? ubifs is jffs3 essentially, a jffs2 with nand awareness added ... correct me if i am wrong ... Thanks, Ben ___ 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
[OpenWrt-Devel] OpenSSL/StrongSwan: AA binary feed update
libopenssl/strongswan - AA binary feed update
libopenssl was updated from 1.0.1g to 1.0.1h.
strongswan was updated from 5.0.0 to 5.1.3.
We updated the AA binary release. The Packages index was also updated.
If you use openssl or strongswan on your unit you need to run :
# opkg update
# opkg upgrade libopenssl/strongswan-{full,...}
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.
OpenWrt Developers
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Help with SysupgradeNAND
On 10/07/2014 08:27, Ben Mulvihill wrote: On Wed, 2014-07-09 at 16:27 +0200, Daniel Golle wrote: On Wed, Jul 09, 2014 at 04:10:52PM +0200, Ben Mulvihill wrote: JFFS2 works on bare MTD devices (originally NOR only, hackish NAND support exists in the wild though YAFFS2 is more commonly used). UBIFS is the only read-write filesystem which works on top of UBI, thus the only possible choice for overlay support. Not the only possibility surely? Currently we generate two images for the BTHOMEHUBV2B. Both use ubi. One has pure ubifs on top. The other has a squashfs/jffs2 overlay making use of gluebi. Everything works apart from sysupgrade but the only reason for doing things that way was that it was a natural progression from the pre-ubi arrangement and it worked out of the box. A squashfs/ubifs overlay is certainly cleaner. I'll see what I need to do to get it working. Ah, ok, now I understand the question :) And yes, you should use squashfs/ubifs for overlay and disable gluebi alltogether. gluebi is deprectated and was meant only for transition. ubiblock offers a much cleaner way for read-only filesystems and UBIFS makes much more sense than jffs2-on-gluebi. The penny has finally dropped! When I first made images using the new ubi support a few weeks ago the squashfs/jffs2 gluebi overlay worked out of the box, and the squashfs/ubifs overlay did not. I assumed I would have to generate the squashfs images for the latter case in some special way, preformatting an empty ubifs partition perhaps, or adding some magic to tell the kernel to mount rootfs_data as ubifs. I have just realised that the images work fine as they are, as long as the gluebi/mtd code doesn't get there first and attempt a jffs2 mount. So all that needs to be done to move over to a squashfs/ubifs overlay is to disable gluebi in the kernel configuration. I should like to ask John whether he would be happy for me to submit a patch to do that, on xway at least, not on xrx200 to avoid affecting the other lantiq nand boards? sorry i should have mentioned this. gluebi is dead, long life ubiblock !!! we backported ubiblock from 3.15, it allows raw r/o access to the squash. ubifs runs without intermediate gluebi/mtd layer, thus making the whole setup much simpler. from what i understand, ubiblock will obsolete gluebi in upstream so we decided to switch early. this should be done for xway and xrx200. John Or would it be better to find some way of enabling the volume_identify code in procd to distinguish a jffs2 rootfs_data from a ubifs rootfs_data. just in case in the future someone needs gluebi in the kernel for some other reason? Thank you Ben ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] There ar some strange things in bb
Hi, i just checked the BB builder and the rpi images get built there. are you testing on HEAD ? John On 10/07/2014 17:10, smile...@gmail.com wrote: After compression of the rootfs, there is a failure. ... mcopy -i /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/boot.img /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/Image ::kernel.img # Copy OpenWrt built kernel ./gen_rpi_sdcard_img.sh /home/smilebef/Downloads/OpenWRT/openwrt/bin/brcm2708/openwrt-brcm2708-sdcard-vfat-squashfs.img /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/boot.img /home/smilebef/Downloads/OpenWRT/openwrt/build_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/linux-brcm2708/root.squashfs 20 + '[' 4 == 5 ']' + echo 'SYNTAX: ./gen_rpi_sdcard_img.sh file bootfs image rootfs image bootfs size rootfs size' SYNTAX: ./gen_rpi_sdcard_img.sh file bootfs image rootfs image bootfs size rootfs size + exit 1 Makefile:40: recipe for target 'install' failed make[5]: *** [install] Error 1 make[5]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux/brcm2708/image' Makefile:30: recipe for target 'install' failed make[4]: *** [install] Error 2 make[4]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux/brcm2708' Makefile:13: recipe for target 'install' failed make[3]: *** [install] Error 2 make[3]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt/target/linux' target/Makefile:21: recipe for target 'target/linux/install' failed make[2]: *** [target/linux/install] Error 2 make[2]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt' target/Makefile:17: recipe for target '/home/smilebef/Downloads/OpenWRT/openwrt/staging_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/stamp/.target_install' failed make[1]: *** [/home/smilebef/Downloads/OpenWRT/openwrt/staging_dir/target-arm_arm1176jzf-s+vfp_uClibc-0.9.33.2_eabi/stamp/.target_install] Error 2 make[1]: Leaving directory '/home/smilebef/Downloads/OpenWRT/openwrt' /home/smilebef/Downloads/OpenWRT/openwrt/include/toplevel.mk:169: recipe for target 'world' failed make: *** [world] Error 2 smilebef@Vigor18:~/Downloads/OpenWRT/openwrt$ Any ideas? Thanks ___ 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] [Patch] [ar71xx] added support for TL-WA830RE V2
Hi, On 08/07/2014 20:29, Fredrik Jonson wrote: +++ b/target/linux/ar71xx/patches-3.10/714-MIPS-auth79-add-TL-WA830REv2-support.patch s/auth79/ath79/g :) John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Trac: Custom Query results in Missing or invalid form token.
On 11/07/2014 08:12, Rafał Miłecki wrote: 1) Please enter https://dev.openwrt.org/query 2) Click Update button This will results in: Error: Bad Request Missing or invalid form token. Do you have cookies enabled? Could someone take a look at this, please? works for me, Do you have cookies enabled? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH][ramips] asl26555: fix devdata partitions
Hi,
we use factory and not devdata to store the eep data. the script needs
to be changed and not the dts file i think.
- factory: partition@3 { -
label = factory; +
devdata: partition@3 { + label =
devdata; reg = 0x3
0x1;
this bit is certainly wrong. just because the ODM decided to use a
none std name does not mean we need to do so ...
John
___
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 TP-LINK TL-WA860RE v1
Hi, On 10/07/2014 22:17, Cezary Jackiewicz wrote: Index: target/linux/ar71xx/patches-3.10/700-MIPS-ath79-add-TL-WA801NDv2-suport.patch 700 already exists. please also verify the other patch names and then resend the patch John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] [packages] enable openssl's arm asm support
Hi,
had to look up if i missed the newest trend but i did not ... :)
https://www.kernel.org/doc/Documentation/SubmittingPatches
quote
The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as an open-source patch. The rules are pretty simple: if you
can certify the below:
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) ...
(b) ...
(c) ...
(d) ...
then you just add a line saying
Signed-off-by: Random J Developer ran...@developer.example.org
using your real name (sorry, no pseudonyms or anonymous contributions.)
/quote
apart from that it looks sane will run this on a few arm boards today.
John
On 11/07/2014 19:09, Daniel Drown wrote:
This speeds up openssl on the arm platform. My test machine is a
dual-core 1ghz Freescale i.MX6 board.
[before] # openssl speed -multi 2 aes-128-cbc aes-128 cbc
33402.86k36116.95k36406.44k36468.74k36208.64k
[after] # openssl speed -multi 2 aes-128-cbc aes-128 cbc
54901.30k60114.15k61398.10k61680.98k61762.22k
or, roughly a 70% speed increase
The ASFLAGS need to change because the asm code includes
crypto/arm_arch.h
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license indicated
in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that work
with modifications, whether created in whole or in part by me,
under the same open source license (unless I am permitted to submit
under a different license), as indicated in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
Signed-off-by: Daniel Drown dan-open...@drown.org
diff --git a/package/libs/openssl/Makefile
b/package/libs/openssl/Makefile index fff260b..5740e13 100644 ---
a/package/libs/openssl/Makefile +++
b/package/libs/openssl/Makefile @@ -105,6 +105,8 @@ else
OPENSSL_OPTIONS+=no-sse2 ifeq ($(CONFIG_mips)$(CONFIG_mipsel),y)
OPENSSL_TARGET:=linux-mips-openwrt + else ifeq ($(CONFIG_arm),y) +
OPENSSL_TARGET:=linux-armv4-openwrt else
OPENSSL_TARGET:=linux-generic-openwrt OPENSSL_OPTIONS+=no-perlasm
@@ -143,7 +145,7 @@ TARGET_CFLAGS += $(FPIC) define Build/Compile
+$(MAKE) $(PKG_JOBS) -C $(PKG_BUILD_DIR) \ CC=$(TARGET_CC) \ -
ASFLAGS=$(TARGET_ASFLAGS) -c \ +ASFLAGS=$(TARGET_ASFLAGS)
-I$(PKG_BUILD_DIR)/crypto -c \ AR=$(TARGET_CROSS)ar r \
RANLIB=$(TARGET_CROSS)ranlib \
OPENWRT_OPTIMIZATION_FLAGS=$(TARGET_CFLAGS) \ @@ -151,7 +153,7 @@
define Build/Compile all +$(MAKE) $(PKG_JOBS) -C $(PKG_BUILD_DIR)
\ CC=$(TARGET_CC) \ - ASFLAGS=$(TARGET_ASFLAGS) -c \ +
ASFLAGS=$(TARGET_ASFLAGS) -I$(PKG_BUILD_DIR)/crypto -c \
AR=$(TARGET_CROSS)ar r \ RANLIB=$(TARGET_CROSS)ranlib \
OPENWRT_OPTIMIZATION_FLAGS=$(TARGET_CFLAGS) \ diff --git
a/package/libs/openssl/patches/220-Configure-arm.patch
b/package/libs/openssl/patches/220-Configure-arm.patch new file
mode 100644 index 000..3bc92e4 --- /dev/null +++
b/package/libs/openssl/patches/220-Configure-arm.patch @@ -0,0
+1,10 @@ +--- a/Configure 2014-07-11 15:48:35.788111874 +
b/Configure 2014-07-11 15:49:10.699784507 + +@@ -406,6 +406,7
@@ + # OpenWrt targets + linux-mips-openwrt,gcc:-DTERMIOS
\$(OPENWRT_OPTIMIZATION_FLAGS) -fomit-frame-pointer
-Wall::-D_REENTRANT::-ldl:BN_LLONG RC4_CHAR RC4_CHUNK DES_INT
DES_UNROLL
BF_PTR:${mips32_asm}:o32:dlfcn:linux-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR),
+ linux-generic-openwrt,gcc:-DTERMIOS \$(OPENWRT_OPTIMIZATION_FLAGS)
-fomit-frame-pointer -Wall::-D_REENTRANT::-ldl:BN_LLONG RC4_CHAR
RC4_CHUNK DES_INT DES_UNROLL
BF_PTR:${no_asm}:dlfcn:linux-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR),
++linux-armv4-openwrt,gcc:-DTERMIOS
\$(OPENWRT_OPTIMIZATION_FLAGS) -fomit-frame-pointer
-Wall::-D_REENTRANT::-ldl:BN_LLONG RC4_CHAR RC4_CHUNK DES_INT
DES_UNROLL
BF_PTR:${armv4_asm}:dlfcn:linux-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR),
+
+ # Android: linux-* but without -DTERMIO and pointers to headers
and libs. + android,gcc:-mandroid -I\$(ANDROID_DEV)/include
-B\$(ANDROID_DEV)/lib -O3 -fomit-frame-pointer
-Wall::-D_REENTRANT::-ldl:BN_LLONG
Re: [OpenWrt-Devel] [PATCH V2][brcm2708] Use uci-defaults for network config
Hi, can you use brcm2708: int he subject next time ? git am strips [foo] from the subject John On 04/07/2014 14:29, Álvaro Fernández Rojas wrote: By using uci-defaults force_link is enabled, which fixes some link issues if ethernet cable isn't connected when LAN is initialized. Signed-off-by: Álvaro Fernández Rojas nolt...@gmail.com --- v2: check for existing network config as Jonas suggested. diff --git a/target/linux/brcm2708/base-files/etc/config/network b/target/linux/brcm2708/base-files/etc/config/network deleted file mode 100644 index 1d5ded3..000 --- a/target/linux/brcm2708/base-files/etc/config/network +++ /dev/null @@ -1,13 +0,0 @@ -# Copyright (C) 2006 OpenWrt.org - -config interface loopback - option ifname lo -option proto static - option ipaddr 127.0.0.1 - option netmask 255.0.0.0 - -config interface lan - option ifname eth0 - option protostatic - option ipaddr 192.168.1.1 - option netmask 255.255.255.0 diff --git a/target/linux/brcm2708/base-files/etc/uci-defaults/02_network b/target/linux/brcm2708/base-files/etc/uci-defaults/02_network new file mode 100644 index 000..e7e35c5 --- /dev/null +++ b/target/linux/brcm2708/base-files/etc/uci-defaults/02_network @@ -0,0 +1,15 @@ +#!/bin/sh +# Copyright (C) 2014 OpenWrt.org + +[ -e /etc/config/network ] exit 0 + +touch /etc/config/network + +. /lib/functions/uci-defaults.sh + +ucidef_set_interface_loopback +ucidef_set_interface_lan eth0 + +uci commit network + +exit 0 ___ 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] [Patch] [ar71xx] added support for TL-WA830RE V2
On 12/07/2014 11:20, Fredrik Jonson wrote: Hello, I'm sorry John, I do not understand what you mean, with your comment. /Fjonson ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel Hi, a patch with the number 700 exists. use 714 please, that would be the next free ath79 support patch. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH V2] ar71xx: add support for TP-LINK TL-WA860RE v1
hi, Index: target/linux/ar71xx/base-files/etc/diag.sh === --- target/linux/ar71xx/base-files/etc/diag.sh (revision 41592) +++ target/linux/ar71xx/base-files/etc/diag.sh(working copy) this is also wrong. should be --- a/target/linux/ar71xx/base-files/etc/diag.sh (revision 41592) +++ b/target/linux/ar71xx/base-files/etc/diag.sh (working copy) you should use git to generate the patches so i can apply them with git am John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH V3] ar71xx: add support for TP-LINK TL-WA860RE v1
On 13/07/2014 10:17, Cezary Jackiewicz wrote: +++ b/target/linux/ar71xx/patches-3.10/715-MIPS-ath79-add-TL-WA860RE-support.patch when i saw your V3 i thought ... darn its needs to be 715 after the merge i did earlier :) Thanks, applied in r41598 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH V2] ar71xx: add support for TP-LINK TL-WA860RE v1
On 13/07/2014 12:39, Jonas Gorski wrote: On Sun, Jul 13, 2014 at 9:12 AM, John Crispin j...@phrozen.org wrote: hi, Index: target/linux/ar71xx/base-files/etc/diag.sh === --- target/linux/ar71xx/base-files/etc/diag.sh (revision 41592) +++ target/linux/ar71xx/base-files/etc/diag.sh(working copy) this is also wrong. should be --- a/target/linux/ar71xx/base-files/etc/diag.sh (revision 41592) +++ b/target/linux/ar71xx/base-files/etc/diag.sh (working copy) you should use git to generate the patches so i can apply them with git am git am understands the -p argument, so you should be able to apply this patch with git am -p0. learned something new today :) seems obvious now that i think about it ... John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker 14.07-rc1
On 14/07/2014 12:59, Xiongfei Guo wrote: Hi, john, How is the luci, which version the luci will be used. Teh devel? or luci will bump to 0.12? Xiongfei Guo Credo Semi. On 07/14/2014 05:12 PM, John Crispin wrote: The OpenWrt developers are proud to announce the first release candidate of OpenWrt Barrier Breaker. ___ __ | |.-.-.-.| | | |..| |_ | - || _ | -__| || | | || _|| _| |___|| __|_|__|__||||__| || |__| W I R E L E S S F R E E D O M - BARRIER BREAKER (14.07 RC1) - * 1/2 oz Galliano Pour all ingredients into * 4 oz cold Coffee an irish coffee mug filled * 1 1/2 oz Dark Rum with crushed ice. Stir. * 2 tsp. Creme de Cacao - Hi, we are using 9b9b17ece34db50cf634a7f5ba38872b1c32c827 for RC1 John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker 14.07-rc1
On 14/07/2014 13:13, Yousong Zhou wrote: On 14 July 2014 17:12, John Crispin j...@phrozen.org wrote: The OpenWrt developers are proud to announce the first release candidate of OpenWrt Barrier Breaker. ___ __ | |.-.-.-.| | | |..| |_ | - || _ | -__| || | | || _|| _| |___|| __|_|__|__||||__| || |__| W I R E L E S S F R E E D O M - BARRIER BREAKER (14.07 RC1) - * 1/2 oz Galliano Pour all ingredients into * 4 oz cold Coffee an irish coffee mug filled * 1 1/2 oz Dark Rum with crushed ice. Stir. * 2 tsp. Creme de Cacao - Cool. Two years have passed and a fresh new OpenWrt release is coming :) actually it is 1 year and 3 months http://downloads.openwrt.org/barrier_breaker/14.07-rc1/ ** Highlights since Attitude Adjustment ** Default configuration and images * Linux kernel updated to version 3.10 * Procd: new preinit, init, hotplug and event system written in C * Native IPv6-support - RA DHCPv6+PD client and server - Local prefix allocation source-restricted routes (multihoming) * Filesystem improvements - Added support for sysupgrade on NAND-flash - Added support for filesystem snapshot and rollback I may ask how can this feature be enabled? I am not following the trunk commits for quite a while and thus not aware of this new feature. use the /sbin/snapshot tool. i think i will make a howto for this in the wiki as its quite a hidden feature Regards. yousong - Rewritten mounting system in C for rootfs and block devices * UCI configuration improvements - Support for testing configuration and rollback to working last working state - Unified change trigger system to restart services on-demand - Added a data validation layer * Networking improvements - Netifd now handles setup and configuration reload of wireless interfaces - Added reworked event support to allow obsoleting network hotplug-scripts - Added support for dynamic firewall rules and zones - Added support for transparent multicast to unicast translation for bridges - Various other fixes and improvements Additional highlights selectable in the package feeds or SDK * Extended IPv6-support - Added DS-Lite support and improved 6to4, 6in4 and 6rd-support - Experimental support for Lightweight 4over6, MAP-E and MAP-T - Draft-support for self-managing home networks (HNCP) * rpcd: new JSONRPC over HTTP-frontend for remote access to ubus * mdns: new lightweight mdns daemon (work in progress) * Initial support for the musl C standard library * Support for QMI-based 3g/4g modems * Support for DNSSEC validation * Added architecture for package signing and SHA256 hashing * ... and many more cool things Package feed reorganization For quite a while already we are not very satisfied with the quality of the packages-feed. To address this, we decided to do a fresh start on GitHub. The new feed https://github.com/openwrt/packages should be used from now on and package maintainers are asked to move their packages there. For the final release we will still build the old packages feed but it will be necessary to enable it manually in the opkg package list to be usable. All current feeds should not have any dependencies on the old.packages feed. Currently a few packages still fail, mainly due to these cross feed dependencies. We will contact the respective maintainers to help resolve these issues for RC2. New build servers We would like to express our gratitude to Imagination Technology for funding the 2 build servers that we used for the release. Whats next ? We aim at releasing Chaos Calmer (CC) before the end of the year. The CC release will use 3.14 or a newer LTS kernel as baseline. Have fun! The OpenWrt developer team ___ 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] openwrt-devel Digest, Vol 103, Issue 58
On 14/07/2014 15:56, Alive4Ever wrote: On Monday, July 14, 2014 12:00:01 PM openwrt-devel-requ...@lists.openwrt.org wrote: The OpenWrt developers are proud to announce the first release candidate of OpenWrt Barrier Breaker. Glad to know that Barrier Breaker will be ready to rock. Would it possible to include my ticket #17028 here? I think it's necessary to add support for newer 3g dongle. Thanks. queued for RC2, updating the device list is not enough, there is a new option that we need to support aswell. 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
Re: [OpenWrt-Devel] [PATCH 3/4] ramips: squelch mdio debugging info on rt2880 ethernet
ok, no idea why it is not in trunk but marked as accepted but i would assume its my fault thanks, merged in r41653 On 14/07/2014 18:55, Claudio Leite wrote: Hello, * Claudio Leite (lei...@staticky.com) wrote: Use pr_debug rather than pr_info since it is only relevant for debugging. Signed-off-by: Claudio Leite lei...@staticky.com While we are talking about things for Barrier Breaker RC's, could this patch be merged in? It was marked as accepted back in April, but I just tested the RC1 release on a RT2880 board and it still has the mdio r/w dumps. While it doesn't affect actual performance, it does slow down boot by a few seconds while it programs the switch. --- .../0220-NET-ralink-squelch_mdio_access.patch | 22 ++ 1 file changed, 22 insertions(+) create mode 100644 target/linux/ramips/patches-3.10/0220-NET-ralink-squelch_mdio_access.patch diff --git a/target/linux/ramips/patches-3.10/0220-NET-ralink-squelch_mdio_access.patch b/target/linux/ramips/patches-3.10/0220-NET-ralink-squelch_mdio_access.patch new file mode 100644 index 000..bc92a02 --- /dev/null +++ b/target/linux/ramips/patches-3.10/0220-NET-ralink-squelch_mdio_access.patch @@ -0,0 +1,22 @@ +Index: linux-3.10.34/drivers/net/ethernet/ralink/mdio_rt2880.c +=== +--- linux-3.10.34.orig/drivers/net/ethernet/ralink/mdio_rt2880.c linux-3.10.34/drivers/net/ethernet/ralink/mdio_rt2880.c +@@ -136,7 +136,7 @@ int rt2880_mdio_read(struct mii_bus *bus + if (err) + return 0x; + +- pr_info(%s: addr=%04x, reg=%04x, value=%04x\n, __func__, ++ pr_debug(%s: addr=%04x, reg=%04x, value=%04x\n, __func__, + phy_addr, phy_reg, fe_r32(FE_MDIO_ACCESS) 0x); + +return fe_r32(FE_MDIO_ACCESS) 0x; +@@ -148,7 +148,7 @@ int rt2880_mdio_write(struct mii_bus *bu + int err; + u32 t; + +- pr_info(%s: addr=%04x, reg=%04x, value=%04x\n, __func__, ++ pr_debug(%s: addr=%04x, reg=%04x, value=%04x\n, __func__, + phy_addr, phy_reg, fe_r32(FE_MDIO_ACCESS) 0x); + + err = rt2880_mdio_wait_ready(priv); -- 1.8.2.1 Thanks. -Claudio ___ 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] [PATCH 00/17] atheros: I/O cleanups
On 14/07/2014 19:05, Sergey Ryazanov wrote: John, please, could you reject this series? I will send new one. i just marked it as Changes Requested John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: soc wmac eeprom cleanup
Hi, lovely, works for me on the 6 boards that i tested. will merge it in a sec. i will look into the fixme bits. John On 14/07/2014 23:13, Roman Yeryomin wrote: Move eeprom extraction from scripts to dts files. Additionally there are few other changes like: - whitespace fixes - add partition labels where needed - BR6524N board doesn't exist (lost in translation?) - fix Edimax 3g-6200nl model - add wmac eeprom to dts for Asus RT-N14U board Compile tested all subtargets and their profiles. Run tested on: - Asus RT-N15 - Asus RT-N14U - Buffalo WHR-600D - Argus ATP52B - Sparklan WCR-150GN Few problems noted: - many boards didn't have wmac eeprom information defined at all - several boards don't have any patitions defined (see FIXME comments in dts) Signed-off-by: Roman Yeryomin ro...@advem.lv --- .../etc/hotplug.d/firmware/10-rt2x00-eeprom| 106 + target/linux/ramips/base-files/lib/ramips.sh | 3 - target/linux/ramips/dts/3G-6200N.dts | 4 + target/linux/ramips/dts/3G-6200NL.dts | 8 +- target/linux/ramips/dts/3G300M.dts | 4 + target/linux/ramips/dts/AIR3GII.dts| 4 + target/linux/ramips/dts/ALL0239-3G.dts | 4 + target/linux/ramips/dts/ALL0256N-4M.dts| 4 + target/linux/ramips/dts/ALL0256N-8M.dts| 4 + target/linux/ramips/dts/ALL5002.dts| 4 + target/linux/ramips/dts/ALL5003.dts| 4 + target/linux/ramips/dts/ARGUS_ATP52B.dts | 4 + target/linux/ramips/dts/ASL26555-16M.dts | 6 +- target/linux/ramips/dts/ASL26555-8M.dts| 5 + target/linux/ramips/dts/AWAPN2403.dts | 4 + target/linux/ramips/dts/AWM002-EVB-4M.dts | 4 + target/linux/ramips/dts/AWM002-EVB-8M.dts | 4 + target/linux/ramips/dts/BC2.dts| 4 + target/linux/ramips/dts/BR-6425.dts| 4 + target/linux/ramips/dts/BR-6475ND.dts | 4 + target/linux/ramips/dts/BROADWAY.dts | 4 + target/linux/ramips/dts/CARAMBOLA.dts | 4 + target/linux/ramips/dts/CY-SWR1100.dts | 1 + target/linux/ramips/dts/D105.dts | 4 + target/linux/ramips/dts/DAP-1350.dts | 6 +- target/linux/ramips/dts/DCS-930.dts| 4 + target/linux/ramips/dts/DIR-300-B1.dts | 6 +- target/linux/ramips/dts/DIR-300-B7.dts | 7 +- target/linux/ramips/dts/DIR-320-B1.dts | 4 + target/linux/ramips/dts/DIR-600-B1.dts | 6 +- target/linux/ramips/dts/DIR-600-B2.dts | 6 +- target/linux/ramips/dts/DIR-610-A1.dts | 2 +- target/linux/ramips/dts/DIR-615-D.dts | 6 +- target/linux/ramips/dts/DIR-615-H1.dts | 4 + target/linux/ramips/dts/DIR-620-A1.dts | 4 + target/linux/ramips/dts/DIR-620-D1.dts | 4 + target/linux/ramips/dts/DIR-645.dts| 1 + target/linux/ramips/dts/ESR-9753.dts | 4 + target/linux/ramips/dts/F5D8235_V1.dts | 6 +- target/linux/ramips/dts/F5D8235_V2.dts | 6 +- target/linux/ramips/dts/F7C027.dts | 4 + target/linux/ramips/dts/FONERA20N.dts | 4 + target/linux/ramips/dts/FREESTATION5.dts | 4 + target/linux/ramips/dts/HG255D.dts | 4 + target/linux/ramips/dts/HW550-3G.dts | 4 + target/linux/ramips/dts/MOFI3500-3GN.dts | 1 + target/linux/ramips/dts/MPRA1.dts | 4 + target/linux/ramips/dts/MPRA2.dts | 4 + target/linux/ramips/dts/MZK-750DHP.dts | 4 + target/linux/ramips/dts/MZK-W300NH2.dts| 4 + target/linux/ramips/dts/NBG-419N.dts | 4 + target/linux/ramips/dts/NCS601W.dts| 4 + target/linux/ramips/dts/NW718.dts | 4 + target/linux/ramips/dts/OMNI-EMB-HPM.dts | 4 + target/linux/ramips/dts/OMNI-EMB.dts | 4 + target/linux/ramips/dts/PSR-680W.dts | 4 + target/linux/ramips/dts/PWH2004.dts| 4 + target/linux/ramips/dts/RT-G32-B1.dts | 8 +- target/linux/ramips/dts/RT-N10-PLUS.dts| 6 +- target/linux/ramips/dts/RT-N13U.dts| 4 + target/linux/ramips/dts/RT-N14U.dts| 4 + target/linux/ramips/dts/RT-N15.dts | 4 + target/linux/ramips/dts/RTN56U.dts | 2 +- target/linux/ramips/dts/RUT5XX.dts | 4 + target/linux/ramips/dts/SL-R7205.dts | 4 + target/linux/ramips/dts/UR-326N4G.dts | 4 + target/linux/ramips/dts/UR-336UN.dts | 10 +- target/linux/ramips/dts/V11STFE.dts
Re: [OpenWrt-Devel] Sysupgrade to Barrier Breaker on au1000 (MTX-1)
On 16/07/2014 00:07, Hauke Mehrtens wrote: On 07/15/2014 07:06 PM, Bruno Randolf wrote: Another problem I noted when upgrading from AA to BB on MTX-1: # sysupgrade -n /tmp/openwrt-au1000-au1500-jffs2-128k-sysupgrade.bin tar: openwrt-au1000-au1500-jffs2-128k.fs: not found in archive Invalid image contents Image check 'platform_check_image' failed. I needed to change in /lib/upgrade/platform.sh: ROOTFS_IMG=openwrt-au1000-au1500-root.fs In AA the ROOTFS image was called differently, the name in BB makes more sense, but how could we provide a good upgrade path from AA to BB? bruno Hi Bruno, au1000 was not updated for BB and as you see there is some work missing. feel free to send a patch to fix the sysupgrade issue. Once that is done and if you volunteert to maintain au1000 for BB, then we culd add it to the list of targets that we build for rc2 John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: soc wmac eeprom cleanup
On 17/07/2014 12:53, Roman Yeryomin wrote: On 15 July 2014 19:40, John Crispin j...@phrozen.org wrote: Hi, lovely, works for me on the 6 boards that i tested. will merge it in a sec. i will look into the fixme bits. So, if nothing is wrong, could it be applied? Regards, Roman ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel Thanks, applied in r41680 John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Sysupgrade to Barrier Breaker on au1000 (MTX-1)
On 17/07/2014 10:55, Bruno Randolf wrote: I volunteer to maintain au1000. The only devices I have are MTX-1 though, but I believe there are not many other au1000 boards out in the wild anyways. good I don't know how to fix the sysupgrade issue. Basically the name used in AA was wrong (ROOTFS_IMG=openwrt-au1000-au1500-jffs2-128k.fs) and this has been chnaged to something more generic in BB (ROOTFS_IMG=openwrt-au1000-au1500-root.fs). sysupgrade from BB to BB works OK, but the problem is upgrade from AA to BB, where the ROOTFS_IMG names in the tar do not match. The only solutions I can think of are, none of which I find really good: 1) Keep on using the old (wrong) name for all image types 2) Provide a symlink with the old name for upgrade from AA to BB 3) Add backwards compatibility code to /lib/upgrade/platform.sh 4) we make a script that we call after the build on the server that repackages the images how about that ? John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.
Hi, do a cat /tmp/sysinfo/* on the unit please ... John On 19/07/2014 20:52, Paul Blazejowski wrote: John, any update on this issue? i strongly believe that the hard-coded wndr4300 string somewhere in the source is the culprit of the problem since the wndr3700v4 board_detection is identified as wndr4300 thus the sysupgrade works for 4300 but not for 3700v4. Regards, -paul On Tue, 2014-06-24 at 23:15 +0200, John Crispin wrote: On 24/06/2014 22:43, Paul Blazejowski wrote: i get The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform. from web interface. this is what i have: -rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58 bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar should i push it from shell using sysupgrade script? it will work from shell, i will look into why it fails via webui. thanks! On Tue, 2014-06-24 at 22:32 +0200, John Crispin wrote: On 24/06/2014 22:25, Paul Blazejowski wrote: Hi again, thanks for the tftp fix, flushing just became so much faster and easier. Tested trunk r41336 after your jffs2 fix and the image boots fine, restored my configuration changes, rebooted the router and all changes are saved now. I will post the working dmesg to the ticket at https://dev.openwrt.org/ticket/16840 but it is safe to say that you can close it ;-) now. Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this is next on the list... i tested 4300 and it works. you need to use the *-ubi-sysupgrade.tar file. Thank you, -paul On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote: On 24/06/2014 19:05, Paul Blazejowski wrote: John, Yes i use the reset with pin and from there i tftp the original firmware from netgear after that i go to the gui and upload the open-wrt image because the router will not accept the wndr3700v4 image (there's a cosmetic fix for that, i created a patch that someone from the forums has sent months ago to this list but it was never accepted...) https://dev.openwrt.org/ticket/16840 With that patch tftp'ing the openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need to flash the original firmware. If there's another method that can be used to flash the image(s) please let me know i would want to try any alternative ways of flashing and could learn a thing or two in the process as well ;-) Thank you, -paul Hi, i just pushed the V vs v fix and another fix that removes the jffs2 magic. i think this might have been the cause of the problems. please retry with current trunk and let me know if the problem is gone or still there 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 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] [PATCH] ramips: add support for Kingston MLW221 [resend]
Hi,
this patch is line broken.
what is the difference between this and the previous ?
John
On 19/07/2014 06:11, L. D. Pinney wrote:
From: L. D. Pinney ldpin...@gmail.com
This patch adds support for the Kingston Mobilelite Wireless
(MLW-221)
http://wiki.openwrt.org/toh/kingston/mlw221
Signed-off-by: L. D. Pinney ldpin...@gmail.com
--- diff --git a/target/linux/ramips/base-files/etc/diag.sh
b/target/linux/ramips/base-files/etc/diag.sh index 908547e..0887606
100755 --- a/target/linux/ramips/base-files/etc/diag.sh +++
b/target/linux/ramips/base-files/etc/diag.sh @@ -73,6 +73,9 @@
get_status_led() { m4) status_led=m4:blue:status ;; +mlw221)
+status_led=kingston:green:status +;;
mofi3500-3gn) status_led=mofi3500-3gn:green:status ;; diff --git
a/target/linux/ramips/base-files/etc/uci-defaults/01_leds
b/target/linux/ramips/base-files/etc/uci-defaults/01_leds index
19ec4f5..359281e 100755 ---
a/target/linux/ramips/base-files/etc/uci-defaults/01_leds +++
b/target/linux/ramips/base-files/etc/uci-defaults/01_leds @@ -113,6
+113,9 @@ case $board in hw550-3g) set_usb_led
hw550-3g:green:usb ;; +mlw221) +set_wifi_led
kingston:blue:wifi +;; mofi3500-3gn) set_usb_led
mofi3500-3gn:green:usb ;; diff --git
a/target/linux/ramips/base-files/etc/uci-defaults/02_network
b/target/linux/ramips/base-files/etc/uci-defaults/02_network index
b54b555..c6a4609 100755 ---
a/target/linux/ramips/base-files/etc/uci-defaults/02_network +++
b/target/linux/ramips/base-files/etc/uci-defaults/02_network @@
-49,6 +49,10 @@ ramips_setup_interfaces() ucidef_set_interface_lan
eth0 ;;
+mlw221) +ucidef_set_interfaces_lan_wan eth0.1
eth0.2 +;; + 3g-6200nl | \ wl-330n | \ wmr300) diff --git
a/target/linux/ramips/base-files/lib/ramips.sh
b/target/linux/ramips/base-files/lib/ramips.sh index
f9ab1e3..71cdd47 100755 ---
a/target/linux/ramips/base-files/lib/ramips.sh +++
b/target/linux/ramips/base-files/lib/ramips.sh @@ -157,6 +157,9 @@
ramips_board_detect() { *HAME MPR-A2) name=mpr-a2 ;; +
*Kingston MLW221) +name=mlw221 +;; *Planex
MZK-750DHP) name=mzk-750dhp ;; diff --git
a/target/linux/ramips/base-files/lib/upgrade/platform.sh
b/target/linux/ramips/base-files/lib/upgrade/platform.sh index
8ada58b..5dec7f8 100755 ---
a/target/linux/ramips/base-files/lib/upgrade/platform.sh +++
b/target/linux/ramips/base-files/lib/upgrade/platform.sh @@ -54,6
+54,7 @@ platform_check_image() { ip2202 | \ m3 | \ m4 | \ +
mlw221 | \ mofi3500-3gn | \ mpr-a1 | \ mpr-a2 | \ diff --git
a/target/linux/ramips/image/Makefile
b/target/linux/ramips/image/Makefile index c7225a6..3a0fe9d 100644
--- a/target/linux/ramips/image/Makefile +++
b/target/linux/ramips/image/Makefile @@ -737,6 +737,7 @@ endif #
MT7620N Profiles #
+Image/Build/Profile/MLW221=$(call
BuildFirmware/Default16M/$(1),$(1),mlw221,MLW221)
Image/Build/Profile/WMR300=$(call
BuildFirmware/Default8M/$(1),$(1),wmr-300,WMR300)
Image/Build/Profile/RT-N14U=$(call
BuildFirmware/Default8M/$(1),$(1),rt-n14u,RT-N14U)
Image/Build/Profile/WR8305RT=$(call
BuildFirmware/Default8M/$(1),$(1),wr8305rt,WR8305RT) @@ -745,6
+746,7 @@ Image/Build/Profile/ZBT-WA05=$(call
BuildFirmware/Default8M/$(1),$(1),zbt-wa05,Z
ifeq ($(SUBTARGET),mt7620n) define Image/Build/Profile/Default +
$(call Image/Build/Profile/MLW221,$(1)) $(call
Image/Build/Profile/WMR300,$(1)) $(call
Image/Build/Profile/RT-N14U,$(1)) $(call
Image/Build/Profile/WR8305RT,$(1)) diff --git
a/target/linux/ramips/dts/MLW221.dts
b/target/linux/ramips/dts/MLW221.dts new file mode 100644 index
000..15fde52 100644 --- a/target/linux/ramips/dts/MLW221.dts
+++ b/target/linux/ramips/dts/MLW221.dts @@ -0,0 +1,118 @@
+/dts-v1/; + +/include/ mt7620n.dtsi + +/ { + compatible =
mlw221, ralink,mt7620n-soc; + model = Kingston MLW221;
+ + palmbus@1000 { + gpio0: gpio@600 { +
status = okay; + }; + + gpio2:
gpio@660 { + status = okay; +
}; + + gpio3: gpio@688 { +
status = okay; + }; + + spi@b00 { +
status = okay; + + m25p80@0 { +
#address-cells = 1; + #size-cells =
1; + compatible = s25fl129p1; +
reg = 0 0; + linux,modalias =
m25p80, s25fl129p1; +
spi-max-frequency = 1000; + +
partition@0 { + label =
u-boot; + reg = 0x0
0x3; + read-only; +
}; + + partition@3 { +
label = u-boot-env; + reg =
0x3 0x1; +
read-only; + }; + +
factory: partition@4 { +
label = factory; + reg =
0x4
Re: [OpenWrt-Devel] [PATCH] lantiq xway: generate ramdisk image by default
technically correct. however there is a dependency bug left over from some cargo cult cleanups. this causes the image builder to not build when ramdisk is enabled. i plan to clean this up post BB. i will ignore this patch until said time. John On 19/07/2014 15:13, Ben Mulvihill wrote: The installation process on nand-based boards using ubi like the BTHOMEHUBV2B makes use of a ramdisk image, so it makes sense to generate this by default. Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com --- --- a/target/linux/lantiq/xway/target.mk 2014-07-19 14:59:39.691201637 +0200 +++ b/target/linux/lantiq/xway/target.mk2014-07-19 12:40:06.101871732 +0200 @@ -1,7 +1,7 @@ ARCH:=mips SUBTARGET:=xway BOARDNAME:=XWAY -FEATURES:=squashfs atm mips16 nand ubifs +FEATURES:=squashfs atm mips16 nand ubifs ramdisk CPU_TYPE:=34kc CPU_SUBTYPE:=dsp ___ 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] [PATCH] lantiq xway: generate ramdisk image by default
sure, i also just figured out why the rc1 lantiq images dont have dsl enabled by default. i will pusah a fix to trunk tonight once i tested it properly John On 21/07/2014 10:29, Ben Mulvihill wrote: If you would that would be great. It is not essential, but that way all the necessary downloads would be in one place on the official openwrt site. Thank you, Ben On Sun, 2014-07-20 at 11:12 +0200, John Crispin wrote: i can build a ramdisk for the board for the reelase if it is needed to install. we do the same for the mikrotik boards. John On 20/07/2014 10:03, Ben Mulvihill wrote: No problem. I'll try to make sure there is a link to a non-official ramdisk image on the wiki. (Along with some installation instructions, which at the moment are lacking!) Ben On Sun, 2014-07-20 at 08:54 +0200, John Crispin wrote: technically correct. however there is a dependency bug left over from some cargo cult cleanups. this causes the image builder to not build when ramdisk is enabled. i plan to clean this up post BB. i will ignore this patch until said time. John On 19/07/2014 15:13, Ben Mulvihill wrote: The installation process on nand-based boards using ubi like the BTHOMEHUBV2B makes use of a ramdisk image, so it makes sense to generate this by default. Signed-off-by: Ben Mulvihill ben.mulvih...@gmail.com --- --- a/target/linux/lantiq/xway/target.mk 2014-07-19 14:59:39.691201637 +0200 +++ b/target/linux/lantiq/xway/target.mk 2014-07-19 12:40:06.101871732 +0200 @@ -1,7 +1,7 @@ ARCH:=mips SUBTARGET:=xway BOARDNAME:=XWAY -FEATURES:=squashfs atm mips16 nand ubifs +FEATURES:=squashfs atm mips16 nand ubifs ramdisk CPU_TYPE:=34kc CPU_SUBTYPE:=dsp ___ 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 ___ 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] Sysupgrade to Barrier Breaker on au1000 (MTX-1)
Hi Bruno i will merge a patch post the rc2 fork that will generate old and new images int he release branch while not doing so in the dev trunk. i really dont want any workarounds in trunk how about that ? John On 21/07/2014 15:20, Bruno Randolf wrote: On 07/21/2014 12:28 PM, Bruno Randolf wrote: It would be possible to create a special image for upgrade from AA, something like openwrt-au1000-au1500-jffs2-128k-sysupgrade-from-12.09.bin, but I think it's simpler to just add a symlink to the tar.gz in all cases, The symlink approach does not work, as dd does not recognize the symlink and the rootfs is broken afterwards. So IMHO the best solution is to create a special sysupgrade image for upgrade from 12.09, like openwrt-au1000-au1500-jffs2-128k-sysupgrade-from-12.09.bin... diff --git a/target/linux/au1000/image/Makefile b/target/linux/au1000/image/Makefile index 63c0b03..56f613b 100644 --- a/target/linux/au1000/image/Makefile +++ b/target/linux/au1000/image/Makefile @@ -65,6 +65,10 @@ define Image/Build $(CP) $(BIN_DIR)/$(IMG_PREFIX)-$(1).fs $(TMP_DIR)/$(IMG_PREFIX)-root.fs tar -C $(BIN_DIR) -cvzf $(BIN_DIR)/$(IMG_PREFIX)-$(1)-sysupgrade.bin \ $(IMG_PREFIX)-vmlinux.bin -C $(TMP_DIR) $(IMG_PREFIX)-root.fs + # backwards compatible image for upgrade from Attitude Adjustment (12.09) + $(CP) $(BIN_DIR)/$(IMG_PREFIX)-$(1).fs $(TMP_DIR)/$(IMG_PREFIX)-jffs2-128k.fs + tar -C $(BIN_DIR) -cvzf $(BIN_DIR)/$(IMG_PREFIX)-$(1)-sysupgrade-from-12.09.bin \ + $(IMG_PREFIX)-vmlinux.bin -C $(TMP_DIR) $(IMG_PREFIX)-jffs2-128k.fs ifeq ($(CONFIG_TARGET_ROOTFS_INITRAMFS),y) $(call Image/Build/Initramfs) endif bruno ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Sysupgrade to Barrier Breaker on au1000 (MTX-1)
On 21/07/2014 19:27, Bruno Randolf wrote: On 07/21/2014 02:22 PM, John Crispin wrote: i will merge a patch post the rc2 fork that will generate old and new images int he release branch while not doing so in the dev trunk. i really dont want any workarounds in trunk how about that ? Sounds OK to me. Anyhow there are not so many au1000 users out there and I guess we can expect them to follow the major OpenWRT releases... bruno ok, so be it ... i will cook up a patch ... ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [BUG] NAND sysupgrade broke ubifs on Netgear WNDR3700v4/4300.
hi, i pushed a patch in the hope that it will work. please test current trunk and tell if the problem is solved. John On 20/07/2014 17:56, Paul Blazejowski wrote: Hi, sorry your email got lost somehow on my end... And the machine hosting mailing list is down at the moment it seems. here is the info: root@router:~# cat /tmp/sysinfo/* wndr4300 NETGEAR WNDR3700v4/WNDR4300 thanks, -paul On Sat, 2014-07-19 at 14:52 -0400, Paul Blazejowski wrote: John, any update on this issue? i strongly believe that the hard-coded wndr4300 string somewhere in the source is the culprit of the problem since the wndr3700v4 board_detection is identified as wndr4300 thus the sysupgrade works for 4300 but not for 3700v4. Regards, -paul On Tue, 2014-06-24 at 23:15 +0200, John Crispin wrote: On 24/06/2014 22:43, Paul Blazejowski wrote: i get The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform. from web interface. this is what i have: -rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58 bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar should i push it from shell using sysupgrade script? it will work from shell, i will look into why it fails via webui. thanks! On Tue, 2014-06-24 at 22:32 +0200, John Crispin wrote: On 24/06/2014 22:25, Paul Blazejowski wrote: Hi again, thanks for the tftp fix, flushing just became so much faster and easier. Tested trunk r41336 after your jffs2 fix and the image boots fine, restored my configuration changes, rebooted the router and all changes are saved now. I will post the working dmesg to the ticket at https://dev.openwrt.org/ticket/16840 but it is safe to say that you can close it ;-) now. Sysupgrade image(s) for 3700v4 and 4300 do not work now, guess this is next on the list... i tested 4300 and it works. you need to use the *-ubi-sysupgrade.tar file. Thank you, -paul On Tue, 2014-06-24 at 20:18 +0200, John Crispin wrote: On 24/06/2014 19:05, Paul Blazejowski wrote: John, Yes i use the reset with pin and from there i tftp the original firmware from netgear after that i go to the gui and upload the open-wrt image because the router will not accept the wndr3700v4 image (there's a cosmetic fix for that, i created a patch that someone from the forums has sent months ago to this list but it was never accepted...) https://dev.openwrt.org/ticket/16840 With that patch tftp'ing the openwrt-ar71xx-nand-wndr3700v4-ubi-factory.img works without need to flash the original firmware. If there's another method that can be used to flash the image(s) please let me know i would want to try any alternative ways of flashing and could learn a thing or two in the process as well ;-) Thank you, -paul Hi, i just pushed the V vs v fix and another fix that removes the jffs2 magic. i think this might have been the cause of the problems. please retry with current trunk and let me know if the problem is gone or still there 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 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] [PATCH v2] ramips: Fix WR8305RT USB LED
Hi,
this patch has $windos style new lines. git am refuses to merge it.
i will mark the other patches you sent as rejected aswell.
please take a few hours to learn git am / git send-email.
John
On 23/07/2014 03:27, L. D. Pinney wrote:
From: L. D. Pinney ldpin...@gmail.com
This patch sets the USB LED to 0 (no device = no light) v2 also
sets the name from lan to usb
Signed-off-by: L. D. Pinney ldpin...@gmail.com
---
diff --git a/target/linux/ramips/dts/WR8305RT.dts
b/target/linux/ramips/dts/WR8305RT.dts index c28e422..812c6e5
100644 --- a/target/linux/ramips/dts/WR8305RT.dts +++
b/target/linux/ramips/dts/WR8305RT.dts @@ -87,9 +87,9 @@ label =
wr8305rt:sys; gpios = gpio1 14 1; }; -lan { +
usb { label = wr8305rt:usb; -gpios = gpio1 15 1; +
gpios = gpio1 15 0; }; wifi { label = wr8305rt:wifi;
___ 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] [PATCH] ar71xx: fix LED configuration for HiWiFi-HC6361.
Hi, i assume the patches was sent various times by accident ? i could not find a difference between the various versions so i am going to merge the last one i got. if this is wrong then please do let me know. John On 23/07/2014 09:00, Yousong Zhou wrote: Signed-off-by: Yousong Zhou yszhou4t...@gmail.com --- target/linux/ar71xx/base-files/etc/uci-defaults/01_leds |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds index 23fa628..7c86b05 100755 --- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds +++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds @@ -124,7 +124,7 @@ esr900) ;; hiwifi-hc6361) - ucidef_set_led_default inet INET hiwifi:blue:internet 0 + ucidef_set_led_netdev inet INET hiwifi:blue:internet eth1 ucidef_set_led_wlan wlan WLAN hiwifi:blue:wlan-2p4 phy0tpt ;; ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2] ramips: Fix WR8305RT USB LED
On 23/07/2014 17:33, Roman Yeryomin wrote: On 23 July 2014 18:26, L. D. Pinney ldpin...@gmail.com wrote: The WR8305RT may be the same as the WA05I have asked ZBT. One difference is uboot is set for 57600 on my WR8305RT...meaning I'll need to patch the WA05 dts to use it. Or update the uboot? I have also asked ZBT for the current uboot... That's very strange because they have asked me to rename WA05 into WR8305RT. They didn't say the baudrate is different. Can you take a photo of pcb? Regards, Roman Hi, whoever decided to put 57600 as the default baud rate in the RTSDK should be tar'ed and feathered. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH]ramips: Add Ralink RT3XXX USB OHCI driver
Hi Roman, do you have this board ? could you see if it also fails for you ? i don't actually have any mt7620n hw with usb exported i think... I remember using ohci/ehci drivers for mt7620n boards (because otg driver didn't work at all) but not sure if I tried any usb 1.1 devices. Unfortunately I can't test it right now, maybe 2-3 days later. I can confirm ohci driver is not functional in latest trunk and this patch enables it. Tested on Asus RT-N14U. But: - the patch doesn't apply cleanly - kernel config should be revised (I see non usb changes and no changes for mt7620n) - the patch itself is pretty dirty to my eye Hi Roman, thanks for testing, i will figure out what the difference is in the code and try to figure out what is missing in our code John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker 14.07-rc1
Hi, we did rc1 and rc2 in trunk as we were fixing stuff. rc2 is almost ready, i already have the trunk built, the IB worked for all targets this time after our fixes. i am about to start one of the builder on old.packages and the other builder on all the other feeds. once that is done and rc2 is online we will most likely fork the release branch and only backport fixes from there on. John On 25/07/2014 14:09, Saverio Proto wrote: Hello John, there will be no release branch here ? http://git.openwrt.org/ thanks Saverio 2014-07-14 11:12 GMT+02:00 John Crispin j...@phrozen.org: The OpenWrt developers are proud to announce the first release candidate of OpenWrt Barrier Breaker. ___ __ | |.-.-.-.| | | |..| |_ | - || _ | -__| || | | || _|| _| |___|| __|_|__|__||||__| || |__| W I R E L E S S F R E E D O M - BARRIER BREAKER (14.07 RC1) - * 1/2 oz Galliano Pour all ingredients into * 4 oz cold Coffee an irish coffee mug filled * 1 1/2 oz Dark Rum with crushed ice. Stir. * 2 tsp. Creme de Cacao - http://downloads.openwrt.org/barrier_breaker/14.07-rc1/ ** Highlights since Attitude Adjustment ** Default configuration and images * Linux kernel updated to version 3.10 * Procd: new preinit, init, hotplug and event system written in C * Native IPv6-support - RA DHCPv6+PD client and server - Local prefix allocation source-restricted routes (multihoming) * Filesystem improvements - Added support for sysupgrade on NAND-flash - Added support for filesystem snapshot and rollback - Rewritten mounting system in C for rootfs and block devices * UCI configuration improvements - Support for testing configuration and rollback to working last working state - Unified change trigger system to restart services on-demand - Added a data validation layer * Networking improvements - Netifd now handles setup and configuration reload of wireless interfaces - Added reworked event support to allow obsoleting network hotplug-scripts - Added support for dynamic firewall rules and zones - Added support for transparent multicast to unicast translation for bridges - Various other fixes and improvements Additional highlights selectable in the package feeds or SDK * Extended IPv6-support - Added DS-Lite support and improved 6to4, 6in4 and 6rd-support - Experimental support for Lightweight 4over6, MAP-E and MAP-T - Draft-support for self-managing home networks (HNCP) * rpcd: new JSONRPC over HTTP-frontend for remote access to ubus * mdns: new lightweight mdns daemon (work in progress) * Initial support for the musl C standard library * Support for QMI-based 3g/4g modems * Support for DNSSEC validation * Added architecture for package signing and SHA256 hashing * ... and many more cool things Package feed reorganization For quite a while already we are not very satisfied with the quality of the packages-feed. To address this, we decided to do a fresh start on GitHub. The new feed https://github.com/openwrt/packages should be used from now on and package maintainers are asked to move their packages there. For the final release we will still build the old packages feed but it will be necessary to enable it manually in the opkg package list to be usable. All current feeds should not have any dependencies on the old.packages feed. Currently a few packages still fail, mainly due to these cross feed dependencies. We will contact the respective maintainers to help resolve these issues for RC2. New build servers We would like to express our gratitude to Imagination Technology for funding the 2 build servers that we used for the release. Whats next ? We aim at releasing Chaos Calmer (CC) before the end of the year. The CC release will use 3.14 or a newer LTS kernel as baseline. Have fun! The OpenWrt developer team ___ 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] Barrier Breaker 14.07-rc1
On 25/07/2014 16:36, Aaron Z wrote: Will Nano and WiFiDog be in RC2? They are in trunk, but were not included in RC1. Aaron Z Hi, they are not in trunk and hence were not in rc1 :) the old.packages feed and the maintained feeds will all be in rc2 John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Barrier Breaker 14.07-rc1
On 25/07/2014 17:36, Aaron Z wrote: - Original Message - On Friday, July 25, 2014 10:44:42 AM John Crispin j...@phrozen.org wrote: Subject: Re: [OpenWrt-Devel] Barrier Breaker 14.07-rc1 they are not in trunk and hence were not in rc1 :) the old.packages feed and the maintained feeds will all be in rc2 I must be confused then. I was going by the fact that they still show up in the trunk snapshots: http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/nano_2.3.6-1_ar71xx.ipk http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/wifidog_20130917-440445db60b0c3aff528ea703a828b0567293387_ar71xx.ipk Is there another place where I should be looking for trunk snapshots? Aaron Z ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel Hi, ok, sorry i get it ... there is a collision of meaning of trunk. i meant that nano is in a feed and not in the main subversion repository. we only built the main repo for rc1 as too many feeds packages still failed. anyhow as of rc2 you will see all the packages you are used to. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 12/23] ar71xx: refresh 451-gpio-74x164-improve-platform-device-support.patch
On 26/07/2014 04:48, Zhao, Gang wrote:
--if (!spi-dev.of_node) { -- dev_err(spi-dev, No device
tree
data available.\n); +pdata = spi-dev.platform_data; + np =
spi-dev.of_node; + + if (!np !pdata) { + dev_err(spi-dev,
No configuration data available.\n);
Hi,
these patches are not refreshes but you actually change the code path.
please resend the whole series with proper annotations inside the
various patch descriptions and subjects.
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH 12/23] ar71xx: refresh 451-gpio-74x164-improve-platform-device-support.patch
On 26/07/2014 08:30, John Crispin wrote:
On 26/07/2014 04:48, Zhao, Gang wrote:
-- if (!spi-dev.of_node) { -- dev_err(spi-dev, No device
tree data available.\n); + pdata = spi-dev.platform_data; + np
= spi-dev.of_node; + + if (!np !pdata) { +
dev_err(spi-dev, No configuration data available.\n);
Hi,
these patches are not refreshes but you actually change the code
path.
please resend the whole series with proper annotations inside the
various patch descriptions and subjects.
John
ok, apparently i had not finished my coffee when reading the patches ...
i am not entirely sure if copying the patches and then fixing them 1
by 1 is the best idea really. lets see what others have to say ...
___ 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] [PATCH] ramips: ethernet mac cleanup
On 24/07/2014 12:22, Roman Yeryomin wrote: Compile tested all subtargets and profiles. Unfortunately I don't own any board affected by these changes, so no run tests. Signed-off-by: Roman Yeryomin ro...@advem.lv Hi Roman, thanks i had this on my list for what feels like decades ... i just added this to my local tree and will test it on 2-3 boards just to be double sure. John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [OT] Anyone interested in donating Broadcom development?
On 27/07/2014 23:07, Rafał Miłecki wrote: Note: this is *not* anyhow officially related to the OpenWrt! This is my private request, I use OpenWrt ML just to reach ppl interested in this topic. Also I can't guarantee my development will success and can't guarantee any progress in any reasonable time. if it makes you feel better i can add the official bit, you have done a pile of great work recently :) official we would like to officially ask those who think that Rafał's work on brcm is important to help him out by donating the named/requested materials to him ... and as usual his work is on a best effort basis /official John ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
