Re: [OpenWrt-Devel] Introducing "fastpath" - Kernel module for speeding up IP forwarding

[Weedy]

On Dec 23, 2014 10:02 AM, "Tomer Eliyahu"  wrote:
>
> Hi,
>
> Our request for uploading the sources is pending approval from
> Marvell's legal department.
>
> Best Regards,
>
> Tomer

Please don't let this die.
Lawyers plea
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] barrier breaker 14.07 stable release location

[Madhu koriginja]

Hi All,
 Please somebody can point me the location from where can I
download the barrier breaker 14.07 stable release.
I saw in Openwrt wiki pages, barrier breaker SVN repository release version
is r42625 and release date is october 2nd(in some place I saw october 20).
I also saw barrier breaker branch still some development activity is
running(26th Jan also some changes are there)
So, please suggest me which version is stable release on barrier breaker.

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

Re: [OpenWrt-Devel] [PATCH 3/9] kernel: Allow ubi autoattach to run on NOR flash

[Maxime Ripard]

On Sun, Jan 25, 2015 at 08:50:32PM +0100, Imre Kaloz wrote:
> Hi,
> 
> On Sun, 25 Jan 2015 18:06:03 +0100, Maxime Ripard
>  wrote:
> 
> >>Sure, but please implement UBI on NOR as a generic solution.
> >
> >What do you mean? It already works quite well (with that patch applied
> >and the NOR sub-profile), so I'm not sure I have to implement
> >anything, be it generic or not.
> 
> I've meant to make it generic, like the squashfs/ubfs/etc images so other
> targets can use it, too.

Well, it uses only prepare_squashfs_image and UbinizeImage works great
for that already, the only thing that differ is the set of options
given to ubinize, so I'm not really sure how that can be turned into
something more generic.

> The A385-RD board has a much smaller SPI-NOR (16MB) though, so we
> could use jffs2 there, but I wasn't seeing much point at creating a
> whole new layout just for a single board.
> >>>
> >>>I'll switch this one to JFFS2 and the MTDSPLIT framework. Are you
> >>>satisfied with the NAND support? Just to know if I can continue to
> >>>model the NOR stuff on that.
> >>
> >>As I've written in the other mail, I'm mostly happy with it, but
> >>please make sure you don't hardcode available profiles but parse
> >>them.
> >
> >If we don't plan on supporting building single sub-profiles like
> >ar71xx, I'm not even sure that we need to parse anything, we can just
> >loop over the sub-profiles list in any case.
> 
> I think supporting that could be handy so users (and people at Marvell) can
> just build what they want.

Ok. But what/how do you want me to parse these profiles then? Apart
from plumbing into the Profile macro itself to add the list of
available profiles, and that would be way too intrusive, I don't
really get what you expect here.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com


signature.asc
Description: Digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] config: fix typo in Global build settings menu

[Daniel Golle]

Signed-off-by: Daniel Golle 
---
 config/Config-build.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config/Config-build.in b/config/Config-build.in
index 280f719..0ca145e 100644
--- a/config/Config-build.in
+++ b/config/Config-build.in
@@ -251,7 +251,7 @@ menu "Global build settings"
endchoice
 
choice
-   prompt "Enable buffer-overflows detction (FORTIFY_SOURCE)"
+   prompt "Enable buffer-overflows detection (FORTIFY_SOURCE)"
help
  Enable the _FORTIFY_SOURCE macro which introduces additional
  checks to detect buffer-overflows in the following standard 
library
-- 
2.2.2
___
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 stable release location

[Claudio Thomas]

Hi Madhu,

the releases of OpenWrt firmwares can be found at
http://downloads.openwrt.org/. For BB 14.07 stable for example
http://downloads.openwrt.org/barrier_breaker/14.07/. But to get the
right firmware for your device you need to know what target and profile
you need.

To find out if there is a 14.07 firmware for your hardware you could
look at http://wiki.openwrt.org/toh/start

