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
