| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
SVN-Revision: 27457
|
|
|
|
|
|
|
|
| |
couple of weeks.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27373
|
|
|
|
|
|
|
|
| |
require the MFD driver to be present for the BAR's to be mapped.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27371
|
|
|
|
|
|
|
|
| |
MFD driver to be present for the BAR's to be mapped."
This reverts commit c485487b63d1c1de72a375f1278d8a98546ba3af.
SVN-Revision: 27370
|
|
|
|
|
|
|
|
| |
driver to be present for the BAR's to be mapped.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27369
|
|
|
|
|
|
| |
unlocked_ioctl on all platforms and fix the arguments to the ioctl handler (based on patch from #9198)
SVN-Revision: 27322
|
|
|
|
| |
SVN-Revision: 27299
|
|
|
|
| |
SVN-Revision: 27295
|
|
|
|
|
|
|
|
|
|
|
|
| |
bridge module has a dependency to IPv6 if IPv6 is enabled. Since the IPv6 module isn't exactly lightweight and bridge also only needs a single function from IPv6, it's rather easy to create a common "lib" module with a RCU pointer to the actual implementation, if the IPv6 module is loaded (although slightly hackish).
The codepath seems to be only taken when using IPv6, so there should be
no negative side effects when IPv6 isn't loaded. I did not measure how
big the performance impact is.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 27237
|
|
|
|
|
|
| |
patch from Peter Wagner
SVN-Revision: 27104
|
|
|
|
| |
SVN-Revision: 27074
|
|
|
|
| |
SVN-Revision: 27073
|
|
|
|
|
|
|
|
|
| |
* remove lqtapi
* bump tapi/dsl to .39
* migrate to new ltq_ style api
* add amazon_se support
SVN-Revision: 27026
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was originally tristate, but was changed to bool to prevent a build
breakage in an earlier patch revision (for a new syscall). The actual
commit[1] changed it in a way this isn't needed anymore, but
accidentially left the EXPORTFS change in. There's no reason for it
not being buildable as a module, so changing it back to tristate is
fine.
see: https://patchwork.kernel.org/patch/812832/
Thank you Jonas Gorski for the patch.
SVN-Revision: 27011
|
|
|
|
|
|
|
|
|
|
| |
* add md5sum for kernel
* add some missing config symbols
* add some ssb patches to make compat-wireless compile
Thank you Peter Wagner for the patch
SVN-Revision: 27009
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds 802.1Q VLAN support for the ADM6996M chip.
The driver is loaded for both the FC and M model. It will detect which of the
two chips is connected. The FC model is initialised, but no further
functionality is offered.
The PHY driver will always report "100 Mbit/s, link up", for both the M and FC
models. This reflects the fact that the link between switch chip and Ethernet
MAC is always on[1].
Further documentation can be found in the kernel's
Documentation/networking/adm6996.txt
Signed-of-By: Peter Lebbing <peter@digitalbrains.com>
SVN-Revision: 26865
|
|
|
|
| |
SVN-Revision: 26818
|
|
|
|
|
|
|
|
|
|
| |
Use offset from struct mtd_part instead of struct mtd_partition for defining
the new partitions. This enables the usage of MTDPART_OFS_APPEND macro in
struct mtd_partition.
Signed-off-by: Jochen Friedrich <jochen@scram.de>
SVN-Revision: 26705
|
|
|
|
| |
SVN-Revision: 26691
|
|
Add support for 2.6.39 based on rc3. Runtime tested on bcm63xx.
SVN-Revision: 26615
|