On 10 March 2015 at 04:43, Tymon wrote:
> my cpu is BCM958522ER which is the same series with 4708 as well, 32MB
> ###boot log: (I updated the xxx-squashfs.trx to the flash)
>
> Hit any key to stop autoboot: 0
> Checking TRX Image at addr 1e20 ...
>Uncompressing ... Primary TRX image OK
On 10 March 2015 at 04:43, Tymon wrote:
> my cpu is BCM958522ER which is the same series with 4708 as well, 32MB
> ###boot log: (I updated the xxx-squashfs.trx to the flash)
>
> Hit any key to stop autoboot: 0
> Checking TRX Image at addr 1e20 ...
>Uncompressing ... Primary TRX image OK
my cpu is BCM958522ER which is the same series with 4708 as well, 32MB spi-nor
flash,
###my dts file is :
/*
* Broadcom BCM470X / BCM5301X ARM platform code.
* DTS for -
*
* Copyright (C) 2014
*
* Licensed under the GNU/GPL. See COPYING for details.
*/
/dts-v1/;
#include "bcm4708
The Netgear R8000 has a PEX8603 connected to the BCM53012 and if
it isn't configured during the bus scan the PCI layer goes crazy
trying to configure phantom devices.
Signed-off-by: Ian Kent
---
.../172-bcm5301x-R8000-handle-PEX8603-switch.patch | 225
.../172-bcm5301x-R800
After a vendor firmware install the values seen in nvram for et0macaddr
and et1macaddr are that of nvram macaddr and nvram macaddr+1.
So set them that way here too.
Signed-off-by: Ian Kent
---
...53xx-deal-with-R8000-mac-address-settings.patch | 83
...53xx-deal-with-R800
The R8000 nvram is larger than 32k, increase nvram allocation to
64k to accomadate.
Signed-off-by: Ian Kent
---
...3xx-increase-nvram-allocation-size-to-64k.patch | 19 +++
...3xx-increase-nvram-allocation-size-to-64k.patch | 20
2 files changed, 39 inser
Add new sprom revision 11 variables to the nvram -> sprom reader.
Signed-off-by: Ian Kent
---
.../111-bcm53xx-add-sprom-rev-11-vars.patch| 426
.../111-bcm53xx-add-sprom-rev-11-vars.patch| 432
2 files changed, 858 insertions(+)
create
Fix thinko' in the bcm47xx sprom driver.
Signed-off-by: Ian Kent
---
.../bcm53xx/files/drivers/misc/bcm47xx-sprom.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/bcm53xx/files/drivers/misc/bcm47xx-sprom.c
b/target/linux/bcm53xx/files/drivers/misc/bcm47x
Looks like the BCM53012 has a similar problem to the BCM53011.
Signed-off-by: Ian Kent
---
...-pcie2-bcma-add-new-PCIe2-driver-for-bcma.patch | 12 +++-
...-pcie2-bcma-add-new-PCIe2-driver-for-bcma.patch | 12 +++-
2 files changed, 22 insertions(+), 2 deletions(-)
diff --git
Rather than struggle working out what needs what I thought it better
to update and resend with the few changes you recommended so we can
work from there.
---
Ian Kent (6):
bcm53xx: fixup early device id 8012
bcm53xx: fix typo in bcm47xx sprom driver
bcm53xx: update sprom from nv
The following series implements...
---
Ian Kent (6):
bcm53xx: fixup early device id 8012
bcm53xx: fix typo in bcm47xx sprom driver
bcm53xx: update sprom from nvram to handle rev 11
bcm53xx - increase nvram allocation size to 64k
bcm53xx: deal with R8000 mac address s
From
https://forum.openwrt.org/viewtopic.php?id=45176
"quote"
Since router CPUS are relatively slow and uni core, expect 2 to 4 times
performance gain if you were to use Hardware NAT.
Open source gives you freedom to shape your router any way you like. You
can even do your own coding in C, BASH, L
Just a heads up, Qualcomm Atheros actually have their current hardware NAT
code open source at codeaurora repository.
https://www.codeaurora.org/cgit/quic/qsdk
Check oss/lklm/qca-ssdk and
oss/ssdk-shell
The only issue is integration into OpenWrt with breaking compatibility with
other arch which O
Alpha Sparc wrote:
> I believe it is due to the hardware NAT not supported.
So, really, nothing to do with wifi drivers at all.
You don't need (hardware) NAT if you run IPv6...
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://
I believe it is due to the hardware NAT not supported.
On Mar 10, 2015 9:52 AM, "Michael Richardson" wrote:
>
>
> valent.turko...@gmail.com wrote:
> > Why it OpenWrt slower than stock firmware? I can help by shining a
bit
> > of light onto this subject. I'm developing custom firwmares bas
valent.turko...@gmail.com wrote:
> Why it OpenWrt slower than stock firmware? I can help by shining a bit
> of light onto this subject. I'm developing custom firwmares based on
I'm curious about this claim to begin with.
Of the people who say this, how many of them actually know how to m
On Mon, 9 Mar 2015, José Vázquez wrote:
OpenWRT is a linux distro oriented to networking so the kernel and
drivers are important, but you must not forget that the init process
(procd and related after AA) is one of the cores of this distro and
makes it work. The most relevant packages are orient
2015-03-09 21:02 GMT+01:00, valent.turko...@gmail.com
:
> Hi all,
> I see this or similar question of forums all the time and I have
> answered it few times. I suggest we open a wiki page and contribute an
> answer.
>
> Here is how I usually reply to similar questions, please give your
> comments i
On Mar 9, 2015, at 1:19 PM, Charlie Smurthwaite wrote:
> On 09/03/15 20:02, valent.turko...@gmail.com wrote:
>> Main issue is that wifi chip manufacturers don't offer open source
>> wifi drivers. If Atheros and Broadcom understood Open source as Intel
>> does then you would get absolutely top sp
On Mon, Mar 9, 2015 at 1:19 PM, Charlie Smurthwaite
wrote:
> On 09/03/15 20:02, valent.turko...@gmail.com wrote:
>>
>> Main issue is that wifi chip manufacturers don't offer open source
>> wifi drivers. If Atheros and Broadcom understood Open source as Intel
>> does then you would get absolutely t
Hello Valent,
I think, despite that fact you will get some opposition about some
points you mentioned here, your email was a good email in my point of view.
First the the most controversial point about how much Atheros contribute
to the open-source world and to Linux is seems to be that they
On 09/03/15 20:02, valent.turko...@gmail.com wrote:
Main issue is that wifi chip manufacturers don't offer open source
wifi drivers. If Atheros and Broadcom understood Open source as Intel
does then you would get absolutely top speed and reliability from
OpenWrt wifi drivers. You don't get top no
If you think Atheros hates Linux and doesn't contribute to the open source
driver after "a few years" of experience with OpenWrt you need to go back
to where ever you came from and keep studying.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.
Hi all,
I see this or similar question of forums all the time and I have
answered it few times. I suggest we open a wiki page and contribute an
answer.
Here is how I usually reply to similar questions, please give your
comments in your replies:
Why it OpenWrt slower than stock firmware? I can he
hi,
my Archer-c5 has 10 LEDs, but in sysfs only the following LEDs are
usable/visible:
$ ls /sys/class/leds
ath9k-phy1 tp-link:blue:wlan2g tp-link:green:usb2
tp-link:blue:qss tp-link:blue:wlan5g
tp-link:blue:system tp-link:green:usb1
$ cat /sys/kernel/debug/gpio
GPIOs 0-23, at
On Mon, 2015-03-09 at 10:28 +0100, Rafał Miłecki wrote:
> On 9 March 2015 at 10:21, Rafał Miłecki wrote:
> > On 9 March 2015 at 10:08, Ian Kent wrote:
> >> Here are some changes done while working to get the R8000 working.
> >> Some are straight forward while some require review.
> >
> > Thanks :
On Mon, 2015-03-09 at 10:23 +0100, Rafał Miłecki wrote:
> On 9 March 2015 at 10:08, Ian Kent wrote:
> > Looks like the BCM53012 has a similar problem to the BCM53011.
>
> Change looks OK, however I'd prefer you to simply modify existing
> patch 170-pcie2-bcma-add-new-PCIe2-driver-for-bcma.patch
>
On 9 March 2015 at 10:21, Rafał Miłecki wrote:
> On 9 March 2015 at 10:08, Ian Kent wrote:
>> Here are some changes done while working to get the R8000 working.
>> Some are straight forward while some require review.
>
> Thanks :)
>
> One request: please use "bcm53xx: " prefix, as it's what we do
On 9 March 2015 at 10:08, Ian Kent wrote:
> Looks like the BCM53012 has a similar problem to the BCM53011.
Change looks OK, however I'd prefer you to simply modify existing
patch 170-pcie2-bcma-add-new-PCIe2-driver-for-bcma.patch
It still wasn't included/accepted mainline, so it's safe to update
On 9 March 2015 at 10:08, Ian Kent wrote:
> Here are some changes done while working to get the R8000 working.
> Some are straight forward while some require review.
Thanks :)
One request: please use "bcm53xx: " prefix, as it's what we do since always.
I'll try to reply to all patches as I find
The Netgear R8000 has a PEX8603 connected to the BCM53012 and if
it isn't configured during the bus scan the PCI layer goes crazy
trying to configure phantom devices.
---
.../172-bcm5301x-R8000-handle-PEX8603-switch.patch | 225
.../172-bcm5301x-R8000-handle-PEX8603-switch.pa
After a vendor firmware install the values seen in nvram for et0macaddr
and et1macaddr are that of nvram macaddr and nvram macaddr+1.
So set them that way here too.
Signed-off-by: Ian Kent
---
...53xx-deal-with-R8000-mac-address-settings.patch | 83
...53xx-deal-with-R800
The R8000 nvram is larger than 32k, increase nvram allocation to
64k to accomadate.
---
...3xx-increase-nvram-allocation-size-to-64k.patch | 19 +++
...3xx-increase-nvram-allocation-size-to-64k.patch | 20
2 files changed, 39 insertions(+)
create mode 1006
Add new sprom revision 11 variables to the nvram -> sprom reader.
Signed-off-by: Ian Kent
---
.../111-bcm53xx-add-sprom-rev-11-vars.patch| 426
.../111-bcm53xx-add-sprom-rev-11-vars.patch| 432
2 files changed, 858 insertions(+)
create
Fix thinko' in the bcm47xx sprom driver.
Signed-off-by: Ian Kent
---
.../bcm53xx/files/drivers/misc/bcm47xx-sprom.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/bcm53xx/files/drivers/misc/bcm47xx-sprom.c
b/target/linux/bcm53xx/files/drivers/misc/bcm47x
Looks like the BCM53012 has a similar problem to the BCM53011.
Signed-off-by: Ian Kent
---
.../171-bcm5301x-fixup-early-device-id-8012.patch | 26
.../171-bcm5301x-fixup-early-device-id-8012.patch | 26
2 files changed, 52 insertions(+)
create mod
Here are some changes done while working to get the R8000 working.
Some are straight forward while some require review.
I'm not sure if I've done the sprom rev 11 change the way it should
be done so that needs fairly close review.
I thought about making a seperate driver for the the PEX8603 in th
37 matches
Mail list logo
