- properly check for the link up condition in the phylib adjust callback
- do not assign skb->dev, eth_type_trans() already does it
- handle skb allocation failures in the refill path
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33780 3c298f89-4303-0410-b956-a3cf2f4a3e73
Commit r33248 introduced a regression by passing the board name plus
'board=' in the third argument. The board name string has to be put
into the image as identifier of the image type.
[juhosg: fix OpenMesh template instead of use of string substitution]
Signed-off-by: Marek Lindner <lindner_marek@yahoo.de>
Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33767 3c298f89-4303-0410-b956-a3cf2f4a3e73
Also share them between the GT701 and the PK5000.
Patch from Daniel Gimpelevich.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33756 3c298f89-4303-0410-b956-a3cf2f4a3e73
Handle the different vlynq device versions, and make the vlynq code more
in line with the original vlynq implementation.
Patch from Daniel Gimpelevich.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33755 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is required for Actiontec PK5000 devices. Path from Daniel Gimpelevich.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33753 3c298f89-4303-0410-b956-a3cf2f4a3e73
CFI detection will reduce the resource size to its real value.
Patch from Daniel Gimpelevich.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33752 3c298f89-4303-0410-b956-a3cf2f4a3e73
At least devices without a switch present on the MDIO bus still get a valid
link and work as expected (such as the Linksys WAG54Gv2).
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33751 3c298f89-4303-0410-b956-a3cf2f4a3e73
And fix the default network configuration to create the required VLANs.
Patch from Daniel Gimpelevich.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33750 3c298f89-4303-0410-b956-a3cf2f4a3e73
Add new device ID's for the hso driver as well as usb storage
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33743 3c298f89-4303-0410-b956-a3cf2f4a3e73
level monitoring and control of Gateworks boards. It is used on several
product families spanning several different target architectures (ixp4xx,
cns3xxx, davinci).
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33720 3c298f89-4303-0410-b956-a3cf2f4a3e73
Resolves crashes when probing multiple serial devices
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33719 3c298f89-4303-0410-b956-a3cf2f4a3e73
Bugfix from linux head - don't delay acks from ECN congestion
experienced in some situations.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33686 3c298f89-4303-0410-b956-a3cf2f4a3e73
The Laguna boards do not use all the same pins for SDHCI as the Cavium
reference board.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33684 3c298f89-4303-0410-b956-a3cf2f4a3e73
The ARM11MPCore Timer/Watchdog registers start at offset 0x600 which is where
all mpcore-wdt boards point the driver base too. I believe this is wrong
because 0x600 is aliased to the timer/watchdog of the 'current CPU' where
0x700 is CPU0's timer/watchdog, and 0x800 is CPU1's timer/watchdog. Thus
if your timer/watchdog application is switching between CPU's it can end up
writing to the wrong CPU's registers which results in random board resets
from watchdog timeouts etc.
This patch forces the timer/watchdog driver to use CPU0's registers always.
Its my opinion that other mpcore-wdt boards should be doing the same thing.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33683 3c298f89-4303-0410-b956-a3cf2f4a3e73
This allows sysupgrade for devices such as the Gateworks Avila/Cambria
product families based on the ixp4xx using the redboot bootloader with
combined FIS directory and RedBoot config partitions on larger FLASH
devices with larger eraseblocks.
This second iteration of this patch addresses previous issues:
- whitespace breakage fixed
- unlock in all scenarios
- simplification and fix logic bug
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33681 3c298f89-4303-0410-b956-a3cf2f4a3e73
Enabling OPTIMIZE_FOR_SIZE cuts the kernel binary down by 50K which is
critical for some small-footprint boards.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33679 3c298f89-4303-0410-b956-a3cf2f4a3e73
Since there is only one user of bcm_tag.h left, we can safely move it
into the firmware-utils directory, replacing the symlink.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33655 3c298f89-4303-0410-b956-a3cf2f4a3e73
gpio_keys_polled needs to be loaded in preinit for buttons to work for
entering failsafe.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33653 3c298f89-4303-0410-b956-a3cf2f4a3e73
Several new features for newer boards:
- add additional UARTs present on some boards
- add additional LEDs present on some boards
- add HSS audio device codec present on some boards
- add support for GSC present on some boards
- add per model setup support for newer boards
- set FLASH window per-model for boards with larger FLASH
Some fixes:
- add IRQ mapping for additional PCI devices (USB Host)
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33647 3c298f89-4303-0410-b956-a3cf2f4a3e73
roll all avila patches into a single patch (no code changes)
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33646 3c298f89-4303-0410-b956-a3cf2f4a3e73
Several new features for newer boards:
- add irq mapping for additional devices
- add platform data for i2c bus to SFP modules
- add additional UARTs present on some boards
- increased R/W delay for expansion bus UARTs
- add additional LEDs present on some boards
- add GPIO exports and configuration
- add ENET switch config present on some boards
- add support for GSC present on some boards
- added per model setup support for newer boards
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33644 3c298f89-4303-0410-b956-a3cf2f4a3e73
roll all cambria patches into a single patch (no code changes)
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33643 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is being done for general cleanup
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33642 3c298f89-4303-0410-b956-a3cf2f4a3e73
Before it was tried to initialize the deactivated PCIe core in client
mode, but this causes the SoC to hang. Just do not initialize it at all
and ignore the core it is not working and nothing is connected to it
when the specific bit is set in the boardflags.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33620 3c298f89-4303-0410-b956-a3cf2f4a3e73
The new version of the ALL0256N now got 8MB SPI NOR flash instead of 4MB.
In order to expose the whole amount of flash, add another image which contains
the corresponding GENERIC_8M mtdparts.
[juhosg: change suffix from '8m' to '8M']
Patch by: Daniel Golle <dgolle@allnet.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33614 3c298f89-4303-0410-b956-a3cf2f4a3e73
Sometimes the PCIe card indicates that it has a sprom somewhere and we
are able to read the memory region, but it is empty and not valid. In
these cases we should try to use the fallback sprom as a last chance.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33601 3c298f89-4303-0410-b956-a3cf2f4a3e73
The chip common and the PCIe code are accessing the sprom struct which
is not filled when these cores are initialized. Fix this by adding an
early initialize and fill the sprom struct before accessing it in other
code.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33600 3c298f89-4303-0410-b956-a3cf2f4a3e73
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.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33597 3c298f89-4303-0410-b956-a3cf2f4a3e73
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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33579 3c298f89-4303-0410-b956-a3cf2f4a3e73
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
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33574 3c298f89-4303-0410-b956-a3cf2f4a3e73
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>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33566 3c298f89-4303-0410-b956-a3cf2f4a3e73
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.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33544 3c298f89-4303-0410-b956-a3cf2f4a3e73
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.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33540 3c298f89-4303-0410-b956-a3cf2f4a3e73
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.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33496 3c298f89-4303-0410-b956-a3cf2f4a3e73
The package block-hotplug doesn't exist, removing reference to it.
Signed-off-by: Daniel Golle <dgolle@allnet.de>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33473 3c298f89-4303-0410-b956-a3cf2f4a3e73
It should be implemmented in a cleaner way.
This reverts the following commits:
[ar71xx] dir-825-b1: Fix wholeflash images
[ar71xx] dir825b1: Add image for DIR-825-B1 that uses the whole flash"
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33459 3c298f89-4303-0410-b956-a3cf2f4a3e73
This will make the kernel crash on systems using qemu < 1.1.0. Until fixed
disable VPFv4 capability probing.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33458 3c298f89-4303-0410-b956-a3cf2f4a3e73
This is a patch to connect eth0.1 (lan) to the only
ethernet connector available.
D-Link DAP-1350 goes bricked with AA 12.09-beta.
This is because the current esw configuration for the
board connects eth0.2 (wan) to the *ONE and ONLY*
ethernet connector available, preventing initial access
to the board through 192.168.1.1 on eth0.1 after flashing,
effectively bricking the board.
There are things that should be done to make this board
really useful, but for AA 12.09, this one liner is
indispensable.
Signed of by Yoichi Shinoda <shinoda@jaist.ac.jp>
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@33411 3c298f89-4303-0410-b956-a3cf2f4a3e73