Each Platform has a own description page (like
http://wiki.openwrt.org/toh/buffalo/wzr-600dhp), there you will normally
find an exact link to the actual firmware and how to update your device.
Link Example (don't use this! it is probably not for your device!):
http://downloads.openwrt.org/barrier_breaker/14.07/ar71xx/generic/openwrt-ar71xx-generic-wzr-600dhp-squashfs-sysupgrade.bin

Best regards,
Claudio

--
Reviewing OpenWrt BB for Xmodus Systems XM1710E GSM/UMTS Router



On 27.01.2015 14:30, Madhu koriginja wrote:
> Hi All,
>  Please somebody can point me the location from where can I
> download the barrier breaker 14.07 stable release.
> I saw in Openwrt wiki pages, barrier breaker SVN repository release
> version is r42625 and release date is october 2nd(in some place I saw
> october 20).
> I also saw barrier breaker branch still some development activity is
> running(26th Jan also some changes are there)
> So, please suggest me which version is stable release on barrier breaker.
>
> Thanks & Regards,
> Madhu
>
>
> ___
> 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 MERCURY MAC1200R

[Roger Pueyo Centelles]

Hi,

@Hartmut
Ok, now I see. Thanks!

@郭传鈜

Acoording to mach-archer-c7.c ,I think we should use ath79_register_pci();
> here and use /lib/preinit/81_load_ath10k_board_bin to load calibration
> data for ath10k.
>

So, I understand I have to remove this line from
target/linux/ar71xx/files/arch/mips/ath79/mach-mc-mac1200r.c

ap91_pci_init(art + MAC1200R_PCIE_CALDATA_OFFSET, tmpmac);

Then, the MACs in my router end in:
- eth0=>47
- eth1=>49
- wlan1=>4A

so it makes sense to have wlan0 ending in 48 (i.e. eth1 minus 1). In
target/linux/ar71xx/base-files/lib/preinit/81_load_ath10k_board_bin (art
partition is mtd4):

dd if=/dev/mtdblock4 \
bs=1 skip=20492 count=2104 >>
/tmp/ath10k-board.bin
;;
mc-mac1200r)
local mac
mac=$(macaddr_add $(cat
/sys/class/net/eth1/address) -1)

dd if=/dev/mtdblock4 \
bs=1 skip=20480 count=6 \
of=/tmp/ath10k-board.bin
macaddr_2bin $mac >> /tmp/ath10k-board.bin
dd if=/dev/mtdblock4 \
bs=1 skip=20492 count=2104 >>
/tmp/ath10k-board.bin
;;
r6100)
local mac
mac=$(macaddr_add $(cat
/sys/class/net/eth1/address) +2)

dd if=/dev/mtdblock2 \

>> +$(eval $(call
>> SingleProfile,TPLINK-LZMA,64kraw,MAC1200R,mc-mac1200r,MC-MAC1200R,ttyS0,115200,0x1201,1,8Mlzma))
>> >The factory image is broken since TP-LINK started to use a new firmware
>> format with RSA signature in China.This should be introduced in the TOH
>> wiki I think:)
>>
>
Besides adding this to the wiki, what should I change so that the factory
firmware is not generated?

Thanks!

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

Re: [OpenWrt-Devel] [PATCH] uboot-lantiq: fix P-2812HNU-F1/3 package dependency

[Ben Mulvihill]

Hi Antti,

(Note that the diffs in this message are for information. They are not
patches submitted for merging - not at this stage anyway.)

> I tried and it seems the ram version
> (openwrt-lantiq-p2812hnufx_ram-u-boot.asc) builds and boots properly.
> 
> The openwrt-lantiq-p2812hnufx_nandspl-u-boot.img indeed does not boot
> correctly. Is anyone working on fixing it? (Apparently conversion to
> TPL is needed)

I am working on the BT Home Hub 3A at the moment (arx100, nand-based 
board), and have also found that asc images build correctly but
nandspl images do not.

There seem to a number of problems. For a start some of the make 
targets seem to be missing. The following fixed that for arx100,
and I think that a similar fix is necessary for danube and vrx200
too.

--- a/arch/mips/cpu/mips32/arx100/config.mk 2015-01-27 12:33:32.0 
+0100
+++ b/arch/mips/cpu/mips32/arx100/config.mk 2015-01-27 18:07:37.0 
+0100
@@ -27,4 +27,9 @@ ALL-y += $(obj)u-boot.ltq.norspl
 ALL-$(CONFIG_SPL_LZO_SUPPORT) += $(obj)u-boot.ltq.lzo.norspl
 ALL-$(CONFIG_SPL_LZMA_SUPPORT) += $(obj)u-boot.ltq.lzma.norspl
 endif
+ifdef CONFIG_SYS_BOOT_NANDSPL
+ALL-y += $(obj)u-boot.ltq.nandspl
+ALL-$(CONFIG_SPL_LZO_SUPPORT) += $(obj)u-boot.ltq.lzo.nandspl
+ALL-$(CONFIG_SPL_LZMA_SUPPORT) += $(obj)u-boot.ltq.lzma.nandspl
+endif
 endif


