NETGEAR doesnt produce a distinct North American image for
WNDR3700v2, they use the same image worldwide. This is a change from
earlier models such as WNDR3700 (v1). NETGEAR's v2 images now contain
an "hd_id" parameter, as well. All observed WNDR3700v2, WNDR3800, and
WNDRMAC images use 29763654+16+64 as their hd_id value.
This patch changes the OpenWrt WNDR3700v2 "factory" image generation
to stop producing the extraneous -NA version and to tag the image with
the same hd_id used in NETGEAR's images.
There is no change to WNDR3700 (v1) image generation, as NETGEAR
continues to produce distinct -NA and worldwide images, neither of
which are tagged with hd_id.
Signed-off-by: Mark Mentovai <mark@moxienet.com>
SVN-Revision: 27053
Newer WRT160NLs have a flash chip with 4K erase blocks instead of 64K,
resulting in miscalculated partition sizes.
Since the actual sizes did not change, hardcode them to their current
sizes, and make sure they are at least one erase block big (in case Cisco
decides to start to use chips with 128K erase blocks).
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 27049
Add the MFGPT high precision timers, and integration into the schedule (clock events).
Use OHCI, not UHCI usb module.
Remove VIA SATA driver from Alix2... that was accidentally cloned from net5501 platform.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27038
The pata-cs5535/pata-cs5536 driver is actually fairly rare: it only gets used on embedded platforms. Therefore, we remove it from the generic x86 configuration.
Also, add definitions for other useful geode modules (high-res timers, MFGPT timers, etc).
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 27037
Add support for Kernel 2.6.38, based on 2.6.38.6. Boots fine on a BCM6358.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 27018
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 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
SVN-Revision: 27010
* 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
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>
SVN-Revision: 27007
The flash driver code should be cleaned up and the broad detection code should be placed into arch code and used here.
This fixes#9323
Thank you Will Holmes for the patch.
SVN-Revision: 27005
Note that the Alix6 uses GPIO 27 to disable wireless transmit (W_DIS#), whereas on all other versions this is used to actuate the speaker.
GPIO 1 : SIM select (Alix6)
GPIO 6 : LED1
GPIO 25 : LED2
GPIO 27 : LED3 or RFKILL (Alix6)
GPIO 24 : Soft switch 1
No kernel version bump. Added i2c-scx200-acb for lm-sensors support.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26880
Note that the Alix6 uses GPIO 27 to disable wireless transmit (W_DIS#), whereas on all other versions this is used to actuate the speaker.
GPIO 1 : SIM select (Alix6)
GPIO 6 : LED1
GPIO 25 : LED2
GPIO 27 : LED3 or RFKILL (Alix6)
GPIO 24 : Soft switch 1
No kernel version bump. Added i2c-scx200-acb for lm-sensors support.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
SVN-Revision: 26879
Add the required board definition, default config and image generation for
the T-Home Speedport W 303V Typ B.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26878
Rename the DSL-274xB rev C2's board ID to "AW4139" to match the one used
for the rev C3 (same hardware) and add a fixup for C2. Also generate
images for C3.
While we are at it, rename the LEDs to conform to the Linux LED naming
conventions.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26876
Make the fixup board ID independent from the image name to allow using
the same board ID for similar devices.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 26874
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
The function __devinit ag71xx_probe() references
a function __devexit ag71xx_phy_disconnect().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __devexit annotation of
ag71xx_phy_disconnect() so it may be used outside an exit section.
The function ag71xx_phy_disconnect() references a function in an exit
section.
Often the function ag71xx_ar7240_cleanup() has valid usage outside the
exit section
and the fix is to remove the __devexit annotation of
ag71xx_ar7240_cleanup.
SVN-Revision: 26855
