summaryrefslogtreecommitdiff
path: root/target/linux/brcm47xx/base-files
Commit message (Collapse)AuthorAgeFilesLines
* brcm47xx: sysupgrade: drop useless shift in platform.shRafał Miłecki2015-06-061-1/+0
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45913
* brcm47xx: extract TRX from image on the flyJohn Crispin2015-06-051-7/+8
| | | | | | | | | | Extracting TRX to separated file in /tmp/ requires extra RAM which may not be available on some chepaer devices. Instead of that lets pass a proper extracting command to the default_do_upgrade. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45901
* brcm47xx: fix handling absolute paths in sysupgrade (for vendor formats)Rafał Miłecki2015-04-171-2/+2
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45472
* brcm47xx: rework vendor fw handling to don't duplicate upgrade callsRafał Miłecki2015-04-161-14/+10
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45470
* otrx: change command line API to start with a modeRafał Miłecki2015-04-141-3/+3
| | | | | | | | This will allow adding more modes without options conflict. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45443
* brcm47xx: verify also standard TRX images during sysupgradeRafał Miłecki2015-04-091-0/+4
| | | | | | | | It allows detecting data corruption for plain TRX as well. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45318
* brcm47xx: fix WRT300N devices magics for sysupgrade checkRafał Miłecki2015-04-091-1/+2
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45317
* brcm47xx: switch to the otrx for verifying TRX imagesRafał Miłecki2015-04-091-16/+2
| | | | | | | | This adds checking CRC32 of provided firmware image. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45316
* brcm47xx: image: share function checking TRX in provided firmwareRafał Miłecki2015-03-311-6/+18
| | | | | | | | This will allow us to calculate crc32 in a shared code. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45202
* brcm47xx: fix checking cross-vendors firmware imagesRafał Miłecki2015-03-311-48/+41
| | | | | | | | | This change won't allow installing e.g. Netgear firmware on Linksys device. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45174
* brcm47xx: display all errors (not just the 1st one) when checking imageRafał Miłecki2015-03-311-10/+8
| | | | | | | | This way people forcing upgrade will know what may go wrong. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45172
* brcm47xx: recognize more device specific firmwaresRafał Miłecki2015-03-311-0/+34
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45171
* brcm47xx: compare provided firmware magic with device magicRafał Miłecki2015-03-301-2/+34
| | | | | | | | | This makes sysupgrade reject firmware images for different devices. Right now only support for 2 sample devices is implemented. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 45170
* brcm47xx: support for flashing CHK and CyberTAN imagesRafał Miłecki2014-12-301-5/+28
| | | | | | | | | This will allow simple sysupgrade-s including simpler reverting to the original firmware. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 43799
* brcm47xx: verify if CHK/CyberTAN contains valid TRXRafał Miłecki2014-12-301-1/+16
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 43798
* brcm47xx: extract magics from specific upgrade images (and still reject them)Rafał Miłecki2014-12-151-1/+17
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 43718
* add "preinit_regular" diag.sh set_state argumentJohn Crispin2014-12-151-0/+3
| | | | | | | | | | | | This new argument is used right after starting regular preinit (which happens if failsafe wasn't triggered). The main purpose of "preinit" argument is to indicate that failsafe can be triggered, however we were missing a way to inform user that we don't wait for a trigger anymore. With this change it's clear when failsafe mode can be triggered. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 43715
* brcm47xx: detect (and still reject for now) CyberTAN fw formatRafał Miłecki2014-12-151-0/+12
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 43714
* brcm47xx: use separated function in upgrade to detect file typeRafał Miłecki2014-12-151-3/+22
| | | | | | Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 43708
* scripts: fix wrong usage of '==' operatorJohn Crispin2014-10-141-1/+1
| | | | | | | | | | | | | | [base-files] shell-scripting: fix wrong usage of '==' operator normally the '==' is used for invoking a regex parser and is a bashism. all of the fixes just want to compare a string. the used busybox-ash will silently "ignore" this mistake, but make it portable/clean at least. this patch does not change the behavior/logic of the scripts. Signed-off-by: Bastian Bittorf <bittorf@bluebottle.com> SVN-Revision: 42911
* brcm47xx: don't create named switch_vlan sectionsHauke Mehrtens2014-07-261-2/+0
| | | | | | | | | | | It doesn't seem to be used anywhere, it's incompatible with other targets and can be confusing. People may think they need to update section name every time they change VLAN ID (well, even I was doing that). Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 41835
* brcm47xx: fix special board handling for some devicesHauke Mehrtens2014-07-141-19/+7
| | | | | | | | | | | Some devices were renamed when converted from diag to in kernel board detection and it was not changed in netconfig. Devices not in the kernel board detection are removed now. This should close: #17111, #16968, #13202 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 41663
* brcm47xx: get switch name from swconfig firstHauke Mehrtens2014-07-051-3/+5
| | | | | | | | | Without this patch the switch config for the adm switch did not worked, because hey are not names eth0. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 41512
* brcm47xx: migrate basic network settings from old releasesHauke Mehrtens2014-07-031-0/+29
| | | | | | | | | | | | | | | | Old OpenWrt releases were using network configs that are not valid anymore. They were specifying ports tagging in a different way (or were not tagging CPU at all) and were using VID 0 which is a reserved value. Modifying network configuration to apply all needed changes would be pretty tricky. Script /etc/init.d/netconfig that generates new config is quite complex itself. So instead let's save the most important settings, regenerate config from the scratch and restore values. This should work for 99% of users. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 41500
* bcm47xx: use eth0 for switch nameHauke Mehrtens2014-06-071-3/+3
| | | | | | | | | | | This fixes some strange problems with tg3. I assume that the Ethernet driver was not brought up if the switch was named switch0. This was reported and tested by ernesto (Faulp3lz). Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 41042
* target/linux/*/base-files/lib/upgrade/platform.sh - wrong check for ARGCJohn Crispin2014-06-021-1/+1
| | | | | | | | | | | | | | | | | | | ARGC is a 'C-ism', but not known/valid in shell-syntax - insert the correct var $# (=number of args) here. under normal conditions this had no impact, but we should at least correct it. the error was observable like this: root@box:~ [ -e "/etc/functions.sh" ] && . /etc/functions.sh root@box:~ [ -e "/lib/functions.sh" ] && . /lib/functions.sh root@box:~ . /lib/upgrade/platform.sh root@box:~ . /lib/upgrade/common.sh root@box:~ platform_check_image /tmp/myfirmware.bin ash: bad number root@box:~ echo $? 0 Signed-off-by: Bastian Bittorf <bittorf@bluebottle.com> SVN-Revision: 40915
* brcm47xx: parse model from cpuinfoHauke Mehrtens2014-01-121-3/+2
| | | | | | | | | Instead of looking into the proc entry provided by broadcom-diag use the board info from /proc/cpuinfo to get the board we are on. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 39256
* brcm47xx: fix led indicationHauke Mehrtens2014-01-121-16/+26
| | | | | | | | | Use the new led api also on brcm47xx. The led for failsafe indication is searched for. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 39255
* brcm47xx: fix network failsafe indicationHauke Mehrtens2014-01-123-75/+18
| | | | | | | | | | Remove the code used on the old switch driver. The Ethernet drive is loaded as a module and needs some time to get up therefor we added some wait function. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 39254
* brcm47xx: use "firmware" partition nameHauke Mehrtens2013-12-012-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Some time ago, after switching to the mainline bcm47xxpart driver following patch has been applied: commit 03cef8725d2062335ffc3de50fc037b294fd458c Author: hauke <hauke@3c298f89-4303-0410-b956-a3cf2f4a3e73> Date: Sat Apr 6 22:22:26 2013 +0000 brcm47xx: use old partition names again for kernel 3.8 This fixes sysupgrade. The partition names are used all over the Internet in various howtos. Thank you russell for spotting this problem. I propose to revert this change and make sysupgrade use "firmware" instead. This makes brcm47xx compatible with widely used ar71xx and after all "firmware" sounds like a much better name for... the firmware. This change doesn't affect "sysupgrade" usage, because it never takes a partition name as a parameter. This change only affects users using mtd tool directly. Hopefully there are not many howtos using "mtd" command. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 38973
* brcm47xx: fix netconfig for inverted vlan?ports in nvramHauke Mehrtens2013-11-111-2/+4
| | | | | | This was observed on the Belkin Share F7D7302. SVN-Revision: 38769
* brcm47xx: add support for ipv6 in default network configHauke Mehrtens2013-10-021-58/+40
| | | | | | | | | Modify /etc/init.d/netconfig to use UCI defaults for building the default network config, which includes appropriate defaults for IPV6. Signed-off-by: Nathan Hintz <nlhintz@hotmail.com> SVN-Revision: 38294
* brcm47xx: run mtd fixtrx linux every timeHauke Mehrtens2013-07-311-8/+1
| | | | | | | | With this patch it is possible to boot a device with kernel 3.10 a second time. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 37625
* brcm47xx: use b53 phy driver for the switch in kernel 3.10Hauke Mehrtens2013-07-141-4/+4
| | | | | | | | | | This makes it possible to use swconfig to controll the switch. This was tested with devices using b43 and bgmac. This was not tested on devices using tg3. This does not support the adm switch used in some very old devices. SVN-Revision: 37304
* brcm47xx: fix switch handlingHauke Mehrtens2013-07-144-34/+35
| | | | | | | | | | | | | | | | This fixes some problems with the switch handling * It now send the messages again to indicate a button for failsafe mode should be pressed * it does not leak packages between wan and lan any more * the switch works again in normal mode The Ethernet connection has to be up when the switch driver switch-robo is insmoded therefor we just do it again. Explicitly set enable_vlan to prevent leaking packages. This should close #13869, #13868 and #13716 SVN-Revision: 37286
* brcm47xx: do not load the kernel modules needed for Ethernet manuallyHauke Mehrtens2013-07-142-15/+0
| | | | | | | add the boot flag to make the kernel modules needed for Ethernet and diag load on startup. SVN-Revision: 37284
* brcm47xx: do not change nvram without user interactionHauke Mehrtens2013-07-141-14/+0
| | | | SVN-Revision: 37281
* brcm47xx: proc gets mounted without this patchHauke Mehrtens2013-07-131-5/+0
| | | | SVN-Revision: 37272
* brcm47xx: remove obsolete hotplug stuffHauke Mehrtens2013-07-132-11/+0
| | | | SVN-Revision: 37271
* brcm47xx: dont manually insmod switch driversJohn Crispin2013-06-211-4/+0
| | | | | | Signed-off-by: John Crispin <bloic@openwrt.org> SVN-Revision: 36993
* brcm47xx: use old partition names again for kernel 3.8Hauke Mehrtens2013-04-061-1/+1
| | | | | | | | This fixes sysupgrade. The partition names are used all over the Internet in various howtos. Thank you russell for spotting this problem. SVN-Revision: 36235
* brcm47xx: netconfig: add bacis support for swconfigHauke Mehrtens2013-03-091-25/+27
| | | | | | Parse the cpu port from swconfig and explicitly mark the cpu port as tagged. SVN-Revision: 35911
* brcm47xx: do not use vlan0 any more.Hauke Mehrtens2013-02-203-43/+43
| | | | | | | | The Broadcom switch driver says that vlan0 should not be used with any switch other than bcm5325. This makes OpenWrt always use vlan1 and vlan2 instead. SVN-Revision: 35704
* brcm47xx: add initial support for kernel 3.8Hauke Mehrtens2013-02-161-0/+14
| | | | | | | | | | | | This contains the following new bigger changes: * new partition parser which still could lake some features or have bugs * new nand flash driver * using physmap-flash flash driver for parallel flash * some changes to the serial flash driver With these changes OpenWrt starts using more of the mainline flash drivers. SVN-Revision: 35632
* brcm47xx: improve cpuport detection for filesafeHauke Mehrtens2013-02-161-13/+9
| | | | | | | Do not try to load bcm57xx.ko any more this is not needed for kernel 2.6 and 3.X Ask the switch driver where the CPU port is. SVN-Revision: 35624
* brcm47xx: fix network config on simpleshareHauke Mehrtens2013-02-161-0/+6
| | | | | | | | | | The included patch will generate a correct network configuration on the simpletech simpleshare. Thank you for the patch Will Holmes (RealOpty) This closes #12361. SVN-Revision: 35623
* brcm47xx: try to automatically detect if the wan port is at port 4 and not ↵Hauke Mehrtens2013-02-161-1/+12
| | | | | | | | at port 0. This should fix #13000. SVN-Revision: 35617
* brcm47xx: if the cpuport of the switch is port 8 assume vlan0ports: "1 2 3 4 ↵Hauke Mehrtens2013-02-141-16/+8
| | | | | | 8" and vlan0ports: "0 8" SVN-Revision: 35597
* brcm47xx: configure vlan correctly on some recent devices.Hauke Mehrtens2013-02-131-1/+4
| | | | SVN-Revision: 35587
* Add Failsafe support for Linksys E3000V1 / WRT610NV2Hauke Mehrtens2013-02-041-0/+1
| | | | | | | | | | | | | Adds specification of the correct cpu_port for Linksys E3000V1 and WRT610NV2 in /lib/preinit/05_init_interfaces_brcm. The list of devices will need to be expanded. Is there a way to determine the correct cpu_port to use in a generic sense; for instance, if "/proc/switch/eth0/port/8" exists, or if "/sys/class/net/eth0/device/driver/module/drivers/bcma:bgmac" exists? Could a similar method be used in "/etc/init.d/netconfig"? Signed-off-by: Nathan Hintz <nlhintz@hotmail.com> SVN-Revision: 35491
generated by cgit v1.1 at 2024-11-28 20:45:52 +0000