Then the ebu configuration word needs to be set in the nandspl
image, as it is for norspl. Once again, the following fixed that
for arx100, and I think something similar will be required for danube
and vrx200.

--- a/arch/mips/include/asm/arch-arx100/config.h2015-01-27 
18:12:32.0 +0100
+++ b/arch/mips/include/asm/arch-arx100/config.h2015-01-27 
18:13:02.0 +0100
@@ -174,6 +174,10 @@
 #define CONFIG_XWAY_SWAP_BYTES
 #endif
 
+#if defined(CONFIG_SYS_BOOT_NAND) || defined(CONFIG_SYS_BOOT_NANDSPL)
+#define CONFIG_SYS_XWAY_EBU_BOOTCFG0x688C688C
+#endif
+
 #defineCONFIG_SYS_MONITOR_BASE CONFIG_SYS_TEXT_BASE
 
 #endif /* __ARX100_CONFIG_H__ */

Finally the ltq-boot-image tool adds a couple of download header to the
final image which I don't think should be there.

Daniel, does all the above make sense?

That said, even after making those changes my nandspl images still
don't work.

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

[OpenWrt-Devel] Anyone familiar with RouterBoot? Trying to port board.

[David Hutchison]

I have everything working on the Mikrotik mAP2n within initramfs.
WLAN, LAN, USB, LEDs, and even the flash chip.

The problem is when I write the kernel to flash I cannot for the life
of me get RouterBOOT to recognize the kernel. My partition layout
looks like this:

static struct mtd_partition rbmap_spi_partitions[] = {
{
.name = "kernel",
.offset = 128 * 1024,
.size = 0x60
},
{
.name = "rootfs",
.offset = 0x62,
.size = MTDPART_SIZ_FULL
},
{
.name = "firmware",
.offset = 128 * 1024,
.size = MTDPART_SIZ_FULL
},
{
.name = "RouterBoot",
.offset = 0,
.size = 128 * 1024,
.mask_flags = MTD_WRITEABLE,
},
};

[3.70] 0x0002-0x0100 : "firmware"
[3.71] 0x0013-0x0100 : "rootfs"
[3.71] mtd: partition "rootfs" set to be root filesystem
[3.72] split_squashfs: no squashfs found in "spi0.0"
[3.72] 0x0002-0x0062 : "kernel"
[3.73] 0x0062-0x0100 : "rootfs"
[3.74] 0x-0x0002 : "RouterBoot"

I know for sure that RouterBoot is 0x2 in size. RouterOS starts at
0x2 and is the only partition, it's size is MTDPART_SIZ_FULL. (
Without trying to get OpenWRT on )

I tried to define a kernel and rootfs partition, but that didn't seem
to work either.

Every other RouterBOARD I have ported too the kernel partition had to
be in YAFFS. However the mAP2n is a SPI flash. The partitions are not
passed by the bootloader, so they have to be defined somehow.

Is there anyone familiar with routerboot that could help point me in
the right direction? I was trying to mtdwrite vmlinux ( I even tried
dd ) to the kernel partition ( which would put it at 0x2, where it
*should* be ).

The files I tried to write were:
openwrt-ar71xx-generic-vmlinux.bin
openwrt-ar71xx-generic-vmlinux.elf

no go, routerboot would output:

---

RouterBOOT backup booter 3.17

RouterBOARD mAP 2n

CPU frequency: 400 MHz
  Memory size:  64 MiB
 Storage size:  16 MiB

Press any key within 2 seconds to enter setup
loading kernel from nand... kernel not found
trying bootp protocol OK

---

Previous RouterBOARDS would not support compressed kernels, I tried
them anyway as this SPI flash seems new for Mikrotik... Still a no-go.

Here is the kernel cmdline within initramfs:
Kernel command line:  bootimage=1 no-uart no-nand parts=1
boot_part_size=16777216 gpio=822077383 HZ=2 mem=64M
kmac=4C:5E:0C:CA:27:0E board=mAP boot=0 mlc=6

I'm not familiar with OpenWRT's image builder, so i'm not sure how I
could create an image for it. I'm not at this point yet, just trying
to get RouterBOOT to execute my kernel.

---

I have UART working but the RX on the board does not seem to see ANY
of my INPUT at the boot-loader level. I can see output, but cannot
provide input... I can't really look at the boot-loader directly :-/

