| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
confusing
SVN-Revision: 26961
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
broadcom-wl driver bound to ssb device with ssb driver probe
have osh handle struct pdev pointer value initialized with
ssb_device pointer. Later on pdev is used with legacy pci
dma api as pci_dev thus causing oops sometimes.
The patch replaces legacy pci dma api and pass relevant
device struct pointer to avoid crashes.
Signed-off-by: George Kashperko <george@znau.edu.ua>
SVN-Revision: 26949
|
|
|
|
|
|
|
|
| |
It was causing an occasional kernel oops.
Signed-off-by: Nathan Hintz <nlhintz@hotmail.com>
SVN-Revision: 26948
|
|
|
|
| |
SVN-Revision: 26947
|
|
|
|
| |
SVN-Revision: 26934
|
|
|
|
| |
SVN-Revision: 26933
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the attached patch makes ipcalc.sh accept IP/Netmask combinations in
CIDR notation. Before you could only do:
# sh ipcalc.sh 192.168.0.0 255.255.255.0 1 10
IP=192.168.0.0
NETMASK=255.255.255.0
BROADCAST=192.168.0.255
NETWORK=192.168.0.0
PREFIX=24
START=192.168.0.1
END=192.168.0.11
with this patch you can also execute it with:
sh ipcalc.sh 192.168.0.0/24 1 10
IP=192.168.0.0
NETMASK=255.255.255.0
BROADCAST=192.168.0.255
NETWORK=192.168.0.0
PREFIX=24
START=192.168.0.1
END=192.168.0.11
The patch is based on #1260 [1], i just changed one line to calculate
the START end END ips right. I wonder why that never got included. If
there is no reason not to do i would like to ask you to commit that
patch, because its a functionality i (and probably others) miss quite often.
Btw, i also fixed 4 useless tabs, that might look a bit strange in the
patch.
Regards, Manuel
SVN-Revision: 26930
|
|
|
|
|
|
| |
override (thx, KanjiMonster)
SVN-Revision: 26927
|
|
|
|
|
|
| |
requests in ad-hoc mode without creating too much spam
SVN-Revision: 26923
|
|
|
|
|
|
| |
Signed-off-by: Jan Willies <jan@willies.info>
SVN-Revision: 26920
|
|
|
|
|
|
| |
some instances
SVN-Revision: 26915
|
|
|
|
| |
SVN-Revision: 26913
|
|
|
|
| |
SVN-Revision: 26912
|
|
|
|
|
|
|
|
|
| |
Since the oldest kernel in trunk is 2.6.30 the modules always use the
newer names, so we can just use the _generic prefix directly.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26903
|
|
|
|
|
|
|
|
|
| |
There's only 2.6, so it doesn't make sense to mention modules that are
2.4 only or for modules that they are available only for 2.6.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26902
|
|
|
|
|
|
|
|
|
| |
With no 2.4 support in trunk, we can safely remove any 2.4 definitions for
kmods and merge the 2.6 definitions into the generic ones.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26901
|
|
|
|
|
|
|
|
|
| |
Since there's only 2.6 in trunk $(KMOD_SUFFIX) can be safely replaced with
ko for all mainline kernel modules.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26900
|
|
|
|
|
|
|
|
| |
stuff into its own file makes sense.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26868
|
|
|
|
|
|
| |
space, so a default route of ::/0 is more correct. Thanks Dave Taht
SVN-Revision: 26857
|
|
|
|
|
|
| |
usb_modeswitch on boot and possibly others (#9352)
SVN-Revision: 26848
|
|
|
|
| |
SVN-Revision: 26841
|
|
|
|
| |
SVN-Revision: 26822
|
|
|
|
| |
SVN-Revision: 26819
|
|
|
|
| |
SVN-Revision: 26816
|
|
|
|
| |
SVN-Revision: 26815
|
|
|
|
|
|
|
|
| |
unprovided kernel crypto modules that are useful for IPSEC. This is an alternative to breaking these modules out into kmod-crypto-wq (crypto_wq.ko), kmod-crypto-rng (rng.ko and krng.ko), and kmod-crypto-iv (eseqiv.ko and chainiv.ko).
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26814
|
|
|
|
|
|
|
|
| |
kmod-ipsec. Also remove the extraneous kmod-crypto-core dependency to eliminate recursion.
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26813
|
|
|
|
|
|
|
|
|
|
|
|
| |
kmod-crypto-rng, and kmod-crypto-iv packages. These packages provide some missing kernel crypto modules which are required for IPSEC. The strongswan4, ipsec-tools, and possibly other IPSEC packages do not work properly without these modules.
NOTE: The KCONFIG associated with each of these modules gets selected
whenever CRYPTO_MANAGER (kmod-crypto-manager) is selected so these
modules are already being built.
Signed-off-by: Lars Hjersted <lars@hjersted.com>
SVN-Revision: 26812
|
|
|
|
|
|
| |
deadlocks
SVN-Revision: 26810
|
|
|
|
| |
SVN-Revision: 26809
|
|
|
|
| |
SVN-Revision: 26808
|
|
|
|
| |
SVN-Revision: 26807
|
|
|
|
| |
SVN-Revision: 26806
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
passthrough Two examples of potentially useful configurations (commented out, of course):
(a) map the ssh service running on the firewall to 22001 externally, without modifying the configuration of the daemon itself. this allows port 22 on the WAN side to then be port-forwarded to a
LAN-based machine if desired, or if not, simply obscures the port from external attack.
(b) allow IPsec/ESP and ISAKMP (UDP-based key exchange) to happen by default. useful for most modern VPN clients you might have on your WAN.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26805
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If there is no sprom on an ssb based pci device on the brcm47xx
architecture ssb now asks the architecture code to look into the nvram
to get some sprom data for this device. Now we are able to read out
pci/1/1/ foo or pci/1/3/ foo config options.
This will fix some problems where the wireless devices does not got an
mac address and the following message was show:
ssb: WARNING: Invalid SPROM CRC (corrupt SPROM)
SVN-Revision: 26801
|
|
|
|
| |
SVN-Revision: 26798
|
|
|
|
|
|
| |
to fix connection hangs on some devices
SVN-Revision: 26795
|
|
|
|
| |
SVN-Revision: 26781
|
|
|
|
| |
SVN-Revision: 26773
|
|
|
|
|
|
|
|
|
| |
Fix compilation for 2.6.39 by replacing SPIN_LOCK_UNLOCKED with
DEFINE_SPINLOCK().
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26771
|
|
|
|
|
|
| |
earlier
SVN-Revision: 26768
|
|
|
|
|
|
| |
configured (#9308)
SVN-Revision: 26765
|
|
|
|
|
|
| |
#9299)
SVN-Revision: 26764
|
|
|
|
|
|
| |
pending patches
SVN-Revision: 26761
|
|
|
|
|
|
| |
seems to be just as inaccurate as the original version of the code
SVN-Revision: 26753
|
|
|
|
| |
SVN-Revision: 26752
|
|
|
|
| |
SVN-Revision: 26751
|
|
|
|
|
|
| |
interface
SVN-Revision: 26750
|
|
|
|
| |
SVN-Revision: 26749
|
|
|
|
|
|
| |
This was fixed upstream
SVN-Revision: 26745
|