summaryrefslogtreecommitdiff
path: root/target/linux/brcm47xx/image
Commit message (Collapse)AuthorAgeFilesLines
* broadcom-diag: support for the WNDR3700v3Hauke Mehrtens2013-04-281-0/+1
| | | | | | | | | | | | | | I recently picked up a WNDR3700 to put OpenWRT on, and only after tearing into the box did I find it was one of the v3 boards, with poor OpenWRT support. This patch should add the board detection and LED/button control to the broadcom-diag module, and should generate a netgear .chk image that the bootloader and stock firmware will accept. The changes to the broadcom-diag module are more than a few lines because the WNDR3700v3 is driving its LEDs through an HC164 8-bit shift register. Signed-off-by: Owen Kirby <osk@exegin.com> SVN-Revision: 36482
* brcm47xx: generate images for Linksys E.... modelsHauke Mehrtens2013-03-271-0/+9
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 36139
* brcm47xx: activate image generation for some Netgear devices which are on ↵Hauke Mehrtens2013-03-271-7/+7
| | | | | | the market and should be supported. SVN-Revision: 36137
* brcm47xx: generate images for more WRT...N modelsHauke Mehrtens2013-03-271-0/+5
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 36136
* brcm47xx: generate images for some more devicesHauke Mehrtens2013-03-201-3/+3
| | | | | | These devices should be supported by trunk now. SVN-Revision: 36099
* brcm47xx: board detection WNDR3400v2Hauke Mehrtens2013-02-251-0/+1
| | | | | | | | | | | | | | | | WNDR3400v2 is based on BCM53xx . Image that is created breaks the router somehow therefore "#". CFE and NVRAM contain different vars - example: CFE line original: Device eth0: hwaddr 74-44-01-37-C6-69, ipaddr 192.168.1.1, mask 255.255.255.0 CFE after openwrt: Device eth0: hwaddr 00-FF-FF-FF-FF-FF, ipaddr 192.168.1.1, mask 255.255.255.0 Logs were posted earlier on this mailing list: https://lists.openwrt.org/pipermail/openwrt-devel/2012-July/016174.html Different logs with factory firmware are in the wiki: http://wiki.openwrt.org/toh/netgear/wndr3400#wndr3400v2 (and on wikidevi for example) Signed off by: Dirk Neukirchen <dirkneukirchen@web.de> SVN-Revision: 35790
* brcm47xx: create image for Netgear WNDR3400 V1Hauke Mehrtens2013-01-261-1/+1
| | | | SVN-Revision: 35323
* brcm47xx: Additional BCM4716 supportHauke Mehrtens2012-12-131-0/+2
| | | | | | | | Additional BCM4716 support. Still needs working ethernet driver. Signed-off-by: Nathan Hintz <nlhintz@hotmail.com> SVN-Revision: 34672
* generate images for the D-Link DWL-3150 as wellImre Kaloz2012-10-271-2/+8
| | | | SVN-Revision: 33961
* generate image for Linksys e3200Hauke Mehrtens2012-08-051-0/+1
| | | | SVN-Revision: 33003
* brcm47xx: generate image for Linksys WRT610N V1Hauke Mehrtens2012-05-131-0/+1
| | | | SVN-Revision: 31696
* brcm47xx: add code to generate images for some netgear devicesHauke Mehrtens2012-02-181-2/+11
| | | | | | This is commented out until we get report of working devices. SVN-Revision: 30639
* brcm47xx: fix padding of trx images, padjffs2 does not work properly on ↵Felix Fietkau2011-08-291-1/+1
| | | | | | empty files by default SVN-Revision: 28125
* brcm47xx: deactivate wndr3400 for now as this device will not bootHauke Mehrtens2011-06-291-1/+1
| | | | SVN-Revision: 27316
* brcm47xx: generate image to flash on Netgear WNDR3400.Hauke Mehrtens2011-06-281-0/+1
| | | | | | The image will not boot because serial flash support is missing this is only for experts. SVN-Revision: 27302
* bcm47xx: Remove kernel checks from image MakefileHauke Mehrtens2011-06-151-6/+2
| | | | | | | | | 2.4 isn't present anymore, so it will always be 2.6 (or newer). Since the 2.6 check will break with 3.0, remove it alltogether. Signed-off-by: Jonas Gorski <jonas.gorski+openwrt@gmail.com> SVN-Revision: 27185
* brcm47xx: Add edimax PS1208mfg supportHauke Mehrtens2010-12-022-1/+13
| | | | | | Thank you clemvangelis for the patches. (closes #7672) SVN-Revision: 24217
* brcm47xx: do not generate image for wgr614_v8 as long as we did not get any ↵Hauke Mehrtens2010-08-061-1/+1
| | | | | | positive reports with that device. SVN-Revision: 22522
* brcm47xx: Add new image generation and fix leds/reset button on WNR834B V2Hauke Mehrtens2010-08-061-0/+6
| | | | | | | | | Thank you realopty for the patch. tools/firmware-utils/src/mkchkimg.c is from http://www.myopenrouter.com/download/10611/mkchkimg/ This closes #7702. SVN-Revision: 22516
* mostly revert commit r22396Hauke Mehrtens2010-07-301-1/+1
| | | | | | | | | | | | | CFE does not boot images generated with these checksums because of wrong checksum. After flashing then with tftp to my Asus wl500-GPv1 the following messages are show: Null Rescue Flag. Boot program checksum is invalid Hello!! Enter Rescue Mode: (Check error) SVN-Revision: 22418
* fix CRC32 calculation for sysupgradeMarkus Wigge2010-07-271-1/+1
| | | | | | | | | | | | | | * reduce image size for CRC calculation by fs_mark size sysupgrade sometimes failed for me and I noticed that it was due to incorrect CRC values in trx-header after performing it. It seems that the fs_mark was completely included in the calculation and that it was nevertheless modified by sysupgrade while appending the jffs data. This only occurs for the first boot after sysupgrade as the flashmap driver recalculates the CRC to an even smaller area when it boots. SVN-Revision: 22396
* renamed wrt54g3gv2-vf imagesMarkus Wigge2010-07-011-2/+2
| | | | | | | | | | 'factory' and 'sysupgrade' did not make much sense. A discussion with jow convinced me that .trx results in a helpdesk disaster. So I decided to use '.bin' for normal bin-headers and '.noheader.bin' for the trx-v2 image. I fixed the wiki accordingly. SVN-Revision: 22013
* add back the base-files/image code from brcm-2.4 to brcm47xxFelix Fietkau2010-06-2610-0/+1414
| | | | SVN-Revision: 21945
* remove brcm47xx symlinks to brcm-2.4 (unfortunately svn does not allow a ↵Felix Fietkau2010-06-261-1/+0
| | | | | | proper type changing commit) SVN-Revision: 21944
* strip the kernel version suffix from target directories, except for brcm-2.4 ↵Felix Fietkau2007-09-061-0/+1
(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
generated by cgit v1.1 at 2024-12-12 08:40:03 +0000