Since 2.6.38 the 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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27237 3c298f89-4303-0410-b956-a3cf2f4a3e73
Also make linux identify itself properly as 3.0, not 3.0.0.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27191 3c298f89-4303-0410-b956-a3cf2f4a3e73
If you turn on I2C, you'll need this symbol defined.
Signed-off-by: Philip A. Prindeville <philipp@redfish-solutions.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27182 3c298f89-4303-0410-b956-a3cf2f4a3e73
* backport 2.6.8 patches to .39 / .32.33
* remove lqtapi
* bump tapi/dsl to .39
* migrate to new ltq_ style api
* add amazon_se support
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27026 3c298f89-4303-0410-b956-a3cf2f4a3e73
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.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27011 3c298f89-4303-0410-b956-a3cf2f4a3e73
* Add missing config symbols
* Update package/kernel for 2.6.39
CONFIG_BT_L2CAP=y and CONFIG_BT_SCO=y are set to build them into the bluetooth module.
Thank you Jonas Gorski for the patch
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27010 3c298f89-4303-0410-b956-a3cf2f4a3e73
* 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
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27009 3c298f89-4303-0410-b956-a3cf2f4a3e73
Fixes for the following warnings:
drivers/mtd/devices/block2mtd.c: In function '_open_bdev':
drivers/mtd/devices/block2mtd.c:272:3: warning: ISO C90 forbids mixed declarations and code
drivers/mtd/devices/block2mtd.c: In function 'add_device':
drivers/mtd/devices/block2mtd.c:399:13: warning: assignment discards qualifiers from pointer target type
In the case of 442-block2mtd_probe.patch, it's not until the insertion of a executable statement before the definition that causes a warning, so I've chosen to resolve the issue here by splitting the definition and the initialization into a definition and a statement (and assignment) instead.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@27007 3c298f89-4303-0410-b956-a3cf2f4a3e73
Thank you Peter Wagner for the patch. I refreshed the kernel patches and added the md5sum of the kernel.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@26905 3c298f89-4303-0410-b956-a3cf2f4a3e73
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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@26865 3c298f89-4303-0410-b956-a3cf2f4a3e73