Any ideas?

Here is my mach-rbmap.c thus far:

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#include 
#include 
#include 

#include "common.h"
#include "dev-ap9x-pci.h"
#include "dev-eth.h"
#include "dev-spi.h"
#include "dev-gpio-buttons.h"
#include "dev-leds-gpio.h"
#include "dev-m25p80.h"
#include "dev-usb.h"
#include "dev-wmac.h"
#include "machtypes.h"
#include "routerboot.h"

#define RB_ROUTERBOOT_OFFSET0x
#define RB_ROUTERBOOT_SIZE  0xe000
#define RB_HARD_CFG_OFFSET  0xe000
#define RB_HARD_CFG_SIZE0x1000

#define RB_ART_SIZE 0x1

static struct mtd_partition rbmap_spi_partitions[] = {
{
.name = "kernel",
.offset = 128 * 1024,
.size = 0x60
},
{
.name = "rootfs",
.offset = 0x62,
.size = MTDPART_SIZ_FULL
},
{
.name = "firmware",
.offset = 128 * 1024,
.size = MTDPART_SIZ_FULL
},
{
.name = "RouterBoot",
.offset = 0,
.size = 128 * 1024,
.mask_flags = MTD_WRITEABLE,
},
};

static struct flash_platform_data rbmap_spi_flash_data = {
.parts  = rbmap_spi_partitions,
.nr_parts   = ARRAY_SIZE(rbmap_spi_partitions),
};

static void __init rbmap_wlan_init(void)
{
u8 *hard_cfg = (u8 *) KSEG1ADDR(0x1f00 + RB_HARD_CFG_OFFSET);
u16 tag_len;
u8 *tag;
char *art_buf;
u8 wlan_mac[ETH_ALEN];
int err;

err = routerboot_find_tag(hard_cfg, RB_HARD_CFG_SIZE, RB_ID_WLAN_DATA,
  &tag, &tag_len);
if (err) {
pr_err("no calibration data found\n

[OpenWrt-Devel] How To Create a Package Tutorial

[Eric Schultz]

All,

I've completed a tutorial on how to create a simple package. I'm not
sure it'll get much use from the folks on here but I figured I'd let
people know. I hope it helps you or someone else learn how to make an
OpenWrt package.

The tutorial is at
http://wiki.prplfoundation.org/wiki/Creating_an_OpenWrt_package_for_a_web_page

Thanks,

Eric

-- 
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
eschu...@prplfoundation.org
cell: 920-539-0404
skype: ericschultzwi
@EricPrpl
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Anyone familiar with RouterBoot? Trying to port board.

[Soren Harward]

On Tue, Jan 27, 2015 at 12:56 PM, David Hutchison
 wrote:
> The problem is when I write the kernel to flash I cannot for the life
> of me get RouterBOOT to recognize the kernel.

What is the filename of the kernel on the yaffs2 filesystem on the
kernel MTD partition?  AFAIK, RouterBoot expects it to be called
"kernel".  Not "vmlinux" or "vmlinuz" or
"openwrt-ar71xx-generic-vmlinux.elf" or anything else.

-- 
Soren Harward
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Anyone familiar with RouterBoot? Trying to port board.

[David Hutchison]

The problem is there is no yaffs2 filesystem like typical
RouterBOARD's, it's all one 16mb SPI flash chip.

If it expects kernel, would renaming the .elf file to just "kernel" be
sufficient? I suppose I could give that a try.

-- Davey

On Tue, Jan 27, 2015 at 5:38 PM, Soren Harward  wrote:
> On Tue, Jan 27, 2015 at 12:56 PM, David Hutchison
>  wrote:
>> The problem is when I write the kernel to flash I cannot for the life
>> of me get RouterBOOT to recognize the kernel.
>
> What is the filename of the kernel on the yaffs2 filesystem on the
> kernel MTD partition?  AFAIK, RouterBoot expects it to be called
> "kernel".  Not "vmlinux" or "vmlinuz" or
> "openwrt-ar71xx-generic-vmlinux.elf" or anything else.
>
> --
> Soren Harward
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] [ar71xx] Add default LED configuration for D-Link DIR-615 rev. C1

[Vincent Wiemann]

This patch adds an entry in the uci-defaults' led-file to configure the
WAN and WLAN LEDs by default.
Signed-off-by: Vincent Wiemann 


--- a/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
+++ b/target/linux/ar71xx/base-files/etc/uci-defaults/01_leds
@@ -116,6 +116,11 @@ dir-615-e4)
ucidef_set_led_switch "lan4" "LAN4" "d-link:green:lan4" "switch0" "0x10"
;;

+dir-615-c1)
+   ucidef_set_led_netdev "wan" "WAN" "d-link:green:wan" "eth1"
+   ucidef_set_led_wlan "wlan" "WLAN" "d-link:green:wlan" "phy0tpt"
+   ;;
+
 dir-825-b1)
