| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
SVN-Revision: 33598
|
|
|
|
|
|
|
|
|
|
| |
The bcma based SoCs with a ieee80211 core on the SoC and an other
connected via PCIe or USB store the sprom for the SoC with a sb/1/
prefix. The SoC with just one wifi core do not use prefixes. The
BCM4706 do not use a prefix for the SoC part at all, because the prefix
is the path to the ieee80211 core and there is non on the BCM4706.
SVN-Revision: 33597
|
|
|
|
|
|
| |
This will hopefully fix bug #9360 and #9097 in trunk.
SVN-Revision: 33596
|
|
|
|
|
|
| |
have the right dependency
SVN-Revision: 33593
|
|
|
|
| |
SVN-Revision: 33592
|
|
|
|
| |
SVN-Revision: 33591
|
|
|
|
|
|
| |
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33581
|
|
|
|
|
|
| |
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33580
|
|
|
|
|
|
|
|
|
| |
Resolves an issue where isochronouse USB would cause the driver to hang as
well as scheduling issues.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33579
|
|
|
|
| |
SVN-Revision: 33575
|
|
|
|
|
|
|
|
|
|
| |
This feature was experimental in old kernels but
that flag has been removed in 2.6.36. Additionally,
the option is enabled by default since then.
See: http://www.spinics.net/lists/linux-usb/msg31993.html
SVN-Revision: 33574
|
|
|
|
| |
SVN-Revision: 33571
|
|
|
|
| |
SVN-Revision: 33570
|
|
|
|
|
|
| |
Required for recent (e)glibc systems
SVN-Revision: 33569
|
|
|
|
|
|
|
|
|
| |
For cns3xxx SCU_CONFIGURATION always shows multipe cores but SCU_CPU_STATUS
shows which ones are active.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33566
|
|
|
|
|
|
| |
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33565
|
|
|
|
|
|
| |
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33564
|
|
|
|
|
|
| |
This is no longer a dependency of kmod-spi-bcm63xx
SVN-Revision: 33562
|
|
|
|
| |
SVN-Revision: 33560
|
|
|
|
| |
SVN-Revision: 33559
|
|
|
|
| |
SVN-Revision: 33558
|
|
|
|
| |
SVN-Revision: 33556
|
|
|
|
| |
SVN-Revision: 33555
|
|
|
|
| |
SVN-Revision: 33554
|
|
|
|
| |
SVN-Revision: 33549
|
|
|
|
| |
SVN-Revision: 33548
|
|
|
|
| |
SVN-Revision: 33547
|
|
|
|
|
|
|
|
|
|
|
| |
Sometimes the port 0 was the WAN port or there could be some device
where the port 0 is not wired to an actual Ethernet port. Now telnet in
failsafe will listen on all ports of the switch so user do not have to
search for the correct port any more. This change will make the switch
leak traffic between the WAN and the LAN port, but you should not use
failsafe while connected to a untrusted network.
SVN-Revision: 33544
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With these images, it is possible to use the 'unused'
partition of the flash. The 'fat' images can be installed
with the sysupgrade command. When a 'fat' image is
installed from a regular one, the platform specific
sysupgrade script copies the calibration data to the
end of the flash. Likewise, when a regular image is
installed from the 'fat' version the sysupgrade script
copies the calibration data back to the original location.
SVN-Revision: 33540
|
|
|
|
| |
SVN-Revision: 33539
|
|
|
|
| |
SVN-Revision: 33538
|
|
|
|
| |
SVN-Revision: 33537
|
|
|
|
| |
SVN-Revision: 33536
|
|
|
|
|
|
| |
Should fix #12211. Compile tested only.
SVN-Revision: 33535
|
|
|
|
| |
SVN-Revision: 33525
|
|
|
|
| |
SVN-Revision: 33516
|
|
|
|
| |
SVN-Revision: 33515
|
|
|
|
|
|
| |
from usb devices
SVN-Revision: 33514
|
|
|
|
| |
SVN-Revision: 33513
|
|
|
|
| |
SVN-Revision: 33511
|
|
|
|
| |
SVN-Revision: 33510
|
|
|
|
| |
SVN-Revision: 33504
|
|
|
|
|
|
| |
performance with jumbo frames
SVN-Revision: 33503
|
|
|
|
| |
SVN-Revision: 33502
|
|
|
|
| |
SVN-Revision: 33501
|
|
|
|
| |
SVN-Revision: 33500
|
|
|
|
| |
SVN-Revision: 33499
|
|
|
|
|
|
| |
requirement of 64), fix skb fragment chaining
SVN-Revision: 33498
|
|
|
|
| |
SVN-Revision: 33497
|
|
|
|
|
|
|
|
|
| |
When not removing support for the wait instruction, when ruining on the
BCM4706 SoC the system stops after msleep() without an exception. I
haven't seen this problem on the other Broadcom SoCs with a 74K CPU,
but in the Broadcom SDK it is deactivated for all CPUs of this type.
SVN-Revision: 33496
|