aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* ath79: remove lines-initial-states propertyDavid Bauer2019-07-252-2/+0
| | | | | | | | | The lines-initial-states property was an early attempt to set the latch bit of the shift register on driver probe. It is not implemented in the driver and was rejected upstream. The latch bit was always set by a GPIO hog, so this property is safe to drop. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: drop an empty case in 02_networkChuanhong Guo2019-07-251-4/+0
| | | | | | | There's an empty case in 02_network introduced by last commit. Drop it. Fixes: ee650ba46c ("ramips: remove needless setting of lan_mac to eth0 in 02_network") Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: remove needless setting of lan_mac to eth0 in 02_networkAdrian Schmutzler2019-07-251-10/+4
| | | | | | | | | | | This removes superfluous lines like lan_mac=$(cat /sys/class/net/eth0/address) Since lan_mac only sets the MAC address for eth0.1, these lines can be safely removed as the address will be inherited from eth0 anyway. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: consistently use lower-case factory partition labelAdrian Schmutzler2019-07-259-26/+24
| | | | | | | | The vast majority of devices labels "factory" partition with lower case. Convert the small fraction with capital letter to that and merge another case in 02_network. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: consolidate MAC address cases in 02_networkAdrian Schmutzler2019-07-251-32/+15
| | | | | | | | This just merges some duplicate definitions and consolidates lines. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Chuanhong Guo <gch981213@gmail.com> [merge duplicated cases for phicomm k2p]
* ramips: use kiB instead of B for IMAGE_SIZEAdrian Schmutzler2019-07-254-4/+4
| | | | | | | This cosmetical patch is just meant to make comparing/checking IMAGE_SIZE values easier. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove ralink_default_fw_size_xxx variablesAdrian Schmutzler2019-07-257-187/+182
| | | | | | | | | | | There are frequent examples of the ralink_default_fw_size_xxx variables being used to "roughly" set flash size without caring about the actual size of the firmware partition. To discourage this behavior, this patch removes the variables and just sets IMAGE_SIZE by its numeric value for each target. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove default IMAGE_SIZE for ramips targetAdrian Schmutzler2019-07-256-1/+66
| | | | | | | | | | | | | | | | | | | Currently, ramips target defines 0x7b0000 as default IMAGE_SIZE for all devices in ramips target, i.e. this will be set if a device does not specify IMAGE_SIZE itself. From 92 devices using that default due to a "missing" IMAGE_SIZE, 14 were incorrect by a small amount (i.e. still "8M" flash) and 12 were completely off ("16M", "4M", ...). This patch thus removes the _default_ IMAGE_SIZE and defines IMAGE_SIZE for each device individually. This should indicate to people supporting new devices that this parameter has to be cared about. For the present code, this patch is cosmetical. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/rt305x: fix IMAGE_SIZE for all devicesAdrian Schmutzler2019-07-251-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes IMAGE_SIZE for all devices based on the partition size given in DTS: DEVICE *.MK *.DTS VERDICT 7links_px-4885-4m (4M) 0x3b0000 7links_px-4885-8m - 0x7b0000 default 8devices_carambola - 0x7b0000 default accton_wr6202 - 0x7b0000 default airlive_air3gii (4M) 0x3b0000 alfa-network_w502u - 0x7b0000 default allnet_all0256n-4m (4M) 0x3b0000 allnet_all0256n-8m - 0x7b0000 default allnet_all5002 32448k 0x1fb0000 allnet_all5003 32448k 0x1fb0000 alphanetworks_asl26555-16m 15872k 0xf80000 alphanetworks_asl26555-8m 7744k 0x790000 arcwireless_freestation5 - 0x7b0000 default argus_atp-52b 7808k 0x7a0000 asiarf_awapn2403 (4M) 0x3b0000 asiarf_awm002-evb-4m (4M) 0x3b0000 asiarf_awm002-evb-8m - 0x7b0000 default asus_rt-g32-b1 (4M) 0x3b0000 asus_rt-n10-plus (4M) 0x3b0000 asus_rt-n13u - 0x7b0000 default asus_wl-330n (4M) 0x3b0000 asus_wl-330n3g (4M) 0x3b0000 aximcom_mr-102n - 0x790000 wrong aztech_hw550-3g - 0x7b0000 default belkin_f5d8235-v2 7744k 0x790000 belkin_f7c027 7616k 0x770000 buffalo_whr-g300n 3801088 0x3a0000 dlink_dap-1350 7488k 0x750000 dlink_dcs-930 (4M) 0x3b0000 dlink_dcs-930l-b1 (4M) 0x3b0000 dlink_dir-300-b1 (4M) 0x3b0000 dlink_dir-300-b7 (4M) 0x7b0000 wrong dlink_dir-320-b1 - 0x7b0000 default dlink_dir-600-b1 (4M) 0x3b0000 dlink_dir-610-a1 (4M) 0x3b0000 dlink_dir-615-d (4M) 0x3b0000 dlink_dir-615-h1 (4M) 0x3b0000 dlink_dir-620-a1 - 0x7b0000 default dlink_dir-620-d1 - 0x7b0000 default dlink_dwr-512-b 7800k 0x7e0000 wrong easyacc_wizard-8800 - 0x7b0000 default edimax_3g-6200n 3648k 0x390000 edimax_3g-6200nl 3648k 0x390000 engenius_esr-9753 (4M) 0x3b0000 fon_fonera-20n - 0x7b0000 default hame_mpr-a1 (4M) 0x3b0000 hame_mpr-a2 - 0x7b0000 default hauppauge_broadway 7744k 0x790000 hilink_hlk-rm04 - 0x3b0000 wrong hootoo_ht-tm02 - 0x7b0000 default huawei_d105 (4M) 0x3b0000 huawei_hg255d 15744k 0xf60000 intenso_memory2move - 0x7b0000 default jcg_jhr-n805r (4M) 0x3b0000 jcg_jhr-n825r (4M) 0x3b0000 jcg_jhr-n926r (4M) 0x3b0000 mofinetwork_mofi3500-3gn - 0x7b0000 default netcore_nw718 3712k 0x3a0000 netgear_wnce2001 (4M) 0x350000 wrong nexaira_bc2 - 0x7b0000 default nexx_wt1520-4m (4M) 0x3b0000 nexx_wt1520-8m - 0x7b0000 default nixcore_x1-16m 16064k 0xfb0000 nixcore_x1-8m 7872k 0x7b0000 olimex_rt5350f-olinuxino - 0x7b0000 default olimex_rt5350f-olinuxino-evb - 0x7b0000 default omnima_miniembplug - 0x7b0000 default omnima_miniembwifi - 0x7b0000 default petatel_psr-680w (4M) 0x3b0000 planex_mzk-dp150n (4M) 0x3b0000 planex_mzk-w300nh2 3648k 0x390000 planex_mzk-wdpr - 0x680000 wrong poray_ip2202 - 0x7b0000 default poray_m3 (4M) 0x3b0000 poray_m4-4m (4M) 0x3b0000 poray_m4-8m - 0x7b0000 default poray_x5 - 0x7b0000 default poray_x8 - 0x7b0000 default prolink_pwh2004 - 0x7b0000 default ralink_v22rw-2x2 (4M) 0x3b0000 sitecom_wl-351 (4M) 0x3b0000 skyline_sl-r7205 (4M) 0x3b0000 sparklan_wcr-150gn (4M) 0x3b0000 teltonika_rut5xx - 0xfb0000 wrong tenda_3g150b (4M) 0x3b0000 tenda_3g300m (4M) 0x3b0000 tenda_w150m (4M) 0x3b0000 tenda_w306r-v2 (4M) 0x3b0000 trendnet_tew-638apb-v2 (4M) 0x3b0000 trendnet_tew-714tru - 0x7b0000 default unbranded_a5-v11 (4M) 0x3b0000 unbranded_wr512-3gn-4m (4M) 0x3b0000 unbranded_wr512-3gn-8m - 0x7b0000 default unbranded_xdx-rn502j (4M) 0x3b0000 upvel_ur-326n4g (4M) 0x3b0000 upvel_ur-336un - 0x7b0000 default vocore_vocore-16m 16064k 0xfb0000 vocore_vocore-8m 7872k 0x7b0000 wansview_ncs601w - 0x7b0000 default wiznet_wizfi630a (16M) 0xfb0000 zorlik_zl5900v2 - 0x7b0000 default zyxel_keenetic (4M) 0x3b0000 zyxel_keenetic-start (4M) 0x3b0000 zyxel_nbg-419n (4M) 0x3b0000 zyxel_nbg-419n-v2 (8M) 0x7b0000 No verdict means that the device is correctly set. Legend: ( ): Value is set via ralink_default_fw_size_xxM [ ]: Value is derived from parent definition - : Value is not set and derived from default definition Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/rt288x,rt3883: fix IMAGE_SIZE for all devicesAdrian Schmutzler2019-07-252-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes IMAGE_SIZE for all devices based on the partition size given in DTS: DEVICE *.MK *.DTS VERDICT airlink101_ar670w (4M) 0x3c0000 wrong airlink101_ar725w - 0x3B0000 wrong asus_rt-n15 (4M) 0x3b0000 belkin_f5d8235-v1 7744k 0x7b0000 wrong buffalo_wli-tx4-ag300n (4M) 0x3b0000 buffalo_wzr-agl300nh (4M) 0x3b0000 dlink_dap-1522-a1 3801088 0x3a0000 ralink_v11st-fe (4M) 0x003b0000 asus_rt-n56u - 0x007b0000 default belkin_f9k1109v1 7224k 0x7a0000 wrong dlink_dir-645 - 0x7b0000 default edimax_br-6475nd 7744k 0x00790000 loewe_wmdr-143n - 0x7b0000 default omnima_hpm 16064k 0x00fb0000 samsung_cy-swr1100 - 0x7b0000 default sitecom_wlr-6000 7244k 0x713000 trendnet_tew-691gr - 0x007b0000 default trendnet_tew-692gr - 0x007b0000 default No verdict means that the device is correctly set. Legend: ( ): Value is set via ralink_default_fw_size_xxM [ ]: Value is derived from parent definition - : Value is not set and derived from default definition Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/mt76x8: fix IMAGE_SIZE for all devicesAdrian Schmutzler2019-07-251-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes IMAGE_SIZE for all devices based on the partition size given in DTS: DEVICE *.MK *.DTS VERDICT alfa-network_awusfree1 (8M) 0x7b0000 buffalo_wcr-1166ds - 0x7c0000 wrong cudy_wr1000 (8M) 0x7b0000 d-team_pbr-d1 (16M) 0x0fb0000 duzun_dm06 - 0x7b0000 default glinet_gl-mt300n-v2 16064k 0xfb0000 glinet_vixmini 7872k 0x7b0000 hilink_hlk-7628n (32M) 0x1fb0000 hiwifi_hc5661a (16M) 0xf70000 wrong hiwifi_hc5861b 15808k 0xf70000 mediatek_linkit-smart-7688 (32M) 0x1fb0000 mediatek_mt7628an-eval-board (4M) 0x7b0000 wrong mercury_mac1200r-v2 - 0x7c0000 wrong netgear_r6120 15744k 0xf60000 onion_omega2 (16M) 0xfb0000 onion_omega2p (32M) 0x1fb0000 rakwireless_rak633 - 0x7b0000 default skylab_skw92a 16064k 0xfb0000 tama_w06 15040k 0xeb0000 totolink_lr1200 7872k 0x7b0000 tplink_archer-c20-v4 7808k 0x7a0000 tplink_archer-c50-v3 7808k 0x7a0000 tplink_archer-c50-v4 7616k 0x770000 tplink_tl-mr3020-v3 7808k 0x7a0000 tplink_tl-mr3420-v5 7808k 0x7a0000 tplink_tl-wa801nd-v5 7808k 0x7a0000 tplink_tl-wr802n-v4 7808k 0x7a0000 tplink_tl-wr840n-v4 7808k 0x7a0000 tplink_tl-wr840n-v5 3904k 0x3d0000 tplink_tl-wr841n-v13 7808k 0x7a0000 tplink_tl-wr841n-v14 3968k 0x3e0000 tplink_tl-wr842n-v5 7808k 0x7a0000 tplink_tl-wr902ac-v3 7808k 0x7a0000 unielec_u7628-01-128m-16m 16064k 0xfb0000 vocore_vocore2 (16M) 0xfb0000 vocore_vocore2-lite (16M) 0x7b0000 wrong wavlink_wl-wn570ha1 (8M) 0x7b0000 wavlink_wl-wn575a3 (8M) 0x7b0000 widora_neo-16m (16M) 0x0fb0000 widora_neo-32m (32M) 0x1fb0000 wiznet_wizfi630s (32M) 0x1fb0000 wrtnode_wrtnode2p (16M) 0x1fb0000 wrong wrtnode_wrtnode2r (16M) 0x1fb0000 wrong xiaomi_mir4a-100m 14976k 0xea0000 xiaomi_miwifi-nano (16M) 0xfb0000 zbtlink_zbt-we1226 (8M) 0x7b0000 zyxel_keenetic-extra-ii 14912k 0xe90000 No verdict means that the device is correctly set. Legend: ( ): Value is set via ralink_default_fw_size_xxM [ ]: Value is derived from parent definition - : Value is not set and derived from default definition Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/mt7621: fix IMAGE_SIZE for all devicesAdrian Schmutzler2019-07-251-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes IMAGE_SIZE for all devices based on the partition size given in DTS: DEVICE *.MK *.DTS VERDICT afoundry_ew1200 (16M) 0xfb0000 asiarf_ap7621-001 (16M) 0xfa0000 wrong buffalo_wsr-1166dhp (16M) 0xf90000 wrong buffalo_wsr-600dhp (16M) 0xfb0000 dlink_dir-860l-b1 (16M) 0xfb0000 d-team_newifi-d2 (32M) 0x1fb0000 d-team_pbr-m1 (16M) 0xfb0000 elecom_wrc-1167ghbk2-s 15488k 0xf20000 elecom_wrc-1900gst 11264k 0xb00000 elecom_wrc-2533gst 11264k 0xb00000 firefly_firewrt (16M) 0xfb0000 gehua_ghl-r-001 (32M) 0x1fb0000 gnubee_gb-pc1 (32M) 0x1fb0000 gnubee_gb-pc2 (32M) 0x1fb0000 hiwifi_hc5962 (32M) 0x2000000 wrong (kernel + ubi) iodata_wn-ax1167gr 15552k 0xf30000 iodata_wn-gx300gr 7798784 0x770000 lenovo_newifi-d1 (32M) 0x1fb0000 linksys_re6500 - 0x7b0000 default mediatek_ap-mt7621a-v60 (8M) 0x7b0000 mediatek_mt7621-eval-board (4M) 0xec0000 wrong (rootfs) mikrotik_rb750gr3 [16128k] 0xfc0000 mikrotik_rbm11g [16128k] 0xFC0000 mikrotik_rbm33g [16128k] 0xFC0000 mqmaker_witi-256m (16M) 0xfb0000 mqmaker_witi-512m (16M) 0xfb0000 mtc_wr1201 16000k 0xfa0000 netgear_ex6150 14848k 0xe80000 netgear_r6220 28672k 0x1c00000 netgear_r6350 40960k 0x2800000 netgear_wndr3700-v5 15232k 0xee0000 netis_wf-2881 129280k 0x7E40000 phicomm_k2p 15744k 0xf60000 planex_vr500 66453504 0x3fb0000 wrong samknows_whitebox-v8 (16M) 0xfb0000 storylink_sap-g3200u3 - 0x7b0000 default telco-electronics_x1 16064k 0xfb0000 thunder_timecloud - 0xfb0000 wrong totolink_a7000r 16064k 0xfb0000 tplink_re350-v1 6016k 0x5e0000 ubiquiti_edgerouterx - 0xfa00000 wrong (kernel1 + ubi) ubiquiti_edgerouterx-sfp - 0xfa00000 wrong (kernel1 + ubi) unielec_u7621-06-256m-16m 16064k 0xfb0000 unielec_u7621-06-512m-64m 65216k 0x3fb0000 wevo_11acnas (16M) 0xfb0000 wevo_w2914ns-v2 (16M) 0xfb0000 xiaomi_mir3g 32768k 0x7980000 wrong (kernel + ubi) xiaomi_mir3p (32M) 0xf980000 wrong (kernel + ubi) xzwifi_creativebox-v1 (32M) 0x1fb0000 youhua_wr1200js 16064k 0xfb0000 youku_yk-l2 (16M) 0xfb0000 zbtlink_zbt-we1326 (16M) 0xfb0000 zbtlink_zbt-we3526 (16M) 0xfb0000 zbtlink_zbt-wg2626 (16M) 0xfb0000 zbtlink_zbt-wg3526-16m (16M) 0xfb0000 zbtlink_zbt-wg3526-32m (32M) 0x1fb0000 No verdict means that the device is correctly set. Legend: ( ): Value is set via ralink_default_fw_size_xxM [ ]: Value is derived from parent definition - : Value is not set and derived from default definition Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/mt7620: fix IMAGE_SIZE for all devicesAdrian Schmutzler2019-07-251-13/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes IMAGE_SIZE for all devices based on the partition size given in DTS: DEVICE *.MK *.DTS VERDICT aigale_ai-br100 7936k 0x7c0000 alfa-network_ac1200rm 16064k 0xfb0000 alfa-network_tube-e4g 16064k 0xfb0000 asus_rp-n53 - 0x7b0000 default asus_rt-ac51u (16M) 0xfb0000 asus_rt-n12p - 0xfb0000 wrong asus_rt-n14u - 0xfb0000 wrong bdcom_wap2100-sk 15808k 0xf70000 buffalo_whr-1166d 15040k 0xfb0000 wrong buffalo_whr-300hp2 6848k 0x7b0000 wrong buffalo_whr-600d 6848k 0x7b0000 wrong buffalo_wmr-300 - 0x7b0000 default comfast_cf-wr800n - 0x7b0000 default dlink_dch-m225 6848k 0x6b0000 dlink_dir-510l - 0xde0000 wrong dlink_dir-810l 6720k 0x690000 dlink_dwr-116-a1 - 0x7e0000 wrong dlink_dwr-118-a1 - 0xfe0000 wrong dlink_dwr-118-a2 - 0xfe0000 wrong dlink_dwr-921-c1 (16M) 0xfe0000 wrong dlink_dwr-921-c3 [(16M)] 0xfe0000 wrong dlink_dwr-922-e2 (16M) 0xfe0000 wrong dovado_tiny-ac - 0x7b0000 default edimax_br-6478ac-v2 7616k 0x00790000 wrong edimax_ew-7476rpc 7744k 0x00790000 edimax_ew-7478ac 7744k 0x00790000 edimax_ew-7478apc 7744k 0x00790000 elecom_wrh-300cr (16M) 0xdf0000 wrong glinet_gl-mt300a (16M) 0xf80000 wrong glinet_gl-mt300n (16M) 0xf80000 wrong glinet_gl-mt750 (16M) 0xf80000 wrong head-weblink_hdrm200 16064k 0xfb0000 hiwifi_hc5661 15872k 0xf80000 hiwifi_hc5761 15872k 0xf80000 hiwifi_hc5861 15872k 0xf80000 hnet_c108 16777216 0xfb0000 wrong iodata_wn-ac1167gr 6864k 0x6b4000 iodata_wn-ac733gr3 6992k 0x6d4000 kimax_u25awf-h1 16064k 0xfb0000 kimax_u35wf 16064k 0xfb0000 kingston_mlw221 15744k 0xf60000 kingston_mlwg2 15744k 0xf60000 lava_lr-25g001 - 0xfe0000 wrong lenovo_newifi-y1 (16M) 0xfb0000 lenovo_newifi-y1s (16M) 0xfb0000 linksys_e1700 - 0x7b0000 default microduino_microwrt 16128k 0xfc0000 netgear_ex2700 (4M) 0x3b0000 netgear_ex3700 7744k 0x790000 netgear_wn3000rp-v3 - 0x7b0000 default nexx_wt3020-4m (4M) 0x3b0000 nexx_wt3020-8m - 0x7b0000 default ohyeah_oy-0001 (16M) 0xfb0000 phicomm_k2g 7552k 0x760000 phicomm_psg1208 - 0x7b0000 default phicomm_psg1218a - 0x7b0000 default phicomm_psg1218b - 0x7b0000 default planex_cs-qr10 - 0x7b0000 default planex_db-wrt01 - 0x7b0000 default planex_mzk-750dhp - 0x7b0000 default planex_mzk-ex300np - 0x730000 wrong planex_mzk-ex750np - 0x730000 wrong ralink_mt7620a-evb - 0x7b0000 default ralink_mt7620a-mt7530-evb - 0x7b0000 default ralink_mt7620a-mt7610e-evb - 0x7b0000 default ralink_mt7620a-v22sg-evb - 0x7f80000 wrong ravpower_wd03 (8M) 0x7b0000 sanlinking_d240 (16M) 0xfb0000 sercomm_na930 20m 0x1400000 tplink_archer-c20i - 0x7a0000 wrong tplink_archer-c20-v1 - 0x7a0000 wrong tplink_archer-c2-v1 - 0x7a0000 wrong tplink_archer-c50-v1 - 0x7a0000 wrong tplink_archer-mr200 - 0x7b0000 default vonets_var11n-300 (4M) 0x3b0000 wrtnode_wrtnode (16M) 0xfb0000 xiaomi_miwifi-mini (16M) 0xf80000 wrong youku_yk1 (32M) 0x1fb0000 yukai_bocco - 0x7b0000 default zbtlink_we1026-5g-16m 16777216 0xfb0000 wrong zbtlink_zbt-ape522ii - 0xf80000 wrong zbtlink_zbt-cpe102 - 0x760000 wrong zbtlink_zbt-wa05 - 0x760000 wrong zbtlink_zbt-we2026 - 0x760000 wrong zbtlink_zbt-we826-16m (16M) 0xfb0000 zbtlink_zbt-we826-32m (32M) 0x1fb0000 zbtlink_zbt-we826-e 32448k 0x1fb0000 zbtlink_zbt-wr8305rt - 0x7b0000 default zte_q7 - 0x7b0000 default zyxel_keenetic-omni - 0x7b0000 default zyxel_keenetic-omni-ii - 0x7b0000 default zyxel_keenetic-viva 16064k 0xfb0000 No verdict means that the device is correctly set. Legend: ( ): Value is set via ralink_default_fw_size_xxM [ ]: Value is derived from parent definition - : Value is not set and derived from default definition Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: support IMAGE_SIZE in kiB for Build/trxAdrian Schmutzler2019-07-251-1/+1
| | | | Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix ralink_default_fw_size_16MAdrian Schmutzler2019-07-255-6/+6
| | | | | | | | | | | | | | | | | | | | | | In ramips, there are the following predefined values for IMAGE_SIZE ralink_default_fw_size_4M 3866624 3776k 0x3B0000 ralink_default_fw_size_8M 8060928 7872k 0x7B0000 ralink_default_fw_size_16M 16121856 15744k 0xF60000 ralink_default_fw_size_32M 33226752 32448k 0x1FB0000 Out of those, the "16M" value is obviously odd, as it provides more room for the remaining partitions than the tree others. Of the devices in all subtargets, there are actually > 50 that have a firmware partition with 0xFB0000 size, while only 5 (!) have 0xF60000. From the former, many are set to ralink_default_fw_size_16M anyway, although it is wrong at the present point. Consequently, it makes sense to change ralink_default_fw_size_16M to 0xFB0000, and to update IMAGE_SIZE for the 5 devices with 0xF60000. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips/rt305x: fix firmware partition size for some 4MB devicesAdrian Schmutzler2019-07-253-3/+3
| | | | | | | | | | | | | | | allnet_all0256n-4m, tenda_w150m and unbranded_wr512-3gn-4m have their firmware partition set to reg = <0x50000 0x3c8000>. However, based on the 4MB flash, the size should be 0x3b0000. After some research in the target's history, it looks like the changed size has been a mistake when transferring device partitions from Makefile to DTS in 770b28f146f. This patch changes the named three devices back to 0x3b0000. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix mac addresses used by Phicomm K2PChuanhong Guo2019-07-251-0/+4
| | | | | | | | | | | Like most mt7621 boards, Phicomm K2P stores LAN/WAN mac addresses at 0xe000/0xe006 of factory partition. Phicomm uses lan_mac-1 as wan_mac, while our default case in 02_network uses lan_mac+1. Add a special case reading lan/wan mac address for Phicomm K2P. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: add kmod-mt7615e to Phicomm K2P imagesRoger Pueyo Centelles2019-07-251-0/+1
| | | | | | | | | | | | Now that the mt76 driver supports the MT7615D chip found on these devices, use it. Also add the wpad-basic package. Note: the driver supports operation on both the 2.4 GHz and the 5 GHz bands, but not yet concurrently. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* kernel: netfilter add connmark savedscp supportKevin Darbyshire-Bryant2019-07-252-0/+242
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | savedscp is a method of storing the DSCP of an ip packet into conntrack mark. In combination with a suitable tc filter action (conndscp but may end up being integrated into connmark) DSCP values are able to be stored on egress and restored on ingress across links that otherwise alter or bleach DSCP. This is useful for qdiscs such as CAKE which are able to shape according to policies based on DSCP. Ingress classification is traditionally a challenging task since iptables rules haven't yet run and tc filter/eBPF programs are pre-NAT lookups, hence are unable to see internal IPv4 addresses as used on the typical home masquerading gateway. The ingress problem is solved by the tc filter, but the tc people didn't like the idea of tc setting conntrack mark values, though they are ok with reading conntrack values and hence restoring DSCP from conntrack marks. x_tables CONNMARK with the new savedscp action solves the problem of storing the DSCP to the conntrack mark. It accepts 2 parameters. The mark is a 32bit value with usually one 1 bit set. This bit is set when savedscp saves the DSCP to the mark. This is useful to implement a 'one shot' iptables based classification where the 'complicated' iptables rules are only run once to classify the connection on initial (egress) packet and subsequent packets are all marked/restored with the same DSCP. A mark of zero disables the setting of a status bit/s. The mask is a 32bit value of at least 6 contiguous bits and represents the area where the DSCP will be stored. e.g. iptables -A QOS_MARK_eth0 -t mangle -j CONNMARK --savedscp-mark 0xfc000000/0x01000000 Would store the DSCP in the top 6 bits of the 32bit mark field, and use the LSB of the top byte as the 'DSCP has been stored' marker. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ar71xx: fix WLAN LED names for Archer C7Tomislav Požega2019-07-251-2/+2
| | | | | | Update WLAN LED colour identifier for both interfaces on Archer C7 Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
* ar71xx: fix system LED names on Archer C5/C7Tomislav Požega2019-07-251-2/+2
| | | | | | | Move system LED board definitions of Archer C5/C7 to reflect actual system LED colour used Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
* ar71xx: Archer C7 v1 LED names and RFKILL fixesTomislav Požega2019-07-251-10/+10
| | | | | | | | | | All leds on these boards are green. v1 has RFKILL GPIO 23 for production units (it had GPIO 13 only for test phase units, and these are rather very rare to find). As for the previous attempt to fix this and revert due to WDR boards have blue leds, it was wrong: WDR board does not use common setup (false). Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
* ar71xx: update qca-usb-quirks patchTomislav Požega2019-07-251-1/+1
| | | | | | | Base address for USB0 has changed from 0x18116c94 on AR934X to 0x18116d94 on QCA9558. CP Typo remained for years here... Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com>
* ath79: fix indent in 01_ledsAdrian Schmutzler2019-07-241-2/+2
| | | | | | | | | Change capitalization from spaces to tabs in order to match the style of the file. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> [fix capitalization in commit title, add short description] Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for D-Link DIR-842 C2Jackson Lim2019-07-246-0/+216
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware spec of DIR-842 C2: SoC: QCA9563 DRAM: 128MB DDR2 Flash: 16MB SPI-NOR Switch: QCA8337N WiFi 5.8GHz: QCA9888 WiFi 2.4Ghz: QCA9563 USB: 2.0 Flash instructions: 1. Upgrade the factory.bin through the factory web interface or the u-boot failsafe interface. The firmware will boot up correctly for the first time. Do not power off the device after OpenWrt has booted. Otherwise the u-boot will enter failsafe mode as the checksum of the firmware has been changed. 2. Upgrade the sysupgrade.bin in OpenWrt. After upgrading completes the u-boot won't complain about the firmware checksum and it's OK to use now. 3. If you powered off the device before upgrading the sysupgrade.bin, just upgrade the factory.bin through the u-boot failsafe interface and then goto step 2. Signed-off-by: Jackson Lim <jackcolentern@gmail.com> [Reword reset-hog comment, fix formatting] Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: enable Newifi D1 SD slotDENG Qingfang2019-07-231-1/+1
| | | | | | | Newifi D1 is shipped with an 8GB microSD card in its SD slot Without SD driver users would not be able to use it unless manually installed Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* treewide: sysupgrade: get rid of platform_nand_pre_upgrade()Rafał Miłecki2019-07-228-88/+64
| | | | | | | | | | | 1) nand_do_upgrade() is always called by a target code 2) nand_do_upgrade() starts with calling platform_nand_pre_upgrade() It means there is no need for the platform_nand_pre_upgrade() callback at all. All code that was present there could bo moved & simplly called by a target right before the nand_do_upgrade(). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* layerscape: sysupgrade: get rid of platform_pre_upgrade()Rafał Miłecki2019-07-221-9/+8
| | | | | | | | | | 1) RAMFS_COPY_BIN and RAMFS_COPY_DATA can be defined at top of the file like it's done for all other targets. 2) fw_printenv.lock can be created one step later in the platform_do_upgrade(). It seems to be working well on many other targets. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* mac80211: Update to version 5.2-rc7Hauke Mehrtens2019-07-183-217/+1
| | | | | | | | | | | | | | This updates mac80211 to version 5.2-rc7, this contains all the changes to the wireless subsystem up to Linux 5.2-rc7. * The removed patches are applied upstream * b43 now uses kmod-lib-cordic * Update the nl80211.h file in iw to match backports version. * Remove the two backports from kernel 4.9, they were needed for mt76, but that can use the version from backports now, otherwise they collide and cause compile errors. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: modify device name of I-O DATA WN-AC1600DGR2INAGAKI Hiroshi2019-07-182-5/+6
| | | | | | | | | | | | | | | | | | | | | | | The hardware of I-O DATA WN-AC1600DGR3 has completely compatibility with WN-AC1600DGR2, so modify the device name of WN-AC1600DGR2 to show the images for DGR2 also support DGR3. Specification of WN-AC1600DGR3: - SoC : Qualcomm Atheros QCA9557 - RAM : DDR2 128 MiB - Flash : SPI-NOR 16 MiB - WLAN : 2.4/5 GHz - 2.4 GHz : QCA9557 (SoC), 2T2R - 5 Ghz : QCA9880, 3T3R - Ethernet : 5x 10/100/1000 Mbps - Switch : QCA8337N - LEDs/Input : 6x/6x (4x buttons, 1x slide-switch) - UART : through-hole on PCB - J1: Vcc, GND, TX, RX from ethernet port side - 115200n8 Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ath79: Add support for TP-Link Archer C60 v2Adrian Schmutzler2019-07-185-2/+79
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C60 v2 is a dual-band AC1350 router, based on Qualcomm/Atheros QCA9561 + QCA9886. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 2T2R 5 GHz - 5x 10/100 Mbps Ethernet - 7x LED, 2x button - UART header on PCB Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed IP address 192.168.0.66 2. Download *-factory.bin image and rename it to tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin in its root directory 4. Turn off the router 5. Press and hold reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery Flash instruction (under U-Boot, using UART): tftp 0x81000000 ...-sysupgrade.bin erase 0x9f030000 +$filesize cp.b $fileaddr 0x9f030000 $filesize reset Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: Add support for TP-Link Archer C60 v1Adrian Schmutzler2019-07-186-1/+186
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C60v1 is a dual-band AC1350 router, based on Qualcomm/Atheros QCA9561+QCA9886. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 2T2R 5 GHz - 5x 10/100 Mbps Ethernet - 7x LED, 2x button - UART header on PCB Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed ip address 192.168.0.66 2. Download *-factory.bin image and rename it to tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin in its root directory 4. Turn off the router 5. Press and hold Reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery. Flash instruction under U-Boot, using UART: 1. tftp 0x81000000 ...-sysupgrade.bin 2. erase 0x9f020000 +$filesize 3. cp.b $fileaddr 0x9f020000 $filesize 4. reset Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link CPE510-v2/v3Andrew Cameron2019-07-186-0/+215
| | | | | | | | | | | | | | | | | | | | | | | | | TP-Link CPE510-v2/v3 is an outdoor wireless CPE for 5 GHz with one Ethernet port based on Atheros AR9344 Specifications: - Based on the same underlying hardware as the TP-Link CPE510 - Power, LAN, and 4 green LEDs - 1 10/100Mbps Shielded Ethernet Port (Passive PoE in) - Built-in 13dBi 2x2 dual-polarized directional MIMO antenna - Adjustable transmission power from 0 to 23dBm/200mw Flashing instructions: Flash factory image through stock firmware WEB UI or through TFTP To get to TFTP recovery just hold reset button while powering on for around 4-5 seconds and release. Rename factory image to recovery.bin Stock TFTP server IP:192.168.0.100 Stock device TFTP adress:192.168.0.254 Signed-off-by: Andrew Cameron <apcameron@softhome.net> [whitespace fixes] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: add support for Trendnet TEW-823DRUPramod Pancha2019-07-185-1/+249
| | | | | | | | | | | | | | | | | | | | | Trendnet TEW-823DRU is a dual-band AC1750 router. The router is based on Qualcomm/Atheros QCA9558 + QCA9880. Specification: 720 MHz CPU 256 MB of RAM 16 MB of FLASH 3T3R 2.4 GHz 3T3R 5 GHz 5x 10/100/1000 Mbps Ethernet Firmware can be flashed from the web interface. Tested on 3 routers with no issues. Signed-off-by: Pramod Pancha <pancha@vill.com> [whitespace fixes] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: add support for TP-Link RE355 v1 and RE450 v1Christoph Krapp2019-07-178-0/+240
| | | | | | | | | | | | | | | | | | | | | | Specification: SoC: Qualcomm Atheros QCA9558 RAM: 64/128MiB Flash: 8MiB SPI-NOR Wifi: - 2.4GHz: 3T3R (QCA9558) - 5GHz: 3T3R (QCA9880) LAN: 1x 10/100/1000 Mbps UART: - TP1: Tx - TP2: Rx - TP3: Gnd - TP4: 3v3 Flash instructions: Flash factory image through stock firmware WEB UI. Signed-off-by: Christoph Krapp <achterin@googlemail.com>
* ramips: add support for TP-Link RE650 v1Georgi Vlaev2019-07-174-9/+204
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link RE650 v1 is a dual-band AC2600 range extender, based on MediaTek MT7621A and MT7615E. According to the wikidevi entry for RE650 this device is identical with TP-Link RE500 as hardware. This patch supports only RE650. Hardware specification: - SoC 880 MHz - MediaTek MT7621AT - 128 MB of DDR3 RAM - 16 MB - Winbond 25Q128FVSG - 4T4R 2.4 GHz - MediaTek MT7615E - 4T4R 5 GHz - MediaTek MT7615E - 1x 1 Gbps Ethernet - MT7621AT integrated - 7x LEDs (Power, 2G, 5G, WPS(x2), Lan(x2)) - 4x buttons (Reset, Power, WPS, LED) - UART header (J1) - 2:GND, 3:RX, 4:TX Serial console @ 57600,8n1 Flash instructions: Upload openwrt-ramips-mt7621-tplink_re650-v1-squashfs-factory.bin from the RE650 web interface. TFTP recovery to stock firmware: Unfortunately, I can't find an easy way to recover the RE without opening the device and using modified binaries. The TFTP upload will only work if selected from u-boot, which means you have to open the device and attach to the serial console. The TFTP update procedure does *not* accept the published vendor firmware binaries. However, it allows to flash kernel + rootfs binaries, and this works if you have a backup of the original contents of the flash. It's probably possible to create special image out of the vendor binaries and use that as recovery image. Signed-off-by: Georgi Vlaev <georgi.vlaev@gmail.com> [re-added variables for kernel header] Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for Bluesocket BSAP1880 boardDaniel Gimpelevich2019-07-178-0/+173
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This board was used in dual-band 802.11n enterprise access points, models BSAP-1800v2 and BSAP-1840, introduced in 2010 by Bluesocket, which was acquired by Adtran in 2011, who has now EOL'ed them. They differed only in that the BSAP-1840's antennae were detachable, while the BSAP-1800v2's were inside the case. They have an external RJ-45 console port, which works with standard Cisco 72-3383-01 console cables. Specification: - System-On-Chip: AR7161 - CPU/Speed: 600 MHz - Flash-Chip: Macronix MX25L12845E - Flash size: 16 MiB - RAM: 64 MiB - Wireless No1: Lite-On WN2601A card: AR9160/AR9103 2.4GHz 802.11bgn - Wireless No2: Lite-On WN2502A card: AR9160/AR9106 5GHz 802.11an - PHY: Vitesse VSC8601, Rev. B Installation: 1. Connect to the serial console using a terminal that supports YMODEM at 115200 bps, 8 data bits, no parity, 1 stop bit 2. Interrupt the bootloader using its password, which is: r00t 3. Issue the "fis init" command, confirming if prompted 4. Look at the length of the openwrt-ath79-generic-*-squashfs-kernel.bin file, and substitute it below, instead of where I have "LeNgTh" 5. Issue the following command, and upload this file using YMODEM protocol load -r -v -b 0x80060000 -m ymodem 6. Issue the following commands, substituting as mentioned above: fis create -b 0x80060000 -l LeNgTh vmlinux_2 load -r -v -b 0x80100000 -m ymodem 7. Using YMODEM, upload openwrt-ath79-generic-*-squashfs-rootfs.bin 8. Issue the "fis free" command, and for the first range in its response, use a hexadecimal calculator to subtract the start from the end in order to substitute it below, with the leading "0x" to specify it in hexadecimal, instead of where I have "LeNgTh" 9. Issue the following commands, substituting as mentioned above: fis create -b 0x80100000 -l LeNgTh -e 0 -r 0 rootfs reset 10.Wait for the status LED to go solid green Tested-by: Brian Gonyer <bgonyer@gmail.com> Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> [fixed obsolete $ARGV in platform_do_upgrade] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: widen RedBoot directory search and add PHYDaniel Gimpelevich2019-07-171-1/+2
| | | | | | | | The Bluesocket BSAP1880 board has a Vitesse PHY, for which the driver was not being included, and its RedBoot directory block is earlier in the flash than the search was allowing. This commit prepares for supporting it. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* ath79: support "rgmii-id" PHY mode in ag71xxDaniel Gimpelevich2019-07-171-0/+2
| | | | | | | The ag71xx code did not include a case for the "rgmii-id" PHY mode in the code. There are devices that need this mode, so I'm adding it. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* brcm47xx: fix 831-old_gpio_wdt.patch for linux 4.19Zachary Cook2019-07-171-2/+2
| | | | | | | | | | | | Fix the following compilation error when using linux 4.19 on brcm47xx: drivers/watchdog/old_gpio_wdt.c:236:2: error: implicit declaration of function 'setup_timer' setup_timer was removed and replaced by timer_setup in linux >=4.15: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=513ae785 Update the patch to use the timer_setup interface Signed-off-by: Zachary Cook <zachcook1991@gmail.com>
* ath79: ar9330: add missing watchdog nodePetr Štetiar2019-07-171-0/+10
| | | | | | | | It was reported in FS#2385, that Carambola2 doesn't currently have working watchdog so fix it by adding watchdog node. Ref: FS#2385 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: add MT7615 wireless support for ELECOM WRC-1167GHBK2-SINAGAKI Hiroshi2019-07-172-4/+12
| | | | | | | | | | | | | ELECOM WRC-1167GHBK2-S has a MediaTek MT7615D chip for 2.4/5 GHz wireless. A driver package for MT7615 chip is added to OpenWrt in a0e5ca4f3523b9eef96bff32e45f6fa8275b982f, so add preliminary MT7615 chip support for WRC-1167GHBK2-S. Note: Currently, DBDC mode for MT7615 is not supported in mt76 driver. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* kernel: generic: fix perf build breakage on 4.19Petr Štetiar2019-07-171-40/+0
| | | | | | | | | | | | Drop 211-host_tools_portability.patch which is breaking perf build on 4.19 kernels by removing the include directory from the host's CFLAGS leading to the following build breakage: pmu-events/jevents.c:48:10: fatal error: linux/list.h: No such file or directory #include <linux/list.h> ^~~~~~~~~~~~~~ Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: apalis: add missing jffs2reset to ramfs during sysupgradePetr Štetiar2019-07-171-1/+1
| | | | | | | | | | | | | jffs2reset is used to cleanup the rootfs_data overlay, but it's currently missing in the ramfs during sysupgrade leading to the following error: Switching to ramdisk... Performing system upgrade... /lib/upgrade/do_stage2: line 27: jffs2reset: not found Fixes: 2f1a11d0089c ("imx6: apalis: fix config survival after sysupgrade -n") Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: apalis: fix sysupgrade pathsPetr Štetiar2019-07-171-5/+2
| | | | | | | | We can't use $board_name in sysupgrade paths for kernel and rootfs as we currently generate one image which could be used on two different base boards. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: add modern network modules to Generic targetAlberto Bursi2019-07-171-1/+2
| | | | | | | | | | | | | | | Many Atom-based embedded/industrial x86 boards can't run 64bit operating systems due to either processor or board firmware limitations, but they have modern interfaces (PCIe) or have modern Intel gigabit controllers onboard. With the current default package selection for x86 Generic target their network won't work. Add the modern gigabit network modules needed or most likely going to be used as add-in cards, similar to what is the list on x86_64 target. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it> [fixed whitespace issue] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* mvebu: sysupgrade: don't use $ARGV in platform_check_image()Rafał Miłecki2019-07-171-1/+1
| | | | | | | sysupgrade passes image path to platform_check_image() as an argument so it can be simply accessed using $1 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: sysupgrade: don't use $ARGV in platform_do_upgrade()Rafał Miłecki2019-07-1716-45/+45
| | | | | | | stage2 passes image path to platform_do_upgrade() as an argument so it can be simply accessed using $1 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: get rid of platform_pre_upgrade()Rafał Miłecki2019-07-161-12/+8
| | | | | | | | | | | The only step between platform_pre_upgrade() and platform_do_upgrade() is switching to ramdisk. It should be fine to "mtd erase firmware" from the later callback and get rid of the first one. This change wasn't tested on affected target but identical code logic was verified to work as expected on brcm47xx with initramfs firmware. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ar71xx: get rid of platform_pre_upgrade()Rafał Miłecki2019-07-161-27/+23
| | | | | | | | | | | The only step between platform_pre_upgrade() and platform_do_upgrade() is switching to ramdisk. It should be fine to "mtd erase firmware" from the later callback and get rid of the first one. This change wasn't tested on affected target but identical code logic was verified to work as expected on brcm47xx with initramfs firmware. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 15:31:36 +0000