ucidef_set_led_usbdev "usb" "USB" "d-link:blue:usb" "1-1"
;;



signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] ralink: check ethernet MAC address whether it is valid

[wengbj]

From: wengbj 

The mac address usually write in factory block. but sometime user erase this 
block , the mac address will change to ff:ff:ff:ff:ff:ff.
This patch is purpose to fix this issue.
---
 .../drivers/net/ethernet/ralink/ralink_soc_eth.c   |4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git 
a/target/linux/ramips/files/drivers/net/ethernet/ralink/ralink_soc_eth.c 
b/target/linux/ramips/files/drivers/net/ethernet/ralink/ralink_soc_eth.c
index d7d1e8e..9900a5e 100644
--- a/target/linux/ramips/files/drivers/net/ethernet/ralink/ralink_soc_eth.c
+++ b/target/linux/ramips/files/drivers/net/ethernet/ralink/ralink_soc_eth.c
@@ -1220,8 +1220,10 @@ static int __init fe_init(struct net_device *dev)
if (priv->soc->switch_init)
priv->soc->switch_init(priv);
 
-   memcpy(dev->dev_addr, priv->soc->mac, ETH_ALEN);
of_get_mac_address_mtd(priv->device->of_node, dev->dev_addr);
+   /*If the mac address is invalid, use default mac address  */
+   if (!is_valid_ether_addr(dev->dev_addr))
+   memcpy(dev->dev_addr, priv->soc->mac, ETH_ALEN);
 
err = fe_mdio_init(priv);
if (err)
-- 
1.7.9.5
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Announcement of mac80211 driver support for Marvell 88W8864 chip

[David Lin]

Hi Ian,

Thanks for the feedback.
1. Client mode support is already in the work. We will plan to release 
it as soon as available. It should be in time for coming WRT1200AC.
2. We will add description to the rate related info.

Thanks,
David

-Original Message-
From: Ian Kent [mailto:ra...@themaw.net] 
Sent: Saturday, January 24, 2015 5:37 PM
To: David Lin
Cc: Jiri Pirko; openwrt-devel@lists.openwrt.org; Imre Kaloz; Chor Teck Law
Subject: Re: [OpenWrt-Devel] Announcement of mac80211 driver support for 
Marvell 88W8864 chip

On Mon, 2015-01-12 at 19:03 -0800, David Lin wrote:
> Hi Ian,
> 
>   1. I will take off these additional blank lines.
>   2. I work for problems reported from community. If you do find problems 
> for the driver, please let me know.

Hi David,

I was disappointed to find that client mode wireless in the driver isn't 
supported yet.

I logged an issue for it at https://github.com/kaloz/mwlwifi/issues/13
along with the kernel WARN() info.

As I say in the issue I believe that client mode is quite important for the 
coming WRT1200AC, assuming the wireless on that device is to be supported by 
this driver.

I've been looking at the driver source and I'm a bit puzzled about the rate and 
ht_sig2 fields in the receive descriptor structure. There's no documentation 
(that I can locate) on the interface to the wireless device so I can't refer to 
it.

It appears the rate field isn't just a rate or an index into the rate table or 
just an MCS rate either. So can you describe what the encoding is please?

The ht_sig2 field has a describing comment of "as the name suggests" but HT SIG 
2 is 24 bits not 16 and even if the CRC and tail fields were discarded, I see 
there's more than the remaining 10 bits being used in the field. So can you 
describe the encoding in this field too please?

The other puzzling thing is the handling of VHT modes.
I don't see anything in the receive descriptor for that case.
It looks like the wireless device handles the rate (along with a lot
more) but how does the driver find out the VHT information that it may need for 
informational and reporting purposes (up to the mac80211 layer).

Could you help with this please.

These questions may sound like I don't know low level wireless concepts and 
that would be correct, but I'm slowly working on that, so sorry for the 
possibly silly questions.

Ian

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