| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
SVN-Revision: 26681
|
|
|
|
| |
SVN-Revision: 25590
|
|
|
|
|
|
| |
96348GW-11 reference design but have different GPIOs therefore we use the board fixups now availabed (thanks the patches by Jonas Gorski) to create a separate board entry for these boards and leave the reference design with reference GPIOs. Also these boards only have enet1 (no enet0) so we set that in the board definition, and use a defconfig for a single interface network.
SVN-Revision: 24442
|
|
|
|
|
|
| |
the reference design 96348GW so we use fixup to allow us to define the correct ones, also the GW6000 has no GPIO-controlled leds.
SVN-Revision: 24305
|
|
|
|
|
|
| |
KanjiMonster for reminding me.
SVN-Revision: 24191
|
|
|
|
|
|
|
|
|
|
| |
Add support for the T-Com Speedport W 500V using a special tagged image as it
identifies itself as a 96348GW, but has some gpios wired differently, and also
has only one ethernet port without a switch attached to it.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 24190
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a fixup for the kernel to check the bcm tag of the image for a boardid in
the information1 field, and use that instead of the supplied one by cfe. This
is triggered by a + at the start of the information1 field.
Also modify the image generation to generate apropriately tagged images.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 24189
|
|
|
|
|
|
|
|
|
|
|
|
| |
The DSL-2740B/DSL-2741B rev C2 support was missing the board definition,
resulting in a kernel panic on boot.
This patch adds it, and also renames the generated image name to properly
reflect that it is for the revision C2, and for both the DSL-2740B and
DSL-2741B.
Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com>
SVN-Revision: 24188
|
|
|
|
|
|
| |
definition. The solves the strange whitespace in front of the image name in the info1 section
SVN-Revision: 24127
|
|
|
|
|
|
| |
eliminted the OpenWRT revision. This makes using the image (router) name as the board name possible, so that boards with same real boardid but different GPIOs can be detected and the correct GPIOs used.
SVN-Revision: 24118
|
|
|
|
|
|
| |
led/buttons not known).
SVN-Revision: 24040
|
|
|
|
|
|
| |
commandline parsing code using gengetopt - We now get long options - We have more options including use of the info section for board information (e.g. to add the same boardid but different GPIOs on different routers) * Added back the ability to write stock images (this is useful, for example, when copying the firmware from the in-memory flash, and then being able to create an image that will let you revert to/test stock firmware * Fixed copying of CRCs to use memcpy instead of strncpy (strncpy stops at 0) * Added ability to use all sections of the imagetag, including custom magic signatures (e.g. for the Telsey router I'm adding soon), info sections, and reserved sections * Added putting the router type (as defined in the image generating Makefile) into the info1 section and the filesystem type in the info2 section. This will be used by mtd (when I add the code) to return the name of image used to flash this router. (As requested by Jo, as well as being useful for same boardid different board scenario described above).
SVN-Revision: 24011
|
|
|
|
|
|
| |
contains board & subtarget infos (if appropriate) allowing subtargets to share the same bin directory without overwriting each other's files
SVN-Revision: 20834
|
|
|
|
|
|
| |
combining the elements so that it is no longer necessary to create an openwrt-only tagid and tagcrc, and elimate the tagid detection and switch statements which made dealing with imagetags overly complicated, especially since the logic would need analogs in all code that touched the imagetag. Patch from cshore.
SVN-Revision: 20652
|
|
|
|
| |
SVN-Revision: 19894
|
|
|
|
| |
SVN-Revision: 18204
|
|
|
|
| |
SVN-Revision: 17190
|
|
|
|
| |
SVN-Revision: 17058
|
|
|
|
| |
SVN-Revision: 16566
|
|
|
|
| |
SVN-Revision: 16506
|
|
|
|
| |
SVN-Revision: 16490
|
|
|
|
| |
SVN-Revision: 16400
|
|
|
|
|
|
|
|
| |
on the brcm63xx chipset.
Signed-Off By: Daniel Dickinson <crazycshore@gmail.com>
SVN-Revision: 16396
|
|
|
|
|
|
| |
with all known imagetag versions from Broadcom and vendors, patch from Daniel Dickinson (fixes #4987).
SVN-Revision: 16393
|
|
|
|
|
|
| |
thanks to Anselmo Luginbuhl and Daniel Dickinson (#4909, #4943)
SVN-Revision: 15253
|
|
|
|
| |
SVN-Revision: 15242
|
|
|
|
| |
SVN-Revision: 15133
|
|
|
|
| |
SVN-Revision: 14896
|
|
|
|
| |
SVN-Revision: 14850
|
|
|
|
| |
SVN-Revision: 14305
|
|
|
|
| |
SVN-Revision: 14264
|
|
|
|
| |
SVN-Revision: 13616
|
|
|
|
| |
SVN-Revision: 13588
|
|
|
|
| |
SVN-Revision: 13583
|
|
|
|
| |
SVN-Revision: 13540
|
|
|
|
| |
SVN-Revision: 13298
|
|
|
|
|
|
| |
working. Also it patches mtd map driver for bcm96xx boards to be sure that CFE1CFE1 code is detected when booting from CFE. (#4201)
SVN-Revision: 13213
|
|
|
|
|
|
| |
testing with 8MB devices
SVN-Revision: 13015
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds CFE tagged image generation in the BCM963xx target image Makefile.
It has to generate its own LZMA compressed kernel because CFE is a LZMA nazi.
It also seems that the Broadcom image tagger as well as CFE use AdvanceCOMP,
which is based on a slightly older LZMA SDK. Anyways, some of the code is
GPL, some of it is LGPL, so it might be that Broadcom owes some sources.
Also, LZMA has a bug which causes it to generate different output when you
are using stdin / stdout compared to plain files. I've just worked around
the issue by using plain files.
Signed-off-by: Axel Gembe <ago@bastart.eu.org>
SVN-Revision: 11171
|
|
|
|
|
|
|
|
|
|
| |
Current kernels have the same kernel entry as load address, so just set them
like this. Also, the BCM963xx uses 0x80010000 as its load address, so use this
too.
Signed-off-by: Axel Gembe <ago@bastart.eu.org>
SVN-Revision: 11169
|
|
|
|
|
|
| |
CONFIG_PCI & CONFIG_USB entries in generic/config and enabling them on targets where appropriate
SVN-Revision: 11097
|
|
|
|
| |
SVN-Revision: 10703
|
|
|
|
| |
SVN-Revision: 9533
|
|
(the -2.4 will be included in the board name here). CONFIG_LINUX_<ver>_<board> becomes CONFIG_TARGET_<board>, same for profiles.
SVN-Revision: 8653
|