can do that.
Regards,
Hante
-Original Message-
From: Rafał Miłecki [mailto:zaj...@gmail.com]
Sent: vrijdag 24 april 2015 14:08
To: Hante Meuleman
Cc: Ian Kent; Arend Van Spriel; Jonas Gorski; mailinglist
Subject: Re: [OpenWrt-Devel] Fwd: Re: [PATCH 10/10] brcmfmac: Add support for
7 8t". I can use cpu port 8 and config
vlan1ports "0 1 2 3 5t" without a problem. So there might be an issue
in the switch code, but there are more problems with this configuration
in other areas.
-Original Message-----
On Thu, 2015-04-23 at 14:48 +, Hante Meuleman wr
in other areas.
-Original Message-----
On Thu, 2015-04-23 at 14:48 +, Hante Meuleman wrote:
> Thank you for the information Ian, that was very helpful. Just found
> part of the problem. My R8000 used to work quite well, till I upgraded
> to new Netgear firmware. The
current bgmac is incorrectly determining the
ethertype as the function eth_type_trans won't take this vlan tag
into account. Trying some trickery (based upon flags in header of
rx frame) to make it work.
-Original Message-
On 29 April 2015 at 12:51, Hante Meuleman wrote:
> Statu
will work on the r8000.
-Original Message-
On 29 April 2015 at 12:51, Hante Meuleman wrote:
> Status report: spent lots of time trying to figure out how to use cpu
> port 8 and use vlan1ports "0 1 2 3 5 7 8t", and found that I got fooled
> by the way I tried to determin
Do not mimic the vlan configuration in some devices like R8000 as the
configuration is to be used with SW accelerators not available in OpenWRT.
It is not possible to use the switch with vlan port configuration 0 1 2 3 5 7
8,
without making some huge modifications. When this configuration is us
The R8000 AP has more than 32K nvram memory. This was an issue for the
userspace app "nvram". This got fixed at some point, but then it was reverted:
http://git.openwrt.org/?p=openwrt.git;a=commit;h=9258d82f1d4a79f86ea72aad349b3f3eeb772d87
Why was it reverted? Would be good to know what exact rea
The boot script gives 1 second for wifi modules to settle. For newer routers
like R8000 which has three wifi devices which all need to be firmware
downloaded, nvram downloaded and initialized this delay is getting very
tight. On some bootups it was seen that not all wifi modules were
initialized by
---
From: Felix Fietkau [mailto:n...@openwrt.org]
On 2015-05-12 10:35, Hante Meuleman wrote:
> The boot script gives 1 second for wifi modules to settle. For newer
> routers
>
> like R8000 which has three wifi devices which all need to be firmware
>
> downloaded, nvram downloa
[mailto:zaj...@gmail.com]
On 12 May 2015 at 11:33, Hante Meuleman wrote:
> Understood, what is wifi detect using as input? Do the netdevs have to
> be up? Where is the information that wifi app is reading coming from?
What about just checking it by yourself?
vim package/base-files/files/sbi
From: Felix Fietkau [mailto:n...@openwrt.org]
On 2015-05-12 11:33, Hante Meuleman wrote:
> Understood, what is wifi detect using as input? Do the netdevs have to
> be up? Where is the information that wifi app is reading coming from?
It looks for registered cfg80211 wiphys. It does not
Added two functions to the bcm47xx_nvram module to get and release copies
of the complete nvram contents. This can be used by for example brcmfmac
to get complete nvram contents which will after some parsing be sent to
device.
Signed-off-by: Hante Meuleman
---
diff --git
a/target/linux
ion in the c file.
-Original Message-
From: Felix Fietkau [mailto:n...@openwrt.org]
Sent: dinsdag 12 mei 2015 22:03
To: Hante Meuleman; OpenWrt Development List
Subject: Re: [OpenWrt-Devel] [PATCH] bcm53xx: Add functions to get/release
copies of nvram contents.
On 2015-05-12 15:10, Hant
on the forum?
On Wed, 2015-04-22 at 11:45 +, Hante Meuleman wrote:
> Today I wrote the original firmware back on the device
> (using the latest from netgear). This worked and the device
> was working fine. Then I flashed openwrt again, now the
> switch didn’t work
an1ports in /etc/config/network then with older
firmware. This setting determines whether or not the switch is going to
work (as you already figured out).
Still investigating to as of why this setting doesn't work with b53 driver.
-Original Message-
On Wed, 2015-04-22 at 11:45 +, H
--Original Message-
On 23 April 2015 at 13:14, Hante Meuleman wrote:
> Attached are
> three files, one is from brcmfmac (firmware.c). This file is
> added to demo how brcmfmac will use a new function of
> bm47xx_nvram. The changes in this file are currently under
> internal review
Attached are the two patch files. They were generated from
include/linux/bcm47xx_nvram.h and from
drivers/firmware/broadcom/bcm47xx_nvram.c.
Sorry about the confusion regarding the
target/linux/bcm53xx/patches-3.18/110-firmware-backport-NVRAM-driver.patch
I was looking at an older repo where th
17 matches
Mail list logo